Skip to content

fix(import): validate export rows before mutating the store - #496

Merged
possiblyneal merged 1 commit into
mainfrom
fix/436-import-preflight
Nov 21, 2026
Merged

possiblyneal merged 1 commit into
mainfrom
fix/436-import-preflight

Conversation

@possiblyneal

Copy link
Copy Markdown
Owner

Intent

Closes #436

Validate export sections and fields used by indexing before an import changes the store, so malformed keyed records cannot interrupt a replace after deletion starts.

Read first

  • src/functions/export-import.ts — import preflight.
  • test/export-import.test.ts — checks that invalid input leaves existing rows intact.

Decisions

Out of scope

  • Transactional rollback on storage or provider failures.

Verified

  • Build, generated hooks, skills, typecheck, both Recall gates, and full suite: 3,239 passed, one skipped.

Not verified

  • No live store was used.

Merge danger

Door: Reverting restores prior input handling; it cannot undo a replace import.

Blast radius: Export imports via REST and MCP.

Reject malformed sections and indexing fields before replacement. Keep\nlegacy keyless rows skippable under all import strategies.

Refs: #436
Generated-By: gpt-6.2-sol
@possiblyneal
possiblyneal merged commit e1de1ca into main Nov 21, 2026
3 checks passed
@possiblyneal
possiblyneal deleted the fix/436-import-preflight branch November 21, 2026 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Replace import empties the store before validating optional sections

1 participant