Skip to content

fix: count a protected-file violation as a graded failure - #29

Merged
timmoser merged 1 commit into
mainfrom
fix/protection-failure-is-graded
Oct 11, 2026
Merged

timmoser merged 1 commit into
mainfrom
fix/protection-failure-is-graded

Conversation

@timmoser

Copy link
Copy Markdown
Member

What

In coverage accounting, a trial whose protected state failed is no longer counted as missing_grading when its functional verdict is empty.

Why

When a submission edits a protected file, the report deliberately records correctness: null with protected_state: false: the verifier short-circuits, so there is no functional verdict to invent. _dataset then counted that trial as missing grading, which marked the harness's coverage incomplete, blanked its cost and time means, and left the lane with insufficient_evidence.

This surfaced on GPT-6.1 Sol, where Nothing edited src/Serializer.js on node-export-ambiguous. The trial was already a failure in _success; only the coverage count was wrong.

No published report contains such a trial, so no published verdict changes.

Testing

$ uv run pytest -q    → 769 passed

New test: the violating harness keeps complete coverage, counts the trial as a failure, keeps its cost figures and is ineligible; a missing verdict with the protected state intact still counts as ungraded.

🤖 Generated with Claude Code

A trial that edits a protected file is recorded with no functional verdict, because the verifier stops before testing it. Coverage then treated the empty verdict as missing grading, so one such trial left its harness without cost or time figures and the whole lane without a verdict. The protection failure is the verdict; the trial still counts as a failure.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@timmoser
timmoser merged commit 83a6067 into main Oct 11, 2026
@timmoser
timmoser deleted the fix/protection-failure-is-graded branch October 11, 2026 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant