Dungeon Keeper current dungeon attempt, 7 November 2026
The first blocker is qualified production source changing during staging. No original browser or guest was launched, and no original native input, digging, persistent dungeon consequence, or current Eversmile screen was observed. The historical activation and semaphore repairs were not repeated; the historical black-screen registry comment was not used as a diagnosis.
Evidence is scratch/runs/20261107-dungeon-keeper-current-dungeon/.
The selected driver qualified locally against main
e112295a4e576e9550077a98613e2ae12b188b65 plus the recorded relevant patches.
Its complete 629-file manifest includes all 149 lib/*.js files, deferred
worker-observe.js, helper imports, generated fixture inputs, both production
modules, and 167 original installed media/manifest inputs. The exact selected
Worker-attach handler rejects a missing observer and successfully evaluates
the present observer before resuming. The actual local Chromium production
guest/render Worker route also passes. Its generated COM caption and white
canvas screenshot were personally inspected. This establishes local driver
attachment, not original Dungeon Keeper gameplay.
Input/release, identity, stale and UNKNOWN refusal controls were reused by
verified identical helper and production hashes from the preceding passing
controls. The real selected driver entry accepts a constructed 25-minute
deadline and rejects 35 minutes, expired and NaN before Chromium/guest
creation, without changing its guard. Local termination returns the exact
closure-quit ACK; process IDs and ports are absent/closed, profile and writer
lock are absent, and native/held input is empty. The captured live standard
module is SHA-256
e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467.
One UUID-idempotent 40-minute box, bx_2qjdjabg, was created at
12:33:19.196Z (create response), expiring at 13:13:18.640Z. During serial
staging the unchanged SHA check rejected lib/guest-worker.js: expected
76,978 bytes, SHA-256
5e42deeefe4fd06f8ab65fd85b5d73eca3ca7b75f19ab61891a82d9d21c574dc;
observed 77,196 bytes, SHA-256
50dbf5f648e8198040e24052e76ba953d6c9c8dc698855d5430e4329b1caa194.
The file is owned by the concurrent Outlaws Worker NE lifecycle worker.
The expected bytes are independently recoverable from the recorded Git SHA;
first-blocker.json verifies that match, and concurrent-source.patch
preserves the observed change. No unrelated source was edited, rolled back,
requalified in place, or silently repinned. The allocation was not retried.
The ledger has 321 successful records; one already queued upload completed
as the executor stopped. A subsequent read-only remote inventory verifies
all 322 uploaded files against the selected pins. No original output,
launcher or runtime PID exists. The box reports ready, remains running,
and is handed back to the coordinator with its expiry. The task's explicit
runtime lifecycle assigns shutdown to the coordinator on recoverable failure;
no stop, delete or resume was requested. Archived state is therefore not
claimed. The immutable browser deadline, never used to launch an original,
was 12:57:53.269304Z.
The existing local installer output is complete: 166 files, 19,754,866 bytes,
and all four pinned executable/DLL/map/sound hashes match
the installer recipe. Its installer package is absent,
but no installed file is missing, so no media recovery or guest modification
was needed. Media remain local and unchanged; every installed file and the
manifest have path, size and SHA-256 records. No source/media archive was made.
Sampled /home free space stayed above 2 GB.
The only executed browser backend was the generated local COM fixture's production guest/render Worker with a legacy WebGL render endpoint, using Chrome 151.0.7922.108 and native 1024×712 inner viewport. Original Dungeon Keeper presentation was not executed: DirectDraw software presentation and active D3D coverage are both unobserved for this task. No FPS, audio, parity, whole-game correctness or persistent action claim follows from these checks. No emulator mismatch was demonstrated, so there is no emulator fix, new regression or code build for this documentation-only finding.
Next work requires released, stable production Worker sources and newly qualified complete driver inputs before a newly authorized original browser attempt. Then inspect fresh original screens and use ordinary native pointer controls to mark digging or perform another persistent dungeon action.