Quake II tunnel guard attempt, 0350
Guard/door objective not achieved. One fresh original passed the accepted0325 armor point, traversed the narrow metal-and-rock passage and reached the fire-lit outdoor slope beneath a broken elevated doorway. Health fell from 100 to 46 near visible fire; the final personally reviewed PNG shows HP 0, a tilted death view and the Load Game menu. Death cause is UNKNOWN. No living guard engagement, kill, operated door or level transition is established. No second life, retry, later gameplay input or later capture followed that image.
Evidence: scratch/runs/20261109-quake2-tunnel-guard-progress-0350/.
Final image review/advance-outside-ramp.png: 181,122 bytes, SHA-256
b58a7645b5638790aed9533ef8f05f7a850e84b46d7a979772e192d3566a4146.
The preceding review/inspect-outside-left.png shows HP46/armor25 and the
outdoor slope; review/pass-armor-point.png shows Jacket Armor25/HP100.
All 18 PNGs were personally viewed. SHA, PNG chunk CRC and IDAT checks pass.
Each of 17 bounded native holds followed review of its freshest PNG, received
a successful numbered reply and balanced physical UP acknowledgments. Two
holds used forward/Control. Passive arrow/slice observations do not prove Ctrl
or weapon consumption. No autoroute, replay, detector, retimestamp, rebinding,
freshness bypass or guest-state manipulation was used.
The accepted0325 note and its final PNG were read and personally reviewed;
that PNG's SHA remains
80c5d2c00152173b84aff5fd98f0c016a638a5019c79829d3774cc1d3265f45b.
Accepted caller/composition/shared-Q3/build checks were reused by exact
path/size/SHA. The 721-provider manifest SHA is
4c11735caac25f912269298379f3c8d81ffb54383be28a1e455bb7142c6b1d76;
local and remote barriers agree. CPU remains 2,185,596 bytes, SHA
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295.
Both strict flags were set before CPU execution and pre-DllMain, both startup
observations retain zero execution entries, and trace [1,0x400000,0x500000]
preceded release of the parked DLL load. Caps and freshness were unchanged.
Custody was pinned to published Git commit
2df8d81b41da78ac0ab846137cf4137f0f1c4a86, SHA
a3a802d1f7cff96b7ee7351702f09284426a8881e81b2f49f607c42869e714ee.
Manifest source base is 9b67856565200e6bf4c982cd019e502eba108488.
After death, only no-input Browser.close cleanup was requested. Browser.close ACK needed SIGTERM; actual exit was zero with both stream EOFs after 14,300 ms under the 19,840 ms nested cap, normal:false. Cleanup's first remote failure was 04:04:30.672Z; quit has no successful numbered reply. No later game input or capture followed either death review or runtime failure. The local client actually waited with status 1 and separate EOFs; its launch transport actually waited with status -9 and separate EOFs. These remain failures. Historical shutdown cause remains UNKNOWN; no shutdown repair is claimed.
Kernel custody records 355 owned identities and 355 actual terminal reaps, verified against 3,673 journal events and before-reap witnesses. Drain is complete, command EOF true, unresolved/remaining/unreaped sets empty. Remote parent actually waited with status 1 and separate stdout/stderr EOFs. Ports 41495/37421 were closed, tracked runtime identities absent, profile FD writers empty and input/runtime locks drained. Local lifecycle and watchdog actually waited with status zero and separate EOFs; the local runtime lock is free. Physical drain does not make browser close normal or qualify all writers. The separate local messageboard watcher tool session ended with status 143; its wrapper wait receipt is missing and separate EOFs remain UNKNOWN. The final integrity sweep found incomplete watcher gzip streams. Original bytes and explicitly partial recovered text are preserved; no complete-gzip claim is made for those local watcher logs. Its tracked child is absent. This does not change the pre-archive verification of the remote artifact set.
Warcraft0350's exact ARCHIVED PHYSICAL_DRAINED release at 03:55:11Z
preceded allocation; Warcraft itself followed Super0350's release. Box
bx_nckcav9a used immutable UUID
48092a8d-d338-4d68-abf2-9cdfd6566b9d. An independently prearmed observable
25-minute watchdog preceded finite-TTL1495 creation. Initial expiry was
2026-11-09T04:20:53.729Z. All 269 remote artifact rows / 251 unique contents
(9,112,958 row bytes; 179 newly stored contents) were retrieved and checked
by stored SHA/size and GNU gzip CRC/decompression before delegated normal
archive. Final state ARCHIVED, stopped 04:05:30.411Z; receipt
stop_eabd003c16a8aaa7, completed 04:05:30.435Z, forced=false,
error=null. Final archiveAfter=null; expiresAt was not returned. Physical-drain
release was posted at 04:05:47Z.
No production code changed. Evidence uses exact Git base plus small patches and existing media/module paths with hashes; no source archive, repeated media or module copy was made locally. No agents/workers, local browser, peer box, RAM gate or public deployment was used. Free /home stayed above 1.5 GB. Native source lifetime remains REVOKED/unqualified, all-writers UNKNOWN, edict ABA UNKNOWN. Full27, parity, audio and FPS remain open.
Next requires separate authorization for a fresh guard/door attempt; this single task stops after publishing this unsuccessful attempt and its evidence.