Target: PR 20059, tris203/t3code, fix/ssh-archive-runner-lock-flake. Scope: only packages/ssh/src/tunnel.test.ts edited. Before: 34 tests passed in one file (21.61s). After: 34 tests passed in one file (21.36s). Focused red against origin/main production: 1 failed, 33 skipped; expected one extraction, observed two. Failure completed in 1.04s, without timeout. Focused green with current production: 1 passed, 33 skipped. SSH package typecheck, test-file lint, formatting, and git diff --check passed. Two lock-implementation text assertions removed. Existing concurrent install test uses stdin/stderr synchronization to force actual lock contention; dead-owner and empty-lock recovery coverage retained. No mixed legacy lock-format compatibility tests added. Production restored byte-for-byte and verified equal to HEAD. Production SHA256: 2115b0780738a359c9f654feb6c4edff3ddfbad5d8d195f35f2dde0905a1ce5c --- Before: origin/main production with revised behavior test --- 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.1 stdout | packages/ssh/src/tunnel.test.ts > archive runner script > installs once when several launches race, and reclaims stale locks [03:02:32.971] ERROR (#1): Error [AssertionError]: expected '\n\n' to equal '\n' at /packages/ssh/src/tunnel.test.ts:1177:16 { actual: '\n\n', expected: '\n', showDiff: true, operator: 'strictEqual', [cause]: undefined } ❯ packages/ssh/src/tunnel.test.ts (34 tests | 1 failed | 33 skipped) 165ms ❯ archive runner script (1) × installs once when several launches race, and reclaims stale locks 163ms ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯ FAIL packages/ssh/src/tunnel.test.ts > archive runner script > installs once when several launches race, and reclaims stale locks AssertionError: expected '\n\n' to equal '\n' - Expected + Received + ❯ packages/ssh/src/tunnel.test.ts:1177:16 1175| concurrency: "unbounded", 1176| }); 1177| assert.equal(yield* fs.readFileString(`${bin}/installs`), "\n"… | ^ 1178| for (const result of results) { 1179| assert.equal(result.exitCode, 0, result.stderr); ❯ IteratorImpl.~effect/Effect/successCont node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:1422:28 ❯ ExitPrimitive.~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 ❯ node_modules/.pnpm/effect@4.0.5/node_modules/effect/src/internal/effect.ts:1159:17 ❯ node_modules/.pnpm/@effect+platform-node-shared@4.0.5_bufferutil@4.1.0_effect@4.0.5_utf-8-validate@6.0.6/node_modules/@effect/platform-node-shared/src/NodeFileSystem.ts:538:11 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ Test Files 1 failed (1) Tests 1 failed | 33 skipped (34) Start at 03:02:31 Duration 1.04s (transform 37%, import 32%, tests 19%, setup 10%, worker 1%) --- After: current production, full focused tunnel suite --- 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.1 Test Files 1 passed (1) Tests 34 passed (34) Start at 03:02:45 Duration 21.36s (tests 97%, transform 1%, import 1%, setup 1%)