Redline single traced fixture: startup terminal, 1295

The one authorized native fixture attempt terminated before any keyboard input or capture. At 2026-11-09T12:21:55.887Z the existing startup gate refused DevToolsActivePort unpublished after 100x100ms poll (observed elapsed 10033 ms, 100 polls). No comma600 command, capture ACK, ordinary quit ACK, period, original game or retry occurred. There is no successful capture to inspect. Keyboard delivery, EventDispatch attribution, latency-flow correlation and the earlier comma cause remain UNKNOWN. Native remains REVOKED; allwriters and edictABA remain UNKNOWN. SingleTaskSTOP.

Evidence is scratch/runs/20261109-redline-traced-native-fixture-1295/. The worker changed only this note and its ignored run inputs/evidence. Production tools, shared clients, custody, Q2/Q3, host, WAT, Heroes II and CLAUDE were not edited. No agents, workers, local Chrome tests, source archives, repeated media/module evidence copies or public deployments were created.

The exact source base is 45c59ace43385a845b90b5a6f2ee7412d353d692; the published 889a18716 trace tool and its 1265 note were used unchanged. Fresh --prepare inputs pin 893 providers (149021585 bytes). git-base.txt, relevant-uncommitted.patch, owned-inputs.patch and the note patch record Git plus small run-specific inputs. Existing media and modules are referenced by original paths and SHA-256 in runtime-pins.json; their required runtime staging is separate from evidence. Retained orchestration providers are recorded by path, size and SHA without copying them into this run.

Before allocation, both the board release and API confirmed Q2 bx_vkc8ygzp, UUID 73881327-5a8f-45e1-8654-be4b78254b9b, ARCHIVED/PHYSICAL_DRAINED, completed unforced stop stop_22c93d116b808404 at 12:15:24.514Z. No Q2 work was altered. One immutable 25-minute UUID deadline was then prearmed with an observable independent watchdog, live process identity and heartbeat. The existing controller also prearmed its process-group watchdog. Local and remote pin barriers matched. The only native entry was the published trace tool's whole single-comma controller under the existing finite kernel custody supervisor.

Launch receipts retain /usr/bin/google-chrome, its actual argv, pid 8647, startup duration 10 seconds, task-owned trace path, Node monotonic/wall/time-origin/hrtime anchors and 166.446 ms spawn-call elapsed time. Spawn time is not readiness. The wire recorder retained its terminal time (Node monotonic 13898.308539 ms) and anchors, with zero input records/raw frames and no drops. No CDP page session or keyboard request IDs were reached. The configured immutable trace window was neither extended nor retried; no observer was added. There is no flushed trace artifact in the final inventory, and retrieval explicitly refused because joined browser stream EOF was false. Missing trace and missing comma preclude EventDispatch/target/clock/latency-flow attribution.

The retained shutdown evidence reports a late DevTools publication on port 43407 after the terminal gate; it was used only by existing filesystem/socket cleanup. No late CDP connection or input followed. This does not establish why Chrome missed the gate, whether trace instrumentation caused delay, or the cause of any earlier native keyboard failure. Startup was not relaxed.

The existing no-input shutdown waited for the browser, which ended with SIGKILL; streamEOF:false, streamsTruncated:true are retained, not promoted to successful browser EOF. Caller and controller watchdog both exited 1; their actual waits and separate stdout/stderr EOF are recorded. Kernel custody completed with 155 actual reaps, no remaining/unreaped processes and no custody failure. Ports 36791 and 43407 were closed; no profile processes or writer locks remained, and the profile was removed.

Unique retrieval retained 26 inventory rows / 24 distinct SHA-size pairs, plus the separately hash-verified final cleanup receipt. Large text was compressed remotely before transfer; all unique bytes were reread and SHA-size verified before normal box shutdown. Gzip validation explicitly found two invalid browser artifacts: ten-byte incomplete chrome-stderr.gz and zero-byte chrome-stdout.gz with no gzip member. They were preserved unchanged. The first existing cleanup command refused while decoding that stderr; the run-specific continuation used the same no-input cleanup, recorded the gzip error and finished physical drain without repairing evidence or issuing browser commands. Initial retrieval similarly refused on the bad gzip; continuation fetched only missing unique files, verified existing bytes and retained per-artifact CRC failures. Valid custody journal/command gzip streams were checked against their uncompressed SHA-size receipts. independent-retrieval-verified.json explicitly limits its verification to bytes, physical drain and actual controller waits; it is not fixture success or browser EOF.

Offline checks passed: exact old/new raw-wire controls, sink/capacity/session/out-of-order/late-reply cases, actual launch-site argv checks, no-input trace retrieval controls, and six whole single-comma inert controller cases preserving independent UP, sticky first failure, capture ACK and terminal bounds. flock /tmp/wine-build.lock bash tools/build.sh passed. The initial local no-launch preflight omitted BROWSER_DEADLINE and was refused before Chrome; the corrected no-launch invocation passed all 893 pins. Both invocations and their actual waits/separate EOF are retained. No native retry followed the startup failure.

Final runtime: bx_vu6j5kxj, UUID f67904f5-7a1b-4a7c-8cda-01c869296506, API ARCHIVED and physically drained. Initial archiveAfter was 2026-11-09T12:43:26.114Z; final archiveAfter:null; expiresAt was not returned. Delegated normal stop stop_98cac7ffc9693ef9 completed 2026-11-09T12:23:51.927Z, forced:false, error null. The box was neither resumed nor deleted. The independent runtime watchdog and lifecycle supervisor both exited 0 with actual waits/separate EOF and released the local runtime lock. Exact final state/expiry/stop data is in final-uuid-state-expiry-stop.json. /home remained above 1.5 GB free.

Next: offline review of the retained startup evidence only. This completed task authorizes no new runtime, trace extension, input, capture or retry.