@qa-gentic/agents 1.1.2 → 1.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@qa-gentic/agents",
3
- "version": "1.1.2",
3
+ "version": "1.1.3",
4
4
  "description": "QA STLC Agents — MCP servers + skills for AI-powered test case, Gherkin, and Playwright generation against Azure DevOps. Works with Claude Code, GitHub Copilot, Cursor, Windsurf.",
5
5
  "keywords": [
6
6
  "playwright",
@@ -129,6 +129,16 @@ than silently routing around it.
129
129
  | File already exists at target path | Read it first; check for overlap; write only net-new content |
130
130
  | `generate_playwright_code` output available | Pass the `files` dict directly to `write_helix_files` — do not reformat |
131
131
 
132
+ **Playwright generation routing (strict — no inference):**
133
+
134
+ | Project state (`list_helix_tree` result) | Action |
135
+ |---|---|
136
+ | `framework_state: "absent"` or `"partial"` (fresh project) | Call `scaffold_locator_repository` FIRST, then `generate_playwright_code` |
137
+ | `framework_state: "present"` (existing boilerplate) | Call `generate_playwright_code` ONLY — never call `scaffold_locator_repository` |
138
+
139
+ Calling `scaffold_locator_repository` on an existing project overwrites the six shared
140
+ infrastructure files and destroys customisations. It is only safe on a fresh project.
141
+
132
142
  ---
133
143
 
134
144
  ## 4. Strict Input → Tool → Output Chains
@@ -10,6 +10,7 @@ description: >
10
10
  work item type: PBI, Bug, or Feature ID.
11
11
  compatibility:
12
12
  tools:
13
+ - qa-playwright-generator:scaffold_locator_repository
13
14
  - qa-playwright-generator:generate_playwright_code
14
15
  - qa-playwright-generator:attach_code_to_work_item
15
16
  - qa-playwright-generator:validate_gherkin_steps
@@ -61,6 +62,30 @@ cached. If `generate-gherkin` already ran for this `work_item_id`, skip PHASE 1
61
62
 
62
63
  ## Step-by-Step Workflow
63
64
 
65
+ ### Step 0 — Route: fresh project vs. existing boilerplate
66
+
67
+ Before any other step, determine whether the Helix-QA project already has the automation
68
+ infrastructure in place.
69
+
70
+ ```
71
+ Call: qa-helix-writer:list_helix_tree(helix_root)
72
+
73
+ ├─ framework_state: "absent" or "partial" → FRESH PROJECT
74
+ │ Call scaffold_locator_repository(...) FIRST
75
+ │ Then call generate_playwright_code(...)
76
+
77
+ └─ framework_state: "present" → EXISTING BOILERPLATE
78
+ Call generate_playwright_code(...) ONLY
79
+ Do NOT call scaffold_locator_repository — infra already exists
80
+ ```
81
+
82
+ **Why this matters:** `scaffold_locator_repository` generates the six shared infrastructure
83
+ files (`LocatorRepository`, `LocatorHealer`, `TimingHealer`, `VisualIntentChecker`,
84
+ `DevToolsHealer`, `cucumber.config.ts`). Calling it on an existing project overwrites those
85
+ files and destroys any customisations. Never call it when `framework_state: "present"`.
86
+
87
+ ---
88
+
64
89
  ### Step 1 — Load existing Playwright artifacts from cache
65
90
 
66
91
  Read from `CACHE[work_item_id]` (populated by the deduplication protocol pre-flight):