@app-studio/qa-cli
v0.5.0
Published
The qa command: the layered run, the doctor, adoption, hardened end-to-end orchestration, seeding and the ratchets.
Readme
@app-studio/qa-cli
One command surface for humans and agents.
qa state validate
qa state list
qa state inspect --id <id>
qa state run --id <id> [--mode mock|live]
qa design record --file <acceptance.json> --reviewer <designer-id>
qa design validate [--feature <key>]
qa design list
qa scenario validate
qa scenario list
qa scenario coverage
qa scenario run --id <id> [--mode mock|live] [--engine <name>] [--profile fast|proof|record]
qa scenario run [--mode mock|live] # complete release-candidate portfolio
qa scenario benchmark --id <id> [--engines chromium,lightpanda] [--runs 5]Validation reads the canonical artifacts. Runtime commands resolve the host command from qa.bindings.json and pass the selected ID through environment variables. Named engines select application-owned commands; capability declarations stop a DOM-only engine from being used for visual proof or video. fast emits a verdict without checkpoint media, proof is the default release evidence, and record enables video-oriented diagnostics. The CLI does not maintain a copied catalogue or a second browser implementation.
Use qa run --list to inspect the progressive proof layers and qa run --from <layer> only after lower layers are known green.
