Skill eval infra error — dev-lead (holdout)
Outcome: error — the eval could not score the skill (infrastructure failure: e.g. every model in the fallback chain throttled, or bad usage / missing tooling).
This is an infra signal, not a skill regression: the model never produced a scorable answer, so the held-out set is currently un-scored and needs a look. Report-only (Phase 1): it does not block any merge.
| skill |
score |
passed |
failed |
total |
dev-lead |
0 |
0 |
2 |
2 |
Regressed cases
dev-lead-hold-underspec — expected {"readiness":"needs-scoping","recommend":"pin a target metric and scope before implementing"}, got nulldev-lead-hold-wellscoped — expected {"readiness":"ready","recommend":"implement as-is; the failing test defines done"}, got null
View the workflow run
Auto-managed by notify-eval-health.sh — this issue is updated in place each run and closed automatically on recovery.
Skill eval infra error —
dev-lead(holdout)Outcome:
error— the eval could not score the skill (infrastructure failure: e.g. every model in the fallback chain throttled, or bad usage / missing tooling).This is an infra signal, not a skill regression: the model never produced a scorable answer, so the held-out set is currently un-scored and needs a look. Report-only (Phase 1): it does not block any merge.
dev-leadRegressed cases
dev-lead-hold-underspec— expected {"readiness":"needs-scoping","recommend":"pin a target metric and scope before implementing"}, got nulldev-lead-hold-wellscoped— expected {"readiness":"ready","recommend":"implement as-is; the failing test defines done"}, got nullView the workflow run
Auto-managed by
notify-eval-health.sh— this issue is updated in place each run and closed automatically on recovery.