fanout-cve-iteration-looplisted

# fanout-cve-iteration-loop ## Execution Mode — FULLY AUTONOMOUS **NEVER pause for confirmation.** Run every phase, command, and fix without asking. The only manual step is the user triggering the eval batch in the Horizon UI. ## Goal Drive fanout-cve-rollout to shippable. This is a **reward-shaped** task (5 independent subscores × 0.2) — the exit bar is Oracle 1.0 + a dense, correct partial-credit gradient, NOT an avg < <TARGET_MEAN> variance target. ## Trigger "Iterate the fanout-cve task until it passes"; "push and validate fanout-cve-rollout"; anything implying repeated push → validate → analyze → fix. Single steps → invoke the specialist directly. ## Task Identity | Field | Value | |---|---| | **UUID** | `<TASK_ID>` | | **Slug / path** | `fanout-cve-rollout` / `tasks/fanout-cve-rollout/` | | **Horizon root** | `/Users/mac/Documents/tasks` | | **Venv** | `source /Users/mac/Documents/tasks/horizon_env/bin/activate` | ## Who does what The agent executes everything except **triggering the eval batch in the Horizon UI**. ## Exit conditions (all, same version) 1. Oracle `passed: true, score: 1.0`, all five subscores `=1` 2. Live red-team: no BLOCKING findings — **especially the stale-env drift live (CM `peer`, pod env `full`), grader truth root-only, a no-op agent scoring 0, and a ConfigMap-only fix scoring exactly 0.2 with the roll-the-pods hint** 3. Rollout gradient: the score histogram spans `{0,0.2,…,1.0}`; no subscore deadweight; a fair share reach 1.0 4. `pods_roll