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>

.agents/skills/bmad-story-automator/data/subagent-prompts-analysis.md

@@ -0,0 +1,87 @@
+# Sub-Agent Analysis Prompts
+
+**Purpose:** Analysis-focused prompt templates for sub-agents spawned during story-automator execution.
+
+**Related:** See `subagent-prompts.md` for core execution prompts (parser, reader, updater).
+
+---
+
+## Code Review Analyzer
+
+**Use:** Analyze code review output to determine review status and next steps.
+
+**Prompt:**
+```
+You are a code review analyzer. Analyze the code review session output.
+
+Story: {story_name}
+Review cycle: {cycle_number} of 3
+Review output:
+---
+{review_output}
+---
+
+Determine the review outcome by looking for:
+1. "Story Status: done" or "Story Status: in-progress"
+2. "Issues Fixed: N" count
+3. "Issues Found: N High, N Medium, N Low"
+
+Return:
+{
+  "storyStatus": "done|in-progress|unknown",
+  "issuesFixed": N,
+  "highIssues": N,
+  "mediumIssues": N,
+  "lowIssues": N,
+  "recommendation": "proceed|retry|escalate",
+  "summary": "brief description of outcome"
+}
+```
+
+**Decision logic:**
+- storyStatus == "done" → proceed (exit review loop)
+- storyStatus == "in-progress" → retry (new review cycle needed)
+- storyStatus == "unknown" → check sprint-status.yaml directly
+
+**CRITICAL:** The orchestrator MUST verify sprint-status.yaml after review completes. The sub-agent analysis is advisory; sprint-status.yaml is the source of truth.
+
+---
+
+## Dependency Analyzer
+
+**Use:** Analyze stories for parallel execution safety.
+
+**Prompt:**
+```
+You are a dependency analyzer. Determine if these stories can safely run in parallel.
+
+Stories to analyze:
+{stories_list}
+
+For each pair of stories, check for:
+- File conflicts (modifying same files)
+- Logical dependencies (one builds on another)
+- Resource conflicts (same database tables, API endpoints)
+- Test conflicts (interfering test data)
+
+Return:
+{
+  "parallelSafe": true|false,
+  "conflicts": [
+    {
+      "story1": "...",
+      "story2": "...",
+      "conflictType": "file|logical|resource|test",
+      "description": "..."
+    }
+  ],
+  "recommendation": "parallel|sequential|partial",
+  "suggestedOrder": ["story order if sequential needed"]
+}
+```
+
+**Parallel safety indicators:**
+- Different feature areas → likely safe
+- Same component/module → check files
+- Database migrations → sequential only
+- Shared test fixtures → check for conflicts