Quake II observed original route, 0105
One fresh original reached actual Easy gameplay by native browser input, then walked through the crash room into its broken floor shaft. The final personally reviewed image shows Crouch here, the low rocky tunnel and 100 health. No living guard or onward door was reached. The corpse and the damaged ribbed entrance are not guard/door success. The orange marks inside that entrance were sparks, not an identified guard. No shots, replay, second life or second original were used. This is an actual gameplay attempt with a concrete remaining input limitation, not guard/onward-route certification.
Evidence: scratch/runs/20261109-quake2-observed-guard-route-0105/.
The clearest final image is review/tunnel-advance.png, SHA-256
e18dc25aadb916050c092cb861612336b6c17f88372955691c9b20e02b3d812c.
All 38 fresh PNGs were personally reviewed before their dependent inputs;
PNG chunk CRC, IDAT decompression and capture SHA checks pass. Thirty-seven
native key commands have exact successful numbered replies, owning admission
and physical-release receipts. The accepted key combination allowlist permits
forward plus steering, but not forward plus crouch. It was left unchanged;
standing forward movement reached the game's explicit crouch prompt.
Original and owning observation
The current canonical 713-provider manifest passed locally immediately before
allocation and identically remotely before launch. Manifest Git identity is
b02b2f649145af8dce8eed0e7e5a8e232726b789. The actual owning compiled CPU is
build/wine-assembly.wasm, 2,185,596 bytes, SHA-256
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295.
The actual EXE hash is
2fa987c9390663e230c5b6479285e7c55511e35f80091bfed96f43062c1c810b.
The e65895936 owning binding and ba5c62c38 strict startup path were retained.
Both WINE_QUAKE2_LOAD_OBSERVATION and
WINE_QUAKE2_NATIVE_WRITE_OBSERVATION were set before slot-zero creation.
The ordinary original DLL-loader call was parked before any DllMain execution,
acquisition, conversion or startup. Both before-run observation receipts show
zero execution entries; the existing trace was armed with
set_trace_esp(1, 0x400000, 0x500000) before releasing that exact saved loader
call once. Offline gate checks preserve its arguments, receiver and Promise
result. They are control checks, not gameplay fixtures.
Actual native observer UUID: 4d64bc74-401a-4cb1-80fb-8dcf7bbd0d44.
The final point receipt retains model range [0x6d7da0,0x6e1da0), epoch 350,
last four-byte store PC 0x410f49 at 0x6d8314; table range
[0x47b554,0x47b954), epoch 36, last four-byte store PC 0x42b116 at
0x47b5e0. Overflow is zero for both recorded counters. LOAD_ENTRY is
0x4117b0; final later-use PC 0x42f0da records indices 10/11, pointers
0x6d7f08/0x6d7f30, candidate headnodes 4873/4883 and actual edict values.
These are owning point receipts, not complete writer history.
Raw status remains INVALID (export: get_last_run_halt); native completion
was interrupted by import: log, startup completion is missing and later-use
records are REJECTED. Their raw reasons retain source lifetime REVOKED or
unobserved, uncovered writers, missed boundaries and edict ABA UNKNOWN.
The sampled source list is empty, not proof of a live source. All-writers,
raw shared memory, imports, other workers, bulk/locked/partial stores and edict
ABA remain UNKNOWN. No valid lifetime, complete loader return or guard/door
continuity is asserted.
Failure and shutdown
After the final capture, ordinary quit hit its unchanged 20-second command-work
deadline at 01:47:55Z. Browser close had a separate unchanged 30-second cap and
finished after 26,593 ms: close ACK, TERM and KILL recorded, browser exit zero,
normal:false. Quit has no successful numbered reply. No input or replay
followed recognition of this UNKNOWN. A cancellation check found the exact own
supervisor PID already absent; it did not signal a replacement process.
The local original-launch tool returned 143, noticed during shutdown; its
wrapper/child wait and stream-EOF receipts are missing. Earlier inputs had
already occurred, so full prompt launch-failure/first-UNKNOWN compliance is
not certified. Four incomplete local gzip streams retain their exact bytes
under .incomplete-gzip names with stored hashes and original/CRC UNKNOWN;
no footer or successful wait was fabricated. Historical 143, nonleader and
untraced-clone coverage remain UNKNOWN.
Remote custody did finish: 361 owned identities, 361 actual reaps, no remaining or unresolved traced identities, command EOF true, journal closed. The remote parent actually waited its supervisor with return code 1 and output EOF. All recorded remote PIDs are absent, ports 34399/38171 closed, no profile FD writers, profile removed, input writer lock absent and runtime lock free. Local tracked identities are absent; lifecycle/watchdog and board watcher were awaited with exit zero and the local runtime lock is free. Physical drain does not repair the missing historical local waits.
All 529 remote regular evidence rows were recovered and verified before stop;
339 added unique stored content. Stored/original SHA-256, sizes and independent
GNU gzip CRC/decompression checks pass for complete recovered gzip files.
The independent immutable UUID watchdog was armed before create with a finite
25-minute deadline. Box bx_5vb8rtbm was normally stopped under delegated
authority at 01:50:10Z and is archived. Stop
stop_d8453dd4a51bdd5c completed, forced false, error null. Initial expiry was
01:54:20.894Z; archived archiveAfter is null. Explicit ARCHIVED
PHYSICAL_DRAINED runtime release was posted for the next queued worker.
Unchanged accepted PATHHASH tests/build were hash-verified and reused; the six
native input/ACK helpers were byte-identical. New checks cover the DLL gate,
actual PNGs, native replies/releases, zero-entry trace prearm, owning module
binding and actual custody records. No production code changed, so no new
production build was needed. Recovery is Git SHA plus small own input patches;
no source/media/module archive, peer box, local heavy runtime, peer deletion,
RAM gate, agent or public deployment was used. /home samples stayed above
1,500,000,000 free bytes.
Next: fix and test prompt launch-terminal observation and quit/close budget composition, and provide an explicitly reviewed bounded native crouch-forward path before any separately authorized original. Retain the current strict observation and continuity limits. This single task stops after publication.