recurring v1.5.0A

Immutable. This exact content never changes and is served at /api/v1/blob/afc6ad2e1cf27630.

---
name: recurring
scope: core
group: missions
emoji: 🔁
description: Manage recurring missions (hourly, daily, weekly, custom interval)
version: 1.5.0
audience: bridge
commands:
  - name: daily
    description: Add a daily recurring mission
    usage: /daily [HH:MM] <text> [project:<name>]
  - name: hourly
    description: Add an hourly recurring mission
    usage: /hourly <text> [project:<name>]
  - name: weekly
    description: Add a weekly recurring mission
    usage: /weekly [HH:MM] <text> [project:<name>]
  - name: every
    description: Add a custom-interval recurring mission
    usage: /every <interval> <text> [project:<name>]
  - name: recurring
    description: List recurring missions, or manage with resume/run/pause/cancel/days sub-commands
    usage: /recurring, /recurring resume <n>, /recurring run [n], /recurring pause <n>, /recurring cancel <n>, /recurring days <n> <days>
handler: handler.py
---

Use `project:all` to make a recurring mission **org-wide**: it runs once at the
workspace root and its instructions iterate over every repo in the workspace
(see `docs/architecture/mission-lifecycle.md`). Without a `project:` tag, a
mission defaults to the first configured project.