hermes - 💡(How to fix) Fix Telegram clarify prompts show busy-session controls and must keep accepting replies [1 pull requests]

Bug Description

When the gateway sends a clarify prompt on Telegram, the prompt currently appends the generic busy-session controls (/steer, /interrupt, /stop) underneath the clarify choices. That makes the clarify UI look like an interrupt surface instead of the active input surface, and it can confuse or steal taps from the actual clarify choices.

There is a related interaction risk: while the agent thread is blocked in clarify_tool.wait_for_response, normal inbound messages in the same chat must continue to reach the gateway runner so typed or transcribed voice replies can resolve the pending clarify. The user should not have to tap an inline button for the bot to keep listening.

Steps to Reproduce

1. Use the clarify tool from a Telegram gateway session with multiple choices.
2. Observe the inline keyboard.
3. Send a typed reply or transcribed voice reply instead of tapping a choice.

Expected Behavior

• The clarify message shows only clarify-specific choices, plus Other when appropriate.
• It does not show the generic busy-session /steer, /interrupt, /stop buttons.
• Typed and transcribed voice replies while the clarify is pending bypass busy queueing and resolve the clarify promptly.
• Slash commands such as /stop still bypass the active-session guard when deliberately issued.

Actual Behavior

• The clarify prompt includes /steer, /interrupt, and /stop buttons under the clarify choices.
• This presents the clarify wait as though the bot is paused/busy rather than actively listening for the user's answer.

Environment

• Gateway platform: Telegram
• Affected area: gateway/platforms/telegram.py clarify prompt rendering and active-session clarify bypass