diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index d782c7e1d..ec01edee4 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "aa9db998f7bfb4785e47ba766a749a93691b9c0a",
-  "syncedAt": "2026-04-30T21:15:45.650Z"
+  "sha": "231e5c618f8ae700d51d080e4182a57588da888b",
+  "syncedAt": "2026-04-30T21:54:58.505Z"
 }
diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md
index f876f172c..4fba316f3 100644
--- a/docs/reference/RELEASING.md
+++ b/docs/reference/RELEASING.md
@@ -194,7 +194,9 @@ Validation` or from the `main`/release workflow ref so workflow logic and
     `openclaw/releases-private/.github/workflows/openclaw-npm-dist-tags.yml`
     for security, because `npm dist-tag add` still needs `NPM_TOKEN` while the
     public repo keeps OIDC-only publish
-  - public `macOS Release` is validation-only
+  - public `macOS Release` is validation-only; when a tag lives only on a
+    release branch but the workflow is dispatched from `main`, set
+    `public_release_branch=release/YYYY.M.D`
   - real private mac publish must pass successful private mac
     `preflight_run_id` and `validate_run_id`
   - the real publish paths promote prepared artifacts instead of rebuilding