oncall-iteration-looplisted

# oncall-iteration-loop ## Execution Mode — FULLY AUTONOMOUS **NEVER pause for confirmation at any point.** Run every phase, command, and fix without asking. Two valid paths → pick the safer. The only manual step is the user triggering the eval batch in the Horizon UI. ## Goal Drive oncall-schedule-coverage-collapse from "needs work" to "shippable". Done when all exit conditions hold; each cycle picks the right specialist and applies the smallest safe fix. ## Trigger "Iterate the oncall task until it passes"; "push and tune until avg < <TARGET_MEAN>"; "run the full loop on oncall-schedule-coverage-collapse"; anything implying repeated push → validate → analyze → fix. Single steps → invoke the specialist directly. ## Task Identity | Field | Value | |---|---| | **UUID** | `<TASK_ID>` | | **Slug / path** | `oncall-schedule-coverage-collapse` / `tasks/oncall-schedule-coverage-collapse/` | | **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**. Never tell the user to push/validate/pull. ## Exit conditions (all, same version) 1. Oracle `passed: true, score: 1.0`, both subscores `=1` 2. Live red-team: no BLOCKING findings — **especially bleater-env reachable, all 3 drift sources live, install-id agent-readable, a no-op agent failing both** 3. Rollout avg `< <TARGET_MEAN>` (and not `< <FLOOR>` — over-hard)