Skip to content

Secure, Fast, and Extensible Sandbox runtime for AI agents.

chore(release): keep release-notes skill in sync with 1.2.0 authoring decisions

高然dc8ed9fac229
diff --git a/.agents/skills/opensandbox-release-notes/SKILL.md b/.agents/skills/opensandbox-release-notes/SKILL.md
index deabcf827..3924614d8 100644
--- a/.agents/skills/opensandbox-release-notes/SKILL.md
+++ b/.agents/skills/opensandbox-release-notes/SKILL.md
@@ -138,11 +138,13 @@ Writing rules:
- **No hard line wrapping** — one paragraph or one bullet per line, no matter how long; markdown renderers join them anyway.
- **Within a component: Features first, then Bug Fixes.** Split the Networking section into `### egress` and `### ingress` subsections (shared items go at the end of the more relevant one, labeled). Split the SDKs section into one `### <Language>` subsection per language (Python, JavaScript, Kotlin, C#, Go) with fsb/feature entries distributed to their language; cross-language items stay as lead bullets directly under `## SDKs` — never use a "Cross-SDK" subheading. Cross-SDK changes always go first.
- **Do not copy PR titles** — synthesize; each entry is tight and dense: problem → change → key scope, in 1–3 sentences, no filler.
-- **Group only PRs that are the same story.** Cite several `[#NNNN](…pull/NNNN)` links in one entry only when they implement one user story (e.g. the same feature across languages, or one coordinated fix campaign). Never bundle unrelated fixes into a "misc correctness" entry just because they share a component — give each its own bullet instead.
+- **Apply a density gradient: major fixes and features expand, minor bugfixes get one sentence.** Headline features, breaking changes, security fixes, and fixes with a user-visible failure story (data loss, hangs, wrong results, outages) each get their own bullet expanded to 2–4 sentences (problem → change → impact). Individually trivial bugfixes get exactly one sentence each ("what broke → now fixed"), and may be folded into a single trailing "smaller fixes/items" bullet per component — semicolon-separated, each with its own `[#NNNN]` citation — so the section leads with what matters. Trivial means: no data-loss/security angle, no behavior change an operator must react to, no migration step.
+- **Group only PRs that are the same story.** Cite several `[#NNNN](…pull/NNNN)` links in one entry only when they implement one user story (e.g. the same feature across languages, or one coordinated fix campaign) — or when they are individually trivial one-liners folded together per the density-gradient rule above. Never bundle unrelated *substantive* fixes into a "misc correctness" entry just because they share a component — give each its own bullet instead.
- **Reference every PR** as a full markdown link `[#NNNN](https://github.com/<owner>/<repo>/pull/NNNN)` at the end of its entry (space-separated for groups, each inside one shared parenthesis).
- **User-facing** — what operators/consumers need, not internals.
-- The opening paragraph states the headline and who should upgrade; for a first umbrella / GA (e.g. `1.1.0`), also state the unified-versioning context and the `1.0.0` gap rationale per the umbrella governance OSEP.
+- The opening paragraph carries only what Highlights cannot: line context (stable cut / rc, what baseline the sections cover), who should upgrade, and package/image shipping timing. It must NOT enumerate the headline features — that is `## Highlights`' job; restating them verbatim is redundancy. The GitHub Release supplies the title (no H1 here), so this paragraph is the first prose on the page; for a first umbrella / GA (e.g. `1.1.0`), also state the unified-versioning context and the `1.0.0` gap rationale per the umbrella governance OSEP.
- rc notes omit: SDK/CLI package claims, `## Installation` SDK lines, `## 👥 Contributors` (optional), and say packages ship at the stable bump.
+- **Upgrade & Compatibility never gets the density gradient** — every behavior change, breaking change, deprecation, and migration step keeps its own complete bullet there, even when its component-section entry was compressed to one sentence.
Fixed boilerplate (fill from the BOM/compat facts, keep wording):