Repository navigation
Rehearse approval hook error after a local state change - #320
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.
Adds a fourteenth project-authored host rehearsal case. The approval fixture writes an in-memory marker and throws; dispatch returns
blocked/approval_error, with one approval request, no claim, and no tool callback. The guide and builder distinguish this from a guarantee that a real authorization system did not change. Regenerates the report and content-hash assets.Focused Node tests, rehearsal
--check, and asset--checkpass locally. The marker is only a local fixture write, not human approval, provider activity, delivery evidence, or proof of production safety.