Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading to OpenClaw 2026.4.11, Gateway startup fails on a legacy Feishu account config that still uses botName, and openclaw doctor --fix does not migrate it to name.

Steps to reproduce

1. Keep an existing Feishu config under channels.feishu.accounts.main with appId, appSecret, and botName.
2. Upgrade OpenClaw to 2026.4.11.
3. Start Gateway or restart the OpenClaw Gateway scheduled task.
4. Observe: Config validation failed: channels.feishu.accounts.main: invalid config: must NOT have additional properties
5. Run openclaw doctor --fix.
6. Start Gateway again and observe the same validation failure.

Expected behavior

The existing Feishu config should keep working after upgrade, or openclaw doctor --fix should migrate channels.feishu.accounts.*.botName to name so Gateway can start successfully.

Actual behavior

Gateway startup fails with: Config validation failed: channels.feishu.accounts.main: invalid config: must NOT have additional properties. openclaw doctor --fix does not repair the legacy botName field. Manually changing botName to name makes openclaw config validate pass.

OpenClaw version

2026.4.11

Operating system

Windows 10 Home China, build 22631

Install method

Global CLI via Scoop-managed Node.js (openclaw.ps1 under D:\Programs\scoop\apps\nodejs\current\bin)

Model

Not reached; Gateway fails during config validation before model execution.

Provider / routing chain

Not reached; Gateway fails during config validation before provider routing is exercised.

Additional provider/model setup details

Not applicable for this repro. The failure happens during Gateway config validation before any model or provider request path is used.

Logs, screenshots, and evidence

Observed startup error:
Config validation failed: channels.feishu.accounts.main: invalid config: must NOT have additional properties

Relevant config shape before manual fix:
channels.feishu.defaultAccount = "main"
channels.feishu.accounts.main.appId = "<redacted>"
channels.feishu.accounts.main.appSecret = "${FEISHU_APP_SECRET}"
channels.feishu.accounts.main.botName = "..."

Manual workaround:
Rename channels.feishu.accounts.main.botName to channels.feishu.accounts.main.name

Verification after manual workaround:
openclaw config validate
=> Config valid: ~\.openclaw\openclaw.json

Impact and severity

Affected users/systems/channels: Existing Feishu channel setups upgraded to 2026.4.11 that still use the legacy botName field Severity: High (blocks Gateway startup) Frequency: Always in the observed setup until the config is manually edited Consequence: Gateway cannot start successfully, and users must manually inspect and repair config instead of relying on doctor --fix

Additional information

Last known good: the same config existed before upgrading to 2026.4.11 First known bad: 2026.4.11 Workaround: manually rename channels.feishu.accounts.*.botName to name

The changelog already mentions: "Docs/Feishu: replace botName with name in the channel config examples so the docs match the strict account schema for per-account display names."

This looks like a migration gap: the docs/schema changed, but doctor --fix does not migrate the older field.