Quake III threaded software input, 2026-11-17
Run: scratch/runs/20261117-quake3-threaded-native-input-arena-gameplay/result.json.
Incomplete: the distinct threaded original reached the main menu and later
Choose Level, showing Q3DM1 / Arena Gate and Major. Arena movement, firing,
enemy consequence and native Quit remain unproved. The independent watchdog
stopped the run when actual /home free space reached 1,485,443,072 bytes,
below the required 1,500,000,000-byte floor. No original was restarted.
The tested production source is immutable published
e7c13db296e380130bc6b9771cf3f55970f5c42f; module SHA-256 is
f40fc54c5b0f1d4bd505364049e091c0092cab27eac0dcb644e8623d2344875b.
All 1,499 retained source pins and 307 existing media/input pins matched.
Source was served from Git objects, with media referenced in place. Loaded
host source and live CDP module readbacks accompany the source checks.
This is an actual guest-Worker run, with an advancing slot-zero guest slice
stream and a separate owning render Worker. Its endpoint 1 is gl-gps,
backend software. A pass-through constructor observer recorded an actual
GpuStreamSoftware.Executor, its real draw/present counters, and the owning
endpoint. No local page executor or URL flag substitutes for that evidence.
Page CPU getters in raw observations describe the page shadow instance;
they are not asserted to describe the running guest Worker.
The previous eight rendering-only controls were reused as bounded software render/input evidence, with their lack of guest consumption kept explicit. A focused new prerequisite launched the real registered Calculator through the same pinned threaded host. Its guest-Worker module matched f40. A trusted 200 ms digit press changed the native display from 0 to 1. Production input dequeue observations recorded DOWN, CHAR and UP for the real guest pump. Cancellation, stale review and wrong owner refused before DOWN. With the producer event loop blocked for 350 ms, independent UP completed around the 200 ms schedule while the producer correctly failed its delivery bound. These are distinct new real-guest controls, not a rerun of the software matrix.
A run-specific persistent release service connected and attached against a neutral ready document before either PE started. This separates transport initialization from current authorization. Each gesture still checks fresh owner object identities, process incarnation and review age inside the fixed 500 ms prearm gate. The 1,500 ms fallback, 1,750 ms independent UP ACK bound, 3,000 ms aggregate bound, fixed short hold and no-replay refusals remain. The independent process owns scheduled physical UP, observes trusted Chrome edges and checks the original renderer's physical state afterward. It never invokes guest exports, pumps a slice or writes input maps. The prerequisite and original used the same service bytes. No production lifecycle fix is claimed from this run-only composition.
One fresh Q3 original then used ordinary mouse/keyboard events: Single Player
click, Tab, ArrowUp, Enter and Escape, all with 150 or 200 ms holds. All five
gestures completed actual protocol/release checks. Native host dequeue logs
show the guest pump took these events, sometimes several seconds after
physical release. Later wholeimages reached Choose Level; the earlier
unchanged main-menu captures did not establish an input defect. Exact
per-edge application response attribution is unknown. The passive dequeue
observer is not an opt-in native USER-return token receipt; none is claimed.
The image named native-exit-request.png actually shows Choose Level, not
a Quit dialog. The last Escape therefore proves no native Quit. No further
input was delivered after the disk stop; the attempted local capture request
was rejected by the existing closed-run guard before writing a command.
The detached custodian actually waited for and drained its outer helper; that helper actually waited for and drained the driver and independent watchdog. On the original, outer helper and driver exited 143 after the watchdog cancellation; watchdog exited 0. The persistent release child exited 0 with both EOFs. Chrome closed normally, exit 0, with both EOFs and no signals. The 900-second watchdog deadline was independently armed before browser startup; the disk floor fired first. Native browser close retained its 8/5/5-second shutdown limits. Named native PIDs and owned driver process groups were absent and profiles removed afterward; absence is separate from the actual wait receipts. The detached custodian's own parent wait and individual Chrome descendant wait syscalls are not separately instrumented.
No production defect was proved, no shared source changed, and no canonical build or affected post-fix original was appropriate. Evidence retains small run inputs as patches and selected personally reviewed wholeimages, with no source archive, media copy or frame series. No box, worker fleet or deployment was created. Further work needs a separately authorized original after the disk-floor stop, retaining the preguest release lifecycle and distinguishing host dequeue, native USER return and application-visible consequences. Full27, parity, audio and FPS remain open.