Merge sentry-cli + sentry-mcp into getsentry/toolkit monorepo (master)

[BYK]

Tracking issue for merging getsentry/cli into the existing getsentry/sentry-mcp repository, validating the combined monorepo there, and only then renaming it to getsentry/toolkit. The final repository is a pnpm workspace (no Turbo) with independent prefixed releases and phased shared code.

Full plan: https://gist.github.com/BYK/8c0ce6cec64608f41fe5654b7827228e

Settled architecture

• Use getsentry/sentry-mcp as the destination; do not create a fresh repository. This preserves MCP production secrets, environments, GitHub App, webhooks, Vercel, and Cloudflare wiring.
• Import CLI while the repository is still named getsentry/sentry-mcp. Rename only after the integrated monorepo and live deployment paths pass every gate.
• Preserve CLI and docs history through two filtered git subtree imports into packages/cli and apps/cli-docs.
• Release products independently with cli@x.y.z and mcp@x.y.z.
• CLI docs and previews are release-gated on Cloudflare; https://cli.sentry.dev/install remains unchanged. The MCP Worker remains on Cloudflare.
• Drop Turbo for pnpm-native orchestration.
• Manage patches at the workspace root and use a shared dependency catalog.
• Colocate first; extract @sentry/toolkit-core later.

Ordered migration gates

1. Prerequisites

• toolkit merge: pre-shape CLI into packages/cli + apps/cli-docs #1238 / chore: pre-shape repo into pnpm-workspace monorepo layout #1254 — pre-shape CLI into packages/cli and apps/cli-docs.
• feat: accept workspace publish requests publish#9339 — accept workspace publish requests.
• fix: bootstrap root publish locations publish#9456 — bootstrap root publish locations.
• feat: prefix-aware read paths for monorepo multi-product releases craft#847 — prefix-aware tag and changelog read paths.
• feat(config): top-level workspaces schema + --workspace selector craft#848 — top-level release workspace schema and selector.
• feat: propagate release workspaces craft#872 — propagate release workspaces.
• Replace the transitional Vercel CLI-docs target with release-gated Cloudflare hosting and previews.

2. Bridge CLI release — hard blocker

• toolkit merge: bridge CLI release + dual-source upgrade compatibility #1244 / feat(cli): add toolkit upgrade bridge #1569 — implement ordered Toolkit-first / CLI-fallback upgrade sources.
• Cut and verify stable bridge CLI release 0.45.0 from getsentry/cli; import is now unblocked.

3. Import and integrate under the current name

• toolkit merge: import CLI into sentry-mcp, validate, then rename #1239 — import CLI and docs history into an integration branch of getsentry/sentry-mcp.
• toolkit merge: unify toolchain + root patches (bump @sentry/* to 10.54.0) #1240 — unify toolchain, dependency catalog, and root patches.
• toolkit merge: drop Turbo, pnpm-native orchestration #1241 — replace Turbo with pnpm-native orchestration.
• toolkit merge: per-product CI with changed-file gating #1242 — per-product CI and changed-file gating.
• toolkit merge: prefixed independent releases (cli@ / mcp@) #1243 — configure prefixed independent release workspaces.

4. Pre-rename validation

• toolkit merge: pre-rename validation, rename, release cutover #1246 — full CLI/MCP CI, workspace release dry-runs, Cloudflare CLI-docs preview, and MCP Cloudflare deploy canary pass under getsentry/sentry-mcp.
• Independent correctness and security reviews pass on the exact integration head.

5. Rename and revalidate

• Validate merged monorepo in sentry-mcp, then rename to getsentry/toolkit sentry-mcp#1156 — rename to getsentry/toolkit, verify all repository and deployment integrations, rerun CI and canaries.
• Run staging releases for both products and the complete CLI compatibility matrix.

6. Cutover and compatibility window

• Dual-publish CLI releases and nightlies to Toolkit and getsentry/cli.
• Announce Toolkit as canonical.
• Keep getsentry/cli writable; do not archive it while dual publishing is active.
• After at least two stable releases and roughly 90 days, verify legacy usage has ended, then archive getsentry/cli with a redirect.

7. Follow-up

• toolkit merge: Phase B — extract @sentry/toolkit-core (shared code) #1247 — extract @sentry/toolkit-core incrementally.

Highest risks

• toolkit merge: bridge CLI release + dual-source upgrade compatibility #1244: compatibility for old binaries that only know getsentry/cli.
• toolkit merge: drop Turbo, pnpm-native orchestration #1241 / Validate merged monorepo in sentry-mcp, then rename to getsentry/toolkit sentry-mcp#1156: changes to the live MCP deploy path and repository identity.

Every gate is sequential. Never rename before pre-rename validation, and never archive getsentry/cli before the compatibility window ends.

[BYK]

Bridge gate complete: #1569 shipped as stable CLI 0.45.0 through getsentry/publish#9491. Pre-bridge legacy upgrade, Toolkit-404/legacy fallback from the bridge binary, live installer, GitHub/npm artifact identity, Homebrew checksums, registry metadata, and release deployment were verified. #1239 is now unblocked; detailed evidence is recorded on #1239.