Bug Description

On Telegram, Hermes normally coalesces tool-progress updates into a single edited message.

After a long run with many tool calls, if one progress edit hits Telegram flood control (RetryAfter), Hermes stops editing that progress message and starts sending fresh tool-progress messages for the rest of the run.

Example symptom: 🔧 patch: "src/components/Button.tsx" (×5)

This appears as a new message instead of updating the existing progress bubble.

Expected Behavior

Tool progress should continue to coalesce into one edited message.

If Telegram rate-limits an edit, Hermes should wait and resume editing later, or buffer updates temporarily. It should not degrade into posting separate progress messages for the rest of the run.

Actual Behavior

After one flood-control hit, progress-message editing is effectively disabled for that run, and later tool updates are posted as separate new messages.

Affected Component

• Gateway

Messaging Platform (if gateway-related)

• Telegram

Additional Logs / Traceback (optional)

WARNING gateway.platforms.telegram: [Telegram] Telegram flood control, waiting 14.0s
INFO gateway.run: [Telegram] Progress edits disabled due to flood control

Root Cause Analysis (optional)

This looks like a gateway state bug:

• Telegram progress-message edit hits flood control
• the adapter returns a failed edit
• the gateway sets can_edit = False
• subsequent tool-progress updates fall back to send(...) instead of edit_message(...)

The problem is that editing is disabled for the remainder of the run instead of recovering after the flood window passes.

Proposed Fix (optional)

Do not permanently disable progress editing after a single flood-control error.

Instead:

• keep the same progress message alive
• wait until retry_after expires, or
• buffer/coalesce updates until editing is allowed again

At minimum, the fallback should recover automatically instead of turning all later progress updates into separate messages.