Repository navigation
Clarify bounded recovery and unresolved publication state - #15
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
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.
Clarify recovery when a GitHub write result is uncertain. Governance writes now remain suspended while bounded authoritative reads resolve state; resumption requires refreshed bindings and preview within existing authority. Release recovery now reports unknown publication visibility instead of claiming failed readback keeps a release private.
Link the two owning wiki pages to the canonical recovery sections. Preserve all descriptions, scope and authorization gates, signing/publication order, and final evidence requirements. VERSION and both manifests remain unchanged at 0.1.0.
Validation: cargo make check, both Plugin Creator validators, both Skill Creator validators, diff/link checks, and exact four-file materialized package hash checks pass. An independent Astra paired synthetic review covered positive, adjacent-negative, and recovery cases; it found no selected safety regression, but does not establish live execution or measured improvement. Full provider operations were not performed.