openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@38ba27834d

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-28 03:26:25 +00:00
parent 2569863f92
commit 7be6d5c61a
3 changed files with 13 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "4b4cde71874f1140346456640b8913042e560661",
"syncedAt": "2026-04-28T03:17:32.906Z"
"sha": "38ba27834dd3f98c19d5833e0598dfef3abb7587",
"syncedAt": "2026-04-28T03:25:01.311Z"
}

13
docs/plugins/sdk-migration.md
View File

@ -89,10 +89,15 @@ For external plugins, compatibility work follows this order:
6. remove only after the announced migration window, usually in a major release
Maintainers can audit the current migration queue with
`pnpm plugins:boundary-report`. The report groups deprecated compatibility
records by removal date, counts local code/docs references, surfaces cross-owner
reserved SDK imports, and summarizes the private memory-host SDK bridge so
compatibility cleanup stays explicit instead of relying on ad hoc searches.
`pnpm plugins:boundary-report`. Use `pnpm plugins:boundary-report:summary` for
compact counts, `--owner <id>` for one plugin or compatibility owner, and
`pnpm plugins:boundary-report:ci` when a CI gate should fail on due
compatibility records, cross-owner reserved SDK imports, or unused reserved SDK
subpaths without a dormant classification. The report groups deprecated
compatibility records by removal date, counts local code/docs references,
surfaces cross-owner reserved SDK imports, classifies dormant reserved SDK
subpaths, and summarizes the private memory-host SDK bridge so compatibility
cleanup stays explicit instead of relying on ad hoc searches.
If a manifest field is still accepted, plugin authors can keep using it until
the docs and diagnostics say otherwise. New code should prefer the documented

3
docs/plugins/sdk-subpaths.md
View File

@ -10,7 +10,8 @@ The plugin SDK is exposed as a set of narrow subpaths under `openclaw/plugin-sdk
This page catalogs the commonly used subpaths grouped by purpose. The generated
full list of 200+ subpaths lives in `scripts/lib/plugin-sdk-entrypoints.json`;
reserved bundled-plugin helper subpaths appear there but are implementation
detail unless a doc page explicitly promotes them.
detail unless a doc page explicitly promotes them. Maintainers can audit active
and dormant reserved helper subpaths with `pnpm plugins:boundary-report:summary`.
For the plugin authoring guide, see [Plugin SDK overview](/plugins/sdk-overview).