fix: enforce requireMention setting for Feishu group chats

[yan-labs]

Problem

The bridge_feishu_require_mention setting exists in the config UI and is loaded from the database, but it was never actually checked in the message handling pipeline. This means the bot responds to all messages in group chats, even when "Require @mention" is enabled.

The Discord adapter correctly implements this check, but the Feishu adapter was missing the equivalent logic.

Changes

src/lib/channels/feishu/inbound.ts

• Added isBotMentioned() helper that checks message.mentions array for the bot's open_id
• When config.requireMention is true and the message is from a group chat (oc_ prefix), skip messages where the bot is not @mentioned
• Strip the @bot mention placeholder (e.g. @_user_1) from message text so the LLM receives clean input

src/lib/channels/feishu/index.ts

• Fetch bot identity via getBotInfo() after gateway starts, storing botOpenId
• Pass botOpenId to parseInboundMessage() for mention detection

How it works

Feishu includes a mentions array in im.message.receive_v1 events:

{
  "message": {
    "mentions": [
      { "key": "@_user_1", "id": { "open_id": "ou_xxx" }, "name": "MyBot" }
    ]
  }
}

The fix checks this array against the bot's open_id (fetched at startup) when requireMention is enabled.

Test plan

• Enable "Require @mention" in Feishu settings
• Send a message in a group chat without @mentioning the bot → bot should not respond
• Send a message in a group chat with @mention → bot should respond, and the @bot placeholder should be stripped from the input
• Send a DM → bot should respond regardless of the setting
• Disable "Require @mention" → bot should respond to all group messages again

[vercel]

@yan-labs is attempting to deploy a commit to the op7418's projects Team on Vercel.

A member of the Team first needs to authorize it.

[JiwaniZakir]

The race window in index.ts between gateway.start() and the completion of resolveBotIdentity() is a silent data-loss risk: any group messages arriving during that window will have this.botOpenId === '', causing findBotMention to return undefined, and the requireMention check in parseInboundMessage will then drop them unconditionally. The comment acknowledges the dynamic read but frames it as a feature rather than a hazard. A safer approach would be to buffer or re-queue messages that arrive before botOpenId is set, or to queue messages only after identity resolution completes.

The isGroupChat heuristic in inbound.ts — chatId.startsWith('oc_') — is an undocumented Feishu internal convention. If Feishu introduces additional group chat ID prefixes or changes this scheme, mention filtering silently breaks for those chats with no indication at the call site. A named constant or a comment linking to Feishu's API docs would make this less fragile.

In resolveBotIdentity, failed retries log a console.warn per attempt but the final console.error on total failure doesn't surface in any structured way — if an operator has requireMention: true and bot identity never resolves, the plugin initializes without error, silently discarding all group messages. Worth considering whether this condition should throw or set a flag that parseInboundMessage can distinguish from "bot identity known, not mentioned."