toolkit merge: import CLI into sentry-mcp, validate, then rename

[BYK]

Sub-task of the toolkit monorepo merge: #1248.

Sequence

Import the pre-shaped CLI into getsentry/sentry-mcp under its current repository name. Validate the complete monorepo and production deployment paths there. Rename the repository to getsentry/toolkit only after those gates pass.

This preserves history and lets GitHub, Vercel, Cloudflare, branch protections, and repository integrations continue operating under the known repository identity throughout integration.

Hard prerequisites

• CLI pre-shape merged: chore: pre-shape repo into pnpm-workspace monorepo layout #1254.
• Bridge CLI release completed and verified: toolkit merge: bridge CLI release + dual-source upgrade compatibility #1244 via feat(cli): add toolkit upgrade bridge #1569 and stable release 0.45.0.
• Create a dedicated integration branch from current getsentry/sentry-mcp main. Do not import directly into main.

History-preserving import

• From the bridge-release commit on getsentry/cli, produce two immutable git filter-repo refs:
  • import/cli — history containing only packages/cli/**
  • import/cli-docs — history containing only apps/cli-docs/**
• Record and verify source commit IDs before import.
• In the integration branch of getsentry/sentry-mcp, import:
  • git subtree add --prefix=packages/cli <cli-remote> import/cli
  • git subtree add --prefix=apps/cli-docs <cli-remote> import/cli-docs
• Verify git log --follow and blame across both trees; docs must never be nested under packages/cli.
• Add apps/* workspace membership and reconcile root files without changing the repository name or deployment destinations yet.

Pre-rename validation gate

• Full MCP and CLI build, typecheck, lint, unit, E2E, eval, binary, npm-package, and docs-preview suites pass.
• Publish workspace dry-runs pass using feat: accept workspace publish requests publish#9339 and fix: bootstrap root publish locations publish#9456.
• Craft workspace selection passes using feat(config): top-level workspaces schema + --workspace selector craft#848 and feat: propagate release workspaces craft#872; prefixed tags are isolated via feat: prefix-aware read paths for monorepo multi-product releases craft#847.
• Existing MCP Vercel and Cloudflare deployments still target getsentry/sentry-mcp.
• Canary the Cloudflare Worker deployment after pnpm-native orchestration replaces Turbo.
• Release-gated Cloudflare CLI-docs preview works from apps/cli-docs, with https://cli.sentry.dev/install unchanged.
• Independent correctness and security reviews pass on the exact integration head.

Only after every gate passes may getsentry/sentry-mcp#1156 rename the repository to getsentry/toolkit.

[BYK]

Master tracking issue: #1248

[BYK]

Bridge release gate passed with stable CLI 0.45.0.

Evidence:

• Bridge implementation: feat(cli): add toolkit upgrade bridge #1569, merged as d21717b1f090e44578c3e6c39b65fddb28d872c0.
• Release tag 0.45.0 points to 03f636f8d1fe6553acf22595eb029ddc8efc79eb, whose ancestry includes the bridge merge.
• Exact release-head CI passed, including unit, lint/typecheck, all platform builds, npm smoke tests, E2E, docs, stable delta generation, and aggregate CI.
• Publish request: publish: getsentry/cli@0.45.0 publish#9491; npm, GitHub, Vercel, registry, and Brew targets completed.
• A downloaded pre-bridge 0.44.1 curl binary upgraded to 0.45.0 through the legacy release, applying the stable delta and installing a binary with SHA-256 658363afd0c6d581b887de41160c40adc7e29c79c015569a57aaf01532ed47be.
• A downloaded bridge 0.45.0 binary resolved Toolkit exact tag 404, legacy exact tag 200, completed a forced pinned curl upgrade, and retained the same published digest.
• The live https://cli.sentry.dev/install script matched the canonical installer byte-for-byte and installed 0.45.0 with the same digest.
• npm and GitHub sentry-0.45.0.tgz artifacts were byte-identical with SHA-256 a65e2c0c005cb628567aca14d78ff7cd7f109a6b604551f491a81f2109969016.
• Homebrew formula and release-registry checksums matched GitHub release digests.

The bridge prerequisite is complete. History import may now begin from the immutable bridge-release commit.