Quake II current startup attempt, 2026-11-18

Run: scratch/runs/20261118-quake2-current-startup-living-enemy-consequence/. The fresh original reached the ordinary main menu. No guest or host input was dispatched. Living enemy, attack binding, attack consequence and ordinary Quit remain unproved. The prior damaged-doorway attempt remains separately closed; its old corpse is not a kill.

At 13:03:39.636 UTC, the published disk guard permanently closed this scope with an actual /home observation of 1,497,882,624 bytes, below the required 1.5 GB floor. The writer responsible for the concurrent decline is unknown. The prepared host fullscreen release was cancelled with zero dispatches. The subsequent proposed host click and Game preparation were refused locally before command publication. There were zero endpoint requests after closure, no retry and no reopening. Host cleanup is not ordinary guest Quit.

The coherent served graph was f6962ba5b1cf2829a66f5cc4d80b293c30719b37, with renderer and display admission from 06f27181f9c977cd1aed99270040efddca00ed75. The helper loader selected 8fd08ea3b browser transients, including explicit UTC, private tmpfs profile/cache/temp paths, component-update and background-network switches. The retained module SHA-256 was a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8; its existing recovery recipe and 81150aeb → f696 source continuity were reused. All 67 registered media/control hashes were verified before and after runtime. No unchanged module was compiled and no qualification campaign was run. Actual executing child module/roles and physical GPU remain unknown; no Debugger gate was added.

The startup used the ordinary registry, GL route, +set vid_ref gl +menu_main and existing cooperative schedule. Selected original/wholehost/consent.png shows the complete private display with Quake II main menu and the host fullscreen button. Raw XWD stayed in memory. No base64 capture, source snapshot, media copy, config/save/state/clock/input-polling/focus change or combat script was used. The prepared operator retains five-second final-wire play freshness, finite holds, independently armed matching physical-zero release, live owner checks and permanent UNKNOWN semantics; no delivered gesture exercised them in this original. Attack bindings were not inspected through the ordinary UI.

The original launched at 13:03:17.922 UTC with finite 1,200-second lifetime, 180-second startup and Quit reserve, and 20-second cleanup allowance. Actual waits include the enclosing launcher exit 1, supervisor/driver exit 1, Chrome exit 0, Xvfb exit 0, openbox exit 0, release exit 0 and watchdog exit 0, each with both pipe EOFs. The supervisor reports no leaks; recorded assigned PIDs were absent and private browser tmpfs was removed. The disk floor was breached; successful cleanup does not erase that observation.

Recovery uses Git, exact relevant binary diffs, owned operator patches and the existing retained module path. Closed logs are compressed only with verified lossless roundtrips. audit.json records served hashes, zero input issues, zero post-closure requests, media continuity, waits and cleanup. result.json is written last. No production code changed, so no new build was required.

Box ID null; state NOT_CREATED; expiry null; stop receipt null. No agents, workers, boxes, Python, Wine, deployment, foreign WIP/cleanup or held-resource changes. Ownership is released and this worker stops with the scope closed.