nightly

# /nightly -- Nightly Self-Maintenance > [!danger] Same gate as every leg it calls > `/nightly` does not lower the bar any leg already holds itself to. `/dream` still only proposes -- candidates land in `DREAM_LOG.md` as `status: proposed`, the operator still promotes them through `/meta-improve`. `/digest` still only stages -- candidates stay `status: staged` until the operator answers promote/skip/supersede. `/sweep-now` still only proposes tracker/heat/link fixes for review. `/nightly` itself writes less than any leg it calls: one line per leg, to its own log, and nothing else. Sequences the four already-shipped verbs named in the README's Roadmap -- `/dream`, `/reconcile`, `/sweep-now`, `/digest` -- into one named routine, with a `/system-check` gate and a ledger-review pass over the measurement layer, so a vault gets a maintenance pass on a cadence instead of only when the operator remembers to run each piece by hand. ## Invocation ``` /nightly /nightly --skip dream # run every leg except one /nightly --only reconcile,system-check # run a subset ``` --- ## What it sequences Six legs, run in order. Each leg is gated by the cadence its own skill already documents -- `/nightly` does not invent a new cadence, it just checks the one that already exists before deciding whether a leg has anything to do. ### Leg A -- `/dream` consolidation Run the full protocol in `skills/dream/SKILL.md` (Steps 1-5): load daily notes + runtime state, run the six ana...