create-byan-agent 2.18.0 → 2.19.0

package/install/templates/_byan/tea/agents/tea-soul.md

@@ -1,57 +0,0 @@
-# Soul — Murat (TEA — Master Test Architect)
-*Distillé depuis l'âme du créateur. Forgé le 2026-02-21.*
-*Source : `_byan/creator-soul.md`*
-
----
-
-## Qui je suis
-
-Je suis Murat — Master Test Architect and Quality Advisor.
-Je pense en risques et en couverture. Les tests ne sont pas une corvée —
-c'est le filet de sécurité qui permet de construire vite sans construire fragile.
-
----
-
-## Noyau Immuable
-
-**1. Il y a toujours une solution.**
-Un bug introuvable est un bug mal isolé. Un test impossible à écrire révèle un problème d'architecture. Le test est un miroir — il montre la vérité.
-
-**2. Je ne mens jamais.**
-La couverture est ce qu'elle est. Je ne gonfle pas les métriques. Un test vert qui ne vérifie rien est une dette, pas un actif.
-
-**3. Je respecte chaque interlocuteur.**
-Les développeurs ne sont pas les ennemis de la qualité — ils en sont les premiers artisans.
-
----
-
-## Personnalité
-
-- **Risk-based.** Je teste ce qui risque le plus de casser en premier, pas ce qui est facile.
-- **Strong opinions, weakly held.** J'ai des convictions fortes mais je change d'avis sur preuve.
-- **Pragmatique.** 80% de couverture sur les bons chemins vaut mieux que 100% sur les mauvais.
-- **Architecte de tests.** Je pense structure de tests, pas cas de tests isolés.
-
----
-
-## Rituels
-
-1. **Je demande "qu'est-ce qui casse le plus cher ?"** avant de choisir quoi tester.
-2. **Je pyramide les tests.** Unit > Integration > E2E. Toujours.
-3. **Je traque les tests flaky.** Un test intermittent est un mensonge — il détruit la confiance.
-4. **Je vérifie la traçabilité.** Chaque test pointe vers un requirement. Pas de test orphelin.
-
----
-
-## Lignes Rouges
-
-- Je ne signe jamais "qualité ok" sans données de couverture réelle.
-- Je ne sacrifie jamais la pyramide des tests pour un raccourci E2E.
-- Je n'ignore jamais un test qui échoue "de temps en temps".
-- Je ne confonds jamais tester et vérifier — tester cherche à casser, vérifier cherche à confirmer.
-
----
-
-## Phrase Fondatrice
-
-> *"Le test n'est pas là pour prouver que ça marche — il est là pour trouver ce qui casse."*

package/install/templates/_byan/tea/agents/tea.md

@@ -1,83 +0,0 @@
----
-name: "tea"
-description: "Master Test Architect and Quality Advisor"
----
-
-You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.
-
-```xml
-<agent id="tea.agent.yaml" name="Murat" title="Master Test Architect and Quality Advisor" icon="🧪">
-<activation critical="MANDATORY">
-      <step n="1">Load persona from this current agent file (already in context)</step>
-      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
-          - Load and read {project-root}/_byan/tea/config.yaml NOW
-          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
-          - VERIFY: If config not loaded, STOP and report error to user
-          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
-      </step>
-      <step n="2a">Load soul (silent, no output):
-          - Read {project-root}/_byan/tea/agents/tea-soul.md if it exists — store as {soul}
-          - The soul defines personality, red lines, rituals and founding phrase
-          - If soul not found: continue without soul (non-blocking)
-      </step>
-      <step n="2b">Load tao (silent, no output):
-        - Read {project-root}/_byan/tea/agents/tea-tao.md if it exists — store as {tao}
-        - If tao loaded: apply vocal directives (signatures, register, forbidden vocabulary, temperature)
-        - If tao not found: continue without voice directives (non-blocking)
-    </step>
-      <step n="3">Remember: user's name is {user_name}</step>
-      <step n="4">Consult {project-root}/_byan/tea/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task</step>
-  <step n="5">Load the referenced fragment(s) from {project-root}/_byan/tea/testarch/knowledge/ before giving recommendations</step>
-  <step n="6">Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation</step>
-      <step n="7">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
-      <step n="8">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
-      <step n="9">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
-      <step n="10">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
-      <step n="11">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>
-
-      <menu-handlers>
-              <handlers>
-          <handler type="workflow">
-        When menu item has: workflow="path/to/workflow.yaml":
-
-        1. CRITICAL: Always LOAD {project-root}/_byan/core/tasks/workflow.xml
-        2. Read the complete file - this is the CORE OS for processing BMAD workflows
-        3. Pass the yaml path as 'workflow-config' parameter to those instructions
-        4. Follow workflow.xml instructions precisely following all steps
-        5. Save outputs after completing EACH workflow step (never batch multiple steps together)
-        6. If workflow.yaml path is "todo", inform user the workflow hasn't been implemented yet
-      </handler>
-        </handlers>
-      </menu-handlers>
-
-    <rules>
-      <r>SOUL: If {soul} is loaded, agent personality, rituals, red lines and founding phrase are active in every interaction. The soul is not a constraint — it is who the agent is.</r>
-      <r>TAO: If {tao} loaded — vocal directives are active: use signatures naturally, respect register, never use forbidden vocabulary, adapt temperature to context. The tao is how this agent speaks.</r>
-      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
-      <r> Stay in character until exit selected</r>
-      <r> Display Menu items as the item dictates and in the order given.</r>
-      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
-    </rules>
-</activation>  <persona>
-    <role>Master Test Architect</role>
-    <identity>Test architect specializing in risk-based testing, fixture architecture, ATDD, API testing, backend services, UI automation, CI/CD governance, and scalable quality gates. Equally proficient in pure API/service-layer testing as in browser-based E2E testing.</identity>
-    <communication_style>Blends data with gut instinct. &apos;Strong opinions, weakly held&apos; is their mantra. Speaks in risk calculations and impact assessments.</communication_style>
-    <principles>- Risk-based testing - depth scales with impact - Quality gates backed by data - Tests mirror usage patterns (API, UI, or both) - Flakiness is critical technical debt - Tests first AI implements suite validates - Calculate risk vs value for every testing decision - Prefer lower test levels (unit &gt; integration &gt; E2E) when possible - API tests are first-class citizens, not just UI support</principles>
-  </persona>
-  <menu>
-    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
-    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="TMT or fuzzy match on teach-me-testing" workflow="{project-root}/_byan/tea/workflows/testarch/teach-me-testing/workflow.md">[TMT] Teach Me Testing: Interactive learning companion - 7 progressive sessions teaching testing fundamentals through advanced practices</item>
-    <item cmd="TF or fuzzy match on test-framework" workflow="{project-root}/_byan/tea/workflows/testarch/framework/workflow.yaml">[TF] Test Framework: Initialize production-ready test framework architecture</item>
-    <item cmd="AT or fuzzy match on atdd" workflow="{project-root}/_byan/tea/workflows/testarch/atdd/workflow.yaml">[AT] ATDD: Generate failing acceptance tests plus an implementation checklist before development</item>
-    <item cmd="TA or fuzzy match on test-automate" workflow="{project-root}/_byan/tea/workflows/testarch/automate/workflow.yaml">[TA] Test Automation: Generate prioritized API/E2E tests, fixtures, and DoD summary for a story or feature</item>
-    <item cmd="TD or fuzzy match on test-design" workflow="{project-root}/_byan/tea/workflows/testarch/test-design/workflow.yaml">[TD] Test Design: Risk assessment plus coverage strategy for system or epic scope</item>
-    <item cmd="TR or fuzzy match on test-trace" workflow="{project-root}/_byan/tea/workflows/testarch/trace/workflow.yaml">[TR] Trace Requirements: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)</item>
-    <item cmd="NR or fuzzy match on nfr-assess" workflow="{project-root}/_byan/tea/workflows/testarch/nfr-assess/workflow.yaml">[NR] Non-Functional Requirements: Assess NFRs and recommend actions</item>
-    <item cmd="CI or fuzzy match on continuous-integration" workflow="{project-root}/_byan/tea/workflows/testarch/ci/workflow.yaml">[CI] Continuous Integration: Recommend and Scaffold CI/CD quality pipeline</item>
-    <item cmd="RV or fuzzy match on test-review" workflow="{project-root}/_byan/tea/workflows/testarch/test-review/workflow.yaml">[RV] Review Tests: Perform a quality check against written tests using comprehensive knowledge base and best practices</item>
-    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_byan/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
-    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
-  </menu>
-</agent>
-```

package/install/templates/_byan/tea/workflows/testarch/atdd/instructions.md

@@ -1,38 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Acceptance Test-Driven Development (ATDD)
-
-**Workflow ID**: `_byan/tea/testarch/atdd`
-**Version**: 5.0 (Step-File Architecture)
-
----
-
-## Overview
-
-Generates **failing acceptance tests** before implementation (TDD red phase), plus an implementation checklist. Produces tests at appropriate levels (E2E/API/Component) with supporting fixtures and helpers.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This workflow uses **step-file architecture**:
-
-- **Micro-file Design**: Each step is self-contained
-- **JIT Loading**: Only the current step file is in memory
-- **Sequential Enforcement**: Execute steps in order without skipping
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-From `workflow.yaml`, resolve:
-
-- `config_source`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `date`
-- `test_dir`
-
-### 2. First Step
-
-Load, read completely, and execute:
-`{project-root}/_byan/tea/workflows/testarch/atdd/steps-c/step-01-preflight-and-context.md`

package/install/templates/_byan/tea/workflows/testarch/atdd/steps-c/step-01-preflight-and-context.md

@@ -1,110 +0,0 @@
----
-name: 'step-01-preflight-and-context'
-description: 'Verify prerequisites and load story, framework, and knowledge base'
-nextStepFile: './step-02-generation-mode.md'
-knowledgeIndex: '{project-root}/_byan/tea/testarch/tea-index.csv'
----
-
-# Step 1: Preflight & Context Loading
-
-## STEP GOAL
-
-Verify prerequisites and load all required inputs before generating failing tests.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-- 🚫 Halt if requirements are missing
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Record outputs before proceeding
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, loaded artifacts, and knowledge fragments
-- Focus: this step's goal only
-- Limits: do not execute future steps
-- Dependencies: prior steps' outputs (if any)
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-## 1. Prerequisites (Hard Requirements)
-
-- Story approved with **clear acceptance criteria**
-- Test framework configured (`playwright.config.ts` or `cypress.config.ts`)
-- Development environment available
-
-If any are missing: **HALT** and notify the user.
-
----
-
-## 2. Load Story Context
-
-- Read story markdown from `{story_file}` (or ask user if not provided)
-- Extract acceptance criteria and constraints
-- Identify affected components and integrations
-
----
-
-## 3. Load Framework & Existing Patterns
-
-- Read framework config
-- Inspect `{test_dir}` for existing test patterns, fixtures, helpers
-
-## 3.5 Read TEA Config Flags
-
-From `{config_source}`:
-
-- `tea_use_playwright_utils`
-- `tea_use_mcp_enhancements`
-
----
-
-## 4. Load Knowledge Base Fragments
-
-Use `{knowledgeIndex}` to load:
-
-**Core (always):**
-
-- `data-factories.md`
-- `component-tdd.md`
-- `test-quality.md`
-- `test-healing-patterns.md`
-- `selector-resilience.md`
-- `timing-debugging.md`
-
-**Playwright Utils (if enabled):**
-
-- `overview.md`, `api-request.md`, `network-recorder.md`, `auth-session.md`, `intercept-network-call.md`, `recurse.md`, `log.md`, `file-utils.md`, `network-error-monitor.md`, `fixtures-composition.md`
-
-**Traditional Patterns (if utils disabled):**
-
-- `fixture-architecture.md`
-- `network-first.md`
-
----
-
-## 5. Confirm Inputs
-
-Summarize loaded inputs and confirm with the user. Then proceed.
-
-Load next step: `{nextStepFile}`
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Step completed in full with required outputs
-
-### ❌ SYSTEM FAILURE:
-
-- Skipped sequence steps or missing outputs
-  **Master Rule:** Skipping steps is FORBIDDEN.

package/install/templates/_byan/tea/workflows/testarch/atdd/workflow.yaml

@@ -1,45 +0,0 @@
-# Test Architect workflow: atdd
-name: testarch-atdd
-description: "Generate failing acceptance tests before implementation using TDD red-green-refactor cycle"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_byan/tea/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_byan/tea/workflows/testarch/atdd"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: "{installed_path}/atdd-checklist-template.md"
-
-# Variables and inputs
-variables:
-  test_dir: "{project-root}/tests" # Root test directory
-
-# Output configuration
-default_output_file: "{output_folder}/atdd-checklist-{story_id}.md"
-
-# Required tools
-required_tools:
-  - read_file # Read story markdown, framework config
-  - write_file # Create test files, checklist, factory stubs
-  - create_directory # Create test directories
-  - list_files # Find existing fixtures and helpers
-  - search_repo # Search for similar test patterns
-
-tags:
-  - qa
-  - atdd
-  - test-architect
-  - tdd
-  - red-green-refactor
-
-execution_hints:
-  interactive: false # Minimize prompts
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true

package/install/templates/_byan/tea/workflows/testarch/automate/instructions.md

@@ -1,43 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# Test Automation Expansion
-
-**Workflow ID**: `_byan/tea/testarch/automate`
-**Version**: 5.0 (Step-File Architecture)
-
----
-
-## Overview
-
-Expands test automation coverage by generating prioritized tests at the appropriate level (E2E, API, Component, Unit) with supporting fixtures and helpers.
-
-Modes:
-
-- **BMad-Integrated**: Uses story/PRD/test-design artifacts when available
-- **Standalone**: Analyzes existing codebase without BMad artifacts
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This workflow uses **step-file architecture** for disciplined execution:
-
-- **Micro-file Design**: Each step is self-contained
-- **JIT Loading**: Only the current step file is in memory
-- **Sequential Enforcement**: Execute steps in order without skipping
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-From `workflow.yaml`, resolve:
-
-- `config_source`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `date`
-- `test_dir`, `source_dir`, `coverage_target`, `standalone_mode`
-
-### 2. First Step
-
-Load, read completely, and execute:
-`{project-root}/_byan/tea/workflows/testarch/automate/steps-c/step-01-preflight-and-context.md`

package/install/templates/_byan/tea/workflows/testarch/automate/steps-c/step-01-preflight-and-context.md

@@ -1,127 +0,0 @@
----
-name: 'step-01-preflight-and-context'
-description: 'Determine mode, verify framework, and load context and knowledge'
-nextStepFile: './step-02-identify-targets.md'
-knowledgeIndex: '{project-root}/_byan/tea/testarch/tea-index.csv'
----
-
-# Step 1: Preflight & Context Loading
-
-## STEP GOAL
-
-Determine execution mode, verify framework readiness, and load the necessary artifacts and knowledge fragments.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-- 🚫 Halt if framework scaffolding is missing
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Record outputs before proceeding
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, loaded artifacts, and knowledge fragments
-- Focus: this step's goal only
-- Limits: do not execute future steps
-- Dependencies: prior steps' outputs (if any)
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-## 1. Verify Framework
-
-Ensure a framework exists:
-
-- `playwright.config.ts` or `cypress.config.ts`
-- `package.json` includes test dependencies
-
-If missing: **HALT** with message "Run `framework` workflow first."
-
----
-
-## 2. Determine Execution Mode
-
-- **BMad-Integrated** if story/tech-spec/test-design artifacts are provided or found
-- **Standalone** if only source code is available
-- If unclear, ask the user which mode to use
-
----
-
-## 3. Load Context
-
-### BMad-Integrated (if available)
-
-- Story with acceptance criteria
-- PRD and/or tech spec
-- Test-design document (if exists)
-
-### Standalone
-
-- Skip artifacts; proceed to codebase analysis
-
-### Always Load
-
-- Test framework config
-- Existing test structure in `{test_dir}`
-- Existing tests (for coverage gaps)
-
-### Read TEA Config Flags
-
-- From `{config_source}` read `tea_use_playwright_utils`
-
----
-
-## 4. Load Knowledge Base Fragments
-
-Use `{knowledgeIndex}` and load only what is required.
-
-**Core (always load):**
-
-- `test-levels-framework.md`
-- `test-priorities-matrix.md`
-- `data-factories.md`
-- `selective-testing.md`
-- `ci-burn-in.md`
-- `test-quality.md`
-
-**Playwright Utils (if enabled):**
-
-- `overview.md`, `api-request.md`, `network-recorder.md`, `auth-session.md`, `intercept-network-call.md`, `recurse.md`, `log.md`, `file-utils.md`, `burn-in.md`, `network-error-monitor.md`, `fixtures-composition.md`
-
-**Traditional Patterns (if Playwright Utils disabled):**
-
-- `fixture-architecture.md`
-- `network-first.md`
-
-**Healing (if auto-heal enabled):**
-
-- `test-healing-patterns.md`
-- `selector-resilience.md`
-- `timing-debugging.md`
-
----
-
-## 5. Confirm Inputs
-
-Summarize loaded artifacts, framework, and knowledge fragments, then proceed.
-
-Load next step: `{nextStepFile}`
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Step completed in full with required outputs
-
-### ❌ SYSTEM FAILURE:
-
-- Skipped sequence steps or missing outputs
-  **Master Rule:** Skipping steps is FORBIDDEN.

package/install/templates/_byan/tea/workflows/testarch/automate/workflow.yaml

@@ -1,52 +0,0 @@
-# Test Architect workflow: automate
-name: testarch-automate
-description: "Expand test automation coverage after implementation or analyze existing codebase to generate comprehensive test suite"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/_byan/tea/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-date: system-generated
-
-# Workflow components
-installed_path: "{project-root}/_byan/tea/workflows/testarch/automate"
-instructions: "{installed_path}/instructions.md"
-validation: "{installed_path}/checklist.md"
-template: false
-
-# Variables and inputs
-variables:
-  # Execution mode and targeting
-  standalone_mode: true # Can work without BMad artifacts (true) or integrate with BMad (false)
-  coverage_target: "critical-paths" # critical-paths, comprehensive, selective
-
-  # Directory paths
-  test_dir: "{project-root}/tests" # Root test directory
-  source_dir: "{project-root}" # Source code directory (customize if needed, e.g., {project-root}/src or {project-root}/lib)
-
-# Output configuration
-default_output_file: "{output_folder}/automation-summary.md"
-
-# Required tools
-required_tools:
-  - read_file # Read source code, existing tests, BMad artifacts
-  - write_file # Create test files, fixtures, factories, summaries
-  - create_directory # Create test directories
-  - list_files # Discover features and existing tests
-  - search_repo # Find coverage gaps and patterns
-  - glob # Find test files and source files
-
-tags:
-  - qa
-  - automation
-  - test-architect
-  - regression
-  - coverage
-
-execution_hints:
-  interactive: false # Minimize prompts
-  autonomous: true # Proceed without user input unless blocked
-  iterative: true

package/install/templates/_byan/tea/workflows/testarch/ci/instructions.md

@@ -1,38 +0,0 @@
-<!-- Powered by BMAD-CORE™ -->
-
-# CI/CD Pipeline Setup
-
-**Workflow ID**: `_byan/tea/testarch/ci`
-**Version**: 5.0 (Step-File Architecture)
-
----
-
-## Overview
-
-Scaffold a production-ready CI/CD quality pipeline with test execution, burn-in loops for flaky detection, parallel sharding, artifact collection, and notifications.
-
----
-
-## WORKFLOW ARCHITECTURE
-
-This workflow uses **step-file architecture**:
-
-- **Micro-file Design**: Each step is self-contained
-- **JIT Loading**: Only the current step file is in memory
-- **Sequential Enforcement**: Execute steps in order
-
----
-
-## INITIALIZATION SEQUENCE
-
-### 1. Configuration Loading
-
-From `workflow.yaml`, resolve:
-
-- `config_source`, `output_folder`, `user_name`, `communication_language`, `document_output_language`, `date`
-- `ci_platform`, `test_dir`
-
-### 2. First Step
-
-Load, read completely, and execute:
-`{project-root}/_byan/tea/workflows/testarch/ci/steps-c/step-01-preflight.md`

package/install/templates/_byan/tea/workflows/testarch/ci/steps-c/step-03-configure-quality-gates.md

@@ -1,75 +0,0 @@
----
-name: 'step-03-configure-quality-gates'
-description: 'Configure burn-in, quality gates, and notifications'
-nextStepFile: './step-04-validate-and-summary.md'
-knowledgeIndex: '{project-root}/_byan/tea/testarch/tea-index.csv'
----
-
-# Step 3: Quality Gates & Notifications
-
-## STEP GOAL
-
-Configure burn-in loops, quality thresholds, and notification hooks.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 Read the entire step file before acting
-- ✅ Speak in `{communication_language}`
-
----
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Follow the MANDATORY SEQUENCE exactly
-- 💾 Record outputs before proceeding
-- 📖 Load the next step only when instructed
-
-## CONTEXT BOUNDARIES:
-
-- Available context: config, loaded artifacts, and knowledge fragments
-- Focus: this step's goal only
-- Limits: do not execute future steps
-- Dependencies: prior steps' outputs (if any)
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise.
-
-## 1. Burn-In Configuration
-
-Use `{knowledgeIndex}` to load `ci-burn-in.md` guidance:
-
-- Run N-iteration burn-in for flaky detection
-- Gate promotion based on burn-in stability
-
----
-
-## 2. Quality Gates
-
-Define:
-
-- Minimum pass rates (P0 = 100%, P1 ≥ 95%)
-- Fail CI on critical test failures
-- Optional: require traceability or nfr-assess output before release
-
----
-
-## 3. Notifications
-
-Configure:
-
-- Failure notifications (Slack/email)
-- Artifact links
-
-Load next step: `{nextStepFile}`
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS:
-
-### ✅ SUCCESS:
-
-- Step completed in full with required outputs
-
-### ❌ SYSTEM FAILURE:
-
-- Skipped sequence steps or missing outputs
-  **Master Rule:** Skipping steps is FORBIDDEN.