release

Topics in the source

• Release Coordination Skill
• Trigger
• Preconditions
• Inputs
• Step 0 — Release Model
• Step 1 — Choose the Candidate
• Step 2 — Draft the Stable Changelog
• Step 3 — Verify the Candidate SHA

Run the full Paperclip maintainer release workflow, not just an npm publish. This skill coordinates: stable changelog drafting via release-changelog canary verification and publish status from master Docker smoke testing via scripts/docker-onboard-smoke.sh manual stable promotion from a chosen source ref GitHub Release creation website / announcement follow-up tasks release-content Cases dogfood: a top-level release case with child blogpost and tweetstorm cases, all linked to the release issue/run Use this skill when leadership asks for: "do a release" "ship the release" "promote this canary to stable" "cut the stable release" Before proceeding, verify all of the following: 1. .agents/skills/release-changelog/SKILL.md exists and is usable. 2. The repo working tree is clean, including untracked files. 3. There is at least one canary or candidate commit since the last stable tag. 4. The candidate SHA has passed the verification gate or is about to. 5. If manifests changed, the CI-owned pnpm-lock.yaml refresh is already merged on master. 6. npm publish rights are available through GitHub trusted publishing, or through local npm auth for emergency/manual use. 7. If running through Pape

This is an excerpt. Refer to the complete source and its current requirements.