PR #60754: fix: prevent duplicate device repair requests for already-paired devices

• Repository: openclaw/openclaw
• Author: EronFan
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/60754

Description (problem / solution / changelog)

Summary

Fix issue #60747 where a stale repair request in blocks /RPC calls with 1008 pairing required.

Problem

When a device that is already paired attempts to connect, creates a new pending repair request even though the device is already paired. This creates stale entries in that can cause:

• and to fail with 1008 pairing required
• Unnecessary pending requests for already-paired devices
• Confusion in the pairing state management

Solution

When is called for an already-paired device and there is no existing pending request, we now return instead of creating a new pending repair request.

The message-handler now handles the status by proceeding with the connection without requiring additional pairing approval.

Changes

• : Added type with status, and modified to return this status when the device is already paired
• : Handle status by proceeding without requiring pairing approval

Testing

The existing test "preserves existing token scopes when approving a repair without requested scopes" tests the old behavior where a repair request was created for an already-paired device. This test will need to be updated to reflect the new behavior where no repair request is created for already-paired devices.

Changed files

• extensions/feishu/src/channel.ts (modified, +26/-23)
• src/gateway/server/ws-connection/message-handler.ts (modified, +4/-0)
• src/infra/device-pairing.ts (modified, +13/-6)
• src/infra/update-runner.ts (modified, +94/-0)
• src/infra/update-startup.ts (modified, +33/-1)