Stronghold unique-owner onward, 2026-11-04

The one authorized original stopped during startup at an exact first-script/ context prerequisite failure for the fourth attached Worker. It reached the personally viewed publisher splash, but no title-enter, main menu, Custom Game press, setup, preset, Start, world gameplay or hostile engagement. There was no retry. The repaired exact-owner discovery from 8008302103f1c4a258fc1a47072f173bc97bdcdb was present but never reached.

Evidence is scratch/runs/20261104-stronghold-unique-owner-onward/. See the preceding handoff. Its 523 sealed artifacts (33,265,087 bytes) remain unchanged. Git plus relevant binary patches preserve source; media/modules remain at existing paths with SHA-256, without snapshots, copies or archives.

Original attempt

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

I viewed the registered selector before its exact receipt and ordinary Launch, then the fresh startup captures at steps 256, 2304, 4352, 6400 and 7424. The last image shows the Gathering of Developers splash. Commands 0–4 ACKed successfully before the next command. Command 5 requested 1,024 further steps; it stopped after 640. There were 126 consecutive complete 64-step ACKs through step 8064, including the already in-flight ACK when the preload fault arrived. The next nested step rejected the preserved first failure. No later command was queued. All controls and input queues were drained; the sole mouse press was the registered Launch button. No title-enter command or game input occurred.

At 19:59:37.352Z the fourth attached Worker, E60569F503FFCA841B70910B1E76B157, session 047BE00EA337392B1233808C1190A00A, rejected with exact first-script/context prerequisite missing, before evaluating its preload or issuing script resume. The previous three Workers had successful first-script/context installation. The recorded overall browser deadline was 20:10:10.938Z, still live. The old failure record does not retain the rejected pause reason, top-frame script metadata or execution context. Which of those remaining prerequisites failed is unknown; no historical cause is invented.

Offline evidence repair and validation

The first-script helper now records the exact target/session/URL, observed time and deadline, individual prerequisite results, paused frame locations, selected script and parsed script identities before accepting or rejecting. Every original prerequisite remains mandatory. Rejection still blocks preload evaluation and script resume; there is no waiting extension, alternate context, URL relaxation, guest change or retry.

An old-helper fixture reproduces the missing rejected-value evidence. New fixtures retain exact missing-context, foreign-URL, wrong-pause, missing-frame, unparsed-script and expired-deadline values while all six reject before evaluation/resume. These are explicitly offline fixtures, not recovered values from this original. This fixes the evidence loss, not the unknown underlying live subcause. Existing disconnect, evaluation exception, closed-target and idle-timeout negatives remain enforced.

Before launch the actual ACK-aware client passed the two-review transport preflight, rejecting advancement at both reviews and after receipts without a successful ACK. Recorded four-Worker/six-send selection passed all nine before-arm negatives. Both current modules passed executable owning getters, callback/branch/scene/setup parity and rejected-init paths. Title/menu/ChooseType recognition, 26 historical routes, 20 before-input gates, ten post-move/freshness, four dependent-gesture, 27 hover, four opacity and 22 shell negatives passed. The causal diagnostics tests, actual retained composition, local contract and both-module executable checks were repeated after the evidence repair; the locked full build passed. Offline tests and startup images are not gameplay.

The local contract binds this assignment and rejects the predecessor. Absolute Chrome/cleanup cutoffs are 23:45Z/23:48Z, with unchanged 720-second browser, 60-second bootstrap, 40-second command and full 180-second cleanup reserve. Exact host/boot/PID-start, run/candidate/manifest/nonce, before-first-script installation and frozen/lifecycle/queue/scene/opacity/freshness/ACK guards remain.

Closure and next prerequisite

Normal direct-CDP closure observed Chrome 1035347 exit 0, signal null, at 19:59:37.606Z. Node 1035326, Chrome and their owned process groups are absent; HTTP45809 refuses connections and the runtime flock is available. The wrapper exit is separately recorded as 0; the owned profile was removed after proof. The resource was explicitly released at 20:00:07Z. Box ID/state/expiry are NA; the coordinator owns future boxes and shutdown.

Next requires separately authorized original qualification of the strict first-script/context prerequisite, now with exact rejected-value evidence. The owner-discovery repair and all timely title/menu/Custom Game reviews must still succeed before the ordinary balanced Custom Game gesture. No enabled setup control, preset or Start was observed, and none receives a readiness grant.