TR2 visible-target preparation ended without firing — 2026-11-08

The one authorized fresh remote original reached gameplay, but no enemy was visible after seven separate navigation inputs. Shared disk writes then crossed the owner's 1.5GB floor, ending preparation. No Control hold was sent. There is no new shot receipt, native target identity, linked damage observation, hit or kill qualification. The visible-target/damage goal remains unqualified; this is a concrete original-run blocker, not a preparation-only success.

Evidence R: scratch/runs/20261108-tr2-visible-target-damage-2142/. The personally reviewed final image is review/webgl/final-no-target.png, 21:48:09.014Z, SHA256 5297716c3b8b6f40d0172cd310ea7a72a718097f1c40d1da82807953420a7287. It shows upright Lara in the narrow rising alley, with no visible enemy. The health bar is not visible. Space was delivered to draw pistols, but ready weapon status and full health were not independently qualified. The complete pre-fire visual conditions therefore never passed, and firing was withheld.

Actual selection and startup

The regenerated closure has607 providers,57,950,900 bytes and17 physical helpers. It selects published observer Git e850fc6a9e47fe72afcdd582a267e234cdfcf650, actual provider SHA256 b3f15b215fe6e97f755cc57e1f1d4d5757f68bf991149668e08bdc1b43cc19a6. The obsolete d018 observer was not selected. Kernel remains published bcf8c7bd788f2c63668406b11f72652006cde8dc, SHA256 5371233b12d3a63e13a9768529af43e5a61b7ff1682b2d3c09e4db6a976e12d0; both journal and command compression are explicitly gzip. Logger979b3a8b, readiness9ba9ae8b and close1f4fe08b remain unchanged.

The accepted2019 browser, launch, inventory and retrieval consumers are byte-identical. The one adapted consumer is shot-options.cjs: its old blanket arrow rejection becomes separate arrow holds requested1–400ms, maximum30, while combos remain refused. The browser's fresh-image admission, independent release and one-observation-attempt lock remain unchanged. Explicit actionObserver:true, weaponObserver:true, untilShot:true forwarding and the requested1900ms Control guard remain unchanged. This guard adaptation implements the newer navigation authorization; no new observer fields needed forwarding.

Published sources resolve from Git blobs; both CPU modules resolve by existing 1810 paths/hashes, without module/media copies or peer-WIP selection. The actual driver preflight checks607 providers and exits before Chrome. All609 uploads joined before the remote HASH barrier and sole launch. Manifest SHA256: 10bfd6a133c3b2f72c1854096cace66b0cb23f6e2e087df296090a658d849946. DevTools became ready in14,154ms within the unchanged30-second cap. Ordinary Enter100ms accepted the reviewed current Hardware3D/Full Screen640×480 sheet. The original drew gameplay on the owning WebGL2 endpoint1, with executing CPU d8facd0658b7f158c6e60bef2de0936471f438f8bf41e9240fd75635f1d319dc. The Intel owning-context versus SystemInfo SwiftShader discrepancy remains unresolved; no physical-GPU claim follows.

Accepted2019's27 Node/57 observer/150 weapon/three inventory/two actual-launch and locked-build proofs were independently checked by retained hashes, without identical reruns. The repaired kernel's155 proof references and new observer's retained inventory, focused real-x86 controls and build evidence were also independently reread. New checks cover the navigation guard, full closure, actual driver preflight, remote HASH barrier, original execution and recovered evidence. Initial local preparation corrected the observer inventory filename, its regularFiles key and an indentation error before allocation; these are recorded in R, not hidden as successful first attempts. No production source change or new full-build execution is claimed.

Navigation and exact outcome

The publication observer armed normally; final publication remained live with failure-null and retained rows. After released Space1500ms, each navigation command used the immediately preceding reviewed image, its hash and bound live identity. Five separate forward holds were followed by two separate right turns to inspect the alley after little forward progress. No inherited dog-facing assumption, combination or attack was used. The captures show limited scene change, not successful target acquisition. Physical host samples do not prove that each interval contained a native game input poll.

Requested navigation durations were400,400,400,400,400,300,400ms. Measured durations were400,400,400,401,400,300,400ms. Navigation4 exceeded the owner's 400ms limit by1ms. The final audit reports navigationActualCapConforms:false; it does not round the result or qualify compliance. The initial audit equality assertion exposed this exception and is retained. Future bounded work would need timing margin; this result authorizes no retry. One stale Graphics Enter request was refused before dispatch with effects0, followed by a fresh capture; no UNKNOWN input was replayed.

No Control command, observer installation for firing, shot entry or shot return exists in this original. New entryTarget, returnTarget, signed HP, targetHealthDelta, exact 42f5e0 → 42f50a link and positiveDamageObserved fields were not produced. They are not zero-target or negative-damage observations. The observer's offline positive-damage controls are not this original's result. No aim, effective firing, hit, damage, crossing zero or kill claim is made. Historical2116 target0/EAXffffffff remains unchanged.

Recovery, normal stop and publication

Shared free space fell below1,500,000,000 bytes during preparation. Used passive JSON metadata was losslessly compressed with original SHA/size recovery records; all logs, including command, Chrome, kernel and board streams, were gzip from their first stored bytes. There was no descriptor bypass or new disassembly. Preparation ended and normal Quit received ACK15. Chrome terminal was0 with signal-null, closeRequest ACK, no signals and13,200ms close duration. Both compressed pipes reached EOF before profile removal and cleanup ACK.

Kernel custody has361 owned PID/start identities and361 matching actual terminal reaps, complete=true, with empty remaining/unreaped/unresolved/cancellation sets. The outer parent actually waited supervisor6370/start8932, exit0 and stdio EOF. Ports44581/38641 closed, profile removed, writer lock absent, runtime lock free and observable owned writable FDs empty. The global census retains1023 unreadable FD entries; CLONE_UNTRACED/nonleader-exec coverage is not claimed. Absence is not substituted for a terminal wait.

The coordinator restored headroom by losslessly compressing its own closed worker-event streams. Then every233 regular remote artifact,41,012,438 original bytes, was recovered through212 gzip transports/5,469,539 bytes. All compressed and original SHA/size and gzip CRC were independently reread, including gzip -dc; selected sources and executing module use verified references. No extension filter, symlink or special file was omitted as ordinary evidence. Retrieval verification preceded the delegated normal-stop request.

A durable UUID preceded the single idempotent create. Independent observable watchdog/normal roles and supervisor were prearmed with immutable25-minute deadline22:07:46.681Z before create; ID and initial expiry22:07:46.214Z preceded runtime. Both roles have actual parent exit-zero waits; the supervisor reports no remaining children. The watchdog did not fire.

Box bx_qh5rjhvx is ARCHIVED, expiry NULL. Stop receipt stop_ebd5e1a09c2a6bc1 completed21:51:58.888Z, forced=false, error=null; stoppedAt21:51:58.871Z. No old box was resumed, stopped or deleted.

Recovery identifies Git SHA, relevant small diff, small owned-input patches and the inherited boot-provider recovery patch by path/hash. There is no source archive, media/module duplication, old-run deletion, peer edit, local Chrome, private guest operation, configuration/backend/binding/clock/seed change, subworker, RAM gate or public deployment. The concurrent disk-floor breach and 401ms interval remain explicit exceptions. audit.py verifies preservation and lifecycle; its pass does not mean the visible-target/damage goal or navigation cap passed. Full27/parity/audio/FPS remain open. The next task needs restored headroom and a separately authorized visible-target preparation; this worker publishes the concrete result and stops.