openclaw - 💡(How to fix) Fix acp.fallbacks schema field missing from runtime — config rejects valid field from PR #69542

Bug Description

acp.fallbacks is documented and merged in PR #69542 (commit 1d4c929a — "feat(acp): add backend provider failover"), but the field is rejected by the runtime schema as an "Unrecognized key."

Expected vs Actual Behavior

Expected: acp.fallbacks should be accepted in openclaw.json as a valid top-level acp config array (e.g. acp.fallbacks: []).

Actual: openclaw config validate returns:

acp: Unrecognized key: "fallbacks"

Additionally, openclaw doctor --fix silently removes the fallbacks key if present in the config file.

Reproduction

1. Add \"acp\": { \"fallbacks\": [] } to openclaw.json
2. Run openclaw config validate → fails with "Unrecognized key: fallbacks"
3. Run openclaw doctor --fix → key is stripped from config

Evidence

• openclaw --version: OpenClaw 2026.5.12 (f066dd2)
• GitHub PR #69542 merged: May 12, 2026 (22:15 UTC)
• Runtime schema file runtime-schema-C9vXpfG_.js (built May 15 10:30 UTC, ~3 days post-merge): contains zero references to acp.fallbacks
• runtime-schema-C9vXpfG_.js does contain these ACP-related entries:

"acp.enabled"
"acp.backend"
"acp.defaultAgent"
"acp.allowedAgents"
"acp.maxConcurrentSessions"
"acp.runtime.ttlMinutes"
"acp.stream.*"

but no "acp.fallbacks" or "acp.fallbacks.*".

• PR #69542 changed 4 files:

  • src/config/schema.help.ts — adds "acp.fallbacks": "..."
  • src/config/types.acp.ts — adds fallbacks?: string[]
  • src/config/zod-schema.ts — adds fallbacks: z.array(z.string()).optional()
  • src/acp/control-plane/manager.core.ts — adds backend failover loop

• The schema help and type changes are absent from the built runtime-schema-C9vXpfG_.js, suggesting the schema build did not pick up the PR changes, or the dist was not regenerated post-merge.

Impact / Severity

• Medium: Feature is merged but unusable for users who upgrade to 2026.5.12. No graceful degradation possible since config rejects the field outright.
• Users cannot configure acp.fallbacks for ACP backend failover.

Suggested Fix

1. Confirm whether runtime-schema-C9vXpfG_.js needs to be regenerated post-PR merge
2. If schema is auto-built on release, verify the 2026.5.12 release build included PR #69542 changes
3. Alternatively: add acp.fallbacks to the schema and redeploy to the registry

Related

• PR #69542: "feat(acp): add backend provider failover for UNAVAILABLE errors"
• Commit: 1d4c929a (May 12, 2026 22:15 UTC)