[dezren39]

For #4988 (task 8792) — the unified fleet schedule registry from the #2024 placement framework (B2).

What

• doc/fleet-schedule-registry.md — one record for every currently-known schedule on all three surfaces, populated from live sources verified 2026-11-03:
  • Muse cron: 131 jobs (120 enabled, 11 disabled) from the live scheduler list — id, title, cadence key, state, owner/scope, definition-file pointer.
  • OpenCode schedules: 16 OpenChamber scheduledTasks from the laptop project stores (queue lanes + the Move opencode executions to laptop-side scheduled tasks — retire the Muse boot handoff #3026 claimant/executor), plus 37 laptop systemd user timers with their live OnCalendar/OnUnitActiveUSec specs — the OS-timer surface implement: fleet OpenCode scheduled-task pattern — systemd timers + opencode run with per-job route #2232 builds on (still open, listed as-is).
  • Jules: 1 entry, retired — the fleet: pilot: first Jules schedule — weekly GitHub Actions version-bump sweep on developing-today/code (from #2020) #2265 pilot was never created; Drew closed it 2026-10-30 as moot (fleet moving off Jules). Section states "none others known".
  • Fields follow implement: unified fleet schedule registry — Muse cron + OpenCode timers + Jules schedules in one record (from #2024) #4988 (surface, name/id, repo/scope, cadence, route/pool, prompt pointer, budget, owner, kill criteria, created, last review); fields a surface does not record are marked not recorded, never guessed.
  • The registry names itself as an input to the design: task-placement framework v1 — decision rules and a shared-pool efficiency model #2024 placement audit.
• AGENTS.md — the same-pass rule written into the repo's runbook text: creating/changing/retiring a schedule on any surface updates the registry in the same pass; the rule is also stated in the registry's own header.

No schedule's cadence or rate was changed (per the packet's scope exclusion).

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 52 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: f916d823-b6f5-40fd-a5f6-dc6ada9ca026

Commits

Reviewing files that changed from the base of the PR and between 464467b and f02decb.

Files selected for processing: 2

• AGENTS.md
• doc/fleet-schedule-registry.md

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-03T21:43:45.625343Z	f02decb	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f02decb72d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve the time component of systemd calendar schedules

The calendar-based rows omit the time component, changing the documented cadence rather than merely abbreviating it. For example, laptop-autocommit is configured with *-*-* *:*:00 in nixos/home/laptop-autocommit.nix:51 (every minute), but these rows show *-*-*, which systemd-analyze calendar normalizes to *-*-* 00:00:00 (daily at midnight). The same loss affects the hourly worktree reaper and 15-minute quota gatherer elsewhere in this table. Since this registry is explicitly an input to the placement audit, these entries misrepresent execution frequency and workload. Preserve the complete calendar expressions when collecting the timer specs.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Record execution routes separately from work queues

The repo-health queue identifies the work scope, not the execution route or quota pool, so it cannot supply the route/pool field required by the Fields section. This information is available for at least the claimant: pm-stack/opencode-claimant/install.mjs:21-26,75-84 sets its execution route to opencode-route / workhorse, but neither its registry row nor this explanation records that route. Omitting execution routes prevents the intended placement/shared-pool audit from identifying which routes recurring model jobs consume. Add the actual execution route/pool to the records, retain queue names as scope, and explicitly mark unavailable routes as not recorded.

Useful? React with 👍 / 👎.