[Bug] Assistant final text reply not delivered to messaging channel after message tool dispatch

Summary

When a turn includes a message tool call that successfully delivers content to a messaging channel (e.g. Telegram), any subsequent assistant text reply appears only in the web transcript but is not delivered to the messaging channel. The user on Telegram only receives the tool-dispatched content, not the assistant's natural-language summary/commentary that follows.

Reproduction Steps

1. Configure a Telegram channel (or any messaging channel).
2. In a conversation, trigger an agent turn that:
   • Uses the message tool to send content (file, text, etc.) to the messaging channel.
   • Then appends a final assistant text reply (e.g. a brief comment or summary).
3. Observe the Telegram side: only the tool-dispatched content arrives. The final assistant text never reaches the messaging channel.
4. Observe the web transcript: the final assistant text is present and visible.

Expected Behavior

After the message tool delivers the primary content, the assistant's subsequent text reply should also be delivered to the messaging channel, so the user sees both the dispatched content and the natural-language commentary in the same channel.

Actual Behavior

• The message tool output is delivered to Telegram correctly.
• The assistant's final text reply (post-tool-call) appears in the web UI transcript but is not forwarded to Telegram.
• This results in the user on Telegram receiving a "headless" file/message with no accompanying context or commentary.

Key Evidence

Checked two real turns where message tool was used:

1. File delivery (music):

   • didSendViaMessagingTool: true
   • assistantTexts: ['小鸡出品，梁静茹《宁夏》，FLAC 无损直接发你了 🎵']
   • Telegram received: the FLAC file only. The comment text never arrived.

2. Text delivery (V2EX hot topics):

   • didSendViaMessagingTool: true
   • assistantTexts: ['V2EX 热门已发到 Telegram ... 人间百态浓缩版 😂']
   • messagingToolSentTexts: only the ranked list body.
   • Telegram received: the ranked list only. The closing comment never arrived.

In both cases, the assistant text was generated and recorded, but not dispatched to the messaging channel after the tool call completed.

Environment

• OpenClaw version: 2026.5.2
• Channel: Telegram
• Model: observed across multiple provider/models

Additional Context

This appears to be a delivery/suppress logic issue: after a successful message tool call within the same turn, the system may be treating the turn as "fully delivered" and skipping the remaining assistant text. Related but distinct from:

• Bug: messaging tool suppress mechanism skips when tool fails then retries in same turn, causing duplicate delivery #55640 (duplicate delivery on retry)
• [Bug]: Telegram transcript contains final reply but no outbound send occurs for [thinking,text] turn on 2026.4.11 #66459 (no outbound send for thinking/text turn)
• [Bug]: deliveryMode="final_only" silently drops long tool-loop replies when no phase=final chunk is emitted #76828 (final_only silently drops long tool-loop replies)

None of these match the exact symptom: message tool content delivered, but subsequent assistant text within the same turn silently dropped from messaging channel delivery.