diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 682a10449..f3a88e178 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "61d53f98d314974b0ed1a88c45eeace603c05a59",
-  "syncedAt": "2026-04-29T15:55:29.593Z"
+  "sha": "8cf724a381a34532ad27fda4a1d9f852a73909ee",
+  "syncedAt": "2026-04-29T16:06:07.142Z"
 }
diff --git a/docs/plugins/sdk-setup.md b/docs/plugins/sdk-setup.md
index d7e8dde9e..6e86bd488 100644
--- a/docs/plugins/sdk-setup.md
+++ b/docs/plugins/sdk-setup.md
@@ -520,6 +520,8 @@ For npm-sourced installs, `openclaw plugins install` runs project-local `npm ins
 Bundled OpenClaw-owned plugins are the only startup repair exception: when a packaged install sees one enabled by plugin config, legacy channel config, or its bundled default-enabled manifest, startup installs that plugin's missing runtime dependencies before import. Third-party plugins should not rely on startup installs; keep using the explicit plugin installer.
 </Note>
 
+Bundled package-level runtime deps are explicit metadata, not inferred from built JavaScript at gateway startup. If a shared OpenClaw root dependency must be available inside the external bundled-plugin runtime mirror, declare it in `openclaw.bundle.mirroredRootRuntimeDependencies` in the root package manifest.
+
 ## Related
 
 - [Building plugins](/plugins/building-plugins) — step-by-step getting started guide