fix(qqbot): accept is_reconnect kwarg in connect() to fix reconnection loop

[danbao]

Problem

The gateway reconnection watcher calls adapter.connect(is_reconnect=True) on failed platforms (gateway/run.py L3176), but QQAdapter.connect() does not accept this keyword argument. This causes every reconnect attempt to fail with:

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

The watcher retries with exponential backoff (60s → 120s → 240s → 300s) indefinitely, filling the log with errors.

Root Cause

QQAdapter.connect() (line 281) has signature async def connect(self) -> bool: — missing the is_reconnect parameter that BasePlatformAdapter.connect() defines and all other platform adapters implement:

Adapter	is_reconnect
base.py	✅
weixin.py	✅
signal.py	✅
api_server.py	✅
bluebubbles.py	✅
webhook.py	✅
whatsapp_cloud.py	✅
yuanbao.py	✅
msgraph_webhook.py	✅
qqbot	❌

Fix

One-line change: add *, is_reconnect: bool = False to match the base class contract.

# Before
async def connect(self) -> bool:

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

Verification

✓ qqbot connected
Gateway running with 3 platform(s)
[QQBot:1903051698] Ready, session_id=...

No more reconnection loop in gateway.log.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #52922 (the earliest open canonical fix for #52914). This PR makes the identical one-line is_reconnect signature fix to QQAdapter.connect(). Saturated fix cluster: #54029 / #53948 / #53546 / #52966 are also duplicates of #52922 for the same is_reconnect contract gap. Flagging for maintainer to pick the canonical PR to merge and close the rest.

[tonydwb]

Code Review Summary

Verdict: Approved

Adds is_reconnect keyword argument to QQAdapter.connect() to match the BasePlatformAdapter.connect contract. The gateway reconnect loop calls connect(is_reconnect=True) on every reconnect attempt, so every adapter must accept it. Without this fix, QQ reconnection raised TypeError: unexpected keyword argument 'is_reconnect'. Test verifies the signature accepts the kwarg and that the reconnect call path doesn't raise TypeError.

---

Reviewed by Hermes Agent

[scutken]

Encountered the same issue on v0.18.0 — QQ bot goes into infinite retry loop after any gateway restart with .

Applied this same one-line fix locally, restarted gateway, and QQ bot reconnects successfully. Can confirm this PR resolves the problem.

[teknium1]

Thanks for the focused QQBot reconnect fix. The exact behavior is already implemented on current main.

• Automated hermes-sweeper review verified QQAdapter.connect(self, *, is_reconnect: bool = False) at gateway/platforms/qqbot/adapter.py:281.
• Commit 276542c729c10ff9d093760897f4c2d1256a79ce added that signature and the regression coverage in tests/gateway/test_qqbot.py:193.
• The reconnect path still forwards is_reconnect=True at gateway/run.py:7910-7912, and the current QQBot test exercises that accepted keyword form.

This supersedes the duplicate fix cluster noted in the prior discussion.