Aranna fresh world action: release preflight blocks allocation

Ordinary player movement or combat remains unverified. Before allocating a box, a read-only check of the resolved retained input adapter found that its mouse release has no independent deadline. This is a harness readiness blocker, not a demonstrated emulator mismatch. No box, Chromium, guest, or input was launched for this run.

Evidence is scratch/runs/20261107-aranna-fresh-world-action/ (R). node R/release-readiness.cjs exits 2 with the concrete failed requirement. It loads the actual point-transform adapter through its retained wrapper chain and checks the resulting dispatch function. The button branch awaits page.mouse.down(), records downCompletedAt, then starts its 60 ms wait; page.mouse.up() runs in the following finally. A pending down promise therefore prevents both the timer and release from being reached. The down await also precedes that try/finally. The resolved lifecycle wraps launch, capture, identity, and shutdown; it supplies no separate input release timer. R/release-readiness.json records the resolved function hash, offsets, and loaded helper hashes. This source-flow check does not demonstrate an actual stalled Chromium acknowledgement or stuck guest button.

The requested complete native-input/capture/review/dispatch qualification in real production guest/render Workers consequently remains unperformed. Positive guarded acquisition, balanced relative movement and mouse action, exact ACK, independent release, and reason-specific stale/replaced-owner/ recentring transition negatives have no new browser pass here. No fresh screenshots or causal world-action pair exist for this run. Allocation was held at this first concrete blocker; no immutable browser deadline or box lifecycle is claimed qualified.

No production or harness behavior was changed. Freshness remains 15 seconds; pointer-lock, mapping, identity, native target/provenance, quotas, and UNKNOWN closure remain unchanged. No retained receipt was replayed, and the previously established capture-expiry diagnosis was not repeated. The restricted base Dungeon Siege lane was untouched. There is no FPS, audio, or parity claim.

The unchanged 1,921-entry recovery manifest, 2,274-entry final retained runtime manifest, and original licence authorization are preserved as metadata, with their exact hashes in R/preserved-inputs.json. They describe retained inputs; they do not certify a new runtime or substitute current main for the old module. No source/media archive or game-media copy was made. Current checkout SHA, relevant binary diff, and patches for this run's new helper and note provide Git-based recovery.

Next work must provide independently timed balanced release and qualify the entire final staged path in real Chromium production Workers before allocating the one original attempt. Then use fresh personally reviewed captures within 15 seconds for ordinary acquisition and world action. This run owns no box, PIDs, ports, browser profile, writer, or native input to hand back. Box ID, state, and expiry are not applicable; no existing box was stopped or resumed. Evidence validation and publication are recorded before R/result.json is written last.