Quake III: fresh Major encounter and lost aim windows, 2026-11-12 2205
Major frag remains unearned. This task ran a fresh original Q3DM1 after the concrete cold-cache recovery restored actual capacity. It reached and visually identified Major in the red-window corridor, but did not retain an exposed target through a reviewed aim consequence. No gameplay shot was sent; no hit, useful weapon consequence or score increase is claimed. This is fresh original evidence, not another subfloor-only stage report.
Evidence is in scratch/runs/20261112-quake3-capacity-ready-major-2205/.
The ready helper stage
(7111f5e4b) supplied 22 helpers, 86,363 bytes, checked against their exact
recorded hashes. The three repaired producers retain the atomic no-overwrite
publication and strict semantic ACK
from a68ab669f. The full-frame route guidance
from ef6fa0453 was used. Historical regressions, locked build and 26-frame
review were not repeated. Fourteen existing control references and the reused
proof references were freshly hash-read, without rerunning their tests.
Concrete dependency and fresh launch
Entry actual free space was 1,463,099,392 bytes. After the small helper stage,
dependency-hold.jsonl records 1,427,988,480 bytes with the exact live
/proc/612264 launcher identity. The next sample, 61.49 seconds later, records
1,657,425,920 bytes and that same live identity. This interval included local
preparation and a 45-second interruptible sleep. No API, allocation or input
was submitted below the floor. The published cold-cache outcome
subsequently confirmed its completed recovery; none of that worker's files
were modified. No cleanup was inferred from a missing process.
Fresh preflight froze 891 file pins and module SHA256
04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17.
Game media remained an existing path/SHA reference, including pak0.pk3
e77abad2466f45a0a7ea018445528f9b95a0fe7789fa1abc1a7718bbf0754b08.
An independent two-hour watchdog was armed and observed alive before
private box creation. Initial expiry was 2026-11-12T23:41:50.146Z.
The qualified provider retained bounded 1 MiB parts. Actual joined provisioning
returned 0 with separate stdout/stderr EOF; all remote chunk/whole checks and
the final 893-file closure passed before original launch. No public host or
other box was used.
Fresh native difficulty captures show Bring It On initially white, then
I Can Win white after an ordinary selection click. easy-cursor-away.png
shows I Can Win remaining white with the cursor away over Fight, before
fight-easy. Real screen pointer lock and trusted relative motion were
observed. Input admission retained the complete 22-field binding, the current
04 module in both workers, and the actual owning WebGL producer with draws
and presentations. Startup's initially empty grey surface was not treated
as permission for gameplay input.
Original route and targeting blocker
The arena shows both player and Major entering, score 0–0. Individually reviewed finite moves pass to the right of the statue, collect Armor Shard, clear the arch posts and enter the lit hall. The floating shotgun is a separate pickup. It is not evidence of a missing opponent body. No shotgun pickup or ammunition-use combat result is claimed for this run.
Three fresh acquisition/consequence pairs establish the narrower blocker:
expose-inner-archshows a complete humanoid on the left of the passage, separate from the pickup. After one left aim correction,aim-visible-humanoidshows the area empty. Fire was withheld.- After crossing the inner arch and exposing the red-window passage,
turn-window-cornershows an exposed humanoid with native Major name text. The body is just right of the reticle. The small right/down correction ends inalign-major-torso, an empty corridor. Fire was withheld. - Following the corridor, far room and stairs reaches
climb-ramp, which shows a humanoid near the red-lit tunnel.aim-ramp-humanoidshows the tunnel empty after the finite left/up correction. Fire was withheld.
Only the corridor capture explicitly names Major; the other two humanoids are not independently identified. These pairs do not establish a rendering, input or AI defect, or the exact reason each target left view. They show that the operator failed to obtain the required settled exposed aim window for one justified shot. The final reviewed frame remains health 100, armor 15, ammo 100 and score 0–0. A native kill message or score increase identifying Major is still required.
A later room movement was rejected locally before request/API/DOWN when actual free space fell to 1,499,467,776 bytes. A 45-second local hold preceded an above-floor sample of 1,525,530,624 bytes, a new full capture and a separately reviewed move with a new label. No uncertain command was replayed. This was a transient gate during the fresh run, not proof that the completed recovery had failed. Final local verification observed 1,495,928,832 bytes, after all remote work and normal box shutdown had already completed; no subsequent runtime API or input was sent.
Recovery, cleanup and scope
fresh-verification.json and fresh-png-check.json verify 49 fresh complete
1024×712 PNGs by SHA, CRC and full decode; 47 capture bindings retain all 22
fields across capture. Seventeen relative motions retain real screen pointer
lock and trusted matching deltas. Twenty-one held input actions contain
24 DOWNs and 24 independently armed, acknowledged UPs, with release parents
actually joined and both EOFs observed. These are this run's checks, not a
repeat of the historical regression matrix or a full-27 claim.
The normal close command ACK succeeded. It closes Chrome through the browser harness; it is not evidence of a guest-menu quit. The actual original Node parent wait is 0 with separate stdout/stderr EOF, and Chrome's actual parent wait is 0 with both EOFs. Unique recovery independently reread all 435 remote output paths and verified their SHA/size locally before shutdown. Identical existing local PNGs were reused instead of stored twice. A separate local recovery wrapper checks actual capacity before each API submission; no frozen remote helper or runtime was changed.
Owned box bx_6m748dm6 is archived, expiry null, normally stopped 2026-11-12T22:04:54.201Z. Receipt stop_b599145f493e7559 is completed, forced false, error null. The original local manager tool session returned 143 and produced no manager-parent-wait record. Its parent wait and separate EOFs remain UNKNOWN. With no stop-attempt record present, a separate delegated stop parent performed the normal stop and actually joined 0 with both EOFs. The orphaned watchdog wrote its terminal stop-observed record; its parent join remains UNKNOWN. No inherited box was touched.
Exact Git identity, relevant binary diff and owned new helper/note patches are retained locally; Git is the source archive. No source archives or media copies, console/config/clock/AI/health/aim-memory/position/media writes, unknown replay, timeout extension, guard weakening, children, other workers or cache/reserve/RAM changes occurred. Historical Quit 21 remains UNKNOWN, unreplayed. No parity, FPS, audio or general crash claim is made.
Publication is documentation only, checked for local links, whitespace and diff integrity. No new build result is claimed. Next requires actual capacity above the floor and a fresh watched run that retains Major visibly under settled aim through one finite fire/release/full-consequence decision.