chore: initial monorepo scaffold + WDS Phase 1+2 artifacts

- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24)
- apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004)
- apps/web: React 19 + Vite 8 (ESM)
- libs/shared/api-interface: Zod contract base
- Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit
- WDS artifacts:
  - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs)
  - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact)
- Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md
- AGENTS.md + README.md como entrada para devs/agentes

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

_bmad/tea/workflows/testarch/README.md

@@ -0,0 +1,77 @@
+# TEA Workflow Step Files
+
+This folder contains the Test Architect (TEA) workflows converted to skill-driven step-file architecture for strict LLM compliance. Each workflow is tri-modal (create, edit, validate) and uses small, ordered step files routed from `SKILL.md` instead of a single monolithic instruction file.
+
+## Why Step Files
+
+- Enforces sequential execution and prevents improvisation
+- Keeps context small and focused per step
+- Makes validation and edits deterministic
+
+## Standard Layout (per workflow)
+
+```
+<workflow>/
+├── SKILL.md                # Canonical entrypoint and mode routing
+├── customize.toml          # Workflow customization surface
+├── workflow-plan.md        # Design reference for step order and intent
+├── workflow.yaml           # Installer metadata
+├── instructions.md         # Short entrypoint / summary
+├── checklist.md            # Validation criteria for outputs
+├── steps-c/                # Create mode steps
+├── steps-e/                # Edit mode steps
+├── steps-v/                # Validate mode steps
+├── templates/              # Output templates (if applicable)
+└── validation-report-*.md  # Validator outputs (latest run)
+```
+
+## Modes
+
+- **Create (steps-c/):** Primary execution flow to generate outputs
+- **Edit (steps-e/):** Structured edits to existing outputs
+- **Validate (steps-v/):** Checklist-based validation of outputs
+
+## Execution Rules (Summary)
+
+- Load **one step at a time**. Do not preload future steps.
+- Follow the **MANDATORY SEQUENCE** exactly in each step.
+- Do not skip steps, reorder, or improvise.
+- If a step writes outputs, do so **before** loading the next step.
+
+## Step Naming Conventions
+
+- `step-01-*.md` is the init step (no menus unless explicitly required).
+- `step-01b-*.md` is a continuation/resume step if the workflow is continuable.
+- `step-0X-*.md` are sequential create-mode steps.
+- `steps-v/step-01-validate.md` is the validate mode entrypoint.
+- `steps-e/step-01-assess.md` is the edit mode entrypoint.
+
+## Validation
+
+- Each workflow has a latest `validation-report-*.md` in its folder.
+- Validation uses the BMad Builder workflow validator (workflow-builder).
+- The goal is 100% compliance with no warnings.
+
+## References
+
+- Step-file architecture: `docs/explanation/step-file-architecture.md`
+- Subagent patterns: `docs/explanation/subagent-architecture.md`
+
+## TEA Workflows
+
+- teach-me-testing
+- test-design
+- framework
+- ci
+- atdd
+- automate
+- test-review
+- nfr-assess
+- trace
+
+## Notes
+
+- `SKILL.md` is the canonical entrypoint. `instructions.md` is a short summary for quick context.
+- `customize.toml` defines activation hooks, persistent facts, and the optional `on_complete` hook.
+- Output files typically use `{test_artifacts}` or `{project-root}` variables.
+- If a workflow produces multiple artifacts (e.g., system-level vs epic-level), the step file will specify which templates and output paths to use.