Q3 corrected controls native attempt, 1130

Integrated published dc66e5df4 prototype replacement/reader-malformed repair with 11f0fbc7 physical fixture and 0da998bf82af wire observation through fresh Q3 run inputs only. The 927 fresh pins, three actual generated invocation checks, composition/wire/execution preload order, complete nine inert controls, dependencies, input evidence, delivery, 15 wire scenarios, cancellation, startup, and locked build passed. The corrected gate reads actual input-positive-webgl-hold.json; cancellation still requires actual wait plus separate stdout/stderr EOF. Combined-only/missing/false-wait controls refused. Rehashed 27 unchanged proof references; inert tests are not native proof. Shared clients, custody, Q2/Redline, host/WAT and input limits were unchanged.

Waited for exact Redline1120 UUID df8a2f5b-3eb8-4ff7-9ccd-3abb0165c5ec, box bx_zmrpm83m, release and API-confirmed ARCHIVED normal completed unforced stop_55ad83ebff98fc33 before allocation. The board listener did not repeat source/runtime checks. One new box had an observable independent immutable 25-minute UUID watchdog armed before create; no local browser or second box.

The first concrete native blocker was positive fixture Enter100ms delivery: input delivery exceeded hold bound; DOWN reply UNKNOWN. Its delivery receipt firstFailure is 11:13:55.746Z (elapsed 101.073ms); transport terminal is 11:13:55.750Z, browser failure .753Z. DOWN request 193 and independent UP 194 have same-session socket entry/return. UP submission elapsed 100.251ms; there is no raw matching reply for either request before terminal. Both promises reject on terminal at approximately 106ms. Socket return is not flush, browser receipt, physical hold or application proof. No samples were recorded; actualHeldInterval, guest polls, browserService, application and callback failure remain UNKNOWN. The retained startup capture was personally inspected: red generated fixture pixels on white, with no original-game consequence claim.

No positive capture/ACK0, nine native controls, ordinary joined quit, cancellation probe, original movement/fire/torch, later guest input/capture or retry followed. The earliest retained failure stays sticky. Trace verification found no later Input or capture entry. No correction or second native attempt was made. Whole fixture NOT_PASS; actual owning-caller Boat cancellation NOT_PROVEN. Local safety cancellation does not satisfy that prerequisite.

Independent no-input cleanup reaped all 165 owned identities, complete command EOF, no unresolved entries, ports closed, profile absent and writers drained. Normal Browser.close is UNKNOWN; the root exit was -9 after terminal cleanup. Local caller and generated parent have actual waits and separate stream EOF. Prelaunch/runtime retain combined EOF only; the cancellation gate still rejects that as separate-stream proof. Nonleader completeness remains UNKNOWN.

All 58 unique recovered artifacts were compressed before transfer and independently SHA/size/gzip-verified before delegated normal stop. Box bx_7qr5v9tq, UUID ad488975-a20c-4d24-a602-2492a1501cf5, initial expiry 2026-11-09T11:38:07.314Z, is ARCHIVED, PHYSICAL_DRAINED. stop_17435ea1ce1bcb6f completed unforced at 11:14:46.012Z. Final archiveAfter is null; expiresAt was not returned. Watchdog actual wait0 and separate EOF are retained; lifecycle lock released.

Evidence: scratch/runs/20261109-q3-corrected-controls-native-1130/. Recovery is Git base 8d7443761494bc1f643538c118ce0f2ded2c13ce plus small relevant/owned patches, reverse-checked; no source archives, media or module copies. Free home stayed above 1.5GB. Next is offline diagnosis of the retained DOWN/UP native reply boundary, then separately authorized whole native fixture and actual owning-caller cancellation before original consequence. Native REVOKED; allwriters/edictABA UNKNOWN. SingleTaskSTOP.