Bug Description

When an agent calls message(action="send", message="Title Text", card={...}), channels that support interactive cards (e.g., Feishu/Lark) send two messages to the user:

1. A plain text message with the message param content
2. The interactive card

The user sees a duplicate — the text message appears immediately before the card, and both contain the same title.

Root Cause

The message (text) parameter is passed through to channel plugins alongside the card parameter without any normalization. Channel plugins like Feishu/Lark see both text and card are non-empty and send them as separate messages, because Feishu msg_type=interactive (card) does not support inline text content.

The message param has dual semantics:

• Without card: message body text (correct behavior: send as text)
• With card: LLMs use it as notification preview / card title (incorrect behavior: sent as separate text message)

Steps to Reproduce

1. Configure a Feishu/Lark channel
2. In an isolated cron job or agent session, call:

   message(action="send", channel="feishu", target="user:ou_xxx", 
           message="Daily Report", 
           card={"header":{"title":{"tag":"plain_text","content":"Daily Report"}},"elements":[...]})

3. User receives TWO messages: "Daily Report" as text + the card

Expected Behavior

Only the card should be sent. The message param should be treated as notification metadata (push notification preview), not as a standalone text message.

Proposed Fix

Add card-aware parameter normalization in the core message tool dispatcher (src/infra/outbound/message-action-runner.ts), before args are passed to channel plugins:

// When card is present, clear message/text to prevent duplicate sends.
// Preserve as _cardNotificationHint for push notification previews.
if (args.card != null && typeof args.card === "object") {
  if (args.message) {
    args._cardNotificationHint = args.message;
    delete args.message;
  }
  if (args.text) {
    args._cardNotificationHint ??= args.text;
    delete args.text;
  }
}

Why fix in core, not plugins:

1. All card-capable channels benefit (Feishu, Teams, Slack, Discord)
2. Single enforcement point — no per-plugin fixes needed
3. LLM behavior is unpredictable — prompt-level fixes ("pass empty message") are unreliable
4. Cleaner plugin contract — plugins can trust that card presence means no separate text

Workaround

Plugin-level fix: in the channel plugin deliverMessage, skip text send when card is present. This has been verified working for Feishu/Lark but needs to be applied to each plugin independently.

Environment

• OpenClaw version: latest (2026.5.x)
• Channel: Feishu/Lark (openclaw-lark extension)
• Trigger: cron jobs with message(action=send) tool calls using card param