## Why

Adding a new messaging channel (like Viber, Signal, WhatsApp, etc.) to AI Manager requires changes across multiple layers: an npm connector package, a server pubmodule, dashboard UI constants and templates, Helm configuration, and assets. There is currently no single reference that maps all the pieces. Without a guide, each new integration requires reverse-engineering the existing Telegram connector architecture. Creating a universal manual reduces future integration efforts from days to hours.

## What Changes

- Create a comprehensive manual `docs/adding-new-channel-guide.md` that documents every file and code change needed to add a new channel
- Research, download, and compare the source code of all existing `@tiledesk/*-connector` packages (Telegram, WhatsApp, Messenger) to identify what is common, what differs, and what is provider-specific
- The manual will document the universal pattern while highlighting the differences found across existing implementations

## Capabilities

### New Capabilities
- `new-channel-integration-guide`: A documentation framework mapping all integration points for adding a new messaging channel to AI Manager, covering all 4 layers (npm package, server pubmodule, dashboard UI, Helm config)

### Modified Capabilities
*(none)*

## Impact

- **`docs/adding-new-channel-guide.md`**: New file — the manual
- **No code changes**: This is a documentation-only change
- **Future work**: The manual will be used as the reference when implementing any specific channel