Hexen II final adapter native proof, 2026-11-20
Evidence: scratch/runs/20261120-hexen2-final-evidence-adapter-native-gameplay/.
The unchanged a98d42dea/ac6d6115f Hexen adapter passed one fresh authored native
receiver run. The exact 2,418,815-byte module SHA-256 starts 10bdae2c56c79eeb;
all 18 existing media pins were checked, and the actual CPU Worker module was
attested once per incarnation. The exact-source 26 Hexen controls, 42 legacy
controls and locked build from the predecessor were reused without rebuilding.
The receiver is the existing genuinely authored GetMessageA GL fixture, with
its normal guest timer and stationary yellow triangle. No forced USER poll,
repaint, original state change, tolerance, masking or matching-phase search.
The personally inspected whole-host source and signed fresh capture matched
all 1280 by 1024 RGBA pixels. Pre-DOWN and socket fences also matched. The signed
fresh capture completed at 1795168841529; the genuine owning USER observation
was 1795168841562. The previous observation at 1795168841481 was correctly not
ready. Actual key A was consumed at the owner-worker-native-user-return boundary
at 1795168841760. The independent release participant emitted trusted UP at
1795168842052 and observed physical state zero. The guest caption became DU.
The opt-in evidenceSink retained complete copied source/fresh PNGs and original
comparison facts; identical PNG bytes share one content-addressed image. No
historical mismatch cause is inferred from this positive run.
One conditional ordinary Hexen II run then reached its main menu. It closed
before fullscreen consent DOWN or any guest DOWN: the inherited run-only
host-review helper allowed live_input_fixture and quake2_demo, rejecting
the actual hexen2_demo app name. The failure and complete reviewed host image
are retained. No later endpoint request, replay or successor scope was issued.
Movement, living-enemy consequence and ordinary Quit remain UNPROVED. Host
cleanup is not Quit. This is a concrete run-helper blocker, not an adapter or
gameplay failure. The run-only correction recipe changes that exact app ID;
offline old-fail/new-pass checks preserve rejection of changed module, viewport,
button, running state, wrong app and expired review. It was not used to restart
the closed scope. Production adapter/common source is unchanged.
Both owned process trees joined under native-supervise and independent finite watchdogs. The unchanged cross-filesystem helper verified full bytes, SHA-256, file and directory fsync before owned tmpfs removal. No source/media snapshots or frame series are retained. Git, relevant diffs, media references and driver recipes describe recovery. Localhost box id=null, state=NOT_CREATED, expiry=null, stopReceipt=null; root owns shutdown and delegated owned cleanup.