Stronghold repaired entry original gameplay, 2026-11-04

Input: 8cb8d986d60dac7a2609f48e2b7de538ef4298a9 and the fresh composed-entry handoff. Evidence: scratch/runs/20261104-stronghold-repaired-entry-original-gameplay/.

The game launched once and displayed its original loading artwork. The first post-Chrome fault was an operator startup script error, before title controls: two observation commands omitted their capture names. CustomGame, setup, preset, Start, world and gameplay remain unverified. No second Chrome/game attempt was made.

The local runtime contract now binds this assignment and requires an explicit mdk2-measured-native LOCAL HEAVY RELEASE for the measured native boundary gameplay task. Foreign actors, old installed-original MDK and GL releases, pre-task timestamps, future timestamps and quoted release rows reject. The long-lived external /tmp/wine-local-runtime.lock remains mandatory in the actual composed entry. No synthetic offline release authorizes Chrome.

Before any Chrome, the actual composed fresh-directory main executes through 2,429 filesystem pins, run-bound process release validation, private ancestor flock validation, real filesystem writes, lifecycle installation and HTTP server creation. An explicit plain Puppeteer mock binding throws one sentinel at the real launch wrapper. An independent child-spawn trap observes zero attempts; there are zero Chrome children. The real server closes. The immutable ESM namespace regression remains; no namespace export is replaced by a mock.

The focused local-runtime tests pass with 38 process-contract negatives and the release-dependency negatives. The full flocked build and 1,016 HTTP content/isolation/cache checks pass. Both accepted modules and all 92 prior fresh-entry and 89 render-observer sealed artifacts are unchanged. Accepted render parity is reused without repeating historical qualification.

The fixed 50M/360s continuous native observer, byte/record/nesting/input/owner/ ACK guards, original 16ms pacing and 720/60/40/180-second runtime/bootstrap/ command/cleanup limits remain. Absolute runtime and cleanup cutoffs remain 23:50Z and 23:53Z. No guest code, configuration or pacing writes were made.

Original outcome and first fault

The real MDK release at 21:32:51Z preceded the sole Chrome process, started at 21:33:47Z under the external runtime flock. The registered Stronghold Crusader Multiplayer Demo selector was personally viewed before Launch. The fresh 256-step black startup window and retained 4,352-step loading artwork were personally viewed. The original title dialog was not reached or reviewed.

Commands 0 and 2 observed startup with unique names; command 1 captured the fresh startup window. An ad hoc startup batch then omitted name. Command 3 advanced to step 4,352 and saved undefined.png. Command 4 advanced another 2,048 steps to 6,400, then the existing fresh-capture guard rejected the reused filename at 21:34:53Z. This is an operator command defect, not evidence of an emulator or game fault. The first failure was preserved and normal closure began immediately. There were no title/game controls or manufactured scenes.

All 100 ordinary 64-step transport ACKs are retained with their actual guest results. They report tickMs 16, requested/ran 64 and running true; their EIP field is 0x00000000, which does not establish a useful guest PC. The owning native callback observer was preloaded but never activated by a route gesture. There is no native callback history or CustomGame callback claim. Final host queue empty/active null is not guest callback proof.

Offline repair and cleanup

The local helper now validates observation and shot capture names before execution, requiring an explicit string, the existing safe name syntax, and an unused PNG path. The mailbox preflight accepts the proposed command and applies the same validation before enqueueing. The run-specific client passes its command to that preflight. No invalid command is silently renamed.

An offline regression replays actual command 4 through the composed observation loop. The old branch performs 2,048 steps before capture failure. Missing, nonstring, unsafe and duplicate names now reject with zero steps and zero captures; the client preflight leaves the command directory empty. The final full-manifest composed mock again checks 2,429 pins and reaches one sentinel with zero Chrome/spawn attempts. Focused tests and the full flocked build pass. The actual runtime manifest, composition and launch patch remain separate from the repaired offline manifest and final patch.

Chrome PID 1199114, start ticks 187523680, exited normally via CDP Browser.close with code 0/signal null at 21:34:53Z. Node 1199086, start 187523617, external flock 1198977 and wrapper 1198986, start 187523219, are absent; the wrapper recorded exit 0. Actual HTTP 44255, DevTools 34141 and prelaunch mock 38353 refuse connections. The exact owned profile was removed after confirming no process used it. The external flock was verified available. LOCAL HEAVY RELEASE was posted at 21:35:31Z for GL's successor. An assignment-bound release repeating those same verified facts was appended at 21:38:40Z to satisfy GL's stricter handoff parser; no new runtime occurred.

Git recovery records the exact tested commit plus relevant binary diff and this new note's patch. Existing media/modules are referenced by path and SHA; no snapshots, tars, source trees or media/module copies were made. Prior evidence is unchanged. Box ID/state/expiry are NA; the coordinator owns shutdown. The next step requires a separately authorized original attempt with explicit unique observation names; this assignment makes no gameplay claim and stops after publishing the tested repair.