release

# Release & Versioning Kandev Stable releases use a **single SemVer** `X.Y.Z` shared across all distribution channels. npm also has an explicit prerelease-only `nightly` channel; it is not part of the unified Stable artifact set. ## Version targets - `apps/cli/package.json` version → `X.Y.Z` - npm main package: `kandev@X.Y.Z` - npm runtime packages: `@kdlbs/runtime-{platform}@X.Y.Z` (5 platforms; declared as `optionalDependencies` in main package) - Git tag: `vX.Y.Z` (three-part; legacy `vM.m` tags normalize to `M.m.0`) - Homebrew formula: `kdlbs/homebrew-kandev` `Formula/kandev.rb` `version "X.Y.Z"` - Scoop bucket: `kdlbs/scoop-kandev` `bucket/kandev.json` version, URL, and hash - GitHub release: `vX.Y.Z` with platform tarballs `kandev-{platform}.tar.gz` + `.sha256` **npm, Homebrew, and Scoop are sibling channels**, not chained. All three consume the same GitHub release artifacts; none depends on another package-manager channel. For npm Nightly, Stable `X.Y.Z` plus a full `main` SHA produces `X.Y.(Z+1)-nightly.sha<first-12-lowercase-hex>`. `kandev` and all five runtime packages publish at that exact version under npm's `nightly` dist-tag. Nightly never moves `latest` and creates no Git tag, GitHub Release, Homebrew formula, Scoop bucket update, Desktop feed/build, or container tag. ## Release flow Stable runs entirely in CI via `.github/workflows/release.yml`, triggered by a maintainer from the GitHub Actions UI: 1. Maintainer clicks "Run workflow" → keeps `channel=s...