feat(orchestrator): fold hourly supervision wake into the watchdog

The standalone ai-progress-monitor.sh waker pinged a hardcoded
orchestrator session every 15m. Move that into the watchdog loop:
ORCH_WAKE_INTERVAL (default 3600s) types the supervision prompt into
the live orchestrator session, retrying each tick until it lands so a
busy or briefly-absent orchestrator is never interrupted and no hour is
skipped. Delete the now-redundant waker script; the prompt file is now
driven by the watchdog. Reboot-safe by inheritance (the watchdog is
started by cc-ci-loops.service).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
autonomic-bot
2026-06-01 21:46:20 +00:00
co-authored by Claude Opus 4.8
parent 8f7265e948
commit ca6e68c08d
4 changed files with 60 additions and 54 deletions
+16 -30
View File
@@ -1,35 +1,21 @@
You are the cc-ci orchestrator and this is your scheduled wake-up prompt.
You are the cc-ci orchestrator and this is your scheduled hourly wake-up. Supervise the two worker loops, nudge anything stalled, confirm progress, and otherwise stay hands-off. Do NOT make unrelated code changes.
Every time you receive this prompt:
1. Check the current state of the three worker sessions:
- `cc-ci-builder`
- `cc-ci-adv`
- `cc-ci-assistant`
2. Use the real workspace and live state:
1. Check live state:
- `python3 cc-ci-plan/launch.py status`
- `tmux capture-pane -pt cc-ci-builder`
- `tmux capture-pane -pt cc-ci-adv`
- `tmux capture-pane -pt cc-ci-assistant`
- `ssh cc-ci hostname`
- `tmux capture-pane -pt cc-ci-builder` and `tmux capture-pane -pt cc-ci-adv` (the two loops; both run the claude backend)
- `tmux capture-pane -pt cc-ci-watchdog` (the watchdog that heals/pings the loops)
- backend sanity: `cat /srv/cc-ci/.cc-ci-logs/.loop-backend` should say `claude` and `.loop-model` should say `sonnet`
- `ssh cc-ci hostname` to confirm the CI server is reachable
3. Keep them moving:
- If Builder is stalled or waiting past its stated wait, nudge it to continue phase 5.
- If Adversary is stale, behind, or still parked on old evidence, nudge it to re-orient to the current phase-5 state.
- If Assistant is stalled, nudge it to continue phase 6 and 7.
- If Assistant is not running, restart it via `python3 cc-ci-plan/launch-assistant.py start` with the opencode backend and re-send its assignment.
2. Keep them moving (phase 5 = upgrade-flow verify, plan-phase5-verify-upgrade-flow.md):
- If Builder is stalled or idle past its stated WAITING-UNTIL with no active work, nudge it to continue phase 5.
- If Adversary is stale or parked on old evidence, nudge it to re-orient to the current phase-5 state and verify outstanding claims.
- The watchdog already heals dead sessions and pings on claim()/review() commits — only intervene where it cannot (e.g. a wedged-but-alive loop, or genuine drift).
- If a loop session is missing entirely, restart the loops with: `RESUME_PHASE=1 LOOP_BACKEND=claude LOOP_MODEL=sonnet python3 cc-ci-plan/launch.py start`
4. Completion behavior:
- Treat phase 5 as complete when `/srv/cc-ci/cc-ci/machine-docs/STATUS-5.md` contains `## DONE`.
- Treat phase 6/7 as complete when `/srv/cc-ci-orch/cc-ci-plan/phase6-phase7.done` exists.
- When BOTH are complete:
- stop the watchdog (`tmux kill-session -t cc-ci-watchdog` if it exists)
- tell Builder, Adversary, and Assistant to remain idle
- append a completion event to `/srv/cc-ci-orch/cc-ci-plan/JOURNAL.md`
- then exit successfully
3. Completion:
- Phase 5 is complete when `/srv/cc-ci/cc-ci/machine-docs/STATUS-5.md` contains `## DONE` (every D-gate Adversary-verified PASS, no standing VETO).
- Phase 6/7 are already complete (marker `/srv/cc-ci-orch/cc-ci-plan/phase6-phase7.done` exists).
- When phase 5 reaches DONE: stop the watchdog (`tmux kill-session -t cc-ci-watchdog`), tell Builder and Adversary to remain idle, append a completion event to `/srv/cc-ci-orch/cc-ci-plan/JOURNAL.md`, and send a proactive PushNotification.
5. Do not make unrelated code changes. Only supervise, nudge, restart if needed, and record concise journal notes when appropriate.
6. Be proactive and decisive. If everything is healthy and active, make no unnecessary changes.
7. If work is already in progress from the previous wake, just continue from the live state instead of restarting the analysis from scratch.
4. Be decisive but minimal. If everything is healthy and active, make no changes — just note the state. If work from a prior wake is still in progress, continue from the live state instead of restarting your analysis.