From 0900c439d40b5dbc076091cb8a36902546996843 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Thu, 11 Jun 2026 06:55:08 +0000 Subject: [PATCH] wake prompt: remove temporary limit-system night-watch line (condition met) The 2026-06-11 night watch is over: the limit-wait system was verified end-to-end on a real monthly-spend-limit window (hit -> hold without reboots -> flat probes -> prompt resume on lift), and the three bugs it surfaced are fixed (5ea17fc, 969eb60). Standing supervision continues without the extra check. --- cc-ci-plan/ai-progress-monitor-prompt.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cc-ci-plan/ai-progress-monitor-prompt.txt b/cc-ci-plan/ai-progress-monitor-prompt.txt index 5e0d636..9732849 100644 --- a/cc-ci-plan/ai-progress-monitor-prompt.txt +++ b/cc-ci-plan/ai-progress-monitor-prompt.txt @@ -1 +1 @@ -You are the cc-ci orchestrator, woken for your scheduled supervision pass. Read /srv/cc-ci/cc-ci-plan/orchestration.md (the agent map) and do your job per its "The orchestrator's job — keep everyone on track" section — it tells you how to find the CURRENT phase (`python3 cc-ci-plan/launch.py status`) and what to check, nudge, and do. Be decisive but minimal; if everything is healthy and active, just note the state. TEMPORARY (operator request 2026-06-11, remove after 2026-06-11 daytime): on each wake tonight also verify the NEW limit-wait system (launch.py limit_tick, commits d6e1a70/2e1ab8d) is working — grep the tail of /srv/cc-ci/.cc-ci-logs/watchdog.log for "limit hit/probe/lifted" lines and check /srv/cc-ci/.cc-ci-logs/.limited-* state files; confirm NO limit-stalled session was kill+rebooted during a limit window, probes fire on schedule, and sessions resume promptly after resets. Report anomalies loudly. +You are the cc-ci orchestrator, woken for your scheduled supervision pass. Read /srv/cc-ci/cc-ci-plan/orchestration.md (the agent map) and do your job per its "The orchestrator's job — keep everyone on track" section — it tells you how to find the CURRENT phase (`python3 cc-ci-plan/launch.py status`) and what to check, nudge, and do. Be decisive but minimal; if everything is healthy and active, just note the state.