Stronghold Crusader demo — hostile-engagement preflight blocked
No hostile engagement, damage or defeat was reached. This attempt stopped before Chrome because the reconstructed runtime could not resolve the browser-driver dependency puppeteer. This does not extend the accepted spear supply/recruitment/movement result in the predecessor note, published at a0522f78a. No game input or attack was issued.
Evidence is scratch/runs/20261104-stronghold-native-hostile-engagement/. The assigned box bx_285595gz independently reported API-idle, health ok, hydrated true, and actual exec RUNNING at 04:36:15Z; an append-only board ACK preceded staging. Only this allocation was accessed.
The minimal runtime was reconstructed directly on the box at /home/user/stronghold-native-hostile-engagement-runtime, without a source archive, local media copy, rebuild, or staging the full checkout. reconstruction-inputs.json records explicit Git blobs and existing original-media paths with full SHA-256. All 2415 predecessor runtime pins passed locally and on the box. Original EXE SHA-256 is 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f. The installed inventory remains referenced at scratch/runs/20261103-stronghold-crusader-original/installed-pin.json; media was transferred directly from its existing paths to the box.
The stated runtime commit is 1188e9bf57ef35bd3363fb88b7ca0da442ce696d. One nonexecuted input, tools/callback-ownership-census.json, did not match that commit despite the predecessor's empty relevant-source patch. Its exact pinned bytes were recovered in memory from the registered-skirmish recipe's dd78dad0b8322a8f4dbb7e615a890c3132437c57 plus relevant-tracked.patch. This run's relevant-source.patch records that census delta against 1188e9bf; other tracked pins match that commit. No shared production file was changed.
The retained predecessor modules supplied canonical cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee and companion 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3. Both staged hashes passed. Neither module was instantiated in this attempt.
Before Chrome, Python helper compilation and JavaScript syntax checks passed. The adapted driver fixture accepted a 64-step ACK and rejected invalid counts, an incomplete/timed-out ACK, input without a capture reference, and unmatched releases. Actual loopback HTTP checks passed status, COOP/COEP and pinned response hashes for the index, app registry, both modules, and original-media manifest. The subsequent require.resolve('puppeteer') failed with MODULE_NOT_FOUND at 04:38:41.788Z, command cmd_9v046xfdge5t; first-failure.json preserves the complete response. No dependency-install retry, browser launch, reload or second browser followed. Capture/recovery behavior in a live browser consequently remains untested.
The original failure is distinct from two local/recovery helper mistakes preserved in the logs: initial git rev-parse handling treated a failed lookup's stdout as a blob ID, and a closure script's broad RUN substitution damaged the literal RUNNING. The input lookup was corrected before staging; only the closure inspection was corrected after the dependency failure. Neither executed a game runtime or changed gameplay.
Recovery inspection at 04:39:22Z proved all 2415 staged pins unchanged, the browser-output directory absent, and no chrome, chromium or node process. The HTTP helper closed its server in finally. Unique helper sources, control responses, provisioning log, pin references, first failure and closure evidence are retained locally; no source tree or media was recovered into evidence. Final health remains API-idle, healthy and hydrated. Box bx_285595gz remains RUNNING, expiry 2026-11-04T05:33:35.510Z; shutdown ownership returns to the coordinator. No stop, delete, resume, subworker, successor, guest write, cheat, game-check edit, Save/Load retry, public deployment or Heroes II occurred.
The concrete next prerequisite is a reproducible installation/resolution of the pinned browser-driver dependency on the assigned runtime before any newly authorized browser attempt. Native Zephyr Very Easy food/popularity/wood management, recruitment, selected-unit identity, hostile identification/health and before/after combat evidence are all unreached in this attempt. No production build was required for this documentation-only change.