diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index bfa6254c4..c2509f082 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "e2c8db2cad406b00e37a2b60e7767ad6232fbf3a",
-  "syncedAt": "2026-05-03T15:25:51.054Z"
+  "sha": "59c523c6b530224f55a5c00baca761563a180e4a",
+  "syncedAt": "2026-05-03T15:50:12.340Z"
 }
diff --git a/docs/tools/plugin.md b/docs/tools/plugin.md
index 6cb1f0cb4..084957383 100644
--- a/docs/tools/plugin.md
+++ b/docs/tools/plugin.md
@@ -161,6 +161,9 @@ Native plugin npm packages must declare `openclaw.extensions` in `package.json`.
 Each entry must stay inside the package directory and resolve to a readable
 runtime file, or to a TypeScript source file with an inferred built JavaScript
 peer such as `src/index.ts` to `dist/index.js`.
+Packaged installs must ship that JavaScript runtime output. The TypeScript
+source fallback is for source checkouts and local development paths, not for
+npm packages installed into OpenClaw's managed plugin root.
 
 Use `openclaw.runtimeExtensions` when published runtime files do not live at the
 same paths as the source entries. When present, `runtimeExtensions` must contain