docs: describe v0.7.2 and ask for real failure reports#96
Merged
Conversation
The scope section still listed 'expanding the frozen dataset beyond six cases' as a next priority, which three suites and 35 cases ago stopped being true. It now names the two things that actually matter: the held-out interval is still wide at twelve cases, and no savings figure is defensible without a with-and-without agent run. Adds an explicit ask for failure reports. A case where FixMap ranks the wrong file on someone else's repository is worth more than one selected by our own rule, because it comes from real distribution rather than our sampling. 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.
Updates the version section for v0.7.2 (
--explain, confidence intervals, misleading-top-result rate).Corrects the scope section, which still listed "expanding the frozen cross-repository dataset beyond six cases" as a next priority — three suites and 35 cases out of date. It now names what actually matters: the held-out interval is still wide at twelve cases, and no savings figure is defensible without a with-and-without agent run.
Adds an explicit ask for failure reports, because a case where FixMap ranks the wrong file on someone else's repository is worth more than one selected by our own rule.
Also fixes a stale v0.7.1 release link in the growth kit.
🤖 Generated with Claude Code