MDK2 original entry with an explicit finite local contract

This assignment consumes published immutable resolver da862db13 and the sole accepted construction entry 6d5121b5. It authorizes one fresh local original attempt, with personal inspection before dependent input. Evidence is in scratch/runs/20261104-mdk2-portable-original-runtime/ (RUN).

tools/mdk2-local-runtime.cjs adds an explicit local-process-v1 release. The release records the real hostname, Linux boot ID, process PID and start ticks, canonical checkout and exact fresh run directory. boxId and allocation expiry are null. It requires the original authorization and assignment plus the explicit local authorization and coordinator shutdown owner. A real, inherited exclusive /tmp/wine-local-runtime.lock descriptor is mandatory.

The local release permits at most 360 seconds from issuance and preserves the original three-minute useful-window admission and three-minute cleanup reserve. Chrome must close by 17:55Z, cleanup by 17:58Z. Creation requires 360+180 seconds before the Chrome cutoff; no late launch or allowance extension is possible. The original 15-minute ceiling remains a ceiling, with the smaller local bound winning. Original command and aggregate deadlines remain byte-for-byte intact.

The accepted entry, 111 retained helpers, observer de6a33f, four original Git dependencies, original432 manifest and retained cffc/580f modules remain unchanged. The resolver supplies and checks actual original filesystem and HTTP bytes. Neither its pin checks nor the original checks are replaced with reported success. No media, modules or source snapshots are copied.

The adapter wraps the retained main-state.sourceForRun composition seam in memory. Exactly two unique source anchors change: the obsolete box-TTL guard becomes the explicit real local-contract check, and Chrome's executable path becomes the existing /opt/google/chrome/chrome. A reverse-equality test proves all other composed source bytes are unchanged. The retained finite-deadline module export dispatches explicitly local releases to the local validator; ordinary box releases retain their original validator. No source file in the retained closure or accepted entry is edited.

The command was prepared first in RUN/launch.cjs. It runs in a dedicated Node process under the local flock, calling createResolver(), installAdapter(), local install(freshRun) and then the unchanged accepted run(freshRun). The resolver and local seams live until the original driver's terminal cleanup has closed its server and the dedicated process exits. The original browser directory guard still enforces one launch. The original measured Escape chain, review/approval/ACK/session checks, input bounds, first-error latch, original construction quantum and 16-slice trace cap remain intact.

The original Python author → operator → next → control files are generated by the accepted entry. A run-local import bootstrap supplies a local runtime_io transport to those unchanged files and their child processes. It checks the release's actual live host/process identity before each operation, executes bounded local subprocesses, and copies only named small captures/reviews within this run. No boat, SSH, API, allocation or closed-box access is available through that transport. Personal review files must be written only after viewing fresh captures; transport identity never establishes visual classification.

Stronghold owns dependency installation and the first local heavy runtime slot. Its 17:16:16Z CJS/ESM-ready acknowledgement was observed and both actual imports were verified. MDK2 performs no npm operation and must wait for Stronghold's explicit slot release before acquiring the lock and launching Chrome.

Fresh original attempt and first failure

Stronghold released its slot at 17:24:17Z. MDK2 acquired the exclusive local lock and ran the prepared command once. The fresh release was issued at 17:25:40.918Z to real Node PID 808638, with closeBy 17:31:40.918Z and recoverBy 17:34:40.918Z. The accepted entry's actual filesystem loop and composed driver's actual loop passed; the adapter independently checked all432 filesystem bodies and all432 HTTP bodies. The actual original endpoint preflight passed its four HTTP bodies before Chrome. The original driver reported ready using Chrome 151.0.7922.108, PID 809290, port 43053 and the original runtime pins.

The first original controller child failed before submitting any command. The initial local Python bootstrap put the run root on PYTHONPATH to load its transport hook. At child interpreter startup, generated original operator.py shadowed Python's standard-library operator, causing the concrete circular import error for or_/eq. RUN/initial-control.log preserves the full error. No startup step, Escape, New Game, Medium, construction or gameplay command was submitted. No controller or native assertion was relaxed and no runtime retry was performed.

After this failure, only the original ACK helper's terminal shot and quit commands were used. I personally inspected the fresh browser/terminal-control-fault.png: the teal emulator desktop and MDK2 data-loading/DLLs-ready log were visible, with FROZEN step0. There was no guest title/menu/gameplay image to classify. The capture's PNG hash, actual state and personal review are retained; the review grants no input or progression. This is a fresh bootstrap observation, not evidence of construction progress.

Normal Chrome closure occurred at 17:26:36.995Z: exit0, signal null. The original Node process exited0. Both PIDs are absent, no Chrome process uses the owned profile, and connecting to the owned server port returns ECONNREFUSED. The local flock was released and reported on the board. The legacy original cleanup field boxLeftRunning:true is preserved as an original field; no allocation exists. The supplemental local closure record explicitly reports box ID/state/expiry NA. Coordinator retains future allocation/shutdown ownership.

Tested repair and evidence

The same worker fixed the local Python transport after closing the attempt. Child PYTHONPATH now names a dedicated python-hooks/ directory containing only sitecustomize.py; it never names the run root containing operator.py. The direct bootstrap also removes its script directory from the import search path before other imports. The accepted-generated author/operator/next/control files remain unchanged. A new test reproduces the actual original child's startup failure with the old search path, then executes the actual original control.py with the isolated hook and real local transport successfully. It also exercises the run-local bootstrap. No browser or game is involved in this repair test. The repaired transport has not been retried in a live attempt.

All20 focused tests pass, including real identity and subprocess controls, foreign identity/authorization/run/deadline rejection, unchanged composed-source reverse equality, missing-lock rejection and the Python-child negative/positive. All51 original integration regressions pass. The first direct regression run reported11 missing gzip-only fixture failures; RUN/regression-preload.cjs decodes only the two retained missing JSON inputs in memory, after which the unchanged suite passes51/51. The original suite verifies the retained inventory/body hashes. The required locked build passed again after the transport repair.

RUN records the exact attempted Git SHA and relevant binary diff, with the three attempted new-file patches. Final patches and final Git context are separate, so the actual failed invocation can be recovered independently of the tested repair. It retains small SHA-sealed logs/captures and module/media path references, with no source snapshots, archives or module/media copies.

Next: a separately authorized fresh original attempt may consume the tested transport repair and unchanged accepted entry. Construction, native completion, Level creation, Lua and gameplay remain unobserved by this assignment.