The pulse reads a challenge issue as a caller, not an error

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jm2auWk6RP71CjaAb4FMoG

.claude/skills/wizwar-pulse/SKILL.md

@@ -22,7 +22,11 @@ quiet, say so in one line before the details.
      protocol error"` — anything nonzero deserves a look (Sentry has
      the stack traces)
 2. **Sentry** (MCP connector, org `locallygrownnet`, project `wizwar`):
-   - `search_issues` for `is:unresolved` — new issues are the headline
+   - `search_issues` for `is:unresolved` — new issues are the headline.
+     An issue titled "<name> challenges Kestrel to a game — <link>" is
+     not an error: it is the keeper's bell (a lobby called Eric to a
+     seat; the room link is in the title). Report it as a caller waiting,
+     with the room code; Eric resolves it himself once answered.
    - `get_monitor_details` for cron monitor slug `new-monitor` (named
      wizwar-backup) — last check-in must be ok and recent; the uptime
      monitor alerts on its own but note any incidents