fix: pass compound senderID to HandleMessage for Telegram allowlist

[zenchantlive]

Fixes Issue #310 - Telegram messages stuck on Thinking

Root Cause

In pkg/channels/telegram.go:358, HandleMessage was called with only the numeric user ID (e.g., "123456789"). However, the allowlist check in BaseChannel.HandleMessage expects the compound format ("123456789|myusername") to match @username entries.

When the allowlist contained @myusername, the numeric-only ID failed the match and the message was silently dropped after showing "Thinking...".

Fix

Use the pre-computed compound senderID instead of just the numeric ID:

• Before: c.HandleMessage(fmt.Sprintf("%d", user.ID), ...)
• After: c.HandleMessage(senderID, ...)

Changes

• pkg/channels/telegram.go: 1 line changed

Testing

• All pkg/channels tests pass (6 tests)
• Build compiles successfully

[Copilot]

Pull request overview

This PR fixes a critical bug in the Telegram channel where messages would get stuck on "Thinking..." when the allowlist used username format (@username). The root cause was a mismatch between the senderID format used in two different allowlist checks within the message handling flow.

Changes:

• Modified Telegram message handler to pass compound senderID ("ID|username") instead of just numeric ID to BaseChannel.HandleMessage, ensuring consistent allowlist matching

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.