docs: clarify legacy compatibility policy · openclaw/openclaw@c6e6b31
steipete
·
2026-05-07
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -32,6 +32,7 @@ Telegraph style. Root rules only. Read scoped `AGENTS.md` before subtree work.
|
32 | 32 | - Owner boundary: fix owner-specific behavior in the owner module. Shared/core gets generic seams only; no owner ids, dependency strings, defaults, migrations, or recovery policy. If a bug names an extension or its dependency, start in that extension and add a generic core seam only when multiple owners need it. |
33 | 33 | - Dependency ownership follows runtime ownership: extension-only deps stay plugin-local; root deps only for core imports or intentionally internalized bundled plugin runtime. |
34 | 34 | - Legacy config repair: doctor/fix paths, not startup/load-time core migrations. |
| 35 | +- No legacy compatibility in core/runtime paths. When old config/store shapes need support, add an `openclaw doctor --fix` rewrite/repair rule with tests and keep runtime code on the canonical contract. |
35 | 36 | - Core test asserting extension-specific behavior: move to owner extension or generic contract test. |
36 | 37 | - New seams: backwards-compatible, documented, versioned. Third-party plugins exist. |
37 | 38 | - Channels: `src/channels/**` is implementation; plugin authors get SDK seams. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
