Lords2 complete staging and successful first LZCopy

Task: NEW-GAME-LORDS2-DEMO-20261015. Evidence: scratch/runs/20261107-lords2-complete-staging/. Follows the fresh-box preparation failure and the OF_CREATE repair. No production emulator edits or manual guest/media/config/save edits were made. The original installer performed its ordinary VFS writes.

The staging omission is corrected. Before allocating a box, I inspected predecessor prepare.py, both generated NE tests, LZcreate/passivity checks, their computed root requires and the runtime/browser dependencies. The inventory now includes test/helpers/ne-lifecycle-image.js and browser-fetched src/api_table.json. The offline filesystem-only audit verified 618 files, 35,205,682 bytes, all eight computed-root edges, the relative require closure, both pinned modules, all 181 media hashes and the launcher manifest. Complete lib/, fonts/icons and root browser assets cover conditional browser imports; npm dependencies are installed remotely. No local emulator, browser or build ran, and no Python file was named inspect.py.

Recovery is Git commit 8804de823ba7523ad07e83b36c38ce165859a0b3, relevant-source.patch, the untracked lib/wininit-boot.js patch, run-local input patches and runtime-pins.json. Existing media is referenced by path/hash; no source archive or repeated media was put in evidence. tested-modules.json verifies recovery from the already retained repair artifacts. The standard module is SHA-256 07f1cc970038f8ab31313b8b200edf26caa63473f293f5fc937f5cfe5c5c7f6e; compatibility is 1d4bd4330ea16947959e3f4472339d5a32a61216cd8b5246198d11046b652c3e.

One fresh box, bx_m9xfz23k, was created at 03:19:55Z after persisting its UUID Idempotency-Key. Its remote file verification passed with 57,302,433,792 free bytes. Node v24.22.1 and Google Chrome 151.0.7922.108 were used. Both pinned modules actually executed and passed WINFLAGS, GetTempDrive, generated OF_CREATE/LZCopy and observer controls: eight passing baseline rows. The passivity checks compare the complete 512 MiB memory, CPU state and VFS operations with observation disabled, enabled and saturated. Production ordinary-input validation passed before the original launch. Prior WINFLAGS/GetTempDrive/OF_CREATE repairs remain intact.

The one original invocation started at 03:21:02.652Z (original-attempt.json), reached normal browser exit at 03:24:08.282Z, and completed evidence retrieval and box shutdown by 03:25:56.688Z, within the 35-minute bound. I personally inspected all nine original-resolution captures. Seven balanced clicks followed Install, System Test Yes, Wave Yes, CD-ROM Detect OK, Video Display Test OK, the offered Yes on the requirements warning, and Yes for default destination C:\SIERRA\L2Demo. Wave Yes is not proof of audible output. All seven clicks, one observation-only command and normal Quit have complete receipts; there was no unknown/partial input, replay or second original invocation. An early read-only fetch requested startup.png before it existed; the FileNotFound is retained. The capture was subsequently retrieved after the queue-ready receipt. No guest operation was repeated and no automated risk flag occurred.

The first installation LZCopy now succeeds. The original child opens C:\LANGUAGE.INF with style 0, handle 5, and C:\SIERRA\L2Demo\LANGUAGE.INF with style 0x1000, handle 6. LZCopy receives source 5/destination 6 and returns DX:AX=0000:0CF1, signed +3313. Read-only live VFS inspection compares every byte of the resident source and destination and reports equal length and equal bytes, 3,313 each. Destination SHA-256 is 2a758d7248807e9566bb24d461426dc3732704a3fe20c4a624d31a9c216345d2, matching the recorded original media. original-causal-result.json retains the actual entry, return, opens, equality result and inventory. Both observed emulator instances identify the tested standard module; HTTP response hashes are also retained.

Copy Files progressed visibly to 93% (C:\FILES\VILL.PL8 to the destination). The subsequent snapshot contains 179 entries under c:\sierra\, including copied game assets. That inventory and a disappearing progress dialog do **not** establish completed installation. The first remaining emulator failure is a thread trap at **CS:IP=0067:946F**, linear EIP 0x1b946f, ESP 0x1f8796. The retained observer's pending call is key 0x00020122: module USER, ordinal **290**, returning to 0067:9478. Its Pascal words decode to **RedrawWindow(hwnd=0x0133, rect=NULL, region=0, flags=0x0101)**. Wine's Win16 USER specification identifies ordinal 290 and its word/pointer/word/word signature. Our win16_user dispatcher in src/09e-win16-api.wat has no ordinal-290 handler, and the unhandled dispatch ends in unreachable. The crash stack and final guest block are retained; observer errors/dropped API records are zero. Numeric Wasm stack indices were not attributed using the current combined-WAT walker, whose index range does not match this compiled module.

I stopped ordinary input at that failure. No game launch, world or movement was observed. Aranna took source/build ownership explicitly at 03:24:06Z, so this worker made no production edit or build. The concrete next repair is a real Win16 USER.290 adapter, with generated NE regression coverage of the observed null-region/rectangle 0x0101 call and correct Pascal/paint behavior, both-module focused tests and a locked build after explicit source/build release. No silent-success substitute or guest bypass is warranted. Original follow-through would require a separately authorized successor; this invocation is terminal.

All 181 remote media files and the launcher manifest remained unchanged. Unique logs, receipts, captures and compressed traces were retrieved and byte/hash verified before shutdown; compression roundtrips are verified. Cleanup finds probe, server, Chrome and deadline-supervisor PIDs absent, profile absent and port 36933 refusing connections. Normal shutdown was explicitly delegated by this task: operation stop_9be801ed82365b49 completed at 03:25:56.688Z, forced=false, error=null. The box is archived with no active expiry. Superseded box bx_bkjk4v3j was not resumed or deleted. No public deployment, nested worker or local heavy runtime occurred.