recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ops: pause cfold until /upgrade-all finishes (serialize — they conflict on CI); journal+memory

Browse Source
This commit is contained in:
autonomic-bot
2026-06-11 22:56:27 +00:00
parent af2b2e8156
commit a1cceef3d4
3 changed files with 45 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cc-ci-plan/JOURNAL.md
+10
View File
@@ -508,3 +508,13 @@ session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private
- .phases-spec now …drone;cfold (10 phases). cfold is the new LAST phase, so the
.run-upgrade-on-complete hook fires /upgrade-all AFTER cfold — correct order (folder
change swept-green before the weekly upgrade runs). Watchdog bounced to load it.
## 2026-06-11 ~22:55 — drone DONE → upgrade fired; cfold PAUSED to serialize
- drone completed 22:31 → watchdog hit sequence-complete, fired the queued /upgrade-all
(cc-ci-upgrader, weekly run) per the operator's earlier request. Upgrade running now.
- I'd queued cfold ~22:52; the bounced watchdog auto-advanced into cfold, making it
CONCURRENT with the upgrade. They conflict (both real-CI; cfold edits the harness the
upgrade's !testme uses; upgrade version-bumps confound cfold's baseline). PAUSED cfold:
stopped its loops + the watchdog; phase-idx preserved at 9. Upgrade left running.
- RESUME cfold (restart watchdog → phase-idx 9) once /upgrade-all is confirmed DONE. See
memory [[cfold-paused-pending-upgrade]]. Will action on supervision wakes.