Quake III visible menu focus and actual arena, 2026-11-17

Run: scratch/runs/20261117-quake3-known-menu-focus-arena-gameplay/result.json. One fresh original reached the actual first-person Q3DM1 arena and visibly turned right. The task remains incomplete: forward movement is ambiguous, fire/enemy consequence and ordinary native Quit are unproved. Following Mouse1, the guest Worker logged unreachable at EIP 0x4629e8. The next capture failed its exact registered-app guard and closed UNKNOWN. No input, query, capture, replay or second original followed that terminal boundary.

The runtime reused published source e7c13db296e380130bc6b9771cf3f55970f5c42f and module SHA-256 f40fc54c5b0f1d4bd505364049e091c0092cab27eac0dcb644e8623d2344875b. Fresh CDP bytecode readbacks matched f40, including the actual guest Worker. Owning render Worker endpoint 1 was gl-gps, software, with an actual GpuStreamSoftware.Executor; the turning checkpoint recorded 22,363 draws and 352 presents. Page CPU getters are shadow observations. Published source bodies and four served Q3 media bodies matched retained pins. No broad inventory, canonical build, media copy or game configuration change was made. The run records exact checkout/runtime pins and relevant binary diffs; Git remains the source archive. Foreign AoW/Sims/review WIP was not adopted.

Wholemenus were personally reviewed. Main -> Choose Level (Q3DM1, Major) -> Game Server (Free For All) -> visibly yellow Next -> server settings -> visibly yellow Fight -> localhost loading -> actual arena. No reset was needed. Keyboard focus traversal retained the selected map and settings. Two newly visible signaling-service error dialogs were dismissed with their ordinary OK buttons. Another recurrence remained visible during turning. Local arena loading and rendering continued despite that host message.

The actual viewport was 945x889 CSS pixels, DPR 1. The logical 640x480 canvas had CSS rect left 0, top 34, width 945, height 855, with letterboxed game presentation. Screenshot viewport coordinates were used directly for CDP. The click aimed at Fight was followed by a cursor near Skirmish and Game Server; this does not establish an ownership or conversion fix. No supported fixture proved a coordinate defect, and no conversion was changed.

Twenty-one ordinary gestures completed independent physical-UP witnesses: 17 held 200 ms and four held 1,000 ms. Each retained owner, current reviewed image/hash, freshness, prearm, UP ACK and aggregate bounds. The release service was initialized before PE launch. Trusted browser edges, host production dequeue and visible consequences remain distinct; native USER return tokens were not instrumented. W DOWN/UP were host-dequeued together after release, and the small scene change is confounded by entry settling: forward movement is not claimed. Right Arrow produced a marked rightward view change. Health 125 -> 124 -> 123 is ordinary excess-health decay and is not enemy damage evidence. No enemy interaction was visibly established.

An erroneous Control-as-fire annotation was corrected: shipped CTRL is +movedown, and MOUSE1 is +attack. The filename player-fire-response.png is the Control/crouch checkpoint, not fire proof. The subsequent Mouse1 held 1,000 ms, completed physical UP, and was host-dequeued DOWN. A guest trap followed before the response capture. Static disassembly shows the reported EIP at call *0x7bde6c; neither the runtime call target nor the trapping WASM site was retained. Temporal association does not prove the root cause. No production fix was guessed, and no affected-original allowance was spent.

The independent 900-second deadline/actual 1,500,000,000-byte disk-floor watchdog was prearmed and did not fire. Chrome closed normally (0, Browser.close ACK, both EOFs, no signals). Release service 0, driver 1 and watchdog 0 have actual wait/both-EOF receipts. The outer tool returned 143; the outer helper-wait receipt is missing and remains UNKNOWN. Named owned PIDs were absent and the owned tmpfs profile removed; absence is not wait proof. Individual Chrome descendant wait syscalls were not instrumented. No box was created: ID null, state NOT_CREATED, expiry null, stop receipt NOT_APPLICABLE.

240 focused evidence checks passed; the prior 53 input/lifecycle checks were reused with helper hash verification. Ten selected, personally reviewed wholeimages remain, with hashes/descriptions and the terminal logs. No production code changed. Next work is a focused offline reproduction of the trap/call target before a justified fix and fresh affected-original validation. This original is closed. Released and stopped.