diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 230b0bb08..1a5b95c4f 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "ae616777f3b185d7e12da4e1dac999bf0ace8bb5",
-  "syncedAt": "2026-04-28T03:11:54.887Z"
+  "sha": "00e30ba8d90f5398f11688bef3e317ef15b0cf90",
+  "syncedAt": "2026-04-28T03:13:34.985Z"
 }
diff --git a/docs/plugins/sdk-migration.md b/docs/plugins/sdk-migration.md
index de64c2dd8..894290b6f 100644
--- a/docs/plugins/sdk-migration.md
+++ b/docs/plugins/sdk-migration.md
@@ -88,6 +88,12 @@ For external plugins, compatibility work follows this order:
 5. document the deprecation and migration path
 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.
+
 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
 replacement, but existing plugins should not break during ordinary minor