Release Docs

Review every release. Inherit scope and session authorization from Release a New Version. Own documentation and changelog publication through completion, not just the source file or PR. For mobile-only distribution, prepare Mobile notes and review affected mobile and shared documentation. Use the Mobile publication steps below; desktop release/tag checks are not applicable.

Before candidate freeze

1. Read docs/AGENTS.md and New Changelog. Compare all user-facing changes since the previous published release in that stream (previous stable for stable notes) with packages/changelog/content/<stream>/<version>.md, docs/, docs/docs.json, and apps/web/public/llms.txt. Cover guides, installation/upgrade instructions, CLI/MCP/API examples, screenshots, troubleshooting, and platform availability. Preserve external-contributor credits and describe shipped behavior only.
2. Prepare the changelog with its date and plain-text summary. Run changed-file formatting, pnpm -F @anlg/changelog typecheck, and affected web checks from web_ci.yaml/root AGENTS.md. For docs, use the Mintlify version pinned in cli_ci.yaml to run validate and broken-links --check-anchors --check-redirects from docs/; preview affected pages and navigation. Coordinate public skill changes with Agent packages.
3. Merge required content before freezing the candidate. Keep unreleased notes hidden: desktop entries require published, non-draft, non-prerelease GitHub desktop_v<version> releases; mobile entries require verified adjacent publication records as specified in packages/changelog/content/mobile/AGENTS.md. Verify the production index omits the candidate and its direct URL returns 404 before publication. A local production build can test this; vite dev intentionally previews drafts.