spawn: per-model launcher, fallback chain, failure notice #2

Merged
caoer115 merged 2 commits from timeline-model-fallback into main 2026-10-26 10:47:49 +00:00
Owner

Collector-watch-hourly missed 06:05–09:05Z on 2026-10-26: one Kimi launcher for every record, Kimi 5-hour wall, no fallback, nobody told. Adds TIMELINE_LAUNCHERS (model→launcher), record fallback: (walked by the 3-attempt loop; skip slots stay due while retrying), exit-10 429-wall kill, and record notify: (ccc-notify --kind blocked once on fallback/unverified/failure). Tests: go test ./... green and nix build .#timeline (check phase) green on workstation-nyc-2 at e6c88af. No CI on this repo.

Collector-watch-hourly missed 06:05–09:05Z on 2026-10-26: one Kimi launcher for every record, Kimi 5-hour wall, no fallback, nobody told. Adds TIMELINE_LAUNCHERS (model→launcher), record fallback: (walked by the 3-attempt loop; skip slots stay due while retrying), exit-10 429-wall kill, and record notify: (ccc-notify --kind blocked once on fallback/unverified/failure). Tests: go test ./... green and nix build .#timeline (check phase) green on workstation-nyc-2 at e6c88af. No CI on this repo.
- TIMELINE_LAUNCHERS (services.agent-timeline.launchers) maps model -> launcher;
  a model it does not name fails before ccc-agent runs and is refused at
  timeline add|edit.
- fallback: "<model> [effort], …" (at most 2): attempt k of a slot runs entry
  k-1 inside the existing 3-attempt loop. A catch_up: skip slot stays due past
  its grace while an attempt failed and attempts remain.
- exit 10 whose screen shows a 429 retry loop kills the tick's own seat and
  counts as failed, so the chain moves on.
- notify: <position> runs TIMELINE_NOTIFY_CMD <position> '<line>' --kind blocked
  once when a slot fires on a fallback, ends unverified, or runs out of
  attempts; services.agent-timeline.notify.sshHost runs ccc-notify on another host.

Why: collector-watch-hourly missed 06:05-09:05Z on 2026-10-26 — every record
spawned through one Kimi launcher, the Kimi 5-hour window walled, and the
timeline neither fell back nor told anyone.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
caoer115/agent-timeline!2
No description provided.