diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 75b5ff6c5..bdd381720 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "3b347d1c7ea05e2dc8ec90eb2193849350a1fdfd",
-  "syncedAt": "2026-05-02T18:51:48.440Z"
+  "sha": "a7a6d241473a38b57bf3d470f7925c0ecf8ac20c",
+  "syncedAt": "2026-05-02T18:59:49.675Z"
 }
diff --git a/docs/cli/plugins.md b/docs/cli/plugins.md
index 814fffcd9..7a22d8ba3 100644
--- a/docs/cli/plugins.md
+++ b/docs/cli/plugins.md
@@ -237,11 +237,17 @@ openclaw plugins search <query> --json
   Switch from the table view to per-plugin detail lines with source/origin/version/activation metadata.
 </ParamField>
 <ParamField path="--json" type="boolean">
-  Machine-readable inventory plus registry diagnostics.
+  Machine-readable inventory plus registry diagnostics and package dependency install state.
 </ParamField>
 
 <Note>
 `plugins list` reads the persisted local plugin registry first, with a manifest-only derived fallback when the registry is missing or invalid. It is useful for checking whether a plugin is installed, enabled, and visible to cold startup planning, but it is not a live runtime probe of an already-running Gateway process. After changing plugin code, enablement, hook policy, or `plugins.load.paths`, restart the Gateway that serves the channel before expecting new `register(api)` code or hooks to run. For remote/container deployments, verify you are restarting the actual `openclaw gateway run` child, not only a wrapper process.
+
+`plugins list --json` includes each plugin's `dependencyStatus` from `package.json`
+`dependencies` and `optionalDependencies`. OpenClaw checks whether those package
+names are present along the plugin's normal Node `node_modules` lookup path; it
+does not import plugin runtime code, run a package manager, or repair missing
+dependencies.
 </Note>
 
 `plugins search` is a remote ClawHub catalog lookup. It does not inspect local
diff --git a/docs/tools/plugin.md b/docs/tools/plugin.md
index 599f66d1b..4f450366e 100644
--- a/docs/tools/plugin.md
+++ b/docs/tools/plugin.md
@@ -120,6 +120,8 @@ installed under OpenClaw's managed plugin roots. npm dependencies may be hoisted
 within OpenClaw's managed npm root; install/update scans that managed root before
 trust and uninstall removes npm-managed packages through npm. External plugins
 and custom load paths must still be installed through `openclaw plugins install`.
+Use `openclaw plugins list --json` to see the static `dependencyStatus` for each
+visible plugin without importing runtime code or repairing dependencies.
 See [Plugin dependency resolution](/plugins/dependency-resolution) for the
 install-time lifecycle.