Quake III: fresh Major shotgun encounter, 2026-11-12 2055

The original player frag against Major remains unearned. This run reached fresh native I Can Win combat and a bounded shotgun attack, but obtained no player score increase, kill message or confirmed outgoing hit. Score stayed 0–0. It follows the capture/combat handoff (a8572bf48) and 2045 follow-up (3166585b2). No parent UNKNOWN or prior observation is revised.

Evidence: scratch/runs/20261112-quake3-major-frag-2055/. All 22 final -small-upload helpers and 869 inherited non-run pins matched exact SHA values. Eleven older references and 14 final helper/proof references were rechecked; unchanged setup matrices were not rerun. Qualified source is ae83f8d550685f98de2f0bd75acf4c7e10a875f4; the current checkout Git pin is 9ca2c6ffebaa921ea0044f8997d71548e7c303ab. Relevant working-tree binary diff, new helper patches and exact pins are retained. No source/media archive was made. Module SHA remains 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17; the existing original pak path retains SHA e77abad2466f45a0a7ea018445528f9b95a0fe7789fa1abc1a7718bbf0754b08.

Preflight measured 1,546,866,688 bytes free on /home. An independent observable two-hour watchdog was armed before box creation. The 1 MiB production assembler completed, all 893 remote file checks passed, and the actual provisioning parent returned 0 with separate stdout/stderr EOF before original launch. Manifest SHA is 0a421061275e6f17fc45fe1bd278455d15ff2639805eb395fda4147fdb142da5. Chrome retained --disable-gpu-compositing; actual guest ownership was WebGL.

Fresh complete native Main, Choose Level and Difficulty frames were reviewed. Choose Level identifies Q3DM1 and Major. Bring It On initially appeared white. A native click acquired real screen pointer lock; actual varying CDP x/y produced trusted relative deltas. A click selected I Can Win, and easy-away-verified.png shows it still white with the cursor away on gold Fight. Only then was Fight clicked. native-reviewed-scope.json records the reviewed image SHA values and actual owner identities.

The original loaded a living courtyard with health 124, machine-gun ammo 100, score 0–0 and native “Major entered the game” text, followed by Major's chat. An aim ACK initially preceded the native view change; a subsequent full frame proved the applied change. Short independently released movement reached the lit hall and a native Shotgun pickup. The later complete frame confirms shotgun ammo 10 and health 100. These observations do not establish a frag.

face-open-hall.png shows the opponent model near the crosshair in the open hall. One finite ordinary attack was declared before submission: 15 seconds of wall-clock MouseLeft hold, with an independently released one-second retreat, then consequence review. Its original held full frame was recovered and binds the same owners; it completed while fire was held, after the shorter retreat had released. This does not assert 15 seconds of guest gameplay or that firing had been consumed by the held frame. The consequence frame shows smoke and shotgun ammo 8, health 100, score 0–0. No outgoing hit is confirmed. A small reviewed aim correction then showed the opponent had left the passage; the next action was ordinary forward reacquisition without fire. Its final frame shows another Shotgun pickup, ammo 10, health 100 and score 0–0. There was no adaptive blind fire chain and no native menu-pause assumption.

Immediately afterward, actual df -B1 /home reported 1,499,697,152 bytes free, below the sole 1,500,000,000-byte floor. No subsequent gameplay input was submitted. The run had losslessly compressed its own closed/quiescent journal prefixes with raw round-trip SHA checks. No reserve, RAM gate or root-owned catalog-cache change was applied. resource-block-observed.json records the first measured breach and stop decision.

The submitted Quit request received no command ACK. The run-local browser loop recorded SyntaxError: Unexpected end of JSON input at its command-file JSON.parse (browser.cjs:100:143), then performed terminal-failure Chrome closure. The recovered final command file commands/21.json is valid Quit JSON, but no command-21-attempt.json or ACK exists. This is an evidenced harness command-ingestion failure; incomplete file publication is a candidate explanation, not a proved production runtime defect. The remote caller exited 1 after its bounded no-ACK check, and the submitted operation was never replayed.

Chrome's actual parent returned 0 with separate stdout/stderr EOF, and closed.json records code 0 and no signal. No actual Node-parent or remote owner outer-parent wait receipt was recovered; both remain UNKNOWN. The command-loop guard is outside the normal cleanup path when parsing throws, so Chrome closure alone cannot stand in for a Node join. No code repair or matched-original before/after claim is made.

Files-only recovery fetched all 219 unique output paths twice, comparing raw size/SHA. Offline validation passed for 26 complete 1024×712 PNGs with strict decode/CRC, 21 full stable 22-field game bindings, four original held full frames, 11 independently released holds with release-parent 0/EOF, and six actual trusted relative-motion receipts. All 21 native state snapshots recover actual module04 CPU and owning renderer scripts, a real WebGL context, and positive completed/draw/present counts. One PNG is the host-shell frame; the four held PNGs are additional to the 21 ordinary native captures.

After evidence verification, delegated normal stop archived own box bx_xs7tuh8z, with final expiry null. Receipt stop_1db408bb4cf799fe completed at 2026-11-12T21:16:21.670Z, unforced, error null. An independent GET agrees. Manager, durable lifecycle parent and independent watchdog actual waits all returned 0 with separate stdout/stderr EOF. Those joins do not replace the UNKNOWN runtime waits above.

This is a docs-only tracked change; no production patch or locked-build result is claimed. Next remains a fresh ordinary Major encounter with actual disk headroom and reviewed aim/fire consequences, after qualifying a response to the harness command-ingestion failure. Native score increase or kill text with Major identity is still required. SoftwareGL, full-27, parity, FPS, audio and general crash-free scope remain open. Parent artifact reviews were not repeated.