release-notes

# release-notes — Generate Release Notes Produce a release-notes document following the "What's New / Improvements / Fixes / Breaking / Acknowledgements" structure used by Hermes, React, VS Code, etc. ## Procedure 1. **Resolve the range:** - If `range:` looks like a git range (`X..Y`), use `git log --pretty` to list commits. - Otherwise treat it as a GitHub milestone name and pull the closed PRs via `github` MCP. 2. **For each commit/PR, extract:** - Type from Conventional Commits prefix (`feat:`, `fix:`, `docs:`, `security:`, `perf:`, `refactor:`, `chore:`) - Scope (inside the parentheses) - Summary (the first line after the prefix) - Body / PR description for context - Author + association (CONTRIBUTOR / COLLABORATOR / MEMBER) 3. **Group:** - **🚀 What's New** — all `feat:` with scope outside `ci|deps|docs` - **⚡ Improvements** — `perf:` and `refactor:` - **🐛 Fixes** — `fix:` - **🔒 Security** — `security:` + any PR labeled `security` regardless of prefix - **💥 Breaking** — any PR labeled `breaking` or any commit with `!:` marker - **📚 Docs** — `docs:` - **🙏 Acknowledgements** — list of all non-MEMBER authors 4. **Write in plain English.** For each entry, rewrite the conventional-commit summary into a reader-friendly one-liner. Example: - Input: `feat(mcp): add http transport with reconnect backoff` - Output: `HTTP MCP servers now reconnect automatically with exponential backoff.` 5. **Include PR links** where avail...