TR2 native jump continuation — physical helper integration repair, 2026-11-08

The fresh continuation stopped before Chrome or the original game launched. My run preparation compared relative manifest paths with an absolute predecessor directory, so none of the 29 runtime helper upload targets moved into the new run directory. The new custodian consumed its one launch request and then failed to find launch-locked.py. This is a new run-preparation defect, not a native game or Alt failure. No request was replayed, second box created, or original launched. Native jump, landing, turn and onward gameplay remain unvalidated.

The substantive repair normalizes helper paths relative to the repository root and binds actual physical bytes, required entry points, upload destinations and literal CommonJS dependencies before allocation and provisioning. Ten repository tool tests and twelve focused run integration tests pass, including execution of the actual provision planner with a mock transport. The broken plan is refused before any upload; the corrected plan uploads the new helper paths and exact bytes. This satisfies the tested new integration repair alternative, with no gameplay claim.

Evidence and small recovery patches: scratch/runs/20261108-tr2-native-jump/.

Failure and causal repair

runtime-pins.json preserves the actual failed 613-pin plan. The inherited manifest was hash-verified before modification. The initial check verified those pins and syntax/hashes of 40 physical local helper files, but did not prove those local files were the targets in the provision plan. Its reported preallocation pass therefore did not establish physical upload closure. physical-upload-baseline-failure.json reproduces the stale-target failure; retrieved/custody.stdout retains the actual missing-launcher traceback. The earlier diagnostic missing-runtime-log failure is also retained.

tools/runtime_helper_closure.py repairs the path normalization and provides a shared, side-effect-free gate. It refuses stale predecessor targets, missing required helpers, differing read/upload paths, hash mismatches, duplicate targets, repository escapes and missing literal helper dependencies. In particular, the actual ordinary-keys.cjs and bound-input.cjs dependency on tools/native-key-controls.cjs must be provisioned. Conditional fixture dependencies require an explicitly inactive environment; the owned launcher now explicitly disables LOCAL_PRODUCTION_FIXTURE for this original route. Active or unspecified conditional dependencies are refused.

The owned helper_closure.py loads that single repository implementation. The owned setup.py uses this generic relocation; verify-prelaunch.py, remote.py allocation and provision.py enforce the physical binding. Preparation also refuses to rewrite an allocated run. repair-successor.py constructs a recovery manifest without overwriting the failed plan, allocation identity or consumed launch request. successor-runtime-pins.json and successor-physical-upload-closure.json verify 613 pins and all 29 required runtime helpers, including the shared native key control. These are recovery inputs for a separately assigned fresh continuation, not permission to replay this closed lifecycle. The new repository tool and its local loader are separately hash-recorded local preflight dependencies; it does not change the native runtime or add keys.

Validation: python3 scratch/runs/20261108-tr2-native-jump/helper_closure_test.py passes 12 tests. The tests reproduce the exact absolute/relative prefix mistake, exercise the real provision planner in both refusal and corrected-transfer cases, and cover each boundary above. final-check.py independently verifies the repaired actual plan, accepted references, retrieved evidence, shutdown and syntax. The final audit passes. The new generic tool also passes python3 tools/runtime_helper_closure_test.py (10 tests). The required new locked build passes, retaining the native module hash below. The accepted 11 native key integration tests and renderer/guard controls were reused without reruns; the new tests concern changed preparation/provisioning code only.

Preserved native authority

The accepted 226 control references, 23 existing media references, 49 repair artifacts, 29 guards, 16 negatives, native build and predecessor pixel authority remain unchanged. Their hashes were checked rather than their tests rerun. The repaired shared key control remains the published 433e926a7 dependency. The native module pin remains d8facd0658b7f158c6e60bef2de0936471f438f8bf41e9240fd75635f1d319dc.

No game runtime existed here, so there are no new actual parsed JavaScript, CPU/owning-WebGL2, publication, screenshot or input observations. The exact five parsed-source pins and retained-source qualification, cache token, scene, owner and source guards remain in the recovery plan. The retained-native predecessor supplies the accepted pixel authority; the alley predecessor supplies its final 299 raw = 41 qualified retained + 258 discarded accounting. No new rows or FPS claim are inferred from those observations. Alt remains a standalone admitted key; no Alt+Up combination or mapping expansion was introduced.

Lifecycle and recovery

One UUID-idempotent box was created after the initial checks with 7.48 GB free disk. The observable independent detached 25-minute watchdog was armed first. Overall, browser and cleanup deadlines were immutable. The remote custodian acquired its own lock and subreaper status before provisioning. Its traceback then exited before browser creation; the lock was released by process exit. No local heavy runtime or local runtime lock was used.

retrieved/no-launch-drain.json verifies the recorded custodian and bootstrap PID/start identities absent, no owned process or file descriptor left, the remote lock free, and no browser/controller endpoint, port, profile, writer or held input created. All 11 unique artifact references / 343,234 bytes were retrieved and independently hash-reread before requesting normal stop. Both normal/watchdog lifecycle children exited zero, the supervisor ended empty and all three local lifecycle PIDs were absent. The first remote diagnostic failure is preserved rather than retried.

Coverage remains the accepted 50 ms descendant census plus subreaper adoption/reaping, not exhaustive kernel task history. The local lifecycle armed records retain PID/parent/session and supervised exit, but did not record local start ticks before exit. Synchronous diagnostics retain parent-awaited command exits. This run makes no stronger custody claim.

Box bx_bk6788ta is archived, expiry null. Normal stop stop_14277e267bd9eb1e completed 14:46:46.021 UTC, forced=false, error=null. No task box remains running.

source-head.txt, relevant.diff, exact source/blob pins, small owned-*.patch files and existing media path/hash references provide recovery. Git remains the source archive. No source/media archive, peer WIP, public deployment, old-box resume/delete or subworker was used.

Next: a separately assigned fresh continuation should consume the corrected physical upload gate, review current UI before Graphics Enter, verify actual five parsed sources plus CPU/owning-WebGL2 module, then use independently released Up to the reviewed slope and a standalone Alt hold of at most 1500 ms. Personally review landing and any separately chosen turn. Full27, parity, audio and FPS remain open.