From 7be6d5c61ac4164ab6fff46f876aba97bc63eb09 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Tue, 28 Apr 2026 03:26:25 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@38ba27834dd3f98c19d5833e0598dfef3abb7587 --- .openclaw-sync/source.json | 4 ++-- docs/plugins/sdk-migration.md | 13 +++++++++---- docs/plugins/sdk-subpaths.md | 3 ++- 3 files changed, 13 insertions(+), 7 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 257b4eba2..e12953a78 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -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" } diff --git a/docs/plugins/sdk-migration.md b/docs/plugins/sdk-migration.md index 894290b6f..415d3e8c7 100644 --- a/docs/plugins/sdk-migration.md +++ b/docs/plugins/sdk-migration.md @@ -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 ` 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 diff --git a/docs/plugins/sdk-subpaths.md b/docs/plugins/sdk-subpaths.md index e06062d54..e27d47900 100644 --- a/docs/plugins/sdk-subpaths.md +++ b/docs/plugins/sdk-subpaths.md @@ -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).