MDK2 onward replay stops at a concrete review-author prerequisite
This assignment did not reach the new resource queue. Its single original browser
replay reached the title/legal screen at step3072, then stopped on a local review
authoring exception before Escape, New Game or Medium. The very next guest command
was quit55. Loading, comic, tutorial, playability, Lua completion, Level l1 and
the new699228-byte resource are all unobserved in this execution. Historical
completion in the predecessor remains
historical evidence; it is not relabelled as this run.
Evidence is scratch/runs/20261104-mdk2-new-resource-queue-onward/ (RUN). The
preparation Git SHA is recorded in preparation-commit.txt; execution retained
source 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, canonical module
cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee and companion
580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3.
The wrapper actually executed with the required fixed SHA
b5f85284acebec7339786c655f56929954cd8212e64bce3ff71fcc65f071e787.
Before runtime, both actual-shot positive and old-suffix negative tests passed locally and on the allocated box, along with the two read-only observer tests. The retained54 classifier/controller controls and six assignment routing controls passed. Qualification verified all432 runtime pins,30 existing media path/hash references, explicit small driver/controller dependencies, both runtime JSON companions, actual assignment RUN/OUT, Puppeteer24.31.0 CJS/ESM imports, executable, cache graph, registered selector/WebGL and isolated HTTP module hashes. No media or module was copied. These checks did not exercise the local Python review author against fixed-wrapper raw JSON sidecars.
Preparation initially invoked the wrapper test before staging read-only.cjs.
That pre-runtime MODULE_NOT_FOUND was corrected by staging the explicit dependency
first; the complete final qualification passed before Chrome. The original failed
log remains. This was not a runtime retry.
The full predecessor707-file seal verified unchanged after restoring27 exact
RGBA files from their adjacent .rgba.gz files. Every restoration matched both
the coordinator roundtrip manifest and original seal SHA/size. Compressed
originals remain; no pixels were synthesized. predecessor-raw-restoration.json
and predecessor-seal-verification.json record this check.
The coordinator's allocation record identifies only fresh bx_7xubp8u9, expiry
2026-11-04T13:19:50.637Z, hard cutoff13:07, recovery13:12 and coordinator normal
shutdown13:15. Runtime began with the entire470-second interval and recovery
fitting those bounds. Before launch, the worker narrowed closeBy to
12:50:42.723Z; that deadline was never reset or extended. Chrome151.0.7922.108
PID11051 has identity time12:42:54.047Z and closed normally at12:45:20.380Z,
elapsed146.333 seconds. The old stopped bx_5dbavbcw was never accessed or resumed.
Seven captures at steps0,512,1024,1536,2048,2560,3072 were separately personally viewed. Each saved the current logical canvas RGBA and actual owner921600 sidecar before PNG. Owner availability was false at startup0 and true thereafter; that absence is retained honestly. The title/legal image was visible at3072. Earlier black captures establish no gameplay. No menu/comic/game input was sent; the observer's only input events are the original balanced browser Launch click, unchanged from startup0 to final. No continuation ledger was created, reset or extended because menu continuation never began.
The first unexpected operational failure after launch was local author.py:
its hash-only JSON discovery accepted startup-3072-raw.json as a capture because
raw metadata also has sha256, then its maximum-step lookup raised
KeyError: state. The shell subsequently invoked next.py open, which found no
authored review and stopped before submitting any guest command. After the last
capture54, quit55 was the next guest command; all56 ACKs succeeded. There was
no guest fault, helper route rejection, lost execution credit or loader stall
demonstrated. Owner PC/decode activity at the target queue cannot be inferred
from startup evidence because that queue was never reached.
The same worker repaired only the ignored run-owned author offline. It now takes
an explicit personally viewed capture name, reads exactly that capture record,
requires its state/step fields and verifies its PNG hash. It does not discover
captures through extension globs or a shared sha256 field. Existing templates,
native gates, inspection approval and input preflight remain intact. Five
offline regression tests pass against the actual recovered3072 capture: correct
explicit selection beside real sidecars, reproduction of the old failure,
sidecar rejection, altered-PNG rejection, and missing/path-traversal rejection.
The repaired author was not used for further guest progression.
Recovery verifies all225 closed inventoried files /11475069 bytes with full hash/size comparisons and an identical second remote inventory. Focused checks pass all56 sequential ACKs, exact step requests,200 served-file hashes, cache-disabled isolated HTTP, seven raw/PNG pairs, fixed-wrapper identity, unchanged input history, normal close before the original deadline, and absent owned PIDs/HTTP listener. All unique captures/logs were recovered; the standard inventory excludes Chrome's disposable profile. Recovery and custody return completed before12:48. Box API was idle/healthy/hydrated; it is left RUNNING, with shutdown ownership returned to the coordinator via messageboard. No stop, resume, delete, second Chrome, reload, guest write/call, forced callback, repaint, fault clear, speculative emulator change, local heavy runtime, subworker or deployment occurred.
Only this note is committed. Git SHA, relevant binary diff and owned small input
patches preserve provenance; evidence stays ignored. No source archives or
module/media copies were made. No production code changed, so no full build is
claimed. The next recipe requires a separately authorized fresh allocation:
qualify this explicit author with real sidecars before launch, use
author.py open startup-3072 only after viewing that execution's actual capture,
then retain all existing ordinary-input, cumulative ledger and deadline controls.
After separately viewed New Game/Medium, observe input-free Lua completion with
192320 delta/active clear, Level l1, then the new699228-byte request and105 queue.
This assignment stops after publication of the concrete prerequisite and fix.