Repository navigation
fix: resolve Quick Flow review failures - #21
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.
Summary
Makes Quick Flow review scope-aware and recoverable. A gate-approved plan is hash-recorded as the review baseline, so documented deferrals and out-of-scope work do not fail review.
Changes
approved-scope.jsonafter Quick Plan approval and requires implementation/review to validate it.FAILas a data verdict, preserving the work in a WIP commit before an explicit partial-ship, Feature Flow escalation, or abort choice.Testing
python3 -m unittest discover -s testspython3 scripts/package-preset.pypython3 scripts/build-catalog.pyCloses #20