suijin-release-macoslisted
Install: claude install-skill Suijin-App/Suijin
# Suijin release (macOS)
Takes Suijin from a green `main` to a published GitHub release that installed copies update to, and proves each stage
before the next one starts. The reader of the result is the app's owner; the readers of the release notes are
Suijin's users. `docs/release-process.md` is the authority on how the pipeline works; this skill is the order of
work and the checks around it.
A release is hard to take back: every installed copy sees it within a day and installs it. So nothing is published
until every check before it passed, and the publish step itself waits for the owner's go-ahead.
## When to use
- "Release Suijin", "ship 0.1.1", "cut a new version", "publish the update", "write the release notes for the next version".
- Not for: day-to-day builds and tests (`./scripts/ci-local.sh`), changes to the release pipeline itself, or the
website.
## Boundaries
- **Secrets.** The Developer ID certificate, the notary profile and the Sparkle private key live in the login
Keychain. Never print, copy or export them, and never create them: if one is missing, stop and tell the owner the
command from `docs/release-process.md` section 2.
- **Publishing.** `gh release create`, pushing a tag and deleting a release are outward-facing. Do them only after the
owner confirmed in this conversation, with the version and the notes in front of them. A go-ahead for one release
does not cover the next.
- **The Discord bot token** lives in TSSC (project Suijin, environme