Heretic II Demo (Raven Software / Activision, 1998)

App heretic2_demo (candidate heretic-2-demo, localOnly). A Quake II-engine third-person action game: Heretic2.exe is a 28 KB stub that imports Quake2Main from quake2.dll; H2Common.dll is shared by everything; the renderer (ref_gl.dll / ref_soft.dll), SndDll.dll and, under Base\, gamex86.dll, Player.dll and Client Effects.dll are LoadLibrary'd at runtime. Registered 274f69e21.

November 12 current checkpoint load comparison

Current module 04c53419… restores the complete unchanged crate0400 set on the actual SoftwareGL owner. The latest control shows HUD health 31 after normal load, a 600 ms backward pulse followed by 3000 ms with the movement key released, and a separate 4500 ms neutral interval. These checks use native pause/resume cycles; their final screenshots display the paused banner. They establish bounded living movement, not sustained onward gameplay.

WebGL again exits natively with code 8 during the same normal load. The new passive observer records successful context creation/current binding and zero at the existing startup error queries. There are no load-time error queries, so those results do not establish a clear error flag during loading. No runtime violation, repair or new checkpoint was proved. That comparison's final successful swap precedes exit by five milliseconds, but its completed pixels were not retained in that run. The2055 witness below fills this observation gap.

Published 8f68731a1; diagnosis, exact recovery and lifecycle limits, run 20261112-heretic2-runtime-boundary-1910. Coordinator review checked 364 references, 30 full PNG identities and PNG CRCs, and four complete frames. The box stopped normally; original local manager/watchdog parent waits remain unknown. Further investigation uses runtime/API/renderer observations only, without guest reverse engineering or guest modifications.

The later original exit-frame witness, published 6e8c88fa2, recovers the actual completed640×480 owning-WebGL image before teardown. The PNG's decoded RGBA equals the independent retained pixel hash, and all22 owner fields match. Completion is5 ms before native ExitProcess(8) entry and6 ms before host exit selection. The complete original frame shows the normal loading console and Paused over black; there is no visible error diagnostic. The final-frame objective is met. Exit cause, loaded-world survival and a new paired comparison remain unknown.

Root verified136 encoded/raw blobs mapping161 paths,11 original full PNGs, 42 balanced trusted input edges and seven independent releases. Whole-four VFS readback matches the unchanged save. The box stopped normally, expiry null; the browser parent1 after the pending post-exit capture is separate from Chrome0 and actual stop/manager/watchdog0 waits with both EOFs.

The retained API audit, a4420f289, identifies the next observation gap. Each of54 zero-EAX ReadFile post-handler records is followed by matching re-entry and success within the ReadFile stream. The frozen source invokes that hook during internal lazy-I/O parking, but the observer did not retain yield/park state. These rows do not prove guest-visible read failures or an exit cause. Ordinary-load-phase park/completion correlation remains needed; no speculative patch, extra GL/GetLastError query or guest reverse engineering follows from the audit.

November 12 observer limits and interrupted follow-up

The later payload-free observer, 66d04d314, removes inherited payload decoding from the future hooks. Its composed IAT/COM tests cover caller-to-thunk re-entry, bounded trace overflow and phase reset; payload guards report zero forbidden reads and zero decoder constructions. Actual original startup records 149 internal read parks and 149 correlated retries in each recorder. These are two observations of the same events, not 298 distinct parks. Guest returns remain UNKNOWN.

That original reached Easy, verified all four save files and typed the sole load crate0400 command. The newer settled screenshot label failed the driver's phase gate before observer reset or Enter. No Load was submitted, so this run neither reproduces Exit8 nor qualifies ordinary-load trace retention. Root checked 330 sealed file hashes, 134 opaque recovered blobs mapping 164 paths, and all twelve unique full PNGs behind thirteen capture paths.

The preceding 2230 staging attempt had retained an inherited WriteFile payload preview, violating the owner's no-decode restriction. Its evidence remains preserved and opaque; root did not inspect or use that payload. Its integrity checks are not a compliance claim. The later payload-free guards do not retroactively qualify it.

A separate driver-gate follow-up ended during provisioning: launcher status1, missing final report, and automatic safety-review refusal. The rejected workflow was not retried. Cleanup, 1c86ee44c, preserved eighteen opaque snapshots and normally archived bx_ktb4h7k3, expiry null, stop stop_20860d58ccf62cab completed unforced. Root verified all snapshot raw/encoded hashes and the stop receipt. Historical provision/manager/watchdog exit statuses and EOFs remain UNKNOWN; process absence is not a clean join or proof of a completed original run. No new cause, runtime repair, loaded-world survival or checkpoint is established.

November 12 health-crate successor

Run 20261112-heretic2-north-opening-health-crate-0400 reached the original tavern crate through the north opening, broke it with native Flying Fist, and recorded HEALTH POTION and HELLORB in the native console. Exact health gain and full-health status remain unmeasured. Staff strikes had not broken this crate; the neighboring small crate remained intact.

The new preferred interior continuation is all four crate0400 files in that run's save-inputs/crate0400/, with crate0400-native-manifest.json and RECOVERY.md. Initialize original Game → Easy, verify the complete unchanged VFS save readback, then use normal console load crate0400. It saves near (291.996,1623.636,−29.967), facing south. Normal reload returned upright; fresh movement reached (289.753,1675.588), followed by released survival. The large crate remained absent. Keep whole tavern0237 and key0136 as living fallbacks. guard0330 and door0136 remain experimental failed-reload sets; do not prefer them. No guard defeat or permanent safety is established.

The actual route crossed near x526 through the opening at y1536–1568, continued north beyond the partition's y1632 end, then went west to the crate's north face. Native map geometry was guidance; the break and pickups were observed in the original game. Some movement completed in a later cycle; the run helper's neutral wait increased from 700 to 3000 ms without changing game clocks. These wall intervals do not establish exact input timing.

The tested published baseline is 30f9318e6, actual Worker module 1165f15c…, software GL. Later shared lib/d3dim-gpu.js work was excluded from this isolated runtime. The coordinator checked 1,380 recovered references / 541 unique raw hashes, 88 native-file references and the full break, pickup-console and loaded-survival images. No production change, build or task commit was made. The box stopped normally before expiry with runtime parent wait/EOF; outer transport exit143 remains separate. WebGL parity, FPS and audio are not established by this route.

November 12 onward-room limit

Run 20261112-heretic2-crate-successor-tavern-onward-0435 normal-loaded crate0400 upright twice and verified fresh movement. Native traversal then climbed the north stairs to a cobbled room with crates, a red banner, a boarded arch and a close humanoid enemy. A bounded Flying Fist attack left it standing. No defeat, door opening or level transition was established.

Both new whole-four saves are experimental. onward0435 normal-loaded with explicit “Corvus died.” Saving earlier on the stairs as landing0435 first rendered upright, but its first fresh backward check reached Load Game without movement. Neither replaces crate0400. Exact health, damage timing and internal death flags remain unknown; these observations do not establish an emulator defect. A future attempt needs different threat handling or a living lower-stair checkpoint. The active slot moved to another game.

The coordinator verified 1,227 recovered references / 479 unique raw hashes, 96 native-file references and the full room/death images. Tested source stayed 30f9318e6 / actual Worker 1165f15c…, isolated from later renderer changes. No production code, build or task commit was needed. The box stopped normally before expiry; runtime and watchdog waits/EOF passed, while outer transport exit143 remains separate. Exact recovery and failed-save manifests remain in that run's RESULT.md and RECOVERY.md.

Licence

license.txt in _user1.cab is Activision's standard licence: personal use of one copy, no copying or distribution without written consent. Hence localOnly, never deployed. (rules.txt beside it is a 1998 contest, not a licence.)

Install

archive.org h2_demo_us, h2_demo_us.exe (40079639 bytes, SHA-1 d6593f2a1a12e39edd92338f95566e9c360d0c4e): an InstallShield self-extractor that 7z x unpacks into data1.cab..data4.cab, setup.ins etc. One file group, "Program Executable Files", 1825 files, 64 MB.

unshield cannot read these cabs. The common header is version 0x01000004 ("major version 0", treated as 5). Every file descriptor has flags 6 (compressed | obfuscated) but the data is not obfuscated, so unshield's de-obfuscation corrupts it ("Decompression failed with code -3"); -O segfaults (1.5.1 and upstream master 0d1e7cb alike). The data is plain IS5: [u16 length][raw deflate] chunks. Descriptors are packed 0x2a apart, with no MD5. tools/is5-extract.js handles it, including files split across volumes; the fetcher step is is5Extract.

Running

Route (headless, --batch-size=50000)

Main menu by b200. Enter at 300/400/500/600 (Game → new game → difficulty) starts the first area by about b700. Up from b1000 walks Corvus to the lectern (tutorial text), Right turns him toward the hall with the stained-glass doors. Evidence: scratch/runs/20261011T0645Z-heretic2_demo-gameplay-claude1863.

This historical headless route does not establish browser gameplay. See the original-browser run below for separately reviewed evidence.

Original browser gameplay reviewed, 2026-10-31

Run: scratch/runs/20261031T1941Z-heretic2-original-browser/. Documentation only; no emulator change or guest code inspection. The input main was 595b9f443b3fb9f92bbc8d25f37b08031cb3f125; the reread published main at launch was 721079ad7ae08c7c27368b56102c1aa781c672b1, verified against remote main over strict known-host SSH. heretic2_demo remains absent from public DESKTOP_APPS and present in the local candidate selector. No deployment.

Fresh original provenance and terms

Archive.org's h2_demo_us metadata returned HTTP 200 and identified h2_demo_us.exe, 40,079,639 bytes, SHA-1 d6593f2a1a12e39edd92338f95566e9c360d0c4e, MD5 ebbaa3ddf3fc5ed84dfbef5f60afe78c. One bounded acquisition into this unique run directory succeeded, HTTP 200, with the exact size and SHA-1; SHA-256 a7b29d478abfffc2221e2d713c2068d1e9f44292875db007160fefc7c0064307. No retry or alternate acquisition was used.

The corpus recipe's 7z installer extraction followed by tools/is5-extract.js on data1.cab produced 1,825 files, 63,842,666 bytes. Every original member was compared by SHA-256 with the installed tree: all 1,825 match, with no missing, changed, or extra installed files. All 1,824 browser-manifest sizes also match. Evidence: archive-metadata.json, archive-pin.json, acquisition.json, corpus-recipe.json, original-comparison.json, manifest-check.json. The derived duplicate extraction was removed after comparison to recover disk; the exact installer, member hashes and recovery recipe remain in the run.

The complete original Readme.htm and _user1.cab's 11,728-byte license.txt were read before runtime. The latter was extracted with the existing IS5 tool; 7z cannot open that cabinet. The licence restricts use to personal use, restricts copying/distribution and forbids reverse engineering, deriving source, modification, decompilation and disassembly. This run kept original guest binaries/assets/configs/saves unchanged, inspected no guest code, and remained private and local. licence-review.json records the document hashes.

Native routes and reviewed controls

The original menu differs from the old batch shorthand: Game → Tutorial starts the lectern room directly. Game → Easy starts the separate demo campaign through its intro. There is no separately observed “New Game” page. Both routes were exercised in one browser lifetime using visible checkpoints and trusted, balanced keyboard events. No console/map/state injection, config/save/cvar edits or added clock overrides were used.

These named screenshots were personally reviewed. Menus, logos and loading screens are route evidence only. The tutorial and docks captures establish player-controlled gameplay. No outgoing hit, kill, objective completion, audio quality, sustained combat, touch qualification or FPS measurement is claimed. The docks health display changes from 100 to 94; its cause was not established. Tutorial captions remain visible after switching to Easy in this lifetime; their reset behavior was not investigated.

Identity, environment and cleanup

Chrome 151.0.7922.108, native 1024×768 content area, defaultViewport: null, default isolated guest Worker, normal WebGL and emulator audio/clock paths. The existing registered wallClock: '1998-09-01T12:00:00Z' was preserved, as were the actual arguments +set vid_ref gl +set gl_driver opengl32 +set vid_xpos 0 +set vid_ypos 0. The browser used the standard local SwiftShader harness; listening was not qualified. HTTP COOP/COEP isolation was checked before launch and guest input.

Before/after identities match for all 528 source/UI files, 866 compiler/tool files and 1,846 original/manifest/shared-runtime pins. The served module is SHA-256 d39f362187ce89abda47fa53bca6bb6576badd8d21b78e44c6fbad973d1636d8; it and source/compiler bytes also match the tested predecessor manifests. All 970 actual HTTP responses carry isolation headers; all 964 served-file receipts (including prelaunch probes) join exact byte pins. Actual responses include ten 404s: optional build/auth/icon/font-bundle requests and the four ole32.dll lookup locations; these are recorded rather than counted as files. All 41 recorded native events are trusted, with 19 balanced key pairs and one Launch mouse pair. verification-summary.json, identity-before.json, identity-after.json, served.jsonl and actual-http-responses.jsonl retain the checks. No fresh build was needed for this documentation-only change.

Runtime ran 19:42:54–19:46:02 UTC, after current Slave Zero terminal lifecycle NEWFULLRELEASE193605 and an independent entire-Chrome/global-crashpad/profile PID/start gate. Inherited FD 9 held /tmp/wine-browser.lock through durable Python Popen.wait for controller, monitor and watcher cleanup. Launch reserve was 2,506,145,792 bytes; continuously sampled minimum was 2,296,856,576 bytes, above the 2.1 GB early-stop threshold. No deadline/resource stop or runtime signal was needed.

Independent final release at 19:46:02 UTC verifies all 24 owned runtime/helper PID/start identities absent, entire Chrome/global crashpad/profile process set empty, HTTP 39777 and DevTools 41911 closed, profile removed, held inputs empty and lock free. Evidence: full-release-proof.json, monitor-end.json, controller-wait.json, boardwatch-wait.json, wrapper-raw-exit.json. Boat ID/state/expiry: N/A, local run. No agents, workers, successors or deploy.

Next boundary: continue the original Easy docks route to a confirmed targeted hit or native objective interaction; qualify audio and FPS separately. No emulator failure or defined-use repair boundary was encountered in this run.

Native docks control and first route blocker, 2026-11-01

Run: scratch/runs/20261101-heretic2-native-objective-control/. One native original, 415.917 seconds, exit 0; no second original. This run reached Easy docks but did not establish an enemy hit or objective completion. The first unresolved obstruction on the attempted route is the wooden crate immediately in front of the closed, carved double doors beneath the lit stone archway. This is a navigation result, not a demonstrated emulator defect or proof that every other route or target is inaccessible.

Ordinary route and paired evidence

The book menu was visible at batch 100. Balanced Enter, Down, Enter selected Game → Easy (game-menu.png, easy-selected.png, easy-intro.png). The native intro advanced to loading without the previous browser Escape/resume sequence. Space down/up at batches 445/450 was queued during loading and dispatched at batch 673; it is not evidence of advancing a Raven-logo frame. readiness-1030.png shows playable docks facing the archway across the pier. The no-input interval through batch 1530 left Corvus at the starting dock; health fell from 100 to 98 without an attack input. Its cause remains unknown.

Up moved Corvus off the pier to the large crate beside the archway (approach-long-before/held/released/settled.png). Right turns explored the adjacent waterside path, where forward holds did not produce continued progress, then returned to the arch. The approach triggered the original caption “Walk into low ledges to automatically climb onto them.” enter-arch-held.png retains this caption. This proximity caption is not claimed as a completed objective.

Ordinary comma/period sidesteps and a short Left correction aligned Corvus with the crate inside the arch; these supplemented Up/Right, Ctrl, a and Space. No console, config, save, map or state injection was used. crate-walk-before/held/released/settled.png shows a forward running pose against the crate followed by standing on the same floor. The identified attack target was this wooden obstruction, not an enemy: crate-attack-before/held/released/settled.png shows the red projectile and a dark surface mark, but the crate remains intact and the doors stay closed. There is no outgoing damage, breakage, kill or objective claim from that shot.

Jump/forward attempts likewise ended back on the floor. The final aligned attempt is retained as aligned-climb-before.png, aligned-climb-forward.png, aligned-climb-held.png, aligned-climb-late.png, aligned-climb-released.png and aligned-climb-settled.png: Corvus raises his arms and becomes airborne beside the crate, then returns to its near side. The earlier Space action trial (door-action-before/held/released/settled.png) did not open or remove the obstruction. blocker-neutral-before.png and blocker-neutral-after.png provide a matched 100-batch no-input interval; the crate, doors and arch remain in place. Camera movement during turns and jumps is visible and is not evidence of traversing the obstacle. No living enemy was identified before stopping. The next gameplay question is how to pass or bypass this first obstruction with ordinary controls.

Identity, validation and release

Dispatch input was dd82ceb03a91273408caf743e64f4a5e4bde06a5. The gate passed at 12:34:18 UTC only after Rayman2 worker 01a19704-c68b-7920-9012-2f41436c746c had fresh launcher final.txt and result.json, plus its 12:34:09 explicit runtime/source/build release. Actual main at the gate and source pin was 065d2c6838eb381a62d63f87b94d30d1d45aa40d; the runtime deadline was 12:59:18. The registered arguments, stock files and wallClock: '1998-09-01T12:00:00Z' were preserved. The native CLI used the existing WAT software GL renderer (--gl-renderer=software), 640×480 captures, 100,000-instruction batches, frozen stepping and ordinary input dispatch. No browser, GPU, Boat, acquisition, install or new EULA was involved; the previously reviewed personal-play licence was reused without guest-code inspection, modification, disassembly or reverse engineering.

Before/after checks match all 1,825 independently compared original files (63,842,666 bytes), full tree membership, the browser manifest and all 1,824 manifest sizes. All 4,444 source/module pins and 860 observed runtime file reads match. The accepted build's complete 4,392 input pins and 141 recorded build reads matched, allowing reuse without a fresh build. Actual runtime compilation received module SHA-256 dd43e4a6624d2449d7133b731d687c32530f7fcf0041a69ba71a09f78c09aaf4. Runtime compilation identifies module bytes; it is not proof of compiler source reads. The observer covers string-path synchronous, callback and promise file reads, not every descriptor or direct OS I/O path.

The observer validation actually executed synchronous and asynchronous Wasm instances, preserved all 536,870,912 shared-memory bytes and clock identities, and retained the last 64 events after 10,001 late events. All 104 PNGs passed chunk CRC and full IDAT decoding; the complete compressed runtime log decoded. All 56 ordinary key edges were dequeued, routed and dispatched; known input queues were empty at the final capture. Guest post-queue coverage is unknown. Identity checks, input records, landmark comparisons and reviewed captures are retained in verification.json, input-consumption.json, pixel-landmarks.json, controls.ndjson and manual-controls.ndjson.

The live controller sampled disk continuously, minimum 2,155,077,632 bytes, above the 2,000,000,000-byte floor. Its owned Node runtime exited normally on the delegated shutdown request. The auxiliary pre-gate guard/watcher ended when their launcher session closed; controller monitoring covered runtime. Local box ID/state/expiry: N/A. No audio, FPS, browser/native parity or full suite claim is made. Only this note is tracked; evidence and control helpers remain in the ignored run directory. cleanup.json verifies owned runtime, helper and watcher PIDs/groups absent and no new temporary directories.

GPU stream v2 main-menu seam (2026-11-16)

On the browser default (software GL on the gps WebGL executor) the main-menu book showed a 1 px dark line at y 256. The book is 1:1 point-sampled WRAP tiles (256x256, 256x128, 256x64, 256x32) whose quad edges sit exactly on pixel centres, so the D3D top-left rule decides the row. The executor emulated that with a 1/128 px y lift, which SwiftShader's 4-bit subpixel grid rounds away; GL then gave row 256 to the upper tile at v = 1.0, which wraps to its texel row 0. The lift is now 1/16 px (Y_CENTRE in lib/gpu-stream-webgl.js) and the per-app glRenderer: 'webgl' opt-out is gone. Headless GL keeps more subpixel bits, so the CLI never showed it: test/test-gpu-stream-webgl-subpixel.js snaps vertices in the VS to reproduce it. Evidence scratch/runs/20261116-gps-edges/.