Quake II fresh remote startup blocker, 2026-11-08

The one fresh authorized remote run failed before CDP connection and original game launch. No current game pixels, native game input, threshold passage, or onward progress were obtained. The upper northern opening remains unqualified. This is a concrete startup blocker, not a preparation-only completion. No retry, second allocation, or inherited UNKNOWN replay occurred. Evidence is in scratch/runs/20261108-quake2-current-opening-2025/.

The actual unchanged repaired 2007 browser and launch consumers were selected at Git 0ce4835928398cb56003fc93221aae136e122db7: 706 providers totaling 109,891,849 bytes. The final actual-driver preflight validated every pin without starting Chrome. All 707 uploads, including the manifest, joined before remote validation of all 706 providers and the single launch. CPU SHA remains d8facd0658b7f158c6e60bef2de0936471f438f8bf41e9240fd75635f1d319dc; it was hashed, not observed executing. Kernel e36d34990d738e616611ce8a8f4309548abcb751bd5ef5ec119d20e561c49360 was selected with both explicit journal_compression='gzip' and command_compression='gzip'. Logger 979b3a8b…, readiness 9ba9ae8b…, and close 1f4fe08b… match the accepted published sources. Accepted custody, Node, inventory, exact-launch and locked-build proofs are referenced by path/hash; the same offline preparation was not repeated.

At 20:29:08.615 UTC, the readiness helper reported exactly 60,000 ms elapsed, with last: not published. Its absolute startup deadline was the earlier of 60 seconds and the browser deadline minus the existing 30-second close reserve; neither deadline was extended. No endpoint or CDP connection was accepted. Recovered Chrome stderr contains GPU exit 134, network-service restart, and D-Bus errors; these do not establish the startup failure's root cause. No renderer qualification or Intel/SystemInfo conclusion follows from this run.

Browser close reached its 30,002 ms cap with no terminal or drain receipt, close request UNKNOWN, and SIGTERM/SIGKILL attempts recorded. The profile was retained and no quit ACK was published. After that cap, a PID/start-verified SIGTERM requested cancellation from this run's own supervisor, 7188/22600. Its parent recorded an actual terminal wait with return code 1. The kernel recorded 132 registered identities and 132 matching actual terminal reaps, command-pipe EOF, and finalized lossless gzip streams. However, kernel-drain.json correctly remains complete: false: retired child 8107/30705 lacks resolved fork lineage, and the supervisor ends at the explicit unresolved-lineage assertion. No complete custody claim is made.

The recovered custody stream contains 235,590 original bytes, SHA-256 928fb24b4627fcaf5a8446f236e143fd3b5da1a0ec4cb308d8fc82888d1480da. The recovered command stream contains 879 original bytes, SHA-256 45ca1779ea11726c1901756239c812a7781864281142b390fdf658fad8230468. All explicit command, browser, Chrome, custody, provisioning and watchdog logs were gzip-written from their first stored bytes. The final inventory enumerates every regular artifact without an extension filter, including the command log and retained Chrome profile. Because UNKNOWN deliberately retains the profile, the inventory consumer records its three Singleton symlinks separately and never follows them; selected source omissions require matching hashes. Chrome's internally generated profile files are retained as produced. All 180 files / 2,716,996 bytes were retrieved and checked against remote size/SHA pins. Python decompression and independent gzip -dc verified original SHA/size and CRC for every recovered gzip before the normal stop request.

At cleanup census all 132 registered PID/start identities were absent, the HTTP port 33405 refused connection, and the heavy lock was free. No DevTools port was published. No accessible FD referenced the retained profile; 48 processes had unreadable FD directories, so exhaustive writer drain is unproved. No game input was held or issued. Absence is not substituted for a terminal wait. CLONE_UNTRACED and nonleader-exec coverage remain unclaimed. The detached remote terminal parent's own exit lacks an external terminal-wait receipt.

The UUID was durable before create and ID/expiry durable before runtime. The observable independent watchdog was prearmed before allocation with its immutable 25-minute cap. After verified retrieval, delegated normal stop completed: box bx_nbuk2fjc, ARCHIVED, expiry NULL, stopped at 20:31:35.530 UTC. Receipt stop_93185522ea29c01d completed at 20:31:35.572 UTC, forced: false, error: null. Both local watchdog roles have actual supervised exit-zero waits; their supervisor records no remaining children. Its detached exit is not promoted to an external terminal wait.

Recovery uses the exact Git SHA, empty relevant tracked binary diff, small owned-input patches with reverse checks, and the existing untracked boot dependency's retained patch with a successful reverse check. Media/modules are existing path/hash references. No source archive, local Chrome, old-run deletion, media/module copies, peer WIP changes, old-box operation, guest writes, handler calls, config/backend/binding/clock/seed changes, subworkers, or public deployment occurred. Sampled local free space remained above 1.5 GB; no continuous-floor claim is made.

Historical supervisor 143/cause UNKNOWN remains unchanged. The 187 static BSP controls and bearing near 92 degrees remain preparation only. Full27, parity, audio, FPS and Intel/SystemInfo renderer limits remain open. Next work must resolve the observed remote startup and cancellation-lineage blockers before another separately authorized original run. This worker stops.