Forsaken beyond-corridor attempt, 7 November 2026

Stopped before allocation at the required disk floor. No new native gameplay consequence was obtained. The previously reviewed Volcano corridor, death and respawn remain the latest gameplay evidence.

Evidence: scratch/runs/20261107-forsaken-beyond-corridor/. Candidate: forsaken-demo.

The required CLAUDE.md, sandbox skill, capture workflow and prior Forsaken note were read first. Recent Aranna balanced-release and SimGolf pulse/control sources were inspected read-only. A run-local draft driver uses the SimGolf pulse, which schedules UP before awaiting DOWN and closes on UNKNOWN. It has not passed complete driver qualification and must not launch originals. No emulator contract mismatch was demonstrated; production code is unchanged.

The first full transitive static CommonJS import scan failed before Chromium started: @node-3d/glfw cannot be resolved from lib/headless-gl.js. This path is reached through optional test/helper dependencies; the scan does not prove that the browser route needs native GLFW. imports.json preserves the exact stack. Do not mask that failure or report all imports qualified. A subsequent qualification must distinguish the executable browser closure from unrelated optional test entry points while retaining every actual and lazy driver import.

At 11:26:07 UTC shared /home had 1,891,045,376 bytes free; the recorded second check at 11:26:32 had 1,948,598,272 bytes, both below the requested 2,000,000,000-byte floor. Owned run inputs occupied about 549 KB, so removing them would not restore the floor. No peer evidence was deleted or compressed. disk-blocker.json records the checks. This is a concrete allocation blocker, not a RAM gate or a guest failure.

All 873 original fixture path/hash references match the retained Forsaken inventory before and after this attempt. No fixture, layout, licence, guest code/config/save/clock, replacement DLL or media was changed. No source/media archive was made. Source identity is main 202c5d2b90948b5a52559eaa3bfce0214d2ff47d plus relevant-source.patch and lib_wininit-boot.js.new.patch; run-specific inputs are preserved in owned-driver-inputs.patch. JavaScript syntax checks pass; no focused emulator regression or full build is claimed for this docs-only change.

No allocation request, UUID box, Chromium process, guest Worker, original launch, native input, capture, provider identification or shutdown occurred. Box ID/state/expiry and executing CPU/render module hashes are unavailable. There is no runtime custody to hand back, and no profile, writer, held input, owned runtime PID or port was created. Actual trusted input, exact ACK, stale/replaced-owner and deadline negatives remain unqualified for this draft. No FPS, audio, parity or full-27 claim is made.

Next: restore the shared disk floor, complete the staged browser-driver import and real Chromium qualification, then use one fresh UUID-idempotent box with an immutable 25-minute browser deadline and the delegated ordinary shutdown. Choose controls from fresh inspected full-page captures toward a new room, intermediate shield/hull damage, enemy defeat or native objective. Do not replay UNKNOWN or reuse an old box.