fix(qqbot): accept is_reconnect kwarg in QQAdapter.connect()

[qiyin-code]

Problem

QQAdapter.connect() was defined without the is_reconnect keyword argument:

async def connect(self) -> bool:

But the gateway calls it with is_reconnect (in _connect_adapter_with_timeout, gateway/run.py:3395):

return await adapter.connect(is_reconnect=is_reconnect)

Every other platform adapter (base.py, signal.py, webhook.py, yuanbao.py, msgraph_webhook.py, api_server.py, bluebubbles.py, whatsapp_cloud.py, weixin.py) accepts this parameter:

async def connect(self, *, is_reconnect: bool = False) -> bool:

This causes a TypeError on every connection attempt:

QQAdapter.connect() got an unexpected keyword argument 'is_reconnect'

The QQ bot can never connect — every reconnect attempt (every 5 min by the watcher) fails with the same error. The adapter enters a retry loop that can never succeed.

Fix

Add *, is_reconnect: bool = False to QQAdapter.connect(), matching the BasePlatformAdapter.connect() contract. The parameter is accepted but not yet used internally (the QQ adapter does not currently differentiate cold boot from reconnect), which is the same approach other adapters take when they accept the kwarg without acting on it.

Reproduction

1. Configure a QQ bot with valid QQ_APP_ID and QQ_CLIENT_SECRET
2. Start the gateway: hermes gateway run --replace
3. Observe the error in gateway_state.json:

   "qqbot": {
     "state": "retrying",
     "error_message": "QQAdapter.connect() got an unexpected keyword argument 'is_reconnect'"
   }

4. Logs show endless retry loop (every 300s) with the same TypeError

Test Plan

• QQ bot connects successfully after this change
• gateway_state.json shows qqbot.state: "connected" after gateway start
• No regression in other platform adapters (they already accept this kwarg)

[alt-glitch]

This was generated by AI during triage.

Duplicate of #52966 (the earliest still-open canonical fix for #52914). This is the identical one-line is_reconnect signature fix as the saturated QQBot cluster; verified the fix is not yet on main (gateway/platforms/qqbot/adapter.py still has the bare async def connect(self)). Prior anchor #52922 is closed/unmerged, so #52966 is canonical.

[teknium1]

Thanks for the focused QQBot reconnect fix. This is an automated hermes-sweeper review; the same behavioral fix is already on current main.

• gateway/platforms/qqbot/adapter.py:281 now defines connect(self, *, is_reconnect: bool = False).
• tests/gateway/test_qqbot.py:193 covers both the default and explicit reconnect call forms.
• The implementation landed in 276542c729c10ff9d093760897f4c2d1256a79ce (fix(qqbot): add is_reconnect param to QQAdapter.connect for gateway reconnect compat).
• This also aligns with the earlier discussion pointing to the canonical QQ reconnect fix; the current code and regression coverage satisfy this PR's request.