diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 0f0d2a008..fb4cfc940 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "2aaac45c07d4d36baca6d9826f95391c8ca31c20",
-  "syncedAt": "2026-04-22T19:37:22.550Z"
+  "sha": "8fcca8a5e1bad8a690f046bac6c564fe5b85d409",
+  "syncedAt": "2026-04-22T19:40:38.992Z"
 }
diff --git a/docs/ci.md b/docs/ci.md
index ea3478cc2..33feda793 100644
--- a/docs/ci.md
+++ b/docs/ci.md
@@ -56,7 +56,7 @@ On pushes, the `checks` matrix adds the push-only `compat-node22` lane. On pull
 The slowest Node test families are split or balanced so each job stays small: channel contracts split registry and core coverage into eight weighted shards each, auto-reply reply tests split by prefix group, and agentic gateway/plugin configs are spread across the existing source-only agentic Node jobs instead of waiting on built artifacts. `check-additional` keeps package-boundary compile/canary work together and separates it from runtime topology gateway/architecture work; the boundary guard shard runs its small independent guards concurrently inside one job, and the gateway watch regression uses the minimal `gatewayWatch` build profile instead of rebuilding the full CI artifact sidecar set.
 
 GitHub may mark superseded jobs as `cancelled` when a newer push lands on the same PR or `main` ref. Treat that as CI noise unless the newest run for the same ref is also failing. Aggregate shard checks use `!cancelled() && always()` so they still report normal shard failures but do not queue after the whole workflow has already been superseded.
-The CI concurrency key is versioned (`CI-v3-*`) so a GitHub-side zombie in an old queue group cannot indefinitely block newer main runs.
+The CI concurrency key is versioned (`CI-v4-*`) so a GitHub-side zombie in an old queue group cannot indefinitely block newer main runs.
 
 ## Runners