Disciples II leader progress, 2026-11-06

Leader movement and a second ordinary response are evidenced. Evidence: scratch/runs/20261106-disciples2-leader-progress/.

The run-local logger copies at most 128 API-name bytes into an ordinary buffer before decoding. Thirteen actual serialized observer controls pass, including shared memory, relevant/irrelevant names, disabled observation, forwarding, return/exception preservation and bounds. Nine exact parser controls, seven serialized callbacks, HTTP controls, mouse-state/button-hold checks and the locked full standard/compat build pass. Production, parser and viewport conversion are unchanged. Final logging: 18,700 Worker rows, 4,444 main rows, zero errors or drops.

One registered original reached Timmoria → Undead → Warrior/Average → day 1. The seal click did not visibly dismiss income here; reviewed ordinary Enter did. Enter accepted the actual default first-leader name Huunreh. Five distinct scenario dialogues were reviewed and cleared. Tab selected Huunreh with Move 20/20. One destination click at native(416,360) displayed blue route flags; a second reviewed click confirmed that route. After the hourglass cleared, movement-settled.png shows displacement relative to the capital, camera recentering and Move 16/20. Afterward, ordinary ArrowRight visibly scrolled terrain left beneath the fixed sidebar (menu-settled.png versus navigation-response.png), with 16/20 unchanged: the second response.

All 36 fresh captures and all 13 predecessor captures were personally inspected. Filenames leader-name, leader-selected and map-stable reflect intent, not their actual income/story-panel contents. Portrait, Escape and disk-menu attempts produced no persistent visible panel; no causal emulator fault or repair is established. Input receipts alone were not used as gameplay proof. API diagnostics cover main slot0; initial input dequeue receipts also show slot4, so these are not complete guest-consumption traces.

Tested source is b2316c3522b2edd9d2d465cc72f828387e707830 plus retained run-helper patches; relevant tracked diff is empty. All 1,282 source/module and 127 media pins match after runtime. Unique main owner: slot0/endpoint1/ thread1, 512 MB; actual WASM SHA-256 43a0097ab79e1e9102d6f12411485a359ebe10b03af5fcf22675b75ad701a081. Final live slots0/1/2/4 all expose this module. Original EXE at test/binaries/candidates/disciples2-demo/installed/discipl2.exe has SHA-256 adba242a0a3563651baffa6ec7d9a6c0978b7ae844a1cccedb2a1f4e8eb7b1f8; media is referenced in place, never copied or archived.

Ordered KKnD1245 → Legacy1253 FINAL releases and independent cleanup preceded tests. Reservation: 13:54:05–14:39:05 UTC; browser 13:55:22–14:20:28. Browser reports CLOSED worker completion; wrapper and lock-holder sessions returned143 with cause unverified, so continuous lock retention/browser exit code are not claimed. Final direct cleanup passes at14:21:47: 83 owned PIDs absent, port42779 refused, profile absent, four locks free, 5.47GB free. No boxes (ID/state/expiry N/A), deployment, listening or performance claim.