openclaw - 💡(How to fix) Fix [Feature]: [Feishu] Card header/footer customization: hide agent label, show elapsed time & completion status, support reply-to context [1 participants]

{
  channels: {
    feishu: {
      cardHeader: {
        mode: "reply-to" | "custom" | "hidden",
        customTitle: "My Bot"
      }
    }
  }
}
2. Card footer: wire up elapsed/status and allow hiding developer metadata
Actually render footer.elapsed and footer.status (already accepted by schema). Add toggles for each footer element:
{
  channels: {
    feishu: {
      footer: {
        elapsed: true,
        status: true,
        agent: false,
        model: false,
        provider: false
      }
    }
  }
}
3. Allow hiding header/footer entirely
{
  channels: {
    feishu: {
      cardHeader: { mode: "hidden" },
      footer: { enabled: false }
    }
  }
}
**Alternatives considered：**
Switch to renderMode: "text" to avoid header/footer entirely, but this loses card markdown formatting (tables, code blocks, etc.)
Manually patch the bundled JS to modify card rendering, but this breaks on every upgrade

### Alternatives considered

_No response_

### Impact

Affected: All Feishu DM and group chat users using card renderMode
Severity: Medium — does not block workflow but degrades daily UX
Frequency: Every single message — the useless header/footer appears on 100% of card replies
Consequence: Card header ("main") wastes space with no user value; footer shows developer metadata (Agent/Model/Provider) instead of actionable info like elapsed time and completion status. Users cannot distinguish which message is being replied to in long conversations. The existing footer.elapsed and footer.status config keys are silently ignored despite passing schema validation, creating a false sense of configurability.

### Evidence/examples

 Config `channels.feishu.footer.elapsed: true` and `channels.feishu.footer.status: true` pass `openclaw doctor` validation on v2026.4.2 but have zero rendering effect in the actual Feishu card
- Related issue: #56882 (footer config rejected by schema in older versions — now accepted but still not rendered)
- Comparable: Telegram and Discord channels show elapsed time; Feishu card mode does not
- Screenshot of current card showing static "main" header and "Agent: main | Model | Provider" footer attached

### Additional information

OpenClaw v2026.4.2, Feishu built-in plugin, renderMode: card, streaming: false
- Must remain backward-compatible with existing config keys
- Ideally the reply-to header mode could reuse the existing Feishu message reply_in_thread / root_id metadata already available in the inbound event payload