bmad-method-test-architecture-enterprise 1.27.2-next.4 → 1.27.2-next.6

package/.claude-plugin/marketplace.json

@@ -31,7 +31,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.27.2-next.4",
+      "version": "1.27.2-next.6",
       "author": {
         "name": "Murat K Ozcan (TEA Creator) & Brian (BMad) Madison"
       },

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method-test-architecture-enterprise",
-  "version": "1.27.2-next.4",
+  "version": "1.27.2-next.6",
   "description": "Master Test Architect for quality strategy, test automation, and release gates",
   "keywords": [
     "bmad",
@@ -127,7 +127,7 @@
     "test:eval-routing-evidence": "node test/test-routing-evidence.js",
     "test:eval-schemas": "node tools/validate-eval-schemas.js",
     "test:eval-teach-me-testing-data": "node test/eval-teach-me-testing.js --validate-only",
-    "test:eval-test-design-data": "node test/eval-test-design.js --validate-only",
+    "test:eval-test-design-data": "node test/eval-test-design.js --validate-only && node test/test-test-design-grounding.js",
     "test:eval-trace-data": "node test/eval-trace.js --validate-only",
     "test:eval-transcript-data": "node test/eval-transcript.js --validate-only",
     "test:file-system-conformance": "node test/test-file-system-conformance.js",

package/src/workflows/testarch/bmad-testarch-test-design/steps-c/step-03-risk-and-testability.md

@@ -60,6 +60,8 @@ Also identify **ASRs** (Architecturally Significant Requirements):
 Using `risk-governance.md` and `probability-impact.md` (if loaded):
 
 - Identify real risks (not just features)
+- Ground every risk in an explicit statement from the supplied epic or a named artifact loaded for this run. Record the supporting statement in the risk description or mitigation notes so another reader can trace the row.
+- Keep the register bounded by the scope supported by the supplied epic or a named artifact loaded for this run. Do not add plausible risks merely because they are common in other systems. If a concern has no supporting statement, record it as an assumption or clarification outside the risk register.
 - Classify by category: TECH / SEC / PERF / DATA / BUS / OPS
 - Score Probability (1–3) and Impact (1–3)
 - Calculate Risk Score (P × I)

package/src/workflows/testarch/bmad-testarch-test-design/steps-c/step-04-coverage-plan.md

@@ -45,6 +45,8 @@ For each requirement or risk-driven scenario:
 - Ensure no duplicate coverage across levels
 - Assign priorities (P0–P3) using `test-priorities-matrix.md`
 - Map NFR-derived risks to planned validation scenarios and evidence sources
+- Use the exact `Risk ID` assigned in the risk register in every `Risk Link` cell. A prose description alone is not a traceable mapping.
+- Give every material risk at least one coverage row whose `Test Level` is suitable for that risk under `test-levels-framework.md`. Explain the suitability in the row notes when the level is not obvious. Preserve the risk ID when rows are split across priorities or test levels.
 
 **Priority rules:** decide each priority on business impact, user reach, and workaround
 availability. Risk score is supporting evidence and is not a required condition for any priority.

package/src/workflows/testarch/bmad-testarch-test-design/test-design-template.md

@@ -131,6 +131,8 @@ workaround. Risk score is supporting evidence and is not a required condition.
 | {requirement} | E2E        | R-001     | 3          | QA    | {notes} |
 | {requirement} | API        | R-002     | 5          | QA    | {notes} |
 
+Use the exact `Risk ID` from the risk assessment in `Risk Link`. Select `Test Level` using `test-levels-framework.md`; explain the suitability in `Notes` when the level is not obvious. Every material risk must appear in at least one coverage row at a test level that can establish it.
+
 **Total P0**: {p0_count} tests, {p0_hours} hours
 
 ### P1 (High)

package/src/workflows/testarch/bmad-testarch-trace/steps-c/step-05-gate-decision.md

@@ -467,6 +467,20 @@ const gateReport = {
 
 This file is the portable, automation-friendly companion to the markdown report. Any CI/CD pipeline, reporting dashboard, or LLM agent can consume it without parsing markdown.
 
+The summary metadata is a strict contract. Emit the resolved run value for every field below. Use the explicit unknown representation `unknown` when a runtime value cannot be resolved. Preserve the exact artifact path supplied by `{outputFile}`. Empty URL fields remain empty until a CI/CD uploader populates them. The formal requirements oracle uses `not_applicable` for both optional UI heuristic statuses when no synthetic user journey oracle exists.
+
+| Field                                                             | Required value for this run                                        |
+| ----------------------------------------------------------------- | ------------------------------------------------------------------ |
+| `decision_mode`                                                   | `{decision_mode}`                                                  |
+| `links.trace_report_path`                                         | `{outputFile}`                                                     |
+| `links.trace_report_url`                                          | `''`                                                               |
+| `links.artifact_url`                                              | `''`                                                               |
+| `links.journey_evidence_url`                                      | `''`                                                               |
+| `tests.skipped_cases`, `tests.fixme_cases`, `tests.pending_cases` | The real inventory counts. Use `0` when no cases have that status. |
+| `heuristics.ui_journey_status`, `heuristics.ui_state_status`      | `not_applicable` for a non-synthetic formal requirements oracle    |
+
+Do not shorten `{outputFile}`, invent a URL, or replace an unavailable runtime value with a guess. Use the literal string `unknown` for an unavailable runtime value.
+
 ```javascript
 const buildFallbackInventory = () => {
   const byLevel = {