TR2 full-journal native action: Chrome startup repair — 2026-11-08

The first fresh attempt exposed a new browser-bootstrap integration defect before the TR2 route was navigated. The run driver now waits for a complete DevTools endpoint under an absolute startup deadline, with eight focused checks passing. Its prepared native bootstrap regression is blocked by the shared runtime lock and was not run. Native movement, weapon consequence and exact qualified original publication remain open. No original game started, no input or observation arm was dispatched, and this attempt was not replayed.

Evidence: scratch/runs/20261108-tr2-full-journal-native-action/.

Published closure and first fault

The tested source is published main 0ae13bf34462d2a0f6ee5f08b2e7c3158e113269. The cheap closure check verifies all 558 tracked runtime inputs byte-for-byte against queue-accounting repair 0e951a0be; all 594 runtime pins pass. The driver preflight starts neither Chrome nor an original. The pinned production module is 6cf120d0d3b3db1823a8105eb26ef52a9093a7f871c37a46117475e213fda1c0. Six bootstrap HTTP checks return the exact pinned bytes before Chrome starts. Peer WIP is excluded.

The accepted full-size 4096-record actualGuest/renderWorker pending-fence regression, queue-capacity, association, handoff, concurrent-arm and retirement controls, and nine-process fixture costs are reused from the preceding runs. There is no standalone cost or publication-acceptance rerun here.

One fresh box launches one blank Chrome. At 09:45:41.513 UTC, the driver's fixed 100 × 100 ms startup loop ends and its unconditional read of chrome-profile/DevToolsActivePort fails with ENOENT. The file was not ready at that read. Chrome's retained stderr also contains its eventual DevTools listening endpoint on port 44689; that line has no timestamp, so its exact arrival time is unknown. The driver records its first terminal failure and closes. Chrome exits normally, code 0, at 09:45:52.716 UTC.

launch.json, which is written immediately before navigation to the registered game route, is absent. There are no commands, native Graphics review, owning game WebGL/module binding, observation Join or original source dispositions. Raw, qualified and discarded counts are unobserved, with no empty-Join or zero-FPS inference. No Up, Space or Control reaches a game.

Bounded bootstrap repair

The owned chrome-ready.cjs replaces the unconditional file read in the owned browser-run.cjs. It waits for both endpoint lines, validates a numeric port in 1–65535 and a /devtools/browser/… path, and rejects a child that exits before readiness. Missing and partially written files can finish within the same absolute deadline. The deadline never resets: it is the earlier of 30 seconds from admission and the existing immutable run deadline minus its 30-second cleanup reserve. Exhaustion fails closed without retrying Chrome or navigating.

The startup allowance changes from the brittle fixed ten-second wait. The existing overall runtime cap, 12-second reviewed-scene freshness, native input holds and independent releases, sticky UNKNOWN/no replay, and all writer/ambiguity/source/canonical/display/lifetime gates are unchanged. This repair changes run-specific bootstrap inputs; no production emulator source or WASM changes, and no new production-build claim is made.

Eight focused checks pass: immediate readiness, partial-file completion, early child exit, three malformed endpoints, an earlier overall cleanup boundary and insufficient startup budget. A prepared real-browser regression would watch one deliberately delayed blank native Chrome with both the former reader and the repaired reader. It has not run: its local wine-runtime.lock waiter remained behind peer holder PID 3681498 from 09:48 until cancellation at 09:59 UTC, despite board coordination and a coordinator release request. The waiter had no child and no fixture directory; only its owned process group was terminated. The exact lock snapshot is in readiness-native-blocked.json. No peer process or file was changed. Native bootstrap validation remains open. No scene, guest state, clock, seed or configuration is forced.

The repaired driver and prepared fixture pass Node syntax checking. Finalization verifies the original driver's pinned hash, all served bootstrap responses, unique remote artifacts, focused results and shutdown records. The existing native-input chain controls also pass, including stale zero-effect refusal, owner replacement and sampler-independent release.

The repository evidence checker reports no containment, missing-file or invalid metadata findings for this run. Its seven unrelated containment errors and historical missing evidence remain in the retained global report.

Recovery and lifecycle

Git is the source archive. source-sha.txt, source-audit.json, relevant.diff, the original runtime-pins.json and small owned new-file patches reconstruct the original inputs. browser-run-before.cjs independently matches the original driver pin. repair.diff, helper/test patches and repair-runtime-pins.json identify the corrected inputs; that corrected original route was not run. Media stays at its existing paths with size/SHA-256 references in media-refs.json. Unique logs and both pinned modules are retained without a source/media archive. The run is an investigation note because TR2 has no exact candidate-corpus entry.

Fresh UUID-idempotent box bx_u2e6wnef is identified before runtime. Normal shutdown and independent 25-minute deadline watchdog delegates are observable before creation. Its initial active expiry is 10:09:48.853 UTC. The remote runtime runs under wine-runtime.lock; the prepared local native browser test requires that lock. A preliminary local lock waiter is canceled before it acquires the lock or launches anything.

Before normal stop, the controller and Chrome PIDs are absent, HTTP port 38299 and actual DevTools port 44689 are closed, the profile and writer are absent, the owned process scan is empty and all 594 pins remain unchanged. All 15 remote artifact references, 15 unique hashes, 4,375,374 bytes are retrieved and independently reread for size/SHA-256 before requesting stop.

Final box state: archived, active expiry null, stopped 09:47:05.384 UTC. Receipt stop_49dd0e6715487890 completes at 09:47:05.402 UTC, forced=false, error=null. Both lifecycle delegates exit 0; their supervisor exits with no remaining children. Disk stays above 5 GB. No old-box resume/delete, second original, public deployment or subworker occurs.

Next is the prepared native bootstrap regression once the shared lock is free, followed by a separately authorized original using the corrected bootstrap: fresh native Graphics default-OK Enter, actual owning WebGL/module identity, full-size live observer at its completed-step boundary, then separately reviewed bounded movement and documented Space/Control consequence if qualified. Final original accounting must satisfy raw = qualified + discarded with explicit dispositions. Full27, parity, audio, game FPS and simulation FPS remain open.