hermes - 💡(How to fix) Fix QQ send path can fail during unrelated platform imports when running outside Hermes venv

Bug Description

Sending a QQBot message can fail before reaching the QQ send logic because the shared send path imports unrelated platform code eagerly.

In practice, if Hermes is invoked outside the main Hermes venv (or otherwise without all optional platform dependencies installed), a missing dependency from some other platform can abort the send path even when the requested delivery target is QQ/QQBot.

This makes QQ sending fragile and couples it to optional dependencies for unrelated platforms.

Steps to Reproduce

1. Have Hermes installed with QQBot configured and working in the normal environment.
2. Run Hermes or a Hermes-driven script from an environment outside the main Hermes venv, so one or more optional dependencies for unrelated platforms are unavailable.
3. Attempt to send a message to QQ / QQBot.
4. Observe that the send path fails during import / setup of another platform before the QQ send logic is reached.

Expected Behavior

• Sending to QQ / QQBot should only require the dependencies needed for the QQ path.
• Unrelated platform adapters should be imported lazily (or failures should be isolated) so that missing optional deps for another platform do not break QQ delivery.

Actual Behavior

• The shared send path can fail early because unrelated platform code is imported eagerly.
• QQ sending never gets a chance to execute.

Why this matters

Hermes supports many optional platforms. A single missing optional dependency should not make an unrelated delivery target unusable.

Possible Fix

• Lazily import platform adapters only when that platform is actually selected, or
• catch and isolate optional platform import failures so they do not poison unrelated send paths.

Environment

• Repo: NousResearch/hermes-agent
• Platform involved: qqbot
• Scenario: running outside the main Hermes venv / missing optional dependencies for unrelated platforms