Repository navigation
feat(store): validate project annotation manifests and plan bindings - #1680
Merged
Merged
Conversation
leemour
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds provider-neutral validation and pure restore planning for selected project annotations before store export/restore. Hosts validate aliases, facts, direct links and explicit external dependencies, then check explicit destination bindings against a complete target snapshot without opening or mutating a store. Coverage explicitly omits tasks, memories, labels and findings; a ready plan never authorizes accepting proposals.
Strict decoding refuses unknown fields/versions, missing dependencies, unrelated links, alias collisions, decision replacement cycles and byte/record overruns. Link origin, free-form evidence and unresolved targets are preserved. Planning refuses changed or missing sources, wrong reference kinds, collapsed actors and populated targets. Fingerprints include the manifest, bindings and target revision.
Database snapshots and atomic apply remain subsequent work; this PR adds no migration or CLI command. Validation: 23 synthetic cases; full typecheck/build and docs checks; staged Biome and gitleaks. No owner store used.