Greptile Summary

This PR adds a pre-flight guard to sendMessageTelegram that short-circuits and returns a synthetic suppressed result when the payload is a bare NO_REPLY token with no media or inline keyboard — mirroring the equivalent Slack-side guard. The change prevents a transient bare token from reaching the Telegram API and brings the suppression logic ahead of the (expensive) Bot-client initialisation.

Key changes:

• parseTelegramTarget, mediaUrl extraction, and buildInlineKeyboard are now computed before resolveTelegramApiContext so the early-exit can use them without touching the API client.
• The guard correctly delegates to the existing isSilentReplyText utility (which already handles surrounding whitespace via ^\s*NO_REPLY\s*$), so the pre-trim() in trimmedText is redundant but harmless.
• TelegramSendResult is fully satisfied by { messageId: "suppressed", chatId: target.chatId }.
• One regression test covers the basic suppression path; the inverse cases (NO_REPLY + media, NO_REPLY + buttons) are not tested but are low-risk given the straightforward boolean guard.

Confidence Score: 4/5

• Safe to merge — the guard is logically correct, non-breaking, and backed by a regression test.
• The change is narrow and well-scoped: it only adds an early-exit path that returns before any API call, leaving all existing send logic untouched. The pure helper functions moved ahead of the guard have no side effects. The return type contract is satisfied. The only gap is missing inverse-case tests (NO_REPLY with media or buttons), but the boolean guard is simple enough that the risk is very low.
• No files require special attention.

_{Last reviewed commit: 917bba6}