fix(telegram): suppress quotes on internal status messages

[timsmykov]

Summary

• Let gateway-internal Telegram progress/status metadata request telegram_reply_to_mode=off.
• Teach the Telegram adapter to honor that per-send metadata override while preserving DM topic routing.
• Keep real user-facing replies anchored normally; only internal status/progress bubbles suppress the visible quoted prompt.

Why

Hermes-created Telegram DM topic lanes can require a reply anchor for routing, but internal progress/status messages should not render as visible replies quoting the user's prompt. This keeps topic delivery while removing repeated quote clutter.

Tests

• python -m compileall -q plugins/platforms/telegram/adapter.py gateway/run.py tests/gateway/test_telegram_thread_fallback.py tests/gateway/test_run_progress_topics.py
• ruff check plugins/platforms/telegram/adapter.py gateway/run.py tests/gateway/test_telegram_thread_fallback.py tests/gateway/test_run_progress_topics.py
• python -m pytest tests/gateway/test_telegram_thread_fallback.py tests/gateway/test_run_progress_topics.py -q -o 'addopts='
• Local git merge-tree against upstream/main: clean

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[tonydwb]

Code Review Summary

Verdict: LGTM

Suppresses quote display on Telegram internal status messages by adding a telegram_reply_to_mode metadata field. The implementation is clean — the gateway sets 'off' mode on non-conversational sends, and the adapter respects it. Tests cover both the metadata propagation and the quote suppression.

Reviewed by Hermes Agent

[teknium1]

Thanks for the focused Telegram routing fix. The current-main premise is still valid: gateway/run.py:17473-17478 preserves Telegram progress metadata, while plugins/platforms/telegram/adapter.py:3647-3682 turns its DM-topic anchor into a reply unless the effective mode is off.

Problems

• The adapter test covers the legacy send_message route, but the PR also changes rich-message routing. Current main dispatches that route through _compute_single_send_routing at plugins/platforms/telegram/adapter.py:1620, so its changed behavior needs direct coverage.

Suggested changes

• Add a rich-message DM-topic test with telegram_reply_to_mode: "off"; verify the sendRichMessage payload has message_thread_id and no reply_parameters.

This is an automated hermes-sweeper review.