Original Uplink: whole-twelve restore prepared, Chrome startup blocked

Run: scratch/runs/20261112-halflife-cleared-bay-onward-1655/.

The attempt to continue beyond the cleared small crate stopped before CDP connected or the guest launched. Chrome did not publish DevToolsActivePort within the existing 600 × 100 ms startup wait. The caller then recorded ENOENT at browser.cjs:93 and closed admission. No fresh VFS verification, native Load, movement, corridor, encounter or successor save is claimed. The startup cause remains unknown; this is not evidence of a game or renderer defect.

The 1635 crate-destruction checkpoint remains unchanged and is still the next starting point. Its fresh-browser restoration and onward route remain untested by this attempt.

Checkpoint and prelaunch verification

Independent verification checked the authoritative export at 20261112-halflife-crowbar-obstruction-1635/recovered/webgl/earned-native-save-d46-export.json.gz: 649713 bytes, SHA256 f523dfeaf57ef0f4d4c470965d4f036b3e67affde4498f203f55650db204d809. The exact twelve paths, strict base64, every decoded size/SHA and the 2006166-byte total match the predecessor manifest. All twelve ordinary required mounts were prepared together; no auxiliary file was substituted. half-life-004.sav remains the native UPLINK01:48 checkpoint.

checkpoint-independent-verification.json, restore-mounts.json and restored-save/ retain the checks and prepared bytes. Postflight rechecks the unchanged original export and every local mount. These are source and staging checks, not a fresh guest VFS or successful Load claim.

Local exact staged-import positive/missing-dependency controls passed, with 65 original media files /93140232 bytes. Binding negatives passed16 cases, passive readiness negatives5, native save collector/export controls passed, and the emitted command body passed102 planned input forms. The tested browser, passive postLoadReady, strict22 binding, independent native release, save reader, delivery and envelope helpers were byte-identical to1635. Earlier production transition/envelope results were reused by hash, not represented as new runs.

Remote verification passed all589 frozen files, then the import-only gate passed after hashes and before browser output. All185 HTTP pins passed before Chrome allocation. Frozen module SHA is 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17; no actual guest/renderer module or SoftwareGL context was observed this time.

Terminal evidence and limits

recovered/webgl/terminal-error.json.gz records the missing endpoint file and noLaterProtocol:true. Chrome stdout and stderr are both empty and share one hash-verified recovered file. No browser exit JSON was produced. There are zero native commands and zero captures. Ordinary quit could not be sent without a CDP connection. The cancellation helper was refused by sticky caller failure before dispatch; that refusal is retained in the actual tool output. No launch or input was replayed.

startup-operation-final.json is the authoritative GET for the original API operation6905: exited1, no signal/OOM/truncation. The error names the browser terminal file. Kernel custody records supervisor SIGTERM cancellation and subsequent cleanup, with all30 owned tasks reaped, no remaining/unreaped tasks, and closed command-log EOF. The native outer parent actually waited1 and joined both output EOFs. This was failure cleanup, not ordinary Chrome shutdown.

retrieval-verified.json and postflight.json verify23 recovered artifact references, gzip roundtrips and hashes. The actual local starter tool wait returned0; provision, manager and watchdog actual parent waits all returned0 with both EOFs. The predecessor's missing joins are not inherited as new proof or new failures. Minimum sampled local free space was1634709504 bytes, above the1.5GB floor. No RAM gate was used.

Source is Git 241ff557017eaf834e270357a03f2377107e6945 plus relevant-source.patch, relevant-untracked-source.patch, fixture-source.patch, new-helper-patches.patch and final-helper-patches.patch. All479 shared production/dependency pins and all589 frozen file bytes still matched after recovery. Git remains the source archive; there is no source/media archive, production edit, new build, forced export, guest write, parity/FPS/audio/full27 claim, worker launch or deployment.

Box shutdown and next step

An observable independent two-hour watchdog was armed before allocation. Unique evidence was retrieved and hash-verified before delegated normal stop. Box bx_bk334rh2 is archived, stopped 2026-11-12T16:55:53.585Z, expiry null (initial18:52:13.772Z). Receipt stop_39c2c5cd15008981 completed16:55:53.618Z, forcedfalse, errornull. No box was deleted, resumed or left billing idle.

Next: establish why this exact Chrome/custody launch failed to publish its endpoint before allocating another original-game attempt. Then verify the whole12 fresh VFS, native01:48 Load/crowbar/SoftwareGL/fresh movement and inspect the tall shelving's side clearance and native crouch/jump route toward the corridor. Historical route notes remain guidance only.