Hexen II recovered disk scope, 2026-11-20

Evidence: scratch/runs/20261120-hexen2-recovered-space-visible-enemy/. One fresh original used the preserved 2418815-byte module 10bdae2c56c79eeb5d0b4ebbc602c8a233e36351380da274a70f7f5e25363564, graph 34c794d549c4ad71dfe40c1647e4ffd0c7a4f8af plus the recorded 72dc77da0 capture delta, committed 65a75893c confirmation repair and the corresponding committed native-input, DOM-target and USER-observer helpers. All 18 original media pins and helper hashes were checked before the fixed 20-minute runtime budget; existing relevant tests/build PASS were reused. No shared source, held regions/mirror, foreign MCM WIP or build was changed.

Preparation saw 1504194560 free bytes on /home. During startup the owning CPU Worker's actual bytecode was fetched exactly once and matched the module. The page/process/CPU/GL endpoint identities were retained. The subsequent full renderer attestation was not reached, so backend execution is not newly verified. No screenshot or manual gesture was produced.

The lifecycle permanently closed at actual /home free 1498566656 bytes, before dispatching Page.bringToFront. The independent 100ms floor monitor also crossed the floor (minimum 1498513408 bytes). No later endpoint request, retry or successor scope occurred. Ordinary combat consequence and Quit remain UNPROVED; the prior Enter-to-ExitProcess cause remains UNKNOWN.

The independent UP child was ready and unarmed. Browser, display children, release child, launcher and monitor have actual waits with both output EOFs; native supervisor reports leaked:false and tracked processes are nonlive. Cleanup used owned local processes only, with the finite native watchdog. Box ID=null, state=NOT_CREATED, expiry=null, stopReceipt=null; root/coordinator retains shutdown ownership. No workers, Python, Wine or public deployment.