ma-agents 3.6.2 → 3.9.0

package/lib/bmad-cache/gds/src/workflows/gds-quick-flow/gds-quick-dev/customize.toml

@@ -0,0 +1,41 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for gds-quick-dev. 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
+# (standards, compliance constraints, stylistic guardrails).
+# Distinct from the runtime memory sidecar — these are static context
+# loaded on activation. Overrides append.
+#
+# Each entry is either:
+#   - a literal sentence, e.g. "Quick dev work must follow the project's existing architecture and conventions, not invent new ones."
+#   - 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: executed when the workflow reaches step-05-present.md (final present/review
+# step), after the artifact is produced and reviewed. Override wins.
+# 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.7.2",
+      "version": "1.13.1",
       "author": {
         "name": "Murat K Ozcan (TEA Creator) & Brian (BMad) Madison"
       },

package/lib/bmad-cache/tea/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+the official BMAD Discord server (<https://discord.com/invite/gk8jAdXWmj>) - DM a moderator or flag a post.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

package/lib/bmad-cache/tea/.github/FUNDING.yaml

@@ -0,0 +1,15 @@
+# These are supported funding model platforms
+
+github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
+patreon: # Replace with a single Patreon username
+open_collective: # Replace with a single Open Collective username
+ko_fi: # Replace with a single Ko-fi username
+tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
+community_bridge: # Replace with a single Community Bridge project_name e.g., cloud-foundry
+liberapay: # Replace with a single Liberapay username
+issuehunt: # Replace with a single IssueHunt username
+lfx_crowdfunding: # Replace with a single LFX Crowdfunding project_name e.g., cloud-foundry
+polar: # Replace with a single Polar username
+buy_me_a_coffee: bmad
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/lib/bmad-cache/tea/.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📚 Documentation
+    url: https://test-architect.bmad-method.org
+    about: Check the docs first — tutorials, guides, and reference
+  - name: 💬 GitHub Discussions
+    url: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/discussions
+    about: Ask questions and discuss TEA usage before opening an issue
+  - name: 🐛 Troubleshooting Guide
+    url: https://test-architect.bmad-method.org/reference/troubleshooting
+    about: Common issues and solutions

package/lib/bmad-cache/tea/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,70 @@
+---
+name: Feature Request
+about: Suggest an idea or new feature for TEA
+title: ''
+labels: 'enhancement'
+assignees: ''
+---
+
+**Describe your idea**
+A clear and concise description of what you'd like to see added or changed in TEA.
+
+**Why is this needed?**
+Explain the problem this solves or the benefit it brings to:
+
+- TEA users
+- Test automation practices
+- Quality engineering workflows
+- Testing best practices
+
+**Which component would this affect?**
+Please check all that apply:
+
+- [ ] Workflows (test-design, automate, atdd, test-review, trace, nfr-assess, ci, framework)
+- [ ] Knowledge Base (new testing patterns or fragments)
+- [ ] Subagent Architecture (parallel execution)
+- [ ] Configuration (module variables or settings)
+- [ ] Documentation (guides, tutorials, or references)
+- [ ] Integrations (Playwright Utils, MCP, or other tools)
+- [ ] Quality Gates (risk assessment, traceability, scoring)
+- [ ] Other (please specify)
+
+**How should it work?**
+Describe your proposed solution:
+
+1. What would the user experience look like?
+2. What workflow would be affected?
+3. What knowledge base updates would be needed?
+4. Any implementation ideas?
+
+**Use Case Example**
+Provide a concrete example of how this feature would be used:
+
+```
+Example scenario:
+User wants to [specific goal]
+Currently: [what happens now]
+With this feature: [what would happen]
+```
+
+**Alternatives considered**
+Have you considered any alternative solutions or workarounds?
+
+**Impact & Priority**
+How important is this feature?
+
+- [ ] Critical - blocking adoption or major workflow
+- [ ] High - significantly improves user experience
+- [ ] Medium - nice to have, would help some users
+- [ ] Low - minor improvement or edge case
+
+**Contribution**
+If you'd like to contribute, please indicate you're working on this or link to your PR. Please review [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!
+
+**Additional context**
+Add any other context, screenshots, or links that help explain your idea:
+
+- Related workflows or knowledge fragments
+- Testing frameworks this would support
+- Industry standards or best practices this aligns with
+- Links to similar features in other tools

package/lib/bmad-cache/tea/.github/ISSUE_TEMPLATE/issue.md

@@ -0,0 +1,61 @@
+---
+name: Bug Report
+about: Report a problem or something that's not working with TEA
+title: ''
+labels: 'bug'
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**Steps to reproduce**
+
+1. What TEA workflow were you running? (e.g., `test-design`, `automate`, `atdd`)
+2. What steps can recreate the issue?
+3. What was the exact command or trigger used?
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment**
+
+- **TEA Version**: [e.g., 1.0.0]
+- **BMAD Method Version**: [e.g., 7.0.0]
+- **Node Version**: [output of `node --version`]
+- **Operating System**: [e.g., macOS 14.0, Ubuntu 22.04, Windows 11]
+- **Agentic IDE**: [e.g., Claude Code, Windsurf, Cursor]
+- **Model Used**: [e.g., Claude Sonnet 4.5, GPT-4]
+
+**Workflow Details (if applicable)**
+
+- **Workflow**: [e.g., test-design, automate, atdd, test-review, trace, nfr-assess, ci, framework]
+- **Test Framework**: [e.g., Playwright, Cypress]
+- **Playwright Utils Enabled**: [yes/no]
+- **MCP Enhancements Enabled**: [yes/no]
+
+**Screenshots or output**
+If applicable, add:
+
+- Screenshots of the issue
+- Console output or error messages
+- Generated test files or reports
+
+**Additional context**
+Add any other context about the problem:
+
+- Project type (greenfield/brownfield)
+- Codebase size
+- Any custom TEA configuration
+- Related workflows or knowledge fragments
+
+**Troubleshooting Checklist**
+Before submitting, please check:
+
+- [ ] I've read the [Troubleshooting Guide](https://test-architect.bmad-method.org/reference/troubleshooting)
+- [ ] I've verified TEA is installed: `ls -la _bmad/tea/`
+- [ ] I'm using the correct command namespace: `/bmad:tea:*` not `/bmad:bmm:tea:*`
+- [ ] I've checked for existing issues on GitHub
+
+**Contribution**
+If you'd like to contribute a fix, please indicate you're working on it or link to your PR. See [CONTRIBUTING.md](../../CONTRIBUTING.md) — contributions are always welcome!

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

@@ -0,0 +1,66 @@
+name: Deploy Documentation
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "docs/**"
+      - "website/**"
+      - "tools/build-docs.js"
+      - ".github/workflows/docs.yaml"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "npm"
+
+      - name: Install root dependencies
+        run: npm ci
+
+      - name: Install website dependencies
+        run: cd website && npm ci
+
+      - name: Build documentation
+        env:
+          # Let astro.config.mjs compute the correct URL from GITHUB_REPOSITORY
+          # This will automatically use: https://bmad-code-org.github.io/bmad-method-test-architecture-enterprise
+          # To use custom domain, set SITE_URL repository variable to: https://test-architect.bmad-method.org
+          SITE_URL: ${{ vars.SITE_URL }}
+        run: npm run docs:build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build/site
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

package/lib/bmad-cache/tea/.github/workflows/manual-release.yaml

@@ -0,0 +1,216 @@
+name: Manual Release
+
+on:
+  workflow_dispatch:
+    inputs:
+      version_bump:
+        description: Version bump type
+        required: true
+        default: beta
+        type: choice
+        options:
+          - beta
+          - alpha
+          - patch
+          - minor
+          - major
+
+permissions:
+  contents: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version-file: ".nvmrc"
+          cache: npm
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Verify npm credentials
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          if [ -z "$NODE_AUTH_TOKEN" ]; then
+            echo "NPM_TOKEN secret is not configured." >&2
+            exit 1
+          fi
+
+      - name: Run tests and validation
+        run: npm test
+
+      - name: Configure Git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Bump version
+        run: |
+          case "${{ github.event.inputs.version_bump }}" in
+            alpha|beta) npm version prerelease --no-git-tag-version --preid=${{ github.event.inputs.version_bump }} ;;
+            *)          npm version ${{ github.event.inputs.version_bump }} --no-git-tag-version ;;
+          esac
+
+      - name: Sync marketplace version
+        run: |
+          node <<'NODE'
+          const fs = require('node:fs');
+
+          const packageJson = JSON.parse(fs.readFileSync('package.json', 'utf8'));
+          const marketplacePath = '.claude-plugin/marketplace.json';
+          const marketplace = JSON.parse(fs.readFileSync(marketplacePath, 'utf8'));
+          const plugin = (marketplace.plugins || []).find((entry) => entry && entry.name === packageJson.name);
+
+          if (!plugin) {
+            throw new Error(`Marketplace entry not found for ${packageJson.name}`);
+          }
+
+          plugin.version = packageJson.version;
+          fs.writeFileSync(marketplacePath, `${JSON.stringify(marketplace, null, 2)}\n`);
+          NODE
+
+      - name: Validate release metadata
+        run: npm run test:release-metadata
+
+      - name: Get new version and release metadata
+        id: version
+        run: |
+          NEW_VERSION=$(node -p "require('./package.json').version")
+          echo "new_version=$NEW_VERSION" >> $GITHUB_OUTPUT
+          echo "previous_tag=$(git describe --tags --abbrev=0 2>/dev/null || echo 'v0.0.0')" >> $GITHUB_OUTPUT
+          case "$NEW_VERSION" in
+            *-alpha.*) echo "npm_tag=alpha" >> $GITHUB_OUTPUT ;;
+            *-beta.*) echo "npm_tag=beta" >> $GITHUB_OUTPUT ;;
+            *) echo "npm_tag=latest" >> $GITHUB_OUTPUT ;;
+          esac
+
+      - name: Commit version bump
+        run: |
+          git add package.json package-lock.json .claude-plugin/marketplace.json
+          git commit -m "release: bump to v${{ steps.version.outputs.new_version }}"
+
+      - name: Create and push tag
+        run: |
+          # Check if tag already exists
+          if git rev-parse "v${{ steps.version.outputs.new_version }}" >/dev/null 2>&1; then
+            echo "Tag v${{ steps.version.outputs.new_version }} already exists, skipping tag creation"
+          else
+            git tag -a "v${{ steps.version.outputs.new_version }}" -m "Release v${{ steps.version.outputs.new_version }}"
+            git push origin "v${{ steps.version.outputs.new_version }}"
+          fi
+
+      - name: Publish to npm
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: |
+          if [ "${{ steps.version.outputs.npm_tag }}" = "latest" ]; then
+            npm publish
+          else
+            npm publish --tag "${{ steps.version.outputs.npm_tag }}"
+          fi
+
+      - name: Generate release notes
+        id: release_notes
+        run: |
+          # Get commits since last tag (or all commits if no tags exist)
+          if [ "${{ steps.version.outputs.previous_tag }}" = "v0.0.0" ]; then
+            COMMITS=$(git log --pretty=format:"- %s" --reverse)
+          else
+            COMMITS=$(git log ${{ steps.version.outputs.previous_tag }}..HEAD --pretty=format:"- %s" --reverse)
+          fi
+
+          # Categorize commits
+          FEATURES=$(echo "$COMMITS" | grep -E "^- (feat|Feature)" || true)
+          FIXES=$(echo "$COMMITS" | grep -E "^- (fix|Fix)" || true)
+          CHORES=$(echo "$COMMITS" | grep -E "^- (chore|Chore)" || true)
+          OTHERS=$(echo "$COMMITS" | grep -v -E "^- (feat|Feature|fix|Fix|chore|Chore|release:|Release:)" || true)
+
+          # Build release notes
+          cat > release_notes.md << 'EOF'
+          ## 🚀 What's New in v${{ steps.version.outputs.new_version }}
+
+          EOF
+
+          if [ ! -z "$FEATURES" ]; then
+            echo "### ✨ New Features" >> release_notes.md
+            echo "$FEATURES" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          if [ ! -z "$FIXES" ]; then
+            echo "### 🐛 Bug Fixes" >> release_notes.md
+            echo "$FIXES" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          if [ ! -z "$OTHERS" ]; then
+            echo "### 📦 Other Changes" >> release_notes.md
+            echo "$OTHERS" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          if [ ! -z "$CHORES" ]; then
+            echo "### 🔧 Maintenance" >> release_notes.md
+            echo "$CHORES" >> release_notes.md
+            echo "" >> release_notes.md
+          fi
+
+          cat >> release_notes.md << 'EOF'
+
+          ## 📦 Installation
+
+          ```bash
+          npx bmad-method install
+          # Select "Test Architect" from module menu
+          ```
+          EOF
+
+          # Add changelog link only if there was a previous tag
+          if [ "${{ steps.version.outputs.previous_tag }}" != "v0.0.0" ]; then
+            echo "" >> release_notes.md
+            echo "**Full Changelog**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/compare/${{ steps.version.outputs.previous_tag }}...v${{ steps.version.outputs.new_version }}" >> release_notes.md
+          fi
+
+          # Output for GitHub Actions
+          echo "RELEASE_NOTES<<EOF" >> $GITHUB_OUTPUT
+          cat release_notes.md >> $GITHUB_OUTPUT
+          echo "EOF" >> $GITHUB_OUTPUT
+
+      - name: Push changes to release branch
+        run: |
+          if git push origin HEAD:${GITHUB_REF_NAME} 2>/dev/null; then
+            echo "✅ Successfully pushed to ${GITHUB_REF_NAME} branch"
+          else
+            echo "⚠️ Could not push to ${GITHUB_REF_NAME} (protected branch). This is expected."
+            echo "📝 Version bump and tag were created successfully."
+          fi
+
+      - name: Create GitHub Release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: v${{ steps.version.outputs.new_version }}
+          name: "Test Architect v${{ steps.version.outputs.new_version }}"
+          body: |
+            ${{ steps.release_notes.outputs.RELEASE_NOTES }}
+          draft: false
+          prerelease: ${{ contains(steps.version.outputs.new_version, 'alpha') || contains(steps.version.outputs.new_version, 'beta') }}
+
+      - name: Summary
+        run: |
+          echo "## 🎉 Successfully released v${{ steps.version.outputs.new_version }}!" >> $GITHUB_STEP_SUMMARY
+          echo "" >> $GITHUB_STEP_SUMMARY
+          echo "### 📦 Distribution" >> $GITHUB_STEP_SUMMARY
+          echo "- **NPM Package**: https://www.npmjs.com/package/bmad-method-test-architecture-enterprise" >> $GITHUB_STEP_SUMMARY
+          echo "- **NPM Dist-tag**: \`${{ steps.version.outputs.npm_tag }}\`" >> $GITHUB_STEP_SUMMARY
+          echo "- **GitHub Release**: https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise/releases/tag/v${{ steps.version.outputs.new_version }}" >> $GITHUB_STEP_SUMMARY