Repository navigation
fix(gauntlet): strict validate tolerates the plugin-root CLAUDE.md warning - #406
Merged
Merged
Conversation
…rning from CLI 2.1.289
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.
Claude Code 2.1.289 warns that the plugin-root CLAUDE.md is not loaded as project context and --strict makes it an error, so every pre-push failed locally (CI pins 2.1.287 and stayed green). That warning is intentional (METHODOLOGY ships via hooks). run_validate now accepts a strict failure only when a plain validate passes and every warning it reports is that one.
Proof: new test-gauntlet-validate-benign.sh (red before, 5/5 after; one mutant killed); the real 2.1.289 CLI passes run_validate. Not changed: the CI validate job in validate.yml, still pinned to 2.1.287; the pin bump will need the same tolerance.