MDK2 fresh New Game and Medium, bounded post-selection gap
Run scratch/runs/20261104-mdk2-adequate-lifetime-menu/ personally viewed fresh
readable New Game with the red controller highlight at3216 slices,
recovered/browser/native-selector-79.png, SHA-256
327fd853357d88a1d41b55bd22c52914904df05ae1e0e4aed70ecab3f055afd9.
A later, separately authored exact-capture/hash/step input review passed unchanged
native readiness and input preflight. Balanced Enter opened Select Difficulty;
at3264, native-selector-82.png, SHA-256
6fd368506c2385fa0a5cad0ebeef734dc6857549a4e1df9b784fe5282163ba3c,
was personally viewed with Medium highlighted. Its separately authored input
review and unchanged preflight passed; the second balanced Enter completed the
native Medium callback/release envelope. Both selections are proved, rather than
inferred from elapsed slices. No movement, fire or mouse input occurred.
Fresh review and containment
Every image was viewed and interpreted in its own tool call before subsequent
review/advance. The exact repaired next.py from5f9d6dd46 required separate
observation-review files; input reviews remained separately bound with native
preflight before remote authorization. No historical review templates were used.
Fresh3184 and3200 pixels still lacked the red highlight/readable New Game; their
truthful opening reviews permitted observation only. This differs from the
historical3184/3200 captures and demonstrates why step counts are not readiness.
At3312 and3328 the fresh captures showed the menu fading after Medium. At3344,
native-selector-103.png showed a black guest surface with version1.000, without
loading/comic/tutorial content. A local read-only scene-transition.identity
probe rejected it with original level construction schemes. Captured native
facts were file=startscreen, conscheme=menu, pending scheme=nil, showmenu=0,
freeze=1, levelnumber=0/checkpoint=0. Thus black pixels did not qualify as
level destruction/construction or loading. This was a premature phase probe,
not demonstrated native-engine failure. On the first rejection, the next browser
command was quit106. No retry, reload, guard change or second browser followed.
Construction, comic cancel, postcomic cinematic and playable readiness remain
unqualified. The construction/comic540-second aggregate anchor was never created.
Verification and recovery
The successor2627b5271 deadline gap was read. This new authorized box satisfied the unchanged ten-minute TTL and three-minute recovery requirements before Chrome. The driver and all38 predecessor control/test inputs matched their recorded hashes; the116/90/177/177 results were reused after verifying their four evidence hashes, not rerun. The exact observation route6 and separate input/native ordering6 behavioral controls passed. Stale extra tests were not repeated.
Before Chrome, actual Puppeteer24.31.0 CJS/ESM imports,432 source/module/media
pins, isolated HTTP full hashes, cache98page/12worker graph and actual staged
closure passed. No source tree/archive or runtime modules/media were copied;
only small run-specific controls were staged. Runtime remains pinned to source
1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, canonical wasm
cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee,
compat 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.
No tracked production code changed and no new full build is claimed or required.
One Chrome9619 opened10:26:32.739Z and closed normally10:31:35.713Z, within the six-minute bound and before its stricter10:32:31.468Z absolute deadline,10:55 hardclose and10:59 recovery deadline. Validation passed107 contiguous successful ACKs,3344 complete slices (each step<=64),18 fresh captures and200 matching served hashes. The input history is exactly balanced Escape, Enter, Enter. Native menu ledger retained allowance113,51commands/272steps and open/newgame/medium=true. All history/fault/ACK/identity/empty-rest/readiness/native-phase and finite-budget guards remain unchanged. Browser fault files are absent.
All354 closed browser artifacts/8,672,175bytes were recovered and fully SHA-verified. Chrome and Node driver are absent by process identity inventory; HTTP34945 is closed;432 runtime pins and37 staged input hashes remain unchanged. Evidence records Git SHA, relevant binary diff and new run-input patches, with a final SHA-256 seal. Publication status is recorded in the run handoff.
bx_8g2vpazy is left RUNNING (last API idle, healthy/hydrated), expiry
2026-11-04T11:04:40.606Z. Shutdown owner and custody return to the coordinator;
11:00 shutdown checkpoint remains theirs. No lifecycle/allocation/source-box
access/local heavy browser/subworker/successor/HeroesII/deployment occurred.
The remaining gap is fresh post-Medium progression under the unchanged phase
identity, followed by separately viewed comic/cinematic if reached. This worker
stops after recovery and its own documentation commit.