Quake III software input and release, 2026-11-17
Run: scratch/runs/20261117-quake3-software-input-release-arena-progress/result.json.
The task remains incomplete: the fresh original reached the main menu, but its
first intended ordinary click was refused before DOWN at the fixed independent
prearm gate. Arena movement, turning, firing, enemy consequence and native Quit
were not reached. No shared production defect or runtime correction was proved.
The exact published runtime remains
e7c13db296e380130bc6b9771cf3f55970f5c42f, module
f40fc54c5b0f1d4bd505364049e091c0092cab27eac0dcb644e8623d2344875b.
All 1,499 source pins and 307 existing media/input pins matched; media was
referenced in place. Execution was cooperative, native thread 1, software GPS.
The live module readback matched f40. This is not a latest-main or threaded claim.
The preceding UNKNOWN original was never resumed, queried or replayed.
The retained bound-input.cjs counts its delivery interval from before DOWN's
CDP reply. A reply does not identify application consumption or a physical UP.
The run-specific helper retains that hold implementation and uses the current
gta2-paired-controller.cjs independent CDP transport in a separately awaited
release process. Process/transport initialization precedes the immutable 500 ms
owner lease; the existing 1,500 ms fallback, 1,750 ms UP acknowledgement and
3,000 ms aggregate bounds remain enforced. There are no guest pumps, input-map
writes, private guest calls, timeout-only increases or synthesized replies.
Final generated controls (controls-v6) used the pinned native module,
GpuStreamSoftware.Executor CLEAR/PRESENT load, production renderer input
handlers and trusted Chrome events. Their eight expected outcomes passed:
- Normal 200 ms key and click: native renderer DOWN/UP state and independent physical-UP witnesses, with actual CDP replies and child waits.
- A 90 ms page rendering delay: release still completed within the fixed bounds.
- A 350 ms producer stall: independent mouse UP reached the native handler; the producer's expired delivery interval remained terminal.
- Cancellation before DOWN, stale capture and wrong owner: terminal refusals.
- A genuine 1,900 ms page rendering task: the 1,750 ms independent deadline expired; no successful UP acknowledgement was invented or replay allowed.
The successful final key/click/delayed controls submitted UP about 204–215 ms after ARM and received its CDP reply about 17–26 ms later. Native page clocks, host monotonic clocks, event trust, renderer physical state, protocol replies and release-child EOF/waits are separate evidence. These rendering-only controls have no guest application, so they prove no guest input consumption. Earlier generated-fixture errors and the initial process-start prearm miss are retained separately; they were not production defects or originals.
One fresh registered original then ran. Passive observations identified the actual software executor and advancing GPS records/presents. A personally reviewed wholeimage shows the Quake III main menu. The intended Single Player click used a fresh matching review and a 200 ms gesture. Its release child reported INITIALIZED, but the subsequent independent owner/prearm check failed the fixed 500 ms gate. UNKNOWN was recorded 2,523 ms after INITIALIZED; there is no detailed protocol trace attributing that entire interval to a particular Chrome operation. The preparatory ordinary mouseMoved call completed, but its individual protocol reply was not logged. No ARM or DOWN submission exists, and no subsequent scene or game-input consequence was observed. This real-load refusal prevents a reliable ordinary-input/arena qualification.
Chrome closed normally (exit 0), with actual stdout/stderr EOFs. The release child exited 1 with both EOFs; the driver exited 1 with both EOFs; the independent watchdog exited 0 with both EOFs and did not expire. The outer supervisor command returned 143, and its helper-wait/both-EOF receipt is missing: that boundary remains UNKNOWN and is not reconstructed from process absence. Final owned process groups were empty and all owned profiles absent. No box was created.
Only the selected result-linked main-menu image is retained. Evidence contains exact helper hashes and relevant patches, not source archives or media copies. No production files were changed, so no canonical build or post-fix original was appropriate. Further work needs a bounded current-owner prearm path under the original's page load and durable outer-helper wait custody. Another original is not authorized by these findings alone. No gameplay, parity, FPS, audio, broader matrix or full27 claim follows.