feat: add regression arm and two verdicts (task 0005) #5
Reference in New Issue
Block a user
Delete Branch "task-0005-regression-arm-and-two-verdicts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task file:
.claude/tasks/0005-regression-arm-and-two-verdicts.mdSummary
Turns a benchmark run into a three-arm experiment and adds a second Regression verdict beside Efficacy, so an edit that silently made a trusted skill worse is caught rather than passing green.
HEADand added automatically whenever the skill's directory differs fromHEAD; a brand-new or unchanged skill degrades to the two-arm efficacy-only shape.wins≥3 ∧ losses≤1; regressionlosses≤1, no wins floor), gates only Efficacy on the hard assertion, and yields a skill-level Regression verdict — green when no case regressed, not-applicable on a two-arm run.Deviations
main,mainwas fast-forwarded to thetask-0004stack tip (a clean linear superset) and pushed, thentask-0005was branched off it — at the user's direction.hard-gate-failfixture case (Efficacy fails on the gate, Regression passes).outputsmap (arm id → final message) to carry the losing-trial evidence the report shows; 0004 had no output text.SKILL.mdprose per the spec's Testing Decisions.Review
Risk
Overall: MEDIUM
skills/benchmark-skill/andchecks/; the core is a pure transform with no external callers.disable-model-invocation) skill-authoring tooling, off any production path.Unaddressed findings
None. All Standards findings (sentence-per-line in two comments, a prose semicolon,
_headlinedisplay-string semicolons, and a repeated comparison-by-rule lookup) and both Spec findings (comparisons stacked instead of side-by-side; cost-table row order) were fixed in the diff.