qaa-agent 1.9.6 → 1.9.7

package/CHANGELOG.md

@@ -3,6 +3,20 @@
 
 All notable changes to QAA (QA Automation Agent) are documented here.
 
+## [1.9.7] - 2026-07-29
+
+### Added
+
+- **Pre-flight checks with UX-friendly error messages across all 10 commands** — every slash command now runs guard checks before its main flow and, on failure, prints a clear, actionable error: a one-line title, a short explanation, two or three concrete options, and a `Try:` command. Coverage includes invalid `--dev-repo`/source paths, missing required MCP servers (Playwright for `/qa-audit`, `/qa-testid`, `/qa-create-test` from-aut and `/qa-fix --run`; Context7 for `/qa-research`; Azure DevOps for `/qa-create-test-ado` and `/qa-test-report`), undetectable frameworks, non-git repositories, and a missing/unauthenticated GitHub CLI. Required-dependency failures STOP; optional-enhancement failures (e.g. live DOM verification) WARN and continue in degraded mode. Every suggested flag is validated against what the command actually accepts.
+
+### Fixed
+
+- **Installer now syncs `workflows/` to the live location** — `install.cjs` Step 4 mirrors `workflows/qa-*.md` into `<claudeDir>/workflows/` alongside commands and agents, using the same scope-aware sync. Commands reference workflows via `@workflows/qa-*.md`; syncing them makes that resolution direct instead of a fallback runtime search, on every install (global or local).
+
+### Documentation
+
+- **QAA_SYSTEM_OVERVIEW.md refreshed for the current system state** — the Installation section now documents the four installer steps, including the live sync of commands, agents, workflows, and CLAUDE.md to the locations Claude Code loads from.
+
 ## [1.9.6] - 2026-07-14
 
 ### Added

package/VERSION

@@ -1 +1 @@
-1.9.6
+1.9.7

package/bin/install.cjs

@@ -1,4 +1,4 @@
-#!/usr/bin/env node
+#!/usr/bin/env node
 
 /**
  * QAA Agent Installer
@@ -320,8 +320,10 @@ async function main() {
   //
   // Claude Code loads slash commands from <claudeDir>/commands, sub-agents from
   // <claudeDir>/agents, and global standards from <claudeDir>/CLAUDE.md — NOT
-  // from the qaa/ install dir. Mirror QAA files there so new versions activate.
-  // Only QAA-owned files (qa*.md / qaa-*.md) are touched.
+  // from the qaa/ install dir. Commands also reference workflows via
+  // @workflows/qa-*.md; mirroring workflows to <claudeDir>/workflows makes that
+  // resolution direct instead of a fragile runtime search. Mirror QAA files
+  // there so new versions activate. Only QAA-owned files (qa*.md) are touched.
 
   console.log('');
 
@@ -344,6 +346,14 @@ async function main() {
   success(`${tag}Live agents → ${path.join(claudeDir, 'agents')} (${agentSync.copied.length} synced${agentSync.pruned.length ? `, ${agentSync.pruned.length} pruned` : ''})`);
   if (agentSync.pruned.length) log(`${tag}Pruned: ${agentSync.pruned.join(', ')}`);
 
+  const workflowSync = syncLive(
+    path.join(installDir, 'workflows'),
+    path.join(claudeDir, 'workflows'),
+    qaMatch, dryRun
+  );
+  success(`${tag}Live workflows → ${path.join(claudeDir, 'workflows')} (${workflowSync.copied.length} synced${workflowSync.pruned.length ? `, ${workflowSync.pruned.length} pruned` : ''})`);
+  if (workflowSync.pruned.length) log(`${tag}Pruned: ${workflowSync.pruned.join(', ')}`);
+
   const cmd = syncClaudeMd(installDir, claudeDir, dryRun, pkgVersion);
   if (cmd.action === 'created')              success(`${tag}CLAUDE.md created (QAA markers) → ${path.join(claudeDir, 'CLAUDE.md')}`);
   else if (cmd.action === 'updated-section') success(`${tag}CLAUDE.md QAA section updated → ${path.join(claudeDir, 'CLAUDE.md')}`);
@@ -359,7 +369,7 @@ async function main() {
   console.log('');
   if (dryRun) log('Dry-run complete — nothing was written.');
   log(`${totalFiles} files installed to ${installDir}`);
-  log(`Live commands & agents synced to ${claudeDir}`);
+  log(`Live commands, agents & workflows synced to ${claudeDir}`);
   log('MCP servers: playwright, context7');
   log('');
   log('Restart Claude Code, then run any QAA command:');

package/commands/qa-audit.md

@@ -103,6 +103,43 @@ APP_URL=$(echo "$RESOLVED" | node -e "const j=JSON.parse(require('fs').readFileS
 
 If you see values you didn't intend in the banner above (interactive mode), you can press Ctrl-C and re-run with explicit flags.
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. A **[STOP]** check that fails: print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP. A **[WARN]** check that fails: print the notice and continue in degraded mode.
+
+### Dev-repo path does not exist — --dev-repo given [STOP]
+If `--dev-repo` was passed (coverage cross-reference) but the path does not exist:
+```
+❌ Dev-repo path not found: {path}
+
+You passed --dev-repo for coverage cross-reference, but that path does not exist
+(or is not a directory).
+
+Options:
+  1. Re-run with a correct path: /qa-audit <tests> --dev-repo <path>
+  2. Drop --dev-repo to audit the test suite without coverage cross-reference
+  3. Check for a typo or an unexpanded ~ in the path
+
+Try: ls {path}
+```
+
+### Playwright MCP not connected — --app-url given [WARN]
+If `--app-url` was passed (live locator verification) but Playwright MCP is unavailable:
+```
+❌ Playwright MCP is not connected — live locator verification will be skipped.
+
+You passed --app-url so /qa-audit can check test locators against the real DOM
+via Playwright MCP. It isn't available, so that check can't run — the rest of
+the audit still proceeds.
+
+Options:
+  1. Connect Playwright MCP (ships with QAA — check ~/.claude.json), then re-run for full verification
+  2. Reinstall to re-register the MCP servers: npx qaa-agent
+  3. Continue now with static scoring only (no live DOM verification)
+
+Try: /mcp
+```
+
 ## Instructions
 
 ### AUDIT MODE (default)

package/commands/qa-create-test-ado.md

@@ -64,6 +64,53 @@ links, or passing XML steps — STOP and restart from step 1.
 
 ---
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. If a **[STOP]** check fails, print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP.
+
+### Azure DevOps MCP not connected [STOP]
+If the ADO MCP tools (`wit_get_work_item`, `testplan_create_test_case`) are unavailable:
+```
+❌ Azure DevOps MCP is not connected — this command can't reach ADO.
+
+/qa-create-test-ado reads a work item and creates Test Cases directly in Azure
+DevOps via the ADO MCP tools. They aren't available in this session.
+
+Options:
+  1. Connect the Azure DevOps MCP server, then re-run
+  2. Verify it's configured in your Claude Code MCP settings
+  3. If you only need local test files (not ADO Test Cases), use /qa-create-test instead
+
+Try: /mcp   (to see connected MCP servers)
+```
+
+### Work item ID missing or not found [STOP]
+- If NO work item ID was provided, print:
+```
+❌ No work item ID provided.
+
+/qa-create-test-ado needs an Azure DevOps work item ID (Bug, User Story, or
+Ticket) to read from.
+
+Options:
+  1. Pass one: /qa-create-test-ado <work-item-id>
+  2. Copy the numeric ID from the work item's ADO URL
+  3. If you only need local test files (not ADO Test Cases), use /qa-create-test instead
+
+Try: /qa-create-test-ado 85508   (example)
+```
+- If an ID WAS provided but `wit_get_work_item` returns nothing for it, print:
+```
+❌ Work item not found: {id}
+
+The ID you gave doesn't resolve to a work item you can access.
+
+Options:
+  1. Double-check the numeric ID from the work item's ADO URL
+  2. Confirm you have access to that work item's project
+  3. Re-run with the correct ID: /qa-create-test-ado <work-item-id>
+```
+
 ## Process
 
 ### Phase 1: Read Pipeline Context

package/commands/qa-create-test.md

@@ -165,6 +165,58 @@ SUGGESTED_MODE=$(echo "$RESOLVED" | node -e "const j=JSON.parse(require('fs').re
 
 The detector resolves the mode automatically when possible (from-ticket, from-aut, ado, etc.) and surfaces it in `SUGGESTED_MODE`. The mode detection logic in Step 1 below uses these resolved values.
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. A **[STOP]** check that fails: print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP. A **[WARN]** check that fails: print the notice and continue in degraded mode.
+
+### Dev-repo path does not exist [STOP]
+If the resolved `--dev-repo` path is not an existing directory:
+```
+❌ Dev-repo path not found: {path}
+
+The --dev-repo path you gave does not exist (or is not a directory), so there's
+nothing to read the code from.
+
+Options:
+  1. Re-run with a correct path: /qa-create-test <feature> --dev-repo <path>
+  2. Run from inside the repo with no --dev-repo (defaults to the current directory)
+  3. Check for a typo or an unexpanded ~ in the path
+
+Try: ls {path}
+```
+
+### Playwright MCP not connected — from-aut mode [STOP]
+If MODE is from-aut and the Playwright MCP tools are unavailable:
+```
+❌ Playwright MCP is not connected — from-aut mode needs it to explore the app.
+
+from-aut generates tests by driving the live app with Playwright MCP. Without
+it, there's no way to discover real elements and locators.
+
+Options:
+  1. Connect Playwright MCP (it ships with QAA — check ~/.claude.json), then re-run
+  2. Reinstall to re-register the MCP servers: npx qaa-agent
+  3. Generate from the code instead (no live app needed): /qa-create-test <feature>
+
+Try: /mcp   (to see connected MCP servers)
+```
+
+### Framework not detectable — from-code mode [STOP]
+If MODE is from-code and no framework can be detected:
+```
+❌ Could not detect a test framework in {dev-repo}.
+
+from-code needs to know which framework to generate for. No config files or
+manifest entries pointed to one.
+
+Options:
+  1. Pass it explicitly: /qa-create-test <feature> --framework <playwright|cypress|jest|vitest|pytest|selenium|robot-framework>
+  2. Run /qa-map first to build the codebase map, then re-run
+  3. Add a framework to the repo (e.g. `npm i -D cypress`) and re-run
+
+Try: /qa-map   (to scan and detect the stack first)
+```
+
 ## Instructions
 
 ### Step 1: Detect Mode

package/commands/qa-fix.md

@@ -115,6 +115,69 @@ TICKET=$(echo "$RESOLVED" | node -e "const j=JSON.parse(require('fs').readFileSy
 
 If you see values you didn't intend in the banner above (interactive mode), you can press Ctrl-C and re-run with explicit flags.
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. If a **[STOP]** check fails, print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP.
+
+### Test files not found [STOP]
+- If a path/directory WAS passed but does not exist, print:
+```
+❌ Test path not found: {path}
+
+The path you passed to /qa-fix doesn't exist.
+
+Options:
+  1. Point at an existing file or directory: /qa-fix <path/to/tests>
+  2. Run from your QA repo root and pass no path (it auto-detects the suite)
+  3. Check for a typo or an unexpanded ~ in the path
+
+Try: ls {path}
+```
+- If NO path was passed and auto-detection found no test files, print (no `Try:` line — there's no path to show):
+```
+❌ No test files found to fix.
+
+/qa-fix auto-detected from the current directory but found no test files.
+
+Options:
+  1. Point at your tests explicitly: /qa-fix <path/to/tests>
+  2. Run from your QA repo root so auto-detection can find the suite
+  3. If you haven't generated tests yet, create them first: /qa-create-test <feature>
+```
+
+### Test runner can't execute [STOP]
+If the test runner binary is missing or fails to launch (an infra failure, not a test failure):
+```
+❌ The test runner could not start.
+
+The framework's runner (npx playwright / cypress / jest / vitest / pytest) is
+missing, misconfigured, or its dependencies aren't installed — so tests never
+ran. This is an ENVIRONMENT ISSUE, not a test failure.
+
+Options:
+  1. Install dependencies in the repo first: npm install  (or the project's equivalent)
+  2. Verify the runner works on its own before re-running /qa-fix
+  3. Run static validation only (no execution): /qa-fix --validate-only
+
+Try: npx {runner} --version   (to confirm the runner is installed)
+```
+
+### Playwright MCP not connected — E2E run requested [STOP]
+If `--run` / `--app-url` was passed (E2E reproduction against the live app) but Playwright MCP is unavailable:
+```
+❌ Playwright MCP is not connected — E2E reproduction against the app needs it.
+
+You asked to run E2E tests against the live app (--run / --app-url), which uses
+Playwright MCP to reproduce failures in the browser. It isn't available.
+
+Options:
+  1. Connect Playwright MCP (ships with QAA — check ~/.claude.json), then re-run
+  2. Reinstall to re-register the MCP servers: npx qaa-agent
+  3. Skip execution and only classify or validate: /qa-fix --classify  (or --validate-only)
+
+Try: /mcp
+```
+
 ## Instructions
 
 ### Step 1: Detect Mode and Test Directory

package/commands/qa-map.md

@@ -73,6 +73,42 @@ All documents written to `.qa-output/codebase/`.
 | QA_REPO_BLUEPRINT.md | If no QA repo — full repo structure, configs, CI/CD strategy |
 | GAP_ANALYSIS.md | If QA repo provided — coverage map, missing tests, broken tests, quality assessment |
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. If a **[STOP]** check fails, print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP.
+
+### Dev-repo path does not exist [STOP]
+If the resolved `--dev-repo` path is not an existing directory:
+```
+❌ Dev-repo path not found: {path}
+
+/qa-map scans a repository; the --dev-repo path you gave does not exist (or is
+not a directory).
+
+Options:
+  1. Re-run with a correct path: /qa-map --dev-repo <path>
+  2. Run from inside the repo with no --dev-repo (defaults to the current directory)
+  3. Check for a typo or an unexpanded ~ in the path
+
+Try: ls {path}
+```
+
+### No framework or testable surfaces detected [STOP]
+If the scan finds no framework and no source it can classify as a testable surface:
+```
+❌ Nothing testable detected in {dev-repo}.
+
+The scan found no test framework and no source it can classify as a testable
+surface, so there's nothing to map or analyze.
+
+Options:
+  1. Point at the app sub-directory if this is a monorepo: /qa-map --dev-repo <path/to/app>
+  2. Add a framework config to the repo first (playwright/cypress/jest/vitest/pytest), then re-run
+  3. To analyze an existing test suite, pass a QA repo: /qa-map --qa-repo <path>
+
+Try: ls {dev-repo}   (to confirm you're pointing at the right directory)
+```
+
 ## Instructions
 
 1. Read `CLAUDE.md` — QA standards.

package/commands/qa-pr.md

@@ -75,6 +75,42 @@ TICKET=$(echo "$RESOLVED" | node -e "const j=JSON.parse(require('fs').readFileSy
 
 If you see values you didn't intend in the banner above (interactive mode), you can press Ctrl-C and re-run with explicit flags.
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. If a **[STOP]** check fails, print the error EXACTLY as shown and STOP.
+
+### Not a git repository [STOP]
+If the current directory is not inside a git repository:
+```
+❌ Not a git repository.
+
+/qa-pr creates a branch, commits QA artifacts, and opens a pull request — all of
+which need a git repo. The current directory isn't one.
+
+Options:
+  1. Run from inside your QA repo (or the repo where the artifacts live)
+  2. Initialize git if this is a new repo: git init && git remote add origin <url>
+  3. If you just want the files locally, skip /qa-pr — the artifacts are already in .qa-output/
+
+Try: git status   (to confirm you're in a repo)
+```
+
+### GitHub CLI not available or not signed in [STOP]
+If `gh` is not installed or `gh auth status` fails:
+```
+❌ GitHub CLI (gh) is not available or not signed in.
+
+/qa-pr uses `gh` to open the draft pull request. It's either not installed or
+not authenticated, so the PR step can't run.
+
+Options:
+  1. Authenticate: gh auth login
+  2. Install the GitHub CLI first (https://cli.github.com), then re-run
+  3. Create the branch and commits locally, then open the PR by hand in your git host
+
+Try: gh auth status
+```
+
 ## Instructions
 
 1. Read `CLAUDE.md` -- git workflow, commit conventions.

package/commands/qa-research.md

@@ -80,6 +80,42 @@ These files are consumed by downstream agents:
 | `API_TESTING_STRATEGY.md` | Planner (API test case design), Executor (implementation patterns) |
 | `E2E_STRATEGY.md` | Planner (E2E scope decisions), Executor (POM and selector patterns) |
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. If a **[STOP]** check fails, print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP.
+
+### Context7 MCP not connected [STOP]
+If the Context7 MCP tools are unavailable:
+```
+❌ Context7 MCP is not connected — research needs it as the primary source.
+
+/qa-research relies on Context7 to fetch current framework and library docs.
+Without it, findings would fall back to training data and could be stale or wrong.
+
+Options:
+  1. Connect Context7 (it ships with QAA — check that it registered in ~/.claude.json)
+  2. Reinstall to re-register the MCP servers: npx qaa-agent
+  3. Skip research for now — downstream agents fall back to cache/training data if no research docs exist
+
+Try: /mcp   (to see connected MCP servers)
+```
+
+### Dev-repo path does not exist [STOP]
+If `--dev-repo` was passed but the path does not exist (default is the current directory):
+```
+❌ Dev-repo path not found: {path}
+
+/qa-research reads the project's stack to focus its research. The --dev-repo path
+you gave does not exist (or is not a directory).
+
+Options:
+  1. Re-run with a correct path: /qa-research --dev-repo <path>
+  2. Run from inside the repo with no --dev-repo (defaults to the current directory)
+  3. Check for a typo or an unexpanded ~ in the path
+
+Try: ls {path}
+```
+
 ## Instructions
 
 ### Step 1: Initialize

package/commands/qa-start.md

@@ -67,6 +67,43 @@ When the workflow's Step 1 invokes the intent detector with `$ARGUMENTS`, you mu
 
 If you pre-translate, the detector sees only flags and reports every value as `source: flag`, which causes `ALL_FROM_FLAGS=true` and bypasses the confirmation checkpoint — defeating its purpose. Always pass raw input.
 
+## Pre-flight checks
+
+Run these BEFORE spawning any agent. A **[STOP]** check that fails: print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP. A **[WARN]** check that fails: print the notice and continue in degraded mode.
+
+### Dev-repo path does not exist [STOP]
+If the resolved `--dev-repo` path is not an existing directory:
+```
+❌ Dev-repo path not found: {path}
+
+/qa-start needs a real directory to scan. The path resolved from your input
+does not exist (or is not a directory).
+
+Options:
+  1. Re-run with a correct path: /qa-start --dev-repo <path-to-your-repo>
+  2. Run from inside the repo with no path (defaults to the current directory)
+  3. Double-check the path — a typo or a ~ that did not expand is the usual cause
+
+Try: ls {path}
+```
+
+### Framework not detectable [STOP]
+If the scanner finds no test framework and no language/config it can map to one:
+```
+❌ Could not detect a test framework in {dev-repo}.
+
+QAA looks for a framework via config files (playwright.config, cypress.config,
+jest/vitest config, pytest.ini, etc.) and package manifests. None were found,
+so it can't decide how to write tests.
+
+Options:
+  1. Pass it explicitly: /qa-start --framework <playwright|cypress|jest|vitest|pytest|selenium|robot-framework>
+  2. Point at the app sub-directory if this is a monorepo: /qa-start --dev-repo <path/to/app>
+  3. Add a framework to the repo first (e.g. `npm i -D @playwright/test`), then re-run
+
+Try: /qa-research   (to investigate the stack before generating tests)
+```
+
 ## Instructions
 
 1. Read `CLAUDE.md` — all QA standards that govern the pipeline.

package/commands/qa-test-report.md

@@ -57,6 +57,53 @@ modifying test cases — STOP and restart from step 1.
 
 ---
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. If a **[STOP]** check fails, print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP.
+
+### Azure DevOps MCP not connected [STOP]
+If the ADO MCP tools are unavailable:
+```
+❌ Azure DevOps MCP is not connected — this command reads from ADO.
+
+/qa-test-report pulls test-case execution status from Azure DevOps via the ADO
+MCP tools and REST API. They aren't available in this session.
+
+Options:
+  1. Connect the Azure DevOps MCP server, then re-run
+  2. Verify it's configured in your Claude Code MCP settings
+  3. Confirm ADO_MCP_AUTH_TOKEN is set if you also need the REST fallback for run outcomes
+
+Try: /mcp   (to see connected MCP servers)
+```
+
+### Work item ID missing or not found [STOP]
+- If NO work item ID was provided, print:
+```
+❌ No work item ID provided.
+
+/qa-test-report needs an Azure DevOps work item ID to build the report from its
+linked test cases.
+
+Options:
+  1. Pass one: /qa-test-report <work-item-id>
+  2. Copy the numeric ID from the work item's ADO URL
+  3. Confirm you have access to that work item's project
+
+Try: /qa-test-report 85508   (example)
+```
+- If an ID WAS provided but `wit_get_work_item` returns nothing for it, print:
+```
+❌ Work item not found: {id}
+
+The ID you gave doesn't resolve to a work item you can access.
+
+Options:
+  1. Double-check the numeric ID from the work item's ADO URL
+  2. Confirm you have access to that work item's project
+  3. Re-run with the correct ID: /qa-test-report <work-item-id>
+```
+
 ## Process
 
 ### Phase 1 — Resolve the Work Item

package/commands/qa-testid.md

@@ -39,6 +39,60 @@ the framework-detection gate — STOP and restart from step 1.
 
 - source-directory: path to frontend source (auto-detects if omitted)
 
+## Pre-flight checks
+
+Run these BEFORE the main flow. A **[STOP]** check that fails: print the error EXACTLY as shown (fill in the `{...}` placeholders) and STOP. A **[WARN]** check that fails: print the notice and continue in degraded mode.
+
+### Source directory not found [STOP]
+If a source directory argument was given but does not exist:
+```
+❌ Source directory not found: {path}
+
+/qa-testid scans frontend components at the given path. That directory does not
+exist.
+
+Options:
+  1. Pass a valid path: /qa-testid <path-to-frontend-src>
+  2. Run with no path to auto-detect (looks for src/, app/, components/, pages/, ...)
+  3. Check for a typo or an unexpanded ~ in the path
+
+Try: ls {path}
+```
+
+### No frontend framework detected [STOP]
+If auto-detection finds no React / Vue / Angular / Svelte / HTML:
+```
+❌ No frontend framework detected.
+
+/qa-testid injects data-testid into UI components, but no React (.jsx/.tsx), Vue
+(.vue), Angular (.component.ts), Svelte (.svelte), or HTML files were found in
+the scanned directory.
+
+Options:
+  1. Point at the frontend source explicitly: /qa-testid <path-to-components>
+  2. If this is a monorepo, target the frontend package: /qa-testid <path/to/web-app>
+  3. This command only applies to frontend repos — there's nothing to inject on a backend/API-only project
+
+Try: ls {source-dir}   (to confirm it holds component files)
+```
+
+### Playwright MCP not connected [WARN]
+If the Playwright MCP tools are unavailable (used to browser-verify injected attributes):
+```
+❌ Playwright MCP is not connected — DOM verification will be skipped.
+
+/qa-testid uses Playwright MCP to confirm injected data-testid attributes render
+in the live DOM. Without it, injection and the audit report still run — only the
+browser-verify step is skipped.
+
+Options:
+  1. Connect Playwright MCP (ships with QAA — check ~/.claude.json) for full verification
+  2. Reinstall to re-register the MCP servers: npx qaa-agent
+  3. Continue now with static validation only (no live DOM check)
+
+Try: /mcp
+```
+
 ## Instructions
 
 1. Read `CLAUDE.md` -- data-testid Convention section.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qaa-agent",
-  "version": "1.9.6",
+  "version": "1.9.7",
   "description": "QA Automation Agent for Claude Code — multi-agent pipeline that analyzes repos, generates tests, validates, and creates PRs",
   "bin": {
     "qaa-agent": "./bin/install.cjs"