ma-agents 2.22.1 → 3.0.0

package/lib/bmad-cache/tea/docs/explanation/tea-overview.md

@@ -343,7 +343,7 @@ Production-ready fixtures and utilities that enhance TEA workflows.
 Production-ready contract testing utilities that reduce raw Pact.js boilerplate and standardize provider verification patterns.
 
 - Install: `npm install -D @seontechnologies/pactjs-utils @pact-foundation/pact`
-- Config: `tea_use_pactjs_utils: true` (default is `true`)
+- Config: `tea_use_pactjs_utils: true` (default is `false`, opt in only when you want Pact-aware workflows)
 - Impacts: `framework`, `atdd`, `automate`, `test-design`, `test-review`, `ci`
 - Utilities include: createProviderState, toJsonMap, setJsonBody, setJsonContent, buildVerifierOptions, buildMessageVerifierOptions, createRequestFilter, noOpRequestFilter, handlePactBrokerUrlAndSelectors, getProviderVersionTags
 - Supports local monorepo flow (`pactUrls`) and remote broker flow (`PACT_BROKER_BASE_URL`, `PACT_BROKER_TOKEN`)
@@ -386,12 +386,12 @@ Optional MCP integration for design-time broker interaction in contract testing
 
 **Configuration** (`_bmad/tea/config.yaml`):
 
-    tea_pact_mcp: "mcp"  # mcp | none
+    tea_pact_mcp: "none"  # none | mcp
 
 | Mode   | What happens                                                                                                        |
 | ------ | ------------------------------------------------------------------------------------------------------------------- |
 | `mcp`  | TEA can use SmartBear MCP tools for provider-state discovery, test review support, can-i-deploy, and matrix checks. |
-| `none` | TEA uses CLI/script guidance only for broker interactions.                                                          |
+| `none` | Default. TEA skips broker/MCP integration entirely unless you explicitly enable it.                                 |
 
 **Setup:**
 

package/lib/bmad-cache/tea/docs/glossary/index.md

@@ -133,7 +133,7 @@ Terminology reference for Test Architect (TEA).
 | **Epic-Level Test Design**   | Test planning per epic (Phase 4) focusing on risk assessment, priorities, and coverage strategy for that specific epic.                                                                                                      |
 | **Fixture Architecture**     | Pattern of building pure functions first, then wrapping in framework-specific fixtures for testability, reusability, and composition.                                                                                        |
 | **Gate Decision**            | Go/no-go decision for release with four outcomes: PASS ✅ (ready), CONCERNS ⚠️ (proceed with mitigation), FAIL ❌ (blocked), WAIVED ⏭️ (approved despite issues).                                                            |
-| **Knowledge Fragment**       | Individual markdown file in TEA's knowledge base covering a specific testing pattern or practice (35 fragments total).                                                                                                       |
+| **Knowledge Fragment**       | Individual markdown file in TEA's knowledge base covering a specific testing pattern or practice (42 fragments total).                                                                                                       |
 | **Browser Automation**       | Playwright CLI and/or MCP servers enabling live browser interaction during test generation. CLI provides token-efficient stateless commands; MCP provides rich stateful automation. Configured via `tea_browser_automation`. |
 | **Network-First Pattern**    | Testing pattern that waits for actual network responses instead of fixed timeouts to avoid race conditions and flakiness.                                                                                                    |
 | **NFR Assessment**           | Validation of non-functional requirements (security, performance, reliability, maintainability) with evidence-based decisions.                                                                                               |

package/lib/bmad-cache/tea/docs/how-to/customization/extend-tea-with-custom-workflows.md

@@ -0,0 +1,73 @@
+---
+title: 'Extend TEA with Custom Workflows'
+description: Add your own workflows to bmad-tea without patching TEA core
+---
+
+# Extend TEA with Custom Workflows
+
+TEA is a standalone module now. That means custom workflows are still supported, but they are not automatically folded into TEA core during updates.
+
+## The Supported Model
+
+Use one of these approaches:
+
+1. Package the workflow as custom content or a custom module.
+2. Add a menu entry to `bmad-tea` through BMAD agent customization.
+3. Reinstall or quick-update BMAD so the workflow and menu entry are registered.
+
+This keeps your TEA extensions compatible with upstream updates.
+
+## Recommended Approach
+
+### 1. Create the workflow as custom content
+
+Use BMad Builder or your own custom module structure to create a workflow that lives outside TEA core.
+
+- BMAD supports custom modules during install/update.
+- BMad Builder is the recommended path for creating reusable custom agents and workflows.
+
+See:
+
+- [How to Customize BMad](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/docs/how-to/customize-bmad.md)
+- [BMad Builder (BMB)](https://github.com/bmad-code-org/bmad-builder)
+
+### 2. Attach the workflow to `bmad-tea`
+
+After TEA is installed, use the generated agent customization file for `bmad-tea` under `_bmad/_config/agents/` and append a menu item:
+
+```yaml
+menu:
+  - trigger: my-custom-workflow
+    workflow: 'my-custom/workflows/my-custom-workflow.yaml'
+    description: My custom TEA extension workflow
+```
+
+This keeps the `bmad-tea` chat/menu experience intact while routing to your custom workflow.
+
+### 3. Reinstall or quick-update BMAD
+
+Run:
+
+```bash
+npx bmad-method install
+```
+
+Then choose a normal update path so BMAD re-applies the customization and refreshes the workflow registration.
+
+## What Not to Do
+
+- Do not patch TEA core files directly if the workflow is project-specific.
+- Do not rely on old embedded-TEA behavior where local workflows appeared to be attached automatically.
+- Do not keep custom workflow logic only in chat instructions. Put it in a real workflow or module so it survives updates.
+
+## When to Use Which Approach
+
+- **Project-specific workflow**: add custom content and attach it to `bmad-tea`
+- **Reusable internal workflow**: package it as a custom module
+- **Reusable public workflow**: consider publishing a standalone BMAD module
+
+## Related Docs
+
+- [TEA Command Reference](/docs/reference/commands.md)
+- [TEA Configuration Reference](/docs/reference/configuration.md)
+- [How to Customize BMad](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/docs/how-to/customize-bmad.md)

package/lib/bmad-cache/tea/docs/how-to/workflows/teach-me-testing.md

@@ -32,7 +32,7 @@ Use TEA's `teach-me-testing` workflow (TEA Academy) to learn testing progressive
 4. **Test Design (60 min)** - Risk assessment and coverage planning workflow
 5. **ATDD & Automate (60 min)** - TDD red-green approach, test generation
 6. **Quality & Trace (45 min)** - Test review (5 dimensions), requirements traceability
-7. **Advanced Patterns (ongoing)** - Explore 35 knowledge fragments on-demand
+7. **Advanced Patterns (ongoing)** - Explore 42 knowledge fragments on-demand
 
 ### What You'll Gain
 
@@ -140,7 +140,7 @@ Skip fundamentals, focus on:
 
 - Session 3: TEA architecture patterns
 - Session 4: Test Design workflow
-- Session 7: Advanced patterns (35 knowledge fragments)
+- Session 7: Advanced patterns (42 knowledge fragments)
 
 **Time commitment:** 3-4 hours (highly targeted)
 
@@ -220,13 +220,13 @@ Skip fundamentals, focus on:
 
 **Topics:**
 
-- Menu-driven exploration of 35 knowledge fragments
+- Menu-driven exploration of 42 knowledge fragments
 - 5 categories: Testing Patterns, Playwright Utils, Configuration & Governance, Quality Frameworks, Auth & Security
 - Deep-dive into specific patterns as needed
 - GitHub links for browsing source
 
-**Resources:** All 35 knowledge fragments
-**GitHub:** [Knowledge Base Repository](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/testarch/knowledge)
+**Resources:** All 42 knowledge fragments
+**GitHub:** [Knowledge Base Repository](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/agents/bmad-tea/resources/knowledge)
 
 ## Completion Certificate
 
@@ -243,7 +243,7 @@ Complete all 7 sessions to receive your TEA Academy completion certificate with:
 1. **Set aside dedicated time** - Each session requires focus (30-90 min)
 2. **Take your own notes** - Session notes are generated, but add personal insights
 3. **Apply immediately** - Practice concepts on your current project
-4. **Explore fragments** - Session 7 has 35 fragments for deep-dive topics
+4. **Explore fragments** - Session 7 has 42 fragments for deep-dive topics
 5. **Share with team** - Help others learn by sharing your experience
 6. **Don't rush** - Learning takes time, pause and resume as needed
 
@@ -295,7 +295,7 @@ After completing TEA Academy, you're ready to use:
 
 - **Documentation:** [TEA Overview](/explanation/tea-overview/)
 - **Knowledge Base:** [Knowledge Base Reference](/reference/knowledge-base/)
-- **GitHub Fragments:** [Knowledge Base Repository](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/testarch/knowledge)
+- **GitHub Fragments:** [Knowledge Base Repository](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/tree/main/src/agents/bmad-tea/resources/knowledge)
 
 ## Support
 

package/lib/bmad-cache/tea/docs/index.md

@@ -34,7 +34,7 @@ npx bmad-method install
 Then trigger workflows via chat:
 
 ```
-tea         # Load TEA agent
+bmad-tea    # Load TEA agent/menu
 test-design # Run Test Design workflow
 ```
 
@@ -46,6 +46,7 @@ Pick a path:
 - **TEA Lite**: Start with [Test Automation](/how-to/workflows/run-automate) only (30 minutes)
 - **Full TEA**: Start with the [TEA Overview](/explanation/tea-overview) for the complete workflow map
 - **Enterprise**: Choose [Greenfield](/how-to/brownfield/use-tea-for-enterprise) or [Brownfield](/how-to/brownfield/use-tea-with-existing-tests)
+- **Custom Extensions**: See [Extend TEA with Custom Workflows](/how-to/customization/extend-tea-with-custom-workflows)
 
 ## Core Workflows
 

package/lib/bmad-cache/tea/docs/reference/commands.md

@@ -7,10 +7,13 @@ description: Quick reference for all 9 TEA workflows - inputs, outputs, and link
 
 Quick reference for all 9 TEA (Test Engineering Architect) workflows. For detailed step-by-step guides, see the how-to documentation.
 
+All workflows listed here are current and supported in TEA, including `nfr-assess`.
+
 **Invocation by tool:**
 
 - Claude Code / Cursor / Windsurf: use slash commands (for example, `/bmad:tea:automate`)
 - Codex: use `$` skills from `.agents/skills` (for example, `$bmad-tea-testarch-automate`)
+- Custom TEA extensions: package the workflow as custom content/module and attach it to `bmad-tea` via customization. See [Extend TEA with Custom Workflows](../how-to/customization/extend-tea-with-custom-workflows.md)
 
 ## Quick Index
 
@@ -55,7 +58,7 @@ Quick reference for all 9 TEA (Test Engineering Architect) workflows. For detail
 4. Test Design (60 min) - Risk assessment, coverage planning
 5. ATDD & Automate (60 min) - TDD red-green, test generation
 6. Quality & Trace (45 min) - Test review, traceability, metrics
-7. Advanced Patterns (ongoing) - 35 knowledge fragments exploration
+7. Advanced Patterns (ongoing) - 42 knowledge fragments exploration
 
 **Features:**
 

package/lib/bmad-cache/tea/docs/reference/configuration.md

@@ -30,8 +30,8 @@ user_skill_level: intermediate
 output_folder: _bmad-output
 test_artifacts: _bmad-output/test-artifacts
 tea_use_playwright_utils: true
-tea_use_pactjs_utils: true
-tea_pact_mcp: 'mcp'
+tea_use_pactjs_utils: false
+tea_pact_mcp: 'none'
 tea_browser_automation: 'auto'
 tea_execution_mode: 'auto'
 tea_capability_probe: true
@@ -135,7 +135,7 @@ npm install -D @seontechnologies/playwright-utils
 
 ### tea_use_pactjs_utils
 
-Enable Pact.js Utils integration for production-ready contract testing utilities.
+Enable Pact.js Utils integration for production-ready consumer-driven contract testing utilities.
 
 **Schema Location:** `src/module.yaml` (TEA module config)
 
@@ -143,12 +143,12 @@ Enable Pact.js Utils integration for production-ready contract testing utilities
 
 **Type:** `boolean`
 
-**Default:** `true`
+**Default:** `false`
 
 **Installer Prompt:**
 
 ```
-Enable Pact.js Utils integration for contract testing?
+Enable Pact.js Utils for consumer-driven contract testing?
 ```
 
 **Purpose:** Enables TEA to:
@@ -168,6 +168,8 @@ Enable Pact.js Utils integration for contract testing?
 - `test-review` - Uses pactjs-utils provider/review patterns
 - `ci` - Adds contract-test stage and quality gates
 
+**Use this when:** your team already practices consumer-driven contract testing or wants TEA to scaffold Pact-aware patterns on purpose. Leave it off for projects that do not use Pact.
+
 **Example (Enable):**
 
 ```yaml
@@ -203,14 +205,14 @@ Pact MCP strategy for broker interaction during contract testing workflows.
 
 **Type:** `string`
 
-**Default:** `"mcp"`
+**Default:** `"none"`
 
 **Options:** `"mcp"` | `"none"`
 
 **Installer Prompt:**
 
 ```
-Enable SmartBear MCP for PactFlow/Pact Broker interaction?
+Enable SmartBear MCP for PactFlow/Pact Broker? Only needed if you already use a broker.
 ```
 
 **Purpose:** Controls whether TEA can use SmartBear MCP tools for:
@@ -226,6 +228,8 @@ Enable SmartBear MCP for PactFlow/Pact Broker interaction?
 - `test-review` - MCP-assisted pact review context
 - `ci` - MCP can-i-deploy/matrix guidance references
 
+**Use this when:** your project already uses PactFlow or Pact Broker and you want TEA to query broker state during review, generation, or gate guidance. Otherwise leave it set to `none`.
+
 **Prerequisites:**
 
 ```bash
@@ -960,8 +964,8 @@ project_name: my-project
 user_skill_level: beginner # or intermediate/expert
 output_folder: _bmad-output
 tea_use_playwright_utils: true # Recommended
-tea_use_pactjs_utils: true # Recommended - production-ready contract testing utilities
-tea_pact_mcp: 'mcp' # Recommended - SmartBear MCP for PactFlow/Broker interaction
+tea_use_pactjs_utils: false # Recommended unless you actively use contract testing
+tea_pact_mcp: 'none' # Recommended unless you already use PactFlow/Broker
 tea_browser_automation: 'auto' # Recommended
 tea_execution_mode: 'auto' # Recommended - capability-aware mode selection
 tea_capability_probe: true # Recommended - fallback safely if mode unsupported
@@ -970,7 +974,7 @@ tea_capability_probe: true # Recommended - fallback safely if mode unsupported
 **Why recommended:**
 
 - Playwright Utils: Production-ready fixtures and utilities
-- Pact.js Utils: Optional contract-testing acceleration for backend/fullstack services
+- Pact.js Utils: Leave disabled until the project explicitly needs contract testing
 - Browser automation (auto): Smart CLI/MCP selection with fallback
 - Together: The three-part stack (see [Testing as Engineering](/docs/explanation/testing-as-engineering.md))
 
@@ -1022,8 +1026,8 @@ tea_capability_probe: true
 project_name: monorepo
 output_folder: _bmad-output
 tea_use_playwright_utils: true
-tea_use_pactjs_utils: true
-tea_pact_mcp: 'mcp'
+tea_use_pactjs_utils: false
+tea_pact_mcp: 'none'
 tea_execution_mode: 'auto'
 ```
 
@@ -1061,10 +1065,10 @@ planning_artifacts: _bmad-output/planning-artifacts
 implementation_artifacts: _bmad-output/implementation-artifacts
 project_knowledge: docs
 
-# TEA Configuration (Recommended: Enable both for full stack)
+# TEA Configuration (Recommended baseline)
 tea_use_playwright_utils: true # Recommended - production-ready utilities
-tea_use_pactjs_utils: true # Recommended - production-ready contract testing utilities
-tea_pact_mcp: 'mcp' # Recommended - SmartBear MCP for broker integration
+tea_use_pactjs_utils: false # Opt in only if your service uses contract testing
+tea_pact_mcp: 'none' # Opt in only if your service uses PactFlow/Broker
 tea_browser_automation: 'auto' # Recommended - smart CLI/MCP selection
 tea_execution_mode: 'auto' # Recommended - capability-aware team/subagent fallback
 tea_capability_probe: true # Recommended - safe fallback
@@ -1098,6 +1102,24 @@ document_output_language: english
 
 ---
 
+### Contract Testing Setup (Opt-In)
+
+Use this profile only for services that already use Pact or want TEA to scaffold contract-testing patterns on purpose.
+
+```yaml
+tea_use_pactjs_utils: true
+tea_pact_mcp: 'none' # Use 'mcp' only if you already use PactFlow/Broker
+```
+
+If you also use PactFlow or Pact Broker:
+
+```yaml
+tea_use_pactjs_utils: true
+tea_pact_mcp: 'mcp'
+```
+
+---
+
 ## See Also
 
 ### How-To Guides