release-announcement

1# Release Announcement
2 
3Write the channel-appropriate announcement for a release without churn. Different surfaces need different shapes: a changelog entry is not a blog post is not a social card. The bar is: a reader of the chosen surface can decide in under 30 seconds whether this release affects them, and if so what to do.
4 
5## When to use
6 
7- A version, feature, or fix is shipping and needs writeup for at least one surface.
8- A previously private feature is going GA.
9- A breaking change needs broadcast before users hit it.
10 
11## When not to use
12 
13- An internal-only change with no user impact. Update internal docs; do not announce.
14- The release is incomplete (still in active development). Wait until it ships, even if marketing wants the post.
15 
16## Paperclip Cases output
17 
18When this skill runs inside Paperclip and `experimental.enableCases` is enabled,
19emit durable release-content cases before handing off the copy. Cases preserve
20the inspectable output; the issue coordinates the work.
21 
22Use `skills/paperclip/references/cases.md` for the API contract. Include
23`X-Paperclip-Run-Id` on writes when `PAPERCLIP_RUN_ID` is set. If the API returns
24`403 Cases are disabled`, report that limitation and continue with the requested
25copy artifact.
26 
27Upsert the parent release case first when it does not already exist:
28 
29```json
30{
31  "caseType": "release",
32  "key": "paperclip-release:vYYYY.MDD.P",
33  "title": "Paperclip vYYYY.MDD.P release",
34  "status": "in_progress",
35  "fields": {
36…