feat: add must/should priority to verification signals#790
Merged
Conversation
All signals were treated equally — any failure caused CONTINUE and looping. But "app runs" and "all tests pass" have different user impact. Add priority: - must: failure blocks completion (user cannot use the artifact) - should: failure reported as known limitation (artifact is usable) Changes: - Design Principle 5: signal priority (must/should) - Plan: Verification Signals require must/should per signal - Plan self-check: new item 4 — every signal has a priority - verify-test: only must failures cause CONTINUE - Bump to 1.0.20 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
Context
Previous design treated all signals equally, causing excessive looping over minor issues (test coverage, placeholder text) while the core artifact was already functional.
Test plan
🤖 Generated with Claude Code