docs: add Matrix QA lane

docs/concepts/qa-e2e-automation.md

@@ -52,6 +52,18 @@ pnpm qa:lab:watch
 rebuilds that bundle on change, and the browser auto-reloads when the QA Lab
 asset hash changes.
 
+For a transport-real Matrix smoke lane, run:
+
+```bash
+pnpm openclaw qa matrix
+```
+
+That lane provisions a disposable Tuwunel homeserver in Docker, registers
+temporary driver and SUT users, creates one private room, then runs the real
+Matrix plugin inside a QA gateway child. The Matrix lane keeps `qa-channel`
+available in the child config for shared qa-lab helpers, but the transport
+under test is Matrix itself.
+
 For a disposable Linux VM lane without bringing Docker into the QA path, run:
 
 ```bash

docs/help/testing.md

@@ -65,6 +65,11 @@ These commands sit beside the main test suites when you need QA-lab realism:
     `.artifacts/qa-e2e/...`.
 - `pnpm qa:lab:up`
   - Starts the Docker-backed QA site for operator-style QA work.
+- `pnpm openclaw qa matrix`
+  - Runs the Matrix live QA lane against a disposable Docker-backed Tuwunel homeserver.
+  - Provisions two temporary Matrix users plus one private room, then starts a QA gateway child with the real Matrix plugin as the SUT transport.
+  - Uses the pinned stable Tuwunel image `ghcr.io/matrix-construct/tuwunel:v1.5.1` by default. Override with `OPENCLAW_QA_MATRIX_TUWUNEL_IMAGE` when you need to test a different image.
+  - Writes a Matrix QA report, summary, and observed-events artifact under `.artifacts/qa-e2e/...`.
 
 ## Test suites (what runs where)