Stronghold qualified Crusader attempt stopped at an unstaged preflight dependency

The single original browser stopped at step 2048, startup loading artwork. It did not reach the title dialog, main menu, qualified Crusader hover, ChooseType, route installation, Zephyr, native Start or world. The game-crop driver itself did not reject or demonstrate a production defect: its qualified menu action was never invoked.

Evidence and small recovery helpers are in scratch/runs/20261104-stronghold-qualified-crusader-native/. Preparation Git SHA is recorded in exact-git-sha.txt; the retained runtime source remains 1188e9bf57ef35bd3363fb88b7ca0da442ce696d. The previously published driver is d1e2b122ab630357ec1e5e350aedc3922cadc66b. Its browser-driver.cjs, menu-driver.cjs and presentation.cjs were copied unchanged into this run. Predecessor helpers remain read-only. owned-new-helpers.patch recovers the run's small inputs; relevant-uncommitted.patch, source-reference.json, dependency-graph.json and the artifact manifest identify the source and retained non-Git inputs. Git remains the source archive; no source snapshot, tar, module or media copy was made.

Actual first missing prerequisite and sequencing error

All 2415 retained pins matched before Chrome. The actual CJS/dynamic ESM imports, run-helper dependency hashes and five HTTP responses with COOP/COEP passed. Offline actual driver tests passed 111 checks / 25 modes, title transport 20 checks, route DOM eight negatives, and the unchanged native Start suite.

I omitted the required cache-graph check before launching Chrome. When I then attempted node tools/check-browser-cache-versions.js in the retained runtime, it failed MODULE_NOT_FOUND: that tools file is absent from the intentionally small retained source graph. The probe was an external preflight command; it did not fault the browser mailbox. A shell command queued after that failed probe still issued the single input-free startup observation, completing 32 full ACKs / 2048 steps. That continuation after failure was my sequencing error. I sent quit immediately afterward. No game keyboard or mouse event was sent. The registered page-level Launch click is separate from in-game input.

The fresh personally reviewed full PNG review/startup2048.png, SHA-256 80707ff6eb3334b13950c5ae52451d290cc5f4010438c94724d9dfe008bf1d87, shows the king, soldiers, castle and loading progress bar, with the frozen counter at 2048. It is startup evidence, not gameplay. The preceding live checkpoint at step 10432 remains historical; this fresh browser did not reach it.

Offline repair and exact recovery recipe

The run-owned preflight.py now stages a small, byte-identical copy of the repository cache validator as cache-check.cjs, verifies its SHA with the other helper dependencies and invokes its exported validator against the actual retained index, host, guest-worker and D3D stream files. It no longer assumes a tools/ installation. launch.py runs this complete preflight with subprocess.run(..., check=True) before the sole launch callback and queues no observation. Five offline sequencing checks prove that missing-file, graph-rejection and import failures prevent launch, and that successful preflight permits one launch. The copied validator passes the current local graph: 98 page scripts / 13 worker scripts. This local result is not a claim that the corrected preflight ran on the assigned box.

The corrected preflight/launcher was not executed remotely, and there was no browser retry. A separately authorized successor can recover the small helpers from this run's patch, retain the dependencies listed in dependency-graph.json by path/SHA, and use a fresh coordinator release. Stage the unchanged own driver/menu/presentation and fresh release at the same relative paths beneath /home/user/stronghold-corrected-native-start-runtime; run python3 scratch/runs/20261104-stronghold-qualified-crusader-native/launch.py only in a fresh run namespace with no existing browser evidence. The launcher automatically stages its own cache validator. Existing names and browser/ must never be reused. Copy the small helpers into the successor's own run and update only run-specific paths before qualification. The runtime-release authorization label must remain stronghold-game-crop-freshness user task, with shutdownOwner: coordinator and a fresh bounded closeBy.

Use the predecessor title/crop notes for the manually reviewed startup/title/menu sequence and route dependencies. Preserve strict ChooseType, native Crusader (304,144), right towers (543,292), preset (67,491), existing routeDispatch queue, strict Zephyr and unchanged native Start (718,569) guards. Stop at the first missing prerequisite or rejection; do not queue commands alongside prerequisites in a shell that can continue on failure. Original world/gameplay remains unproved by this attempt.

Closed evidence and box handoff

Driver 9351 opened Chrome 9377, Chrome 151.0.7922.108, with identity recorded at 08:01:31.260Z. Chrome closed normally at 08:01:47.083Z, exit zero. The close deadline was the earlier 15-minute bound, 08:16:31.259Z, within the assigned 08:23Z hard close. recovery-closed-verified.json verifies 52 closed files / 1287037 bytes, recovered before 08:02Z, without hashing active logs. verification.json verifies the 32 complete ACKs, zero game mouse events, 370 matching served-pin receipts, successful quit and closed evidence. No browser first-failure record exists because the failure occurred in the external preflight.

Actual readonly exec at 08:02:31.423Z confirms driver/Chrome absent, private HTTP 46043 closed, and all 2415 retained pins unchanged. bx_pu5e3qkn remains RUNNING / API-idle, healthy/hydrated, expiry 2026-11-04T08:39:09.954Z. The coordinator owns shutdown and receives runtime custody. No box lifecycle action, source-box access, second browser, reload, guest write/call, forced scene, subworker, successor, local heavy/browser run, Heroes II or deployment occurred.

Only run helpers and this note changed; no production-code build gate applies. The intended live qualified-menu and gameplay objective is unfinished at the concrete preflight dependency blocker. This single-task worker publishes the tested offline sequencing repair, hands back the running box and stops.