release-new-version

# Release a New Version Use this for Nightly builds, stable desktop releases, and requested mobile store distribution. A stable desktop release must come from `main`, after the changelog and required CLI, MCP, API, agent-package, and documentation updates are accurate, validated, and merged. Desktop and watchOS share the marketing version in `release-version.json`. iOS and Android use `apps/mobile/release-version.json`. Platform build numbers and publication schedules remain independent. ## Core Rule Do not trigger a stable release from an unmerged branch. Complete the release surface review and changelog below, merge the required changes to `main`, then freeze the candidate and release that merged commit through its Nightly tag. ## Nightly and Stable Operations - Existing users and the main download remain on stable. Nightly is an explicit separate-app install, with its own updater feed and CLI command. It opens the same local database as stable; settings, store, and sign-in stay per app. - The team uses Nightly for daily meetings. Volunteers can join through the announcement in the next stable changelog and product-update newsletter. - `.github/workflows/desktop_nightly.yaml` runs daily at 15:00 UTC (midnight KST) and can be dispatched manually from `main`. It runs desktop JS/i18n and native CI, including source CloudSync rebuilds, before building and publishing all desktop platforms through `desktop_cd.yaml` with `channel=nightly`. - Nightly versions are `...