Document/support same-card completion re-notification for CardKit streaming

Feature request

Please document or support a CardKit agent pattern for completion notification without sending a new message.

Problem

Agent integrations often render long-running replies as Feishu/Lark CardKit streaming cards. The final state is shown by updating the existing card to Completed / 已完成. Because this is an in-place update, a user who switched away may miss that the task finished.

The desired pattern is not to send a follow-up text message. The desired pattern is to re-push / refresh the completed state on the same CardKit card/message.

Desired pattern

1. Create/reply with a CardKit streaming card.
2. Update it while the agent is working.
3. Complete/close the card so it shows Completed / 已完成.
4. Optionally, after a short delay, update the same card's status/header/footer again to the completed state.
5. Do not send a separate message.
6. Do not duplicate the answer content.

Requested improvement

Either would be useful:

Option A — lark-cli helper / example

Provide a documented example for same-message CardKit completion re-notification:

• which CardKit endpoint should be used after completion;
• whether updating header/status/footer on a completed card is supported;
• any timing/sequence constraints;
• how to preserve the original message/card identity and topic/thread context.

Option B — agent skill guidance

Add guidance to lark-cli's agent skills explaining:

• when this pattern is appropriate for long-running agent responses;
• why a new chat message is not desired;
• how to re-update the same completed card safely;
• how to avoid duplicate/noisy re-notifications;
• what API errors mean the card can no longer be updated.

Expected invariant

The user should see only one CardKit message in the chat. Completion re-notification, if enabled, should be implemented as an update to that existing CardKit card/message, not as a new ordinary message.

Downstream use case

Hermes Agent CardKit streaming replies in Feishu/Lark: after a long response finishes, the card already says 已完成, but it would be useful to refresh/re-push that completed state once so the user notices completion without adding chat clutter.

Start by locating the CardKit streaming update implementation and the lark-cli agent skills that cover agent responses. Check the available post-completion CardKit operations, identity and timing constraints, then document or support a same-card refresh that preserves one message and avoids duplicate content.