Greptile Summary

This PR adds per-dispatch deduplication to prevent semantically identical Telegram payloads from being sent multiple times within the same turn. The implementation introduces a buildDeliveredPayloadKey function that creates a normalized key from text, media URLs, and reply target, while intentionally excluding the audioAsVoice flag to catch duplicates regardless of delivery format.

Key changes:

• Deduplication uses a Set to track delivered payload keys within each dispatch turn
• The dedupe key is based on trimmed text, media list, and replyToId only
• When a duplicate is detected, it logs the skip and marks as delivered without re-sending
• Keys are only added to the Set after successful delivery, allowing retries on failures
• Test coverage validates the specific scenario of duplicate voice messages with different audioAsVoice values

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The implementation is clean and focused, with proper null handling, correct Set-based deduplication scoped to a single dispatch turn, and appropriate test coverage. The logic correctly handles edge cases like delivery failures (keys only added on success) and empty payloads (returns null key). The intentional exclusion of audioAsVoice from the dedupe key is well-documented and solves the stated problem.
• No files require special attention

_{Last reviewed commit: 687ce1a}