hermes - 💡(How to fix) Fix Telegram busy-session interrupt buttons can disappear during long turns

Bug Description

Telegram gateway can lose visible busy-session controls (/steer, /interrupt, /stop) during long-running turns even when display.busy_buttons: true is configured.

This surfaced during a live Nagatha/Skippy web-automation workflow: after gateway restarts/config edits, Tyler observed the interrupt buttons were gone again while the agent was still doing tool work.

Expected Behavior

When a Telegram session is actively running tools or otherwise busy, the user should have visible interrupt controls attached to a current control/progress bubble:

• /steer
• /interrupt
• /stop

This should survive common live operations:

• gateway restart
• profile config edits unrelated to busy buttons
• tool progress / streaming / background process notification configuration changes

Actual Behavior

The controls disappear from the Telegram UX despite profile config still showing:

• display.busy_buttons: true
• display.busy_input_mode: queue
• display.tool_progress: all

Evidence / Context

Local profile checks showed busy buttons enabled for Nagatha and Skippy, but Telegram did not show controls. Launchd also reported stale/non-zero status for ai.hermes.gateway-nagatha while a gateway process was still running, suggesting state/process supervision may contribute.

Notes

This may be fork/live-branch drift or a bypass path where busy controls are only attached to some tool-progress surfaces. The issue should be tested against origin/main with a fake Telegram adapter/harness that starts a long tool turn and verifies reply_markup contains the busy-session control row throughout the turn.