Lords2 repaired-copy original follow-through

Task: NEW-GAME-LORDS2-DEMO-20261015. Evidence: scratch/runs/20261107-lords2-repaired-copy-gameplay/. Follows the OF_CREATE repair, published as c55fefee93e517e7dba940e21096fd2bf6a658d6. WINFLAGS and GetTempDrive repairs remain intact. No production code or guest media/config/save bytes changed.

The precise blocker is again the operational disk reserve, before ordinary installer input. The ONE original invocation ran 2026-11-07 03:07:09.187–03:08:01.137 UTC. At 03:08:00.710 UTC the existing 2.05 GiB guard measured 2,175,426,560 free bytes and queued normal Quit. Chrome and the probe exited 0. The prepared Install command's atomic publication then refused EEXIST because sequence 0 already contained that Quit. No Install command was published, no input was replayed, and there was no renewed automated risk flag or retry. The coordinator was notified on the append-only messageboard at 03:08:16 UTC; its approximate start time was corrected there at 03:08:41 UTC.

I personally inspected startup.png at original resolution: Sierra On-Line Setup's Main Menu with Install visible. input-review.json, commands/0.json and its completed Quit receipt distinguish a reviewed proposed click from dispatched input. The final observer has no LZCopy calls and no files under the default destination. Parent startup LZOpenFile probes for the logo exist; these are not the installation copy. Original post-fix copied bytes, installation completion, actual world and movement remain unobserved. This run demonstrates no new emulator divergence.

Independent predecessor cleanup passed after Aranna-native-point's explicit 03:05:33 release: all 50 recorded PIDs absent, ten ports refused, five profiles absent and four locks free. Only then was the local lane taken. Both standard and compatibility modules pass the generated NE/VFS OF_CREATE-copy regression, WINFLAGS, GetTempDrive and passive LZ-observer checks. Observer controls compare full 512 MiB memory, CPU state and VFS operations with tracing disabled, enabled and saturated. The production ordinary-input validator and range-server test pass. A synthetic readout control verifies that hashing skips lazy VFS accessors and does not materialize them. Run-local command publication uses a complete temporary file and exclusive hard link so the queue cannot read a partially written JSON command; no shared harness was changed.

Both modules match the predecessor's locked-build artifacts: standard 07f1cc970038f8ab31313b8b200edf26caa63473f293f5fc937f5cfe5c5c7f6e, compatibility 1d4bd4330ea16947959e3f4472339d5a32a61216cd8b5246198d11046b652c3e. No new build was necessary. Both observed original instances and the HTTP module response match the standard hash. The original launch source commit is 1d8d03ccabb91fde9b93c3625f6ecae62af56585; relevant binary diffs and owned helper patches are retained, without source archives. Of 213 observed HTTP responses, 203 match local bytes; the remaining responses match the predecessor's localhost-injected index HTML and optional build-info/CARDS 404 probes. All 181 original media files and the unchanged launcher manifest pass before and after, referenced in place rather than copied.

Independent cleanup at 03:08:41.677 UTC passed: all five recorded PIDs absent, both ports refused, the browser profile absent, no profile descendants and all four locks free; disk free was 2,809,729,024 bytes. Runtime/source/build were explicitly released at 03:08:41 UTC. No boxes were allocated, stopped, deleted or resumed; box ID/state/expiry are not applicable. Large unique readouts and logs were compressed in this run only.

The next original observation would still need fresh authorization and stable disk headroom before ordinary input through the default Destination Directory. It must inspect the first installation LZCopy source, destination, creation style, signed result and copied bytes. This invocation is terminal; no continuation or relaunch was attempted after the guard.