Hexen II: first spider encounter, death and native respawn, 2026-11-07

The original registered browser route advances beyond the previously verified Paladin courtyard movement and attack animation. The skull-panel doors open on ordinary forward contact, admitting the Paladin to an interior chamber. A close spider becomes visible; health falls to 12, then a reviewed capture shows health 0 and the rolled death view with the spider overhead. The next passive capture shows a native respawn in the original courtyard with health restored to 80. Weapon contact, damage to the spider and a kill remain unproved.

Evidence: scratch/runs/20261107-hexen2-first-enemy-progress/.

Preconditions and original route

The owning-Worker MIDI repair abf1b8c5b31c501e81871392256740ffafdcd138 was published with passing production Worker lifecycle/integration regressions and the locked full build before this task began. The validation, publication and source manifest were checked; all recorded source hashes still matched. The four MIDI production sources served to this browser also match those pins. No callback bypass, music disabling or cooperative scheduling was used.

The recorded manifest inventory was reused and verified: all 14 original files, the manifest, and installed root glh2.exe. Root executable SHA-256 remains 76d96731e3076441e5c70bce2089cd8f36f25b373214f656aa9d5cd8d532e9dd. The registered root deliberately avoids the bundled MiniGL beside the GLRoot executable. No layout or game bytes changed. Investigation used runtime/API observations and emulator sources only, respecting the bundled licence; there was no guest disassembly, extraction, patch or substitute engine/DLL.

Before allocation, actual Chromium controls passed positive native trusted key/combo/click/drag request, publish, consume and exact numbered ACK, balanced input and independent release. Nine identity replacements, stale and slow captures, partial delivery, UNKNOWN/late ACK sticky closure and wrong ACK had reason-specific rejection assertions. All transitive CommonJS imports resolved. The complete staged driver passed at the final app-selection boundary with zero original launches and the proposed 25-minute browser deadline. Native viewport was preserved: no emulation or resize. No identity or deadline guard was relaxed.

Git source commit is 3f0751ef18cc869e84f070796116f9effcfe2510; relevant uncommitted hunks and owned driver inputs are retained as patches. Git remains the source archive; there are no source/media archives. All 655 staged pins matched before launch and at terminal inspection. Live guest and render Worker modules were recovered and both match canonical SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467.

One fresh UUID-idempotent box bx_3rz64w6z was allocated at 11:09:42 UTC with expiry 11:49:42 UTC and a 40-minute total deadline including retrieval and explicitly delegated normal nonforced shutdown. There was one original heavy runtime, launched at 11:10:05 UTC. Browser deadline remained 11:34:12.136 UTC. No old box was resumed and no UNKNOWN input was replayed.

Reviewed consequences and ownership

Fresh notice and menu captures guided Enter through Single Player, New Game, Paladin and Apprentice. Model meshing was allowed to progress naturally, without editing guest time or caches. The first world capture shows health 79. A nearby black silhouette was inspected and judged urn-like; it was not counted as an enemy. Individual reviewed arrow holds then aligned and climbed the stone ramp.

The passive attack recorder failed with passive screenshot UNKNOWN before saving any frames. Its failure is retained and no attack-animation or weapon contact claim relies on it. The independent main command transport completed successfully; it was not replayed. Subsequent passive capture has its own ID. The retained DOM observations confirm the trusted balanced Mouse1 pair.

All seven world/progression/encounter/death/respawn captures preserve the exact same process, document, guest Worker instance/module, render endpoint, render Worker instance/module, canvas and page renderer identities (gameplay-review.json). Actual process is 1000, guest endpoint 1 / slot 0, Worker target 4FDB8C037AD01DB06E10D8EB3D04C946; render Worker target 7326F4866A70B88EC2E8F8BB830EBD18, GL/WebGL endpoint 1. A passive query of the live owning WebGLBackend confirms WebGL 1.0, WebGLRenderingContext, ANGLE Intel UHD Graphics 620 / Mesa 23.2.1, context not lost. Page renderer is Win98Renderer, scheduling remains threaded Worker. Native viewport is 945×889, with the 640×480 guest framebuffer displayed in 945×855 beneath the full-page strip. Black models remain a rendering limitation in these captures; this run does not prove a new emulator semantic defect. No FPS, audio quality, rendering correctness or parity claim follows.

Retrieval and shutdown

The last passive check found no held keys or mouse buttons and an empty input queue. Chrome closed normally at 11:18:46.426 UTC, exit 0 without a signal. Terminal checks confirmed all 13 recorded runtime/observer PIDs absent, both ports closed, profile and writer lock absent, and 21 exact successful ACKs. All 280 terminal files (10,622,691 bytes), including the unique recovered live module, were retrieved and SHA-verified before delegated normal box stop. Box bx_3rz64w6z is archived, stopped at 11:19:45.958 UTC; the operation is completed with forced:false, final expiry null. Runtime and box shutdown finished within eleven minutes of allocation. Custody returns to the coordinator with no running assigned box. No resume or deletion was performed. Final shared /home free space is above 2 GB; no peer data was removed.

No emulator changes were required. Only this note is committed. Next, if assigned, is a fresh encounter with an attack captured before the Paladin dies, to establish weapon contact/damage or an enemy kill; rendering, audio and performance require their own evidence. Historical October 11 CLI movement remains accepted separately.