Replay QA

pnpm qa replays scenario tool calls against a fresh DevSpace server, renders every card in a local MCP Apps host, and captures evidence with agent-browser.

Each run is isolated: its own HOME, config, SQLite state, worktree root, allowed root, and Git fixture under .devspace-dev/qa/runs/<timestamp>/<scenario>/. Ports are allocated dynamically, so runs never replace an existing process.

Run

pnpm qa --list                       # scenarios and descriptions
pnpm qa                              # every scenario
pnpm qa codex-edit-review            # one scenario
pnpm qa --theme dark codex-edit-review
pnpm qa --bare-host codex-edit-review   # host sends a theme but no style variables
pnpm qa --checkout ../other-worktree    # QA another checkout with this harness
pnpm qa --no-build ...                  # skip `pnpm build:app` in the target checkout

The exit code is non-zero when a step fails its expectations, a card does not initialize or render, or the page reports errors.

Each run directory contains:

• report.md: pass/fail per step, card state and height, failures, and screenshot paths. Read this first.
• transcript.json: the tool list, every request and response, UI resources, and calls the cards made back to the server.
• server.log: the DevSpace server's JSON log.
• artifacts/: a full-page screenshot, one screenshot per card, an accessibility snapshot, the browser console, and errors.json.

Look at the screenshots before reporting UI behavior. A passing report means that cards rendered, not that they look right.

Interact with cards