From 23b5fc4753cd428caf78a974992b1c49533bb445 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Thu, 11 Jun 2026 20:50:25 +0000 Subject: [PATCH] journal: weekly upgrade skipped tonight, queued after phase queue via watchdog hook --- cc-ci-plan/JOURNAL.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/cc-ci-plan/JOURNAL.md b/cc-ci-plan/JOURNAL.md index f22014d..e587c4d 100644 --- a/cc-ci-plan/JOURNAL.md +++ b/cc-ci-plan/JOURNAL.md @@ -472,3 +472,17 @@ session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private - mailu RE-QUEUED after kuma: spec now rcust;shot;lvl5;bsky;dstamp;mailu(skipped);kuma; mailu(redo);drone — 9 phases, idx6=kuma. Watchdog bounced to load fix+spec. Builder correctly sonnet at kuma (per-phase override still working). + +## 2026-06-11 ~20:50 — weekly upgrade: skip tonight, queue after phases (operator) +- Operator: cancel tonight's weekly /upgrade-all cron, run it once after the current + phase queue (…mailu→drone) finishes instead. +- cc-ci-upgrade-all.timer STOPPED (can't `disable` — /etc/systemd read-only). Stamp + forwarded to 06-12 03:00 so a reboot/rebuild tonight schedules NEXT run 06-19, NOT a + catch-up of tonight's 02:00 slot. GOTCHA: `systemctl start` on this timer fires the + service IMMEDIATELY (Persistent=true) — it did, launched an unwanted upgrader run at + 20:47 which I killed. DO NOT `start` the timer to re-arm; let a host reboot/nixos-rebuild + reactivate it (the drone P0 rebuild will), forward-stamp prevents catch-up. +- Post-phase run wired: watchdog hook (launch.py 3fa3178) launches launch-upgrader.py + start when the LAST phase hits ## DONE, gated by flag /srv/cc-ci/.cc-ci-logs/.run-upgrade- + on-complete (set now, consumed once). Upgrader inherits sonnet. So when `drone` completes, + /upgrade-all auto-starts.