MDK2 fresh native New Game readiness, contained observation-review error

Run scratch/runs/20261104-mdk2-fresh-menu-cinematic/ reached a fresh readable New Game label and original native readiness together at3200 slices. recovered/browser/native-selector-76.png, SHA-256 0c3c2c8b49146e29b645853fcca03237afff9883beaffb61dfd00e72fbe03f60, was personally viewed: controller icon highlighted red, New Game readable, legal overlay absent. Native startscreen selection0, applied scheme title, pending scheme nil, current lang, freeze nil, and empty/rest input state passed unchanged preflight-input-review.cjs with a separately authored, exact-capture offline-only New Game review after browser closure. No review was submitted to authorize New Game input. Medium, comic cancel, postcomic cinematic, playable readiness, movement and fire were not reached.

First error and containment

The fresh3184 capture already showed readable New Game and the highlighted controller. I incorrectly classified it with absent-label/none-selection opening fields. I issued its input-free observe call in the same orchestration as viewing the image, before interpreting the returned pixels. That inaccurate review is preserved and explicitly superseded by review-correction.json. It authorized only state/step16/shot, with unchanged guest input history. This is an operator review error, not a native engine failure or a successful selection. On recognizing the discrepancy after personally viewing3200, the next browser command was quit79. There was no second browser, reload, input retry or guard weakening.

The run-owned next.py is repaired offline: all menu/scene observation routes now require a separately authored observation-review-<fresh-capture>.json, bound to capture/hash/steps/personal inspector before any remote review. Input routes retain separate input-review files and unchanged local native preflight. Historical observation templates are removed. Six offline checks cover absent review, valid review, wrong capture/hash/steps, and template removal. This route repair was not retried live. Future execution must view and interpret each image before invoking the separate review/advance operation. route-repair.patch preserves the change.

Verification and provenance

The actual driver, controller and staged cinematic helper are byte-identical to fe26bfcad1dfc169e572fba8f11b1fc2b3c70058's tested inputs. Production tools/mdk2-cinematic-review.cjs matches its staged helper. Exact-revision prior 116 focused /90 candidate /177 predecessor /177 redirected results are reused, with input and test-evidence hashes recorded in reused-tests.json. No tracked production code changed; no new build is claimed or required for this note. The retained pinned runtime remains source 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, canonical wasm cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, compat 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.

Before Chrome,432 exact source/module/media pins, actual Puppeteer24.31.0 CJS/ESM, isolated HTTP full hashes, cache98page/12worker references, process identity and actual staged driver/helper closure passed. Initial remote test selection wrongly included local captured fixtures; corrected selection left those tests local. One unchanged synthetic150ms ACK timing case failed, as previously documented; the unchanged full applicable rerun passed207/207 before Chrome. Guards were not changed to make it pass.

The sole Chrome23689 session closed normally10:13:27.347Z, ahead of10:17 hardclose. Validation checks80 contiguous successful ACKs,3200 completed slices (step max64), only balanced title Escape input, and all served hashes. First menu allowance113 was explicit; menu ledger24commands/128steps, newgame=false, medium=false. The construction540-second aggregate anchor was never created, reset or extended. All history/ownership/ACK/fault/identity/native-phase and finite budgets remain.

All268 closed browser artifacts/6,076,702bytes were recovered with full SHA verification before10:22. Chrome and driver absent; HTTP33149 closed; 432 runtime pins and37 staged input hashes unchanged. Git SHA, relevant binary diff, run-owned repair patch and new-input patches preserve provenance. No source archives or module/media copies were staged. The local shared D3D edits were not substituted into the pinned runtime.

bx_dmq33y4w is left RUNNING (API idle, healthy/hydrated), expiry 2026-11-04T10:27:13.933Z, shutdownOwner coordinator, custody returned. No lifecycle, allocation, source-box access, local heavy browser, subworker, successor, HeroesII or deployment occurred. Next work requires separate authorization: the fresh menu can be reviewed truthfully for balanced New Game/Medium, then input-free cinematic observation and only separately reviewed playable controls if reached. Publication outcome is recorded in the run handoff; local commit is not proof of publication.