@devo-bmad-custom/agent-orchestration 1.0.0

package/src/bmm/workflows/generate-project-context/steps/step-03-complete.md

@@ -0,0 +1,235 @@
+# Step 3: Context Completion & Finalization
+
+## Context:
+
+- All rule categories from step-2 are complete; technology stack and versions are documented.
+- This is the final step — optimize and finalize the context file for AI agent consumption.
+
+## YOUR TASK:
+
+Complete the project context file, optimize it for LLM efficiency, and provide guidance for usage and maintenance.
+
+## COMPLETION SEQUENCE:
+
+### 1. Review Complete Context File
+
+Read the entire project context file and analyze:
+
+**Content Analysis:**
+
+- Total length and readability for LLMs
+- Clarity and specificity of rules
+- Coverage of all critical areas
+- Actionability of each rule
+
+**Structure Analysis:**
+
+- Logical organization of sections
+- Consistency of formatting
+- Absence of redundant or obvious information
+- Optimization for quick scanning
+
+### 2. Optimize for LLM Context
+
+Ensure the file is lean and efficient:
+
+**Content Optimization:**
+
+- Remove any redundant rules or obvious information
+- Combine related rules into concise bullet points
+- Use specific, actionable language
+- Ensure each rule provides unique value
+
+**Formatting Optimization:**
+
+- Use consistent markdown formatting
+- Implement clear section hierarchy
+- Ensure scannability with strategic use of bolding
+- Maintain readability while maximizing information density
+
+### 3. Final Content Structure
+
+Ensure the final structure follows this optimized format:
+
+```markdown
+# Project Context for AI Agents
+
+_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
+
+---
+
+## Technology Stack & Versions
+
+{{concise_technology_list}}
+
+## Critical Implementation Rules
+
+### Language-Specific Rules
+
+{{specific_language_rules}}
+
+### Framework-Specific Rules
+
+{{framework_patterns}}
+
+### Testing Rules
+
+{{testing_requirements}}
+
+### Code Quality & Style Rules
+
+{{style_and_quality_patterns}}
+
+### Development Workflow Rules
+
+{{workflow_patterns}}
+
+### Critical Don't-Miss Rules
+
+{{anti_patterns_and_edge_cases}}
+
+---
+
+## Usage Guidelines
+
+**For AI Agents:**
+
+- Read this file before implementing any code
+- Follow ALL rules exactly as documented
+- When in doubt, prefer the more restrictive option
+- Update this file if new patterns emerge
+
+**For Humans:**
+
+- Keep this file lean and focused on agent needs
+- Update when technology stack changes
+- Review quarterly for outdated rules
+- Remove rules that become obvious over time
+
+Last Updated: {{date}}
+```
+
+### 4. Present Completion Summary
+
+Based on user skill level, present the completion:
+
+**Expert Mode:**
+"Project context complete. Optimized for LLM consumption with {{rule_count}} critical rules across {{section_count}} sections.
+
+File saved to: `{output_folder}/project-context.md`
+
+Ready for AI agent integration."
+
+**Intermediate Mode:**
+"Your project context is complete and optimized for AI agents!
+
+**What we created:**
+
+- {{rule_count}} critical implementation rules
+- Technology stack with exact versions
+- Framework-specific patterns and conventions
+- Testing and quality guidelines
+- Workflow and anti-pattern rules
+
+**Key benefits:**
+
+- AI agents will implement consistently with your standards
+- Reduced context switching and implementation errors
+- Clear guidance for unobvious project requirements
+
+**Next steps:**
+
+- AI agents should read this file before implementing
+- Update as your project evolves
+- Review periodically for optimization"
+
+**Beginner Mode:**
+"Excellent! Your project context guide is ready! 🎉
+
+**What this does:**
+Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
+
+**What's included:**
+
+- Exact technology versions to use
+- Critical coding rules they might miss
+- Testing and quality standards
+- Workflow patterns to follow
+
+**How AI agents use it:**
+They read this file before writing any code, ensuring everything they create follows your project's standards perfectly.
+
+Your project context is saved and ready to help agents implement consistently!"
+
+### 5. Final File Updates
+
+Update the project context file with completion information:
+
+**Frontmatter Update:**
+
+```yaml
+---
+project_name: '{{project_name}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+sections_completed:
+  ['technology_stack', 'language_rules', 'framework_rules', 'testing_rules', 'quality_rules', 'workflow_rules', 'anti_patterns']
+status: 'complete'
+rule_count: { { total_rules } }
+optimized_for_llm: true
+---
+```
+
+**Add Usage Section:**
+Append the usage guidelines from step 3 to complete the document.
+
+### 6. Completion Validation
+
+Final checks before completion:
+
+**Content Validation:**
+✅ All critical technology versions documented
+✅ Language-specific rules are specific and actionable
+✅ Framework rules cover project conventions
+✅ Testing rules ensure consistency
+✅ Code quality rules maintain standards
+✅ Workflow rules prevent conflicts
+✅ Anti-pattern rules prevent common mistakes
+
+**Format Validation:**
+✅ Content is lean and optimized for LLMs
+✅ Structure is logical and scannable
+✅ No redundant or obvious information
+✅ Consistent formatting throughout
+
+### 7. Completion Message
+
+Present final completion to user:
+
+"✅ **Project Context Generation Complete!**
+
+Your optimized project context file is ready at:
+`{output_folder}/project-context.md`
+
+**📊 Context Summary:**
+
+- {{rule_count}} critical rules for AI agents
+- {{section_count}} comprehensive sections
+- Optimized for LLM context efficiency
+- Ready for immediate agent integration
+
+**🎯 Key Benefits:**
+
+- Consistent implementation across all AI agents
+- Reduced common mistakes and edge cases
+- Clear guidance for project-specific patterns
+- Minimal LLM context usage
+
+**📋 Next Steps:**
+
+1. AI agents will automatically read this file when implementing
+2. Update this file when your technology stack or patterns evolve
+3. Review quarterly to optimize and remove outdated rules
+
+Your project context will help ensure high-quality, consistent implementation across all development work. Great work capturing your project's critical implementation requirements!"
+

package/src/bmm/workflows/generate-project-context/workflow.md

@@ -0,0 +1,49 @@
+---
+name: generate-project-context
+description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
+---
+
+# Generate Project Context Workflow
+
+**Goal:** Create a concise, optimized `project-context.md` file containing critical rules, patterns, and guidelines that AI agents must follow when implementing code. This file focuses on unobvious details that LLMs need to be reminded of.
+
+**Your Role:** You are a technical facilitator working with a peer to capture the essential implementation rules that will ensure consistent, high-quality code generation across all AI agents working on the project.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **micro-file architecture** for disciplined execution:
+
+- Each step is a self-contained file with embedded rules
+- Sequential progression with user control at each step
+- Document state tracked in frontmatter
+- Focus on lean, LLM-optimized content generation
+- You NEVER proceed to a step file if the current step file indicates the user must approve and indicate continuation.
+
+---
+
+## INITIALIZATION
+
+### Configuration Loading
+
+Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
+
+- `project_name`, `output_folder`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Paths
+
+- `installed_path` = `{project-root}/_bmad/bmm/workflows/generate-project-context`
+- `template_path` = `{installed_path}/project-context-template.md`
+- `output_file` = `{output_folder}/project-context.md`
+
+---
+
+## EXECUTION
+
+Load and execute `{project-root}/_bmad/bmm/workflows/generate-project-context/steps/step-01-discover.md` to begin the workflow.
+
+**Note:** Input document discovery and initialization protocols are handled in step-01-discover.md.

package/src/bmm/workflows/qa/automate/workflow.yaml

@@ -0,0 +1,233 @@
+id: qa-automate
+name: QA Automate
+description: >
+  Playwright-first E2E test workflow. Builds a test plan from specs or diffs,
+  generates .spec.ts test files, authenticates via dev/user quick-login + Dev Kit,
+  runs tests via playwright-cli (MCP fallback), captures annotated screenshots,
+  and produces an HTML gallery report. Optionally promotes specs to tests/ for
+  permanent tracking.
+
+phases:
+  - id: phase-0
+    name: Auth Setup
+    auth_reference: |
+      ## Auth Reference
+      - Login page at localhost:3000 has TWO quick-login buttons: "Login as Dev" and "Login as User" — single click, no credentials needed
+      - Default to "Login as Dev" for most scenarios; use "Login as User" for user-perspective flows
+      - If quick-login buttons absent: fall back to manual credential login
+      - Dev Kit button (visible when logged in): (1) Emulate user — switch acting-as context, (2) Edit permissions — modify any user's permission flags, (3) Add money/XP — inject currency/XP to set preconditions
+      - Always configure preconditions via Dev Kit before scenarios requiring specific state
+      - Save auth state after login: playwright-cli state-save {feature-slug}/auth.json
+    description: >
+      Navigate to localhost:3000. Click "Login as Dev" (default) or "Login as User"
+      for user-perspective flows. If quick-login buttons are absent, fall back to
+      manual credential login (check config or prompt user).
+      After login: playwright-cli state-save _bmad-output/qa-tests/{feature-slug}/auth.json
+      Store auth state path as session variable auth_state_path.
+      Use Dev Kit (visible when logged in) to configure per-scenario preconditions:
+        - Emulate user: switch acting-as context
+        - Edit permissions: modify user permission flags
+        - Add money/XP: inject precondition values
+    outputs:
+      - _bmad-output/qa-tests/{feature-slug}/auth.json
+
+  - id: phase-1
+    name: Test Plan
+    description: >
+      Analyze plan files (PRDs, epics, stories) and/or recently edited code.
+      Derive feature-slug deterministically:
+        1. Take plan filename stem or story title
+        2. Lowercase, replace spaces/non-alphanumeric with hyphens
+        3. Truncate to 40 chars
+        4. Append - + first 4 hex chars of SHA-256 of full absolute path
+           Shell: echo -n "/full/path/to/file.md" | sha256sum | cut -c1-4
+        5. Example: user-profile-edit-a3f2
+      If no plan file: prompt user for a feature name to use as slug base.
+      Output test-plan.md using the schema below.
+    outputs:
+      - _bmad-output/qa-tests/{feature-slug}/test-plan.md
+    schema: |
+      # Test Plan: {feature-slug}
+      Generated: {ISO-8601 datetime}
+      Source: {plan file path or "manual"}
+      Auth strategy: {dev-login | user-login | state-file}
+      Auth state file: {absolute path to auth.json}
+
+      ## Scenarios
+      ### {n}. {Scenario Title}
+      - URL: {starting URL}
+      - Pre-conditions: {Dev Kit setup required, e.g. "set user XP to 500"}
+      - Steps: {numbered list}
+      - Expected outcome: {assertion}
+      - Screenshot triggers: {list of moments to capture}
+
+  - id: phase-2
+    name: Test File Generation
+    description: >
+      Write .spec.ts playwright test files into _bmad-output/qa-tests/{feature-slug}/tests/.
+      Each file must:
+        - Import from @playwright/test
+        - Use baseURL from playwright.config.ts (localhost:3000)
+        - Load auth state at test.use() block:
+            test.use({ storageState: '{absolute-project-root}/_bmad-output/qa-tests/{feature-slug}/auth.json' });
+        - Substitute {absolute-project-root} with resolved project root at generation time
+    outputs:
+      - _bmad-output/qa-tests/{feature-slug}/tests/*.spec.ts
+
+  - id: phase-3
+    name: Execution Preflight + Run
+    description: >
+      Preflight 1 (CLI binary): playwright-cli --version
+        - Exit 0 → playwright_tool=cli
+        - Fails → playwright_tool=mcp
+      Preflight 2 (App reachable): curl localhost:3000 with 3 retries, 3s apart, 10s timeout
+        - Unreachable → ABORT: "App not reachable at localhost:3000 — start Docker containers first."
+      Double-failure (CLI unavailable AND MCP unconfigured):
+        ABORT: "Neither playwright-cli nor playwright MCP is available.
+                Install playwright-cli or configure the playwright MCP server, then retry."
+      Run tests:
+        - playwright-cli mode: playwright-cli open localhost:3000, execute scenario steps, screenshot
+        - MCP fallback: browser_navigate, browser_click, browser_fill_form, browser_take_screenshot, browser_snapshot
+      Document playwright_tool used in report header.
+
+  - id: phase-4
+    name: Screenshots
+    description: >
+      For every screenshot taken, record a JSON entry and append to manifest.json.
+      Failure screenshots included with status: "failed" — do NOT block report.
+    outputs:
+      - _bmad-output/qa-tests/{feature-slug}/screenshots/{nn}-{step-name}.png
+      - _bmad-output/qa-tests/{feature-slug}/screenshots/manifest.json
+    manifest_entry_schema: |
+      {
+        "filename": "01-login-page.png",
+        "scenario": "{scenario title}",
+        "step": "{step description}",
+        "why": "{why this screenshot was taken}",
+        "shows": "{what is visible in the screenshot}",
+        "tests": "{what feature/assertion this screenshot proves}",
+        "status": "passed | failed",
+        "timestamp": "{ISO-8601}"
+      }
+
+  - id: phase-5
+    name: HTML Gallery Report
+    description: >
+      Read _bmad-output/qa-tests/{feature-slug}/screenshots/manifest.json.
+      Iterate over each entry; render one card per entry into the HTML template,
+      substituting all {placeholder} values from corresponding JSON fields.
+      Compute summary totals from manifest:
+        total = manifest.length
+        passed = count where status=passed
+        failed = count where status=failed
+        duration = last_timestamp minus first_timestamp
+      Card classes: passed entry → "card passed" + "badge pass", failed → "card failed" + "badge fail"
+      Write completed HTML to _bmad-output/qa-tests/{feature-slug}/report.html.
+    outputs:
+      - _bmad-output/qa-tests/{feature-slug}/report.html
+
+  - id: phase-6
+    name: Open Report
+    description: >
+      Detect platform:
+        if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "cygwin" ]] || command -v cmd.exe &>/dev/null
+          then PLATFORM=windows
+        elif [[ "$(uname)" == "Darwin" ]]
+          then PLATFORM=mac
+        else PLATFORM=linux
+        fi
+      Open using absolute path to report.html:
+        Windows: start "" "C:\absolute\path\to\report.html"
+        Mac:     open /absolute/path/to/report.html
+        Linux:   xdg-open /absolute/path/to/report.html
+      Always print absolute path to terminal regardless of platform.
+
+  - id: phase-7
+    name: Promote (optional)
+    description: >
+      Present user with list of generated .spec.ts files.
+      Ask: "Which test files would you like to promote to tests/ for permanent tracking?"
+      For each selected file, before copying:
+        - Check if file exists in tests/: if [ -f "tests/{filename}" ]
+        - If exists → prompt: "[O]verwrite / [R]ename with timestamp suffix
+          (e.g. auth-flow-20260309.spec.ts) / [S]kip this file" — default: Skip
+      On successful copy: "✅ Promoted {filename} to tests/"
+      NOTE: This write to {project-root}/tests/ is explicitly exempted from the
+      _bmad-output/qa-tests/ write constraint.
+      If user skips: session complete.
+
+html_template: |
+  <!DOCTYPE html>
+  <html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>QA Report — {feature-slug}</title>
+    <style>
+      :root {
+        --pass: #22c55e; --fail: #ef4444; --bg: #0f0f11; --surface: #1a1a1f;
+        --border: #2a2a35; --text: #e2e2e8; --muted: #6b6b80; --accent: #7c3aed;
+      }
+      * { box-sizing: border-box; margin: 0; padding: 0; }
+      body { background: var(--bg); color: var(--text); font-family: 'Inter', system-ui, sans-serif; padding: 2rem; }
+      .report-header { border-bottom: 1px solid var(--border); padding-bottom: 1.5rem; margin-bottom: 2rem; }
+      .report-header h1 { font-size: 1.5rem; font-weight: 700; margin-bottom: 0.25rem; }
+      .report-header .meta { color: var(--muted); font-size: 0.875rem; }
+      .summary { display: flex; gap: 1rem; margin-bottom: 2rem; flex-wrap: wrap; }
+      .summary-card { background: var(--surface); border: 1px solid var(--border); border-radius: 0.5rem; padding: 1rem 1.5rem; min-width: 140px; }
+      .summary-card .label { font-size: 0.75rem; color: var(--muted); text-transform: uppercase; letter-spacing: 0.05em; }
+      .summary-card .value { font-size: 1.75rem; font-weight: 700; margin-top: 0.25rem; }
+      .summary-card.pass .value { color: var(--pass); }
+      .summary-card.fail .value { color: var(--fail); }
+      .gallery { display: grid; grid-template-columns: repeat(auto-fill, minmax(340px, 1fr)); gap: 1.5rem; }
+      .card.passed { background: var(--surface); border: 1px solid var(--border); border-radius: 0.75rem; overflow: hidden; }
+      .card.failed { background: var(--surface); border: 1px solid var(--fail); border-radius: 0.75rem; overflow: hidden; }
+      .card img { width: 100%; display: block; aspect-ratio: 16/10; object-fit: cover; }
+      .img-wrap { position: relative; }
+      .badge { position: absolute; top: 0.5rem; right: 0.5rem; padding: 0.25rem 0.6rem; border-radius: 999px; font-size: 0.7rem; font-weight: 700; text-transform: uppercase; letter-spacing: 0.05em; }
+      .badge.pass { background: var(--pass); color: #000; }
+      .badge.fail { background: var(--fail); color: #fff; }
+      .card-body { padding: 1rem; }
+      .card-scenario { font-size: 0.7rem; color: var(--accent); text-transform: uppercase; font-weight: 600; letter-spacing: 0.05em; margin-bottom: 0.4rem; }
+      .card-step { font-size: 0.875rem; font-weight: 600; margin-bottom: 0.75rem; }
+      .card-meta { display: flex; flex-direction: column; gap: 0.5rem; }
+      .card-meta-row { display: flex; gap: 0.5rem; font-size: 0.8rem; }
+      .card-meta-row .key { color: var(--muted); min-width: 52px; flex-shrink: 0; }
+      .card-meta-row .val { color: var(--text); }
+      .timestamp { font-size: 0.7rem; color: var(--muted); margin-top: 0.75rem; }
+    </style>
+  </head>
+  <body>
+    <div class="report-header">
+      <h1>QA Report — {feature-slug}</h1>
+      <div class="meta">Run: {timestamp} &nbsp;|&nbsp; Source: {plan-file} &nbsp;|&nbsp; Tool: {playwright_tool}</div>
+    </div>
+    <div class="summary">
+      <div class="summary-card"><div class="label">Total</div><div class="value">{total}</div></div>
+      <div class="summary-card pass"><div class="label">Passed</div><div class="value">{passed}</div></div>
+      <div class="summary-card fail"><div class="label">Failed</div><div class="value">{failed}</div></div>
+      <div class="summary-card"><div class="label">Duration</div><div class="value" style="font-size:1.2rem">{duration}</div></div>
+    </div>
+    <div class="gallery">
+      <!-- FOR EACH entry in manifest.json: render one card block below.
+           passed entry: class="card passed", badge class="badge pass", label="PASSED"
+           failed entry: class="card failed", badge class="badge fail",  label="FAILED" -->
+      <div class="card {passed|failed}">
+        <div class="img-wrap">
+          <img src="screenshots/{filename}" alt="{step}" loading="lazy" />
+          <span class="badge {pass|fail}">{PASSED|FAILED}</span>
+        </div>
+        <div class="card-body">
+          <div class="card-scenario">{scenario}</div>
+          <div class="card-step">{step}</div>
+          <div class="card-meta">
+            <div class="card-meta-row"><span class="key">Why</span><span class="val">{why}</span></div>
+            <div class="card-meta-row"><span class="key">Shows</span><span class="val">{shows}</span></div>
+            <div class="card-meta-row"><span class="key">Tests</span><span class="val">{tests}</span></div>
+          </div>
+          <div class="timestamp">{timestamp}</div>
+        </div>
+      </div>
+    </div>
+  </body>
+  </html>

package/src/bmm/workflows/qa-generate-e2e-tests/checklist.md

@@ -0,0 +1,33 @@
+# Quinn Automate - Validation Checklist
+
+## Test Generation
+
+- [ ] API tests generated (if applicable)
+- [ ] E2E tests generated (if UI exists)
+- [ ] Tests use standard test framework APIs
+- [ ] Tests cover happy path
+- [ ] Tests cover 1-2 critical error cases
+
+## Test Quality
+
+- [ ] All generated tests run successfully
+- [ ] Tests use proper locators (semantic, accessible)
+- [ ] Tests have clear descriptions
+- [ ] No hardcoded waits or sleeps
+- [ ] Tests are independent (no order dependency)
+
+## Output
+
+- [ ] Test summary created
+- [ ] Tests saved to appropriate directories
+- [ ] Summary includes coverage metrics
+
+## Validation
+
+Run the tests using your project's test command.
+
+**Expected**: All tests pass ✅
+
+---
+
+**Need more comprehensive testing?** Install [Test Architect (TEA)](https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/) for advanced workflows.

package/src/bmm/workflows/qa-generate-e2e-tests/instructions.md

@@ -0,0 +1,110 @@
+# Quinn QA - Automate
+
+**Goal**: Generate automated API and E2E tests for implemented code.
+
+**Scope**: This workflow generates tests ONLY. It does **not** perform code review or story validation (use Code Review `CR` for that).
+
+## Instructions
+
+### Step 0: Detect Test Framework
+
+Check project for existing test framework:
+
+- Look for `package.json` dependencies (playwright, jest, vitest, cypress, etc.)
+- Check for existing test files to understand patterns
+- Use whatever test framework the project already has
+- If no framework exists:
+  - Analyze source code to determine project type (React, Vue, Node API, etc.)
+  - Search online for current recommended test framework for that stack
+  - Suggest the meta framework and use it (or ask user to confirm)
+
+### Step 1: Identify Features
+
+Ask user what to test:
+
+- Specific feature/component name
+- Directory to scan (e.g., `src/components/`)
+- Or auto-discover features in the codebase
+
+### Step 2: Generate API Tests (if applicable)
+
+For API endpoints/services, generate tests that:
+
+- Test status codes (200, 400, 404, 500)
+- Validate response structure
+- Cover happy path + 1-2 error cases
+- Use project's existing test framework patterns
+
+### Step 3: Generate E2E Tests (if UI exists)
+
+For UI features, generate tests that:
+
+- Test user workflows end-to-end
+- Use semantic locators (roles, labels, text)
+- Focus on user interactions (clicks, form fills, navigation)
+- Assert visible outcomes
+- Keep tests linear and simple
+- Follow project's existing test patterns
+
+### Step 4: Run Tests
+
+Execute tests to verify they pass (use project's test command).
+
+If failures occur, fix them immediately.
+
+### Step 5: Create Summary
+
+Output markdown summary:
+
+```markdown
+# Test Automation Summary
+
+## Generated Tests
+
+### API Tests
+- [x] tests/api/endpoint.spec.ts - Endpoint validation
+
+### E2E Tests
+- [x] tests/e2e/feature.spec.ts - User workflow
+
+## Coverage
+- API endpoints: 5/10 covered
+- UI features: 3/8 covered
+
+## Next Steps
+- Run tests in CI
+- Add more edge cases as needed
+```
+
+## Keep It Simple
+
+**Do:**
+
+- Use standard test framework APIs
+- Focus on happy path + critical errors
+- Write readable, maintainable tests
+- Run tests to verify they pass
+
+**Avoid:**
+
+- Complex fixture composition
+- Over-engineering
+- Unnecessary abstractions
+
+**For Advanced Features:**
+
+If the project needs:
+
+- Risk-based test strategy
+- Test design planning
+- Quality gates and NFR assessment
+- Comprehensive coverage analysis
+- Advanced testing patterns and utilities
+
+→ **Install Test Architect (TEA) module**: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
+
+## Output
+
+Save summary to: `{implementation_artifacts}/tests/test-summary.md`
+
+**Done!** Tests generated and verified.