Quake II current browser movement, 2026-11-18
Run: scratch/runs/20261118-quake2-current-reviewed-browser-enemy-progress/.
The sole original reached ordinary Game → Easy and visibly advanced from the
starting room toward the lower doorway using four manually reviewed W/A/D
gestures. Living-enemy damage/defeat and ordinary Quit remain unproved.
No fire input was sent. The body already visible by the doorway is existing
scenery, not a credited kill.
The concrete terminal cause is shared disk capacity. At
2026-11-18 11:26:57.105 UTC, the shared admission guard measured
1,498,701,824 bytes free on /home, below the required 1.5 GB floor,
and permanently closed the scope. This is an actual floor breach, not a
claim that the floor was maintained. The responsible concurrent writer was
not established by this run. No endpoint request, replay, scope reopening or
second original followed closure; the subsequent operator command was refused
locally. Host cleanup does not establish native Quit.
Runtime and qualified operator
The runtime was assembled in memory from published Git
f6962ba5b1cf2829a66f5cc4d80b293c30719b37, excluding concurrent worktree
changes. Recompilation matched the retained module exactly:
a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8.
prepared.json, media.json, initial-git.json, binary worktree diff and
recovery-before-runtime.json retain recovery/provenance inputs. The original
registry, media and modern controls were unchanged, with
+set vid_ref gl +menu_main, relative mouse declaration and the registered
10,000-block cooperative schedule. No map, console, save, config, media,
clock, AI, seed or forced-focus write supplied progress.
The operator uses the current production display-capture request and exact
document/process/window/canvas/GL endpoint tokens. It retains whole private
desktop screenshots and request-local immutable readback metadata, checks
the owner before and after capture and before input, and preserves five-second
play and thirty-second menu deadlines at the actual DOWN socket boundary.
Heavy Git/media/module recovery happens before capture. It does not run the
historical af8 asynchronous Worker/module recovery and held-paint gate before
every key. Independent child Debugger module/role recovery was omitted;
executing-child bytes and roles remain unknown. The observed presentation
route is the owning gl-gps bridge and ordinary native GL publication receipt;
physical GPU execution is not claimed.
Every Chrome launch used normal Puppeteer defaults, a fresh isolated profile,
a private authenticated X display, and explicit --disable-component-update
and --disable-background-networking. No shared launcher was edited.
The author coordinated the launch flags/module retention on the messageboard.
The declared authored aggregate was 600 seconds, at most two scopes. The first
reached an ordinary native GL display and closed without input while the
run-local release protocol was tightened offline. The second passed personally
reviewed blue → red output from trusted Enter, independent matching UP with
physical zero, and ordinary Escape → guest ExitProcess(0). It used the same
published native GL fixture and runtime graph. The prepared independent
release process now acknowledges a 1,750 ms ARM before DOWN; the requested
hold is at most 1,500 ms. Process/document checks precede preparation, while
the matching release checks the retained document/process even during normal
window retirement. Prior current-display, owner/replacement, UNKNOWN and ordered
input controls were reused; this authored run qualifies the changed operator
path, not combat.
There were no tracked source, controller or test changes, so no new code commit/build is represented by this report. Run-local operators, their seals, the authored qualification and recovery recipes are retained in ignored evidence.
Original observations and limits
One original was declared with 1,200 seconds total, 180-second startup, irreversible 180-second Quit reserve and 20-second cleanup allowance. It launched at 11:21:19 UTC and closed early on the disk observation above. Trusted host fullscreen consent preceded guest menu input. Six guest gestures were sent: two menu Returns, two W movements, one A sidestep and one D sidestep. Seven independent UP receipts including host consent report physical zero. Ten other intents expired locally before DOWN and joined their cancelled prepared helpers. They were not replayed or called successful movement.
Selected complete frames include original/wholehost/forward-009.png
(initial player viewpoint), forward-010.png (first approach), left-012.png
(after the next W, at the doorway), forward-013.png (after A), and
forward-017.png (after D). turn-left-018.png is the last selected whole
world frame; its proposed turn expired without DOWN. These establish visible
world progress only. They do not establish a living target, outgoing hit,
defeat, goal completion or ordinary Quit. Health remains 100 in these reviewed
world frames; ambient animation is not credited as combat.
Audit checks pass all delivered request ages/hold limits, independent physical
neutral receipts, registered media/config hashes, selected PNG decoding,
owner-field replacement negatives and runtime cleanup. All 133 recorded
runtime PIDs are absent. Thirty-eight retained child waits across the authored
and original scopes record actual close and both stdout/stderr EOFs. The
original browser driver exited 1, Chrome exited 0, native supervisor exited 1,
and disk watchdog exited 0. All private displays/profiles were removed and
supervisor receipts report no leaks. The original invoking tool returned 143;
its separate run.cjs enclosing receipt was not written, so that enclosing
wait/EOF remains unknown, rather than inferred from the driver wait.
Only selected named whole screenshots remain. Redundant images were pruned
with hashes recorded; closed protocol logs were gzip-compressed after exact
roundtrip checks, with paths and recovery commands in audit.json. Git remains
the source archive; no source-tree snapshot, media copy or extra module copy
was retained. The post-runtime finite drain monitor is separate from the
original watchdog; it cannot cover a historical sampling gap or erase the
original floor breach. result.json is written last after final receipts.
Box ID null; state NOT_CREATED; expiry null; stop receipt null. No agent, worker, box, Python, Wine reference run or public deployment was created. Foreign WIP, held Blood II/Sims/Heroes II work and UT ISO/partials were untouched. This task releases ownership and stops with the original permanently closed.