Quake II guard/door prerequisite limitation, 2026-11-08
The requested outgoing guard or onward-door consequence is not established. The current-module local route qualification did not reach a clearly living, aligned guard or a reviewed ordinary onward threshold. Therefore no fresh watched box was allocated. This is an incomplete route prerequisite, not a demonstrated emulator mismatch. No emulator change was made.
Evidence is in the ignored
scratch/runs/20261108-quake2-guard-door-progress/ directory. The accepted
WebGL/SoftwareGL health pickups and incoming damage from the preceding notes
stand. This run supplies no additional pickup deliverable, outgoing hit,
defeat, door opening, new-room transition or level completion.
Reviewed route and corrected identifications
The bounded local browser used registered quake2_demo, ordinary Game →
Easy, the complete pinned 67-path media closure and unchanged original
642-byte controls. local/world.png shows the starting diagonal support and
100-health HUD. forward.png, face-ramp.png and descend.png show movement
down to the broken ribbed alcove and its preexisting corpse. The corpse is
excluded from any defeat claim.
The subsequent right-side slope led around the support to the upper floor,
window and crates (upper-approach.png). Turning back exposed the fallen pod
and a small wall feature (lower-access.png). Its initial live description
as an upright guard was wrong: the closer target-approach.png,
breach-offset.png and breach-approach.png do not establish a living actor;
the feature remains at the broken wall. The earlier yellow shape by the
ribbed alcove was also insufficient to distinguish an actor from flame.
These corrections supersede the raw admission-review prose. No gameplay
attack was sent. The only Enter holds selected the normal menus.
Several bounded holds produced no visible camera/position change, including the second short right turn and a left strafe beside the support. Other holds visibly moved/turned the player. Exact ACKs and physical key observations do not prove native consumption, and collision or guest input timing was not isolated. No causal input defect is claimed. This route returned through known starting geometry without qualifying a new threshold; further turning or firing without a verified target was stopped.
Identity, safety and validation
Runtime Git SHA is 2ea85dd913c97e0a675f3430e8c46e2bd734b8e9, with the
relevant uncommitted tracked patch and untracked dependency patch retained.
All 21 bound captures identify executing guest module SHA-256
cc438f727a39e39d1016045d37ae95f60cf8f9793e6b117e14beabb80c27e07a;
world captures identify the same renderer module. This differs from the
earlier accepted f9650607… module and is not substituted for that evidence.
All 176 successful served reads match launch pins. No source/media archive
was made; recovery uses Git, binary diffs, new-file patches and media hashes.
Owning render Worker endpoint 1 reports api: gl, backend webgl, no failed
endpoint, and a live non-lost WebGL 1 WebGLRenderingContext owned by
WebGLBackend. Both CPU exports report gl_sw_enabled() == 0. Chrome reports
ANGLE Intel UHD Graphics 620/Mesa; this provider string is not physical-GPU
proof. Chrome is 151.0.7922.108, V8 15.1.206.16. The native canvas is 640×480;
no emulated resize was used. A numeric fallback counter is absent from the
captured GL statistics and remains unmeasured.
The actual safe Python request and numbered ACK consumer pass waits of 0, 1000, 2000 and 10000 ms, including 250/750 ms holds. Oversized waits, post-UNKNOWN publication and insufficient immutable-deadline reserve reject. All eight timing regressions pass. Independent UP passes slow observation and injected UNKNOWN controls. The local stream has 21 exact successful numbered ACKs, including quit, 18 independent releases (250–751 ms), zero gameplay UNKNOWN and no replay. All 48 PNGs pass CRC/IDAT validation; 27 are passive film frames. No guest state/config/binding/clock/seed edit, private handler or console/map command was used.
Runtime console, page logs, state, Worker diagnostics and process exits are
retained alongside gameplay. The sampled states report no trap; no Worker
exception/error artifact was emitted. Chrome exited zero through ordinary
completion at 07:08:30.797 UTC. These bounded observations do not establish
broad crash freedom. The first evidence-verifier attempt incorrectly expected
a number field inside the ACK body; the number is its filename/transport
envelope. That host validator error was corrected without runtime replay.
Final drain proves controller, Chrome and passive-film PIDs absent, both ports closed, profile/writer absent. Local artifacts have an independently checked size/SHA-256 manifest. Free disk remained above 5 GB at sampled boundaries. Box ID: none; state NOT_ALLOCATED; expiry and stop receipt not applicable. No box was resumed, deleted or left idle.
Next work needs a locally reviewed route from this starting support to an unambiguous living target or ordinary onward threshold before allocating the single watched original. Historical outer-base topology remains a hint, not current acceptance. Full27, parity, audio and unmeasured FPS remain open.