Feature Request

Problem:
When the gateway emits lifecycle warnings (e.g. memorySearch failed, provider init failures), they are posted to whichever Discord channel is currently active. This creates noise in conversation channels unrelated to system health.

Example:
After a gateway restart, the Gemini embedding provider takes ~30s to initialise. Any memory_search call during this window fails and the gateway posts ⚠️ 🔌 Gateway: memorySearch failed directly into the user's active conversation channel.

Proposed solution:
Add a config option to route gateway lifecycle warnings to a dedicated channel:

{
  "messages": {
    "lifecycleTarget": "channel:1234567890"
  }
}

This would allow users to route all gateway health/warning messages to a dedicated channel (e.g. #troubleshooting) rather than polluting active conversation channels.

Alternatives considered:

• Suppressing warnings entirely (not ideal — useful for debugging)
• Per-channel suppression flags (more complex than needed)

Environment: Windows 10, OpenClaw v2026.3.12, Discord channel plugin