observability-contextlisted

## When to invoke Auto-loads when the caller references: - **Sentry issue URL**: `sentry.io/organizations/<org>/issues/<id>/` or `<org>.sentry.io/issues/<id>/`. - **Sentry event ID**: a raw event ID mentioned alongside a Sentry context clue (e.g. "Sentry event `abc123`"). - **Free-text production signal**: text describing a production error, exception, stack trace, regression, or alert — WHEN a Sentry MCP tool (`mcp__sentry__*`) is reachable in-session. If no reference is present, exit cleanly. ## Adapters ### Sentry - **Trigger:** Sentry issue URL (`sentry.io/organizations/<org>/issues/<id>/` or `<org>.sentry.io/issues/<id>/`), a raw Sentry event ID paired with a Sentry context clue, or free-text mention of a production error/exception/stack trace/regression/alert, gated on a reachable `mcp__sentry__*` tool. - **Fetch:** `mcp__sentry__get_issue` with the issue ID or URL (aspirational — this plugin ships no Sentry MCP integration; this recipe activates only if the user has one connected). For a bare event ID, first resolve it via `mcp__sentry__get_event`. - **Extract → block fields:** title/message and culprit → Message / culprit; `firstSeen` → First seen; event count and rate over the query window → Frequency; top stack frames or breadcrumb trail (condensed) → Stack / breadcrumb summary; issue permalink → Source. - **Degrade:** If no `mcp__sentry__*` tool is reachable, emit `observability-context: Sentry MCP unavailable; proceeding without context.` Never fabricate or g