Summary

Fix parseInteractiveCardContent() to handle Feishu API post-format fallback content for interactive card messages.

Fixes openclaw#60380
Related: openclaw#41609 openclaw#48281

Problem

When reading card messages via GET /im/v1/messages/{message_id}, Feishu returns body.content in a post-style fallback format — nested arrays with tag:"text" elements — instead of the original card template JSON. The existing parser only handled card template format (div/markdown tags), causing all fallback content to silently return "[Interactive Card]".

Before: Any message(action=read) on a card → "[Interactive Card]"
After: Extracts title + text content from both card template and post-format fallback

Example

API returns this for a card message:

{
  "title": "🤖 clawdbot",
  "elements": [[
    {"tag": "img", "image_key": "img_v3_02ad_..."},
    {"tag": "text", "text": "Daily report summary"},
    {"tag": "text", "text": "13 people missing reports"}
  ]]
}

• Before: "[Interactive Card]"
• After: "🤖 clawdbot\nDaily report summary\n13 people missing reports"

Changes

extensions/feishu/src/send.ts

• Handle nested arrays in elements (post-format fallback [[...]])
• Extract tag:"text" and tag:"a" elements from fallback content
• Extract card title from header.title.content (template) or top-level title (fallback)
• Support tag:"plain_text" elements
• Return title even when elements array is missing

extensions/feishu/src/send.test.ts

• Add test: post-format fallback with nested arrays and title
• Add test: card template with header.title.content
• Add test: link extraction from tag:"a" elements with href

Testing

• Verified with real Feishu API responses from production bot
• Existing card template format tests still pass (div/markdown)
• 3 new test cases covering fallback scenarios