autonomic-bot
7c042c2f2a
Audit every enrolled recipe's CI badge/card screenshot, diagnose defects (plausible null-every-run; ~4.8KB blank-frame SPAs: immich/lasuite-meet/ cryptpad/flaky n8n), fix via harness default-wait improvement first, per-recipe SCREENSHOT hooks second; M1 audit matrix + M2 visually-verified PNGs on fresh real-CI runs (>=2 !testme). Cosmetics-never-block and secret-safety guardrails binding. Also: temporary hourly-wake instruction to verify the new limit-wait system tonight; journal entry.
2 lines
931 B
Plaintext
2 lines
931 B
Plaintext
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.
|