START SHA 39c49baf05620e1c1c0e1a4af251f301a51944c3 COMMAND vp test run apps/server/src/orchestration-v2/ThreadLaunchService.test.ts -t 'holds\ a\ message\ queued\ during\ setup\ that\ arrives\ after\ the\ setup\ .*' UTC 2026-10-27T14:26:17.388036+00:00 HOST fs-33 Linux; root /home/ubuntu/wt/pr-17885-evidence-parent Overlay: HEAD test file copied from c740ee52fabfabea61f16a43a1591c5777d54eca as uncommitted TEST-ONLY overlay; production unchanged Test SHA256 ae215f31df993e29c3a31678324da8097b11e7fa28d37e7a7b2946a68f24c41d apps/server/src/orchestration-v2/ThreadLaunchService.test.ts note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead. RUN v5.0.5 /home/ubuntu/wt/pr-17885-evidence-parent stdout | src/orchestration-v2/ThreadLaunchService.test.ts > holds a message queued during setup that arrives after the setup failed [14:27:26.897] ERROR (#1): Error [AssertionError]: expected undefined to be true at /home/ubuntu/wt/pr-17885-evidence-parent/apps/server/src/orchestration-v2/ThreadLaunchService.test.ts:1333:14 { actual: undefined, expected: true, showDiff: true, operator: 'strictEqual', [cause]: undefined } stdout | src/orchestration-v2/ThreadLaunchService.test.ts > holds a message queued during setup that arrives after the setup interrupted [14:27:27.344] ERROR (#6439): Error [AssertionError]: expected undefined to be true at /home/ubuntu/wt/pr-17885-evidence-parent/apps/server/src/orchestration-v2/ThreadLaunchService.test.ts:1333:14 { actual: undefined, expected: true, showDiff: true, operator: 'strictEqual', [cause]: undefined } ❯ |t3| src/orchestration-v2/ThreadLaunchService.test.ts (41 tests | 2 failed | 39 skipped) 1423ms × holds a message queued during setup that arrives after the setup failed 974ms × holds a message queued during setup that arrives after the setup interrupted 445ms ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯ FAIL |t3| src/orchestration-v2/ThreadLaunchService.test.ts > holds a message queued during setup that arrives after the setup failed FAIL |t3| src/orchestration-v2/ThreadLaunchService.test.ts > holds a message queued during setup that arrives after the setup interrupted AssertionError: expected undefined to be true - Expected: true + Received: undefined ❯ src/orchestration-v2/ThreadLaunchService.test.ts:1333:14 1331| const wake = (yield* threads.getThreadProjection(launched.thread… 1332| assert.equal(wake.status, "queued"); 1333| assert.isTrue(wake.queueHeld); | ^ 1334| 1335| // Nor does the next one, though the run that message started is… ❯ ~effect/Effect/successCont ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:1422:28 ❯ ~effect/Effect/evaluate ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/core.ts:585:30 ❯ FiberImpl.runLoop ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:654:41 ❯ FiberImpl.evaluate ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:595:23 ❯ FiberImpl.evaluate ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:589:27 ❯ Array. ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:1025:13 ❯ MixedSchedulerDispatcher.runTasks ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/Scheduler.ts:254:17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯ Test Files 1 failed (1) Tests 2 failed | 39 skipped (41) Start at 14:26:32 Duration 54.53s (transform 79%, setup 11%, import 7%, tests 3%) EXIT 1 END SHA 39c49baf05620e1c1c0e1a4af251f301a51944c3 COMMAND vp test run apps/server/src/orchestration-v2/ThreadLaunchService.test.ts -t 'holds\ a\ message\ queued\ during\ setup\ that\ arrives\ after\ the\ setup\ .*' START SHA 39c49baf05620e1c1c0e1a4af251f301a51944c3 COMMAND vp test run apps/server/src/orchestration-v2/runtimeLayer.test.ts -t 'keeps\ queued\ user\ selections\ and\ pauses\ only\ the\ limited\ provider' UTC 2026-10-27T14:27:28.243711+00:00 HOST fs-33 Linux; root /home/ubuntu/wt/pr-17885-evidence-parent Overlay: HEAD test file copied from c740ee52fabfabea61f16a43a1591c5777d54eca as uncommitted TEST-ONLY overlay; production unchanged Test SHA256 d19873121f61da367adf8571f02d52e285c9a4edef15cd8be2c71805cb684cd0 apps/server/src/orchestration-v2/runtimeLayer.test.ts note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead. RUN v5.0.5 /home/ubuntu/wt/pr-17885-evidence-parent stdout | src/orchestration-v2/runtimeLayer.test.ts > OrchestrationV2LayerLive lifecycle > keeps queued user selections and pauses only the limited provider [14:27:54.566] ERROR (#3055): Error [OrchestratorDispatchError]: Failed to dispatch orchestration command queue.resume (runtime-layer-queue-provider-limit:resume-available). at /home/ubuntu/wt/pr-17885-evidence-parent/apps/server/src/orchestration-v2/Orchestrator.ts:12021:25 at orchestrationV2.dispatch.withReceipt (/home/ubuntu/wt/pr-17885-evidence-parent/apps/server/src/orchestration-v2/Orchestrator.ts:12326:7) at orchestrationV2.dispatch.withReceipt (definition) (/home/ubuntu/wt/pr-17885-evidence-parent/apps/server/src/orchestration-v2/Orchestrator.ts:12108:44) { _tag: 'OrchestratorDispatchError', commandId: 'runtime-layer-queue-provider-limit:resume-available', commandType: 'queue.resume', [cause]: [Error: Continue the limited thread before resuming its queue.] } ❯ |t3| src/orchestration-v2/runtimeLayer.test.ts (90 tests | 1 failed | 89 skipped) 584ms ❯ OrchestrationV2LayerLive lifecycle (50) × keeps queued user selections and pauses only the limited provider 208ms ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯ FAIL |t3| src/orchestration-v2/runtimeLayer.test.ts > OrchestrationV2LayerLive lifecycle > keeps queued user selections and pauses only the limited provider OrchestratorDispatchError: Failed to dispatch orchestration command queue.resume (runtime-layer-queue-provider-limit:resume-available). ❯ src/orchestration-v2/Orchestrator.ts:12021:25 12019| ) 12020| ) { 12021| return yield* new OrchestratorDispatchError({ | ^ 12022| commandId: command.commandId, 12023| commandType: command.type, ❯ ~effect/Effect/successCont ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:1422:28 ❯ ~effect/Effect/evaluate ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/core.ts:585:30 ❯ FiberImpl.runLoop ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:654:41 ❯ FiberImpl.evaluate ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:595:23 ❯ FiberImpl.evaluate ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:589:27 ❯ Array. ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:1025:13 ❯ MixedSchedulerDispatcher.runTasks ../../node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/Scheduler.ts:254:17 Caused by: Continue the limited thread before resuming its queue. ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ Test Files 1 failed (1) Tests 1 failed | 89 skipped (90) Start at 14:27:34 Duration 20.68s (transform 54%, import 22%, setup 21%, tests 3%) EXIT 1 END SHA 39c49baf05620e1c1c0e1a4af251f301a51944c3 COMMAND vp test run apps/server/src/orchestration-v2/runtimeLayer.test.ts -t 'keeps\ queued\ user\ selections\ and\ pauses\ only\ the\ limited\ provider'