Aranna final pinned qualification and original gameplay attempt

The previously incomplete exact retained-frontend target action now passes in actual Chromium. Original snowy-world movement or attack remains unproved: the fresh box stopped at a concrete launcher packaging failure before Chromium. Evidence is scratch/runs/20261107-aranna-final-pinned-gameplay/ (R).

The release repair and its seven real Chromium controls from the predecessor were retained by hash, without repeating them. The original-world limitations in the movement diagnosis also remain: stale captures cannot authorize input, and no emulator mismatch has been established.

R/qualification.json records one immutable 25-minute local session. Its server buffered 153 verified retained frontend resources, including the guest and render Worker scripts, before launch. Shared-main drift could not replace those served bytes. The actual guest instantiated observer module SHA-256 88ff2708a2dec89af430fac2ba778f39857c2716e851299c3ecbfa62fd5e7d1f. Both production guest and GL render Workers were present. This generated fixture uses GDI for its visible target; it does not prove original D3D output.

Personally inspected control-pinned/response-03.png shows “Single Player”; response-04.png shows “Start New Game” after one guarded native target click. The capture, exact owning Worker/module, native point (400,155), full target provenance and release receipts were retained. Counters advanced to two downs and two ups, with buttons clear and both exact transport ACKs. Release was scheduled before invoking DOWN. The preceding acquisition even sent UP before the delayed DOWN acknowledgement, without losing either ACK.

Free disk was restored to 2,322,673,664 bytes before Chromium. During the same session it fell below 2 GB and prevented review/target-command publication. No target command was published at that refusal. After recovery, an observation produced a fresh capture and the click passed. No deadline, freshness, identity, provenance or UNKNOWN guard was relaxed. R/local-cleanup.json records normal local shutdown with owned PIDs absent, both ports closed and profile absent.

One fresh UUID-idempotent box, bx_ayh8sjps, was created at 11:38:00.785Z, initially expiring at 12:18:00.621Z. The original 1,921-entry fixture manifest and licence authorization were preserved unchanged. All 2,323 proposed staging pins passed remote size/SHA checks, including the original Expansion.dsres reconstructed from 55 individually verified parts. However, that inventory was incomplete: it omitted launch dependencies. Passing hashes for listed files did not establish a complete launch closure.

The first launcher invocation found its Python supervisor absent. This happened before any original-attempt marker or browser. The prepared supervisor was then added to the manifest and staged; all 2,324 listed pins passed again. The existing immutable original window, 11:45:15.679–12:10:15.679Z, was retained. At 11:46:04.423Z the launcher wrote its one-attempt marker, then R/runtime-http.cjs failed opening the unstaged retained-runtime-pins.json. The server and Chromium had not started. R/remote-evidence/supervisor-staged.log preserves the exact ENOENT and stack. These two omissions are this worker's packaging errors, not evidence of an emulator mismatch.

The attempt marker was neither removed nor bypassed. No original browser, guest execution, native game input, target action or world consequence followed. The restricted base Dungeon Siege lane was untouched. All 2,324 listed pins still passed the terminal SHA check. No guest binary, configuration, save, memory, clock or DLL was edited.

Nine unique terminal evidence files (2,217 bytes) were retrieved and SHA-verified before the explicitly delegated normal shutdown. There were no remote live modules to retrieve because Chromium never launched; the actual locally instantiated qualification module is retained in control-pinned/. Terminal checks found both remote launcher PIDs absent, runtime locks free, no browser profile or runtime ports created, and writer/input clear. Local qualification PIDs, ports and profile were also cleared. R/boat-terminal-state.json verifies archived, stopped at 11:47:28.331Z, stop completed with forced:false, and expiry null. No box was resumed; no running box custody remains.

Git SHA plus relevant tracked diff and owned-helper/new-note patches provide source recovery. Evidence includes the qualifying captures, exact native provenance and ACKs, retrieved instantiated module, manifests and launch logs. No source tree or media archive was created. Production sources were unchanged; this is a documentation-only publication, with no production build claim. Syntax checks, evidence validation and publication are recorded in R before result.json is written last.

Next work must stage and verify the complete launcher dependency closure, including the retained-runtime manifest and Python supervisor, before a newly authorized fresh attempt. The final pinned Chromium target action is complete and should be inherited by hash. Ordinary snowy-world movement or attack still requires a new original run and fresh personally inspected consequence captures.