fix(feishu): use open_message_id for card action reply instead of token

[wlknight]

When a Feishu interactive card button is clicked, the agent fails to send a reply with: 'Invalid ids: [c-...]'. The root cause is that _handle_card_action_event() sets message_id to the card action token (format c-xxx), but the Feishu ReplyMessage API requires an open_message_id (format om_xxx).

P2CardActionTriggerData.CallBackContext already provides the open_message_id field, but the adapter only extracted open_chat_id from it while ignoring open_message_id.

Two-line fix:

1. Extract open_message_id from CallBackContext
2. Prefer open_message_id as message_id (fall back to token/uuid)

What does this PR do?

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform:

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

[alt-glitch]

This was generated by AI during triage.

Related: #6422 (same open_message_id approach) and #43609 (sets message_id=None) both target gateway/platforms/feishu.py, which has been relocated to plugins/platforms/feishu/adapter.py (the old core path no longer exists on main). This PR patches the live plugin path directly (the buggy message_id=token or uuid is still on main at line ~2896), so it is the version aligned with current code. Broader #43048 fixes this plus two other card-action bugs. Flagging the cluster so a maintainer can pick.

[teknium1]

Thanks for targeting the live Feishu plugin path. The defect remains on current main: plugins/platforms/feishu/adapter.py:3009 places the card callback token in MessageEvent.message_id; gateway/platforms/base.py:107 then uses that value as the reply anchor, and plugins/platforms/feishu/adapter.py:4613-4621 sends it to Feishu's reply endpoint.

Problems

• The PR has no regression test. The shared callback fixture at tests/gateway/test_feishu_approval_buttons.py:57-74 exposes only open_chat_id, and TestNonApprovalCardAction.test_routes_as_synthetic_command at lines 417-438 never asserts the emitted event ID.

Suggested changes

• Add open_message_id to the fixture and assert that a non-approval card action uses it as MessageEvent.message_id; retain fallback coverage for absent context IDs.

Automated hermes-sweeper review.

[teknium1]

Please add focused coverage for this path: provide context.open_message_id in the card-action fixture and assert that the dispatched synthetic event uses it as message_id. The existing non-approval card-action test only checks the generated text.