TR2 current linked shot attempt — 2026-11-08

Concrete remote blocker: the sole fresh launch timed out before DevTools readiness. No original game, current gameplay pixels or Control hold occurred. First exact linked shot RETURN remains unqualified. There was no replay or second launch. Evidence R: scratch/runs/20261108-tr2-current-linked-shot-2027/.

The remote integration selects 607 exact providers / 17 physical helpers. It retains the historical 1940 selection's game media, CPU/renderer module and nine HTTP resolver pins, removes its obsolete census-launch helpers, and uses the unchanged accepted 2019 browser, shot-options, launch, inventory digest and retrieval consumers. The accepted repair's 89 evidence references and decoded gzip originals were independently hash-checked; 27 Node, observer57, weapon150, inventory3, two actual launch controls and the locked build are reused by hash. These identical offline checks were not rerun. No production source was changed and no new build is claimed.

Published Git blobs explicitly select observer d018d806…, kernel e36d3499…, logger 979b3a8b…, readiness 9ba9ae8b…, close 1f4fe08b…. The CPU remains d8facd0658b7f158c6e60bef2de0936471f438f8bf41e9240fd75635f1d319dc, hashed but not executed. Full hashes, sizes and Git authorities are in runtime-pins.json and published-selection.json. Both kernel journal and command compression are explicitly gzip. The actual driver preflight validates all607 providers and exits before Chrome. Individually uploaded607 providers plus manifest/lifecycle inputs pass the remote content-verified staging barrier; its manifest SHA256 is b037e1db15c0a47f6572a0f16b1f7b699f3459898bd7169447cc458f54eb6380. The outer launch parent requires that same barrier before its exclusive claim.

A durable fresh UUID and immutable25-minute cap precede the single create. Independent observable normal/watchdog roles and their supervisor retain PID/start identities and compressed heartbeats before allocation. Box ID and initial expiry 20:55:57.953Z were persisted before runtime. The watchdog did not fire. No preexisting box was resumed or deleted.

At 20:31:55.902Z, the accepted readiness helper records DevTools startup deadline; not published; no replay at its30-second startup subcap. The retained profile later contains a valid endpoint and Chrome stderr contains a listening message; these later artifacts do not invalidate the recorded deadline or authorize attaching after failure. The driver never reached native-key preflight, registered-app navigation, graphics review, publication arming or gameplay. Nine HTTP pin checks completed before Chrome launch. No current owning WebGL2/module authority or healthy/drawn-pistol pixels were qualified. The sole requested1900ms Control was never dispatched.

Browser cleanup could not request CDP close and exhausted its30-second cap: 30002ms, terminal null, drained false, closeRequest UNKNOWN, SIGTERM then SIGKILL. The profile was retained and no cleanup/quit ACK was issued. The owned kernel supervisor then received one identity-checked SIGTERM for terminal cleanup. It retains114 PID/start terminal reaps, including11 subsequent adoption waits; all owned identities match actual before-reap/terminal sequences. The outer parent actually waits for supervisor status1 and stdio EOF. Remaining, unreaped and unresolved-ptrace sets are empty; both ports35399/33861 are closed and the runtime lock is released. No input receipt or held-input file exists.

Kernel complete remains false. Three autoattached tasks were killed and reaped without reconciled parent fork events: PID/start6714/14894, 6784/16396 and7127/17982. Their actual terminal waits establish retirement, not complete fork lineage. CLONE_UNTRACED and nonleader-exec limits remain; absence is not substituted for a wait. No writable FD into the run was observed in the final /proc scan; unreadable entries were skipped, so exhaustive FD coverage is not claimed. Failed browser drain remains UNKNOWN despite eventual kernel-level retirement.

Recovery inventories every regular evidence file without an extension filter, excluding only exact selected helper inputs. It retains206 regular references / 110 unique compressed transports,4,620,801 original referenced bytes and664,477 transport bytes. Every transport and original hash/size is independently reread; gzip decoding checks CRC, including nested originals and the kernel command log. Three profile Singleton symlinks are recorded without following them. The retained profile's regular files are individually recovered, without a directory archive. Browser/Chrome/kernel-command and lifecycle journals were gzip from their first stored bytes. Chrome's internal profile databases/logs are recovered in their native bytes inside individual gzip transports; those native profile files are not claimed to have been gzip at creation.

The first local nested-gzip verification failed because Python3.12 exposed a numeric outer .mode; explicitly passing mode='rb' corrected the local verifier. Already recovered files were reverified, without remote reexecution or refetch. An initial closure check also caught the missing physical ack-client helper; adding that unchanged accepted dependency made preflight pass before allocation. The first audit's assertion collapsed tracer and later adoption waits into one per-PID row; the final audit checks their actual sequence links separately. These failed local checks are retained and are not gameplay outcomes.

final-audit.json passes closure/barrier identity, sole-create/prearm chronology, no-gameplay assertions, exact terminal/adoption links, retained UNKNOWN/profile, all recovered SHA/CRC checks and the final API state. Normal/watchdog actual terminal waits are0, supervisor children are empty, and the local supervisor's actual tool terminal wait is0. Unique evidence was recovered and verified before the explicitly delegated normal stop.

Box bx_wws687r7 / ARCHIVED, expiry null. Stop stop_a5e399e16e6c6896 completed 20:34:30.859Z, forced=false,error=null. No billing-idle runtime remains. Source provenance uses Git SHA, relevant binary diff, small owned-helper patches and existing media/module path+hash references; no source-tree archive, media/module copy, peer WIP capture, old-run deletion, local Chrome, guest/private call/write, backend/config/binding/clock/seed change, public deployment, RAM gate or subworker occurred. Sampled home free space was above1.5GB; no continuous-floor claim is made.

Next work must resolve fresh remote readiness and cancellation-lineage closure before another explicitly authorized original. The bounded observer contract remains2500ms/32 records with actual retirement/remainder accounting and exact poll/Action/full-input/caller-ESP/weapon/shot links. Any later sole Control requires fresh reviewed upright/full-health/drawn-pistol pixels and explicit actionObserver:true, weaponObserver:true, untilShot:true; inspect first exact shot RETURN before any further action, with pendingWeapon:true expected and pendingShot:false required. Raw return0 is only attempted-shot evidence; the five-cycle type2/zero-ammo fixture is not production proof. The1940 early frame advance remains readiness evidence. Intel/SystemInfo SwiftShader qualification, Full27/parity/audio/FPS remain open.