Bug Report: replyInThread config 'disabled' not working

Repo: openclaw/openclaw Title: replyInThread config 'disabled' not working - thread replies still sent

Description

When setting replyInThread: "disabled" in the Feishu channel account config, thread replies are still being sent. This causes @mention tags to be lost when bots reply with quote/reply format.

Environment

• OpenClaw version: 2026.4.26
• Channel: feishu
• Config: channels.feishu.accounts.<account>.replyInThread = "disabled"

Root Cause

In the Feishu send module (extensions/feishu/send-BjhQwBW9.js), the replyInThread parameter is checked with truthiness instead of explicit string comparison:

// Line ~790
...params.replyInThread ? { reply_in_thread: true } : {}

When replyInThread = "disabled", JavaScript treats the non-empty string as truthy, so reply_in_thread: true is still sent to the Feishu API. The correct check should be:

...params.replyInThread === "enabled" ? { reply_in_thread: true } : {}

Impact

• Bots cannot @ mention each other reliably in group chat when using quote/reply format
• The replyInThread: "disabled" config has no effect
• Only messages sent without replyToMessageId work correctly for @ mention forwarding

Expected Behavior

When replyInThread: "disabled" is set, the Feishu API should NOT receive reply_in_thread: true parameter.

Files Affected

• extensions/feishu/send-BjhQwBW9.js — sendReplyOrFallbackDirect function (line ~780-805)
• extensions/feishu/send-BjhQwBW9.js — image, file, media send functions (lines ~244-295, ~434-498)
• Any other location where replyInThread is used as a boolean flag

Suggested Fix

Replace all occurrences of:

...params.replyInThread ? { reply_in_thread: true } : {}

With:

...params.replyInThread === "enabled" ? { reply_in_thread: true } : {}