diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index dceefa75b..b104d85bd 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "0335a8783ca94a890927032b45fdc0e20be0fd89",
-  "syncedAt": "2026-04-06T16:34:47.945Z"
+  "sha": "b4e1747391c74fead9cd1657bdbb366382ea5f22",
+  "syncedAt": "2026-04-06T16:48:47.307Z"
 }
diff --git a/docs/channels/qa-channel.md b/docs/channels/qa-channel.md
index c62ef42da..1ed0f3618 100644
--- a/docs/channels/qa-channel.md
+++ b/docs/channels/qa-channel.md
@@ -75,10 +75,13 @@ self-check, and writes a Markdown report under `.artifacts/qa-e2e/`.
 Private debugger UI:
 
 ```bash
-pnpm qa:lab:build
-pnpm openclaw qa ui
+pnpm qa:lab:up
 ```
 
+That one command builds the QA site, starts the Docker-backed gateway + QA Lab
+stack, and prints the QA Lab URL. From that site you can pick scenarios, choose
+the model lane, launch individual runs, and watch results live.
+
 Full repo-backed QA suite:
 
 ```bash
@@ -96,10 +99,10 @@ Current scope is intentionally narrow:
 - threaded routing grammar
 - channel-owned message actions
 - Markdown reporting
+- Docker-backed QA site with run controls
 
 Follow-up work will add:
 
-- Dockerized OpenClaw orchestration
 - provider/model matrix execution
 - richer scenario discovery
 - OpenClaw-native orchestration later
diff --git a/docs/concepts/qa-e2e-automation.md b/docs/concepts/qa-e2e-automation.md
index f60aba5a2..23642cb35 100644
--- a/docs/concepts/qa-e2e-automation.md
+++ b/docs/concepts/qa-e2e-automation.md
@@ -21,13 +21,21 @@ Current pieces:
 - `qa/`: repo-backed seed assets for the kickoff task and baseline QA
   scenarios.
 
-The long-term goal is a two-pane QA site:
+The current QA operator flow is a two-pane QA site:
 
 - Left: Gateway dashboard (Control UI) with the agent.
 - Right: QA Lab, showing the Slack-ish transcript and scenario plan.
 
-That lets an operator or automation loop give the agent a QA mission, observe
-real channel behavior, and record what worked, failed, or stayed blocked.
+Run it with:
+
+```bash
+pnpm qa:lab:up
+```
+
+That builds the QA site, starts the Docker-backed gateway lane, and exposes the
+QA Lab page where an operator or automation loop can give the agent a QA
+mission, observe real channel behavior, and record what worked, failed, or
+stayed blocked.
 
 ## Repo-backed seeds
 
diff --git a/docs/help/testing.md b/docs/help/testing.md
index 8d456b499..36cac632c 100644
--- a/docs/help/testing.md
+++ b/docs/help/testing.md
@@ -26,6 +26,7 @@ Most days:
 - Faster local full-suite run on a roomy machine: `pnpm test:max`
 - Direct Vitest watch loop: `pnpm test:watch`
 - Direct file targeting now routes extension/channel paths too: `pnpm test extensions/discord/src/monitor/message-handler.preflight.test.ts`
+- Docker-backed QA site: `pnpm qa:lab:up`
 
 When you touch tests or want extra confidence: