docs: clarify multipass live auth support

This commit is contained in:
Shakker
2026-04-09 00:34:20 +01:00
committed by Shakker
parent 445fe55331
commit 655cfb477a
2 changed files with 13 additions and 5 deletions

View File

@@ -59,10 +59,13 @@ pnpm openclaw qa suite --runner multipass --scenario channel-chat-baseline
```
This boots a fresh Multipass guest, installs dependencies, builds OpenClaw
inside the guest, runs `qa suite` on the mock-openai lane, then copies the
normal QA report and summary back into `.artifacts/qa-e2e/...` on the host.
It reuses the same scenario-selection behavior as `qa suite` on the host and
only changes where that suite runs.
inside the guest, runs `qa suite`, then copies the normal QA report and
summary back into `.artifacts/qa-e2e/...` on the host.
It reuses the same scenario-selection behavior as `qa suite` on the host.
Live runs forward the supported QA auth inputs that are practical for the
guest: env-based provider keys, the QA live provider config path, and
`CODEX_HOME` when present. Keep `--output-dir` under the repo root so the guest
can write back through the mounted workspace.
## Repo-backed seeds

View File

@@ -51,7 +51,12 @@ These commands sit beside the main test suites when you need QA-lab realism:
- `pnpm openclaw qa suite --runner multipass`
- Runs the same QA suite inside a disposable Multipass Linux VM.
- Keeps the same scenario-selection behavior as `qa suite` on the host.
- Reuses the same provider/model selection flags as `qa suite`; the runner only changes where the suite executes.
- Reuses the same provider/model selection flags as `qa suite`.
- Live runs forward the supported QA auth inputs that are practical for the guest:
env-based provider keys, the QA live provider config path, and `CODEX_HOME`
when present.
- Output dirs must stay under the repo root so the guest can write back through
the mounted workspace.
- Writes the normal QA report + summary plus Multipass logs under
`.artifacts/qa-e2e/...`.
- `pnpm qa:lab:up`