Quake II headroom-restored gameplay, 2026-11-18
Run: scratch/runs/20261118-quake2-headroom-restored-enemy-gameplay/.
One fresh original reached ordinary Game → Easy and visibly moved from the
starting room to the damaged lower doorway. Living-enemy encounter, attack,
combat consequence and ordinary Quit remain unproved. No fire was sent.
The already-present body near the doorway is scenery, not a credited kill.
The scope permanently closed at 2026-11-18 12:20:55.059 UTC, when the
independent reserve monitor measured 1,500,983,296 bytes free on /home.
A subsequent host check saw 1,074,511,872 bytes, below the required 1.5 GB
floor. This run therefore does not claim the floor was maintained. The
concurrent writer is unknown. Later headroom recovery did not reopen the scope.
The proposed next preparation was refused locally before a command or endpoint
request. There was no replay, second original or endpoint request after closure.
Published runtime and actual readbacks
The served source graph was pinned to published Git
f6962ba5b1cf2829a66f5cc4d80b293c30719b37, with only lib/renderer.js selected
from 06f27181f9c977cd1aed99270040efddca00ed75. Admission came from that same
repair commit. The retained module was unchanged:
a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8.
All 67 registered media/control hashes were verified before and after runtime.
Git, exact pins, relevant binary diff and the retained module recovery path
supply recovery; no source snapshot or media copy was made.
The repaired renderer ran successfully on the affected original: 17 production current-display readbacks passed their live checks and the offline metadata recheck. Sixteen used retained publication pixels, and one used an ordinary publication after request. The new unretained, request-held, clean-completion branch was not exercised. This is original gameplay evidence for the repaired runtime, not a new causal native qualification of that branch. No native readback blocker occurred and no production code was changed. The predecessor's focused tests, Chrome contracts and locked build remain predecessor evidence; no fresh build or broad qualification campaign is represented here.
The original registry, GL route, +set vid_ref gl +menu_main, relative mouse
controls and 10,000-block cooperative schedule were preserved. Browser profiles,
cache and temporary paths used published 2a1afa6c4 tmpfs helpers, with component
updates and background networking disabled. The whole display was captured
without storing raw XWD files. Child module/role attribution and physical GPU
execution remain unknown. There were no map, save, config, media, clock, AI,
solver, forced-focus or polling changes.
Inputs and selected consequences
A personally reviewed host fullscreen consent preceded guest input. Nine guest gestures were delivered: two menu Returns, four W movements, A and D sidesteps, and one left-arrow turn. Seven further prepared intents expired locally with zero dispatches. Every delivered gesture had a prepared independent release process; ARM acknowledgment preceded DOWN, holds were at most 1,500 ms, fallback was 1,750 ms, and each matching release reported physical zero. Five-second play and thirty-second menu freshness were checked at the actual socket boundary. The audit retains the actual request/whole-frame ages.
Selected complete screenshots are original/wholehost/forward-06.png (starting
room), forward-07.png (approach beside the support), right-10.png (lower
opening), forward-13.png (doorway centered after the turn), and
forward-14.png (inside the damaged opening). Health remains 100. Sparks and
weapon idle animation are not credited as combat. The final W delivery has no
subsequent reviewed frame because the disk closure followed it; its additional
consequence is unknown.
The first full-size review attempts expired before movement. A run-local
whole-frame preview then reduced display size while preserving the original
1280×1024 screenshots and the unchanged freshness check. Its first resize
attempt failed because sharp was unavailable; pngjs supplied the preview
instead. That intent expired without input. The post-closure failed preparation
left the prior preview image on disk; it was not used to justify another action.
The offline audit's first invocation incorrectly used today's time for historical
freshness and failed; its corrected replay uses each recorded completion time,
while separately checking actual delivered socket ages. These were local
harness/audit corrections, not guest behavior changes.
Lifetime and evidence
The sole original launched at 12:16:23.606 UTC with a fixed 1,200-second total, 180-second startup and Quit reserve, and 20-second cleanup allowance. Disk preemption ended it early. The ordinary Quit reserve does not override permanent UNKNOWN closure; host cleanup is not native Quit.
audit.json verifies zero post-closure requests, all delivered ages/releases,
17 historical readbacks, selected PNG decoding, served renderer/module hashes,
media continuity and 63 absent runtime PIDs. Twenty-three retained actual child
waits include both stdout/stderr EOFs. Chrome exited 0, the browser driver and
native supervisor exited 1, and the disk watchdog exited 0. The supervisor
reports no leaks; private tmpfs and X display resources were removed. The outer
invoking tool returned 143 without original-enclosing-wait.json; its separate
launcher wait/EOF is unknown and is not inferred from inner waits.
Only seven selected whole screenshots and one derived readback PNG remain.
Redundant image hashes and removals are recorded in storage.json; 41,618,574
bytes were recovered from this run's own images. Closed protocol logs were
compressed with exact gzip roundtrip checks and recovery instructions. The
independent finite monitor covers offline sealing separately; its final minimum
and actual joins are recorded in result.json, without erasing the floor breach.
Box ID null; state NOT_CREATED; expiry null; stop receipt null. No agents,
workers, boxes, Python, Wine reference run, deployment, foreign cleanup or held
resource changes were performed. Ownership is released and this worker stops
with the original permanently closed. result.json is written last.