MDK2 exact helper qualified; visible New Game and Medium, pending-scheme stop

Run scratch/runs/20261104-mdk2-exact-helper-native-replay/ staged and qualified the exact sealed observation helper, then performed one original browser replay. Fresh personally viewed pixels established highlighted New Game at step 3184 and the difficulty dialog with Medium highlighted at step 3232. Balanced ordinary Enter presses selected both. Tutorial and playable progress remain unproved. The replay stopped at its first unexpected controller failure; no retry, reload, second Chrome or predicate change followed.

Verified predecessor c4212edbb's complete seal: 44 files / 261934 bytes, seal SHA-256 84065258e835234e8df7a21c2ade98b230a7e4b160133aac10ccb706c10eebe2. Also verified the original candidate run's seal. Personally VIEWED historical step-3200 native-selector-76.png, SHA-256 52066472b64a5e63e650195bf842ec3221534336121acd7762254c84ccea989e, before making assumptions: readable New Game and a white controller permit input-free observation only. Highlighted New Game, Medium, pending and playable predicates were retained.

Before Chrome, inventoried the actual candidate/helper/driver import closure against sealed local files, including candidate sibling imports rather than relying only on runtime pins. All 24 resolved files matched actual remote bytes after planned staging. The only changed candidate file was the 7492-byte helper at 20261104-mdk2-unhighlighted-menu-onward/unhighlighted-control.cjs, SHA-256 b116e469f472a79affd4757850cfc509b618f7c665a3707c1a282b403821a6c7. The inherited b115459 helper was replaced before qualification, never executed. The small assignment wrapper was staged too; every other imported dependency already matched. Exact remote 37/40 sealed sibling sets and all 432 runtime pins were rechecked. The actual wrapper top-level test passed RUN, OUT and execution of the exact predecessor observe-browser.js preload, with main disabled.

Reused the unchanged sealed 85 passing controls (26 unhighlighted/wrapper, 30 pending, 18 scene, 5 predecessor routes, 6 adapter routes), plus predecessor CJS/ESM Puppeteer 24.31.0, isolated HTTP full-hash and cache98/12 evidence. No forced guest callback fixture ran. No environment rebuild, latest-main WASM, ESP/EIP/argument write, repaint, module/media copy or source archive occurred. Original source remains 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, canonical module cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, companion 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. Actual runtime identity and served-byte logs were recovered.

The sole Chrome (PID 14723, Chrome/151.0.7922.108) launched at approximately 11:26:43Z under the unchanged 350-second window ending 11:32:32.052Z, 600000ms TTL admission and recovery reserves. Startup advanced through separate fresh VIEW-first captures at steps 0, 512, 1024, 1536, 2048, 2560 and 3072. The last showed the title/legal overlay; a balanced Escape opened the menu. Fresh captures at 3120, 3136, 3152 and 3168 showed opening animation. At 3184, the controller had a red ring and New Game was readable. Exact capture-bound input review and native preflight passed before the first Enter. At 3232, personally viewed Medium was highlighted; its separate input/native preflight passed before the second Enter. The white-controller helper was qualified but not invoked: this replay reached the stronger highlighted predicate directly.

At 3280, pixels showed the Medium fade. The unchanged pending gate permitted one 16-slice input-free observation, producing black pixels at 3296. After VIEW and a separate exact review, the next 16-slice observation completed all three driver replies, including fresh capture pending-control-97 at 3312. At 11:31:32.335Z, its post-observation classifier rejected contradictory pending scheme: conscheme=menu, newconscheme=game, still level 0 / checkpoint 0, startscreen, freeze 1, showmenu 0. This is the exact first failed prerequisite, not proof of a guest crash or tutorial readiness. The failed phase and its latched error remain intact. No classifier relaxation or further observation was attempted. The final black capture was personally VIEWED after closure for reporting only.

Quit was the very next command, number 100. It acknowledged orderly Chrome exit 0 at 11:31:39.614Z, within six minutes and before the hard 11:43Z cutoff. All preceding replies were complete and successful; failure occurred in the controller's post-capture classification. Final input was balanced and drained. Menu continuation used 208 slices / 39 commands; pending used 32 slices / 6 commands, within the requested 512-slice / 96-command continuation ceiling. The 540-second continuation bound was not approached.

Recovered all 356 closed remote run files / 7117114 bytes with complete size/SHA comparisons by 11:32:15Z, before 11:48Z. No source tree or Chrome profile was archived. The final process inventory was empty for Chrome/Node. recovery-result.json, remote-recovery-inventory.json, qualification logs, candidate import inventory, captures/reviews, exact Git SHA, relevant binary diff and small owned input patches preserve custody and reproducibility. Only this note is committed; no production code or local heavy/build run was needed. Focused checks and publication are recorded in the run.

bx_ejf8j8yx is left RUNNING (API idle, health ok, hydrated), expiry 2026-11-04T11:58:35.973Z. Custody returned to the coordinator; shutdown remains the coordinator's at 11:52Z. No lifecycle action occurred. The next separately authorized investigation can assess the captured menu-to-game pending scheme; this assignment ends with the original predicate rejection preserved.