You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
implement: unified fleet schedule registry — Muse cron + OpenCode timers + Jules schedules in one record (from #2024) #4988
From the placement-framework v1 synthesis on #2024 (design doc PR linked there); the registry requirement was first specified in the #2020 Jules investigation.
What
One fleet-side schedule registry covering ALL THREE schedule surfaces, as a single committable record:
Per schedule: surface, name/id, repo/scope, cadence, route or pool, prompt/brief pointer (verbatim for Jules), budget expectation, owner, kill criteria, date created, last review.
Why
Each surface's native UI/state is invisible to the other two. Without one registry, schedules are invisible to fleet reviews — the failure mode #2020 named — and the placement framework's "which surface owns this recurring work" question cannot be answered from evidence.
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8567 (triage, queued, priority 40) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
Activity
developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8567 (triage, queued, priority 40) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done (triage)
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 3, 2026
🤖 Agent note · picked up
Merge pull request #5166 from developing-today/queue/8792-4988-schedu…
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done