Diablo II XP401 camp exit: capacity prerequisite blocked before allocation
The requested continuation did not launch. Direct /home free-space observations were 1,482,924,032 bytes at initial inspection and 1,497,505,792 bytes at the recorded refusal, both below the required strictly-greater-than-1,500,000,000-byte floor. This is a capacity prerequisite blocker, not a new camp-route or runtime failure. No exit, combat, XP, level, quest consequence, or successor save was established.
Evidence: scratch/runs/20261112-diablo2-xp401-camp-exit-0100/. The qualified fresh-browser XP401 checkpoint, parent report 8c4ab88de, remains the continuation point. All four original 1540 earned-save files were independently reread against the parent export review and remain unchanged. No XP380 or death-outcome state was used. Parent native stats remain historical evidence: level1, XP401, life53/55, Den uncleared. They were not observed in a new browser here.
Read-only verification passed for 28 original-media entries in the parent manifest, module04 SHA-256 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17, inherited helper identities and proof-report references, and the three provider files against their exact published bytes in 5c2c410a5. Accepted matrices were referenced by hash, not rerun. No helper edits or production code changes were made; no build was required.
The actual unchanged startup-data.cjs reader was attempted locally and refused with ENOENT for the parent's raw runtime-pins.json, before browser/allocation/input. Worker818484 had concurrently preserved that metadata as runtime-pins.json.gz; its MANIFEST-RECOVERY-0050.md documents recovery. Reading the compressed bytes without restoring or changing that worker's files verified all four manifest mounts and original media. This does not claim a successful actual startup-reader execution. A future launch must first resolve the manifest in its owned startup inputs and pass the actual reader. No missing-file failure was bypassed for execution.
Git identity, relevant binary diff, owned-note addition patch, hashes and observations are retained in the run. Git remains the source archive. No media or source archive, cache cleanup, reserve/vendor/DB/session modification, gameplay input, replay, guest write, console command, or forced call occurred. Parent command83 remains refused before input; historical lifecycle UNKNOWNs remain unchanged.
New box: none / NOT_CREATED. Expiry null; stop receipt inapplicable. No allocation, provisioner, browser, renderer, or deadline watchdog was started. The local coordination watcher was terminated and actually waited; its pipe EOF observations are recorded separately. No preexisting box was resumed, stopped, or deleted.
Next: once actual free disk exceeds the floor, use one independently watched fresh private box, complete provisioning and SHA verification, pass the whole-four startup reader, wait for the actual native menu, Load SAMEHERO normally, verify XP401/life53, inspect fresh full map/UI frames, and find the visible camp exit. Only native earned consequences justify SaveExit/full-four export/normal Load/fresh movement.