Hexen II reviewed WebGL pause and enemy boundary, 2026-11-18

The unchanged registered original reached a living two-spider encounter at health 68 using actual WebGL. Ordinary native Pause was verified and used to preserve the encounter for review. Enemy damage/defeat and ordinary Quit are not proved: the independent disk watchdog closed the scope before any attack or aiming adjustment was sent. This is a disk-floor cancellation, not a guest Quit or an enemy-hit failure.

Evidence: scratch/runs/20261118-hexen2-reviewed-living-enemy-consequence-webgl/.

Coherent graph and controls

The memory-only Git reader served proven commit 34c794d549c4ad71dfe40c1647e4ffd0c7a4f8af. All 1,448 source pins and all 18 media/manifest/registered-control pins matched. The previously compiled module was reused without recompilation: 2,418,470 bytes, SHA-256 1504acf2ea5cac3ec3b8c627f4edc64c564e62ad37c06928f288bd8ae83b4f37. Foreign worktree changes were excluded. The six production control dependencies also matched that commit byte for byte. No runtime/helper production fix or new build qualification is claimed.

Headful Chrome ran on an authenticated private X11 display with viewport emulation disabled. Natural endpoint receipts report gl-gps, backend webgl1, positive presents and ANGLE Intel UHD Graphics 620 / Mesa 23.2.1. Actual document/process/guest module object and GL endpoint/Worker/bridge identities were retained and checked throughout. No Debugger-domain request was sent. Consequently this run authenticates immutable served module bytes and actual module object identity, but does not independently recover executing Worker bytecode; the prior proven graph's recovered-byte evidence is reused. No hardware, FPS or parity claim follows.

A first scope closed before any input because the local observer asserted device.backend rather than the retained actual device.stats.backend. Its evidence already showed WebGL. The assertion was corrected offline; all waits completed before a distinct fresh scope. Neither scope was reopened. The file named startup-dialog.png actually shows the native main menu; no visible startup-dialog claim is made from it.

The qualified process-only release reader, atomic command publication and independent physical UP route were reused. A passive window-capture event ledger was installed before all input and retained trusted key DOWN/UP events. Transport ACKs remain separate from guest consumption. No Mouse1 input or attack was sent, so no mouse pair, attack ACK or enemy hit is claimed.

Personally reviewed original and normal pause

Reviewed native menus selected Single Player, New Game, Paladin and Apprentice. Meshing completed naturally. The courtyard showed upright fists and health 81. Ordinary Pause produced the native PAUSED plaque. Two whole frames 14.095 seconds apart retained the same camera, fists and HUD despite a 300-ms W input; natural presents increased from 9,751 to 10,177. Pixel differences were confined to sky coordinates x263–384/y351–386. The sky still animates; this is native play pause, not a claim that every rendered pixel freezes. Ordinary resume and subsequent movement changed the camera and advanced up the ramp.

A short right turn and manually selected W gestures reached the chamber. A capture immediately following travel still showed a transient close wall; the later paused view showed the chamber at health 68. Neither capture timing nor physical UP is treated as immediate guest-command completion.

Z had no view effect while paused. A finite ordinary Pause+Z gesture (300 ms), followed by an explicitly predeclared ordinary repause, exposed two upright spiders above the crosshair with health still 68. The paused enemy frame was personally reviewed. No attack was chosen at that misaligned angle. Read-only inspection of unchanged pak0.pak confirmed the default PageDown +lookup binding. An additional guarded run-local PageDown sender was prepared and syntax/event-shape tested, but never executed. It is retained as unused input preparation, not as a tested browser route or a production fix.

Exact stop, waits and recovery

At 15:50:07.235 UTC the independent watchdog sampled 1,499,836,416 free bytes on /home, below the required 1.5-billion-byte floor. It wrote local cancellation; the browser command loop closed without another runtime endpoint request. The subsequent attempted capture was refused locally before dispatch. No attack, later aim, Escape, menu Quit or terminal query followed. The initial scope minimum was 1,509,036,032 bytes; the final scope's continuous floor claim is false. The remaining cause is insufficient disk headroom before the aimed attack and Quit phase, not an isolated game/input defect.

Actual browser and display waits exited 0, with drained stdout/stderr EOFs. Native-supervisor/enclosing launcher/invoker waits exited 1 for cancellation, with both EOFs; watchdog wait exited 0. Containment reported no leaks. Native guest exit before host cleanup is not established; cleanup was cancellation and must not be labeled ordinary Quit0. All recorded owned PIDs were checked absent after closure.

All run growth used owned tmpfs. Selected whole PNGs were losslessly compressed with decoded-pixel equality and exact original-PNG regeneration verified. Unselected intermediate frames were omitted explicitly; their scene metadata and hashes remain. Unique helpers, logs, input receipts, Git identities, relevant binary diffs, owned note patch and recovery instructions were retained and verified before owned tmpfs removal. The module is a verified duplicate of the prior retained module and has a recorded recovery recipe. Git remains the source archive; no source snapshots, media copies or capture bundles were made.

No workers, boxes, Wine, Python, deployment, foreign cleanup, laptop actions or held-title actions occurred. Box ID null, state NOT_CREATED, expiry null, stop receipt null. Ownership is released after evidence sealing.