Sized local asset manifests
A schemaVersion1 local browser manifest may give each entry a safe integer size (bytes) and loadMode:
required: fetch bytes before launch; failure rejects launch. Native modules and fonts remain required in generated lazy trees.lazy: mount an HTTP range provider with its declared size. Mounting performs no HEAD or GET. A guest read fetches the missing 1 MiB cache chunk through the existing parked-read Loading/Retry/Quit UI. No eager fallback is hidden behind this mode.background: mount identically, then after the guest starts warm the initial cache chunk of up to eight explicitly marked files, serially. Remaining files stay on demand and are counted as deferred. Errors are recorded onwine.backgroundAssets; later guest reads retain retry behavior. Stopping the app aborts pending range requests and prevents further warmup jobs. Background is not a whole-file or whole-tree prefetch.
required with optional:true is contradictory and rejected. Background startup is idempotent within one running-host lifetime. A load after stop creates a fresh lifetime and warmup queue; old providers retain their cancelled signal. Legacy entries without loadMode keep their existing behavior. Existing httpRange discovery and measured preloadRanges are unchanged. Explicit lazy/background modes cannot also request synchronous image decoding or launch preloads. Aliases of the same URL share one provider; contradictory size/mode declarations fail validation. A provider's lifetime signal is separate from the launch download signal.
Candidate preparation (tools/fetch-candidate-corpus.js --id=ID --prepare) emits exact stat sizes. A candidate's browser policy can set defaultLoadMode and per-relative-path fileLoadModes. Regardless of a lazy default, EXE/DLL/OCX/VBX/DRV/TTF/TTC/FON stay required. Both Dredmor candidates opt in; no game bytes are committed. Regenerate the ignored local manifests when changing policy or fixture contents. Wine Ops explicitly advertises byte-range capability in its private emulator entry. Its sized files use validated HTTP 206 responses and the bounded VFS chunk cache, so a small read does not download a complete large archive. An ignored Range request can fall back only when the server returns the complete body with the expected decoded length; concurrent first reads share that probe. Other/static hosts retain ordinary full GETs for individual files or Berrry deployment parts. For split releases, only the parts intersecting the guest read are downloaded; unrelated parts remain unloaded. No HEAD is needed for a known size.
Auditing installed games
node tools/audit-app-loading.js --root=CHECKOUT compares registry/local-manifest loading decisions with actual file sizes. --write-sizes fills absent local-manifest sizes with stat-verified lengths, preserves explicit loading policies and registry metadata, and saves the original manifest beside it. It removes an accidental reference to the manifest itself. Stale declared sizes, missing files and escaping paths are reported rather than guessed. This does not install absent game data.
Run node tools/gen-app-file-sizes.js --data-root=CHECKOUT to refresh inline registry lengths. Size stamping also applies to entries with explicit httpRange/loadMode: it supplies metadata without overriding their policy. Unsized entries otherwise stay eager. Native modules, synchronous configuration/font readers, persisted files, Win16 and synchronous fault-reader routes retain their required residency.
The October 19 Wine Ops audit repaired 34 manifests and populated 318 missing inline lengths. Black & White 2's 364 unsized companion files become 7 eager (4,281,670 bytes) and 357 lazy (901,689,101 bytes), excluding its separately loaded executable. Everything.stuff is 432,577,472 bytes and can now be fetched by section on Wine Ops. Ten game manifests are absent on this box; this audit does not claim those games are installed or establish gameplay compatibility.
Validation includes actual host/VFS mounting of6000 files with zero startup requests, sparse reads, aliases, metadata rejection, cancellation, required failures, background bounds/stop/errors, and actual preparation with native/font classification. This establishes loader behavior, not Dredmor startup or gameplay compatibility; those require a recorded ordinary launch.