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

Start by creating the dedicated integration branch from getsentry/sentry-mcp main, then review packages/cli, apps/cli-docs, and the root workspace files before applying the history-preserving import. Run the listed MCP, CLI, publish, craft, deployment, preview, correctness, and security validations. Done means every gate passes before the repository rename issue is acted on.

Sub-task of the toolkit monorepo merge: getsentry/cli#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: getsentry/cli#1254.
• Bridge CLI release completed and verified: getsentry/cli#1244 via getsentry/cli#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 getsentry/publish#9339 and getsentry/publish#9456.
• Craft workspace selection passes using getsentry/craft#848 and getsentry/craft#872; prefixed tags are isolated via getsentry/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.