diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 7a69b42a0..c717651bc 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "fb80405693ca1931e06b6f710b0c3d0f4e497eec",
-  "syncedAt": "2026-04-24T23:58:04.498Z"
+  "sha": "e625651de82f2c3bea33e7b47f2817b38ad78650",
+  "syncedAt": "2026-04-24T23:58:33.720Z"
 }
diff --git a/docs/plugins/manifest.md b/docs/plugins/manifest.md
index e7d757462..1cca08c99 100644
--- a/docs/plugins/manifest.md
+++ b/docs/plugins/manifest.md
@@ -335,6 +335,11 @@ adapter during the deprecation window, but non-bundled plugins that still use it
 receive a manifest diagnostic. New plugins should put setup/status env metadata
 on `setup.providers[].envVars`.
 
+OpenClaw can also derive simple setup choices from `setup.providers[].authMethods`
+when no setup entry is available, or when `setup.requiresRuntime: false`
+declares setup runtime unnecessary. Explicit `providerAuthChoices` entries stay
+preferred for custom labels, CLI flags, onboarding scope, and assistant metadata.
+
 Set `requiresRuntime: false` only when those descriptors are sufficient for the
 setup surface. OpenClaw treats explicit `false` as a descriptor-only contract
 and will not execute `setup-api` or `openclaw.setupEntry` for setup lookup. If