#2086

Send Telegram and Discord messages without replies

OpenGit-on-my-levelwants to merge intofrom

Summary

  • Send CAR Telegram messages as standalone messages, including chunked replies and document uploads.
  • Send CAR Discord messages without outbound reply references, including shared sender and outbox replay paths.
  • Make the pre-commit hook reliable by isolating pytest temp directories and refreshing stale deterministic test expectations.

Why

Reply metadata forces noisy notifications. Standalone messages are less disruptive while inbound reply context remains available for routing and context.

Validation

  • Normal pre-commit hook passed end-to-end.
  • Core checks: 10,001 tests passed, plus Ruff, Black, and mypy.
  • Web Hub checks passed, including build and 1,010 Vitest tests.
  • Focused regression suite: 116 passed.
  • Chat surface lab: 20 passed; latency suite green (7/7).

Activity

3
cursor[bot]2mo ago

PR Summary

Medium Risk Changes chat delivery behavior on both Telegram and Discord outbound paths, including outbox replay. UX/notification impact is intentional but worth verifying across chunked and retry sends.

Overview CAR Telegram and Discord responses are now standalone messages instead of threaded replies, reducing noisy notifications while still parsing inbound reply context for routing.

Outbound reply_to_message_id is dropped from Telegram sendMessage/sendDocument (including chunked sends). Discord strips message_reference in the adapter, shared channel sender, and outbox replay path so retries cannot reintroduce stale reply links.

Also isolates the chat-apps pytest basetemp in check.sh so parallel validation lanes no longer share temp dirs.

Reviewed by Cursor Bugbot for commit 1b529b4972482722eb36d6ca09a3dfc960387d8a. Configure here.