Aranna launcher closure and original gameplay attempt

Evidence is scratch/runs/20261107-aranna-launcher-closure-gameplay/ (R). This continues the final pinned qualification. Original snowy-world movement and attack require personally inspected native consequence captures; generated control scenes do not establish gameplay.

The passing retained qualification is inherited without repeating its control suites. All 153 frontend resources, including production guest/render Workers, match their qualified hashes. The observer module remains SHA-256 88ff2708a2dec89af430fac2ba778f39857c2716e851299c3ecbfa62fd5e7d1f. All 28 original-media entries and licence-authorization bytes remain unchanged.

The local preflight constructs the pinned HTTP server, expands the retained driver, and resolves launch/helper imports without a browser or guest. Node loader hooks also check ESM dependencies that CommonJS extension hooks miss. The trace resolves 369 files. All 2,998 proposed paths are unique and relative; their sizes and hashes are locally recoverable and verified. The closure adds the retained-runtime manifest, Python supervisor, and exact installed Node runtime dependencies. The fresh box lacks Puppeteer; 645 package files (7,765,890 bytes) are pinned instead of installing a floating version.

An exploratory check also found an inherited unused pointer-recovery wrapper whose target does not exist. That wrapper belongs to adapter-reload tooling; the launcher and its input path do not import it. It was not used or substituted.

One fresh UUID-idempotent box, bx_47ytuqcz, was created at 11:53:29.177Z with initial expiry 12:33:28.909Z. The archived predecessor box was neither resumed nor used. Original media is staged from its existing path, with Expansion.dsres reconstructed from individually hashed transfer parts. No source or media archive is created. Git SHA plus relevant patches provide source recovery.

Remote preflight at 12:00:43Z verifies all 2,998 staged files, the expanded driver hash, and the same 369 imports before any original-attempt marker. Chrome is 151.0.7922.71; remote Node is v24.22.1. The original attempt marker is written once at 12:00:49.656Z within the immutable 12:00:47.790–12:25:47.790Z window. Chromium launches and the original guest instantiates the exact module above. The launch dependencies missing from the predecessor are resolved. Optional shell build-info/favicon/app-icon requests return 404; they do not prevent the original licence dialog from appearing.

Personally inspected startup.png and response-00.png show the original Aranna EULA. One ordinary absolute pointer move, authenticated against the fresh response-00 owning Worker/module and geometry, completes at 12:01:57.215Z. Canvas (164,427) maps to browser (174,587), over Accept. The capture age at validation is 11.511 seconds, inside the unchanged 15-second guard. This is pointer movement in a licence dialog, not player movement or an attack. No native button or keyboard input follows.

The concrete first blocker is the next read-only Boat exec used to hash response-01.png and its state. It does not return within the CLI's 20-second remote / 35-second local timeout. Its remote outcome is unavailable; the invocation is not replayed. Without the next personally inspected fresh capture, no click is published. No guard, deadline, observer quota, guest state, original media, configuration, save, clock or DLL is changed. There is no demonstrated emulator mismatch or emulator repair.

The distinct terminal quit command completes normally at 12:03:18.113Z. All 2,998 staged pins still match afterward. Terminal evidence retrieval recovers and SHA-verifies 43 files (2,775,152 bytes), including the exact 2,221,881-byte live module. The subsequently recovered response-01.png was personally inspected: the pointer is over Accept and the EULA remains open. It was unavailable for gameplay review before freshness expired. The inspected terminal.png shows the guest stopped. Neither image proves world gameplay.

Remote cleanup confirms all 11 recorded PIDs absent, both ports (40487 and 45913) closed, the temporary browser profile absent, all three runtime locks free, and writer/input clear. The task explicitly delegates normal nonforced box shutdown; its stop request is recorded after evidence retrieval. The terminal API confirms archived, stopped at 12:04:35.313Z, stop completed with forced:false, and expiry null. No box remains in this worker's custody.

Only this investigation note is published. Focused validation covers local pin recovery, complete staged size/SHA checks before and after launch, import resolution, syntax, inspected evidence, and cleanup. Production code is unchanged; no full-build or gameplay qualification is claimed. The next step is to make capture delivery reliable inside the existing 15-second guard before another authorized original attempt. Passing control suites remain inherited and should not be repeated.