fix(qqbot): add missing is_reconnect parameter to QQAdapter.connect()

[LAN-TINA-WS]

Problem

QQ Bot connection enters an infinite failure loop. Every reconnect attempt crashes:

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

Root Cause

The Hermes gateway calls adapter.connect(is_reconnect=True) during reconnection. All platform adapters (Telegram, Discord, Slack, etc.) accept this parameter — but QQAdapter's connect() only accepted self, causing reconnection to fail permanently.

Fix

One line — add is_reconnect: bool = False to QQAdapter.connect() signature. Default value preserves existing behavior for initial connections.

Verification

• Gateway logs confirm QQ Bot now connects and reconnects successfully
• Session resume works correctly after server-initiated reconnect (op 7)

[alt-glitch]

This was generated by AI during triage.

Duplicate of #52966 — identical one-line fix adding the is_reconnect: bool = False parameter to QQAdapter.connect() in gateway/platforms/qqbot/adapter.py, which #52966 (the earliest still-open canonical fix for issue #52914) already implements. The earlier #52922 is closed/unmerged, so #52966 is the canonical open target. Part of a saturated fix cluster (#57105, #58607). Maintainer picks one to merge.

[needles-mybot]

Duplicate: already fixed on main in 4b873dc64 (QQAdapter.connect() missing is_reconnect param). Closing.

[teknium1]

Thanks for the focused reconnect fix. This 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.
• The reconnect path forwards that keyword at gateway/run.py:3500 and invokes it with True at gateway/run.py:8011-8013.
• Commit 276542c729c10ff9d093760897f4c2d1256a79ce added the implementation and the equivalent regression test at tests/gateway/test_qqbot.py:193-206.

The discussion correctly identified this as a duplicate/saturated fix cluster; the current-main fix is the verified resolution.