PR #24092 real Linux dev environment verification, 2026-10-28
main: github/main 9ebca5f71c
PR head: 88dcc0c4d2524f67572a7058f4c86bd03ba32162

Commands:
git worktree add ../main github/main; (cd ../main && vp i)
setsid nohup timeout 6600 vp run dev > /tmp/main-dev.log 2>&1 &
timeout 180 node /tmp/pr24092/race.mjs /home/user/main main
stop captured main dev process group
git switch --detach 88dcc0c4d2524f67572a7058f4c86bd03ba32162; vp i
setsid nohup timeout 6600 vp run dev --home-dir /home/user/t3code/.t3 > /tmp/dev.log 2>&1 &
Playwright + /usr/bin/google-chrome: add /tmp/pr24092/workspace real git repo, choose Codex GPT-6.1-Sol, submit pwd/git status turn, observe final reply.
timeout 180 node /tmp/pr24092/race.mjs /home/user/t3code pr
stop captured PR dev process group
setsid nohup timeout 1200 node /tmp/pr24092/server-race.mjs > /tmp/pr24092/server-transcript.txt 2>&1 &
Playwright: pair with actual release server launched by exact PR launcher, create project and thread through UI, run Codex GPT-6.1-Sol before and after A resumes.
timeout 180 node /tmp/pr24092/neighbors.mjs

Method: unmodified launcher source copied into npm package layout with version 0.1.3. Official release archive and original SHA256SUMS mirrored byte-for-byte on localhost. Real executable, bundled client, dependencies and Codex provider; no mock executable, provider, response, fixture or filesystem hook. Node inspector pauses A immediately after its failed rename and missing-marker read; B independently downloads and publishes a real runtime. Then A resumes. This controls scheduling only.


MAIN: original race
main: A paused at publication boundary line 115; B installs the official checksum-verified v0.1.3 release
B exit=0 t3 v0.1.3 
B executable inode=2619579
after A's next filesystem operation: peer executable ENOENT exit=null
peer executable preserved=false
A: t3 v0.1.3
A final stderr=
final peer inode preserved=false


PR: same race
pr: A paused at publication boundary line 117; B installs the official checksum-verified v0.1.3 release
B exit=0 t3 v0.1.3 
B executable inode=2726676
after A's next filesystem operation: peer executable t3 v0.1.3 exit=0
peer executable preserved=true
A: t3 v0.1.3
A final stderr=
final peer inode preserved=true


PR: running peer server
A paused after failed rename and missing-marker check, before lock acquisition.
B launcher PID=26261; official v0.1.3 archive, original SHA256SUMS, localhost byte-for-byte release mirror.
Before A resumes: B executable inode=2855233; health=200
A: t3 v0.1.3
A exit=0
After A resumes: same B executable inode=true
Direct executable probe: t3 v0.1.3 exit=0
After A resumes: B health=200


PR: nearby behaviors
Held recovery lock: {"code":1,"out":"","err":"t3: another t3 is installing 0.1.3. If none is running, delete /tmp/pr24092/locked-home/runtime/versions/0.1.3.lock and try again."}
Incomplete directory preserved=true
After manual lock removal: {"code":0,"out":"t3 v0.1.3","err":""}
Automatic stale recovery complete=true; only version directory=["0.1.3"]
Cached reuse with unreachable release host: {"code":0,"out":"t3 v0.1.3","err":""}
Cached executable inode unchanged=true


Real provider results
PR dev app: runtime verification ready.
Peer server before resume: concurrent runtime server ready.
Peer server after resume: peer runtime survived concurrent recovery.
All requested pwd/git status tool calls ran in /tmp/pr24092/workspace; no workspace file changes.

Checks
Blacksmith: vp test run scripts/build-npm-launcher.test.ts passed (1 test).
Blacksmith: vp run check:changed passed format, lint, both knip checks, scripts typecheck and launcher test. Fetched shallow base/head history to repair initial missing merge-base setup.
Existing GitHub checks: 28 successful, 0 pending, 0 failing at inspected head.

Unverified
macOS/Windows, native desktop/iOS/Android, mixed standalone/server/SSH installer races, abrupt termination during lock ownership. The documented fail-fast contention/manual stale-lock removal behavior remains.