diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 3ace6af21..474049fcf 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "d40dd9088ee2708c15968dcaf5d5ce1e7b9fe6d3",
-  "syncedAt": "2026-04-23T21:22:44.880Z"
+  "sha": "e64da8bde04b7f3ae6c482e0a5b05478a6461dbe",
+  "syncedAt": "2026-04-23T21:47:30.523Z"
 }
diff --git a/docs/ci.md b/docs/ci.md
index 8de995cbc..d49c99b7c 100644
--- a/docs/ci.md
+++ b/docs/ci.md
@@ -28,12 +28,14 @@ for slow tests. It has no pure schedule: a successful non-bot push CI run on
 `main` can trigger it, but it skips if another workflow-run invocation already
 ran or is running that UTC day. Manual dispatch bypasses that daily activity
 gate. The lane builds a full-suite grouped Vitest performance report, lets Codex
-make only small coverage-preserving test performance fixes, then reruns the
-full-suite report and rejects changes that reduce the passing baseline test
-count. If the baseline has failing tests, Codex may fix only obvious failures
-and the after-agent full-suite report must pass before anything is committed.
-It uses GitHub-hosted Ubuntu so the Codex action can keep the same drop-sudo
-safety posture as the docs agent.
+make only small coverage-preserving test performance fixes instead of broad
+refactors, then reruns the full-suite report and rejects changes that reduce the
+passing baseline test count. If the baseline has failing tests, Codex may fix
+only obvious failures and the after-agent full-suite report must pass before
+anything is committed. When `main` advances before the bot push lands, the lane
+rebases the validated patch, reruns `pnpm check:changed`, and retries the push;
+conflicting stale patches are skipped. It uses GitHub-hosted Ubuntu so the Codex
+action can keep the same drop-sudo safety posture as the docs agent.
 
 ```bash
 gh workflow run duplicate-after-merge.yml \
diff --git a/docs/reference/test.md b/docs/reference/test.md
index 8a10f69d6..07e692117 100644
--- a/docs/reference/test.md
+++ b/docs/reference/test.md
@@ -20,7 +20,7 @@ title: "Tests"
 - `auto-reply` now also splits into three dedicated configs (`core`, `top-level`, `reply`) so the reply harness does not dominate the lighter top-level status/token/helper tests.
 - Base Vitest config now defaults to `pool: "threads"` and `isolate: false`, with the shared non-isolated runner enabled across the repo configs.
 - `pnpm test:channels` runs `vitest.channels.config.ts`.
-- `pnpm test:extensions` and `pnpm test extensions` run all extension/plugin shards. Heavy channel extensions and OpenAI run as dedicated shards; other extension groups stay batched. Use `pnpm test extensions/<id>` for one bundled plugin lane.
+- `pnpm test:extensions` and `pnpm test extensions` run all extension/plugin shards. Heavy channel plugins, the browser plugin, and OpenAI run as dedicated shards; other plugin groups stay batched. Use `pnpm test extensions/<id>` for one bundled plugin lane.
 - `pnpm test:perf:imports`: enables Vitest import-duration + import-breakdown reporting, while still using scoped lane routing for explicit file/directory targets.
 - `pnpm test:perf:imports:changed`: same import profiling, but only for files changed since `origin/main`.
 - `pnpm test:perf:changed:bench -- --ref <git-ref>` benchmarks the routed changed-mode path against the native root-project run for the same committed git diff.