froid-plane-test-architecture-enterprise 1.23.4

package/.claude-plugin/marketplace.json

@@ -0,0 +1,52 @@
+{
+  "name": "froid-plane-test-architecture-enterprise",
+  "owner": {
+    "name": "Murat K Ozcan (TEA Creator) & Brian (Froid) Madison"
+  },
+  "license": "MIT",
+  "homepage": "https://github.com/cordya-ai/froid-plane-test-architecture-enterprise",
+  "repository": "https://github.com/cordya-ai/froid-plane-test-architecture-enterprise",
+  "keywords": [
+    "froid",
+    "test-architect",
+    "test-engineering",
+    "testing",
+    "quality",
+    "quality-gates",
+    "risk-based-testing",
+    "verification-and-validation",
+    "traceability",
+    "nfr",
+    "test-automation",
+    "automation",
+    "contract-testing",
+    "pact",
+    "playwright",
+    "cypress",
+    "mobile",
+    "maestro"
+  ],
+  "plugins": [
+    {
+      "name": "froid-plane-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 Froid Plane ecosystem.",
+      "version": "1.23.4",
+      "author": {
+        "name": "Murat K Ozcan (TEA Creator) & Brian (Froid) Madison"
+      },
+      "skills": [
+        "./src/agents/froid-tea",
+        "./src/workflows/testarch/froid-testarch-atdd",
+        "./src/workflows/testarch/froid-testarch-automate",
+        "./src/workflows/testarch/froid-testarch-ci",
+        "./src/workflows/testarch/froid-testarch-framework",
+        "./src/workflows/testarch/froid-testarch-nfr",
+        "./src/workflows/testarch/froid-testarch-test-design",
+        "./src/workflows/testarch/froid-testarch-test-review",
+        "./src/workflows/testarch/froid-testarch-trace",
+        "./src/workflows/testarch/froid-teach-me-testing"
+      ]
+    }
+  ]
+}

package/.coderabbit.yaml

@@ -0,0 +1,40 @@
+# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
+
+language: "en-US"
+early_access: true
+reviews:
+  profile: chill
+  high_level_summary: false # don't post summary until explicitly invoked
+  request_changes_workflow: false
+  review_status: false
+  commit_status: false
+  walkthrough: false
+  poem: false
+  auto_review:
+    enabled: true
+    drafts: false # Don't review drafts automatically
+    auto_incremental_review: false # always review the whole PR, not just new commits
+    base_branches:
+      - main
+  path_filters:
+    - "!**/node_modules/**"
+  path_instructions:
+    - path: "**/*"
+      instructions: |
+        Focus on inconsistencies, contradictions, edge cases and serious issues.
+        Avoid commenting on minor issues such as linting, formatting and style issues.
+        When providing code suggestions, use GitHub's suggestion format:
+        ```suggestion
+        <code changes>
+        ```
+    - path: "**/*.js"
+      instructions: |
+        CLI tooling code. Check for: missing error handling on fs operations,
+        path.join vs string concatenation, proper cleanup in error paths.
+        Flag any process.exit() without error message.
+chat:
+  auto_reply: true # Response to mentions in comments, a la @coderabbit review
+issue_enrichment:
+  auto_enrich:
+    enabled: false # don't auto-comment on issues
+

package/.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 FROID 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/.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: froid
+thanks_dev: # Replace with a single thanks.dev username
+custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📚 Documentation
+    url: https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/
+    about: Check the docs first for tutorials, guides, and reference
+  - name: 🐛 Troubleshooting Guide
+    url: https://cordya-ai.github.io/froid-plane-test-architecture-enterprise/reference/troubleshooting/
+    about: Common issues and solutions

package/.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/.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]
+- **FROID 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.froid-plane.org/reference/troubleshooting)
+- [ ] I've verified TEA is installed: `ls -la _froid/tea/`
+- [ ] I'm using the current invocation: `/froid-testarch-*` (Claude Code, Cursor, Windsurf) or `$froid-testarch-*` (Codex)
+- [ ] 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/.github/ISSUE_TEMPLATE/rule_quality_report.md

@@ -0,0 +1,46 @@
+---
+name: Rule Quality Report
+about: An agent misread, ignored, or was misled by a TEA rule or knowledge fragment
+title: ''
+labels: 'rule-quality'
+assignees: ''
+---
+
+TEA ships rules. This report is about a rule that failed to steer an agent, not about TEA crashing. One report per rule, please.
+
+**Agent and model**
+Which agent ran, and which model: e.g. Claude Code / Claude Opus 4.6, Cursor / GPT-5.1, Windsurf, Codex.
+
+**Which rule**
+The file and the section inside it. Examples:
+
+- `criteria-registry.md`, row H3
+- `resources/knowledge/network-first.md`, the "declare the intercept before navigating" section
+- a step file such as `steps-c/step-03-generate-tests.md`
+
+**Which workflow was running**
+e.g. `test-design`, `automate`, `atdd`, `test-review`, `trace`, `nfr-assess`, `ci`, `framework`, `teach-me-testing`.
+
+**The prompt you gave**
+
+```text
+
+```
+
+**What it produced**
+The non-compliant part only. Trim to the smallest excerpt that still shows the violation.
+
+```text
+
+```
+
+**What it should have done**
+State the behavior the rule was supposed to produce, and why you read the rule as requiring it.
+
+**Your read of the cause** (optional)
+
+- [ ] The rule says the right thing and the agent ignored it
+- [ ] The rule is ambiguous and the agent picked a defensible wrong reading
+- [ ] The rule is wrong or out of date
+- [ ] The rule was never loaded (wrong fragment selected, or none)
+- [ ] Not sure

package/.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@v5
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v6
+        with:
+          node-version-file: ".nvmrc"
+          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://cordya-ai.github.io/froid-plane-test-architecture-enterprise
+          # To use custom domain, set SITE_URL repository variable to: https://test-architect.froid-plane.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/.github/workflows/publish.yaml

@@ -0,0 +1,193 @@
+name: Publish
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - "src/**"
+      - "package.json"
+      - "package-lock.json"
+  workflow_dispatch:
+    inputs:
+      channel:
+        description: "Publish channel"
+        required: true
+        default: "latest"
+        type: choice
+        options:
+          - latest
+          - next
+      bump:
+        description: "Version bump type (latest channel only)"
+        required: false
+        default: "patch"
+        type: choice
+        options:
+          - patch
+          - minor
+          - major
+
+concurrency:
+  group: publish-${{ github.event_name }}-${{ github.ref_name }}-${{ inputs.channel || 'push' }}
+  cancel-in-progress: ${{ github.event_name == 'push' }}
+
+permissions:
+  id-token: write
+  contents: write
+
+jobs:
+  publish:
+    if: github.repository == 'cordya-ai/froid-plane-test-architecture-enterprise' && (github.event_name != 'workflow_dispatch' || github.ref == 'refs/heads/main')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Generate GitHub App token
+        id: app-token
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        uses: actions/create-github-app-token@v3
+        with:
+          app-id: ${{ secrets.RELEASE_APP_ID }}
+          private-key: ${{ secrets.RELEASE_APP_PRIVATE_KEY }}
+
+      - name: Checkout
+        uses: actions/checkout@v5
+        with:
+          fetch-depth: 0
+          token: ${{ steps.app-token.outputs.token || secrets.GITHUB_TOKEN }}
+
+      - name: Setup Node
+        uses: actions/setup-node@v6
+        with:
+          node-version-file: ".nvmrc"
+          cache: "npm"
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Ensure trusted publishing toolchain
+        run: |
+          # npm trusted publishing requires modern npm on the runner.
+          npm install --global npm@11.6.2
+
+      - name: Configure git user
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests
+        run: npm test && npm run test:cli
+
+      - name: Derive next prerelease version
+        if: github.event_name == 'push' || (github.event_name == 'workflow_dispatch' && inputs.channel == 'next')
+        run: |
+          NEXT_VER=$(npm view froid-plane-test-architecture-enterprise@next version 2>/dev/null || echo "")
+          LATEST_VER=$(npm view froid-plane-test-architecture-enterprise@latest version 2>/dev/null || echo "")
+
+          BASE=$(node -e "
+            const semver = require('semver');
+            const next = process.argv[1] || null;
+            const latest = process.argv[2] || null;
+            if (!next && !latest) process.exit(0);
+            if (!next) { console.log(latest); process.exit(0); }
+            if (!latest) { console.log(next); process.exit(0); }
+            const nextBase = next.replace(/-next\.\d+$/, '');
+            console.log(semver.gte(latest, nextBase) ? latest : next);
+          " "$NEXT_VER" "$LATEST_VER")
+
+          if [ -n "$BASE" ]; then
+            npm version "$BASE" --no-git-tag-version --allow-same-version
+          fi
+          npm version prerelease --preid=next --no-git-tag-version
+
+      - name: Bump stable version
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: npm version "${{ inputs.bump }}" --no-git-tag-version
+
+      - name: Stamp CHANGELOG release section
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: node tools/stamp-changelog.js
+
+      - 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: Publish prerelease to npm
+        if: github.event_name == 'push' || (github.event_name == 'workflow_dispatch' && inputs.channel == 'next')
+        run: npm publish --tag next --provenance
+
+      - name: Commit version bump
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: |
+          VERSION=$(node -p 'require("./package.json").version')
+          git add package.json package-lock.json .claude-plugin/marketplace.json CHANGELOG.md
+          git commit -m "release: bump to v${VERSION} [skip ci]"
+          git tag -a "v${VERSION}" -m "Release v${VERSION}"
+
+      - name: Push version commit and tag
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: git push origin main --follow-tags
+
+      - name: Publish stable release to npm
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: npm publish --tag latest --provenance
+
+      - name: Create GitHub Release
+        if: github.event_name == 'workflow_dispatch' && inputs.channel == 'latest'
+        run: |
+          TAG="v$(node -p 'require("./package.json").version')"
+          VERSION="${TAG#v}"
+          has_release_notes() {
+            awk '
+              /^[[:space:]]*$/ { next }
+              /^[[:space:]]*-{3,}[[:space:]]*$/ { next }
+              { found = 1 }
+              END { exit found ? 0 : 1 }
+            ' <<< "$1"
+          }
+          BODY=$(awk -v ver="$VERSION" '
+            /^## / {
+              if (found) exit
+              if ($0 ~ ("^##[[:space:]]*\\[?[[:space:]]*v?" ver "[[:space:]]*\\]?([[:space:]]*-[[:space:]].*)?$")) found=1
+              next
+            }
+            found { print }
+          ' CHANGELOG.md)
+          if ! has_release_notes "$BODY"; then
+            BODY=$(awk '
+              /^##[[:space:]]*\[Unreleased\]/ { found=1; next }
+              /^## / {
+                if (found) exit
+                next
+              }
+              found { print }
+            ' CHANGELOG.md)
+            if has_release_notes "$BODY"; then
+              echo "::notice::No CHANGELOG.md entry for $TAG — using [Unreleased] notes"
+            fi
+          fi
+          if ! has_release_notes "$BODY"; then
+            echo "::warning::No CHANGELOG.md entry for $TAG — falling back to auto-generated notes"
+            gh release create "$TAG" --generate-notes
+          else
+            gh release create "$TAG" --notes "$BODY"
+          fi
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}