@keber/qa-framework 1.6.2 → 1.7.1

package/CHANGELOG.md

@@ -33,6 +33,43 @@ has been removed or parameterized. See `docs/comparison-matrix.md` and `docs/gen
 
 ---
 
+## [1.7.1] - 2026-05-06
+
+### Fixed
+
+- **Agent instructions template extracted** — `templates/qa-framework.instructions.md` is now
+  the single source of truth for QA agent rules. Both `init` and `upgrade` read and interpolate
+  this file instead of maintaining separate hardcoded strings, eliminating the rule divergence
+  that caused `upgrade` to deploy only 7 rules instead of 11.
+- `upgrade.js` — removed `buildCopilotInstructions()` function (dead code after template extraction).
+
+---
+
+## [1.7.0] - 2026-05-06
+
+### Changed
+
+- **Agent instructions moved to `.github/instructions/qa-framework.instructions.md`** — the
+  framework no longer writes to `.github/copilot-instructions.md`. The new file is a VS Code
+  `*.instructions.md` file with `applyTo: '**'` frontmatter, which Copilot loads automatically.
+  This eliminates the conflict between framework-owned rules and project-owned custom instructions:
+  both files coexist independently and the framework file is freely upgradeable.
+
+### Added
+
+- **`upgrade` step 2b — automatic migration of old `copilot-instructions.md`**:
+  - If the file contains only QA Framework content (any previous version) → the file is deleted.
+  - If the file contains custom instructions and a QA Framework section → the QA section is stripped and the custom content is preserved.
+  - If the file contains no QA Framework content → the file is left untouched.
+  The detection marker is the heading `# QA Framework Instructions`, consistent across all versions.
+
+### Migration
+
+Run `npx qa-framework upgrade`. No manual steps required.
+See `MIGRATION-NOTES.md` — section "Upgrading from a version that used `.github/copilot-instructions.md`".
+
+---
+
 ## [1.6.2] - 2026-05-05
 
 ### Added

package/README.md

@@ -1,7 +1,7 @@
 # qa-framework
 
 > Reusable, installable, agent-oriented QA framework for spec-driven automated testing.
-> Current version: **v1.6.2**
+> Current version: **v1.7.1**
 
 ---
 
@@ -61,7 +61,7 @@ npm install @keber/qa-framework
 1. Create the `qa/` directory tree in your project root
 2. Copy all base templates into place
 3. Create `qa/qa-framework.config.json` for project-specific settings
-4. Generate `.github/copilot-instructions.md` with QA agent behavior rules (11 rules + ADO detection)
+4. Generate `.github/instructions/qa-framework.instructions.md` with QA agent behavior rules (11 rules + ADO detection)
 5. Copy the `skills/` set to `.github/skills/` so the agent can load them on demand
 6. Create `qa/AGENT-NEXT-STEPS.md` with follow-up steps
 
@@ -73,9 +73,13 @@ After `npm update @keber/qa-framework`, run:
 npx qa-framework upgrade
 ```
 
-This overwrites **only** framework-owned files (skills, `copilot-instructions.md`,
+This overwrites **only** framework-owned files (skills, `qa-framework.instructions.md`,
 `QA-STRUCTURE-GUIDE.md`) and never touches your specs, test plans, automation code, or memory.
 
+If upgrading from a version that wrote to `.github/copilot-instructions.md`, `upgrade`
+automatically removes the QA section from that file (or deletes it if it contained only
+framework content), and creates `.github/instructions/qa-framework.instructions.md` instead.
+
 ---
 
 ## Repository Structure (this package)
@@ -148,7 +152,7 @@ qa-framework/
 │
 └── scripts/                          <- CLI commands
     ├── cli.js                        <- Entry point (qa-framework <command>)
-    ├── init.js                       <- Scaffold qa/ tree + skills + copilot-instructions
+    ├── init.js                       <- Scaffold qa/ tree + skills + qa-framework.instructions.md
     ├── upgrade.js                    <- Refresh framework-owned files after npm update
     ├── generate.js                   <- Generate individual artifact from template
     └── validate.js                   <- Check structure compliance
@@ -194,10 +198,15 @@ Additionally, `init` writes to the project root:
 
 ```
 .github/
-├── copilot-instructions.md      <- Generated agent rules (11 rules + ADO detection)
-└── skills/                      <- Copied from package skills/ (one folder per pipeline stage)
+├── instructions/
+│   └── qa-framework.instructions.md  <- QA agent rules (framework-owned, applyTo: '**')
+└── skills/                           <- Copied from package skills/ (one folder per pipeline stage)
 ```
 
+> `qa-framework.instructions.md` is a VS Code `*.instructions.md` file, separate from any
+> custom `.github/copilot-instructions.md` the project may already have. The two files
+> coexist without conflict and are independently upgradeable.
+
 See [docs/folder-structure-guide.md](docs/folder-structure-guide.md) for a full explanation of every folder.
 
 ---
@@ -218,7 +227,7 @@ them via `read_file` without touching `node_modules`.
 
 ### QA Pipeline
 
-Skills map to the pipeline stages enforced by `.github/copilot-instructions.md`:
+Skills map to the pipeline stages enforced by `.github/instructions/qa-framework.instructions.md`:
 
 | Stage | Skill | Task | Track | Prerequisite |
 |---|---|---|---|---|
@@ -254,7 +263,7 @@ Options:
   --version, -v               Show version
 ```
 
-**upgrade** overwrites only framework-owned files (skills, `copilot-instructions.md`,
+**upgrade** overwrites only framework-owned files (skills, `qa-framework.instructions.md`,
 `QA-STRUCTURE-GUIDE.md`) and never touches project-owned files. Run `--dry-run` to preview
 without writing.
 

package/docs/installation.md

@@ -51,7 +51,7 @@ qa/
 └── 08-azure-integration/README.md
 └── memory/INDEX.md
 
-.github/copilot-instructions.md     <- Generated agent rules
+.github/instructions/qa-framework.instructions.md  <- QA agent rules (framework-owned)
 .github/skills/                     <- 8 agent skill sets (SKILL.md + references/)
 ```
 
@@ -93,7 +93,7 @@ After `npm update @keber/qa-framework`:
 npx qa-framework upgrade
 ```
 
-This overwrites only framework-owned files (`.github/skills/`, `copilot-instructions.md`,
+This overwrites only framework-owned files (`.github/skills/`, `.github/instructions/qa-framework.instructions.md`,
 `QA-STRUCTURE-GUIDE.md`) and migrates the `07-automation/` structure if upgrading from
 v1.5.x. Your specs, tests, and memory are never touched.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@keber/qa-framework",
-  "version": "1.6.2",
+  "version": "1.7.1",
   "description": "Reusable spec-driven QA framework for IDE-agent-assisted automated testing. Installable as an npm package. Provides structure, templates, agent instructions, and optional integrations for Playwright and Azure DevOps.",
   "keywords": [
     "qa",

package/scripts/init.js

@@ -253,9 +253,9 @@ if (fs.existsSync(structureGuideSrc)) {
   writeIfMissing(structureGuideDest, fs.readFileSync(structureGuideSrc, 'utf8'));
 }
 
-// --- .github/copilot-instructions.md ---
+// --- .github/instructions/qa-framework.instructions.md ---
 const githubDir         = path.join(cwd, '.github');
-const copilotInstrPath  = path.join(githubDir, 'copilot-instructions.md');
+const copilotInstrPath  = path.join(githubDir, 'instructions', 'qa-framework.instructions.md');
 
 // Detect whether the ado-qa skill is available (installed or already copied)
 const adoQaInstalled = fs.existsSync(path.join(cwd, 'node_modules', '@keber', 'ado-qa'))
@@ -264,17 +264,16 @@ const adoSkillReady  = fs.existsSync(path.join(cwd, '.github', 'skills', 'ado-qa
 const adoAvailable   = adoQaInstalled || adoSkillReady;
 
 const adoSection = adoAvailable
-  ? `
-## Azure DevOps integration (ado-qa)
+  ? `## Azure DevOps integration (ado-qa)
 
 The \`ado-qa\` skill is installed. Load it in PowerShell before any ADO operation:
 \`\`\`powershell
 . .github/skills/ado-qa/load.ps1
 \`\`\`
 Refer to \`qa/00-guides/AGENT-INSTRUCTIONS-ADO-INTEGRATION.md\` for the full ADO workflow.
+
 `
-  : `
-## Azure DevOps integration (not installed)
+  : `## Azure DevOps integration (not installed)
 
 > ⚠️ **Agent note:** \`ado-qa\` is not installed in this project.
 > To enable Azure DevOps integration (query Work Items, Test Plans, create bugs, etc.) run:
@@ -282,50 +281,13 @@ Refer to \`qa/00-guides/AGENT-INSTRUCTIONS-ADO-INTEGRATION.md\` for the full ADO
 > npm install github:keber/ado-qa
 > \`\`\`
 > This will automatically copy the ADO skills to \`.github/skills/\` via postinstall.
-`;
 
-const copilotInstrContent = `# QA Framework Instructions
-
-This project uses \`@keber/qa-framework\` v${config.frameworkVersion ?? '1.0.0'} for spec-driven automated testing.
-
-## Agent behavior rules
-
-0. **On every conversation start:** check if \`qa/AGENT-NEXT-STEPS.md\` exists. If it does, read it and complete its steps before anything else.
-1. Before performing any QA task, load the relevant skill from \`.github/skills/\`. For project context, read \`qa/memory/INDEX.md\` if it exists, then load only the memory files relevant to the current task — do not load all memory files unconditionally. Never execute a pipeline stage unless its prerequisite is satisfied.
-2. Always save artifacts in the correct \`qa/\` subfolder - refer to \`qa/QA-STRUCTURE-GUIDE.md\`
-3. Never hardcode credentials - always use env vars and \`<PLACEHOLDER>\` in documentation
-4. Follow the naming conventions in \`qa/00-standards/naming-conventions.md\`
-5. Read previous test suites code in \`qa/07-automation/e2e/tests/\` if available before writing new automation to maintain consistency in style and approach
-6. Project QA config is at \`qa/qa-framework.config.json\`
-7. Save learnings in \`qa/memory/\` with proper naming and metadata. Always update \`qa/memory/INDEX.md\` after adding or updating any memory file.
-8. **Sprint/module completion criteria:** A sprint or module is complete when every TC in scope has one of these three valid states - and no other: (a) \`test()\` passing: the app meets the spec; (b) \`test.fail()\`: the app violates the spec **and** a file \`qa/06-defects/open/DEF-SIS-NNN_*.md\` exists documenting which business rule is violated and what the app actually does; (c) \`test.skip()\`: the TC is not yet executable, annotated with \`PENDING-CODE\` and a linked issue. A sprint is **not** complete if any TC is failing without \`test.fail()\`, or has \`test.fail()\` without a defect file, or has \`test.skip()\` without a \`PENDING-CODE\` reason.
-9. **On sprint/module completion:** (1) update the module status row in \`qa/README.md\`; (2) move the completed sprint checklist from \`AGENT-NEXT-STEPS.md\` to the \`## Sprint History\` section of \`qa/README.md\`; (3) trim \`AGENT-NEXT-STEPS.md\` so it contains only the next sprint — never let it accumulate more than one active sprint.
-10. **Assertion polarity rule (BLOCKING):** A test must assert what the **spec** requires, not what the app currently does. If the app fails to meet the spec, use \`test.fail()\` + correct assertion to document the defect — **never invert or weaken an assertion to make a test go green.** A failing test that exposes a real defect is always more valuable than a passing test that hides one.
-11. **Character encoding safety (BLOCKING):** In ALL generated content (markdown, scripts, test titles, ADO fields, config files), never use characters at these Unicode code points: em-dash (U+2014), en-dash (U+2013), horizontal ellipsis (U+2026), smart/curly quotes (U+201C, U+201D, U+2018, U+2019), or directional arrows (U+2190-U+21FF). Use ASCII equivalents instead: \` - \` (hyphen with surrounding spaces) for dashes, \`...\` for ellipsis, \`"\` and \`'\` for quotes, \`->\` and \`<-\` for arrows. Exception: Latin Extended characters (U+00C0-U+024F) are always permitted - this covers Spanish vowels with accents (U+00E0-U+00FA), n with tilde (U+00F1/U+00D1), and u/o with umlaut (U+00FC/U+00DC, U+00F6/U+00D6).
-
-## Formatting rules for generated content
-1. Generate the output in \`UTF-8\` encoding without BOM (\`UTF-8\`, no signature).
-2. Ensure the raw output is \`UTF-8\` encoded with no \`EF BB BF\` bytes at the beginning.
-
-## QA Pipeline
-
-Stages must run in order. Never start a stage unless its prerequisite is met.
-
-| Stage | Task | Skill | Prerequisite |
-|---|---|---|---|
-| 1 | Analyze module | \`.github/skills/qa-module-analysis/SKILL.md\` | None |
-| 2 | Generate specifications | \`.github/skills/qa-spec-generation/SKILL.md\` | 00-inventory.md exists |
-| 3 | Generate test plan | \`.github/skills/qa-test-plan/SKILL.md\` | 05-test-scenarios.md exists |
-| 4 | Generate test cases | \`.github/skills/qa-test-cases/SKILL.md\` | Test plan exists |
-| 5 | Generate automation | \`.github/skills/qa-automation/SKILL.md\` | Specs approved, no PENDING-CODE |
-| 5b | Stabilize failing tests | \`.github/skills/qa-test-stabilization/SKILL.md\` | Failing tests exist |
-| 6 | Maintenance | \`.github/skills/qa-maintenance/SKILL.md\` | Application change delivered |
-| — | ADO integration | \`.github/skills/qa-ado-integration/SKILL.md\` | ADO enabled in config |
-
-## Project KB
-1. \`qa/README.md\`          — The Living Index: module status, sprint history, blockers, quick-start commands.
-2. \`qa/memory/INDEX.md\`    — Index of all memory files; load this before selecting which files to read.
 `;
+
+const instrTemplatePath = path.resolve(__dirname, '..', 'templates', 'qa-framework.instructions.md');
+const copilotInstrContent = fs.readFileSync(instrTemplatePath, 'utf8')
+  .replace('{{VERSION}}', config.frameworkVersion ?? '1.0.0')
+  .replace('{{ADO_SECTION}}', adoSection);
 writeIfMissing(copilotInstrPath, copilotInstrContent);
 
 // --- AGENT-NEXT-STEPS.md — readable by the agent after install ---
@@ -337,7 +299,7 @@ const nextStepsContent = `# ✅ @keber/qa-framework installed successfully
 ## What was scaffolded
 
 - \`qa/\` folder structure with spec templates and agent instructions
-- \`.github/copilot-instructions.md\` with QA agent behavior rules
+- \`.github/instructions/qa-framework.instructions.md\` with QA agent behavior rules (framework-owned, safe to upgrade)
 
 ## Required next steps
 

package/scripts/upgrade.js

@@ -81,12 +81,51 @@ if (!fs.existsSync(skillsSrc)) {
 }
 
 // ---------------------------------------------------------------------------
-// 2. .github/copilot-instructions.md — overwrite (framework-owned sequencer)
+// 2. .github/instructions/qa-framework.instructions.md — overwrite (framework-owned)
 // ---------------------------------------------------------------------------
-const copilotInstrPath = path.join(githubDir, 'copilot-instructions.md');
-const copilotContent = buildCopilotInstructions(config);
+const copilotInstrPath = path.join(githubDir, 'instructions', 'qa-framework.instructions.md');
+const instrTemplatePath = path.resolve(__dirname, '..', 'templates', 'qa-framework.instructions.md');
+const copilotContent = fs.readFileSync(instrTemplatePath, 'utf8')
+  .replace('{{VERSION}}', config.frameworkVersion ?? '1.0.0')
+  .replace('{{ADO_SECTION}}', '');
 forceWrite(copilotInstrPath, copilotContent);
 
+// ---------------------------------------------------------------------------
+// 2b. Migration: strip QA Framework section from old copilot-instructions.md
+//
+// Handles all cases:
+//   A. File has custom instructions + QA section  → keep custom, strip QA section
+//   B. File has ONLY QA section (any version)     → delete the file
+//   C. File does not mention QA Framework         → leave untouched
+//
+// The QA section always starts with "# QA Framework Instructions" across all
+// previous versions, so that heading is the reliable split point.
+// ---------------------------------------------------------------------------
+const oldCopilotPath = path.join(githubDir, 'copilot-instructions.md');
+if (fs.existsSync(oldCopilotPath)) {
+  const oldContent = fs.readFileSync(oldCopilotPath, 'utf8');
+  const qaMarker   = '# QA Framework Instructions';
+  const qaIdx      = oldContent.indexOf(qaMarker);
+
+  if (qaIdx !== -1) {
+    // Extract anything before the QA section, removing any trailing separator
+    const before = oldContent.slice(0, qaIdx).replace(/\s*\n---\s*$/, '').trim();
+
+    if (before.length === 0) {
+      // Case B: file contained only QA Framework content → delete it
+      if (!dryRun) fs.unlinkSync(oldCopilotPath);
+      updated.push(oldCopilotPath);
+      console.log(`  [deleted]  .github/copilot-instructions.md (contained only QA Framework rules — now in .github/instructions/qa-framework.instructions.md)`);
+    } else {
+      // Case A: file had custom content too → write back only the custom part
+      if (!dryRun) fs.writeFileSync(oldCopilotPath, before + '\n', 'utf8');
+      updated.push(oldCopilotPath);
+      console.log(`  [cleaned]  .github/copilot-instructions.md — removed QA Framework section, kept custom instructions`);
+    }
+  }
+  // Case C: no QA marker found → leave untouched (no log noise)
+}
+
 // ---------------------------------------------------------------------------
 // 3. qa/QA-STRUCTURE-GUIDE.md — overwrite (framework doc)
 // ---------------------------------------------------------------------------
@@ -276,40 +315,3 @@ function copyDirForce(srcDir, destDir) {
   }
 }
 
-function buildCopilotInstructions(cfg) {
-  const version = cfg.frameworkVersion ?? '1.0.0';
-  return `# QA Framework Instructions
-
-This project uses \`@keber/qa-framework\` v${version} for spec-driven automated testing.
-
-## Agent behavior rules
-
-0. **On every conversation start:** check if \`qa/AGENT-NEXT-STEPS.md\` exists. If it does, read it and complete its steps before anything else.
-1. Before performing any QA task, load the relevant skill from \`.github/skills/\`. For project context, read \`qa/memory/INDEX.md\` if it exists, then load only the memory files relevant to the current task — do not load all memory files unconditionally. Never execute a pipeline stage unless its prerequisite is satisfied.
-2. Always save artifacts in the correct \`qa/\` subfolder — refer to \`qa/QA-STRUCTURE-GUIDE.md\`
-3. Never hardcode credentials — always use env vars and \`<PLACEHOLDER>\` in documentation
-4. Follow the naming conventions in \`qa/00-standards/naming-conventions.md\`
-5. Project QA config is at \`qa/qa-framework.config.json\`
-6. Save learnings in \`qa/memory/\` with proper naming and metadata. Always update \`qa/memory/INDEX.md\` after adding or updating any memory file.
-7. **On module/sprint completion** (all TCs passing): (1) update the module status row in \`qa/README.md\`; (2) move the completed sprint checklist from \`AGENT-NEXT-STEPS.md\` to the \`## Sprint History\` section of \`qa/README.md\`; (3) trim \`AGENT-NEXT-STEPS.md\` so it contains only the next sprint — never let it accumulate more than one active sprint.
-
-## QA Pipeline
-
-Stages must run in order. Never start a stage unless its prerequisite is met.
-
-| Stage | Task | Skill | Prerequisite |
-|---|---|---|---|
-| 1 | Analyze module | \`.github/skills/qa-module-analysis/SKILL.md\` | None |
-| 2 | Generate specifications | \`.github/skills/qa-spec-generation/SKILL.md\` | 00-inventory.md exists |
-| 3 | Generate test plan | \`.github/skills/qa-test-plan/SKILL.md\` | 05-test-scenarios.md exists |
-| 4 | Generate test cases | \`.github/skills/qa-test-cases/SKILL.md\` | Test plan exists |
-| 5 | Generate automation | \`.github/skills/qa-automation/SKILL.md\` | Specs approved, no PENDING-CODE |
-| 5b | Stabilize failing tests | \`.github/skills/qa-test-stabilization/SKILL.md\` | Failing tests exist |
-| 6 | Maintenance | \`.github/skills/qa-maintenance/SKILL.md\` | Application change delivered |
-| — | ADO integration | \`.github/skills/qa-ado-integration/SKILL.md\` | ADO enabled in config |
-
-## Project KB
-1. \`qa/README.md\`          — The Living Index: module status, sprint history, blockers, quick-start commands.
-2. \`qa/memory/INDEX.md\`    — Index of all memory files; load this before selecting which files to read.
-`;
-}

package/templates/qa-framework.instructions.md

@@ -0,0 +1,45 @@
+---
+applyTo: '**'
+---
+# QA Framework Instructions
+
+This project uses `@keber/qa-framework` v{{VERSION}} for spec-driven automated testing.
+
+## Agent behavior rules
+
+0. **On every conversation start:** check if `qa/AGENT-NEXT-STEPS.md` exists. If it does, read it and complete its steps before anything else.
+1. Before performing any QA task, load the relevant skill from `.github/skills/`. For project context, read `qa/memory/INDEX.md` if it exists, then load only the memory files relevant to the current task — do not load all memory files unconditionally. Never execute a pipeline stage unless its prerequisite is satisfied.
+2. Always save artifacts in the correct `qa/` subfolder - refer to `qa/QA-STRUCTURE-GUIDE.md`
+3. Never hardcode credentials - always use env vars and `<PLACEHOLDER>` in documentation
+4. Follow the naming conventions in `qa/00-standards/naming-conventions.md`
+5. Read previous test suites code in `qa/07-automation/e2e/tests/` if available before writing new automation to maintain consistency in style and approach
+6. Project QA config is at `qa/qa-framework.config.json`
+7. Save learnings in `qa/memory/` with proper naming and metadata. Always update `qa/memory/INDEX.md` after adding or updating any memory file.
+8. **Sprint/module completion criteria:** A sprint or module is complete when every TC in scope has one of these three valid states - and no other: (a) `test()` passing: the app meets the spec; (b) `test.fail()`: the app violates the spec **and** a file `qa/06-defects/open/DEF-SIS-NNN_*.md` exists documenting which business rule is violated and what the app actually does; (c) `test.skip()`: the TC is not yet executable, annotated with `PENDING-CODE` and a linked issue. A sprint is **not** complete if any TC is failing without `test.fail()`, or has `test.fail()` without a defect file, or has `test.skip()` without a `PENDING-CODE` reason.
+9. **On sprint/module completion:** (1) update the module status row in `qa/README.md`; (2) move the completed sprint checklist from `AGENT-NEXT-STEPS.md` to the `## Sprint History` section of `qa/README.md`; (3) trim `AGENT-NEXT-STEPS.md` so it contains only the next sprint — never let it accumulate more than one active sprint.
+10. **Assertion polarity rule (BLOCKING):** A test must assert what the **spec** requires, not what the app currently does. If the app fails to meet the spec, use `test.fail()` + correct assertion to document the defect — **never invert or weaken an assertion to make a test go green.** A failing test that exposes a real defect is always more valuable than a passing test that hides one.
+11. **Character encoding safety (BLOCKING):** In ALL generated content (markdown, scripts, test titles, ADO fields, config files), never use characters at these Unicode code points: em-dash (U+2014), en-dash (U+2013), horizontal ellipsis (U+2026), smart/curly quotes (U+201C, U+201D, U+2018, U+2019), or directional arrows (U+2190-U+21FF). Use ASCII equivalents instead: ` - ` (hyphen with surrounding spaces) for dashes, `...` for ellipsis, `"` and `'` for quotes, `->` and `<-` for arrows. Exception: Latin Extended characters (U+00C0-U+024F) are always permitted - this covers Spanish vowels with accents (U+00E0-U+00FA), n with tilde (U+00F1/U+00D1), and u/o with umlaut (U+00FC/U+00DC, U+00F6/U+00D6).
+
+## Formatting rules for generated content
+1. Generate the output in `UTF-8` encoding without BOM (`UTF-8`, no signature).
+2. Ensure the raw output is `UTF-8` encoded with no `EF BB BF` bytes at the beginning.
+
+{{ADO_SECTION}}
+## QA Pipeline
+
+Stages must run in order. Never start a stage unless its prerequisite is met.
+
+| Stage | Task | Skill | Prerequisite |
+|---|---|---|---|
+| 1 | Analyze module | `.github/skills/qa-module-analysis/SKILL.md` | None |
+| 2 | Generate specifications | `.github/skills/qa-spec-generation/SKILL.md` | 00-inventory.md exists |
+| 3 | Generate test plan | `.github/skills/qa-test-plan/SKILL.md` | 05-test-scenarios.md exists |
+| 4 | Generate test cases | `.github/skills/qa-test-cases/SKILL.md` | Test plan exists |
+| 5 | Generate automation | `.github/skills/qa-automation/SKILL.md` | Specs approved, no PENDING-CODE |
+| 5b | Stabilize failing tests | `.github/skills/qa-test-stabilization/SKILL.md` | Failing tests exist |
+| 6 | Maintenance | `.github/skills/qa-maintenance/SKILL.md` | Application change delivered |
+| — | ADO integration | `.github/skills/qa-ado-integration/SKILL.md` | ADO enabled in config |
+
+## Project KB
+1. `qa/README.md`          — The Living Index: module status, sprint history, blockers, quick-start commands.
+2. `qa/memory/INDEX.md`    — Index of all memory files; load this before selecting which files to read.