[Bug]: Docs: Feishu channel docs still use botName, but current config schema only accepts name #52718
Description
Bug type
Regression (worked before, now fails)
Summary
Summary
The Feishu channel documentation still shows botName in config examples, but the current implementation only accepts name for per-account display names.
This makes the docs misleading, especially for multi-account setup.
What I found
The current Feishu account config schema only accepts name and uses .strict():
extensions/feishu/src/config-schema.ts
Relevant part:
export const FeishuAccountConfigSchema = z
.object({
enabled: z.boolean().optional(),
name: z.string().optional(),
appId: z.string().optional(),
appSecret: buildSecretInputSchema().optional(),
...
})
.strict();
### Steps to reproduce
configure the openclaw.config as
~~~json
"channels": {
"feishu": {
"defaultAccount":"FinanceAssistant",
"typingIndicator": false,
"resolveSenderNames": false,
"domain": "feishu",
"accounts":{
"FinanceAssistant":{
"appId": "xxx",xx
"appSecret": "xxxxx",
"botName":"FinanceAssistant",
"typingIndicator":true,
"groupPolicy": "open"
},
"MailAssistant":{
"appId": "xxxxx",
"appSecret": "xxxx8",
"botName":"MailAssistant",
"typingIndicator":true,
"groupPolicy": "open"
}
}
}
}
~~~
### Expected behavior
update the section of Feishu at :Advanced configuration - > Multiple accounts
<img width="1476" height="1146" alt="Image" src="https://github.com/user-attachments/assets/2e07caf4-4dbe-4429-b6df-f73e0e4cc88c" />
### Actual behavior
<img width="1476" height="1146" alt="Image" src="https://github.com/user-attachments/assets/3c2799bc-9326-436f-838e-7a9ca74ccf9a" />
### OpenClaw version
2026.3.23
### Operating system
All
### Install method
_No response_
### Model
not related
### Provider / routing chain
not related
### Additional provider/model setup details
_No response_
### Logs, screenshots, and evidence
```shellImpact and severity
No response
Additional information
No response