releaselisted
Install: claude install-skill Vinedine/para-os
# Release a revision
A revision marks a template change that an existing vault has to react to. The scheme is at
the top of `CHANGELOG.md`; read it first. `/para-upgrade` executes each entry, so an entry is
an instruction to an agent, not a summary for people. Work merges into `main`; a revision has
shipped once it is reachable from `origin/stable`, which users install and upgrade from.
## 1. Decide whether this needs a revision
List what changed since the last revision shipped:
```bash
git fetch origin
git diff --stat origin/stable...HEAD
git log --oneline origin/stable..HEAD
```
A change needs a revision when a vault must do something: re-sync a skill or `para-shared/`,
copy a rule file, edit its `CLAUDE.md`, update an installed integration. Wording that changes no
rule does not. When nothing qualifies, say so and stop.
## 2. Pick the label
Read the newest `## YYYY.MM.NN` heading in `CHANGELOG.md`, and check whether `origin/stable`
already has it (`git show origin/stable:CHANGELOG.md`).
- **Not shipped yet**: this change folds into that open revision. Keep the label and extend
its entry.
- **Already shipped**: cut the next one. Same month, next sequence (`2026.09.05` is followed
by `2026.09.06`); a new month restarts at `.01`. Take the month from the system clock.
An argument naming a revision overrides this; confirm it is newer than every heading.
## 3. Write the entry
Match the entries below it exactly: a bold one-line summary with its own `Reaction:`, then