From 13b75347d2cf3ceae778120102646573ec638969 Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Mon, 13 Apr 2026 02:42:16 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@20266c14cbca8cfbc35b9aa46d2701cab710f76e --- .openclaw-sync/source.json | 4 ++-- docs/concepts/qa-e2e-automation.md | 5 +++++ 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 86f4c23e9..d3dd9e182 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "403783a3b12fb621949ea35df5d0d9e77f3c7f2e", - "syncedAt": "2026-04-12T22:41:55.093Z" + "sha": "20266c14cbca8cfbc35b9aa46d2701cab710f76e", + "syncedAt": "2026-04-13T02:42:15.721Z" } diff --git a/docs/concepts/qa-e2e-automation.md b/docs/concepts/qa-e2e-automation.md index 35a9434ec..16c3ba241 100644 --- a/docs/concepts/qa-e2e-automation.md +++ b/docs/concepts/qa-e2e-automation.md @@ -131,6 +131,11 @@ the source of truth for one test run and should define: - optional gateway config patch - the executable `qa-flow` +The reusable runtime surface that backs `qa-flow` is allowed to stay generic +and cross-cutting. For example, markdown scenarios can combine transport-side +helpers with browser-side helpers that drive the embedded Control UI through the +Gateway `browser.request` seam without adding a special-case runner. + The baseline list should stay broad enough to cover: - DM and channel chat