TR2 timing margin and terminal admission — 2026-11-10
The title driver now requests separate navigation holds of at most 300 ms, refuses measured release completion above 400 ms, requires a current reviewed visible enemy before the sole linked shot, and checks the game canvas for an unchanged result. Its first failure latches before owning kernel cancellation; later Evaluate, key release, capture, and Browser.close requests are refused. The accepted native key fixture is reused by verified reference, never rerun. The generated caller identifies its actual selected CPU instead of hardcoding the historical d8fac module. Shared runtime, renderer and startup providers are unchanged by this work.
Implementation: tools/tr2-visible-target-margin.cjs. Controls:
node tools/tr2-visible-target-margin.test.cjs scratch/runs/20261110-tr2-visible-target-margin-0415/browser-run.cjs.
The complete generated execute function covers changed images, unchanged
images, a 401 ms release, and zero-dispatch stale admission. Its generated
failure/send functions prove sticky cancellation and zero later protocol.
The actual production Worker instantiation assignment installs the current
compiled module; the serialized TR2 observer arms and restores that instance.
The existing exact native shot-call/damage/return suite passes 20 controls
against current CPU 4f2c69a1528e01a9ab5127201d5e8a222da2a35236377a1351f444f55fa5a7d9.
These authored offline states establish no original hit. The title suite passes
14 controls; the locked full build passes. No second native fixture or browser
is used by those controls.
One original, concrete freshness blocker
Evidence: scratch/runs/20261110-tr2-visible-target-margin-0415/.
The retained 2142 route images were recovered by their recorded gzip/SHA/size
and individually inspected at world-first, pre-draw, pistols-drawn, nav01,
nav04 and nav07. They show the same rising alley without a visible enemy.
The chosen distinct route was a left turn first, followed by separately
reviewed navigation, rather than repeating five forward holds and right turns.
The one original used 660 pinned inputs, both current CPU modules, unchanged original media, and a pre-Chrome driver preflight. Every 703 staged input/chunk upload joined before remote assembly and the full SHA/size barrier. Original startup reached the current Graphics sheet. The initial screenshot and a fresh screenshot were each personally reviewed: Hardware 3D, full screen, 640×480 High Color. Ordinary Enter100 accepted those existing settings.
The resulting personally reviewed screenshot is
review/webgl/world-first.png, captured 04:22:56.690Z, completed
04:22:57.686Z, SHA256
bef2a2d1e3ea6a77c1b9c9280d051a434b928594a7aa9b7f163198e0823a5aff.
It shows upright Lara facing the rising alley, brick on the left and a green
wall on the right, with no visible enemy. The owning WebGL2 endpoint and
executing CPU 4f2c69a1 are recorded in its bound identity. No physical-GPU,
frame-rate or parity claim follows.
The next command requested ArrowLeft300. At 04:23:14.806Z, the unchanged 12-second freshness fence refused the image at age 18,116 ms, before dispatch. There is no ArrowLeft admission/hold receipt or later screenshot. The request is not evidence of movement, native polling, or a measured navigation hold. This is a distinct review-to-admission blocker, not a repeated empty-route attempt. No Space, Control, shot observer, ammo change, target identity or target-health observation was produced. The encounter goal remains open.
First failure immediately latched owning cancellation. There was zero later guest protocol, input, capture, retry, quit, extension or second native run. The outer parent actually waited the supervisor (status 1 following its cancellation exception), with separate stdout/stderr EOF records. Kernel custody records 202 owned identities and 202 actual terminal reaps, complete=true, with no remaining/unreaped/unresolved entries. Chrome was cancelled; a normal Browser.close or Chrome exit-zero result is not claimed. CLONE_UNTRACED coverage remains unaudited.
Verified retrieval and delegated stop
The finalized remote inventory retained 76 unique artifacts, 858,291 bytes. All SHA/size pairs were independently reread; 13 gzip streams passed full decompression/CRC and both unique PNGs passed full decode/CRC before the sole normal-stop request. The third screenshot is byte-identical to startup and deduplicated. Executing module bytes matching selected modules use verified source references. Staged chunks and Chrome profile cache are excluded explicitly; all selected runtime inputs remained byte-identical.
A local recovery check first found Pillow unavailable. It continued from the already finalized inventory and already retrieved hashes using the installed pngjs full decoder; no guest request or repeated download was needed. The allocator's inherited LBreakout board label was corrected append-only; the actual box name, UUID and ownership always identify this TR2 task.
One independent watchdog was observable before creation, UUID
87b6d305-40ea-4a7c-8a68-3a70e31cd678, immutable deadline
04:45:50.378824Z; original API expiry 04:45:49.821Z. Its supervisor actually
waited the watchdog with return code 0 and separate stdout/stderr EOF.
No deadline was changed and the watchdog did not expire.
Box bx_2578zw8k is ARCHIVED, expiry NULL. Sole unforced stop receipt stop_454cf2770c1bf1be completed 04:24:38.126Z, error=null; stoppedAt 04:24:38.099Z. Other boxes were untouched.
Recovery uses exact Git SHA, relevant binary diff and small owned-input patches; there is no source archive, local media copy, local Chrome, nested worker, guest write, artificial native call, clock/tier/configuration change or public deployment. Next requires separately authorized work that resolves the review-to-admission latency within the existing freshness limit. This worker does not attempt another original and stops after publication.