feat: Telegram two-way communication with voice message support

[dzianisv]

Summary

Implements full Telegram integration for OpenCode notifications with two-way communication including voice message support.

Features

Outbound Notifications

• Task completion notifications via Telegram (text + TTS audio)
• Session context tracking for reply routing

Inbound Replies

• Text message replies forwarded to OpenCode sessions
• Voice/video message support with local Whisper STT transcription
• Unified architecture: voice messages use telegram_replies table

Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│  Telegram   │     │  telegram-  │     │  Supabase   │     │ TTS Plugin  │     │  Whisper    │
│   User      │     │  webhook    │     │  Realtime   │     │             │     │  Server     │
└──────┬──────┘     └──────┬──────┘     └──────┬──────┘     └──────┬──────┘     └──────┬──────┘
       │                   │                   │                   │                   │
       │ 🎤 Voice message  │                   │                   │                   │
       │──────────────────>│                   │                   │                   │
       │                   │ Download audio    │                   │                   │
       │                   │ (has BOT_TOKEN)   │                   │                   │
       │                   │                   │                   │                   │
       │                   │ INSERT telegram_  │                   │                   │
       │                   │ replies (audio)   │                   │                   │
       │                   │──────────────────>│                   │                   │
       │                   │                   │ WebSocket push    │                   │
       │                   │                   │──────────────────>│                   │
       │                   │                   │                   │ POST /transcribe  │
       │                   │                   │                   │──────────────────>│
       │                   │                   │                   │ {text: "..."}     │
       │                   │                   │                   │<──────────────────│
       │                   │                   │                   │ Forward to session│

Key Components

Component	Description
telegram-webhook Edge Function	Handles /start, /stop, /status, and incoming replies
send-notify Edge Function	Sends notifications with session context
whisper/whisper_server.py	Local Whisper STT server (port 8787)
subscribeToReplies() in tts.ts	Unified handler for text + voice messages

Database Schema

• telegram_subscribers - User subscriptions
• telegram_reply_contexts - Active session routing (24h TTL)
• telegram_replies - Incoming messages with new voice columns:
  • is_voice - Boolean flag for voice messages
  • audio_base64 - Base64-encoded audio from Edge Function
  • voice_file_type - voice, video_note, or video
  • voice_duration_seconds - Duration in seconds

Configuration

{
  "telegram": {
    "enabled": true,
    "uuid": "your-uuid-here",
    "receiveReplies": true
  },
  "whisper": {
    "enabled": true,
    "model": "base",
    "port": 8787
  }
}

Testing

• 168 tests passing
• Covers webhook handling, voice transcription, migration structure

Files Changed

• tts.ts - Unified voice handling in subscribeToReplies()
• supabase/functions/telegram-webhook/index.ts - Voice → telegram_replies
• supabase/functions/send-notify/index.ts - Outbound notifications
• supabase/migrations/ - 3 migration files
• whisper/whisper_server.py - Local Whisper HTTP server
• docs/telegram.md - Architecture documentation
• test/tts.test.ts - Updated tests

Closes #1

[dzianisv]

Post-Merge Fix: Deployment Issue (Jan 25, 2026)

What Happened

After this PR was merged, Telegram replies weren't working. The code was correct but the Edge Functions weren't deployed to Supabase.

Root Cause

• send-notify was deployed at 04:25 UTC on Jan 24
• This PR was merged at 20:39 UTC on Jan 24
• The deployed function was 16 hours older than the code, missing the reply context storage

Fix Applied

1. ✅ Deployed send-notify v5 with reply context code
2. ✅ Deployed telegram-webhook v8 with simplified emoji confirmations
3. ✅ Added CI/CD: .github/workflows/deploy-supabase.yml
4. ✅ Added deploy script: scripts/deploy-supabase.sh
5. ✅ Set GitHub secrets: SUPABASE_ACCESS_TOKEN, SUPABASE_PROJECT_REF, SUPABASE_DB_PASSWORD

Going Forward

Supabase functions now auto-deploy when files in supabase/ change and are merged to main/master.

Verification

Test Session ID: ses_test_1769374929564
✓ Notification sent: reply_enabled=true
✓ Reply forwarded to session