real dev verification, 2026-10-28 UTC
main: github/main 40d335a7ba
pr: 03afbb12bb539e4f06c44da433abe9c4bb4b7854
client: repo Playwright, /usr/bin/google-chrome, 1440x960 dark
provider: Codex gpt-6.1-sol, local proxy
data: project added in UI at /home/user/recovery-proof; no mocks/fixtures/demo data

completed identical git status/rev-parse turn on main and PR: RECOVERY-READY
waited >30 seconds connected before stopping each backend
actual browser descriptor request intervals during outage (seconds):
main: 3.354, 7.413, 11.428
pr: 3.074, 2.588, 4.757, 3.107, 3.767, 4.626, 3.066, 3.060, 3.104, 4.828

PR backend stop: 10:22:37.593 UTC
backend process restart requested: 10:23:16.319 UTC
HTTP listening: 10:23:18.544 UTC
real browser websocket reconnected automatically: 10:23:20.176 UTC
existing thread follow-up completed: RECOVERY-CONTINUED, earlier marker retained

second check: SIGKILL backend while real Codex timeout 60 sleep 45 command was running
10:24:54.928 HTTP listening
10:24:54.983 V2 recovery: terminalizedRuns=1 stoppedSessions=1
10:24:55.142 stopping agents left by previous server
old Codex/tool PIDs gone
UI showed T3 Code restarted and resumed this turn
follow-up real Codex git status/rev-parse: RECOVERY-AFTER-CRASH; working tree clean; RECOVERY-READY retained

blacksmith: vp test run apps/server/src/serverRuntimeStartup.test.ts packages/client-runtime/src/connection/supervisor.test.ts
2 files, 54 tests passed

not established by this run: readiness during prolonged recovery; live relay/Cloudflare tunnel; update-trial launcher commit/rollback; retry window expiry after 120s; native desktop/mobile; other providers
recovery finished in 55ms on crash restart, too quickly to claim prolonged recovery coverage