Dungeon Keeper original capture gesture, 7 November 2026

The original reached Main Menu. One ordinary trusted gesture qualified the automatic unlocked input path at that instant: capture intent was false, and MOVE/DOWN/UP reached the normal consumer. Useful continuous steering, Start New Game, Eversmile and dig/build remain unproven. The first unresolved gate is a fractional driver anchor versus integer trusted DOM coordinate; the unchanged helper rejected motion before sending any step. This is not a Pointer Lock rejection or an emulator correction.

Evidence: scratch/runs/20261107-dungeon-keeper-capture-gesture/. I personally inspected the immutable owner-scoped review/startup.png (red rotating intro), menu.png (Main Menu with Start New Game), after-gesture.png (dimmed Main Menu) and current-scene.png (Main Menu). The later capture resolves the dimmed image as insufficient evidence of credits or gameplay. No credits dismissal was needed.

Actual input and capture decisions

All 646 retained runtime/media pins matched before allocation and after execution. The unchanged original-successor recipe launched the registered dungeon_keeper_demo route in one fresh separate box. Automatic profile selection remained unchanged; there was no explicit relativeMouse profile. The retained next-capture-observer.cjs expression was installed through observer.cjs, which rereads actual page/guest module bytes and compares all 22 owner/module/window/epoch fields before and after its observation. Existing selector and consumer observers call their original functions once and preserve their returns. No guest writes or private input handlers were used.

recovered/passive-install.json, passive-menu.json and passive-gesture.json retain the actual decisions and capture observer rows. The observer was installed at 15:13:11.415Z. Escape dismissed the reviewed startup animation, receiving numbered ACK 0. At 15:13:30.466Z the selector returned false with a false cached hint, absent recenter state and no lock.

The reviewed Main Menu title, outside all action rows, identified the purpose of the single deliberate ordinary capture/focus gesture. Command 1 used normalized (0.5,0.11) at 15:13:45Z. The actual move and DOWN decisions were false, with false cached hint, no warp and no recenter run. The request wrapper recorded no requestPointerLock call, change or error. The trusted native events were MOVE/DOWN/UP at CSS (352,246). The ordinary consumer returned MOVE, hit test, DOWN and UP for HWND 98305 at guest (320,52). UP was armed before DOWN, independently attempted at 15:13:45.489Z and acknowledged at .492Z; the command received exact numbered ACK 1. The document observer retained DOWN but not UP; the separate native observer, consumer and independent release receipt establish UP without inferring it from that incomplete document event list.

After a fresh capture (ACK 2) and personal review of Main Menu, command 3 requested four (2,0) physical CSS steps at 40 ms intervals. The helper saved recovered/original/motion-qualify-motion.json: released mouse, automatic profile, capture intent false, no lock, inside the guest picture, steps=[]. It failed unlocked native anchor changed at 15:14:24.092Z. The browser driver computed and retained Y as 194 + 480 * 0.11 = 246.8; the trusted event's clientY was 246. X was 352 in both. The exact equality gate correctly refused the mismatch. No step, physical-anchor reset, second capture gesture, forced profile, direct capture call or UNKNOWN replay followed. ACK 3 never arrived; the transport became sticky and the driver closed on its first fault.

Executable next diagnostic and verification

Run the offline reproduction, which opens no browser and sends no input:

node scratch/runs/20261107-dungeon-keeper-capture-gesture/next-anchor-diagnostic.cjs

It invokes the unchanged helper against the retained anchor and admission, reconstructs the driver's fractional point, asserts the same failure and asserts zero effects. Next trace Chromium's client-coordinate integer conversion against submitted CDP doubles and the driver's physical pointer bookkeeping. Preserve the exact anchor and all capture/freshness gates. Any justified harness correction needs focused failing-before/pass-after coverage and a locked build before a separately authorized fresh original. Do not reset the physical anchor or retry this closed lane. Only after useful consumed motion may a successor steer toward Start New Game/Eversmile.

Observer syntax and return/throw/once/restoration controls passed, as did the offline anchor reproduction and all retrieved SHA/length checks. The global evidence checker still fails on unrelated Alice and Tunnel/Twist containment errors and reports historical missing artifacts. This run has no candidate-manifest registration, so the evidence remains in this investigation note. No production code changed; no production regression fix or build is claimed.

Source and terminal custody

source.json records preflight sourceSHA 4069c54524a667c40be2a474eeea3225ba55ee58, pin-source commit 34384c0938832cc8d32a26c061b41947ad30c490, relevant tracked/new binary patches and the predecessor source reference. runtime-pins.json retains individual path/length/SHA references, including existing game media; source and media were not archived. Small run-specific diagnostic inputs have a recovery patch. The retained executing page/guest module is e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467. Browser: Chrome 151.0.7922.71, V8 15.1.206.10.

retrieval-verified.json verifies 73 unique artifacts, 3,066,572 bytes. Custody confirms Chrome exit zero, browser/server PIDs 18950/18939 absent, ports 43155/43819 closed, no matching live runtime process, profile/writer lock absent, no held inputs, final buttons zero and queue empty. The browser's closure destroys the installed observation wrappers. Sampled /home free space remained above 2 GB.

Lifecycle was explicitly delegated by this task. One UUID Idempotency-Key POST created bx_e54wh4z7; no old box was resumed or changed. The creation response used archiveAfter, not expiresAt; the initial allocation script's KeyError is retained. The same allocation was provisioned without a repeated POST. The immutable deadline was 15:36:46.380Z, bounded by original expiry 15:51:46.234Z. After verified retrieval and browser cleanup, one normal stop stop_510cd46e8b8d6f64 completed, forced=false, error null, at 15:14:56.611Z; box state archived, stoppedAt 15:14:56.593Z. boat-state-2.json verifies the terminal result. Archived archiveAfter is null; data-retention expiry is not exposed and remains unknown. No running box or pending lifecycle work remains assigned to this worker.