Problem

When Hermes runs terminal commands, the Feishu client shows "Command Approval Required". Clicking "Allow once", "Always", or "Deny" all result in error code 200340. The card action callback is not properly handled.

This is a high-frequency recurring issue with multiple attempted fixes:

• fix(feishu): approval card not updating after button click — use PATCH instead of PUT NousResearch/hermes-agent#9533: "use PATCH instead of PUT"
• fix(feishu): approval card never updates — use im.v1.message.patch instead of update NousResearch/hermes-agent#8847: "use im.v1.message.patch instead of update"
• Feishu command approval card buttons fail with error code 200340 NousResearch/hermes-agent#10251, [Bug]: Feishu approval card fails to update after button click (error 200340) NousResearch/hermes-agent#10154, [Bug]: Feishu Card Interactive Button Error: Code 200340 - No card.action Callback Received & Severe Response Timeout NousResearch/hermes-agent#8764, [Bug] Error code 200340 when approving dangerous commands via Feishu/Lark gateway NousResearch/hermes-agent#6893, [Bug]: 飞书中进行审核，出现200340错误 NousResearch/hermes-agent#8246 all report the same issue

Root Cause

The approval card is created as an interactive message but updated using the wrong API:

• Should use: im.v1.message.patch (message patch, not card update)
• Card action callback routing in _handle_card_action_event() is also incorrect

Reference

Upstream fixes:

• fix(feishu): approval card not updating after button click — use PATCH instead of PUT NousResearch/hermes-agent#9533 (closed, not merged)
• fix(feishu): approval card never updates — use im.v1.message.patch instead of update NousResearch/hermes-agent#8847 (closed, not merged)

OpenClaw design:

• card-interaction.ts: Structured envelope with version ocf1
• card-ux-approval.ts: Complete approval UX lifecycle
• Uses FeishuStreamingSession for real-time card updates

Implementation Plan

1. Fix _resolve_approval() in gateway/platforms/feishu.py to use PATCH message API
2. Ensure card action callback extracts message_id correctly from event context
3. Verify the card update_id is properly passed for deduplication
4. Test with actual Feishu approval flow