Quake II onward tunnel gameplay, 0325
One fresh original traversed the low rock tunnel beyond the crash room and collected Jacket Armor: 25 armor, 100 health. The final PNG was personally reviewed before ordinary quit. This is new visible onward-tunnel gameplay beyond Q20219's crash-room 102HP endpoint. No living guard engagement, kill, onward door operation or next-level transition is claimed.
Evidence: scratch/runs/20261109-quake2-guard-door-onward-0325/.
Final image: review/collect-tunnel-armor.png, 446,102 bytes, SHA-256
80c5d2c00152173b84aff5fd98f0c016a638a5019c79829d3774cc1d3265f45b.
The preceding tunnel-left-opening.png shows the armor still present;
the final image shows its pickup text and new armor HUD. Twenty fresh PNGs
were personally inspected; capture SHA, PNG chunk CRC and IDAT checks pass.
Each dependent command followed review of its current image. No autoroute,
replay, retimestamp, rebinding, second life or second original was used.
Eighteen native holds have successful numbered replies and balanced physical UP receipts, including three forward/Ctrl holds. The game's visible movement, Crouch Here prompt and armor pickup establish gameplay consequences. Passive held samples observe arrow physical state and advancing owning slices; their coverage does not include Ctrl/weapon consumption. No exact count of game input polls, simulation steps or weapon consumption is invented.
The 721-provider manifest retains the canonical CPU SHA
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295
(2,185,596 bytes), both strict observation flags and unchanged caps/freshness.
Manifest SHA is
6796cbb6e617dbbd034ac9a85f3adf754fce4b11e4c32f32a9238da9802f67bc.
Local and remote provider barriers agree. Custody source came directly from
published Git commit 0cde26d0b, SHA
c7264650beb466176d4c5169aa50666805d7c53bc43b7a0404d93c462c72568b;
concurrent native0325 WIP was excluded. Manifest Git identity is
1193187dbbac78636c6fda9ee1978ccb715efebd. Both before-run receipts retain
zero execution entries, strict flags before slot-zero creation and the existing
trace [1,0x400000,0x500000] before releasing the parked original DLL load.
Native source lifetime remains REVOKED/unqualified, all-writers UNKNOWN and edict ABA UNKNOWN. Screenshots do not qualify these properties. Full27, parity, audio and FPS remain open. Historical shutdown cause remains UNKNOWN; Q20301's unchanged small-Chrome passes at 237/207 ms and delayed EOF at 1,569 ms establish no historical shutdown repair.
Ordinary quit failed after Browser.close ACK, TERM and KILL: actual browser
exit zero and both stream EOFs, elapsed 17,289 ms within the 19,863 ms nested
cap, normal:false. First remote failure was 03:34:26.542Z. Quit has no
successful numbered reply. No later gameplay input or capture occurred.
The monitored local client actually waited with status 1 and separate stdout/
stderr EOFs; its launch transport actually waited with status -9 and both
EOFs. The remote supervisor actually waited with status 1 and both EOFs.
These failures remain failures; the successful tunnel consequence predates them.
Custody records 356 owned identities and 356 actual terminal reaps, verified against 3,633 journal events and their before-reap witnesses. Kernel drain is complete, command EOF true, remaining/unreaped sets empty. Ports 36243/40529 were closed, recorded remote runtime PIDs absent, profile FD writers empty and input/runtime locks drained. Historical untraced/nonleader coverage remains UNKNOWN. Local client/lifecycle/watchdog waits and distinct EOFs are retained; the local heavy lock is free. Physical drain is separate from normal close.
The exact Super0320 ARCHIVED PHYSICAL_DRAINED release preceded creation.
Box bx_eec74n3h used immutable UUID
a1c41bb1-cd89-431a-b65c-35dee81ff61b, an independently prearmed observable
25-minute watchdog, finite TTL1498 and initial expiry
2026-11-09T03:49:44.522Z. All 291 remote artifact rows / 271 unique contents
(9,461,010 row bytes; 191 newly stored contents) were recovered with SHA/size
and GNU gzip CRC/decompression verification before delegated normal stop.
The box is ARCHIVED, stopped 03:35:20.940Z; receipt
stop_baf6369e617a6c14, completed 03:35:20.961Z, forced=false,
error=null. Final archiveAfter=null; expiresAt was not returned. Runtime release
was posted promptly after archive and local watchdog drain.
No production code changed. Accepted caller/composition/shared-Q3 tests and locked build were verified by path/hash and reused without repeated fixture acceptance. Fresh validation covers all PNGs, numbered replies, physical releases, strict startup gates, actual waits, separate EOFs, no later commands/ captures after failure and recovered artifact integrity. Evidence recovery uses Git SHA plus small run-input/owned-note patches; no source tree, media or module archive was made. No local Chrome, concurrent heavy runtime, peer box, agent, worker or public deployment was used. Disk samples stayed above 1.5 GB.
Next, if separately authorized: continue from a fresh original toward guard/ door gameplay, preserving the native/source UNKNOWN limits. This single task stops after publishing this note.