Validate merged monorepo in sentry-mcp, then rename to getsentry/toolkit

[BYK]

Part of the sentry-cli + sentry-mcp -> getsentry/toolkit monorepo merge. Master: getsentry/cli#1248.

Decision

Use the existing getsentry/sentry-mcp repository as the integration destination because it already owns MCP production secrets, environments, branch protections, GitHub App installation, webhooks, Vercel, and Cloudflare wiring.

Do not rename first. Import CLI into getsentry/sentry-mcp, validate the complete monorepo and live deployment paths under the current repository identity, then rename to getsentry/toolkit as the final repository cutover. GitHub redirects preserve the old repository URL after the rename.

CLI pre-shape is complete: getsentry/cli#1254. The bridge CLI release in getsentry/cli#1244 is a hard prerequisite for import.

Pre-rename integration

• Shipped the verified bridge CLI 0.45.0 before importing CLI history (toolkit merge: bridge CLI release + dual-source upgrade compatibility cli#1244).
• Integrated on a branch before Toolkit #1320 merged into getsentry/sentry-mcp.
• Imported history into packages/cli and apps/cli-docs through Toolkit #1320 (toolkit merge: import CLI into sentry-mcp, validate, then rename cli#1239).
• Added apps/* to pnpm-workspace.yaml.
• Unify root toolchain, catalogs, patches, and lockfile.
• Replaced Turbo with pnpm-native workspace builds and an exact-version MCP deployment; protected deployment and live Worker smoke tests passed after Toolkit #1400.
• test.yml discovers changed workspaces through scripts/ci-projects.mjs and has a skip-aware required test gate.
• Verify Vercel CLI-docs previews from apps/cli-docs.
• Exact-head correctness and security reviews passed for Toolkit #1320.

Rename gate

All pre-rename checks above must pass before this step.

• Renamed getsentry/sentry-mcp to getsentry/toolkit after the import; repository ID 957245447 remained unchanged.
• Confirm the old URL redirects and the default branch, protections, environments, secrets, GitHub App, webhooks, Vercel project, and Cloudflare Worker connection remain intact.
• Update repository/homepage references and explicit repository slugs in workflows, package metadata, docs, Craft, Publish, Vercel, and Cloudflare configuration.
• Reran required CI and deployed the exact-version production MCP Worker successfully under getsentry/toolkit.
• Confirm a release-gated CLI-docs preview under the new repository name; Vercel is live but preview verification was not established here.
• Run a prefixed workspace-release dry-run for both cli and mcp.
• Run the CLI upgrade compatibility matrix in toolkit merge: bridge CLI release + dual-source upgrade compatibility cli#1244.

Deployment ownership

• MCP Worker remains on Cloudflare.
• CLI docs and previews use release-gated Vercel as the final host, with https://cli.sentry.dev/install unchanged. The MCP Worker remains on Cloudflare.

Cross-links

• Master: Merge sentry-cli + sentry-mcp into getsentry/toolkit monorepo (master) cli#1248
• Bridge CLI release: toolkit merge: bridge CLI release + dual-source upgrade compatibility cli#1244
• History import: toolkit merge: import CLI into sentry-mcp, validate, then rename cli#1239
• Verification/cutover: toolkit merge: pre-rename validation, rename, release cutover cli#1246
• Craft prefix-aware tags: feat: prefix-aware read paths for monorepo multi-product releases craft#847
• Craft workspaces: feat(config): top-level workspaces schema + --workspace selector craft#848 and feat: propagate release workspaces craft#872
• Publish workspaces: feat: accept workspace publish requests publish#9339 and fix: bootstrap root publish locations publish#9456

[linear-code]

MCP-1002

[BYK]

Master tracking issue: getsentry/cli#1248 (getsentry/cli#1248)

[BYK]

Status for the repository-cutover tracker: the CLI import was merged via #1320 before the getsentry/sentry-mcp → getsentry/toolkit rename; Toolkit production MCP now runs the reviewed exact-version deployment (#1399, #1400), and the live version was verified after the successful protected deploy. The CLI stable release and GHCR nightly are published; the shell-installer Toolkit-nightly cutover awaits review in #1403. The user chose to retain the live, release-gated Vercel CLI-docs setup, superseding the old Cloudflare-docs replacement requirement. The old broad CI/deployment PR #1343 was closed; its remaining trusted CI report publication is tracked in #1402. This tracker should stay open for the product compatibility/dual-publish gates and the legacy PR/issue migration rather than treating the historical pre-rename checklist as work to repeat.