diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 527aadf4f..3a91f87bf 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "ab0f8a79ca248155147e3a6b1cfa696094179b1e",
-  "syncedAt": "2026-05-03T16:45:25.953Z"
+  "sha": "7ea7f060389123381996716dab4ea1ef9f10a84f",
+  "syncedAt": "2026-05-03T16:56:20.927Z"
 }
diff --git a/docs/cli/update.md b/docs/cli/update.md
index db2affd06..12699c62b 100644
--- a/docs/cli/update.md
+++ b/docs/cli/update.md
@@ -103,10 +103,17 @@ explicit `openclaw completion --write-state` runs.
 When a local managed Gateway service is installed and restart is enabled,
 package-manager updates stop the running service before replacing the package
 tree, then refresh the service metadata from the updated install, restart the
-service, and verify the restarted Gateway reports the expected version. With
-`--no-restart`, package replacement still runs but the managed service is not
-stopped or restarted, so the running Gateway may keep old code until you restart
-it manually.
+service, and verify the restarted Gateway reports the expected version before
+reporting success. On macOS, the post-update check also verifies the LaunchAgent
+is loaded/running for the active profile and the configured loopback port is
+healthy. If the plist is installed but launchd is not supervising it, OpenClaw
+re-bootstraps and kickstarts the LaunchAgent automatically, then reruns the
+health/version/channel readiness checks. If the Gateway still does not become
+healthy, the command exits non-zero and prints the restart log path plus explicit
+restart, reinstall, and package rollback instructions. With `--no-restart`,
+package replacement still runs but the managed service is not stopped or
+restarted, so the running Gateway may keep old code until you restart it
+manually.
 
 ## Git checkout flow