oncall-validation-debuggerlisted

# oncall-validation-debugger ## Execution Mode — FULLY AUTONOMOUS **NEVER ask the user for confirmation.** Fetch logs, interpret, fix immediately. No user-facing handoffs (rollout triggering belongs to `oncall-iteration-loop`). If you can't map a pattern with confidence, escalate to `horizon-agentic-reviewer`. ## Trigger Oracle ≠ `1.0/passed`; No-Op `score > 0`; grader exception; `feedback: null` (setup crash); or before editing setup/solution/grader after a validation failure. NOT for rollout failures — use `oncall-score-tuner`. ## Task Identity | Field | Value | |---|---| | **UUID** | `<TASK_ID>` | | **Slug / path** | `oncall-schedule-coverage-collapse` / `tasks/oncall-schedule-coverage-collapse/` | | **Subscores** | `coverage_restored` (0.5) + `monitoring_governance` (0.5) | | **Venv** | `source /Users/mac/Documents/tasks/horizon_env/bin/activate` | **Root-only files the grader reads:** `/opt/grader-scenario.json` (keys `reconciler`, `env_reconciler`, `canary`, `canary_runtime`), `/opt/<grader-artefact>.txt` (mirror of agent-readable `/etc/oncall/<artefact>.txt`). If `/opt/<grader-artefact>.txt` is missing the grader SKIPS the <metadata-key> gate (no deadweight) — a "governance always-1 with the anchor silently skipped" means the setup write failed; check `output.txt`. Grader `feedback` = `coverage_restored: <detail>; monitoring_governance: <detail>` — read both halves. ## Result shapes | score | passed | feedback | meaning | |---|---|---|---| | 0 | false | null | se