Observation
Built-in game knowledge contains entities, aliases, and title mappings that rarely change between starts. Re-importing the same seed data repeats serialization and database work without changing the searchable result. The import process needed a durable way to distinguish an unchanged source from a new revision.
Treatment
The importer serializes the seed records in a stable order and calculates a SHA-256 content hash. It stores that hash with a source key in the import state. On the next run, matching source and hash values return skipped=True before the entity and alias write stage. When the input changes, the importer proceeds with the transaction and records the new state.
Verification
Focused tests run an initial import and confirm it is not skipped, repeat the same input and confirm the skipped state with unchanged stored metadata, then change the title-mapping seed and confirm that import resumes with a different hash. The implementation order shows the early return before writes; the tests verify state transitions and do not claim a measured SQLite write count.