MDK2 explicit finite113 route: fresh comic, elapsed guard before cancel
Run scratch/runs/20261104-mdk2-explicit-menu-scene/ reached original New Game,
Medium, and a fresh original Level 1 intro comic in one Chrome on assigned
bx_72zd7r2c. The requested cancellation and post-cancel playable scene remain
unproved: the first controller failure was the unchanged shared 540-second
deadline, before the cancellation reserved commands or submitted input.
The finite113 candidate from published 133bd82c3 was selected explicitly on
the first authorized menu call in this new namespace. Every menu consumer
resolved this tested candidate; the ledger finished at 50 commands/272 slices,
limit113, with open, newgame, and medium true. No ledger reset, upgrade,
or edit occurred. Corrected staging follows 2488b55b1; only small direct run
helpers were staged, including an explicitly tested cache checker with explicit
historical runtime paths. No runtime module transfer was necessary.
Native route and first failure
Every latest phase capture was personally inspected before the dependent phase.
Startup reached the original legal/title at step3072. The original title Escape
was balanced, but its opening-consumption witness is not claimed. Native readiness
first became visible at step3184 (native-selector-73); it was classified ready,
then New Game at3248 showed the Medium-highlighted original difficulty dialog.
Medium completed at3296, followed by original fading and construction. No stale
opening classification was used after New Game readiness.
Construction used 16 inspected quanta, 688 slices/48 commands, starting
08:44:29.261Z. The original loading cover then required 20 inspected quanta,
10,240 slices/200 commands. At08:52:04.927Z, step14272,
recovered/browser/comic-control-343.png shows Kurt holding a mop in the original
comic. Personally viewed full PNG SHA-256:
85dcfe9e7723243ec12d1697ceb4c86405282d1cf912f095ac7382b0aa097532.
Native resource completion was1 with queue0/active0 and11,352,133 completed bytes;
those counters are not a gameplay claim. COM_PAUSE was at rest, raw/previous/
active/phase0; the original movie target remained present.
The shared elapsed deadline was08:53:29.261Z. The inspected cancellation request
reached the controller at08:54:31Z, after an excessive operator delay between the
comic capture and request. It failed with
AssertionError [ERR_ASSERTION]: aggregate continuation deadline at
comic-control.cjs:54, before reservation or its first state command. The failure
latched. No cancellation Escape, press edge, release witness, callback-completion
claim, or post-cancel state/step/shot occurred. No retry, reload, second browser,
forced scene, Lua, guest write, or guessed input followed. The next and final
command was quit. This is an elapsed guard result, not a game crash or a defect
in the finite menu budget. A subsequent authorized run needs prompt personal
inspection/continuation within the existing deadline; this task does not change it.
Tests and identity
Preparation Git HEAD was 7cc7c5767600cba80c60f7b6c5d161ccfa076eaa;
local-head.txt and empty relevant.diff record relevant local source state.
Historical tested runtime source is
1329b1ba6eb00144ff77d4cd92a8513d4fc953ad. All432 existing runtime/media pins
were checked before Chrome and again after closure. Media and modules remain at
their recorded existing paths in runtime-pins.json; no copies or source
archives were made. Canonical wasm SHA-256 is
cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee;
compat is 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.
All30 staged helper inputs remained byte-identical after closure.
Before Chrome: finite candidate90/90, predecessor177/177, and predecessor177/177
redirected to the actual candidate passed sequentially. Local staging3/3,
process-identity tests, cache-checker self-test, real runtime CJS and ESM imports
of Puppeteer24.31.0, historical cache graph98page/12worker, registered MDK2/WebGL
selectors, HTTP module fullSHA and isolation checks passed. The runtime's absent
tools/ directory was handled by a small explicit checker, not a source-tree copy.
The first runtime offline suite exposed missing historical fixtures, not a game
error: actual failed-title capture, original source decoder/PE/archive/script
fixtures, and the recovered304-slice/57-command ledger are unavailable there;
these cases passed locally. The applicable unchanged runtime suite had one modeled
ACK timeout in its150ms fixture; that failure is retained. Sequential unchanged
rerun passed206/206 (recovered/preflight-tests-final.tap) before Chrome. No
controller readiness, callback, inspection, release, ACK, fault, slice or elapsed
guard was weakened. One initial shell JSON-quoting error occurred before the first
browser command; no command/ledger was submitted by it. Two local image lookups
used absent filenames and were corrected before progression.
Offline analyze.py verifies all354 command ACKs, contiguous command numbers,
238 step commands totaling14,272 slices, maximum64 per command, all53 capture
hashes via the closed inventory, balanced title Escape/NewGame Enter/Medium Enter
and no comic Escape, unchanged unreserved comic ledger, failure-before-send source
order, and all200 served-file hashes. No driver first-failure/bootstrap latch
exists; the comic controller's elapsed latch is the first runtime boundary.
Closure and custody
Chrome151.0.7922.108 PID10626 closed normally, exit0/no signal, at
08:54:44.977Z, within the original15-minute bound ending08:54:45.369Z and hard
09:05Z close. Driver10614 is absent; HTTP40439 is closed; no browser identities
remain. cleanup.json, postclose.json, and validation.json retain checks.
Unique closed evidence:1,133 files,26,176,902 bytes, each recovered and checked
against full SHA-256 by08:55Z, before09:10Z. closed-inventory.json includes
commands, ACKs, PNGs, reviews, native observations and the exact failure. Small
owned input patches and this note's patch accompany exact Git provenance;
seal.json inventories stable local evidence. No media/module/source archive.
Runtime bx_72zd7r2c was left RUNNING (API idle, healthy/hydrated), expiry
2026-11-04T09:15:18.658Z, shutdownOwner coordinator. Ownership is returned;
no lifecycle action, source-box access, allocation, deployment or successor was
performed. Single task stops with the exact first failure preserved.