hermes - 💡(How to fix) Fix [Feature] Add config option to suppress fallback/rate-limit status messages from gateway channel

Problem Hermes currently sends internal lifecycle status messages (e.g. ⚠️ Rate limited — switching to fallback provider..., ⚠️ Empty/malformed response — switching to fallback...) directly through the gateway status callback. This floods the main chat with technical debugging noise that users don't want to see.

The fallback logic itself works fine — only the messaging to the user channel is too verbose. There's no existing config option to suppress these lifecycle/status messages selectively.

Desired behavior Add a config key under logging: (e.g. logging.status_suppression: true or logging.suppress_fallback_notifications: true) that:

Still allows fallback to other providers when rate-limited / connection errors occur (no change to logic) Suppresses the _emit_status() calls for rate-limit and fallback messages from being sent to the gateway channel Optionally still writes those messages to the gateway log for debugging, but keeps them out of the chat UI Leaves other status messages (errors, warnings, tool failures) visible by default — this is specifically about internal fallback chain messages

Current state No config only workaround exists The messages come from _emit_status() in run_agent.py and are forwarded via status_callback("lifecycle", ...) to the gateway Users see technical rate-limit/fallback messages in every channel every time these occur Patches to run_agent.py break on updates

Impact For production/gateway users this is the primary source of noisy "technical debug" messages. Users who actually want this visibility can check the gateway log anyway. A simple logging.status_suppression: true toggle would solve this cleanly.