fix(lark): link feedback cards to persisted messages#447
Open
glow-Kev1n wants to merge 1 commit into
Open
Conversation
glow-Kev1n
marked this pull request as ready for review
July 23, 2026 15:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
chat.recordFeedbackmessage_idcompatibleRoot cause
Feishu feedback cards previously carried only the session and CardKit card ID. That was sufficient to identify the card, but not to unambiguously correlate an older card with its persisted assistant turn.
message_refremains the card aggregation and re-vote idempotency key. The newmessage_idis used only for the exact chat-message link.The field is optional on callbacks and RPC requests so cards created by older Runtime versions remain compatible.
Validation
npx vitest run src/gateway/channels/lark-card.test.ts src/gateway/channels/lark.test.ts— 144 tests passednpm run build— passedBoth checks ran on the development host with Node.js 22.22.3.