MDK2 explicit capture author works; personal visual classification remains required

The single original replay stopped at step3184, still showing the title/legal screen after balanced Escape. No Enter was sent. New Game, Medium, Lua completion, Level l1, the105-resource queue, loading artwork, comic, tutorial and gameplay were not reached. The concrete prerequisite is a truthful current visual review: capture identity and a matching PNG hash do not validate inherited visual claims.

Evidence is scratch/runs/20261104-mdk2-explicit-capture-native-onward/ (RUN). This follows the explicit-author repair published at9449784c6 and the input-free Lua predecessor. The earlier Lua completion and queue observations remain historical evidence.

Before Chrome, the five actual-author controls passed beside the predecessor's real raw/owner sidecars. Actual operator-to-author integration exercised all seven supported modes with explicit capture identity; legacy one-argument dispatch was rejected. The initial integration fixture had a temporary template-path error; its corrected final regression passed before launch. The executed author was byte-identical to the repaired9449784c6 author. The fixed wrapper was unchanged, SHA b5f85284acebec7339786c655f56929954cd8212e64bce3ff71fcc65f071e787.

All54 classifier/controller controls and six routing controls passed locally. Actual-shot positive, old-suffix negative and both read-only observer controls passed locally and remotely. An attempted remote54-control rerun found its historical test file absent; the remote combined test had only reported the four available shot/observer tests. This is retained explicitly, rather than claiming remote54 coverage. The complete local54 suite passed before Chrome.

Remote qualification verified432 runtime pins,30 existing media paths and hashes, explicit small dependencies and runtime JSON, actual assignment RUN/OUT, Puppeteer24.31.0 CJS/ESM imports, executable permission, cache graph, registered MDK2/WebGL selection and isolated HTTP module hashes. Execution source remained 1329b1ba6eb00144ff77d4cd92a8513d4fc953ad, canonical module cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee and companion 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. Only small inputs were staged; modules and media were referenced in place.

The coordinator appended fresh allocation bx_n9wn7srk before dispatch, expiry 13:43:13.046Z, guest cutoff13:30, recovery13:35 and coordinator shutdown13:39. Hydration was verified before launch. The470-second interval and recovery fit those bounds; the worker narrowed closeBy once to13:14:12.949Z and never extended it. Chrome151.0.7922.108 PID15760 identity time13:06:24.588Z closed normally at 13:09:39.444Z, elapsed194.856 seconds. There was no second Chrome or reload.

Twelve captures were personally viewed separately at steps0,512,1024,1536,2048, 2560,3072,3120,3136,3152,3168,3184. Each retained current logical canvas RGBA and the actual owner921600 sidecar before PNG. Startup0 has no available owner; later owner PC/register/stack/wait/yield/scheduler records remain in the evidence. The developer logo appeared at2048, black at2560 and title/legal at3072. After the original balanced Escape, the PNG remained title/legal through3184. Native state at3184 was freeze1, scheme title, current lang, no Level/resource queue. This is not loading, comic, tutorial or playable evidence, nor evidence of a pending resource decode stall.

The author correctly bound every invoked mode to its explicit viewed capture and PNG hash. Its historical opening template nevertheless asserted openingAnimationVisible:true and transitioning:true without independently authored current visual classification. The worker used that unsupported claim for four16-slice observation groups at3120–3168, recognizing the inconsistency at3184. Those reviews are retained as an operator error, not valid animation evidence. Recognition stopped progression: final shot75 was immediately followed by quit76. All77 sequential ACKs succeeded. No New Game or Medium review/press occurred. The menu ledger remains112 slices/21 commands, open true, newgame and medium false; no counter or deadline was reset.

The same worker repaired only ignored run helpers offline. author.py and the main operator.py now require MODE, explicit capture identity and a separate current personal-review JSON. The author verifies that review's capture, PNG hash, step, personal-inspection declaration, inspector, screen, selection and mode. It consults no historical visual template. Tests exercise the actual operator and actual author across all seven modes, reject missing personal review for every mode, and reject stale identity/hash/step, absent inspection, blank inspector/screen and wrong mode. The original five author controls still pass. Executed helpers and the narrow repair patches remain distinct. This repair has not been used for further runtime progression.

Recovery verifies all315 closed files /21498556 bytes with full size/SHA checks and an identical second remote inventory. Focused checks pass all77 ACKs, exact step counts,200 served-file hashes, cache-disabled isolated HTTP,12 PNG/raw pairs, fixed-wrapper identity, balanced Escape, drained input and normal close before the original deadline. Owned processes are closed and Chrome is absent. Custody returned at13:11:49: box API idle/healthy/hydrated, left RUNNING, expiry 13:43:13.046Z; the coordinator owns shutdown13:39. No lifecycle operation, guest call/write, forced callback, repaint, fault clear, emulator repair, local heavy runtime, other box, subworker or deployment occurred.

Only this note is committed. Preparation Git SHA, relevant binary diff and owned small-file patches preserve provenance; no source archive or media/module copies were made. No production code changed and no full build is claimed. The next recipe is offline personal-review authoring first, then a separately authorized fresh replay: inspect each capture, supply its actual visual classification, use ordinary title observation while title/legal remains, and press Enter only after separately viewed New Game and Medium highlights. Preserve all existing native gates, cumulative ledgers and absolute deadlines. This task stops after publication of the prerequisite and tested helper repair.