docs: clarify runtime migration boundary · openclaw/openclaw@c8f7e91
steipete
·
2026-05-31
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -64,6 +64,7 @@ Skills own workflows; root owns hard policy and routing.
|
64 | 64 | - Tests may use observed examples, but prod literals need a short contract reason. |
65 | 65 | - Compatibility is opt-in. "Shipped" means reachable from a release Git tag; main/GitHub/PR/unreleased code is not shipped. |
66 | 66 | - Refactor default: one canonical path. Delete the old path unless user explicitly wants compat or the shipped public contract is obvious and cited. |
| 67 | +- Core runtime consumes only current canonical shapes/config/data. Legacy or retired shapes normalize only in doctor/migration code before runtime; no runtime shims, aliases, or fallback readers. |
67 | 68 | - Keep old behavior only for an explicit public API/config/plugin SDK/data contract, tagged upgrade path, security/migration boundary, dependency contract, or observed prod state. |
68 | 69 | - If unsure, ask before preserving compat. Do not keep aliases, shims, fallback stacks, stale names, or obsolete tests just in case. |
69 | 70 | - Tests alone do not make internals contracts. If compat stays, name the contract and migration/removal plan in code, test, or PR. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
