Add CLAUDE.md pointing at the practice that already exists - #137
Merged
Conversation
TESTING.md, CONTRIBUTING.md and FORMAT.md carry the practice this repository runs on, but nothing loads them at the start of a session, so they are found by accident or not at all. This restates none of them. It points at them, and adds only what is not already written down: that --no-build reuses the previous binary when the build fails, that scripts/mutate.sh exists and why it refuses a dirty tree, that CI now gates on five runners across both architectures, and that BSD grep quietly corrupts a coverage scan on macOS. Co-Authored-By: Claude Opus 5 <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.
TESTING.md,CONTRIBUTING.mdandFORMAT.mdalready carry how this repository is built and proven. Nothing loads them at the start of a session, so an agent working here finds them by accident or not at all — and this session it was by accident, several PRs in.This restates none of them. It points at them, and adds only what was not written down anywhere:
dotnet test --no-buildsilently reuses the previous binary. CONTRIBUTING.md covers the analyzer/exit-code trap; this is its sibling. If the build failed, the test result you are reading belongs to the last thing that compiled. It produced two confidently reported results this month that were measured against the wrong binary.scripts/mutate.shexists. I hand-rolled mutations all session and never used it, which is the clearest evidence that a pointer was missing. It enforces the dirty-tree refusal whose rule "was learned three times".-latestform.grepcorrupts a naive coverage scan on macOS —BloomFiltermatches insideBloomFilter64. That produced a wrong coverage number in an earlier PR body.It also records the roster rule in the place an agent will read first, including its corollary: no counts in comments or docs, since a count is a hand-maintained roster and one here was wrong for several releases.
Deliberately not included: anything about how the maintainer prefers to work. This file is public; that belongs elsewhere.
Docs only — no code, no build impact.