Diablo II: exact compressed startup manifest reader fixed; native run capacity blocked
The actual prepare/emitted browser seam now reads the declared startup manifest as raw bytes or its verified local sibling gzip. The production reader requires the original raw size and SHA before parsing, validates the runtime schema and pinned restore manifest, and verifies all four raw save dependencies and their HTTP/VFS destinations. A corrupt present raw file cannot fall back to gzip. Encoded save files cannot substitute for the raw URLs required by the ordinary native loader.
Evidence: scratch/runs/20261113-diablo2-exact-manifest-0120/. Its own prepare.cjs consults the per-run MANIFEST-RECOVERY-0050.md recovery contract and exact recovery-index row. The original 1615-attempt2 runtime manifest remains 173,721 raw bytes, SHA-256 bd7257f728bd8e079a1473adb84cc6df7a3808a82f392479f0d67cc2f2327f8e; its retained gzip SHA is cf3416c51c58f73fc9c9473b86c81fd7e90d7c6a514859ab8aec794412ee76dc. No original manifest, expected pin, parent helper, or save was rewritten or restored. This fixes the actual ENOENT reader dependency reported in parent ee4681bc1.
The emitted browser performs the new reader check as its first operation and supplies the returned mounts directly to the existing native launcher. Remaining inherited helpers are referenced at their original paths; only the owned new browser has its startup/pins/source-helper reads adapted. The owned prepare and browser are retained as addition patches, with exact source Git SHA and relevant binary diff. This is an executed local prepare/consumer fix, not a claim of remote provisioning or native startup.
Focused tests passed: raw/gzip identity and bounded decompression/refusal controls, seven independently pinned invalid-schema cases, and actual prepare/emitted-consumer integration. The integration has 34 child executions: two equal successful closures and 32 refusals through data-check and normal native-entry paths. Sixteen failed prepare calls also refuse before writing an output prefix. Corrupt/truncated/wrong-SHA/wrong-manifest/missing-manifest inputs, changed restore metadata, every missing save, and encoded-save substitution are rejected with zero trapped process, network/API, browser, input or file-write effects. The physical test stage is removed. The locked build passed; module04 remains SHA-256 04c534192ee3fe39e388536c2ce710c12c47a5cd2ca4d95c19f9d00b1e8f0a17.
All four original XP401 saves, 28 original media references, 24 inherited proof/helper references, and three exact published provider files at 5c2c410a5d606d808898cce1b6e3c5d10786228b were reread and verified. Five published provider qualification references were also verified. Accepted XP401 fresh-Load/input and provider matrices were reused by exact SHA without rerunning them. The 1615 qualification remains historical: level1, XP401, life53/55, Den uncleared; no XP380/death state was mixed in.
The distinct continuation blocker is actual capacity. At the recorded decision /home had 1,481,535,488 bytes available, below the strictly-greater-than-1,500,000,000-byte floor. The separate resource worker had terminated with zero reclaim. No holding loop, API allocation, watchdog, provisioner, Chrome, renderer, or gameplay input was started. Camp exit, combat, native earned consequence, new full-four export and successor Load remain unproved. This is not a new guest route defect.
Box NONE / NOT_CREATED, expiry null, stop receipt inapplicable. No inherited box was changed. Actual outer-tool separate stdout/stderr EOF observations are UNKNOWN; the build/test tool exits and coordination-watcher termination are recorded without upgrading inherited lifecycle UNKNOWNs. No source/media archive, retired log/cache/reserve/vendor/DB/session modification, other worker edit, guest-state write, console/force call, child worker, or public deployment occurred.
Next requires actual disk capacity, a final native helper freeze integrating the published explicit RAM stage and qualified compact consumers, then one fresh independently watched private box with complete joined provisioning/SHA verification. Mount the unchanged XP401 four, wait for the native menu, normal Load/stats/quest/fresh move, then inspect the actual camp exit and a short combat/retreat. Only native XP/quest/level proof justifies ordinary SaveExit/title/full-four export/normal Load/fresh movement. Den remains uncleared until native proof.