Skip to content

feat(evals): canonical top failure modes with failureModeDetail (phase 11) - #26

Merged
Yosoyepa merged 2 commits into
mainfrom
phase-11-top-failure-modes
Aug 4, 2026
Merged

feat(evals): canonical top failure modes with failureModeDetail (phase 11)#26
Yosoyepa merged 2 commits into
mainfrom
phase-11-top-failure-modes

Conversation

@Yosoyepa

@Yosoyepa Yosoyepa commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Audit GAP #10: five named top failure modes each carry >=50 cases at the literal failureMode level (reminder-atomicity-violation 50, delivery-concurrency-violation 50, idempotency-replay-duplicate 57, temporal-misinterpretation 60, security-boundary-breach 50). Fine-grained slugs preserved in the new optional failureModeDetail field; runner/CLI gain --failure-mode-detail. Suite unchanged: 299 cases, same IDs/contractRefs/expected.

Gates: ruff/mypy clean, pytest 853 passed, eval gate 299/299, coverage 92%, diff-cover 100%.

Audit GAP #10: five named top failure modes now each carry >=50 cases
at the literal failureMode level. The previous fine-grained slugs are
preserved in the optional failureModeDetail field, and the runner/CLI
gain a symmetric --failure-mode-detail filter.
@Yosoyepa
Yosoyepa merged commit 24b2cc4 into main Aug 4, 2026
5 checks passed
@Yosoyepa
Yosoyepa deleted the phase-11-top-failure-modes branch August 4, 2026 23:14
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