comms-contextlisted

## When to invoke Auto-loads when the caller references: - **Slack permalink**: `<workspace>.slack.com/archives/<channel>/p<timestamp>`. - **PagerDuty incident URL**: `<subdomain>.pagerduty.com/incidents/<id>`. - **PagerDuty incident ID**: a bare incident ID mentioned alongside a PagerDuty context clue (e.g. "PagerDuty incident `PD-4521`"), when a PagerDuty MCP tool (`mcp__pagerduty__*`) is reachable in-session. - **Free-text on-call signal**: text describing a page, on-call escalation, or Slack thread reference. If no reference is present, exit cleanly. ## Adapters ### Slack permalink - **Trigger:** Slack permalink URL (`<workspace>.slack.com/archives/<channel>/p<timestamp>`). - **Fetch:** `mcp__slack__get_permalink_thread` with the channel and timestamp parsed from the URL (aspirational — this plugin ships no Slack MCP integration; this recipe activates only if the user has one connected). Resolve the permalink to a channel + timestamp, then fetch the root message and its thread replies. - **Extract → block fields:** message author plus every distinct thread replier → Participants; message and reply timestamps in chronological order → Timeline; if the thread reaches a visible resolution or decision, summarize it, else "ongoing" → Status; the permalink itself → Source. - **Degrade:** If no `mcp__slack__*` tool is reachable, emit `comms-context: Slack MCP unavailable; proceeding without context.` Never fabricate thread content or participants. ### PagerDuty incident - *