A rebuilt manifest leaves out every entry whose files are missing on that machine, so a run
with failed downloads silently dropped entries from the tracked file (PR #7 carried one 42
audio entries short; all 42 still resolve upstream). The run now keeps the current manifest,
prints the entries it would drop (also in the report) and exits 1. The tool runs main only as
a script so the guard and parseArgs can be tested; ASSETS.md documents the flag.
data/assets.json pointed 灼热源石虫 / 炽焰源石虫 at /assets/local/ files that only exist
where tools/local-extract ran, with no fallback: without the extraction the
asset tests failed, setup re-ran fetch-assets (rewriting the tracked manifest)
and the slugs drew as icon diamonds.
- The web model stays the 源石虫 alias (spine + spineAliasOf). The official
model is enemies[id].spineLocal: file names in the data/local-assets.json
group spine/enemy/<id> plus the parsed metadata, from the committed
tools/assets/local-enemy-spines.json (fetch-assets --local-spines refreshes
it from the extracted files, read only). The manifest is byte-identical with
or without the extraction and has no /assets/local/ URL.
- Client: assets.js spineEntry uses spineLocal only when the local manifest
lists every file (createFieldView awaits assets.local() with the manifest);
UnitView loads the web model when the local one fails.
- extract.py writes the atlas with size: / pma: true itself (the same text as
atlas.mjs normalizeAtlas), so the extraction is usable without a fetch pass.
- setup notes when an older extraction lacks the enemy models.
sganggs