docs: clarify config migration policy

This commit is contained in:
Peter Steinberger
2026-05-25 08:20:36 +01:00
parent a8fc28c71a
commit c44367f1e5
2 changed files with 10 additions and 1 deletions

View File

@@ -38,6 +38,15 @@ Contribution rules:
- Do not open large batches of tiny PRs at once; each PR has review cost.
- For very small related fixes, grouping into one focused PR is encouraged.
Configuration compatibility:
OpenClaw runtime code reads the current configuration schema only.
We do not keep long-lived aliases or compatibility branches that silently accept old, renamed, or malformed config keys.
When a config change makes existing user config invalid, the same change needs a doctor migration.
`openclaw doctor --fix` should detect the old shape, explain it, back it up when needed, and rewrite it to the canonical format.
Core-owned config and auth state are repaired in core doctor code; plugin-owned config is repaired by that plugin's doctor contract.
## Security
Security in OpenClaw is a deliberate tradeoff: strong defaults without killing capability.