fanout-cve-validation-debuggerlisted

# fanout-cve-validation-debugger ## Execution Mode — FULLY AUTONOMOUS **NEVER ask for confirmation.** Fetch logs, interpret, fix immediately. No user-facing handoffs. Can't map a pattern → 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. NOT for rollout-gradient issues — use `fanout-cve-score-tuner`. ## Task Identity | Field | Value | |---|---| | **UUID** | `<TASK_ID>` | | **Slug / path** | `fanout-cve-rollout` / `tasks/fanout-cve-rollout/` | | **Subscores (0.2 each)** | `cve_image_patched`, `configmap_reverted`, `pods_rolled_live_env`, `gitops_committed`, `argocd_synced` | | **Venv** | `source /Users/mac/Documents/tasks/horizon_env/bin/activate` | Grader `feedback` is `name=0/1 (detail)` for each subscore, joined by `; `, plus a partial-fix HINT. Root-only file the grader trusts: `/opt/grader-cve.json` (`patched_version`, `vulnerable_versions`). Oracle = `1.0` only when all five are 1. ## Step 1 — Fetch + read ```bash cd /Users/mac/Documents/tasks && source horizon_env/bin/activate horizon tasks validate-logs -a oracle tasks/fanout-cve-rollout 2>&1 cat tasks/fanout-cve-rollout/.validation/*/result.json 2>/dev/null | python3 -m json.tool ``` ## Step 2 — Map symptom → cause → fix ### Branch A. `feedback: null` / `score: 0` — setup crash | `output.txt` pattern | Cause | Fix | |---|---|---| | `k3s is not ready after 180 seconds` | `ENABLE_