Description:
When using OpenClaw connected via Telegram DM channel with verbose mode enabled, tool execution logs (read/write/edit/exec) appear inconsistently. Sometimes they display correctly, other times they are completely absent from the chat despite tools executing successfully (verified via git history and file timestamps).

This makes it difficult to verify whether the agent is actually performing the actions it claims to be doing.

Environment:

• Channel: Telegram DMs
• Model: kimi-coding/k2p5
• Verbose mode: enabled (confirmed via /status)
• Runtime: agent=main

Steps to reproduce:

1. Connect OpenClaw to Telegram DM channel
2. Enable verbose mode (/verbose on)
3. Trigger multiple tool calls in sequence (e.g., read, write, exec)
4. Observe that some tool executions appear in verbose logs while others do not

Expected behavior:
All tool execution logs should consistently appear in the Telegram chat when verbose mode is enabled.

Actual behavior:
Tool execution logs appear sporadically. Example: Agent reports "done. pushed to backup" but no git commit or git push logs were visible in the chat. Git history later confirms the actions did occur.

Additional context:

• Issue Feature: Separate tool event streaming from channel verbose mode #8901 mentions separating tool event streaming from channel verbose mode — may be related
• Issue [Bug]: Verbose output missing filenames for read/write/edit tools when using file_path parameter #10059 mentions missing filenames in verbose output — different but in same area
• This appears to be a race condition or delivery issue rather than verbose mode being disabled