# v0.25.2 — Close Telegram-Gated Code Path Gaps

## What Changed

**Watchdog notifications for Slack** — Session intervention and recovery alerts from the watchdog now go to the correct Slack channel, not just Telegram topics.

**Resume heartbeat includes Slack** — The 60-second proactive resume UUID save now covers Slack channel-session mappings. Previously only Telegram topics were tracked, meaning Slack sessions lost resume context on server crash.

**Graceful shutdown saves Slack resume** — On server shutdown (SIGINT/SIGTERM), resume UUIDs are now saved for both Telegram topics and Slack channels. Previously gated behind an if-telegram check.

**Prompt Gate relay for Slack** — Detected prompts in Slack-bound sessions now relay to the Slack channel with interactive Block Kit buttons. Previously prompts only went to Telegram topics.

## What to Tell Your User

Several infrastructure systems that only worked with Telegram now also work with Slack. Watchdog alerts, session resume on restart, and prompt approvals all properly route to Slack channels now. This means Slack sessions are more reliable and recover better after server restarts.

## Summary of New Capabilities

| Capability | How to Use |
|-----------|-----------|
| Watchdog alerts in Slack | Automatic when sessions get stuck |
| Resume across restarts | Automatic — sessions resume with context after server restart |
| Prompt relay in Slack | Automatic — approval prompts appear in the session channel |
