Fresh original MDK2 attempt with isolated Python hooks

This assignment consumes published 95283746f8aef765c9bd8533323b0e0c3d91c098 and its tested isolated python-hooks/ transport. Evidence is in scratch/runs/20261104-mdk2-repaired-python-original/ (RUN).

The exact dedicated-process command was prepared first in RUN/launch-command.sh and RUN/launch.cjs: acquire the inherited exclusive local runtime lock, create the immutable resolver, install its verified adapter, install the explicit local release, then call unchanged accepted 6d5121b5 run(freshRun).

The owner explicitly renewed this assignment's absolute Chrome cutoff to 18:25Z and cleanup cutoff to 18:28Z. The only production change renews these dated constants. Release creation still requires the full 360+180 seconds before the Chrome cutoff, with at most360 browser seconds and180 cleanup seconds. Real hostname, boot ID, PID/start ticks and canonical fresh run bind the local release. Original endpoint/Worker identity, module hashes, capture session hashes, current inspection approvals, ACKs, input limits, command and aggregate deadlines, first-error latch and16-slice construction trace remain in the unchanged accepted composition. No fabricated box identity is used.

The original111 helpers, observer de6a33f, four Git dependencies, original432 filesystem/full HTTP checks and retained cffc/580f modules stay immutable. No current build output substitutes for those modules. GitSHA plus relevant binary diff records the tested source; media/modules remain existing path/SHA references. No source snapshot, archive or media/module copy is made.

Before Chrome, the focused suite executes the actual original control.py child with PYTHONPATH pointing only to isolated python-hooks/, and executes the actual run-local bootstrap. Both succeed using bounded local transport. The offline negative reproduces the historical stdlib-shadow failure without entering any browser/controller sequence. The live attempt consumes only the repaired transport. All21 focused tests and51 original integration regressions pass; the required locked full build passes. Regression fixture decoding uses the predecessor's sealed in-memory gzip-only fixture preload.

Stronghold-title-recognition-onward has priority for the first local runtime turn. This worker waits for its explicit release before taking the sole local runtime lock; the queued GL worker uses the same lock if needed. No overlap, allocation, boat/API, box SSH, dependency installation or subworker is used.

Observed result and first concrete blocker

Stronghold explicitly released its first turn at17:39:55Z. The prepared command then acquired the exclusive lock once. Actual attempted main was 9800e74b3105d2be4ced4720f315ad53aedf092a, plus the recorded two-file renewal patch and new investigation note. The accepted432 filesystem/full HTTP checks, original111 helpers and endpoint preflight passed before Chrome151 launched. The local release belongs to real NodePID830130/start ticks186126057, issued 17:40:53.154Z, closeBy17:46:53.154Z, recoverBy17:49:53.154Z. ChromePID830408 reported ready at17:41:09Z on loopback37377. Original retained module cffca869…bcee was compiled/transferred/instantiated in the owning Worker.

The repaired transport successfully ran the original author/operator/next/control chain. Every dependent capture was personally viewed first. Startup captures show teal desktop0, gray512/1024 and black1536/2048/2560. Step3072 shows the true MDK2 logo/legal title. The original measured Escape route positively samples native consumption, then releases Escape. Separately viewed opening captures show legal fading and menu artwork. Step3216 shows readable New Game and a red controller highlight; the original native preflight precedes one balanced Enter. Step3264 shows Select Difficulty with orange Medium; a separate personal review and native preflight precede one balanced Enter. Steps3312/3328 show fading artwork,3344 black with red version,3360 black with faint version. No other game input was submitted and no gameplay, comic or tutorial was visible.

At3360 the unchanged native classifier reports level-destruction-construction: Level is absent, both schemes are game, levelnumber/checkpoint remain0, activeResource/resourceQueue0. The recorded prior resource request is6206912, completion1/completedBytes982692; its raw words describe an11100-byte request, not the desired192320-byte level1 request. These are distinct observations; they do not establish level1 Lua completion or a new Level table.

The first construction observation failed before its16-slice quantum. Command109 returned foreign main ownership from accepted frozenOwnership(). It rejects when the first owner row lacks slot0 or thread1. The earlier actual main sidecar and terminal owning-Worker report both show thread1; the failed barrier did not persist its rows, so the exact failing row value is unknown. No ownership guard was changed. No trace was started and no construction slice was executed. All109 earlier commands have successful matching ACKs; the final frozen count remains3360. The construction ledger reserves a quantum before submission and must not be mistaken for execution evidence.

The worker stopped immediately. The original quit helper itself rejects the failed ACK109 before submitting quit; no alternate controller or bypass was used. The unchanged finite timer closed Chrome normally at17:46:53.655Z (501ms after closeBy), exit0/signal null. Node exited0, both PIDs are absent, HTTP37377 refuses connections, and the local lock was available at17:47:08Z. The original cleanup reason retains its legacy fifteen minute browser bound wording, although this release lasts360seconds. Its boxLeftRunning:true is also a legacy original field, not an allocation claim. Own closed Chrome profile was removed. Unique raw captures are losslessly gzip-compressed with decoded hash/size and recovery instructions; all PNGs/logs remain sealed in RUN.

Next: offline diagnosis of the accepted ownership barrier against the actual main endpoint wrapper, with its checks preserved. This assignment performs no second browser attempt. Construction progress, level1 completion, Level creation and gameplay remain unobserved. Box ID/state/expiry: NA. Coordinator owns future allocation and shutdown.