Summary

• Problem: Telegram progress-mode drafts could remain visible when verbose tool output or visible tool artifacts were delivered as standalone messages.
• Solution: Rotate and clear tool-progress-only answer drafts before sending visible tool output payloads.
• What changed: Updated Telegram dispatch ordering and added regression coverage for verbose tool text and visible tool artifact paths.
• What did NOT change: Telegram transport, rich message rendering, provider behavior, tool execution, auth, secrets, network, or progress draft implementation internals.

Fixes #90753

Regression Test Plan

• Coverage level: Unit test
• Target test file: extensions/telegram/src/bot-message-dispatch.test.ts
• Scenario locked in: progress drafts are cleared before durable verbose tool output and visible tool artifacts are delivered.
• Why this is the smallest reliable guardrail: the regression is dispatch ordering, so the test asserts draft clearing happens before standalone Telegram deliveries.

Verification run:

pnpm test extensions/telegram/src/bot-message-dispatch.test.ts -- -t "clears progress drafts before"

Test Files  1 passed (1)
Tests       2 passed | 118 skipped (120)

Root Cause

• Root cause: progress-mode tool status drafts were not rotated before all visible tool-output delivery paths.
• Missing detection / guardrail: existing tests covered final-answer cleanup but not durable verbose tool output or visible tool artifact delivery.