Q3 observed input native fixture, 1055
Integrated 0da998bf82af wire observation with corrected 11f0fbc7
physical-fixture composition in fresh run inputs only. All three actual
generated invocations and runtime preload orders passed offline checks:
composition, wire observer, execution boundary. Fresh 927-provider pins,
dependency/input/prelaunch checks, 15 inert wire scenarios and the locked build
passed. Reused 27 unchanged proof references were SHA/size/gzip-verified;
inert results are not native proof. Shared callers, custody, Q2, Redline,
host and WAT were unchanged.
Both exact predecessor archive/drain releases were received and API-verified
before allocation: Q21040 UUID 348dbc99-5ccc-45f0-bc6c-f70dd63199dd,
stop_e2eb1f4df06800fb; Redline1050 UUID
1e82aeaf-4307-4c24-9261-ee19593e2763, stop_5f822093e343645e.
Waiting used a board listener without repeated source/runtime checks.
The actual fixture crossed the previous delivery boundary. Enter DOWN request
109 and UP request 113 have socket entry/return and successful raw matching
replies for the same session, before pending-map removal. DOWN reply elapsed
3.726ms; independent UP submission elapsed 100.736ms, reply 103.436ms.
The unchanged 100ms origin/caps were retained. The independent physical reader
recorded commanded VK13 at 32768 in a wholly held sample, then zero on release,
with identical renderer/reader/worker/module/endpoint source identity. The
actual input-positive-webgl-hold.json reports fixturePhysicalGate: PASS.
Positive capture and ACK0 succeeded. The reviewed capture is a generated red
triangle; it establishes no original-game consequence. Socket return is not
flush/receipt/application proof. Browser service time, application time,
callback failure and guest polls remain UNKNOWN; no separate trusted-DOM
event timestamp was retained.
The whole fixture did not pass. Its first unexpected failure at
10:55:58.624Z was the replacement negative control: spreading the renderer
loses its inherited physical reader, so admission throws
TypeError: w?.renderer?.peekKeyDownState is not a function instead of the
expected identity-change refusal. Missing-context and wrong-owner controls
passed first. No local-controls completion, ordinary fixture quit,
cancellation probe, original movement/fire/torch, later guest input/capture or
retry followed. The wire observer's transport-terminal field remains null:
the sticky first failure is the browser assertion, not a fabricated transport
failure. A future gate must read the actual success receipt's -hold.json
name; this run never reached the later whole-fixture gate.
Independent no-input cleanup reaped all 254 owned identities with complete command EOF, no unresolved entries, closed ports/profile/writers and normal Browser.close ACK with exit0 and no signals. Local callers and generated parent have actual waits and separate stdout/stderr EOF. Prelaunch/runtime wrappers retain combined EOF only; the fresh cancellation gate explicitly rejects that as separate-stream proof. Safety cleanup is not the actual Boat cancellation prerequisite.
Box bx_66q35u3g, UUID e17486c0-a7b0-434b-aea0-c5fb359d76f3, had initial
expiry 2026-11-09T11:19:20.408Z. Its immutable 25-minute UUID watchdog was
observed alive before create; actual wait0 and separate EOF are retained.
All 67 unique evidence contents were compressed before transfer and
independently SHA/size/gzip-verified before delegated normal stop.
stop_38df34ebb9c9f1a7 completed unforced at 10:56:24.843Z:
ARCHIVED, PHYSICAL_DRAINED. Final archiveAfter is null; expiresAt not returned.
Evidence: scratch/runs/20261109-q3-observed-input-native-gameplay-1055/.
Recovery uses exact Git base plus small binary patches; no source archives,
media or module copies. Free home remained above 1.5GB. Next is offline repair
of the replacement-control admission boundary, then separately authorized
whole fixture and actual owning-caller cancellation proof before gameplay.
Native REVOKED; allwriters/edictABA UNKNOWN; actual Boat cancellation
NOT_PROVEN. SingleTaskSTOP.