# Issue 24300 final runtime verification

Head: 4a840995dada0a22f22cb68d32b0cb666bb40ba9. Merged main: 1c10563ddb. Ubuntu Linux fs-04, native codex-cli 0.163.0. Real web client (port6307) and server through vp run dev (port14347), isolated worktree .t3 state, browser1280×800 without device emulation. Wrapper records PID before exec; only those captured PIDs were signalled. No live T3 state was written.

Final check: vp run check:changed passed format, lint, both knip checks, GraphQL, affected3package typechecks and140tests in4files. Existing lint warnings only. No tests ran during final runtime observation.

22:54:20 UTC browser New thread sent: Reply with FINAL_BASELINE. Do not use tools or change files.
22:54:24 browser displayed FINAL_BASELINE; native app-server PID3010262 was sleeping normally.
22:54:28 kill -STOP3010262; browser New thread sent: Reply with FINAL_STOP. Do not use tools or change files.

22:54:29.245 outgoing thread/start id4. At22:56:04 original PIDstillstopped; persisted runstarting. No Node watch restart or test process during observation.
22:56:29.258 persisted run run:thread:2f04b4cc-e3c4-4a3b-a6b0-f7893b86388f:ordinal:1 becamefailed. UI: Provider turn failed to start — Codex app-server did not answer thread/start within2minutes. Shared session error updated22:56:31.301. At22:56:39 original PID3010262 absent; no wrapper-recorded PID alive. No automatic replacement and no FINAL_STOP reply.
22:56:46 manual Newthread request: Reply with FINAL_RECOVERED. Do not use tools or change files. A distinct native process PID3012951 spawned; UI displayed FINAL_RECOVERED andDone by22:56:55.
22:57:02 kill -KILL3012951. Shared session projection changedtoerror22:57:02.641, before nextsend. Same existing native thread then sent: Reply with FINAL_RESUMED_AFTER_DEATH. Do not use tools or change files.

Protocol confirms FINAL_RECOVERED turn/completed22:56:50.620; persisted runcompleted22:56:50.654. Afterdeath, distinct PID3014229 handled outgoing thread/resume id2 at22:57:03.709 and turn/completed22:57:06.616; persisted ordinal2 completed22:57:06.646. UI displayed FINAL_RESUMED_AFTER_DEATH andDone. Original failedrun remainedfailed.

Result: exact-head 120-second boundedfailure, stopped-process cleanup, no automatic setupretry, successful manualreplacement, immediate transport-death retirement, and existing-threadresume recovery all observed. No serverrestart occurred during finalsequence. No changed renderpaths; visualmatrixempty. No claim that the natural hours-long backlog trigger was reproduced. Windows/macOS process cleanup notrun.