Lords II demo: visible county interaction
Verified ordinary player-controlled map interaction after the published WinExec repair 9b1da000e. Evidence is in scratch/runs/20261107-lords2-map-interaction/. No emulator or guest change was needed. This follows the installation and conquest-map investigation.
The decisive pair is map-before.png (04:52:31Z), showing the selected Radberryshire field's Farmland – Cattle panel, and farmland-after-selection.png (04:53:29Z), showing that same field's Farmland – Wheat panel. At 04:52:47Z an ordinary trusted pointer click on the visible wheat icon changed field usage. The intervening tutorial says changes take effect the following season; the final wheat panel says the wheat field is currently unused. This verifies selection and a farming control, not a harvested crop, completed turn, army movement, battle, audio, or whole-game playability.
I personally inspected the installation, installed title, demo greeting, opponent confirmation, conquest map/objectives, county panels and intervening tutorial captures. Their immediately following *-state.json.gz snapshots preserve the matching browser/process/VFS/module context. Before and after, the installed game is running, stopped is false, and the recorded far fault is null. No CPU exception/termination records occur in these snapshots. Observer traces are bounded; they are supporting context, not an assertion that every guest instruction was traced. Input commands, completion receipts and the production harness log are retained. The final panel was reopened through the same visible map coordinate used for the initial selection.
One fresh separate box, bx_jzwvk95j, was created at 04:47:14Z using a persisted UUID Idempotency-Key. No old box was resumed, deleted, or forked. Its original expiry was 06:17:14.283Z. Before the single original session, all 638 runtime/media pins matched, including all 181 original media files. Puppeteer and Chrome 151.0.7922.108 passed an independent page/click/normal-close smoke test, and the actual production queued-input validator accepted the prepared ordinary input kinds. Every subsequently submitted command also passed that validator before publication.
The run-local copy of tools/web-input-probe.js changes only its runtime root and command lifetime from 420000 to 1200000 ms. harness-only.patch records that exact change; no shared harness or emulator file was edited. A separate 1260-second guard was armed before launch. The task bound was 04:46:37–05:21:37Z, inclusive of cleanup. This provided sufficient capture time for ordinary installation and gameplay, without restarting the original. The original was launched at about 04:48:14Z, and the command queue advertised a 05:08:39.685Z deadline.
The immutable runtime source identity is Git 0570b3e09427b10624039622055736b59729f224, an empty relevant tracked diff, and the retained untracked lib/wininit-boot.js patch. runtime-pins.json records the individual staged files. The loaded module identity in all five observed instances is standard SHA-256 e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467; staged compatibility is 04acbb89f66ad9814836b5e2c34de659b518f4e1994f50c4ee8069c991f02f72. Exact modules remain retained by the predecessor run under tested-standard.wasm and tested-compat.wasm. Git and patches are the source recovery record; no source/media archive was created.
Installation used its default C:\SIERRA\L2Demo destination and normal visible confirmations. The generated Lords 2 Demo desktop shortcut was opened with two trusted pointer clicks. The game then reached title → Proceed → Begin the conquest → Game Objectives → county interaction. Installed LORDS2.EXE remains SHA-256 c83df505c4be850c10425f1770090ba3ca31fa6b87d8bce2cde3c66ae11dd0dc; SMACKW32.DLL remains 16725648b30a2bdcd2959a52ca92f9a0e14a7fc9fb26c84e90363c2631887f83. No guest files, registers, API results, or saved state were changed outside normal installation/game controls.
Two diagnostic mistakes are retained. The startup readiness assertion waited 35 seconds and expired at 04:48:49.617Z; the same uninterrupted session opened its command queue at 04:48:50.126Z. A subsequent read-only observation confirmed the live installer and longer deadline. There was no repeated launch or replayed input. A local observation script initially omitted import json and failed before making a remote call; that local script was corrected. Neither was a risk flag or emulator discrepancy. The first map click dismissed objectives and selected an underlying field; the resulting cattle panel was inspected before choosing the wheat control.
After the reviewed pair, command 18 requested ordinary quit. Chrome exited normally, code 0, at 04:53:47.735Z. remote-cleanup.json verifies harness 6804, server 6803, guard 6805 and Chrome 6823 absent; HTTP 36939 and debug 43425 closed; no Chrome using the owned profile; /tmp/wine-assembly-input-2xTY00 absent. All 181 media and 638 runtime pins still matched. The 79 retrieved remote evidence files are hash-checked in retrieved-final.json; matching snapshots are compressed individually. Local free space remained above 2 GB.
Following evidence retrieval and verified process cleanup, the explicitly delegated normal stop completed at 04:54:15.078Z. Box bx_jzwvk95j is archived, stop completed with forced:false, and has no active expiry or running runtime to hand back. Old boxes were untouched. Only this note is committed; ignored evidence is published with result.json last. Further scenario/turn/battle coverage is separate future work. This task stops after this verified farming-control result.