hermes - 💡(How to fix) Fix Improve Feishu startup diagnostics when lark-oapi is missing

Bug Description

When Feishu is configured, the gateway can still start with No adapter available for feishu if the lark-oapi dependency is missing. The only visible clue is a warning like Feishu: lark-oapi not installed or FEISHU_APP_ID/SECRET not set, which makes the failure look like a config problem instead of a missing runtime dependency.

Related to #21653, but this issue is specifically about startup diagnostics and actionable guidance.

Steps to Reproduce

1. Configure Feishu credentials / enable the Feishu adapter.
2. Start the gateway without lark-oapi installed in the environment.
3. Observe the gateway log output.

Expected Behavior

The gateway should surface a clear error that Feishu is configured but lark-oapi is missing, and ideally point to the installation / upgrade step required to fix it.

Actual Behavior

The gateway logs a generic warning and reports No adapter available for feishu, which makes diagnosis slower.

Affected Component

• Gateway (Telegram/Discord/Slack/WhatsApp)
• Configuration / startup diagnostics
• Feishu platform adapter

Debug Report

Not available from the forwarded conversation. Relevant log excerpts were:

• Feishu: lark-oapi not installed or FEISHU_APP_ID/SECRET not set
• No adapter available for feishu

Operating System

macOS 26.3.1

Python Version

3.11.13

Hermes Version

Hermes Agent v0.13.0 (2026.5.7)

Additional Logs / Traceback

The gateway only connected after lark-oapi was installed and the gateway was restarted.

Root Cause Analysis

The runtime dependency check appears to conflate a missing package with a missing config signal, which makes the startup failure too ambiguous.