Quake II current custody integration and upper-route gate, 0900
Q2 production composition now requires the exact tested custody provider from
c443739b5e27d85fe434d54cd3e4c45eb51fc833, SHA256
05b7fe42cf7ac09df5f12f0ea073ea066892efb598b64b05fae19a3492c9f32c.
Drift fails before either fixture or original starts. Code is published on main
as 3af071d402f50ba55eb91d5343c823281034a94b.
The actual native browser now passes ordinary joined quit, but the preserved
caller rejects clean launch stderr EOF after quit ACK. Whole fixture failed;
no original, upper-route action, guard or onward door was attempted. The first
unexpected runtime failure was terminal; no later input, capture or retry ran.
Evidence: scratch/runs/20261109-quake2-current-custody-upper-route-0900/.
Integration and offline corrections
The 723-provider frozen closure stages committed custody c443739b5, caller
1473c5952a52d5d2b4546b93a0d462b64fe5c6cd, reader 5bc5f86 with terminal
repair 4ba9f3a1b08c11219c50023f4abffb3bf6c6f9cf, and historical host/Worker
providers. The efdcad9a staged-root repair is preserved: fixture bytes match
0820 exactly and the actual launch branch supplies the authenticated root
/home/user/q2-current-0900. CPU remains 2185596 bytes, SHA256
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295.
All 21 actual composed-driver scenarios pass, including the added custody drift refusal; the locked build passes. Existing exact-source accepted reader, caller, retirement and close proofs were SHA/size verified and reused (63 references), including c443739b5's actual caller/driver/close/ptrace oldFAIL/newPASS proof. This is not a duplicate qualification task. That proof's successful quit ACK does not establish orderly completion of the retained full PIPE controller.
Run-input invocation fixes were implemented offline. The direct Node preflight
now supplies the explicit root and authenticates frozen providers through Git
rather than comparing them with current peer files. The actual generated parent
invocation passes from unrelated cwd /home/user; missing/wrong roots fail
before Chrome. The PIPE-controller's two EOF controls pass with actual child
waits and separate EOF. The first offline invocation was refused by the peer's
runtime lock and was deferred until release; initial logs are retained. None of
these offline invocation corrections retried a runtime. Outer logs drain to gzip
from their first byte.
Actual fixture and first terminal blocker
Strict flags, native keyboard/type/combo preflights and preCPU/preDLLmain owner,
module, instance, endpoint1 and slot0 gates ran. Zero execution entries and
NOT_ARMED native stores precede release. Startup identifies Worker target
67D06E6BD42462E444327A80A0C4A14A, instance
7c90b8a2-1687-44f5-a184-c623eff39532:1, with the exact CPU hash above.
I personally reviewed startup, fixture-comma and fixture-period PNGs. They show
the expected authored idle fixture desktop/readme, not original gameplay.
Each 500 ms command explicitly sets requireMotion:true and captureHeld:true.
There are three comma and four period wholly-held physical-high SNAPSHOT
samples. A fourth comma sample straddles release and is excluded from that
count. Both reverse releases ACKed; fresh post-action captures show physical
keys zero, and numbered command ACKs 0 and 1 pass. Received-frame bytes are
authored fixture state and prove neither original consumption nor contact.
Ordinary quit receives numbered ACK 2 at 09:08:03.610Z. The browser close
receipt is closeRequest:ACK, normal:true, no signals, exit0/signal null,
drained true, elapsed 930 ms, cap 19800 ms. The remote supervisor and
caller parent each actually wait0 with separate stdout/stderr EOF.
At 2026-11-09T09:08:04.627632Z, the local caller latches
owned launch transport stdio EOF: 1. Here 1 is the stderr stream index,
not the launch exit status: the launch transport actually waits0. The preserved
1473 Session's launch EOF callback unconditionally calls fail; its input loop
continues waiting after successful quit ACK. The local PIPE caller therefore
actually waits1. This is a concrete caller completion blocker, despite the
successful browser quit. No cap, EOF requirement or failure classification was
relaxed, and the caller was not modified. Independent no-input cancellation
joined the existing owner. All five local caller children actually wait0 with
separate EOF; the controller actually waits1. No original controller exists.
Evidence and lifecycle
Before create, exact Redline0856 UUID df37f243-b2f7-49d8-88ab-db02200d6141
and Q30856 UUID c465b205-2314-4765-9b8f-4527fc179943 had ARCHIVED
PHYSICAL_DRAINED releases. One box: bx_4nngv8ma, UUID
58edf026-2407-456f-8a64-9e5ce76dc817. Independent immutable watchdog was
observably armed 09:05:01.677Z, before create, with 25-minute deadline
09:29:54.964Z. Initial expiry/archiveAfter: 09:29:54.710Z, TTL1486.
Fixture inventory has 78 rows/55 newly stored unique contents; root inventory has 81 rows/3 additional unique contents, reusing fixture evidence. Every row was independently SHA/size reread before archive. All 11 remote gzip rows pass GNU gzip CRC and independent decompression/hash. All five remote PNG rows are covered by verified hashes and three distinct stored PNG CRC/decompression checks. Custody has 173 owned / 173 actual reaps, complete true, command-log EOF true, and no remaining/unreaped/unresolved entries. Each reap matches its recorded before-reap witness. Ports 36531/38947 are closed, profile absent, FD writers empty and runtime/input locks free. Absence is not wait proof.
Final state ARCHIVED, stopped 09:09:30.332Z. Stop receipt stop_6bb0cfe8684bf5df, completed 2026-11-09T09:09:30.350Z, forced false, error null. Final archiveAfter null; expiresAt not returned. Allocation watchdog and lifecycle supervisor actually wait0 with separate EOF; board tail actually waits -15 with separate EOF. PHYSICAL_DRAINED was posted at 09:10:04Z.
Recovery uses Git base plus small production/run-input patches and existing media/module path/SHA references; no source/media/module archive was made. Free /home remains above 1.5 GB. No agents/workers, local heavy browser, deployment, shared custody, peer host/WAT, Q3, Redline, Heroes II or Claude edits. Native lifetime remains REVOKED; all-writers and edict ABA remain UNKNOWN. 0635 damage cause remains UNKNOWN; no descent, crate turn, ladder or Space assumption occurred. Next is a scoped Q2 orderly-caller-completion correction that preserves cancellation, before any newly authorized original attempt. Single-task STOP.