docs: catch up with recent CLI changes (--workers, --junit, binaries)

- Parallel workers are now supported for web flows; Android still requires --workers 1
- Document the new --junit [path] flag and how it composites with console/JSON/agent output
- Add a precompiled binary install path alongside npm
- Rewrite the stale "workers capped at 1" troubleshooting entry to cover the Android constraint

Author: smonn

qawolf/libraries/cli/api-reference/commands.mdx

@@ -52,8 +52,9 @@ Options:
 
 - `--retries <n>` — number of retries for each failing flow. Default: `0`.
 - `--bail` — stop after the first failure. Default: `false`.
-- `--workers <n>` — parallel worker count. Default: `1`. Currently capped at `1`.
+- `--workers <n>` — parallel worker count for web flows. Default: `1`. Android flows must run with `--workers 1`; the CLI errors out if Android flows are selected with a higher value.
 - `--timeout <ms>` — per-flow timeout in milliseconds. Default: `30000`.
+- `--junit [path]` — write a JUnit XML report. With no value, writes to `<output-dir>/junit-report.xml`. Pass an explicit path to override.
 - `--video <mode>` — `on`, `off`, or `retain-on-failure`. Default: `off`.
 - `--trace <mode>` — Playwright trace mode. `on`, `off`, or `retain-on-failure`. Default: `off`.
 - `--har <mode>` — HAR capture mode. `on`, `off`, or `retain-on-failure`. Default: `off`.

qawolf/libraries/cli/troubleshooting.mdx

@@ -80,13 +80,14 @@ Check:
 - `@qawolf/testkit` is listed in `package.json` and installed
 - the command is being run from the project root, or from a directory inside a pulled environment
 
-## Parallel Worker Count Capped At 1
+## Android Flows Are Not Supported With `--workers > 1`
 
-Cause: `--workers <n>` was set to a value greater than `1`. Parallel workers are not yet supported.
+Cause: `--workers <n>` was set to a value greater than `1` and at least one Android flow was selected for the run.
 
 Check:
 
-- omit `--workers` or set it to `1`
+- rerun the Android flows with `--workers 1`
+- split the run into a web-only invocation with `--workers <n>` and an Android-only invocation with `--workers 1`
 
 ## Basic Target Flow Cannot Be Executed
 

qawolf/local-execution/authenticate.mdx

@@ -9,17 +9,23 @@ Before the CLI can pull flows from your workspace or run flows that depend on en
 
 ## Install the CLI
 
+The CLI ships in two forms: an npm package and a precompiled standalone binary.
+
+### Install with npm
+
 <Check>
   Node.js 24 or later is required.
 </Check>
 
-Install the CLI globally with npm:
-
 ```bash
 npm install -g @qawolf/cli
 ```
 
-Verify the install:
+### Install a precompiled binary
+
+Download the binary for your platform from [GitHub Releases](https://github.com/qawolf/cli/releases). Builds are published for Linux x64, macOS (Apple Silicon and Intel), and Windows x64. The binary has no Node.js runtime dependency. Extract the archive, then move the binary into a directory on your `PATH`.
+
+### Verify
 
 ```bash
 qawolf --version

qawolf/local-execution/run-flows-locally.mdx

@@ -90,6 +90,28 @@ qawolf flows run --env staging --bail
 
 `--bail` is useful when iterating on a single flow and you want to fail fast.
 
+## Run web flows in parallel
+
+```bash
+qawolf flows run --env staging --workers 4
+```
+
+`--workers` controls how many web flows run concurrently. Android flows must run with `--workers 1` — the CLI errors out if Android flows are selected with a higher value.
+
+## Write a JUnit XML report
+
+```bash
+qawolf flows run --env staging --junit
+```
+
+The CLI writes a JUnit XML report to `qawolf-output/junit-report.xml` (or under the directory set by `--output-dir`). Pass an explicit path to override the default:
+
+```bash
+qawolf flows run --env staging --junit ./reports/results.xml
+```
+
+The XML report is written alongside the console output and is independent of `--json` and `--agent`.
+
 ## Run flows you authored locally
 
 If you've scaffolded a [local-only project](/qawolf/local-execution/set-up-a-project) with `qawolf init`, run without `--env`:
@@ -106,7 +128,7 @@ The CLI discovers flows matching `**/*.flow.{ts,js}` in the current directory an
 
 ## Current limitations
 
-- `--workers` is capped at `1`. Parallel execution is on the roadmap.
+- Android flows must run with `--workers 1`. Parallel execution is supported for web flows only.
 - iOS flows are not executed. The CLI prints a clear error if an iOS flow is selected for a run.
 - Flows that target the legacy `"Basic"` platform pull successfully but cannot be executed by the CLI.
 - Dynamic-target flows — flows where `target` is a computed value rather than a string literal — are included in every run because the CLI cannot determine the platform ahead of time.