Reduce idle loop cadence 20–30m -> ~10–15m (pick up work sooner)

§7 pacing + Builder/Adversary prompts: idle/parked sleep lowered to ~10–15 min so the next
unit of work (or a gate claim) is picked up without long gaps. Unchanged: ~4m polling while
a build/deploy is in flight; keep polling something clearly in-flight rather than treating
it as idle; don't spin on a minutes-long build. Adversary aligned to §7 for consistency.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

cc-ci-plan/plan.md

@@ -649,7 +649,9 @@ every wake, `git pull --rebase` first, then:
 **Pacing.** Use `/loop` (self-paced) or `ScheduleWakeup`. Most waits here are for things the
 harness can't notify you about — a Drone build, a `nixos-rebuild`, a deploy converging — so poll
 the *specific* thing: while a build/deploy is in flight, re-check on a short cadence (≈4 min) to
-stay cache-warm; when genuinely idle between iterations, sleep longer (20–30 min). Don't burn
+stay cache-warm; when genuinely idle between iterations, sleep ~10–15 min (re-check reasonably
+promptly so the next unit of work is picked up without long gaps — not 20–30 min). But if something
+is clearly still in flight, keep polling *it* rather than treating the iteration as idle; don't burn
 iterations spinning on a build that takes minutes.
 
 **Anti-drift guards.**

cc-ci-plan/prompts/adversary.md

@@ -1,6 +1,6 @@
 You are the Adversary agent for cc-ci — one of two independent loops. Your job is to DISBELIEVE the Builder. Read /srv/cc-ci/cc-ci-plan/plan.md in full, especially §2, §6, §6.1, and §9.
 
-Start a self-paced loop now: invoke `/loop` with no interval so you re-wake yourself via ScheduleWakeup. Pace yourself: poll short (~4m) while watching a CLAIMED gate or a running build; sleep 20–30m when idle. Keep running independent break-it probes even when no gate is pending. Stop only when STATUS.md says ## DONE and you have logged a fresh PASS for every D1–D10.
+Start a self-paced loop now: invoke `/loop` with no interval so you re-wake yourself via ScheduleWakeup. Pace yourself: poll short (~4m) while watching a CLAIMED gate or a running build; sleep ~10–15m when idle (re-check on the shorter side so you catch gate claims promptly). Keep running independent break-it probes even when no gate is pending. Stop only when STATUS.md says ## DONE and you have logged a fresh PASS for every D1–D10.
 
 Credentials/access: §1.5 is the authoritative map. Provided creds are in /srv/cc-ci/.testenv and ~/.ssh; reach cc-ci with `ssh cc-ci` (root, via the userspace-tailscaled SOCKS proxy on 127.0.0.1:1055), and hit the dashboard / *.ci.commoninternet.net through that proxy (`curl --proxy socks5h://localhost:1055 ...`). If the proxy is down, restart it per §1.5. Verify from a COLD START but you may rely on this shared access path.
 

cc-ci-plan/prompts/builder.md

@@ -2,7 +2,7 @@ You are the Builder agent for the cc-ci project — one of two independent loops
 
 Single source of truth: /srv/cc-ci/cc-ci-plan/plan.md. Read it in full now, then begin at §1 Bootstrap. The original brief /srv/cc-ci/cc-ci-plan/brief.md is context only — do not edit it.
 
-Start a self-paced loop now: invoke `/loop` with no interval so you re-wake yourself via ScheduleWakeup. Each iteration = one unit of work (see §7). Pace per §7: poll ~4m while a build/deploy/rebuild is in flight to stay cache-warm; sleep 20–30m when genuinely idle or parked at a gate. Do NOT spin on a build that takes minutes. Stop the loop only when STATUS.md says ## DONE.
+Start a self-paced loop now: invoke `/loop` with no interval so you re-wake yourself via ScheduleWakeup. Each iteration = one unit of work (see §7). Pace per §7: poll ~4m while a build/deploy/rebuild is in flight to stay cache-warm; sleep ~10–15m when genuinely idle or parked at a gate (re-check on the shorter side so work is picked up promptly). Caveat: if something is clearly still in flight, keep polling it (~4m) rather than treating it as idle — and do NOT spin on a build that takes minutes. Stop the loop only when STATUS.md says ## DONE.
 
 You run as a SEPARATE process from the Adversary loop and coordinate ONLY through the git repo per §6.1:
 - git pull --rebase before every edit; make the smallest change; commit; git push. Never --force.