crusader 1.01 exploration

docs/map-rendering.md

@@ -26,14 +26,46 @@ Internal package layout:
 
 Current supported data roots:
 
-- `STATIC` for No Remorse
+- `STATIC` for the default No Remorse retail set when populated
+- `STATIC_1.01` for No Remorse 1.01
+- `STATIC_DEMO` for a future No Remorse demo set
+- `STATIC_JP` for a future No Remorse Japanese set
 - `STATIC_REGRET` for No Regret
 
 Current asset note:
 
 - `STATIC_REGRET` in this workspace now includes `FIXED.DAT`
+- `map_renderer/STATIC` now contains a populated No Remorse retail-style asset set including `CRUSADER.EXE`, `FIXED.DAT`, and `EUSECODE.FLX`
+- `map_renderer/STATIC_1.01` currently contains `CRUSADER.EXE`, `FIXED.DAT`, `EUSECODE.FLX`, `DTABLE.FLX`, and the rest of the shipped renderer inputs
 - the renderer still accepts `--fixed-dat` so alternate map copies can be tested without changing the rest of the static asset path
 
+## Versioned Asset Audit
+
+Current map-renderer workspace findings for No Remorse version support:
+
+- `map_renderer/STATIC` and `map_renderer/STATIC_1.01` are both populated and can now be compared directly
+- verified SHA-1 and size differences exist between the retail-style `STATIC` set and `STATIC_1.01` for `CRUSADER.EXE`, `DAMAGE.FLX`, `EUSECODE.FLX`, `FIXED.DAT`, `GLOB.FLX`, `OVERLOAD.DAT`, `TYPEFLAG.DAT`, `UNKCOFF.DAT`, and `UNKDS.DAT`
+- `CRUSADER.EXE` differs materially: retail-style `STATIC/CRUSADER.EXE` is `991878` bytes with SHA-1 `5F3EB75202FA54CDC6703B875BFC505EB1EE320D`, while `STATIC_1.01/CRUSADER.EXE` is `979382` bytes with SHA-1 `3BE9A196E5504E7ACB4E84FE3DF16503C16616FD`
+- `EUSECODE.FLX` differs materially: retail-style `STATIC/EUSECODE.FLX` is `556613` bytes with SHA-1 `D7912724673F27C5D2E5B4FB9C41B22D67AE828A`, while `STATIC_1.01/EUSECODE.FLX` is `418556` bytes with SHA-1 `B2176648C9A795156AF764E4CEB45E4CF1973010`
+- `FIXED.DAT` differs materially: retail-style `STATIC/FIXED.DAT` is `3735392` bytes with SHA-1 `4A8CF1ED99996B8B37A3A0FD33ACF09C1BB642E5`, while `STATIC_1.01/FIXED.DAT` is `3734592` bytes with SHA-1 `685757B0AC8871C0247F7B5963C4EB5ED68DC89C`
+- `GLOB.FLX` also differs: retail-style `STATIC/GLOB.FLX` is `264974` bytes with SHA-1 `9E26B13F81E425C33CFB1D5A6CF202AAEB8C0F00`, while `STATIC_1.01/GLOB.FLX` is `264884` bytes with SHA-1 `01A31DAF4806946B8AEA0D3483DD5C3BA1D149ED`
+- many shipped art/palette/data files are unchanged between these two roots, including `ANIM.DAT`, `DTABLE.FLX`, `SHAPES.FLX`, `GAMEPAL.PAL`, `FONTS.FLX`, `GUMPS.FLX`, `TRIG.DAT`, `WPNOVLAY.DAT`, and `XFORMPAL.DAT`
+- the web renderer should therefore treat available versions as detected data roots rather than assuming one remorse asset set stands in for all releases
+
+Renderer version-support changes:
+
+- the UI now exposes a version selector above the map selector and only lists variants whose static roots actually contain usable map data
+- No Remorse variants are modeled as separate cache/export identities so `STATIC_1.01`, future `STATIC_DEMO`, and future `STATIC_JP` builds do not collide in `.cache` or `site/data/maps`
+- shared annotation sources such as the remorse shape catalog CSV and DTable name dump remain reused across No Remorse variants until version-specific tables are added
+- the build path now resolves `REMORSE_XFORMPAL_PATH` for every No Remorse variant, not just the legacy `remorse` id
+
+Follow-up comparison plan once more data roots are added:
+
+- compare `CRUSADER.EXE` hashes between `STATIC`, `STATIC_1.01`, `STATIC_DEMO`, and `STATIC_JP`
+- compare `FIXED.DAT` hashes and map counts between versions
+- compare `EUSECODE.FLX` hashes between versions
+- record any map-count or mission-table differences in this note once the missing folders are populated
+
 The immediate goal is practical and narrow: load a fixed map, expand glob placements, decode the required shapes from `SHAPES.FLX`, apply `GAMEPAL.PAL`, and render a deterministic PNG.
 
 ## Source Cross-Checks Used