Quake III: qualified intent reused; courtyard reached, capacity interrupted combat

Major hit, frag and useful combat consequence remain unearned. One fresh original reached Q3DM1's courtyard after native I Can Win selection. No exposed Major was reviewed, no aim/fire intention was submitted, and no gameplay shot was made. Repeated actual local disk-floor refusals prevented completion of the reviewed right-arch approach. A bounded ten-minute local hold/recheck window exhausted the named recovery dependency without restoring sustained progress. This adds arena and closure evidence to the existing capacity blocker; it establishes no new engine or guest-input defect.

Evidence: scratch/runs/20261112-quake3-qualified-intent-native-frag-2245/. Starting Git commit: 2aec10f07161f00a42a710f18dfb05bf7f59822e. The parent intent qualification is 6e3df25f7; the target/pickup route is ef6fa0453. The foreground floating shotgun remains a separate pickup; no body-rendering defect is established.

Exact reuse and fresh provisioning

qualified-reuse.json records SHA/size equality for the inherited helpers, including the finite intention, actual browser consumer and native holder, plus the retained nine-case test result, actual fixture parent wait and locked build log. Existing identity/release/capture proof references and the 18-case atomic controls were freshly hash-read. Neither local matrix nor the build was rerun. No new implementation is claimed. The finite intention still means one visually chosen ordinary relative motion immediately followed by finite Enter attack, with independent UP prearmed before either motion or DOWN, a full held frame, acknowledged release and full released consequence. It was retained unchanged but never exercised in this original's combat.

Preflight had 1,533,747,200 actual free bytes on /home, 895 frozen local inputs, successful staged imports and unchanged module SHA256 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17. An independent private two-hour watchdog was armed and observed alive before box creation. Initial expiry was 2026-11-13T00:33:44.015Z. All 897 remote closure files passed SHA/size verification; provisioning actually joined 0 with both EOFs before original launch. Provider parts remained bounded to 1 MiB, with the inherited strict 30-second transport caps and UNKNOWN/no-replay behavior. Existing media stayed path/SHA references, including pak0.pk3 SHA256 e77abad2466f45a0a7ea018445528f9b95a0fe7789fa1abc1a7718bbf0754b08.

Native observations and capacity boundary

The fresh native menu showed Q3DM1 and Major. I Can Win became white and stayed white after ordinary pointer motion moved the cursor away over Fight. Only then was Fight clicked. Full captures subsequently showed connection, sounds, BSP and player loading, then the courtyard with Major's native chat line. The courtyard statues and pickups were not treated as an exposed opponent.

The first downloaded courtyard PNG showed ammo 100, health 120 and score 0–0, but the floor refused its state download. It was not used to authorize input. After a local hold, a new complete fresh-courtyard frame showed health 106, ammo 100 and score 0–0, with a current full-22 binding and positive actual CPU-owning WebGL producer. It authorized one finite ordinary rightward motion toward the visible right-arch approach. Its trusted locked delta was confirmed. The subsequent full PNG still showed the courtyard, health 105, ammo 100 and score 0–0. Its state download again hit the local floor, so it did not authorize another action. No camera/guest application-timing conclusion follows from that acknowledged ordinary motion alone. No movement key or attack was sent in the arena. The three Enter holds were menu navigation only.

capacity-hold.jsonl records local free-space/PID samples over the bounded window 22:41:53.444Z–22:51:53.445Z (600.000 seconds). There were brief above-floor resumptions for new observations and the single reviewed motion; this was not a continuous no-API or continuously subfloor interval. Each sample's zero-call fields describe that local sampling iteration. Every resumption required a positive actual check, and no refused native command was replayed. Final window free space was 1,498,173,440 bytes; the terminal check was 1,497,956,352 bytes. PID 699958 remained live. Its board entry confirmed the assigned old exec-server/voice recovery had already completed; its files and worker were untouched. Only this run's closed provisioning logs were losslessly compressed, saving 1,073,133 bytes with a durable recovery journal and full roundtrip/SHA checks. No cache, reserve or RAM setting changed.

Integrity and delegated shutdown

verification.json verifies 19 complete 1024×712 PNGs by CRC/decode/SHA, 18 full-22 bindings, 17 captures with a positive owning-WebGL producer, seven acknowledged DOWNs and independent UPs with actual release-parent waits, and three trusted real-pointer-lock motions. The startup pre-draw capture was not used for native input. There are no held gameplay frames: no arena key hold or aim/fire intention occurred. These counts do not qualify the unchanged finite intention in original combat.

All 175 remote output paths were independently reread and hash-verified locally. Identical downloaded PNGs and the unchanged module were referenced without another copy. Exact Git identity, relevant binary diff, owned new patches and the relevant untracked lib/wininit-boot.js patch are retained; there is no source-tree archive or media copy.

Normal Browser.close was acknowledged. This proves browser closure, not guest-menu quit. Chrome, original owner, local manager, independent watchdog and outer lifecycle parent all actually joined 0 with separate stdout/stderr EOFs. Box bx_4kyyxv9v was normally stopped at 2026-11-12T22:53:13.593Z, is archived, and has expiry null. Receipt stop_f3bc7e0b9454bcf6 completed with forced false and error null. The box was stopped immediately after unique evidence recovery and local hash verification; no further runtime API was used afterward.

Historical Quit 21, historical manager/watchdog UNKNOWNs and the parent's first failed fixture producer wait remain UNKNOWN and unreplayed. No inherited box was accessed, no children or other workers were launched, and no console/config, AI, clock, health, position, guest memory, media or direct guest aim state was written. No FPS, audio, parity, full-27 or general crash claim is made. Next requires actual capacity sufficient to finish a fresh reviewed encounter: visible Major before the unchanged single finite aim/fire intention, full held/released consequence, and native Major kill text or a score increase identifying Major for any frag claim.