# v0.25.3 — Platform-Agnostic Session Health Systems

## What Changed

**StallTriageNurse works for Slack** — The LLM-powered session recovery system was previously gated behind an if-telegram check. Now it initializes for any messaging adapter and uses platform-aware callbacks for message history, topic/channel communication, and session respawning.

**TriageOrchestrator works for Slack** — The next-generation session recovery system (with scoped diagnostic sessions) is no longer Telegram-exclusive. All callbacks resolve Slack channels via synthetic ID mapping.

**SessionRecovery works for Slack** — The fast mechanical recovery path now routes kill commands through SessionManager (firing the beforeSessionKill hook for resume UUID saving) and handles Slack channel-bound sessions.

**SessionMonitor works for Slack** — Proactive health monitoring now aggregates sessions from both Telegram topics and Slack channels. Alerts route to the correct platform.

**Resume heartbeat includes Slack** — The 60-second proactive resume UUID refresh now covers Slack sessions.

## What to Tell Your User

Session health monitoring and automatic recovery now work for Slack sessions, not just Telegram. If a Slack session gets stuck, the same intelligent triage system that works for Telegram will detect and attempt to recover it.

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Stall triage for Slack | Automatic — detects and recovers stuck Slack sessions |
| Session monitoring for Slack | Automatic — proactive health checks for all sessions |
| Session recovery for Slack | Automatic — mechanical fast-path recovery |
