Repository navigation
test(projects): verify published selected annotation restore - #184
Merged
Merged
Conversation
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
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.
An isolated project reconstruction needs explicit destination bindings and lifecycle preservation before it can support gathering comparisons. Add an independent published-Core0.374 SDK fixture that restores one alias, one proposed fact and one evidence link into separately seeded destination IDs.
The check preserves source bytes, verifies preview leaves target bytes unchanged, rejects a stale namespace fingerprint, preserves the bound author and unrelated facts, and refuses repeat restoration without duplicates. It records exact source/runtime/integrity/entry hashes; registry bytes match the validated release artifact. Existing Core0.373 results remain frozen.
The README includes the reproduction command and limits: selected facets only, no owner data, no live reset, no extraction/retrieval score. Validation: published-package driver passes, changed files pass Biome, repository documentation checks pass.