chore(e2e): calibration report 2026-06-01#347
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
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.
Auto-generated by the E2E Nightly workflow's calibration
step (validation-gap 2b for IS-060, see #148).
See
docs/research/results/upstream_judge_calibration_2026-06-01.mdfor the report.
The diff vs the previous calibration report is the primary
value; this PR will be a no-op on days where regex/LLM
verdicts and rule-class counts match yesterday's run.
The matching JSON sidecar
(
upstream_judge_calibration_*.json) carries thefree-text reasons and exact per-call cost; it is NOT
committed via this PR (excluded from add-paths) so
non-deterministic per-call data does not produce daily
review noise. The sidecar lives in the workflow's
artifact bundle.