toolkit merge: independent CLI releases and continuous MCP deployment

[BYK]

Sub-task of the toolkit monorepo merge (master issue linked below). Plan: https://gist.github.com/BYK/8c0ce6cec64608f41fe5654b7827228e

Product-specific releases: cli@x.y.z for the CLI; the MCP Worker deploys continuously from tested main, independently of the stdio npm package.

• release.yml selects CLI or MCP workspace and computes the selected package version.
• .craft.yml has separate CLI and MCP workspaces; CLI targets GitHub cli@, npm, registry, Homebrew, and release-gated Vercel, with published stable 0.46.0 and 0.47.0.
• CLI nightlies use a commit-timestamped -dev.N version and publish to Toolkit GHCR.
• Verified the MCP Worker deploys continuously from tested main through the protected exact-version workflow (feat(docs): add Vercel analytics and speed insights #1399, docs: weekly documentation audit — fix Zod→Valibot drift, stale versions, dataset list #1400). A prefixed mcp@ GitHub release is not needed for Worker deployment; keep npm releases available for stdio consumers.
• Retain release-gated CLI docs and previews on Vercel at https://cli.sentry.dev/install (the earlier Cloudflare-docs proposal was superseded).

See §5 + §6.

[BYK]

Master tracking issue: #1248

[BYK]

CLI releases are prefixed and independent; MCP production deploys continuously from a successful main Test through the reviewed exact-version workflow (#1399/#1400). A separate mcp@ GitHub tag is not needed for Worker delivery. The MCP stdio npm target remains in Craft for package releases when needed.