feat: add versioned evaluation report regression diff - #33
Merged
Conversation
Add diff_versioned_reports() and a --diff CLI flag that compares two --json evaluation reports and surfaces added/removed case IDs, cases that flipped pass/fail (split into regressions and fixed), rubric dimensions that lost their hard gate, and corpus version drift. Exits non-zero on a failing current run or a detected regression. This closes Week 6's exit gate: a repeatable regression report existed since Day 1, but nothing made two reports easy to compare, so a reviewer had to eyeball two full JSON dumps to notice a case quietly stopped passing. Replaces the leftover generic Week 6 roadmap bullets (which restated Day 1's work) with a single Day 5 closeout line. Co-Authored-By: Claude Sonnet 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
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.
Add diff_versioned_reports() and a --diff CLI flag that compares two --json evaluation reports and surfaces added/removed case IDs, cases that flipped pass/fail (split into regressions and fixed), rubric dimensions that lost their hard gate, and corpus version drift. Exits non-zero on a failing current run or a detected regression.
This closes Week 6's exit gate: a repeatable regression report existed since Day 1, but nothing made two reports easy to compare, so a reviewer had to eyeball two full JSON dumps to notice a case quietly stopped passing.
Replaces the leftover generic Week 6 roadmap bullets (which restated Day 1's work) with a single Day 5 closeout line.