feat(gateway/feishu): render markdown tables via interactive card

[eaglewa]

Summary

Feishu post / lark_md elements cannot render GFM markdown tables — the
message arrives blank on the client. _build_outbound_payload therefore
downgraded any table content to plain text, losing the table formatting.

The interactive-card markdown component (card schema 2.0) does render
tables, so this routes table content to an interactive card instead. Non-table
content is unchanged:

• markdown (headings/bold/lists/code) → post (renders fine today)
• plain text → text
• table content → interactive card 2.0 markdown (new)

send() falls back to plain text if a card payload is rejected by the API, so
a malformed card can never drop the message.

Tests

tests/gateway/test_feishu_card_rendering.py:

• table content → interactive card 2.0 markdown (content preserved verbatim)
• a table embedded in surrounding prose still routes to a card
• non-table markdown still routes to post (unchanged)
• plain text stays text (unchanged)

[alt-glitch]

Duplicate of #12114 (canonical Feishu markdown table rendering PR). This is part of the 70+ PR cluster tracked by #27469. Competing with open PRs #32455, #31038, #23494, and others. Please check #27469 for consolidation status before proceeding.

[teknium1]

Thanks for the focused table-rendering contribution. The underlying issue remains: current main routes detected tables to plain text at plugins/platforms/feishu/adapter.py:4524-4533.

Problems

• The patch changes gateway/platforms/feishu.py, but 5600105478ffde29d7566b45421b100eaa29c4ef moved the active adapter to plugins/platforms/feishu/adapter.py; this needs a port rather than a direct merge.
• The new interactive exception fallback does not cover unsuccessful API responses: the adjacent response fallback remains restricted to msg_type == "post" at plugins/platforms/feishu/adapter.py:1924-1936.
• edit_message() also consumes _build_outbound_payload() (plugins/platforms/feishu/adapter.py:1958), but its fallback is post-only at :1963-1971.

Suggested changes

• Port the implementation and tests to the bundled plugin path.
• Cover interactive send exceptions, unsuccessful responses, and edit rejection with plain-text fallback tests.

Automated hermes-sweeper review.

[teknium1]

This handles exceptions, but the response-based fallback immediately below remains limited to msg_type == "post". If Feishu rejects an interactive card by returning an unsuccessful response rather than raising, send() still returns failure; extend that guard and add coverage for this response path.