Stronghold first-script cause onward, 2026-11-04

The one authorized original passed startup, completed both title-enter reviews and their successful ACK, reached the personally viewed Custom Game hover, then stopped while draining Custom Game DOWN on the observer's boundary cap. No setup, preset, Start, world gameplay or hostile engagement was reached. There was no second original.

This assignment follows d26dfce997a6219e19bcb74b542af98e3f817b1b and the unique-owner handoff. Evidence is scratch/runs/20261104-stronghold-first-script-cause-onward/. The predecessor's rejected first-script subcause remains unknown; its raw pause, script and execution-context values were not recorded.

Offline prerequisites

The actual attached-driver composition compiles with its 30 retained helpers and invokes the rejected-value diagnostic helper before preload evaluation. Six fixtures reject missing context, foreign script URL, wrong pause reason, missing frame, unparsed top-frame script and expired deadline, retaining the rejected values without evaluating or resuming the script. These fixtures do not reconstruct the predecessor's missing live values.

The actual command client passes both title-review boundaries and rejects advancement after either receipt until a successful command ACK. All 37 local contract negatives pass. The assignment binding rejects the preceding startup assignment; Chrome/cleanup absolute cutoffs are 23:50Z/23:53Z, preserving the 720-second browser, 60-second bootstrap, 40-second command and full 180-second cleanup reserve. Host/boot/PID-start, candidate, manifest, run and nonce remain bound. No scene, freshness, ownership, input or first-fault check is relaxed.

Both modules pass executable pre-instantiation owning getters, rejected-init paths and callback/branch/scene/setup fixture parity. The recorded four-Worker, six-send topology passes exact slot-0/endpoint-1/thread-1 selection and all nine before-arm negatives. Recognition and input checks cover title/menu/ChooseType, 26 historical routes, 20 before-input gates, ten post-move/freshness cases, four dependent-gesture cases, 27 hover cases, four opacity cases and 22 shell negatives. The locked full build passes. Offline fixtures are not gameplay.

All 418 sealed predecessor artifacts (10,296,719 bytes) and all 523 artifacts from the preceding menu attempt (33,265,087 bytes) match their seals. Source evidence uses Git SHA plus relevant binary patches, with media and modules referenced at their existing paths and hashes rather than copied.

Original result

The runtime started after fresh MDK's 20:10:41Z release and GLTron's explicit 20:16:15Z release, under /tmp/wine-local-runtime.lock. The candidate is 86dc176a3b25a1eda252d1f4b83a1e30a8bb417b plus the relevant prelaunch binary patch. All 2,429 filesystem pins, including 1,856 original media files, 164 full-body HTTP preflight responses and 1,038 served responses matched. Original EXE SHA-256 remains 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f at test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe. Normal/compatibility module hashes remain 78a0b1d61b23428a1ae909d739440ae0de059bbbd84a69a2ad3e4c37471ad664 and 99b579cd17b57f94145df92ae6d28110f24fc284d13a1b2c0ebe3596bd10a77f.

All six attached Workers passed the exact instrumentation-pause, parsed top-frame script, exact Worker URL, positive execution-context and live-deadline checks. Each used execution context 1. This successful attempt does not recover the preceding attempt's unknown rejected values.

I personally viewed the registered selector and startup captures at 256, 2304, 4352, 6400 and 7424 steps. Command 5 requested the title-dialog review at 20:17:56.504Z and the resulting main-menu review at 20:18:05.922Z. Both fresh captures were personally viewed before their exact receipts. The command ACKed at 20:18:17.356Z, before its 20:18:34.901Z deadline. Command 6 was enqueued after that ACK. Its menu and hover reviews, then the ChooseType installation, ChooseType review and current Custom Game hover review also completed with successful ACKs before the next input. There was no automatic review acceptance.

Command 10 selected the unique exact owner at target 62145D089DDB004B4797987808AC9C03, session 58DCA4AFAA09459449DA6FC90306DD9F, slot 0, endpoint 1, thread 1. Its observer armed before the ordinary Custom Game DOWN at step 7808. The baseline scene values were current/requested 55, manager4 4294967295, manager8 122202, mode/saved 0. DOWN enqueued the exact original messages 132 and 513 at native point (543,292), hwnd 65537, lParam 19137055, mask 1.

While the actual route driver was awaiting DOWN drainage, the observer reached 1,000,001 block boundaries and failed with boundary overflow, retaining the unchanged 1,000,000 cap. Its report has no native callback/branch/setup records and no pending native saved-return intervals. The last successful annotated 64-step ACK was through step 8704, at 995,000 boundaries. The next execution advanced frozen state to 8768, but its post-execution observer check failed; it is not counted as a successful transport ACK. There are 136 consecutive complete 64-step transport ACKs through 8704.

The first command failure was recorded at 20:19:56.582Z, before its 20:20:19.328Z deadline. Cleanup issued ordinary UP, leaving mask 0 and an UP message 514 queued at the same point; that UP was not guest-consumed before shutdown. The command never reached its DOWN-consumed or normal UP phase. This is a balanced host cleanup, not a completed guest gesture. The last fresh capture is the pre-DOWN Custom Game hover; no post-DOWN scene is claimed.

First remaining prerequisite and closure

The exact first remaining prerequisite is completing the genuine Custom Game input-drain/callback sequence within the existing observer boundary cap. The retained evidence identifies the cap fault, but does not establish why DOWN drainage had not completed. A different trace budget, reset, partial history or skipped drainage would bypass the present checks. None was applied. No emulator or guest causal repair is justified by these retained observations; the existing both-module executable boundary-overflow negatives pass. Source changes in this assignment bind the fresh authorization and isolate offline test outputs from the sealed predecessor evidence.

Normal direct-CDP closure observed Chrome 1063993 exit 0, signal null, at 20:19:56.702Z. Node 1063971, Chrome and owned process groups are absent; HTTP36605 refuses connections and the sole runtime flock is available. The wrapper exit is separately recorded as 0. The owned profile was removed after closure proof. The resource was explicitly released at 20:20:46Z. Box ID/state/expiry are NA; the coordinator retains future-box and shutdown ownership. Further original execution requires a new assignment; no retry occurred here.