agents.toml: re-add cf48 (opus cfold review) dropped during the launch-system migration
The unification transcribed phases from .phases-spec before cf48 was added, so the operator's just-requested opus 4.8 cfold review got dropped. Re-append it after ghost (system is past cf55/on pvfix, so can't insert before pvfix without shifting the live phase index). agents.py re-reads config each tick.
This commit is contained in:
@@ -618,3 +618,30 @@ session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private
|
||||
when cf48 starts since per-phase backend isn't overridable).
|
||||
- Also this session: relaunched after a session restart (NOT a host reboot, 13d uptime); loops+watchdog
|
||||
were stopped in a claude-sonnet limit window on cf55 → restarted via RESUME_PHASE=1 launch.py start.
|
||||
|
||||
## 2026-06-13 ~05:27 — launch system unified (agents.toml + agents.py); cutover done
|
||||
- Replaced the 5 bespoke launchers + ~15 dotfiles with ONE config (cc-ci-plan/agents.toml)
|
||||
+ ONE driver (cc-ci-plan/agents.py: up/down/status/watchdog/logs/phase). Design + behavior
|
||||
mapping in cc-ci-plan/plan-unified-launch.md.
|
||||
- launch.py and launch-orchestrator.sh are now COMPATIBILITY SHIMS → agents.py (originals at
|
||||
*.orig). So `launch.py start|status|stop|watchdog|logs`, the systemd boot chain
|
||||
(cc-ci-loops-start → launch.sh → launch.py start), and your startup routine all drive the
|
||||
new system transparently — no behavior change for you.
|
||||
- Config is the single source of truth; the watchdog re-reads it every tick (no more env-vs-file
|
||||
drift, which had caused the opencode-revert bug earlier today). Backend/model/prompt/watch
|
||||
policy per agent live in agents.toml. To change a model or backend: edit agents.toml.
|
||||
- State (phase index, resume ids, limit windows) now under .cc-ci-logs/state/. Phase machine
|
||||
unchanged; de-duped the doubled `mailu` entry (cf55 was idx 10 → now idx 9; current phase
|
||||
pvfix = idx 10). All agents respawned via the new system and confirmed working on pvfix.
|
||||
- The new watchdog tmux session (cc-ci-watchdog) runs `agents.py watchdog`. Same heal/limit/
|
||||
stall/handoff/phase-advance/wake behavior, lifted verbatim, now config-driven.
|
||||
|
||||
## 2026-06-13 ~05:30 — startup: unified agents.toml live; re-added dropped cf48
|
||||
- Session relaunch (NOT a host reboot, 13d uptime). Supervision UP: unified `agents.py watchdog`
|
||||
(--config agents.toml) + builder/adv on claude-sonnet + orchestrator on claude-opus-4-8. Phase
|
||||
pvfix [proxy /16 fix] in progress; cf55 confirmed ## DONE (advance was legit).
|
||||
- The launch-system unification (agents.toml + agents.py) was deployed in the gap. It was transcribed
|
||||
from .phases-spec BEFORE I added cf48 (05:15), so cf48 (the operator's opus cfold review) was
|
||||
DROPPED. Re-added it to agents.toml — appended AFTER ghost (the system is already past cf55/on
|
||||
pvfix, so inserting before pvfix would shift the live phase index). agents.py re-reads config every
|
||||
tick, so no watchdog bounce needed. cf48 runs as the last phase, opus 4.8, claude backend.
|
||||
|
||||
Reference in New Issue
Block a user