MDK2 prompt fresh-comic cancel: positive press exposes helper phase defect

Run scratch/runs/20261104-mdk2-prompt-comic-cancel/ reached original New Game, Medium, and a fresh original Level 1 intro comic on assigned bx_qgpbrx29. Cancellation was submitted promptly after personal inspection, within the unchanged 540-second aggregate deadline. The first failure was the retained helper's empty-native-input-list assertion during its positive press sample. No completed cancel/release witness, post-cancel scene, playable readiness, movement, or fire is claimed. The sole browser closed normally; a narrowly scoped repair is tested offline and retained for a separately authorized fresh run.

Live route and exact first boundary

Predecessor 75f88bf3eb39462c08305311cec0441ead6d141c documented an operator delay after its comic capture. This run does not reproduce that elapsed failure. All commands, capture paths, review schemas, and dependent continuation commands were prepared before Chrome. Each of the 54 fresh captures was personally viewed before its dependent continuation. Review metadata uses the new capture's own SHA, step, namespace, session, and ACK barrier; no historical pixels were used.

The explicit finite113 allowance was selected on the first menu command. Every consumer resolved the staged tested candidate. Menu ledger finished at 51 commands/272 slices, commandLimit113, open/newgame/medium true. Startup reached the original legal title at step3072. Balanced title Escape led through inspected opening animation. At3184 the controls were visible but the New Game label was not readable; another input-free16-slice observation showed highlighted New Game at3200. Original New Game led to Medium-highlighted difficulty at3248; Medium finished at3296. No selection was inferred from stale title pixels.

Original construction began at3344, aggregate anchor09:08:43.091Z. Its first15 reviewed quanta reached the Hectic loading cover at4016. Eighteen loading quanta reached13232, where the cover cleared to black. Native state still identified original Level1/checkpoint9, game/game schemes and resource work, so three more separately reviewed construction quanta used the unchanged construction helper. Both ledgers retained the same original start; no reset or allowance change. Construction totals:18 quanta/864 slices/54 reserved commands. Loading totals: 18 quanta/9216 slices/180 commands before the single cancel reservation.

At09:14:33.172Z the fresh capture recovered/browser/comic-control-337.png, step13424, shows the original MDK2 intro comic cover, distinct from the Hectic loading cover. Personally inspected full SHA-256: 824c302e68cf2148e20ede1bbb8ab04b2353035885f3b93c5fc3182c461d742a. Native game scheme was applied, movie target present, original IntroMovieADone and pause-handler identities present, COM_PAUSE at rest, renderer input empty, native list empty. Resource completion1/queue0/active0 and11,352,133 completed bytes were observations, not playable readiness.

The cancellation controller was requested at09:14:42.561Z:9.389 seconds after the capture command,359.470 seconds after the shared anchor,180.530 seconds before deadline09:17:43.091Z. It reserved its unchanged eight-command/48-slice envelope once. Actual acknowledged commands340–344 were state-before, tick20, trusted screen Escape-down, step16, state-press. At13440, COM_PAUSE raw/previous/ active were1/1/1, phase4; native list contained exactly {count:1,entries:[{binding:1,value:1,extra:0}]}. Renderer queue was empty, activeInput null. The original movie target changed from139514944 to139482944; natural script progression also changes targets, so causality and Done execution remain unproved.

movie-boundary.cjs:11 rejected the positive press with native input not drained, through pressed at comic-control.cjs:102. The first-error latch is retained. Comic ledger reserves9264 slices/188 commands, loadingQuanta18, skipAttempted true, no cancelWitness; only the first16 cancel slices executed. The next and final command345 was quit. No scripted Escape-up,32-slice release, postcancel step/shot, retry, reload, second browser, guessed gameplay input, Lua, or guest write followed. Browser shutdown released held host keys before closure; that is not a sampled native release witness. This is a controller assertion, not a game crash or budget/deadline defect.

Offline repair and verification

The live-tested movie-boundary.cjs remains byte-identical. Its generic sample requires an empty native list even when pressed() is inspecting the currently active COM_PAUSE edge. The retained actual snapshot reproduces that rejection. movie-boundary-repaired.cjs is a separate offline candidate: positive press may contain exactly one matching binding/raw-value/extra0 entry, with active1 and phase equal to the original fall4. Unknown/additional entries still reject. Before/rest, post observation, and final release continue to require an empty native list. Native record/callback identity, source/module, ownership/ACK, inspection, release, fault, readiness, step/command/time guards are unchanged. No production source was changed; no claim is made that a repaired live release or post-cancel scene would pass.

test-actual-press-repair.cjs:12/12 tests, including actual old failure/fixed press, unchanged rest/before rejection, mutation-free reads and ten negative identity/list cases. repaired-suite.cjs redirects only the offline module cache to the candidate; the actual retained controller/driver's modeled post-comic suite passes50/50, including release failure, ACK, partial execution, repeated skip, deadline/cap, callback/record and resource guard cases. The repair and tests are ignored run inputs, not a production code commit; no full-build result is claimed for this documentation-only publication.

Before Chrome, sequential candidate90/90, predecessor177/177, redirected actual candidate177/177 passed locally; runtime-applicable suite206/206 passed on the assigned box. Staging3/3 and process-identity checks passed. Actual Puppeteer 24.31.0 CJS/ESM imports, cache graph98page/12worker, registered MDK2/WebGL selector, HTTP isolation/full module SHA and all432 retained runtime/media pins passed. Only32 small inputs were staged; no existing modules or media were recopied. One local preflight Python missing-import error occurred before Chrome and was corrected; one early local image lookup was retried after its download completed. Neither submitted gameplay or reset any ledger.

analyze-run.py verifies all346 contiguous successful command ACKs,225 step commands/13,440 actual slices/max64,54 captures and matching reviews, exact input history, conserved ledgers, failure-before-release, all200 served-file hashes, and closed inventory fullSHA. Relevant local preparation SHA: 7dbf713d61ae53d78bdfded14806e402d47c7860; relevant.diff is empty. Historical runtime source remains 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, canonical wasm cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, compat 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. Exact Git identity, relevant binary diff, owned small-input/note patches, pins, logs, tests and a final artifact seal retain provenance without source archives.

Closure, custody, and next boundary

Chrome151.0.7922.108 PID11161 ran09:05:21.015–09:14:52.096Z, normal exit0/no signal, before its15-minute deadline09:20:21.014Z and hard09:30Z close. Driver11149 absent, no browser identities, HTTP42769 closed. All432 runtime/media pins and30 staged JavaScript inputs remained unchanged. Unique closed evidence: 1110 files/25,254,452 bytes, fully recovered and SHA-checked by09:15:14Z, before 09:35Z. cleanup.json, postclose.json, closed-inventory.json, recovery and validation records retain the checks.

bx_qgpbrx29 is left RUNNING (API idle, healthy/hydrated), expiry 2026-11-04T09:40:33.748Z; shutdownOwner coordinator, custody returned. No allocate/resume/stop/delete, source-box access, local Chrome/heavy runtime, subworker/successor, HeroesII or deployment occurred. Next requires a separately authorized fresh namespace with the repaired press observer preflighted; it must still establish balanced native release, input-free postcancel scene and reviewed playable readiness before any movement/fire. This single assignment stops here.