@devo-bmad-custom/agent-orchestration 1.0.4 → 1.0.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devo-bmad-custom/agent-orchestration",
-  "version": "1.0.4",
+  "version": "1.0.5",
   "description": "BMAD Method — AI-native agile workflow system for Claude Code and compatible AI assistants",
   "keywords": [
     "bmad",

package/src/_memory/master-orchestrator-sidecar/instructions.md

@@ -985,7 +985,7 @@ flowchart TD
 
 Chain: `Quick Spec → Research (1–2 in-process) → UX Design → Review Gate 1 (3 sub-agents: AR+DRY · UV · SR) → Quick Dev → Final Review Gate (3 sub-agents: AR+DRY · UV · SR) → QA Tests (Playwright) → ⛔ USER APPROVAL → /prepare-to-merge`
 
-**QA Enforcement (Medium):** Use `@playwright/test` directly. NEVER use playwright MCP tools. QA agent writes `.spec.ts` files only.
+**QA Enforcement (Medium):** Use `@playwright/test` directly via `cd frontend && npx playwright test`. NEVER use playwright MCP tools. QA agent writes `.spec.ts` files and runs them with `npx playwright test`. If Chromium is not installed, run `npx playwright install chromium` first.
 
 **Research step:** 1–2 in-process analyst-agent sub-agents depending on task scope. UI-heavy: one explores codebase, one researches design patterns online. Backend-only: one agent suffices. If research reveals task is infeasible or out of scope, agents report to Master Orchestrator who HALTS and presents findings to user before proceeding to Review Gate 1.
 
@@ -1129,7 +1129,7 @@ When a story reaches `story-done` state, Master Orchestrator AUTOMATICALLY spawn
 
 On QA pass: proceed to next story or Epic Retrospective. On QA failure: route back to Dev Story agent (split pane) with failing test output.
 
-**QA Enforcement (Large):** `@playwright/test` only. NEVER use playwright MCP tools. QA sub-agent writes `.spec.ts` files and runs them via Playwright CLI.
+**QA Enforcement (Large):** `@playwright/test` only via `cd frontend && npx playwright test`. NEVER use playwright MCP tools. QA sub-agent writes `.spec.ts` files and runs them with `npx playwright test`. If Chromium is not installed, run `npx playwright install chromium` first.
 
 **Per-Story Dev Agent (Large Track):**
 For large stories (3+ files or includes UX work), spawn a **new dedicated dev agent** per story in split pane:
@@ -1215,7 +1215,7 @@ flowchart TD
 
 Chain: `Quick Spec → Quick Research (1 analyst, optional) → Quick Dev → Review Gate (3 sub-agents: AR+DRY · UV · SR) → QA Tests (Playwright) → ⛔ USER APPROVAL → PTM`
 
-**QA Enforcement (Compact):** Use `@playwright/test` directly. NEVER use playwright MCP tools. QA agent writes `.spec.ts` files only.
+**QA Enforcement (Compact):** Use `@playwright/test` directly via `cd frontend && npx playwright test`. NEVER use playwright MCP tools. QA agent writes `.spec.ts` files and runs them with `npx playwright test`. If Chromium is not installed, run `npx playwright install chromium` first.
 
 **Research decision:** Optional — Master Orchestrator decides at QS completion:
 - Unfamiliar codebase area → spawn 1 analyst (codebase exploration)
@@ -1266,7 +1266,7 @@ flowchart TD
 
 Chain: `Quick Spec → Research (2 in-process) → PRD → UX Design + Arch Notes + Sprint Plan (same session) → Review Gate 1 (3 sub-agents: AR+DRY · UV · SR — reviews all plans vs PRD) → Dev (split pane) → Review Gate 2 (3 sub-agents: AR+DRY · UV · SR) → QA Tests (Playwright) → ⛔ USER APPROVAL → PTM`
 
-**QA Enforcement (Extended):** Use `@playwright/test` directly. NEVER use playwright MCP tools. QA agent writes `.spec.ts` files only.
+**QA Enforcement (Extended):** Use `@playwright/test` directly via `cd frontend && npx playwright test`. NEVER use playwright MCP tools. QA agent writes `.spec.ts` files and runs them with `npx playwright test`. If Chromium is not installed, run `npx playwright install chromium` first.
 
 **Research scope:** Always 2 agents:
 1. Codebase exploration agent (what files/patterns are involved?)