Aranna acquisition before arming, 2026-11-07

The unchanged registered original passed the ordinary EULA, Main Menu, Single Player, Start New Game, Choose Hero, name entry (Aranna) and Normal difficulty route. It stopped at the first concrete blocker: “The selected map could not be loaded.” The game returned to Choose Hero with that modal. World gameplay and character movement remain unverified. No implementation defect was established, and no code or input guard was changed. Capture retirement fix 727eb72cb remains intact.

Evidence is in scratch/runs/20261107-aranna-acquire-before-arm/. The predecessor's actual terminal, explicit final release at 04:07:45Z and coordinator terminal verification at 04:08:14Z were read before this run. Graphics released at 04:09:23Z and Lords2 at 04:10:34Z. The actual four-lock supervisor then held the source/build/local-runtime window from 04:11:00Z through cleanup, within the inclusive 35-minute limit ending 04:46:00Z. No agents, workers or boxes were created.

Focused control and corrected order

The existing small generated control ran first with the retained production-shell input adapter, one-way observer and qualified standard module. Trusted acquisition completed before observer arming. A real native manager store at (399,155) and a complete positive hover transaction proved the Single Player target before its balanced click. The visible control changed to Start New Game, matching generated sequence stage 1 and DOWN2/UP2. Ordinary Space then disabled relative intent; the deliberately stale generated-only relative ticket was refused with zero effects, unchanged pointer/native point and no replay. This reran only the focused sequencing control; the retained broader standard/compat controls were inherited.

Control Quit6 and Chrome exited 0. Ten control PIDs, both ports and its profile were absent before the gate allowed the ONE original. All four actual locks remained held. control-approved.json records the checks. All eight control screenshots were inspected at their original 1001×800 resolution; transient black GDI captures were not treated as completion. All seven active captures have matching state. The terminal PNG shows Ready, but its generated-only state readout failed after shutdown (capture-error.json); no terminal state is invented. Two initially inaccurate capture descriptions were corrected explicitly in their owned review files.

The original reached the visible Main Menu in response-12.png. A trusted balanced click in the clear left margin acquired screen pointer lock in response13 without changing the menu. Only then did command14 arm the observer at 04:17:43Z. An ordinary bounded relative movement produced actual manager point (79,399); read-only planning moved it to (399,155). Response16 visibly highlighted Single Player, with complete native positive-hit transaction279, exact loaded target provenance and balanced return. Command17 activated it with a balanced click. No native point was fabricated.

The retained full hover proof is scoped to the first Single Player target. Later actions followed the already qualified later-action guards, measured native manager points and reviewed visible targets. Natural lock release during menu transitions was handled through fresh trusted acquisition, never absolute movement while unsettled. The final Normal target was measured at (399,295), with fourteen manager stores below the unchanged bound. All original commands completed: 39 receipts, 20 input actions, ten balanced mouse gestures and three balanced Escape presses. There were no input UNKNOWNs, replay, held buttons, repeated arming or relaunch.

Visible route and first blocker

All forty original 1001×800 captures have matching state evidence and were personally inspected. Key checkpoints are:

Progression stopped immediately at response37; the modal was not dismissed. Passive retained loading evidence covers expansion.dsmap, expansion.dsres and logic.dsres. Between Normal and the failure capture, 436 observed broker completions contain no nonzero broker errors or read mismatches. This does not prove every load operation succeeded or identify the cause. Existing decision/API observations remain in original/observations.jsonl; load-phase-summary.json indexes the observed failure path. No guest, media, save or configuration file was edited.

Exact identity and cleanup

Runtime source identity is Git ea81b0a3baa4d73d80bbe8baaf37c409fb8b5ac3, with source-identity.json, the relevant binary diff and owned new-input patches. Qualified runtime JavaScript matched the inherited controls. Worker debugger bytecode confirmed the actually instantiated standard observer SHA-256 e7d6617cecdf3275db05454763c07cad7e6eb557afc2a14ca3413d960328fd31. Other retained pins are standard baseline 07f1cc970038f8ab31313b8b200edf26caa63473f293f5fc937f5cfe5c5c7f6e, compat baseline 1d4bd4330ea16947959e3f4472339d5a32a61216cd8b5246198d11046b652c3e, and compat observer 6b5edb202b5e03d84056b8663869f8485de2b5a7d592ece0e350dc43a88a005d. No current full-build module was substituted. Active original evidence retains owner slot0/endpoint1, target 2C2F131E5BFAB72B097023DC7148B2F4, session 4402A3BCAF0373F1567412D9E0748207 and that exact module. Unknown/retired auxiliary identities were not assigned to the owner.

Normal Quit38 completed at 04:25:30Z; Chrome and the original Node driver/server exited 0 at 04:25:31Z. Ten original PIDs, HTTP39587/CDP40555 and its profile were absent while holder1410358 still held all four actual locks. Source postcheck and all 28 media size/SHA pins passed before release. After the release marker, the outer exec shell reported terminal143; its cause is UNKNOWN. This is separate from the recorded successful child/Chrome terminals. The holder was independently absent and all four locks independently free at 04:25:52Z. The board's earlier holder-PID typo and overbroad terminal wording were corrected explicitly.

The source/build/local-runtime window was explicitly released at 04:25:52Z, about fifteen minutes into the inclusive bound. Both sessions' processes, ports and profiles are closed; the owned board watcher was terminated separately. Free disk was 2.73GB at release, above the 2GB floor. No box was assigned or created: ID/state/expiry/ownership are none. No source/media archive or deployment was made.

Next work is causal diagnosis of the retained map-load failure before another separately authorized original. This run makes no world, movement or gameplay-support claim and stops after evidence publication.