Summary

• stop send_weixin_direct() from reusing a live Weixin adapter across event loops
• force one-shot Weixin sends to use an isolated aiohttp.ClientSession
• add a regression test covering cross-loop direct-send safety

Why

Cron delivery and other one-shot messaging paths can call send_weixin_direct() outside the gateway's main event loop. Reusing a live Weixin adapter from those paths can cross event-loop boundaries and trigger aiohttp task/timeout errors instead of delivering the message.

Root cause

send_weixin_direct() preferred _LIVE_ADAPTERS[resolved_token] whenever a live adapter and _send_session existed. That live adapter's aiohttp session is created inside the gateway event loop, but one-shot delivery helpers may execute from another loop or thread. Reusing the live adapter directly in that context can raise errors such as:

• Timeout context manager should be used inside a task

Behavior before

• cron / one-shot Weixin delivery could try to reuse a live adapter bound to another event loop
• delivery could fail with aiohttp timeout/task-context errors

Behavior after

• send_weixin_direct() no longer reuses a live adapter across loops
• one-shot delivery uses an isolated session instead
• live gateway operation remains unchanged for normal in-loop sends

How to test

• source venv/bin/activate && python -m pytest tests/gateway/test_weixin.py -q
• with the gateway running and a Weixin target configured, trigger cron or one-shot delivery and confirm it no longer fails with Timeout context manager should be used inside a task

Platforms tested

• Linux (local Hermes development environment on omarchy)

Notes

• This PR is intentionally scoped to event-loop safety for one-shot Weixin delivery helpers.
• It takes the low-risk approach of avoiding cross-loop live-adapter reuse instead of adding more complex loop-handoff logic.