fix(telegram): pipe table auto-rich bypasses rich_messages: false config

[pizzav-xyz]

Bug Description

Commit 9d225fbf4 (fix(telegram): auto-rich pipe tables and topic routing for sendRichMessage) added _content_is_pipe_table_primary() which forces pipe-table content through sendRichMessage even when rich_messages: false is configured.

This reintroduces the "This message is not supported on your version of Telegram" error on clients that don't support Bot API 10.1 rich messages (AyuGram, Telegram Web, some desktop clients).

Root Cause

_rich_delivery_enabled() was changed to:

def _rich_delivery_enabled(self, content: str) -> bool:
    return bool(
        getattr(self, "_rich_messages_enabled", True)
        or self._content_is_pipe_table_primary(content)  # ← bypasses config
    )

The or clause means pipe tables always go through sendRichMessage regardless of the rich_messages opt-in setting.

Expected Behavior

When platforms.telegram.extra.rich_messages: false is set, no content should be sent via sendRichMessage — including pipe tables. The legacy MarkdownV2 path should be used for all content.

Actual Behavior

Pipe tables are auto-routed to sendRichMessage even with rich_messages: false, breaking delivery on AyuGram and Telegram Web.

Fix

Remove the or self._content_is_pipe_table_primary(content) bypass from _rich_delivery_enabled() so the config flag is fully respected.

def _rich_delivery_enabled(self, content: str) -> bool:
    return bool(
        getattr(self, "_rich_messages_enabled", True)
    )

Related

• Fixes [Bug]: Telegram Web showing "This message is not supported on the web version of Telegram" #46098, [Bug]: Telegram Web cannot render sendRichMessage assistant replies #45785 (original reports, still open)
• Regression from 9d225fbf4 which landed after fix(telegram): make Bot API 10.1 rich messages opt-in (default off) (#48422) #50322 (the opt-in fix)
• PR fix(telegram): keep rich messages opt-in for copyable replies #48422 addresses the same config default but doesn't cover the pipe table bypass

[couturierc]

Confirming this on AyuGram (Hermes 0.18.2, gateway on Telegram).

With platforms.telegram.extra.rich_messages: false explicitly set in config.yaml, any assistant reply containing a Markdown pipe table still routes through sendRichMessage and renders as an unsupported-message card:

This message is not supported on your version of Telegram. Please update to the latest version.
[ Update AyuGram ]

Non-table replies (plain prose, bold/italic, bullet lists, fenced code blocks) render correctly, which isolates the failure to the pipe-table auto-rich path exactly as described in the root cause — _rich_delivery_enabled()'s or self._content_is_pipe_table_primary(content) clause overriding the opt-out.

I applied PR #53825's one-line removal of that clause locally and can confirm pipe tables then fall back to the legacy MarkdownV2 path (row-group bullets / aligned code block), which AyuGram renders fine. tests/gateway/test_telegram_rich_messages.py passes (72 passed) with the PR's test updates. LGTM as the correct fix.