diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 6857d6da8..24ce72630 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "d6eac07b066b0ba9d9d4cf8fdcb0c2058104120a",
-  "syncedAt": "2026-04-23T00:10:21.986Z"
+  "sha": "0946e37523f93f1c2d0c93fb6682d3e74495e547",
+  "syncedAt": "2026-04-23T00:23:51.751Z"
 }
diff --git a/docs/cli/plugins.md b/docs/cli/plugins.md
index b292be325..7c164e578 100644
--- a/docs/cli/plugins.md
+++ b/docs/cli/plugins.md
@@ -243,6 +243,15 @@ or exact version. OpenClaw resolves that package name back to the tracked plugin
 record, updates that installed plugin, and records the new npm spec for future
 id-based updates.
 
+Passing the npm package name without a version or tag also resolves back to the
+tracked plugin record. Use this when a plugin was pinned to an exact version and
+you want to move it back to the registry's default release line.
+
+Before a live npm update, OpenClaw checks the installed package version against
+the npm registry metadata. If the installed version and recorded artifact
+identity already match the resolved target, the update is skipped without
+downloading, reinstalling, or rewriting `openclaw.json`.
+
 When a stored integrity hash exists and the fetched artifact hash changes,
 OpenClaw treats that as npm artifact drift. The interactive
 `openclaw plugins update` command prints the expected and actual hashes and asks