Repository navigation
Validate reviewed plan evidence and expose failed-apply recovery - #43
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.
Evidence reports previously checked only the shape of an external ActionPlan digest, allowing altered plan contents to be cited under an old digest. Report input now shares the same canonical content and root-identity validation used before applying a plan. Failed applies also expose retained backup locations in both text and JSON; incomplete rollback has separate recovery evidence and never claims a restored/applied Receipt or retries into a replacement directory.
Validation: 718 distinct checks passed with one existing skip; initial loopback/built-CLI prerequisite failures were retained and the affected 18 checks then passed. TypeScript, lint and build passed. The built CLI completed plan/apply/verify/report (exit 1 before, 0 after), rejected five altered plans without data changes, and real-filesystem fault injection verified both rollback outcomes and backup settings. Synthetic data only; no Skill script, provider, deployment or installation change.