ma-agents 3.12.3 → 3.13.1

package/lib/bmad-cache/gds/src/workflows/3-technical/gds-game-architecture/engine-mcps.yaml

@@ -60,6 +60,29 @@ engine_mcps:
         license: "MIT"
         benefit_summary: "Broad Unity version support (2021.3+) with natural language control and fast batch operations for AI-driven scene building."
 
+      unity_mcp_official:
+        name: "Unity MCP (Official)"
+        repo: "Unity AI Assistant package (com.unity.ai.assistant)"
+        search_term: "Unity MCP official Unity AI Assistant docs"
+        description: "Unity's first-party MCP server, bundled with the Unity AI Assistant, exposing the Editor to external AI clients"
+        capabilities:
+          - "Manage scenes and GameObjects"
+          - "Run asset operations"
+          - "Edit scripts"
+          - "Read Unity console output"
+          - "Automate in-editor tasks"
+        install_type: "Bundled in the Unity AI Assistant package - no separate server"
+        install_steps:
+          - "Open Edit > Project Settings > AI > Unity MCP"
+          - "The MCP bridge starts automatically with the Editor"
+          - "Approve direct connections from your AI client"
+        requirements: "Unity 6+ with the AI Assistant package; paid Unity AI subscription (~$10/month - verify current pricing)"
+        supported_clients: ["Claude Code", "Cursor"]
+        license: "Proprietary (Unity)"
+        docs: "https://docs.unity3d.com/Packages/com.unity.ai.assistant@2.8/manual/integration/unity-mcp-overview.html"
+        note: "Requires a paid Unity AI subscription. The free open-source MCPs (mcp_unity, unity_mcp_coplay) cover the same workflow - prefer those unless the user already pays for Unity AI."
+        benefit_summary: "First-party MCP built into the Unity Editor, but gated behind a paid Unity AI subscription; the open-source alternatives are free."
+
   unreal:
     engine: "Unreal Engine"
     mcps:
@@ -162,6 +185,53 @@ engine_mcps:
         license: "MIT"
         benefit_summary: "Full bidirectional Godot integration - AI agents can read and write scripts, scenes, and nodes directly."
 
+      godot_mcp_gopeak:
+        name: "GoPeak (HaD0Yun)"
+        repo: "HaD0Yun/Gopeak-godot-mcp"
+        search_term: "Gopeak godot mcp github"
+        description: "Comprehensive MCP server for Godot 4.x with ~95+ tools spanning the full edit-run-inspect-fix workflow"
+        capabilities:
+          - "Find, launch, and manage Godot projects and editor execution"
+          - "Create and modify scenes and GDScript files with typed properties"
+          - "Work with resources, materials, shaders, and imports"
+          - "Debug via logs, LSP diagnostics, DAP breakpoints, and runtime inspection"
+          - "Capture screenshots and inspect the live scene tree"
+          - "Inject input and call runtime methods for testing"
+          - "Discover tools through a catalog with dynamic capability groups"
+          - "Access ClassDB introspection and a CC0 asset library"
+        install_type: "Node.js MCP server (npx, no Godot plugin needed)"
+        install_steps:
+          - "Run via 'npx -y gopeak' (or 'npm install -g gopeak')"
+          - "Configure your MCP client with paths to the Godot executable and a tool profile"
+          - "Choose a tool exposure profile: compact, full, or legacy"
+        requirements: "Godot 4.x (4.4+ for UID features), Node.js"
+        supported_clients: ["Claude Desktop", "Claude Code", "Cursor"]
+        license: "MIT"
+        benefit_summary: "The most capable Godot MCP - ~95+ tools, active development, and a one-command npx launch with no Godot plugin required."
+
+      godot_mcp_tugcantopaloglu:
+        name: "Godot MCP (tugcantopaloglu)"
+        repo: "tugcantopaloglu/godot-mcp"
+        search_term: "tugcantopaloglu godot-mcp github"
+        description: "MCP server for Godot 4.x with 149 tools, including runtime GDScript execution over a TCP channel"
+        capabilities:
+          - "Execute arbitrary GDScript at runtime; manipulate nodes and signals"
+          - "Control animation, input, raycasting, audio, and video playback"
+          - "Headless scene parsing, project-setting edits, and resource creation"
+          - "3D/2D rendering, physics joints, skeletal animation, particles, and shaders"
+          - "UI theming and networking (HTTP, WebSocket, multiplayer)"
+        install_type: "Node.js MCP server + runtime GDScript autoload (no editor plugin)"
+        install_steps:
+          - "git clone https://github.com/tugcantopaloglu/godot-mcp.git"
+          - "cd godot-mcp && npm install && npm run build"
+          - "Copy the MCP interaction server GDScript into your project"
+          - "Register it as an autoload named 'McpInteractionServer' in Project Settings"
+          - "Configure your MCP client with the built server path"
+        requirements: "Godot 4.x (4.4+ for UID features), Node.js 18+; TCP port 9090 for runtime tools"
+        supported_clients: ["Claude Code", "Cursor", "Cline"]
+        license: "MIT"
+        benefit_summary: "Largest tool surface (149 tools) with runtime GDScript execution over TCP - strong for live in-game AI interaction and testing."
+
       godot_mcp_docs:
         name: "Godot MCP Docs"
         repo: "Nihilantropy/godot-mcp-docs"
@@ -181,6 +251,55 @@ engine_mcps:
         license: "MIT"
         benefit_summary: "AI agents get access to the full Godot documentation for accurate API usage without relying on training data."
 
+  roblox:
+    engine: "Roblox Studio"
+    mcps:
+      roblox_studio_mcp:
+        name: "Roblox Studio MCP (Official)"
+        repo: "Official Roblox Studio plugin — not a community GitHub repo"
+        search_term: "Roblox Studio MCP plugin Claude Code setup"
+        description: "First-party MCP server built into Roblox Studio. Gives AI agents direct access to the DataModel, scripts, live Luau execution, asset generation, and playtest control — no copy-pasting needed."
+        capabilities:
+          # DataModel exploration
+          - "Investigate the place in parallel and return a compact summary (explore_subagent)"
+          - "Explore the instance hierarchy as a flat JSON array (search_game_tree)"
+          - "Inspect any Instance's properties, attributes, and children in detail (inspect_instance)"
+          # Script tools
+          - "Read Scripts, LocalScripts, and ModuleScripts with line numbers (script_read)"
+          - "Search all script contents by string or Luau pattern (script_grep)"
+          - "Find scripts by name via fuzzy match (script_search)"
+          - "Apply multiple edits to a script atomically (multi_edit)"
+          # Live execution
+          - "Execute arbitrary Luau in the live game context and return the result (execute_luau)"
+          - "Retrieve output logs while the game is running (console_output)"
+          # Playtest control
+          - "Start or stop a playtesting session (start_stop_play)"
+          - "Spawn a test character that runs through gameplay scenarios in its own context (playtest_subagent)"
+          - "Move the player character to a position or Instance during play (character_navigation)"
+          - "Simulate key presses, key holds, and text input (keyboard_input)"
+          - "Simulate mouse clicks, movement, and scrolling (mouse_input)"
+          # Visual
+          - "Capture the current Studio viewport in Play mode (screen_capture)"
+          # AI asset generation
+          - "Generate a textured 3D mesh from a text prompt (generate_mesh)"
+          - "Generate a custom material or texture (generate_material)"
+          - "Generate custom procedural models that scale and adapt automatically (generate_procedural_model)"
+          - "Insert assets, plugins, and models from the Creator Store (insert_from_creator_store)"
+          # Multi-studio
+          - "List all connected Studio instances and switch the active one (list_roblox_studios, set_active_studio)"
+        install_type: "Roblox Studio Plugin (official, bundled with Studio or available via Plugin Manager)"
+        install_steps:
+          - "Open Roblox Studio"
+          - "Install the MCP plugin from the Studio Plugin Manager if not already present"
+          - "The plugin starts a local MCP server when Studio is running"
+          - "In Claude Code: claude mcp add roblox-studio <server-command> (verify exact command via Roblox docs)"
+          - "Confirm the active Studio instance with list_roblox_studios before making edits"
+        requirements: "Roblox Studio (latest version recommended)"
+        supported_clients: ["Claude Code", "Claude Desktop"]
+        license: "Proprietary (Roblox)"
+        note: "Unlike community MCPs for other engines, this is a first-party tool maintained by Roblox. The execute_luau tool — which runs arbitrary Luau in the live game context — is a capability no community engine MCP currently matches. Verify install steps via current Roblox documentation, as the plugin ecosystem evolves."
+        benefit_summary: "The official Roblox Studio MCP gives AI agents 21 tools covering the full edit → script → run → inspect → fix loop. The standout capability is execute_luau: run assertions, inspect live state, fire RemoteEvents, and verify game behavior directly from the AI session without leaving Claude Code."
+
   general:
     engine: "Any"
     description: "General-purpose MCPs useful for any game engine"
@@ -215,9 +334,12 @@ recommendation_rules:
     note: "When multiple MCPs exist for an engine, present the top 1-2 options and let the user choose"
     unity_default: "mcp_unity"
     unity_alternative: "unity_mcp_coplay"
+    unity_official_note: "unity_mcp_official exists but needs a paid Unity AI subscription - recommend it only when the user already has one"
     unreal_default: "unreal_mcp"
-    godot_default: "godot_mcp_bradypp"
-    godot_alternative: "godot_mcp_ee0pdt"
+    godot_default: "godot_mcp_gopeak"
+    godot_alternative: "godot_mcp_tugcantopaloglu"
+    roblox_default: "roblox_studio_mcp"
+    roblox_note: "Only one MCP exists for Roblox and it is first-party and official — recommend it unconditionally"
 
   recommend_if:
     godot_docs_needed:

package/lib/bmad-cache/gds/src/workflows/4-production/gds-investigate/customize.toml

@@ -0,0 +1,62 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-investigate. Mirrors the
+# agent customization shape under the [workflow] namespace.
+
+[workflow]
+
+# --- Configurable below. Overrides merge per BMad structural rules: ---
+#   scalars: override wins • arrays (persistent_facts, activation_steps_*): append
+#   arrays-of-tables with `code`/`id`: replace matching items, append new ones.
+
+# Steps to run before the standard activation (config load, greet).
+# Overrides append. Use for pre-flight loads, compliance checks, etc.
+
+activation_steps_prepend = []
+
+# Steps to run after greet but before the workflow begins.
+# Overrides append. Use for context-heavy setup that should happen
+# once the user has been acknowledged.
+
+activation_steps_append = []
+
+# Persistent facts the workflow keeps in mind for the whole run.
+# Use for citation conventions (path:line vs path#L42), grading-scale
+# overrides (ITIL severity 1-5 instead of High/Medium/Low), tone
+# directives (engineering vs exec-facing), or compliance constraints
+# the case file must respect.
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Use ITIL severity 1-5 instead of High/Medium/Low for confidence."
+#   - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
+#     (glob patterns are supported; the file's contents are loaded and treated as facts).
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+]
+
+# Scalar: path to the case-file template, resolved from the skill root.
+# Override to point at an org-shaped template (compliance sections,
+# SLA fields, post-mortem hooks, ITIL fields).
+
+case_file_template = "references/case-file-template.md"
+
+# Scalar: subdirectory under {implementation_artifacts} where case files land.
+# Override for org taxonomies (forensics/, cases/, incidents/, bug-bash/).
+
+case_file_subdir = "investigations"
+
+# Scalar: filename pattern for new case files. {slug} expands to the
+# ticket ID or a short user-agreed name.
+
+case_file_filename = "{slug}-investigation.md"
+
+# Scalar: executed when the workflow finalizes the case file at Outcome 5,
+# after the conclusion is presented. Override wins. Use for post-case
+# automation: post the case to Slack/Teams, push fields back to ticketing,
+# link the case to a sprint, trigger a follow-up retro.
+# Leave empty for no custom post-completion behavior.
+
+on_complete = ""

package/lib/bmad-cache/tea/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "bmad-method-test-architecture-enterprise",
       "source": "./",
       "description": "Master Test Architect module for quality strategy, test automation, CI/CD quality gates, and structured testing education. Part of the BMad Method ecosystem.",
-      "version": "1.15.1",
+      "version": "1.19.0",
       "author": {
         "name": "Murat K Ozcan (TEA Creator) & Brian (BMad) Madison"
       },

package/lib/bmad-cache/tea/.github/workflows/docs.yaml

@@ -25,14 +25,14 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
         with:
           fetch-depth: 0
 
       - name: Setup Node.js
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
-          node-version: "20"
+          node-version-file: ".nvmrc"
           cache: "npm"
 
       - name: Install root dependencies

package/lib/bmad-cache/tea/.github/workflows/quality.yaml

@@ -18,10 +18,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version-file: ".nvmrc"
           cache: "npm"
@@ -36,10 +36,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version-file: ".nvmrc"
           cache: "npm"
@@ -54,10 +54,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version-file: ".nvmrc"
           cache: "npm"
@@ -72,10 +72,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version-file: ".nvmrc"
           cache: "npm"
@@ -93,10 +93,10 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        uses: actions/checkout@v5
 
       - name: Setup Node
-        uses: actions/setup-node@v4
+        uses: actions/setup-node@v6
         with:
           node-version-file: ".nvmrc"
           cache: "npm"

package/lib/bmad-cache/tea/AGENTS.md

@@ -0,0 +1,31 @@
+# Repository Guidelines
+
+## Project Shape
+
+- Core TEA module content lives in `src/`.
+- Public documentation lives in `docs/`; the Starlight site consumes it through `website/`.
+- GitHub Actions workflows live in `.github/workflows/`.
+- Release metadata must stay synchronized across `package.json`, `package-lock.json`, and `.claude-plugin/marketplace.json`.
+
+## Common Commands
+
+- `npm test`: full quality gate used before release.
+- `npm run format:check`: Prettier check.
+- `npm run lint`: ESLint check.
+- `npm run lint:md`: markdownlint check.
+- `npm run docs:validate-links`: docs link validation.
+- `npm run docs:build`: full docs and site build.
+- `npm run test:release-metadata`: package/lockfile/marketplace version sync check.
+
+## Changelog Discipline
+
+- For any user-facing change, documentation change, workflow/CI change, release behavior change, or bug fix, update `CHANGELOG.md` in the same PR.
+- Put unreleased work under the top `## [Unreleased]` section using Keep a Changelog headings such as `Added`, `Changed`, `Fixed`, `Deprecated`, or `Removed`.
+- When preparing or repairing a stable release, convert the relevant `[Unreleased]` notes into an exact version section like `## [1.16.0] - YYYY-MM-DD`.
+- Do not leave release-worthy changes only in GitHub auto-generated notes. The publish workflow can fall back to `[Unreleased]`, but an exact version entry is preferred for stable releases.
+
+## PR Notes
+
+- Mention validation commands actually run.
+- For docs-only changes, at minimum run `npm run docs:validate-links`, `npm run lint:md`, and `npm run format:check`.
+- For workflow or release changes, run `npm run format:check`, `npm run lint:md`, `npm run lint`, and `npm run test:release-metadata`.

package/lib/bmad-cache/tea/CHANGELOG.md

@@ -5,6 +5,47 @@ All notable changes to the Test Architect (TEA) module will be documented in thi
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [Unreleased]
+
+### Changed
+
+- NFR workflow boundary clarified: `test-design` now owns NFR planning (thresholds, planned evidence, NFR-derived risks) and `nfr-assess` is reframed as NFR Evidence Audit — evaluating implementation evidence against planned thresholds after code exists.
+- `nfr-assess` step-02 now checks for an existing `test-design` NFR plan first and uses it as the primary threshold source, falling back to raw documents only for missing or UNKNOWN thresholds.
+- TEA agent menu gains a `GATE` routing intent that guides users through the release gate sequence (optional test-review → optional nfr-assess → trace Phase 2 gate) without merging those workflows.
+- NFR domains in `nfr-assess` corrected from "maintainability" to "scalability" to match the four parallel subagent domains (security, performance, reliability, scalability).
+- TEA phase table updated: `nfr-assess` marked optional at the Release phase.
+- NFR planning items in `test-design` step-05 output checklist conditioned on NFR scope.
+- Engagement models table: TEA Solo row for NFR Evidence Audit updated from No to Optional.
+- GitHub Actions workflow dependencies upgraded to Node 24-compatible major versions:
+  - `actions/checkout@v5`
+  - `actions/setup-node@v6`
+  - `actions/create-github-app-token@v3`
+- Publish releases now use `[Unreleased]` changelog notes before falling back to generated GitHub release notes when an exact version section is missing.
+- Documented workflow-local knowledge resources as intentional self-contained skill packaging and added validation for workflow-local knowledge indexes.
+
+---
+
+## [1.16.0] - 2026-05-08
+
+### Added
+
+- Claude Cowork marketplace plugin support.
+- TEA Phase 3 command examples in the overview docs, including direct slash commands and Codex skill invocations.
+- System-level and per-epic `test-design` usage examples in the TEA overview docs.
+
+### Changed
+
+- Catalog dependency metadata now uses `preceded-by` and `followed-by` column names.
+- TEA overview command guidance now distinguishes workflow names, TEA menu codes, slash commands, and Codex skills.
+
+### Fixed
+
+- Normalized `module-help.csv` to the documented 13-column schema.
+- Clarified the exact `/bmad:tea:ci` command path for Phase 3 CI setup.
+- Clarified the difference between Phase 3 system-level `test-design` and Phase 4 per-epic `test-design`.
+
+---
+
 ## [1.2.4] - 2026-02-22
 
 ### Changed
@@ -15,7 +56,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Affected workflows: `atdd`, `automate`, `ci`, `framework`, `nfr-assess`, `teach-me-testing`, `test-design`, `test-review`, `trace`
   - Removed redundant `web_bundle: false` from workflow.yaml files
 
-## [Unreleased]
+## [Historical Unreleased Notes]
 
 ### Added
 

package/lib/bmad-cache/tea/README.md

@@ -3,7 +3,7 @@
 [![Python Version](https://img.shields.io/badge/python-%3E%3D3.10-blue?logo=python&logoColor=white)](https://www.python.org)
 [![uv](https://img.shields.io/badge/uv-package%20manager-blueviolet?logo=uv)](https://docs.astral.sh/uv/)
 
-TEA (Test Engineering Architect) is a standalone BMAD module that delivers risk-based test strategy, test automation guidance, and release gate decisions. It provides a single expert agent (Murat, Master Test Architect and Quality Advisor) and nine workflows spanning Teach Me Testing (TEA Academy), framework setup, test design, ATDD, automation, traceability, NFR assessment, CI guidance, and test review.
+TEA (Test Engineering Architect) is a standalone BMAD module that delivers risk-based test strategy, test automation guidance, and release gate decisions. It provides a single expert agent (Murat, Master Test Architect and Quality Advisor) and nine workflows spanning Teach Me Testing (TEA Academy), test design, framework setup, CI guidance, ATDD, automation, test review, NFR Evidence Audit, and traceability.
 
 Docs: <https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise/>
 
@@ -43,9 +43,12 @@ TEA has two layers of files, and each has a specific job:
 | `steps-v/*.md`                                     | **Validate** steps — always 1 file: evaluate against checklist                                       | On demand                                               |
 | `checklist.md`                                     | Validation criteria — what "done" looks like for this workflow                                       | Read by steps-v                                         |
 | `*-template.md`                                    | Output skeleton with `{PLACEHOLDER}` vars — steps fill these in to produce the final artifact        | Read by steps-c when generating output                  |
-| `src/agents/bmad-tea/resources/tea-index.csv`      | Knowledge fragment index — id, name, tags, tier (core/extended/specialized), file path               | Read to decide which shared TEA fragments to load       |
+| `src/agents/bmad-tea/resources/tea-index.csv`      | Agent-level knowledge fragment index — id, name, tags, tier (core/extended/specialized), file path   | Read by the TEA agent for direct recommendations        |
+| `src/workflows/testarch/<workflow>/resources/`     | Workflow-local knowledge index and fragments                                                         | Read by workflow steps from that workflow's skill root  |
 | `resources/knowledge/*.md`                         | Reusable fragments — standards, patterns, API references                                             | Selectively read into context based on tier + config    |
 
+Workflow resource directories intentionally duplicate the TEA knowledge base. Each workflow skill must stay self-contained so it can be installed, copied, or invoked without reaching across skill boundaries. When knowledge changes, propagate the intended updates to the affected workflow resource directories instead of replacing them with a central runtime path.
+
 ```mermaid
 flowchart LR
   U[User] --> A[Agent Persona]
@@ -120,7 +123,7 @@ npx bmad-method install
 1. Install TEA (above)
 2. Load the TEA menu with `$bmad-tea` if you want a conversational entrypoint.
 3. Run one of the core workflows:
-   - `TD` / `/bmad:tea:test-design` / `$bmad-tea-testarch-test-design` — test design and risk assessment
+   - `TD` / `/bmad:tea:test-design` / `$bmad-tea-testarch-test-design` — test design, risk assessment, and NFR planning
    - `AT` / `/bmad:tea:atdd` / `$bmad-tea-testarch-atdd` — failing acceptance tests first (TDD red phase)
    - `TA` / `/bmad:tea:automate` / `$bmad-tea-testarch-automate` — expand automation coverage
 4. Or use in party mode: `/party` to include TEA with other agents
@@ -137,14 +140,14 @@ npx bmad-method install
 | Trigger | Slash Command                | Codex Skill                      | Purpose                                                   |
 | ------- | ---------------------------- | -------------------------------- | --------------------------------------------------------- |
 | TMT     | `/bmad:tea:teach-me-testing` | `$bmad-tea-teach-me-testing`     | Teach Me Testing (TEA Academy)                            |
+| TD      | `/bmad:tea:test-design`      | `$bmad-tea-testarch-test-design` | System-level or epic-level test design and NFR planning   |
 | TF      | `/bmad:tea:framework`        | `$bmad-tea-testarch-framework`   | Scaffold test framework (frontend, backend, or fullstack) |
 | CI      | `/bmad:tea:ci`               | `$bmad-tea-testarch-ci`          | Set up CI/CD quality pipeline (multi-platform)            |
-| TD      | `/bmad:tea:test-design`      | `$bmad-tea-testarch-test-design` | System-level or epic-level test design                    |
 | AT      | `/bmad:tea:atdd`             | `$bmad-tea-testarch-atdd`        | Generate failing acceptance tests + checklist             |
 | TA      | `/bmad:tea:automate`         | `$bmad-tea-testarch-automate`    | Expand test automation coverage                           |
 | RV      | `/bmad:tea:test-review`      | `$bmad-tea-testarch-test-review` | Review test quality and score                             |
+| NR      | `/bmad:tea:nfr-assess`       | `$bmad-tea-testarch-nfr`         | Audit implemented NFR evidence                            |
 | TR      | `/bmad:tea:trace`            | `$bmad-tea-testarch-trace`       | Trace requirements to tests + gate decision               |
-| NR      | `/bmad:tea:nfr-assess`       | `$bmad-tea-testarch-nfr`         | Assess non-functional requirements                        |
 
 ## Configuration
 

package/lib/bmad-cache/tea/_git_preserved/hooks/commit-msg.sample

@@ -15,10 +15,60 @@
 # SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
 # grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
 
-# This example catches duplicate Signed-off-by lines.
+# This example catches duplicate Signed-off-by lines and messages that
+# would confuse 'git am'.
+
+ret=0
 
 test "" = "$(grep '^Signed-off-by: ' "$1" |
 	 sort | uniq -c | sed -e '/^[ 	]*1[ 	]/d')" || {
 	echo >&2 Duplicate Signed-off-by lines.
-	exit 1
+	ret=1
 }
+
+comment_re="$(
+	{
+		git config --get-regexp "^core\.comment(char|string)\$" ||
+			echo '#'
+	} | sed -n -e '
+		${
+			s/^[^ ]* //
+			s|[][*./\]|\\&|g
+			s/^auto$/[#;@!$%^&|:]/
+			p
+		}'
+)"
+scissors_line="^${comment_re} -\{8,\} >8 -\{8,\}\$"
+comment_line="^${comment_re}.*"
+blank_line='^[ 	]*$'
+# Disallow lines starting with "diff -" or "Index: " in the body of the
+# message. Stop looking if we see a scissors line.
+line="$(sed -n -e "
+	# Skip comments and blank lines at the start of the file.
+	/${scissors_line}/q
+	/${comment_line}/d
+	/${blank_line}/d
+	# The first paragraph will become the subject header so
+	# does not need to be checked.
+	: subject
+	n
+	/${scissors_line}/q
+	/${blank_line}/!b subject
+	# Check the body of the message for problematic
+	# prefixes.
+	: body
+	n
+	/${scissors_line}/q
+	/${comment_line}/b body
+	/^diff -/{p;q;}
+	/^Index: /{p;q;}
+	b body
+	" "$1")"
+if test -n "$line"
+then
+	echo >&2 "Message contains a diff that will confuse 'git am'."
+	echo >&2 "To fix this indent the diff."
+	ret=1
+fi
+
+exit $ret

package/lib/bmad-cache/tea/_git_preserved/hooks/fsmonitor-watchman.sample

@@ -29,8 +29,6 @@ if ($version ne 2) {
 
 my $git_work_tree = get_working_dir();
 
-my $retry = 1;
-
 my $json_pkg;
 eval {
 	require JSON::XS;
@@ -123,8 +121,7 @@ sub watchman_query {
 sub is_work_tree_watched {
 	my ($output) = @_;
 	my $error = $output->{error};
-	if ($retry > 0 and $error and $error =~ m/unable to resolve root .* directory (.*) is not watched/) {
-		$retry--;
+	if ($error and $error =~ m/unable to resolve root .* directory (.*) is not watched/) {
 		my $response = qx/watchman watch "$git_work_tree"/;
 		die "Failed to make watchman watch '$git_work_tree'.\n" .
 		    "Falling back to scanning...\n" if $? != 0;
@@ -142,15 +139,12 @@ sub is_work_tree_watched {
 		# Watchman query just to get it over with now so we won't pay
 		# the cost in git to look up each individual file.
 		my $o = watchman_clock();
-		$error = $output->{error};
+		$error = $o->{error};
 
 		die "Watchman: $error.\n" .
 		"Falling back to scanning...\n" if $error;
 
 		output_result($o->{clock}, ("/"));
-		$last_update_token = $o->{clock};
-
-		eval { launch_watchman() };
 		return 0;
 	}
 

package/lib/bmad-cache/tea/_git_preserved/packed-refs

@@ -1,2 +1,2 @@
 # pack-refs with: peeled fully-peeled sorted 
-b0ee2a5128d0f0b9f32c30a0017722a846518349 refs/remotes/origin/main
+8734d51f24071ddbcb3617390b5fcddb4128ef77 refs/remotes/origin/main

package/lib/bmad-cache/tea/_git_preserved/refs/heads/main

@@ -1 +1 @@
-b0ee2a5128d0f0b9f32c30a0017722a846518349
+8734d51f24071ddbcb3617390b5fcddb4128ef77

package/lib/bmad-cache/tea/_git_preserved/refs/tags/v1.19.0

@@ -0,0 +1 @@
+452c9dd80219cf7cf7fd5666f9724067cb5c5d11

package/lib/bmad-cache/tea/_git_preserved/shallow

@@ -1 +1 @@
-b0ee2a5128d0f0b9f32c30a0017722a846518349
+8734d51f24071ddbcb3617390b5fcddb4128ef77

package/lib/bmad-cache/tea/docs/explanation/engagement-models.md

@@ -205,12 +205,11 @@ Steps:
 **Phase 2: Planning**
 
 - PM creates PRD with NFRs
-- (Optional) TEA runs `nfr-assess` (Enterprise only)
 
 **Phase 3: Solutioning**
 
 - Architect creates architecture
-- TEA runs `test-design` (system-level) → testability review
+- TEA runs `test-design` (system-level) → testability review and NFR evidence plan
 - TEA runs `framework` → test infrastructure
 - TEA runs `ci` → CI/CD pipeline
 - Architect runs `implementation-readiness` (fed by test design)
@@ -229,7 +228,7 @@ Steps:
 **Release Gate:**
 
 - (Optional) TEA runs `test-review` → final audit
-- (Optional) TEA runs `nfr-assess` → validate NFRs
+- (Optional) TEA runs `nfr-assess` → audit NFR evidence
 - TEA runs `trace` Phase 2 → gate decision (PASS/CONCERNS/FAIL/WAIVED)
 
 **What You Get:**
@@ -396,7 +395,7 @@ flowchart TD
 | -------------------------- | --------------------------- | ----------------------------- |
 | **None**                   | Any model                   | Choose based on project needs |
 | **Light** (internal audit) | TEA Solo or Integrated      | Gate decisions helpful        |
-| **Heavy** (SOC 2, HIPAA)   | TEA Integrated (Enterprise) | NFR assessment mandatory      |
+| **Heavy** (SOC 2, HIPAA)   | TEA Integrated (Enterprise) | NFR evidence audit mandatory  |
 
 ## Switching Between Models
 
@@ -444,17 +443,17 @@ Result: TEA where it adds value, skip where it doesn't
 
 ## Comparison Table
 
-| Aspect                | No TEA  | TEA Lite  | TEA Solo   | Integrated (Green) | Integrated (Brown) |
-| --------------------- | ------- | --------- | ---------- | ------------------ | ------------------ |
-| **BMad Required**     | No      | No        | No         | Yes                | Yes                |
-| **Learning Curve**    | None    | Low       | Medium     | High               | High               |
-| **Setup Time**        | 0       | 30 min    | 2 hours    | 1 day              | 2 days             |
-| **Workflows Used**    | 0       | 2-3       | 4-6        | 8                  | 8                  |
-| **Test Planning**     | Manual  | Optional  | Yes        | Systematic         | + Regression focus |
-| **Quality Gates**     | No      | No        | Optional   | Yes                | Yes + baseline     |
-| **NFR Assessment**    | No      | No        | No         | Optional           | Recommended        |
-| **Coverage Tracking** | Manual  | No        | Optional   | Yes                | Yes + trending     |
-| **Best For**          | Experts | Beginners | Standalone | New projects       | Legacy code        |
+| Aspect                 | No TEA  | TEA Lite  | TEA Solo   | Integrated (Green) | Integrated (Brown) |
+| ---------------------- | ------- | --------- | ---------- | ------------------ | ------------------ |
+| **BMad Required**      | No      | No        | No         | Yes                | Yes                |
+| **Learning Curve**     | None    | Low       | Medium     | High               | High               |
+| **Setup Time**         | 0       | 30 min    | 2 hours    | 1 day              | 2 days             |
+| **Workflows Used**     | 0       | 2-3       | 4-6        | 8                  | 8                  |
+| **Test Planning**      | Manual  | Optional  | Yes        | Systematic         | + Regression focus |
+| **Quality Gates**      | No      | No        | Optional   | Yes                | Yes + baseline     |
+| **NFR Evidence Audit** | No      | No        | Optional   | Optional           | Recommended        |
+| **Coverage Tracking**  | Manual  | No        | Optional   | Yes                | Yes + trending     |
+| **Best For**           | Experts | Beginners | Standalone | New projects       | Legacy code        |
 
 ## Real-World Examples
 
@@ -496,7 +495,7 @@ Decision: Full BMad Method + TEA Integrated
 Result:
 - Full lifecycle integration
 - Quality gates before releases
-- NFR assessment for enterprise customers
+- NFR evidence audit for enterprise customers
 ```
 
 ### Example 2: Enterprise (TEA Integrated - Brownfield)