Lords II demo: seasonal turn and county management
Verified the unchanged installed demo advancing from Winter 1268 to Spring 1268 after an ordinary visible End Turn click, with a county field changed from Living Fallow to Wheat beforehand. No emulator discrepancy was demonstrated and no emulator or guest code was changed. Evidence is retained in scratch/runs/20261107-lords2-season-progress/. This extends the predecessor farming-control result, published as 2472ef81a.
The personally inspected sequence is:
| Capture | UTC time | Visible result |
|---|---|---|
food-help-dismiss.png |
05:03:26 | Winter 1268; Radberryshire field is Farmland – Living Fallow. |
field-wheat-before-turn.png |
05:03:52 | Same map coordinate reopened after the wheat-icon click; Farmland – Wheat, currently unused. |
county-panel-close.png |
05:04:04 | Winter 1268; population 172, happiness 56, cattle 36, 200 crowns. |
end-turn.png |
05:04:24 | Spring 1268; population 204, happiness 62, cattle 38, 200 crowns. |
field-after-season.png |
05:04:38 | Same field remains Farmland – Wheat in Spring, currently unused. |
Command 22 selected the visible wheat icon. Command 23 reopened the same field. Command 24 closed its panel and command 25 clicked the visible End Turn control once; its completed receipt precedes the Spring capture. Command 26 reopened the field after the season. Matching immediately following *-state.json.gz snapshots show the installed game running, stopped false and farFault null. The retained diagnostics are selective path/API observers, not a full CPU trace; the game observer has zero selected path records. These observations do not establish a harvest, army movement, combat, audio, multiple turns, threaded execution, or whole-game correctness. The unused-wheat description alone does not demonstrate an emulator defect.
One fresh separate box, bx_2kpggy2w, was created at 04:57:53Z with a UUID Idempotency-Key persisted before the create request. No old box was resumed or otherwise touched. Before the single original session, all 638 runtime/media SHA-256 pins, including all 181 original media files, matched. Shared pinned paths exactly matched the predecessor. Chrome 151.0.7922.108 and Puppeteer passed a separate page/click/normal-close smoke test. The actual production queued-input validator passed its self-test and prepared ordinary inputs; every submitted command was validated again before queue publication.
The run-local production harness changes only its runtime root and command lifetime from 420000 to 1200000 ms, retained in harness-only.patch. A separate 1260-second guard was armed at launch. The queue advertised a 05:18:34.942Z deadline. Ordinary installation used the default C:\SIERRA\L2Demo, then the real generated Lords 2 Demo shortcut was opened with two trusted pointer clicks. Title, greeting, opponent confirmation, objectives, tutorials and county panels were inspected. No guest patching, saved-state forcing, synthetic replacement, or UNKNOWN-input replay occurred.
The early installer input labels are historical intentions, not reliable descriptions of the resulting dialogs. Inputs 4–8 include ineffective clicks and a repeated visible display test because the initially assumed confirmation order and coordinates differed from the captured result. Some early capture-and-next-input tool calls were batched, so this portion did not fully meet the requested inspection-before-next-input discipline. From command 9 onward, each image was opened and inspected in a separate call before the next action. Every input had a completed receipt; none had an unknown outcome. These input-selection mistakes are not emulator discrepancies. The decisive management and seasonal sequence used that separate inspection discipline throughout.
The tested runtime pin manifest records Git 2472ef81ac266b5a500153998577c266473286cc, an empty relevant tracked diff, and the retained untracked lib/wininit-boot.js patch. All five observed module instances report standard WASM SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467; staged compatibility is 04acbb89f66ad9814836b5e2c34de659b518f4e1994f50c4ee8069c991f02f72. Exact identical modules remain retained in scratch/runs/20261107-lords2-winexec-search/tested-standard.wasm and tested-compat.wasm. This is the pinned predecessor runtime, not a claim about a later concurrent build. Git and patches are the source recovery record; no source/media archive was made.
Across the five reviewed gameplay state snapshots, installed LORDS2.EXE remains SHA-256 c83df505c4be850c10425f1770090ba3ca31fa6b87d8bce2cde3c66ae11dd0dc and SMACKW32.DLL remains 16725648b30a2bdcd2959a52ca92f9a0e14a7fc9fb26c84e90363c2631887f83. Execution used cooperative browser mode, ?debug&no-threads, viewport 1000×800, and ordinary production presentation. No shared source, harness, or build files were edited. No code regression test or new locked build was warranted for this documentation-only result.
Command 27 requested ordinary harness quit. Chrome exited normally, code 0, at 05:04:58.397Z. remote-cleanup.json verifies harness 6091, server 6090, guard 6092 and Chrome 6110 absent; HTTP 36939 and debug 45797 closed; no Chrome using the owned profile; /tmp/wine-assembly-input-lo397u absent. All 181 media and 638 runtime pins still matched. All 107 retrieved evidence files passed size/SHA-256 checks. Large matching snapshots/logs were compressed individually, and local free space remained above 2 GB.
After evidence retrieval and process/port/profile cleanup, the explicitly delegated normal stop was requested at 05:05:52.531Z. Box bx_2kpggy2w is confirmed archived, stopped at 05:05:52.849Z, operation completed with forced:false, and no active expiry or running runtime to hand back. Only this note is committed. Further work, if requested, should test ordinary army recruitment/movement or later harvest; this task stops after one verified season and one county-management action.