qaa-agent 1.9.5 → 1.9.7

package/commands/qa-testid.md

@@ -2,12 +2,97 @@
 
 Scan frontend source code, audit missing data-testid attributes, and inject them following the naming convention in CLAUDE.md. Creates a separate branch for the changes.
 
+## ⚠ MANDATORY: How to Execute This Command
+
+Execute these steps IN ORDER. Every step is mandatory. Do NOT improvise,
+reorder, skip, or invent steps.
+
+1. Read `CLAUDE.md` — the data-testid Convention section — before anything else.
+2. Execute `workflows/qa-testid.md` end-to-end, in order, without skipping steps.
+3. Preserve ALL workflow gates. In particular, do NOT bypass:
+   - **Framework detection** (workflow Step 2, `detect_frontend`): if no frontend
+     directory, no framework, or no component files are found, STOP with the
+     workflow's error — do NOT proceed to injection.
+   - **Audit checkpoint / user approval** (workflow Step 4, CHECKPOINT phase):
+     the testid-injector MUST present TESTID_AUDIT_REPORT.md and wait for the
+     user to approve proposed values BEFORE injecting. Do NOT inject without it.
+   - **Branch creation** (workflow Step 4 INJECT phase / Step 5,
+     `create_branch_and_commit`): injection happens ONLY on the separate branch
+     `qa/testid-inject-{YYYY-MM-DD}` — never on the working branch.
+4. Spawn the scanner and testid-injector via Task() with their
+   `<critical_directive>` blocks, as the workflow specifies — do NOT do the
+   scan/audit/injection inline.
+
+### DO NOT
+- Inject any data-testid before the user approves the audit report
+- Modify source files on the working branch (injection is branch-isolated)
+- Change application logic — only add data-testid attributes
+- Skip framework detection or proceed when it reports no frontend
+- Invent steps not in the workflow, or reorder them
+
+If you find yourself injecting before approval, working off-branch, or skipping
+the framework-detection gate — STOP and restart from step 1.
+
 ## Usage
 
 /qa-testid [<source-directory>]
 
 - 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,41 +1,41 @@
-{
-  "name": "qaa-agent",
-  "version": "1.9.5",
-  "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"
-  },
-  "keywords": [
-    "qa",
-    "automation",
-    "testing",
-    "claude-code",
-    "playwright",
-    "jest",
-    "pytest",
-    "ai-agent"
-  ],
-  "author": "Backhaus7997",
-  "license": "MIT",
-  "dependencies": {
-    "@playwright/mcp": "latest",
-    "@upstash/context7-mcp": "latest"
-  },
-  "files": [
-    "bin/",
-    "agents/",
-    "workflows/",
-    "templates/",
-    "docs/COMMANDS.md",
-    "docs/DEMO.md",
-    "docs/TESTING.md",
-    "commands/",
-    "skills/",
-    "frameworks/",
-    "settings.json",
-    ".mcp.json",
-    "CLAUDE.md",
-    "CHANGELOG.md",
-    "VERSION"
-  ]
-}
+{
+  "name": "qaa-agent",
+  "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"
+  },
+  "keywords": [
+    "qa",
+    "automation",
+    "testing",
+    "claude-code",
+    "playwright",
+    "jest",
+    "pytest",
+    "ai-agent"
+  ],
+  "author": "Backhaus7997",
+  "license": "MIT",
+  "dependencies": {
+    "@playwright/mcp": "latest",
+    "@upstash/context7-mcp": "latest"
+  },
+  "files": [
+    "bin/",
+    "agents/",
+    "workflows/",
+    "templates/",
+    "docs/COMMANDS.md",
+    "docs/DEMO.md",
+    "docs/TESTING.md",
+    "commands/",
+    "skills/",
+    "frameworks/",
+    "settings.json",
+    ".mcp.json",
+    "CLAUDE.md",
+    "CHANGELOG.md",
+    "VERSION"
+  ]
+}