diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 40bccaeb9..b44f98522 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "9b397b414a1bde7633fa04283adbe5bc523d3a69",
-  "syncedAt": "2026-05-04T01:14:13.601Z"
+  "sha": "a04d9060d3b3a6e9234824aed130e90f48d55122",
+  "syncedAt": "2026-05-04T01:22:33.701Z"
 }
diff --git a/docs/concepts/mantis.md b/docs/concepts/mantis.md
index 49826a33c..8c0602e9b 100644
--- a/docs/concepts/mantis.md
+++ b/docs/concepts/mantis.md
@@ -123,7 +123,9 @@ worktrees, runs `discord-status-reactions-tool-only` against each worktree, and
 uploads `baseline/`, `candidate/`, `comparison.json`, and `mantis-report.md` as
 Actions artifacts. It also renders each lane's timeline HTML in a Crabbox
 desktop browser and publishes those VNC screenshots beside the deterministic
-timeline PNGs in the PR comment.
+timeline PNGs in the PR comment. The workflow builds the Crabbox CLI from
+`openclaw/crabbox` main so it can use the current desktop/browser lease flags
+before the next Crabbox binary release is cut.
 
 You can also trigger the status-reactions run directly from a PR comment: