Dungeon Keeper local driver qualification, 7 November 2026

The staged browser driver passed local qualification with the existing small production guest/render Worker fixture. This prepares a later original Dungeon Keeper digging attempt; no original game was booted and no box was allocated, resumed, stopped, or deleted. The registered original route, configuration, installed executable, DLLs, and assets remain unchanged.

Evidence and executable staging helpers are retained in scratch/runs/20261107-dungeon-keeper-local-driver/. The successful execution is local-production-complete/; the initial local-production/ execution closed at the 1.5 GB disk floor before any native input (native-input.json is empty). Writes paused until disk recovered. The successful run then completed and closed its own local browser/server/profile, releasing the shared fixture queue. No held original-game input or UNKNOWN command was retried.

The actual staged browser.cjs, bound-input.cjs, qualification.cjs, and qualify.cjs ran against production guest-worker.js and d3d-render-worker.js. Both live Worker modules were recovered through CDP and matched SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467. runtime-pins.json records source/media hashes and the source Git commit; source.json and the adjacent binary patches preserve relevant uncommitted sources and owned new helper files. Git remains the source archive.

Passing controls:

The reviewed image is the fixture caption on a white canvas. Its observer reports WebGL2/ANGLE Intel UHD 620 for the fixture only. It establishes no original-game rendering backend, gameplay, dungeon digging, FPS, audio, parity, runtime compatibility, or full27 result. No emulator mismatch or production code change was required; no full build was needed for this documentation and ignored-helper change.

Rerun the helpers from the owned run directory after verifying disk and pins: node test-deferred.cjs, node test-transport.cjs, PYTHONDONTWRITEBYTECODE=1 python3 validate-deadline.py, and node check-http-closure.cjs. The successful browser command used LOCAL_PRODUCTION_FIXTURE=1 LOCAL_QUALIFICATION_EXIT=1, CASE_TAG=local-production-complete, and an externally constructed BROWSER_DEADLINE=now+1500000, under /tmp/wine-build.lock. Use a fresh case directory for a future isolated fixture run.

Next: the coordinator may assign a separate original-runtime attempt using the preserved registered route, after checking disk and the runtime pins again. Inspect fresh original captures before ordinary native actions. Box ID, state, and expiry are all not applicable; this assignment owns no test box.