Stronghold Crusader demo — military construction, missing spear blocker
Ordinary original controls in Zephyr — Very Easy (1/10), versus The Rat constructed an Armoury, Barracks, and Poleturner’s Workshop. Recruitment reached a concrete resource blocker: the native Spearman control shows Cost 8 and a red X beside the required spear. The Armoury subsequently shows zero spears and zero of every other weapon type. An ordinary held recruitment click produced no identified new unit. Recruitment, movement toward The Rat, attack, and victory are not demonstrated. The bounded task stops at the missing weapon; it does not establish that recruitment is generally unavailable in this demo.
Evidence: scratch/runs/20261104-stronghold-ordinary-military/. No production source, original executable, configuration, guest memory, game checks, or mounted media was edited. Save/Load was not retried; its accepted grey-control blocker remains in stronghold-native-save-load-20261104.md (413afa3bb875caaf11503e5437a9eb7b68b48f6d). Village and food notes supplied the ordinary control route.
Inspected controls and outcome
Named captures below are under recovered/browser/, with paired state JSON and screenshot hashes, personally inspected:
main-menu.png,choose-type.png,custom-skirmish.png,scenario-one-again.png,village-entry.png: registered selector/Launch → original title → Crusader → right-hand towers → scenario 1 → Zephyr. The initial custom screen says “Not available in the demo”; scenario 1 selects the available route. An additional ordinary scenario click opened the character picker; the subsequent start-arrow click entered gameplay. Some exploratory capture names, includingzephyr-readyandpicker-closed, describe intended actions rather than verified results; the actual images remain authoritative.barracks-preview.pngactually identifies Armoury, 5 wood, not Barracks.armoury-placed.pngshows its placement and 95 available wood, down from 100. The initial scenario gold counter finishes at 8,000; the earlier 2,700 invillage-entrywas still counting upward.recruitment-preview.pngidentifies Barracks, 15 stone. Early east/south positions did not place it.barracks-west-preview.pngshows an obstructed red footprint;barracks-clear-preview.pngshows a usable preview northwest of the keep.poleturner-actual-preview.pngand later panels show the persistent Barracks there. Two stone had already been consumed during exploratory castle controls; the Barracks uses 15 of the remaining 48. No production defect is inferred from these attempts.- The weapon menu contains empty space before its first actual workshop icon. Early clicks at x≈40/110 did not select a workshop; their misleading “fletcher” helper filenames do not establish a Fletcher. An enlarged inspection crop is retained locally. The actual icon at browser (213,770) selects Poleturner’s Workshop, 10 wood and 100 gold.
poleturner-actual-preview.pngshows its usable preview southeast of the keep;barracks-panel.pngandarmoury-inventory.pngshow the workshop remaining after switching panels. Gold is 7,900 afterward. barracks-panel.png: Available Peasants 5.spearman-cost.png, step 30,144: Spearman, Cost 8, with the missing-spear red X.spearman-attempt.png, step 30,784: the held recruitment attempt leaves that requirement red, with Available Peasants 4 and 7,900 gold. The peasant change alone is not evidence of recruitment; a workshop worker is also active.armoury-inventory.png, step 31,680: the native Armoury inventory shows 0 under all weapon/armour icons, including spears. This corroborates the recruitment resource blocker. No workshop delivery was awaited after identifying it. Popularity also fell during this construction-only route; final HUD 3, population 4/10. Sustainable recruitment would additionally need village support.
Mouse/key commands used trusted browser input, with sequential acknowledged frozen advancement of at most 64 steps per request. After exploratory selections, the run helper added two acknowledged 64-step requests between pointer movement and button press to allow the pointer to settle; this was a run-only control adjustment, not a diagnosed production repair.
Exact runtime and validation
Runtime remains the existing /home/user/stronghold-registered-skirmish-runtime, Git 1188e9bf57ef35bd3363fb88b7ca0da442ce696d. source-reference.json, empty relevant-source.patch, and all 2,415 unchanged runtime pins record the actual tested inputs. Concurrent main changes were not substituted. Git is the source archive; no source snapshots/tarballs or media copies were made.
Original media remains at the existing installed paths, referenced by scratch/runs/20261103-stronghold-crusader-original/installed-pin.json (1,856-file inventory, with the two previously excluded auxiliary executables absent). Original EXE: test/binaries/candidates/stronghold-crusader-demo/installed/App_Executables/Stronghold Crusader multiplayer demo.exe, SHA-256 9024c533095f2227b0105b7e8a9e4cf28ec4fb206b165629787b2c97cf99f13f. Companion manifest: d51be8d9ab1038b7dc2b3242f3a4ebed382f1fbf33d558211a80bd36ab112b21.
Both actual modules were recovered and full-SHA verified: canonical cffca869b541e6eff12ae3a6b74c4476977e0a7e23cd43d8ec5ba8faecd4bcee (2,143,540 bytes), compatibility 580f49f3c78d26e6855efa0beb37046d03ea24690ff98cfcb3e94ce5e6cb1ee3 (2,146,153 bytes). Canonical compilation/instantiation and transfer to guest Worker 0 are linked by observers; compatibility was retained but not selected. Actual presentation is guest Workers, Canvas 2D/DirectDraw, with no observed WebGL context. The toolbar setting is not a backend claim. Chrome 151.0.7922.108, Node 24.22.1, Puppeteer 24.31.0, 1200×900 viewport, original 800×600 game canvas, cross-origin isolation, local index.html?debug&candidates&frozen.
Before browser launch, helper syntax/imports, static-server entry point, Chrome availability, Python compilation, and runtime pins were checked. verify.py passes 653 completed sequential requests, 495 step requests, maximum 64, total 31,680 steps, 111 input commands, 72 trusted observed events, balanced controls, empty final queue and zero mouse mask. All 1,058 HTTP receipts match their pins. node test/test-app-files-policy.js passes. No production code changed, so no production build was required. These checks validate the evidence/control path, not military success.
Recovery and handback
Assigned bx_e94v5mct was verified RUNNING/API-idle, healthy, hydrated and ACKed before use. Expiry remains 2026-11-04T03:35:44.549Z, shutdown owner coordinator. Browser interval 02:47:06.143–02:57:43.418Z, 637.275 seconds, below the single-segment 20-minute bound.
2,022 live files including both actual modules were recovered and full-SHA verified before browser/helper close. Final recovery verifies 2,026 files, including cleanup records. Chrome PID 15875 exited normally with code 0; browser driver absent, loopback port 43031 closed. The box remains RUNNING/API-idle, health ok, hydrated, with the same expiry. Recovery and cleanup completed before 02:59Z, ahead of 03:25Z. No allocation, resume, stop, delete, subworker, successor task, or public deployment occurred.
Next, in a separately assigned task, establish actual spear delivery to the Armoury while keeping peasants available, then recruit through the Barracks and inspect a selected unit responding to a movement/attack order. This run makes no such claim.