/drive — Cron-Driven Manifest Runner

Goal

Take a manifest (or an existing PR in babysit mode) to a terminal state through repeated stateless ticks. This wrapper handles argument parsing, mode validation, pre-flight, and bootstrap, then hands control to the scheduler — /loop when available, the inline-fallback scheduler otherwise — to schedule /drive-tick on the configured interval. In loop mode, /drive exits immediately after kickoff and ongoing work happens in scheduled tick invocations. In inline-fallback mode, the scheduler runs inside the Claude session and /drive holds until a terminal state or budget exhaust — see references/fallback-inline.md.

Coexists with /do and /auto. /drive is the canonical PR-lifecycle skill in manifest-dev (graduated from manifest-dev-experimental).

Multi-repo PR sets: when the manifest declares Repos: in Intent (multi-repo changeset), each repo's PR is tended by its own /drive invocation pointing at the same canonical /tmp manifest. Run-id qualification (gh-{owner}-{repo}-{pr-number} in github mode) already isolates locks (/tmp/drive-lock-{run-id}) and execution logs (/tmp/drive-log-{run-id}.md) per-PR — no cross-repo collisions. Concurrent amendments to the shared manifest by different ticks are last-writer-wins (no locking; see manifest-dev:define/references/MULTI_REPO.md §f). Single-repo manifests are unaffected.

Input

$ARGUMENTS = [<manifest-path>] [--platform none|github] [--sink local] [--base <branch>] [--interval <duration>] [--max-ticks <N>]