Quake III: finite aim/fire extension and live capacity interruption, 2026-11-12 2235

The run-local finite ordinary aim/fire extension passed nine focused local cases, including trusted Chrome events echoed by an actual Worker. Major frag remains unearned. The fresh original reached native I Can Win selection and Fight, but recurring local disk pressure stopped native work before a reviewed arena/target frame. No original aim/fire intent, gameplay shot, hit, health/ammo consequence or score increase is claimed. Current arena score and health are UNKNOWN. This is a tested operator-action extension and a concrete capacity interruption, not an emulator or guest timing defect.

Evidence: scratch/runs/20261112-quake3-finite-aim-fire-major-2235/. The starting Git commit is cea21ab6d927e6a5263b8c3691b41487ab40c634. The 2205 encounter (3fc3232cf) supplies the observed lost target windows; its 49 PNGs, 47 bindings and score 0–0 remain historical. The separate shotgun pickup is not an enemy or proof of a body-rendering defect. The route note (ef6fa0453) remains guidance; this run did not reach that route.

One finite intention

Owned finite-intent.cjs, native-input.cjs and browser.cjs add one command: action: "aim-fire", declared integer dx/dy, and a finite hold of 3,000–15,000 host milliseconds. It permits exactly one bounded nonzero ordinary pointer-lock motion followed by Enter attack. It rejects extra keys or per-key hold overrides. There is no target-state query, tracking, automatic correction, conditional firing from game state or repeated shot loop.

The existing independent release process connects and arms Enter-UP before motion or DOWN. Within that already armed interval, the consumer checks the reviewed frame's freshness and all 22 identity fields, requires actual screen pointer lock, sends the one motion, and checks trusted matching relative movement. It checks identity and freshness again before Enter-DOWN. Freshness is checked after the asynchronous identity read as well as before it; a focused failure case exposed the need for that second check during development.

The hold sampler checks all 22 fields and retains the existing full PNG held capture. A command cannot succeed without a full held consequence, independent acknowledged release, actual release-parent join, and the normal full released capture. Changed identity, untrusted/mismatched motion, expired review or uncertain DOWN terminates the action; only cleanup UP follows. The declared interval starts when the independent owner arms, before the motion checks. It is not a promised duration of attack inside the guest. Guest polling, simulation steps and applied guest hold timing remain UNKNOWN.

The producers retain atomic no-overwrite publication and strict semantic ACK from a68ab669f. drive.py, operate.py and local-drive.py are unchanged by SHA. atomic-controls-reused.json references the unchanged 18-case atomic regression result and test/log hashes; those regressions were not rerun. Capture controls and the original identity/release observer controls were freshly hash-read by reference. That reuse does not qualify the new extension in original combat.

Focused verification

node scratch/runs/20261112-quake3-finite-aim-fire-major-2235/finite-intent.test.cjs passes nine cases. The exact local producer bytes emit a command consumed by the extracted actual browser loop/action and actual native holder. The fixture uses explicit synthetic 22-field identities; it is not a substitute original game. Chrome receives trusted locked relative motion, then trusted Enter DOWN and independent UP; a real page-owned Worker echoes those delivered events. The positive case records one motion, one DOWN, prearmed release, full held and released screenshots, and actual producer/release/Chrome waits with EOFs.

Failure cases cover identity replacement after motion, expiry during an identity read, deliberately hidden motion/DOWN replies, partial multi-key DOWN, independent prearm attachment failure, actual armed cleanup-UP failure following target destruction, and false semantic ACK. They preserve once-only submission and terminal failures. The uncertainty cases deliberately inject uncertainty after real CDP delivery; they do not claim naturally lost Chrome replies. Initial fixture failures and their corrections are retained. The first failed fixture producer was sent SIGTERM; its actual producer wait/EOF remains UNKNOWN. The final positive fixture has its actual successful producer wait.

flock /tmp/wine-build.lock bash tools/build.sh passed. Module SHA256 remains 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17. No production source was changed. verification.json also verifies the recovered native evidence and all 893 frozen local input hashes.

Fresh original and capacity stop

Entry capacity was 1,531,629,568 bytes; preflight was 1,519,443,968 bytes. The named DeusEx PID 666029 recovery had already completed according to its board entry. Its files were left alone. Above-floor preflight froze 893 pins, kept provider parts bounded to 1 MiB, and armed/observed an independent two-hour watchdog before private creation. Initial expiry was 2026-11-13T00:19:10.098Z. All 895 remote closure files passed SHA/size verification, and actual provisioning joined 0 with both EOFs before launch. Existing media remained path/SHA references; pak0.pk3 retains e77abad2466f45a0a7ea018445528f9b95a0fe7789fa1abc1a7718bbf0754b08.

Native Q3DM1/Major roster, Bring It On white, I Can Win white, and I Can Win remaining white with the cursor away over Fight were reviewed. Two motions prove real screen pointer lock and matching trusted deltas. The recovered Fight consequence reads Connecting to localhost / Awaiting connection...0; it is not a reviewed arena or combat frame.

The first local floor refusal occurred before a frame-download API after the selection ACK. Actual free space was 1,499,111,424 bytes, then 1,498,775,552 bytes after a 45-second interruptible hold. PID 666029 was no longer live; there was no remaining concrete recovery dependency to await. Lossless gzip of this run's completed provisioning logs, with full roundtrip/hash checks, restored 1,501,925,376 bytes. A new full difficulty frame and separately reviewed cursor-away/Fight decisions followed; no uncertain command was replayed. After Fight ACK, actual free space fell to 1,499,689,600 bytes. Native work ended and only normal close, files-only recovery and stop cleanup followed. No allocation or native DOWN was submitted from a known subfloor local check. No claim of continuous above-floor capacity is made.

Recovery and closure

verification.json verifies 13 full 1024×712 PNGs by CRC/decode/SHA, 12 full-22 capture bindings, 11 positive owning-WebGL capture records, seven DOWNs and seven independent acknowledged UPs with release-parent waits, and two trusted pointer-lock motions. Startup's pre-draw capture was not used for input. The two actual workers use the current 04 module. These counts describe menus and loading, not seven gameplay attacks or a combat acceptance result.

All 137 remote output paths were independently reread and verified locally. Existing identical local PNGs and the identical tested module were referenced instead of duplicated. Closed provisioning logs are retained losslessly with hashes in owned-log-compression.json. Git commit, relevant binary diff, owned new helper/note patches and media references are retained; there are no source-tree archives or media copies.

Normal Browser.close ACK succeeded. This is browser closure, not a proved guest-menu quit. Chrome, original Node, local manager, outer lifecycle parent and independent watchdog all actually joined 0 with separate stdout/stderr EOFs. Owned box bx_frgxf9w8 is archived, expiry null, normally stopped 2026-11-12T22:26:45.221Z. Stop receipt stop_9a1c96d3e4185302 is completed, forced false, error null.

Historical Quit 21 cause and historical parent joins remain UNKNOWN and unreplayed; this run's observed joins do not repair them. No inherited box, other worker, cache/reserve/RAM setting, guest console/config, aim, health, position, AI or clock was changed. No FPS, audio, full-27, parity or general crash claim is made. Next requires sufficient actual capacity and a fresh watched original with a reviewed visible Major frame, followed by one finite intent and full consequence. Only native Major kill text or a score increase identifying Major earns the frag.