bug: Sentry MCP integration returns 401 — Incident Responder cannot run

[sw-factory-automations]

Description

The Sentry MCP integration at the Ona organization level is in MCP_INTEGRATION_PHASE_FAILED state with error: "Failed to connect to MCP server Sentry: unauthorized (401)".

This blocks the Incident Responder, Performance Monitor, and any other automation that relies on Sentry MCP tools (search_issues, get_sentry_resource, search_events, update_issue). Production errors are not being triaged automatically.

• Integration URL: https://app.gitpod.io/integrations/mcp/019d67bb-cd75-7d7a-9081-342070c92bf3/
• Region: https://de.sentry.io
• Organization: ona-2j
• Project: memo

Acceptance Criteria

• Sentry MCP integration re-authorized and in a healthy state
• Incident Responder automation can successfully call search_issues via MCP
• pnpm lint && pnpm typecheck && pnpm test pass (no code changes expected)

Technical Notes

• This is an organization-level configuration issue, not a code bug. A human administrator needs to re-authorize the Sentry OAuth integration at the Ona platform level.
• The OAuth token has either expired or was revoked.
• No code changes are needed — this is purely an infrastructure/config fix.
• Until resolved, production error monitoring is manual-only.