fix(qqbot): accept gateway reconnect flag

[lordlink01]

Summary

• update QQBot adapter to accept the gateway's connect(is_reconnect=...) keyword argument
• document that QQBot manages resume vs identify internally and can ignore the flag
• add a regression test that calls QQAdapter.connect(is_reconnect=True)

Why

GatewayRunner now forwards is_reconnect through _connect_adapter_with_timeout() to every adapter. QQBot still exposed connect(self), so gateway startup/reconnect failed before it could open the QQ websocket:

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

Test Plan

• python3 -m pytest tests/gateway/test_qqbot.py::TestVoiceAttachmentSSRFProtection::test_connect_accepts_gateway_reconnect_flag -q -o 'addopts='
• python3 -m pytest tests/gateway/test_qqbot.py -q -o 'addopts='

[alt-glitch]

This was generated by AI during triage.

Duplicate of #52966 — identical one-line fix adding the keyword-only is_reconnect: bool = False parameter to QQAdapter.connect() (same function, same regression test). #52966 is the earliest still-open canonical fix for issue #52914 (the prior anchor #52922 is closed). This is a saturated cluster of byte-equivalent fixes for the same v0.17.0 reconnect regression.

[tonydwb]

Code Review Summary

Verdict: Approved

Changes

Updates QQAdapter.connect() to accept is_reconnect: bool = False keyword argument for compatibility with the gateway's common PlatformAdapter.connect() contract. QQBot manages resume vs. cold identify internally from stored session state. Also adds a dedicated regression test.

Quality

• Clean contract alignment: matches the base class signature
• Well-documented with docstring explaining how QQBot handles the flag internally
• Regression test covers the exact call pattern gateway.run uses

Suggestions

• None

---

Reviewed by Hermes Agent

[tonydwb]

Code Review

COMMENT: fix(qqbot): accept gateway reconnect flag

Small fix (21 additions, 2 deletions). No security concerns.

---

Reviewed by Hermes Agent

[yangguo]

I hit the same regression on a live Hermes gateway with QQBot enabled after updating to current origin/main (88a58ff13). The gateway process stayed up, but QQBot stayed in retrying state with:

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

The local gateway state showed Telegram/Discord connected while QQBot remained retrying with that error.

I independently tested the same minimal fix locally and this PR is the cleaner version of it: QQBot accepts the gateway reconnect kwarg without changing its QQ auth/WebSocket behavior.

Additional local validation I ran:

scripts/run_tests.sh tests/gateway/test_qqbot.py -q
# 165 passed

scripts/run_tests.sh tests/gateway/test_platform_reconnect.py tests/gateway/relay/test_relay_adapter.py -q
# 52 passed

.venv/bin/python -m ruff check gateway/platforms/qqbot/adapter.py tests/gateway/test_qqbot.py
# All checks passed

I opened a duplicate PR while debugging (#61356) and closed it in favor of this one.

[lordlink01]

The official reconnect-contract fix has now landed via #61767, which includes the QQBot regression fix and repository-wide adapter contract coverage. Closing this duplicate now that upstream main contains the fix. Thank you.