Skill eval infra error — scrum-master (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 |
scrum-master |
0 |
0 |
2 |
2 |
Regressed cases
scrum-master-hold-cyclic-dag — expected {"decomposition":"good","recommend":"break the cycle — the DAG must be acyclic with a clear entry point"}, got nullscrum-master-hold-well-planned — expected {"decomposition":"good","recommend":"plan is sound; proceed to implementation"}, 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 —
scrum-master(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.
scrum-masterRegressed cases
scrum-master-hold-cyclic-dag— expected {"decomposition":"good","recommend":"break the cycle — the DAG must be acyclic with a clear entry point"}, got nullscrum-master-hold-well-planned— expected {"decomposition":"good","recommend":"plan is sound; proceed to implementation"}, 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.