docs: clarify plugin externalization guidance · openclaw/openclaw@6257130
steipete
·
2026-05-14
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -33,7 +33,7 @@ Skills own workflows; root owns hard policy and routing.
|
33 | 33 | - Dependency ownership follows runtime ownership: plugin-only deps stay plugin-local; root deps only for core imports or intentionally internalized bundled plugin runtime. |
34 | 34 | - Internal bundled plugins ship in core dist; bundled-only facade loader ok only for them. |
35 | 35 | - External official plugins own package/deps and are excluded from core dist; core uses registry-aware `facade-runtime` or generic contracts. |
36 | | -- Moving external: update package excludes, official catalogs, docs, tests, and prove core runtime paths resolve installed plugin roots before root-dep removal. |
| 36 | +- Externalizing a bundled plugin: update package excludes, official catalogs, docs, tests, and prove core runtime paths resolve installed plugin roots before root-dep removal. |
37 | 37 | - Legacy config repair belongs in `openclaw doctor --fix`, not startup/load-time core migrations. Runtime paths use canonical contracts. |
38 | 38 | - New seams: backward-compatible, documented, versioned. Third-party plugins exist. |
39 | 39 | - Channels are implementation under `src/channels/**`; plugin authors get SDK seams. Providers own auth/catalog/runtime hooks; core owns generic loop. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
