Each data dump is taken from a specific set of mods at specific versions, but today only a 16-character fingerprint of the enabled mod names is persisted (data_fingerprint in the meta table, written at dump.ts:363-371). The actual mod list is read transiently to compute that hash (readModList, dump.ts:222) and then discarded, including the versions it already carries.
Persist the full list at dump and import time: each mod's name, version, and enabled state, stored in the active project's database alongside the existing fingerprint and synced_at. This records the provenance of the project's reference data and gives later features a concrete previous state to diff against, instead of a hash that can only say that something changed.
Display it: show the project's mods and versions somewhere in the UI, for example a settings or project-info surface, so the user can see exactly what their saved plans were built against.
This is the data foundation for drift detection in #27, which needs the previous name and version set to report what was added, removed, enabled, disabled, or version-changed, and it feeds the migration capture in #26, where a mod's version changing is the cue to re-scan its migration files.
Each data dump is taken from a specific set of mods at specific versions, but today only a 16-character fingerprint of the enabled mod names is persisted (
data_fingerprintin themetatable, written atdump.ts:363-371). The actual mod list is read transiently to compute that hash (readModList,dump.ts:222) and then discarded, including the versions it already carries.Persist the full list at dump and import time: each mod's name, version, and enabled state, stored in the active project's database alongside the existing fingerprint and
synced_at. This records the provenance of the project's reference data and gives later features a concrete previous state to diff against, instead of a hash that can only say that something changed.Display it: show the project's mods and versions somewhere in the UI, for example a settings or project-info surface, so the user can see exactly what their saved plans were built against.
This is the data foundation for drift detection in #27, which needs the previous name and version set to report what was added, removed, enabled, disabled, or version-changed, and it feeds the migration capture in #26, where a mod's version changing is the cue to re-scan its migration files.