MDK2 repaired press: balanced native cancel and input-free 3D dialogue
Run scratch/runs/20261104-mdk2-repaired-press-cancel/ reached original New
Game/Medium, a freshly reviewed intro comic, a balanced native COM_PAUSE Escape
press/release, and four input-free observations ending in rendered 3D dialogue.
Playable readiness and movement/fire remain unproved. The single browser closed
at the newly reviewed cinematic boundary. No runtime fault or demonstrated
production defect occurred; the retained controller only permits comic-classified
postcancel observations, so further cinematic progression needs a truthful,
tested observation route. Its guards were not widened during this run.
Fresh route and balanced native witness
The predecessor is d343539adff2ce649b21a77b37dc61fa69c63210, documented in
mdk2-prompt-comic-cancel-20261104.md. This run installed its tested
movie-boundary-repaired.cjs byte-for-byte as the fresh namespace's
movie-boundary.cjs. The actual controller/driver therefore resolved the repair
directly. Positive press permits only the exact active binding/raw-value/extra0
entry; before/rest/release retain empty-list requirements. Identity, ownership,
ACK, fault, readiness and finite aggregate guards remain unchanged.
All commands, review schemas and capture paths were prepared before Chrome. The first menu command explicitly selected 113; final menu accounting was 51 commands/272 slices, New Game and Medium true. Each of 58 fresh captures was personally viewed before its dependent continuation; the final scene received a terminal review followed by quit. No historical capture was used for approval. Original legal title appeared at3072; balanced title Escape at3120 led through reviewed animation. New Game was readable at3200, Medium highlighted at3248, and Medium completed at3296. Construction began at3344. Sixteen construction quanta/688 slices/48 commands reached the Hectic loading cover at4032.
Nineteen input-free loading quanta/9728 slices reached the original MDK2 intro
comic at13760, capture recovered/browser/comic-control-334.png, SHA-256
45d940d3dd996670721d38260c05328e2d30ecd5490c5d0ebe23f513764a40c4.
The next cancel request began09:35:28.391Z, 7.343 seconds after the capture ACK,
383.336 seconds after the unchanged09:29:05.055Z aggregate anchor; the original
540-second deadline was09:38:05.055Z. No reset or allowance increase occurred.
Acknowledged commands344–351 were exactly state-before, tick20, trusted screen
Escape-down, step16, state-press, trusted screen Escape-up, step32, fresh shot.
At13776, native COM_PAUSE raw/previous/active were1/1/1, phase4, with exactly
{count:1,entries:[{binding:1,value:1,extra:0}]}. At13808, raw/previous/active
were0/0/0, phase2, native list empty, renderer queue empty and activeInput null.
Original callback and pause-record identities persisted. The conserved ledger
contains cancelWitness.nativePressThenRelease=true via its result object.
Movie target changed, but callback execution and causal attribution remain
unproved: natural ScriptUpdate also calls StopScript. This is evidence of native
input consumption and subsequent scene progression, not an isolated causal test.
Personally reviewed postcancel boundary
Four acknowledged state/step64/shot envelopes added256 input-free slices.
Captures352,355,358 and361 retain identical trusted-input history, empty renderer
and native input lists, native COM_PAUSE rest and original identities. The cover
remained at13872, then cross-faded; at14064 it had cleared to three rendered
characters and dialogue, “Come, toast, Kurt. You've done well.”
recovered/browser/comic-control-361.png SHA-256:
b6bffb41072a415e6578ecb92294f660baae2d45f831adb357ed6e23f1ae7378.
This is a visible 3D cinematic, without a reviewed playable-control boundary.
No movement, fire, second cancel, Lua or guest-memory write followed.
The concrete continuation blocker is comic-control.cjs:scene(): for
observe-post-cancel, it requires screen=opening-comic,
originalScene=level1-intro-a-comic and comicPanelsVisible=true. Those assertions
cannot truthfully describe the final capture. The worker closed instead of
misclassifying the cinematic or submitting unsupported input. An offline test
passes the accurate cinematic review to the actual retained function and confirms
its rejection. This was not submitted live, did not latch a runtime error,
and is not evidence of a game defect. No speculative production repair or full
build is claimed for this documentation-only change.
Verification and provenance
Before Chrome: candidate90/90, predecessor177/177, redirected actual candidate177/177, actual retained positive/negative press12/12 plus modeled actual-controller/driver postcomic50/50; staging3/3 and identity tests passed. Assigned-runtime applicable suite206/206 passed, actual Puppeteer24.31.0 CJS/ESM imports passed, registered MDK2/WebGL, isolated HTTP full hashes and cache graph 98 page/12 worker references passed. All432 runtime/media pins matched. Only35 small inputs were staged; existing module/media paths were referenced.
After closure, test-live-witness.cjs passed15/15 on this run's actual snapshots:
exact positive entry, empty-list release, nine invalid press cases, unchanged
before/release/post rejection of positive lists, four conserved post observations,
and truthful cinematic guard rejection. analyze-run.py verifies1170 closed
files/29,199,923 bytes,365 contiguous successful ACKs,236 step commands/14,064
actual slices/max64,58 matching personally reviewed captures, exact balanced
input history, shared ledgers, prompt cancel/deadline and all200 served hashes.
One local image lookup preceded its completed download and was retried after
completion; it submitted no command or input and was not a runtime failure.
local-head.txt, relevant.diff and owned new-input/note patches record local
preparation, including relevant pre-existing uncommitted hunks. These local
changes were not substituted for the pinned historical runtime. Runtime source
is 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad; canonical wasm
cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee, compat
580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.
seal.json retains exact artifact identities. Git is the source archive; no
source trees, media copies, scratch/docs/test-binary archives were staged.
Closure and custody
Chrome151.0.7922.108 PID9908 ran09:24:59.782–09:36:58.851Z, normal exit0/no
signal, before its15-minute deadline09:39:59.782Z and hard09:51Z close.
Driver9896 absent, browser identities absent, HTTP33349 closed. All432 pins and
34 hashed staged inputs remained unchanged. All1170 unique closed files were
recovered and SHA-checked by09:37:13.784Z, before09:56Z; exact recovery log timestamps
and recovery-result.json are retained.
bx_rsp888x8 remains RUNNING (API idle, healthy/hydrated), expiry
2026-11-04T10:01:36.010Z; shutdownOwner coordinator, custody returned.
No lifecycle/allocation/source-box access, local Chrome/heavy guest runtime,
subworker/successor, HeroesII or deployment occurred. Next boundary is a tested,
truthfully classified original cinematic observation route, then personal review
of playable readiness before movement/fire. This assignment stops here.