Quake II bound move-up route, 0635

The requested progress beyond 0537's red-lit lower passage was not achieved. One fresh original Outer Base run ended at the first personally observed unexpected death screen. No further input, capture or retry followed. Damage cause is UNKNOWN; no guard encounter or operated door is established.

Evidence: scratch/runs/20261109-quake2-bound-moveup-route-0635/ (ignored).

Decisive images and terminal boundary

Before runtime I personally viewed 0537's frame-right-consequence.png and hatch-descent-result.png, and 0600's bindings-screen.png. No prior 47-hold route was replayed. I personally viewed every fresh decision PNG.

Fresh first-scene.png shows the starting area at HP100. pane-result.png shows a projectile approaching the pane; it does not establish shattered glass. pane-near.png shows a close metal wall and crates. My interim description of that image as inside the pane room was too strong: these frames do not independently establish traversal. room-floor.png shows the crash-pod area at HP94, captured 06:56:24.914Z, completed 06:56:25.293Z.

The next and final image, review/crate-side.png, shows a tilted view, HP0 and LOAD GAME, with ENTERING Outer Base selected. Capture time was 2026-11-09T06:57:03.775Z, completion 06:57:04.179Z; 187793 bytes, SHA-256 d7ea3a412ca4c62ff9c58ccc973241c8273cf4fb4d14a070802edaaf8e2d353d. The final command attempted a left turn from the reviewed crash-pod view. No load, respawn, menu navigation, later input or capture followed this image. terminal.json records personal review separately from capture time.

This is a concrete terminal gameplay blocker, not a damage-cause diagnosis. HP alone cannot identify an attacker, fall, hazard or timing defect. Retained runtime failure receipts first report deliberate caller revocation during cleanup, not an earlier transport failure explaining the death. All 56 passive samples were SNAPSHOT on one memory identity; all nine holds had ACK releases. Those facts do not prove consumption or survival between PNGs.

The actionable route limitation is that pane break and actual interior entry were not established before moving onward. A separately authorized successor needs decisive fresh images of those transitions before attempting the hatch; an owning event/contact witness would be needed to diagnose damage or ascent. No successor or additional runtime is scheduled by this task.

Exact preparation and controls

The 722-provider closure uses 0537's exact providers except published reader 75b1a18c358f91a32790eac85fe12bc1b0d9427d. Caller 1473c5952a52d5d2b4546b93a0d462b64fe5c6cd and custody 4341b87723a7d56bc98223215cca4cdc878fcae2 were explicitly pinned. Five older providers were read directly from Git without reverting shared files. CPU: 2185596 bytes, SHA-256 a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295.

The exact 19 final 0537 proof references passed SHA/size verification. Four published 0625 reader/test/build references matched its retained integrity index. Fresh compiled preflight and both actual composed persistent PIPE lifecycle cases passed against the final caller before create, including actual waits and separate stdout/stderr EOF. No production code changed; no build against different shared sources is claimed. Local/remote manifests matched f3e1048d09fb3876dd4252053bd3c6c9d80c5be9373f330a69b0ff0b05455ff2.

Before first input, fresh sparse rows established Space32/Mouse2(201) +moveup, a97/comma44 +moveleft, d100/period46 +moveright, left130 +left, right131 +right, Alt132 +strafe, Enter13/Mouse1(200) +attack, Control133 +movedown. These remained stable in all samples. Death occurred before a ladder or any Space attempt. No a input or move-up claim was made. No guest write or rebind was used. Consumption, contact and ascent cause remain UNKNOWN.

Native lifetime remains REVOKED; all-writers and edict ABA remain UNKNOWN. Strict lineage, observation flags, preCPU/preDLLmain barriers and all work/ACK/hold/freshness/close caps were unchanged.

Retrieval and lifecycle

The exact Drakan 0635 ARCHIVED PHYSICAL_DRAINED release preceded create: bx_yuspm6ar, UUID 1cf87c53-ac3c-48ff-a96b-a4ae4e82fe05, stop_0c5ed0ef9ded78e9 completed 06:50:46.557Z. No peer runtime was modified. An observable independent watchdog was armed 06:51:45.389Z, before create, against immutable UUID d0f9ed07-5967-4d1b-93ac-ea79750df84b and 25-minute deadline 07:16:45.264Z. Exactly one box: bx_zzxck5un, TTL1498, initial expiry/archiveAfter 2026-11-09T07:16:45.168Z.

The caller retained stdin PIPE through gameplay and started output drains before launch. It and the remote parent actually waited1 with separate EOF after deliberate revocation: cancellation cleanup, not a normal close proof. The kernel-cancelled launcher exited -9. Custody records 346 owned / 346 actual reaps, 3844 events, complete true, command-log EOF true; no remaining, unreaped or unresolved ptrace/lineage/resume entries. Ports45927/34947, tracked processes, profile FD writers and runtime/input locks drained; the profile directory remained. Historical UNKNOWNs are not upgraded by census.

All 166 remote regular-file rows, 5594290 row bytes and 99 newly stored unique contents, passed independent SHA/size verification before archive. Every gzip passed GNU gzip CRC and independent decompression/hash. Verification also checked all 11 PNG chunk CRCs/decompression, 10 commands, nine hold releases, capture identity/order, unchanged barriers and actual reaps. Recovery uses Git base plus small patches and existing media/module path/SHA references; no source tree, media or module archive was created.

Final state ARCHIVED, stopped 06:59:02.417Z. Receipt stop_f0d1a38a57eff38f, completed 2026-11-09T06:59:02.436Z, forced false, error null. Final archiveAfter null; expiresAt not returned. Watchdog and lifecycle supervisor actually waited0 with separate EOF, releasing the local runtime lock. PHYSICAL_DRAINED posted 06:59:27Z. Board watcher actually waited its tail child -15 with separate stdout/stderr EOF; outer tool completed0. Free /home stayed above 1.5 GB (1830871040 at gameplay verification). No agents, workers, local browser or deployment were launched.

Single-task STOP. Onward success and damage cause remain unestablished.