Files
PaperClipAI/server/src/__tests__/environment-execution-target-duplex.test.ts
T
Nicky LeachandClaude Opus 5.5 11ac90e31f fix(build): typecheck server/src/__tests__ and fix every type error (#18739)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work
> - The server has about 1,100 test and helper files in
`server/src/__tests__`
> - `server/tsconfig.json` excludes that directory, Vitest does not
check types, and no script runs the tsconfig in that directory
> - So a test can call a function with the wrong arguments and still
pass, and no tool reports it
> - This gap hid 2,168 real type errors, and some of them hid tests that
did not test what they claim
> - This pull request fixes all of these errors and adds the directory
to the server layers from paperclipai/paperclip#18737
> - The benefit is that a type error in a server test now fails the
typecheck, with no baseline and no backlog

## Linked Issues or Issue Description

Refs paperclipai/paperclip#18737, which is merged and added the server
layers. Refs paperclipai/paperclip#18738, which is merged and checks the
test projects outside `pnpm -r`, so it is not a duplicate. Refs
paperclipai/paperclip#18137, which records that this directory has no
check.

**What happened?**

No tool checked the types of 1,074 of the 1,101 files in
`server/src/__tests__`. I searched `package.json`, the workflows, and
all tsconfig files. 27 files are in the program of another tsconfig, and
these 27 have 0 errors. 11 of the 27 are in
`helpers/maintenance/tsconfig.json`. No script ran that project when I
measured this. paperclipai/paperclip#18738 now runs it.

**Expected behavior**

The server typecheck checks these files, and a type error fails the
check.

**Steps to reproduce**

1. On the base commit, run `tsc -p server/src/__tests__/tsconfig.json
--noEmit`. It reports 6,536 errors and needs 12.3 GiB.
2. Add a type error to any file in `server/src/__tests__`.
3. Run `pnpm --filter @paperclipai/server typecheck`. It passes.

**Paperclip version or commit**

I measured the error breakdown below on commit `8dfd632452`, with
TypeScript 7.0.2. The branch now includes master up to
paperclipai/paperclip#18865.

**Deployment mode**

Not applicable. This issue applies to development and CI. No production
source file in the server changes.

### Error breakdown

Each row adds one change to the row above.

| Step | Total errors | Change | Cause |
| --- | --- | --- | --- |
| Config as committed | 6,536 | | |
| Add `src/types/*.d.ts` | 4,447 | -2,089 | Config. The Express request
types were missing. |
| Set `rootDir` to the repository root | 2,436 | -2,011 | Config. |
| Set `allowImportingTsExtensions` | 2,181 | -255 | Config. Vitest
accepts `.ts` imports. |
| Add `ES2024.Promise` to `lib` | 2,138 | -43 | Config. Node 24 has
`Promise.withResolvers`. |
| Set `allowJs` for `.mjs` imports | 2,148 | +10 | Config. It removes 8
`TS7016` errors and shows new real errors. |
| Set `declaration` to false | 2,142 | -6 | Config. Tests emit nothing.
|
| Count only files in `server/src` | 2,058 | -84 | Other packages: 53
Daytona, 29 Runner test, 2 UI. |

So 4,478 of the 6,536 errors (69%) came from config or scope, and 2,058
are real type errors in 314 files. The 29 Runner test errors are also
real, which gives 2,087 errors. Tests that master added after this
measurement had 81 more errors, so this pull request fixes 2,168 errors.

This table classifies the first 2,058 errors.

| Kind of real error | Errors |
| --- | --- |
| Wrong argument or assignment type | 1,023 |
| Stale or partial fixture objects | 525 |
| Property that the type does not have | 317 |
| Missing narrowing of null or unknown | 101 |
| Implicit any | 60 |
| Missing name or module | 16 |
| Other | 16 |

### What the type errors hid

Most errors were stale fixtures and loose mocks. These errors hid real
test problems, and this pull request fixes them:

- **A test that never ran.** `instrumentation.test.ts` required
`sdk-trace-base`, which is not installed. So 3 span tests were skipped.
They now run and pass.
- **Assertions that could not fail.**
- `issue-thread-interactions-service` used a company ID as an issue ID.
- `status-card-evaluation-work` compared `[]` with `[]` in a rollback
check.
- `slack-conversation-lifecycle` read `item.issueId`, which does not
exist.
  - `email-channels` used a permission key that does not exist.
- `heartbeat-project-env` imported `LOW_TRUST_REVIEW_PRESET`, which is
not exported. The value was undefined.
- **Postgres processes that did not stop.** 11 test files called `stop`
on the test database helper. That method does not exist, and the helper
method is `cleanup`.
- **Arguments that the service ignored.**
- `methodKey` is now `connectionMethodKey` in the Daytona, Unikraft,
1Password, and Railway tests.
- 108 calls passed `"owner-user"` to a parameter that expects an options
object.
- 9 chat wizard fixtures passed `managementContext` as `source`, so they
ran `existing_app` and not `manifest`.
  - 2 tests passed a `{ userId }` actor that the function ignores.
- Inserts into `environments` passed a `companyId` column that the table
does not have.
- **Problems in tests that master added during this work.**
- `sandbox-creation-operations` read `database.connectionString` when an
external test database was set. In that mode `database` is undefined, so
the fixture would stop with a TypeError. It now uses the external URL.
- `idle-completed-history` set a Dot operation to `dispatched`. That is
a Muse status, and the Dot type does not have it. The fixture now uses
`admitted`, which is a real in-flight Dot status.

### Possible product problems, not changed

These may be real problems in production code or types. I did not change
them, because this pull request does not change production behavior:

- `decisions-service` `service.create` does not validate the lenient
`cancel_issue_tree` input.
- `createConnection` ignores `input.connectionPurpose`.
- The `createConnection` route schema default stores `{}` for
`transportConfig`.
- `prepareManagedAiRuntime` accepted the invalid value `mode:
"connection"`.
- `createBinding` accepts invalid `projectionClass` strings outside
class 3.
- `ensureManagedProjectWorkspace` forwards an untyped `repoRef` by
spread.
- `routineVariableSchema.label` is optional, but `RoutineVariable.label`
is required.
- `ToolRunContext.projectId` may be too strict.
- `withdrawInteraction` reads `issue.status`, which its type omits.
- `issueService.list` and `reconcileNativeFinalizations` omit fields
that they return at runtime.
- `createGitHubExternalObjectProvider` handles `tokenProvider: null`,
but its type forbids this value.

## What Changed

- Fixed the 2,168 type errors. The diff changes 322 test and helper
files.
- Corrected `server/src/__tests__/tsconfig.json`. Editors and the
typecheck now read the same options and report the same errors.
- Added three `test-tree` layers to
`server/scripts/typecheck-layers.mjs`. They read the server layers as
declarations, and any error fails them. A hash of the path selects the
shard, so a new file does not move other files.
- Added `server/scripts/typecheck-stubs/daytona-sdk.d.ts`. Server tests
reach Daytona plugin source, and the root install does not have
`@daytonaio/sdk`.
- Changed two imports in `ui/src/lib/issue-execution-policy.ts` to use
`.js` extensions, because server tests import this file.
- Made `declarationsConfig` and `--declarations-only` skip the
`test-tree` layers, because these layers emit nothing. Other projects
read only the source layers. Added a test for this.
- Updated `doc/DEVELOPING.md`.

## Verification

Run these commands:

```sh
pnpm --filter @paperclipai/server typecheck
pnpm exec vitest run server/scripts/typecheck-layers.test.mjs
```

Results on macOS (arm64), Node 24, 16 cores. Each check ran after the
merge of paperclipai/paperclip#18738 unless the row says otherwise:

| Check | Commit | Result |
| --- | --- | --- |
| Server typecheck, `PAPERCLIP_TYPECHECK_LOW_MEMORY=1`, all 7 layers |
`6e45a08573` | Exit 0, 0 errors, 62 seconds, peak 3.52 GiB |
| `node scripts/typecheck-test-projects.mjs --low-memory` | `a3306bd13e`
| Exit 0, 0 errors, 42 seconds, peak 3.25 GiB |
| The same script with `--reuse-declarations` | `1b878aabc0` | Exit 0, 0
errors |
| `typecheck-layers.test.mjs` and `live-recovery-work.test.ts` |
`01db5634e4` | 90 passed. These include real compiler runs for a pass, a
type error, and an invalid tsconfig. |
| `tsconfig.declarations.json` after a full server typecheck |
`0fb1e4fb0a` | It references only `below`, `cycle`, and `above`. No
generated config names a `tsconfig.layers.json` file. |
| Owned runtime test in `idle-completed-history` | `e8f2f448ac` |
Passed, with the fix that master later replaced |
| `idle-incoming-wake`, `plugin-idle-manager`, and the changed
`chat-channels` test | `6e45a08573` | 30 passed |
| Runner `native-execution.test.ts` | `eab4dcc1f4` | 114 passed |
| The 19 server test files that changed since `eab4dcc1f4`, and
`typecheck-layers.test.mjs` | `259737b700` | 4,275 of 4,277 passed. The
2 failures are in `chat-channels` and are in the list of 7 below. |

The peak is the largest single process, from `/usr/bin/time -l`. Peaks
for the server typecheck were between 3.42 GiB and 3.56 GiB across 8
runs. Peaks for the test projects were 3.25 GiB and 3.37 GiB across 2
runs. I did not measure a cgroup.

**Runtime check of the fixes.** Types do not prove that a test still
works. So I ran all 309 changed server test files, 11,929 tests, before
the rebase onto paperclipai/paperclip#18737:

| Result | Tests | Detail |
| --- | --- | --- |
| Passed | 11,913 | Includes the 2 tests and the 54 `dot-runner` tests
that passed in a later run, as described below. |
| Failed | 7 | The same 7 tests also fail on the commit before the
fixes. |
| Skipped | 9 | These tests have their own skip conditions: `sentry` 5,
and 1 each in `bundled-plugin-registration`, `customer-success-cloud`,
`onepassword-connection`, and `workspace-runtime-https-live-exercise`. |

The 7 tests that fail with and without this change, on my machine:

- 3 tests in `chat-channels` and `email-channels` stop with `ENOENT` on
a `SKILL.md` file. The path is in the parent checkout, above the git
worktree that I used, so I expect that the worktree is the cause. I did
not prove this.
- `workspace-instance-cleanup` compares `/private/var/...` with
`/var/...`. This is a macOS symlink difference.
- 2 tests in `git-reproducible-managed-checkouts` get
`unknown_base_git_files` and expect `unpushed_managed_checkout`. I did
not find the cause.
- 1 more test in `chat-channels`, `materializes direct external-chat
finals once`, gets `undefined`. I did not find the cause.

CI is the check for these 7 tests. `ci / verify` passed on `eab4dcc1f4`.

Failures during this work:

- My fix to `agent-runtime-connector-access` changed an invalid
permission key in the setup, but not in the assertion. The runtime check
found this. I corrected the assertion, and the file passes.
- `heartbeat-plugin-environment` failed one wait in the full run. It
passed three times alone, so I think that load caused the failure. It
can fail again under load.
- `dot-runner` skipped all 54 tests in the full run because `cargo` was
not on my `PATH`. It then passed 54 of 54 with the toolchain on the
`PATH`.
- My first `lib` value removed the default DOM types, and the error
count went up by 375. I added the DOM libraries.
- My Daytona stub with bare `any` left 48 errors, because generic
helpers then inferred `unknown`. I added shapes that return promises.
- One fix to `agent-secrets-routes` used `class_3_static_lease`, and the
test failed. That class allows only specific paths. I reverted to
`unclassified`.
- `ci / General tests (server (8/12))` failed on `259737b700` because of
the flaky port in `idle-completed-history`. paperclipai/paperclip#18853
fixed this test on master, so this pull request keeps that fix.

**Audit of the diff.** I counted these patterns in added and removed
lines, to find fixes that only hide an error:

| Pattern | Added | Removed |
| --- | --- | --- |
| `@ts-ignore` | 0 | 0 |
| `@ts-expect-error` | 0 | 1 |
| `.skip` | 0 | 0 |
| `as any` | 9 | 9 |
| `: any` | 11 | 2 |
| `as never` | 8 | 2 |
| `as unknown as` | 35 | 4 |
| `Promise<unknown>` | 16 | 5 |
| `expect(` | 128 | 113 |

No hunk removes more `expect(` calls than it adds. Three removals of
test content were intentional, and I checked each one:

- `muse-control` removed `signalToken`. Line 1012 already asserts that
it is absent.
- `merged-pr-confirmation-sweep` removed legacy aliases. Other tests
cover them.
- `heartbeat-workspace-branch-containment` removed a `finalize` branch
that no test row can reach.

Some partial fixtures stay unchecked through `as unknown as` and
`Promise<unknown>`, mostly in `issue-agent-mutation-ownership-routes`
and `issue-comment-reopen-routes`.

**Accuracy of the check.** One program over the tree and the three
shards reported the same errors at the same positions. Memory, as the
peak of the largest process on one thread, was 3.93 GiB for one program
and 2.43 GiB for the largest shard. I measured these two values before
the fixes.

Not run or not proven:

- I did not run the full `pnpm test:run`, or a root `pnpm build`. I
expect CI to run the full suites.
- I did not run the 4 GiB container check, or the full
`scripts/typecheck-low-memory.mjs`. The peaks above come from macOS, so
they are not a Linux cgroup measurement.
- I did not run the UI typecheck after the merges.
- `workspace-runtime-https-live-exercise` is skipped, so its `cleanup`
fix did not run.

## Risks

- **A large diff in test files.** 328 files change. A pull request that
edits the same tests can get merge conflicts. New tests on master can
also add type errors before this merges. Any such error fails this check
and needs a fix here.
- **A higher cost for changes to source types.** A change to a type can
add errors in test files that the author did not touch. The author must
then fix them. This is the purpose of the check, but it is new work.
- **Changed test behavior.** Some tests now run paths that they did not
run before, such as the 9 chat wizard fixtures and the 3 span tests.
They pass here, but they can be more sensitive to timing or to the
environment.
- **The Daytona stub can go stale.** The stub is written by hand. If the
plugin uses a new SDK member, the typecheck reports an error until
someone updates the stub.
- **The release path.** `release-verify.yml` and `scripts/release.sh`
run `pnpm -r typecheck`, so they now run this check.
- **The tsconfig change.** The test transform reads
`server/src/__tests__/tsconfig.json`. The options that I changed are for
type checks, and the runs above passed.
- **A gap that remains.** Tsconfigs in `packages/paperclip-runner` and
in most sandbox provider plugins exclude `*.test.ts`. This check does
not read most of those test files, so they can still drift. That work is
separate from this pull request.

> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and
discuss it in `#dev` before opening the PR. Feature PRs that overlap
with planned core work may need to be redirected — check the roadmap
first. See `CONTRIBUTING.md`.

## Model Used

Anthropic Claude Opus 5.5 (`claude-opus-5-5`) through Claude Code, with
reasoning, tool use, code execution, and subagents. The runtime does not
show the context window size.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [ ] I have run tests locally and they pass (7 tests fail locally, with
and without this change. See Verification.)
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 15:27:38 -08:00

383 lines
15 KiB
TypeScript

import { beforeEach, describe, expect, it, vi } from "vitest";
const { mockResolveEnvironmentDriverConfigForRuntime, mockResolvePluginSandboxProviderDriverById } =
vi.hoisted(() => ({
mockResolveEnvironmentDriverConfigForRuntime: vi.fn(),
mockResolvePluginSandboxProviderDriverById: vi.fn(),
}));
vi.mock("../services/environment-config.js", () => ({
resolveEnvironmentDriverConfigForRuntime: mockResolveEnvironmentDriverConfigForRuntime,
}));
// The centralized duplex authorization gate resolves the exact lease capability
// snapshot before it calls the driver. The plugin branch of the snapshot reads
// the pinned plugin's declaration from the database. These service tests carry no
// database, so replace only the by-id declaration resolver. The test sets the
// resolved declaration per case; every other export stays real.
vi.mock("../services/plugin-environment-driver.js", async (importActual) => ({
...(await importActual<typeof import("../services/plugin-environment-driver.js")>()),
resolvePluginSandboxProviderDriverById: mockResolvePluginSandboxProviderDriverById,
}));
import type { EffectiveExecutionCapabilities } from "@paperclipai/adapter-utils/execution-target";
import { createSshCommandManagedRuntimeRunner } from "@paperclipai/adapter-utils/ssh";
import type { Environment, EnvironmentLease } from "@paperclipai/shared";
import { resolveEnvironmentExecutionTarget } from "../services/environment-execution-target.js";
import {
buildSandboxCapabilityNarrowing,
environmentRuntimeService,
} from "../services/environment-runtime.js";
import type {
EnvironmentRuntimeDriver,
EnvironmentRuntimeService,
} from "../services/environment-runtime.js";
import type {
DuplexChannelHostSession,
PluginWorkerManager,
} from "../services/plugin-worker-manager.js";
// A snapshot that grants the opt-in duplex capability, plus the rest true so the
// gate reads only the duplex flag.
const DUPLEX_GRANT: EffectiveExecutionCapabilities = {
reusableLeases: true,
nativeSyncIn: true,
nativeSyncOut: true,
persistentProcessSessions: true,
independentControlCommands: true,
incrementalSessionOutput: true,
concurrentSyncOperations: true,
duplexCommandStream: true,
runnerWebSocketIngress: true,
};
const DUPLEX_ABSENT: EffectiveExecutionCapabilities = {
...DUPLEX_GRANT,
duplexCommandStream: false,
};
function flushMicrotasks(): Promise<void> {
return new Promise((resolve) => setTimeout(resolve, 0));
}
// A fake worker manager whose one worker returns a controllable host session.
// The session records every host→worker call and lets the test settle the exit.
function makeFakeWorkerManager() {
let settleWait: (value: { exitCode: number | null }) => void = () => {};
const waitPromise = new Promise<{ exitCode: number | null }>((resolve) => {
settleWait = resolve;
});
const hostSession = {
onData: vi.fn(),
write: vi.fn(),
wait: vi.fn(() => waitPromise),
kill: vi.fn(),
close: vi.fn(async () => {}),
} satisfies DuplexChannelHostSession;
const openDuplexChannel = vi.fn(async () => hostSession);
const worker = { openDuplexChannel, supportedMethods: ["duplexChannelOpen"] };
const manager = {
getWorker: vi.fn(() => worker),
} as unknown as PluginWorkerManager;
return { manager, worker, hostSession, openDuplexChannel, settleWait };
}
const PLUGIN_LEASE: EnvironmentLease = {
id: "lease-1",
companyId: "company-1",
providerLeaseId: "provider-lease-1",
metadata: {
sandboxProviderPlugin: true,
pluginId: "test.plugin",
provider: "daytona",
},
} as unknown as EnvironmentLease;
const SANDBOX_ENVIRONMENT: Environment = {
id: "env-1",
driver: "sandbox",
} as unknown as Environment;
// A plugin driver declaration that grants the opt-in duplex capability. The
// centralized gate reads it through the by-id resolver and pairs it with the
// worker's verified `duplexChannelOpen` verb to grant the capability.
const DUPLEX_DECLARED_DRIVER = {
plugin: {},
driver: { sandboxCapabilities: { duplexCommandStream: true } },
};
// The fixed refusal the centralized gate throws when the lease does not grant the
// opt-in duplex capability.
const DUPLEX_DENIED = /does not grant the duplex command stream capability/;
beforeEach(() => {
// The default resolves a clean sandbox config and a declaration that grants the
// duplex capability, so the plugin lease reaches the worker. Each refusal test
// overrides one input to deny the capability.
mockResolveEnvironmentDriverConfigForRuntime.mockReset();
mockResolveEnvironmentDriverConfigForRuntime.mockResolvedValue({
driver: "sandbox",
config: { provider: "daytona", timeoutMs: 30_000 },
});
mockResolvePluginSandboxProviderDriverById.mockReset();
mockResolvePluginSandboxProviderDriverById.mockResolvedValue(DUPLEX_DECLARED_DRIVER);
});
describe("sandbox driver duplex channel wiring", () => {
it("reaches the worker manager route with the lease scope and delegates the channel members", async () => {
const { manager, worker, hostSession, settleWait } = makeFakeWorkerManager();
const service = environmentRuntimeService({} as never, { pluginWorkerManager: manager });
const channel = await service.openDuplexChannel({
environment: SANDBOX_ENVIRONMENT,
lease: PLUGIN_LEASE,
command: ["bridge-callback"],
});
// The driver resolves the worker by the pinned plugin id and passes the same
// lease scope the sandbox execute path uses.
expect(manager.getWorker).toHaveBeenCalledWith("test.plugin");
expect(worker.openDuplexChannel).toHaveBeenCalledWith({
driverKey: "daytona",
companyId: "company-1",
environmentId: "env-1",
providerLeaseId: "provider-lease-1",
command: ["bridge-callback"],
});
// write / stop / close map to write / kill / close on the host session.
const inputBytes = new TextEncoder().encode("input-bytes");
channel.write(inputBytes);
expect(hostSession.write).toHaveBeenCalledWith(inputBytes);
channel.stop();
expect(hostSession.kill).toHaveBeenCalledTimes(1);
await channel.close();
expect(hostSession.close).toHaveBeenCalledTimes(1);
// onData maps one to one.
const dataListener = vi.fn();
channel.onData(dataListener);
expect(hostSession.onData).toHaveBeenCalledWith(dataListener);
// onExit bridges the host session's one-time wait() to the exit listener.
const exitListener = vi.fn();
channel.onExit(exitListener);
expect(exitListener).not.toHaveBeenCalled();
settleWait({ exitCode: 7 });
await flushMicrotasks();
expect(exitListener).toHaveBeenCalledWith({ exitCode: 7 });
});
it("refuses a lease that is not a plugin-backed sandbox lease before it reaches the worker", async () => {
const { manager, worker } = makeFakeWorkerManager();
const service = environmentRuntimeService({} as never, { pluginWorkerManager: manager });
const nonPluginLease = {
id: "lease-2",
companyId: "company-1",
providerLeaseId: "provider-lease-2",
metadata: { pluginId: "test.plugin", provider: "daytona" },
} as unknown as EnvironmentLease;
// The lease is not a plugin-backed sandbox lease, so the effective snapshot
// never grants the opt-in duplex capability. The centralized gate refuses the
// open before the driver, so the worker `duplexChannelOpen` RPC never runs.
await expect(
service.openDuplexChannel({
environment: SANDBOX_ENVIRONMENT,
lease: nonPluginLease,
command: ["bridge-callback"],
}),
).rejects.toThrow(DUPLEX_DENIED);
expect(worker.openDuplexChannel).not.toHaveBeenCalled();
});
});
// Direct regressions for the centralized authorization gate on
// EnvironmentRuntimeService.openDuplexChannel. The gate resolves the exact lease
// capability snapshot and refuses unless it grants the opt-in duplex capability.
// Every refusal must happen before the driver, so the worker `duplexChannelOpen`
// RPC never runs.
describe("EnvironmentRuntimeService.openDuplexChannel capability gate", () => {
it("refuses a lease whose provider does not declare the duplex capability", async () => {
const { manager, worker } = makeFakeWorkerManager();
// The worker verifies the duplex verb, but the declaration omits the opt-in
// capability. An opt-in capability needs an explicit declaration, so the
// effective snapshot denies it.
mockResolvePluginSandboxProviderDriverById.mockResolvedValue({ plugin: {}, driver: {} });
const service = environmentRuntimeService({} as never, { pluginWorkerManager: manager });
await expect(
service.openDuplexChannel({
environment: SANDBOX_ENVIRONMENT,
lease: PLUGIN_LEASE,
command: ["bridge-callback"],
}),
).rejects.toThrow(DUPLEX_DENIED);
expect(worker.openDuplexChannel).not.toHaveBeenCalled();
});
it("refuses a lease whose worker does not verify the duplex verb", async () => {
const { manager, worker } = makeFakeWorkerManager();
// The declaration grants the capability, but the worker does not advertise
// the `duplexChannelOpen` verb, so the runtime never verified it. A
// declaration never grants an unverified capability.
worker.supportedMethods = [];
const service = environmentRuntimeService({} as never, { pluginWorkerManager: manager });
await expect(
service.openDuplexChannel({
environment: SANDBOX_ENVIRONMENT,
lease: PLUGIN_LEASE,
command: ["bridge-callback"],
}),
).rejects.toThrow(DUPLEX_DENIED);
expect(worker.openDuplexChannel).not.toHaveBeenCalled();
});
it("refuses a lease narrowed away from the duplex capability", async () => {
// A fake driver returns a snapshot that grants every capability except the
// duplex one, which models a lease narrowed away from it. The gate keys on
// the exact duplex flag, so it refuses even though the other capabilities are
// granted, and never calls the driver open.
const openDuplexChannel = vi.fn();
const narrowedDriver = {
driver: "sandbox",
acquireRunLease: vi.fn(),
releaseRunLease: vi.fn(),
resolveCapabilities: vi.fn(async () => ({ ...DUPLEX_ABSENT })),
openDuplexChannel,
} as unknown as EnvironmentRuntimeDriver;
const service = environmentRuntimeService({} as never, { drivers: [narrowedDriver] });
await expect(
service.openDuplexChannel({
environment: SANDBOX_ENVIRONMENT,
lease: { ...PLUGIN_LEASE, metadata: { ...PLUGIN_LEASE.metadata, driver: "sandbox" } },
command: ["bridge-callback"],
}),
).rejects.toThrow(DUPLEX_DENIED);
expect(openDuplexChannel).not.toHaveBeenCalled();
});
it("refuses a lease whose provider config fails to resolve", async () => {
const { manager, worker } = makeFakeWorkerManager();
// The declaration grants the capability and the worker verifies the verb, but
// the provider config cannot be resolved. An untrusted provider fails closed,
// so the config-resolution failure narrows the duplex capability away.
mockResolveEnvironmentDriverConfigForRuntime.mockRejectedValue(new Error("config unresolved"));
const service = environmentRuntimeService({} as never, { pluginWorkerManager: manager });
await expect(
service.openDuplexChannel({
environment: SANDBOX_ENVIRONMENT,
lease: PLUGIN_LEASE,
command: ["bridge-callback"],
}),
).rejects.toThrow(DUPLEX_DENIED);
expect(worker.openDuplexChannel).not.toHaveBeenCalled();
});
it("narrows the duplex capability away when the provider config resolution fails", () => {
// Unit cover for the narrowing rule the config-failure case relies on: a
// failed config resolution fails closed on the opt-in duplex capability.
const narrowing = buildSandboxCapabilityNarrowing({
leasePolicy: "reuse_by_environment",
leaseMetadata: {},
configResolutionFailed: true,
});
expect(narrowing.duplexCommandStream).toBe(false);
const granted = buildSandboxCapabilityNarrowing({
leasePolicy: "reuse_by_environment",
leaseMetadata: {},
configResolutionFailed: false,
});
expect(granted.duplexCommandStream).toBeUndefined();
});
});
// Build a sandbox execution target with a fixed capability snapshot and a fake
// environment runtime whose openDuplexChannel is a spy. The helper returns the
// runner and the spy so a test reads the capability-gated member.
async function buildSandboxRunner(input: {
snapshot: EffectiveExecutionCapabilities | null;
}) {
mockResolveEnvironmentDriverConfigForRuntime.mockResolvedValue({
driver: "sandbox",
config: { provider: "daytona", timeoutMs: 30_000 },
});
const openDuplexChannel = vi.fn(async () => ({
write: vi.fn(),
onData: vi.fn(),
onExit: vi.fn(),
stop: vi.fn(),
close: vi.fn(async () => {}),
}));
const environmentRuntime = {
execute: vi.fn().mockResolvedValue({
exitCode: 0,
signal: null,
timedOut: false,
stdout: "ok",
stderr: "",
metadata: {},
}),
supportsSync: () => false,
syncIn: vi.fn(),
syncOut: vi.fn(),
openDuplexChannel,
resolveCapabilities: vi.fn(async () =>
input.snapshot ? Object.freeze({ ...input.snapshot }) : null,
),
} as unknown as EnvironmentRuntimeService;
const target = await resolveEnvironmentExecutionTarget({
db: {} as never,
companyId: "company-1",
adapterType: "codex_local",
environment: { id: "env-1", driver: "sandbox", config: { provider: "daytona" } },
leaseId: "lease-1",
leaseMetadata: { remoteCwd: "/work" },
lease: { id: "lease-1", leasePolicy: "reuse_by_environment" } as never,
environmentRuntime,
});
if (!target || target.kind !== "remote" || target.transport !== "sandbox") {
throw new Error("expected a sandbox execution target");
}
return { runner: target.runner, openDuplexChannel };
}
describe("inline sandbox runner duplex capability gate", () => {
it("exposes openDuplexChannel that delegates to the runtime when the capability is granted", async () => {
const { runner, openDuplexChannel } = await buildSandboxRunner({ snapshot: DUPLEX_GRANT });
expect(runner?.openDuplexChannel).toBeDefined();
await runner!.openDuplexChannel!({ command: ["bridge-callback"] });
expect(openDuplexChannel).toHaveBeenCalledWith({
environment: expect.objectContaining({ id: "env-1" }),
lease: expect.objectContaining({ id: "lease-1" }),
command: ["bridge-callback"],
});
});
it("omits openDuplexChannel when the capability is absent", async () => {
const { runner } = await buildSandboxRunner({ snapshot: DUPLEX_ABSENT });
expect(runner?.openDuplexChannel).toBeUndefined();
});
it("omits openDuplexChannel when the capability snapshot is null", async () => {
const { runner } = await buildSandboxRunner({ snapshot: null });
expect(runner?.openDuplexChannel).toBeUndefined();
});
});
describe("ssh runner factory", () => {
it("omits openDuplexChannel", () => {
const runner = createSshCommandManagedRuntimeRunner({
spec: { remoteCwd: "/work" } as never,
});
expect(runner.openDuplexChannel).toBeUndefined();
});
});