Quake III restored-capacity threaded original, 2026-11-17
Run: scratch/runs/20261117-quake3-restored-capacity-threaded-arena-gameplay/result.json.
Incomplete: one fresh original reached Choose Level (Q3DM1 / Arena Gate,
Major), then Game Server setup (Q3DM1, Free For All), with a later visibly
highlighted Game Type row. Arena movement, turning, firing, enemy consequence
and ordinary native Quit remain unproved. The independent actual-disk
watchdog stopped the original at 1,499,058,176 bytes available, below the
unchanged 1,500,000,000-byte floor. The 900-second deadline did not expire.
Neither this terminal nor the earlier original was reopened or replayed.
This used the published e7c13db296e380130bc6b9771cf3f55970f5c42f source
and retained module SHA-256
f40fc54c5b0f1d4bd505364049e091c0092cab27eac0dcb644e8623d2344875b.
The new actual guest-Worker CDP bytecode readback matched f40. Its owning
render Worker endpoint 1 was gl-gps, backend software, with an actual
GpuStreamSoftware.Executor and advancing draw/present statistics. Page
CPU getters remain shadow-instance observations, not guest CPU proof.
The previous run's 1,499 source / 307 media pins, real Calculator display
0-to-1, negative input/release checks and lifecycle controls were reused;
no broad inventory, matrix, media copy or canonical build was repeated.
The independent release service attached to the neutral threaded shell before the registered Q3 launch. Seven ordinary gestures, all 200 ms, were delivered: Single Player click, Enter, Tab, a click intended for Fight, Enter, Tab, Tab. Each completed its existing owner/freshness/prearm/deadline and independent UP checks. Trusted Chrome edges, physical UP witnesses and host production input dequeues are retained separately. There is no native USER-return-token instrumentation. Exact per-edge Q3 response is unknown. The click intended for Fight was followed by Game Server setup, so neither its label nor its requested viewport coordinate proves activation of Fight. No game configuration, clock, save or media was changed. No console command, private guest call or forced pump was used.
The last reviewed wholeimage shows Game Server setup, not an arena or Quit dialog. An attempted Escape after closure was refused by the local guard before a command file or physical event was written. There was no retry. Chrome closed normally, code 0, Browser.close ACK, both EOFs and no signals; the release service exited 0 with actual wait and both EOFs. The helper actually waited for driver 143 and watchdog 0 with both EOFs. The outer custodian's helper-wait receipt is missing: that boundary is UNKNOWN despite the tool session reporting terminal 143. Named owned PIDs were absent and the owned tmpfs profile was removed; absence is not wait proof. Individual Chrome descendant wait syscalls are not separately instrumented.
No production defect was proved or product source changed. The run retains small helper inputs as patches, exact pins and selected personally reviewed wholeimages; Git remains the source archive. No box, worker or deployment was created. Full27, parity, FPS and audio remain open. Further gameplay requires a separately authorized fresh original with actual capacity above the same floor, retaining all input and release fences. A useful ordinary route would return from Game Server and visibly focus Fight, then review the skill/arena transition. Release and stop.