docs: sync ADP changes from cloudv2 (2026-06-26)

[micheleRP]

Summary

Documents the new Sentry managed MCP server, the one user-facing ADP change merged to cloudv2 main in the last 24 hours that requires docs.

Sentry is a read-only managed MCP server (per-user OAuth, 16 read tools, optional single-organization scoping) for the diagnose-and-fix flow: discover orgs/projects → read an issue and its stack trace → scope impact across tags/releases → localize the fix to a suspect commit.

Maturity: beta. The server's register_mcp.go does not set FeatureGate: "alpha", so it is not alpha-gated in source, and it is not in the GA set. Per the docs maturity policy it ships documented as beta (:page-beta: true, badge:beta in the catalog).

Changes

• New page modules/connect/pages/managed/sentry.adoc — setup how-to (prerequisites, OAuth credentials, UI + rpk ai mcp create config with unrestricted and org-confined variants, full 16-tool reference, examples, troubleshooting, limitations).
• Catalog managed-catalog.adoc — new Sentry row under Utility with a beta badge and setup-guide link; updated the source-verification comment.
• Nav modules/ROOT/nav.adoc — Sentry entry under the managed catalog (alphabetical).

Preview pages

• Sentry Managed MCP Server (new)

(404s until Netlify finishes the preview build — expected.)

cloudv2 source commits

• f7121d02d — feat(aigw): add the Sentry managed MCP server to the catalogue
• bcdaea997 — feat(aigw): expand Sentry MCP with 11 read tools for diagnose-and-fix (final surface = 16 tools)

Grounded against apps/aigw/internal/mcp/managed/mcps/sentry/register.go and register_mcp.go, proto/mcps/redpanda/mcps/sentry/v1/sentry_config.proto, and apps/aigw/docs/sentry-mcp.md on main.

Not documented (intentionally)

The remaining cloudv2 commits in the window are adp-ui frontend changes (Activity drill-down, guardrail setup assistant, faceted-filter UI, bundle perf, AI SDK upgrade) and internal/infra work — no user-facing config, API, CLI, default, or behavior changes that need docs.

Optional reviewer

Added @malinskibeniamin (author of the source commits) as an optional reviewer for a source-accuracy courtesy check. Their approval is not blocking.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FJBbvNLBEJyx7BZZYYJ6Me

[netlify]

✅ Deploy Preview for redpanda-agentic-data-plane ready!

Name	Link
🔨 Latest commit	b22c55c
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-agentic-data-plane/deploys/6a3e94e45091be000812313b
😎 Deploy Preview	https://deploy-preview-111--redpanda-agentic-data-plane.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[micheleRP]

[adp-docs PR critic] Verdict: looks accurate against the cloudv2 source. No critical or blocking issues found. I verified every factual claim in the diff against redpanda-data/cloudv2 main.

Source accuracy — verified ✅

• 16 tools and their names — match apps/aigw/internal/mcp/managed/mcps/sentry/register.go exactly (all 16 SentryReadService_*Tool registrations: list_organizations, list_projects, list_issues, get_issue, get_issue_latest_event, list_issue_events, get_issue_event, get_event, resolve_event_id, get_issue_tag, list_issue_tag_values, list_issue_hashes, get_event_committers, list_releases, get_release, list_release_commits).
• Config schema — organization_slug and the user_oauth oneof with provider_name + required_scopes match proto/mcps/redpanda/mcps/sentry/v1/sentry_config.proto and proto/mcps/redpanda/mcps/v1/auth.proto (UserOAuthAuth). The @type type.googleapis.com/redpanda.mcps.sentry.v1.SentryMCPConfig is correct.
• organization_slug confinement (forces the value, rejects mismatches, leaves list_organizations unrestricted), scope_upgrade_required semantics, read-only by design, sentry.io-only, and the PII/tags note all match the source proto comments and apps/aigw/docs/sentry-mcp.md.
• Scopes — org:read, project:read, event:read, project:releases. Note: the comment in sentry_config.proto mentions only the first three, but the authoritative well-known sentry provider config and the per-scope breakdown in apps/aigw/docs/sentry-mcp.md both confirm all four (project:releases is needed for list_releases/get_release/list_release_commits). The PR's four-scope list is the correct one.

Maturity (policy) — verified ✅

• register_mcp.go does not set FeatureGate: "alpha", so the server is not alpha-gated in source and beta is the correct label per the repo's maturity policy. Category: MANAGED_MCP_CATEGORY_UTILITY in source matches the new catalog row's placement under Utility.

Correctness — verified ✅

• New page resource ID matches the file path (connect:managed/sentry.adoc); nav entry placed alphabetically; catalog row has the right cell count for the 3-column table.
• All xref targets exist in-repo: oauth-providers.adoc, user-delegated-oauth.adoc, create-server.adoc, test-tools.adoc, register-remote.adoc.

Minor (non-blocking), nothing to fix

• I did not independently audit the full 24h cloudv2 commit window to confirm Sentry was the only doc-requiring change (the body lists the rest as adp-ui/infra). The Sentry documentation itself is complete and accurate against source; flagging only that the "nothing else needs docs" claim was taken on the PR's word.

Accurate, well-grounded, and standards-compliant. Advisory only — no approval implied.

---

Generated by Claude Code

[micheleRP]

[adp-docs PR critic] Re-review of new commit b22c55c4 ("apply docs-team-standards review fixes") — still accurate against the cloudv2 source. No critical or blocking issues.

This commit landed after my first review (a10f9a40). It is style/wording only — dropping hardcoded tool counts from prose, orgs→organizations, parallel imperative Tools-table descriptions, un-bolding non-link emphasis, expanding PII on first use, adding a UI-label TODO, wrapping rpk ai in an xref, and restructuring the examples under one H2. None of these touch maturity/status, product positioning, or other policy-sensitive content. I re-verified the changed surface:

Source accuracy — re-verified ✅

• Example argument names ground to proto/mcps/redpanda/mcps/sentry/v1/sentry_service.proto: the list_issues example's organization_slug, project_slug, query, stats_period are exactly the ListIssuesRequest fields; the get_issue_latest_event example's organization_slug + issue_id are exactly GetIssueLatestEventRequest.
• Tools-table descriptions (now imperative/parallel) still match the per-RPC comments in sentry_service.proto — including get_issue_event's oldest = regression boundary, get_event_committers needing a source-code integration, and list_release_commits as the candidate set behind a regression.
• 16 tools / tool names unchanged and still match apps/aigw/internal/mcp/managed/mcps/sentry/register.go. The four read scopes are unchanged.

Correctness — re-verified ✅

• The newly added xref reference:rpk/rpk-ai/rpk-ai.adoc resolves (page exists in-repo). rpk ai mcp create --managed-config is a real command (rpk-ai-mcp-create.adoc) and the JSON-config pattern is consistent with the existing Salesforce page.
• Catalog/nav changes from the first commit are unchanged and remain correct.

Verdict carries over from my first review: accurate, well-grounded, standards-compliant. The // TODO: confirm the exact UI field labels… note is an honest, appropriate caveat — worth resolving via a UI walkthrough before this is considered final, but not blocking. Advisory only — no approval implied.

---

Generated by Claude Code