fix(db): normalize diffResults on import #16
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary\nFixes a full-session import failure when exported diff results include
fanVersionId: null.\n\n## Root Cause\nIndexedDB composite keys require valid key values; diffResults are exported withfanVersionId: null, but the store keyPath usesfanVersionId(normalized to "" at write time elsewhere). Import bypassed that normalization and wrote records directly, causingDataError.\n\n## Changes\n-services/db/operations/imports.ts: normalize diffResults records before storing.\n- Tests: strengthen diffResults export/import assertions + add adversarial/unit coverage for provider/telemetry paths.\n-docs/WORKLOG.md: log entry.\n\n## Testing\n-npx tsc --noEmit\n-npm test -- --run