Eval failures now say whether they're reproducible and flag runs killed before reporting.
What's wrong with this entry?
When the eval harness's integrity check fails, each failure is now labelled as provokable or unprovokable, and a note is added when the child agent was killed before it could report which calls it refused, so a killed run is no longer indistinguishable from a genuine mismatch.
the child was killed before it reported which calls it refused itself
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
plugin evalno longer swallows piped inputBoth mention eval
-
v2.1.234
Plugin eval reference documents image grading and new exit codes
Both mention eval
-
v2.1.234
claude plugin evalhandles termination signals and cleans up its outputBoth mention eval