MW3 cockpit action attempt — 2026-11-07

This bounded task stopped on the original operation map. Cockpit movement, turning, firing, displacement, ammunition changes and projectiles remain UNKNOWN. No Launch click was sent without a proved target. The concrete boundary is physical pointer headroom in the unchanged published native helper.

Evidence: scratch/runs/20261107-mw3-cockpit-action/. The ordinary route and unchanged tools/dungeon-keeper-native-motion.cjs came from published 102638214. No accepted qualification matrix, nested worker, forced profile, private input handler, guest write, configuration/clock change, timeout relaxation, archive, old-box resume or deletion was used. No production code changed; there was no demonstrated emulator repair or required locked build.

Local qualification before allocation

The exact run-specific browser, observer and numbered transport ran locally against the generated public-COM fixture with actual production guest/render Workers and the pinned executing module. A personally reviewed capture admitted the observer, then an ordinary ArrowUp pulse. Exact numbered ACKs 0–3, armed independent UP, breakpoint removal, diagnostic-buffer deletion, Chrome exit 0, profile/lock removal and closed-child refusal passed. The fixture did not call MW3 GetDeviceState: actual original consumption was tested separately below.

Focused mocked observer controls rejected changed instance, changed module bytes and a wrong completion location before breakpoint installation. Its exact false-returning condition retained simulated pressed/released states and restored its diagnostic globals. A stalled DOWN acknowledgement still independently attempted UP and returned sticky UNKNOWN. Published native-motion tests passed. These are focused closure checks, not repetitions of accepted matrices.

Original route and actual acquisition completion

All 308 inherited pins matched before allocation. The successor's 308 runtime pins matched before launch and after completion; the separately staged boot script has its own path/length/SHA pin. Source SHA, relevant tracked binary patches, owned new-helper patches and existing media path/hash/length references preserve recovery. The executing guest and owning renderer module was e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467, 2,182,493 bytes. This measured module identity does not claim a rebuild at the recorded source SHA.

The fresh original showed the Zipper splash, then Main Menu. A premature read-only startup-image retrieval found no file while capture was still running; its error was retained. A subsequent passive readiness inventory established the completed capture; immutable bytes were retrieved without input replay. The first written review incorrectly called the splash a menu. The correction is retained in the next input review; no input was sent using that splash review. Only the read-only observer was armed from it.

Before the first original press, the observer verified the exact full 470-byte GetDeviceState body and the actual executable location 887941. It attached to the driver's owning guest Worker instance and endpoint, checked the pinned module bytes, and used the driver's existing 18-field owner/module/epoch and 120-second freshness admission. Capture/admission records retain focus HWND 65537; no stronger separate HWND-object admission gate is claimed.

A personally reviewed blank-area acquisition click used physical approximately (513,364). Automatic selection remained true, explicit profile absent, cooperative flags 5, and Pointer Lock became screen. Its 100 ms independent release was armed before DOWN. The observer retained 2,324 actual successful returns, zero drops, all HRESULT 0 and caller 0x4fa56c. Three returns at 15:26:38.819Z, .847Z and .884Z contained left button 0x80; independent UP was attempted at 15:26:38.900Z, acknowledged at .905Z, and subsequent retained returns contained zero. The cursor during those pressed completions was (320,240). Observer cleanup completed at 15:27:01.876Z. This diagnostic observation establishes acquisition-press consumption, not performance.

Fresh personally reviewed captures and ordinary trusted input reached Pilot Entry, typed a, confirmed it, accepted the default Bushwacker/Operation 1A/ Wave 1 setup, and opened the operation map. The transport retained exact numbered ACKs 0–13, 51 trusted native events, independently scheduled UP for every press and no UNKNOWN replay. Navigation was not presented as cockpit action.

First unresolved boundary

The final software cursor was (543,426), tracked physical pointer (691,524), within canvas bounds left/top (10,194), size (684,480). The lower-right icon appeared green but no Launch tooltip appeared, including a passive settled capture. Its immutable SHA-256 is 9e8e472a52c2ad8ee812f63664d44a5cad6925a7c8bddb1251bb2fe5cbd240f4. The predecessor's proved Launch point was software (575,432). Additional rightward native motion toward that point exceeds the physical canvas bound.

boundary.cjs runs the exact unchanged helper against these retained values; its first +8 step is refused as physical step outside canvas, with zero input effects. This diagnostic ran locally after the original stopped taking input. No bypass, reanchor, speculative click or original retry was attempted. The acquisition anchor selected in this run left insufficient rightward headroom; this is a driver-route limit, not evidence of a guest input defect.

Next, if separately authorized: qualify the route locally with a reviewed acquisition anchor that leaves sufficient physical headroom, then arm the actual completion observer before cockpit movement/fire input. This task did not prepare or launch another original.

Recovery and delegated shutdown

All 184 remote artifacts (9,918,379 bytes) were retrieved with SHA/length verification before normal stop. The initial cleanup check caught the driver still exiting and was retained. A later passive check proved both Node and Chrome absent without signals, both ports closed, profile and writer lock absent, and held inputs empty. Chrome exited normally with code 0 at 15:30:40.064Z. Local production-fixture processes/profile/lock were also closed. Sampled free disk stayed above 2 GB; no continuous minimum is claimed.

One fresh UUID Idempotency-Key POST allocated bx_zmshp448. The immutable allocation-response-derived deadline was 15:50:15.539Z; execution ended well before it. After verified evidence recovery, delegated normal stop stop_e918ae790bd04271 completed 15:31:31.113Z, forced:false. The box is archived, current archiveAfter:null; original expiry was 16:25:15.411Z, retained-data expiry unknown. Lifecycle ownership is closed.

Focused closure, observer, motion, boundary, custody, hash and owned-evidence checks passed. The global evidence checker still reports unrelated existing Alice and Tunnel/Twist containment errors. No production repair/build, cockpit action, movement, firing, FPS or parity success is claimed. This single task ends here.