Original MDK2 callback selection attempt, 2026-11-04
New Game and Medium were not activated. One browser remained on the original title/legal screen through step 3200 after one balanced Escape. The v2 read-only observer reported Level.file=startscreen, freeze=1, applied title scheme, no pending scheme, effective native showmenu zero, and native Enter at rest. No Enter or comic Escape was sent. The original title-opening callback/input boundary remains unresolved; browser delivery alone does not establish original callback execution.
Evidence: scratch/runs/20261104-mdk2-native-callback-selection/. The predecessor is the native selection boundary note, commit 9ab81c37e51ebc81b0475e19bbe855ac54edab6c. Its recovered corrected v2 observer, callback/release checks, and four test files were reused. The native observer bytes are unchanged. Raw Lua gamecontrol.showmenu remained nil while the separate effective native accessor read zero; no raw-accessor predicate was introduced. No production files changed.
Preparation and tested dependency repair
Actual remote execution at 05:34:25.687Z and API inspection independently verified assigned box bx_85fyu4ug: running execution, API idle, healthy, hydrated, snapshot verified 05:34:01.138Z, expiry 05:48:31.042Z. All 432 existing runtime pins, actual Puppeteer 24.31.0 import, registered MDK2/WebGL selector, isolated HTTP responses and full module hashes passed before the only browser. There was no runtime/media restaging or installation.
Before launch, the original 117 tests passed: 13 native observer, 48 selector, 50 comic, and 6 inspection-barrier cases. Browser-driver limits were updated to seven minutes and absolute close 05:41Z; recovery metadata was explicitly updated to 05:43Z. Startup remained bounded to 4096 steps/180 seconds, selector to 512 steps/64 commands/240 seconds, each step command at most 64. Startup reached title at 3072 within 180 seconds.
The inherited controller also subtracted a three-minute recovery reserve from the browser deadline. With the new browser deadline this would incorrectly stop commands at 05:38Z. Run-only recoveryEnd(id) now uses the earlier of the browser deadline and explicit recovery cutoff minus two minutes. Legacy identities without that metadata retain their previous three-minute reserve. Both selector and comic controllers use this calculation; callback/native release checks, inspection authorization and aggregate caps remain intact.
The first attempted deadline edit simply removed the reserve and failed the existing comic reserve rejection test (116/117 passed). A shell sequence lacked fail-fast handling and uploaded that candidate and executed one inspected no-input 16-step observation despite this test failure. That was a workflow error; it is not a passing tested-before-use claim. deadline-tests.log preserves the failed regression. The corrected metadata-aware implementation passed all original 117 tests before its subsequent use (deadline-fixed-tests.log). Six additional offline deadline tests pass, including actual Spool ACK after 05:38Z and rejection before submission at 05:41Z; these added tests were run after browser closure and are not live evidence.
Actual result and evidence limits
Browser identity timestamp was 05:34:54.776Z; normal close ACK was 05:38:42.766Z, comfortably inside both bounds. validation.json records 78 contiguous successful command ACKs, 55 step commands totaling 3200, maximum 64, and 13 personally viewed captures. Inputs comprised the balanced Launch mouse click and one balanced trusted Escape on the screen; there were zero Enter edges. The selector used 128 steps and 22 commands. No second browser, reload, repeated Escape, guest writes, arbitrary readiness delay, or native/Lua invocation occurred.
The title/legal pixels remained visible after Escape and five finite observations; no highlighted New Game control appeared. At 3184 and 3200 the native observer still read freeze one. At 3200 this was classified as the unexpected title-opening boundary and game work stopped. first-runtime-boundary.json, recovered/browser/native-selector-74.png (SHA-256 74b9e9e1ffa0e5b81589c081d47c9b42fd8a0c017350ace23b929237c292e825) and its original native state preserve the failure. No New Game readiness attempt, native selection callback confirmation, or Enter release polling sequence occurred; merely deploying those helpers does not validate them live.
There is an additional inspection annotation defect: five post-Escape title captures were approved with openingAnimationVisible=true, although their actual pixels show the static title/legal screen. Those observations did not establish an opening animation. The retained approval log is not rewritten; validation.json explicitly records this limitation. The last screenshot was personally viewed and deliberately left unapproved. No annotation authorized Enter, Medium, or comic control.
The cause of the unsuccessful title opening is unknown. Earlier successful runs and this run differ in observed outcome despite identical runtime pins; this does not prove a timer, readiness threshold, callback bug, or input-consumption cause. Additional arbitrary steps or another Escape were not used to manufacture progress. Next work must establish the original title-opening callback/native input boundary before attempting New Game, then Medium with the retained v2 callback/release checks.
Recovery and handback
All 263 closed remote artifacts (6,450,224 bytes) were recovered by full size/SHA-256 and independently verified stable before 05:43Z. Closure checks found normal Chrome exit, fixed-identity browser/driver absence, private port 42823 closed, all 200 served pins matching, and all 432 runtime pins unchanged. Existing canonical module/media paths and hashes are referenced without repeated copies. Source identity is execution Git 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, recorded checkout SHA, relevant binary diffs, and owned new helper/note patches; no source archive was made.
Final actual execution at 05:39:06.642Z and refreshed API inspection verified the box still running/idle, healthy and hydrated, snapshot verified 05:39:02.028Z. Box bx_85fyu4ug is left RUNNING, expiry 2026-11-04T05:48:31.042Z; shutdown ownership returns to the coordinator. No allocation, resume, stop, deletion, successor, subworker, lifecycle action, deployment, or other game run occurred.