Authorized original licence acceptance readiness

The 2026-10-18 user receipt authorizes ordinary Accept/Yes for Dungeon Siege, AoE3, Conan, Aranna, Shadow Man, Jedi Knight and Army Men. It does not record guest acceptance. All seven remain acceptedInGuest=false at this checkpoint. Root owns serialized runtime, task ledgers and any later compatibility work. Other review restrictions and the prohibition on public deployment remain.

Fresh local findings

Read-only audit on 2026-10-19 found the following. Historical source/module pins are evidence only; none have been reused as current runtime admission.

The Dungeon Siege extracted directory is test/binaries/win98-games-a-d/DungeonSiege demo-D3D/extracted. Its .original-package.json seals every file; the original outer SFX is absent. The original executable is 3,608,640 bytes, SHA-256 8df1ba314073f8e9e7b48c7ed0fd3a976b1dafb722bffcb41f613a4c60a421ab. The retained outer identity is 192,188,416 bytes, a501306cad88c0fc41f986d92109343d68ac79fc11aaa6611724d84be628f3f8. Extraction provenance is not an installation or gameplay claim. The registered original route already presents the genuine EULA; do not fabricate acceptance registry state or swap in another executable.

First bounded acceptance allocation

1. After root grants the sole runtime, recheck free space, exact physical current source, runtime dependencies, registered companions and canonical wasm. Record new pins and actual HEAD in a unique run directory; the historical 937466db... controller pins are not applicable.
2. Launch the registered Dungeon Siege original route with ordinary renderer input. Capture its settled genuine EULA and identify the actual visible Accept control from that capture. Do not reuse guessed coordinates from another game or issue direct guest commands/memory writes.
3. Send one normal mouse click on Accept; retain before/after PNGs, actual input receipt and bounded log. Stop at the next stable screen or first failure. Only an observed guest transition following that click changes the recorded acceptance status. Permission and a queued input are insufficient.
4. Preserve original bytes. Export resulting guest state separately. Verify source/fixture hashes and absence of the owned process group on exit. Installation/gameplay and further inputs remain distinct evidence stages.

Proposed allocation: 60 seconds guest, 75 seconds controller, 90 seconds hard process-group deadline, 8 MiB log cap; admit above 2 GiB +128 MiB after planned writes, stop at 2 GiB +64 MiB. Reserve 256 MiB for captures/guest state, and stop if actual growth exceeds it. Initial audit free bytes: 3,268,358,144. Refresh this value on grant; it is not a reservation. No build, browser, guest or download ran during this preparation.

Small-package recovery recipes

Army Men: retained source URL https://archive.thedatadungeon.com/army_men_1998/distributions/1998-09-14_microsoft_windows_demo/a.zip, 18,373,265 bytes, SHA-256 dd1faca49d6e5adc0a3db58831039274930b468caa713f1c0fb4fe074754908f. Inner self-extractor: 18,418,688 bytes, 5b0db6d109d49818ce617cd539451c73273f09a98f8089065b10107790777752. Use the original acquisition inventory to select the embedded ZIP format explicitly; the historical default PE archive attempt failed. Verify all 187 payload hashes from scratch/runs/20261015-army-men-original-acquisition/payload-hashes.json. Normal SETUP.EXE generates _ins576._mp, 648,704 bytes, 48141f38085b79f09e6e34d6c835ca3fefe970141b6f8435cf70ee7046c028c0. Historical captured empty args/cwd c:\armymen and registry timing must be preserved, not replaced with invented launch parameters. Normal Welcome Next was (415,394) at 640x480; re-observe before clicking. Allow five seconds for licence text to settle (earlier blank capture was premature), then inspect the fresh Yes control and click it normally once.

Jedi Knight: retained original URL https://ia801506.us.archive.org/0/items/jedi-knight/jedidemo.exe, 21,195,858 bytes, SHA-256 8aae38165e08b68bb63cfd21b8c28ed1d4d8f1bb400a0162588d5b86acdc827e. The retained tools/extract-jedi-knight-demo.js in the historical /home/user/lbreakout2-registration checkout verifies package identity and all 39 single-file ZIP records, 40,812,035 extracted bytes. Copy/review the small extractor into recovery evidence before using it; do not run that historical checkout as the emulator. The compact capture is scratch/runs/20261015-jedi-installer-capture/evidence/run/capture; its original child is 674,816 bytes, 12a2929a615924e212490f4ef3a1cbb36ecebddafea0f358991a0fc57b7cab84. Validate the full run/bootstrap/captured-child.json captureManifest and actual bootstrap registry. Empty args/cwd C:\ are authentic; _ins0432.ini owns the options and must not be translated into guessed command-line arguments. The observed Software License Agreement requires normal visible Yes selection.

Both recipes fit well below a whole-disc recovery, but each still needs a fresh size/reserve calculation and byte validation. No recovery was performed in this checkpoint. Prior stopped-box evidence/review restrictions are not superseded by licence permission.

Evidence: scratch/runs/20261019-authorized-installer-preparation/ contains the fresh Dungeon Siege full-file audit and read-only readiness script/receipts.

First authorized runtime allocation

Root granted current canonical /tmp/wa-recovery-20261014, HEAD a53f43dba7a884a7a53a4c86172d3226aa69f5c3, wasm da72a16f9551cb2cd8bc2f0ee636eb966ec9c7cde9a56931201bb6d1fb11a2c7. The registered fixture was absent there. A hard-link preparation failed with EXDEV before any guest started; explicit fixture-file symlinks then resolved the same 37 verified original files and two manifests without duplication.

The single original CLI allocation reached and visibly rendered its genuine English EULA. Initial loading consumed most of the 60-second guest budget. The reviewed settled screenshot shows Accept at center (163,432) in 640x480. The normal mouse click request reached a closed HTTP control endpoint after the guest's time bound: ECONNREFUSED. No input was delivered and no licence was accepted. No automatic retry was made. Future input must still verify the fresh screen; this is not permission to click blindly at startup.

Guest exit0, no signal, owned process group absent; all original files and canonical wasm unchanged. The full physical source comparison found only root-owned TODOS.md changed during the run; runtime sources were unchanged. Minimum observed free space was 2,585,423,872 bytes. The 17,785-byte log, original EULA.RTF, reviewed before/final frames, input failure receipt, separate acceptance.json and final guest state remain in scratch/runs/20261019-dungeon-siege-authorized-acceptance/. The full output preserves a missing native ole32.dll warning; the observed EULA does not establish later game compatibility.

Revised allocation: Dungeon Siege accepted, next API blocker

Root reviewed the genuine screen and granted one revised 90/105/120-second allocation with fresh 256 MiB output reserve and the same disk thresholds. Actual HEAD was c0b98c2dc02c668a2f4bc8e19b55a1ea08eee39b, same canonical module and originals. Runtime-only physical pins numbered 3,222; changing task ledgers were excluded while HEAD remained recorded independently.

The fresh EULA frame was inspected again. One normal click (163,432) was actually delivered at batch 1235837; accept-input.txt and the guest log agree. The original EULA returned EAX1, disappeared, and the game created its Dungeon Siege Demo main window and game thread. Dungeon Siege licence acceptance is now observed (acceptedInGuest=true). The other six titles remain authorized but unaccepted. The earlier false receipt is preserved as the separate first allocation, not overwritten.

The next original failure is CreateToolhelp32Snapshot(4,0), at EIP 0x00617fc6 (jmp [0x6f5284]), return address 0x00425ef2, batch1235874. It hits the explicit unimplemented API trap, exit1, no signal. No further retry, compatibility workaround or gameplay claim. Before/after frames are reviewed; the after frame is teal and is not evidence of gameplay.

All runtime/source, original fixture and wasm pins remain unchanged; owned process group absent. Minimum free bytes 2,430,791,680; log 13,925 bytes; no guard fired. The crash occurred before normal final registry/VFS export, so persistent accepted state was not exported. The first allocation's pre-acceptance VFS must not be represented as accepted state.

Evidence: scratch/runs/20261019-dungeon-siege-authorized-acceptance-2/, including actual input receipt, reviewed screenshots, physical pins, exact original EULA.RTF, acceptance.json, postflight and 14-file artifact seal. Terms SHA-256: bd4f7b3460e8821a9ea33934f3e5ff99614911d1d0fa37494e5f2797ef15b81d.