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>

.claude/skills/wds-4-ux-design/data/scenario-init/06-shortest-path.md

@@ -0,0 +1,92 @@
+# Question 5: What's the Shortest Path?
+
+**Map the minimum journey from starting point to mutual success**
+
+---
+
+## The Question
+
+```
+Agent: "Let's map the shortest possible journey from
+        [starting point] to [mutual success]:
+
+        What's the absolute minimum path?"
+```
+
+---
+
+## Why This Matters
+
+Shortest path means:
+
+- No unnecessary steps
+- No feature bloat
+- Clear focus
+- Faster to mutual success
+
+**Every extra step is a chance to lose the user.**
+
+---
+
+## Example: Dog Week
+
+```
+Agent: "From 'frustrated parent on Google' to 'active subscription + harmony':
+        What's the minimum path?"
+
+Designer: "Google → Landing page → See how it works →
+           Sign up → Set up family → Start using calendar →
+           First walk completed → Everyone happy"
+```
+
+**Why this path:**
+
+- Landing: Understand solution (addresses frustration)
+- How it works: See it's simple (addresses complexity fear)
+- Sign up: Commit to trying (low friction)
+- Family setup: Get everyone involved (necessary for accountability)
+- Calendar: Plan first week (immediate action)
+- First walk: Proof it works (mutual success moment)
+
+---
+
+## What Agent Captures
+
+```
+SCENARIO: Parent Onboarding to First Success
+
+START: Google search (frustrated, tired of nagging)
+END: First walk completed (harmony, system working)
+
+CRITICAL PATH:
+1. Landing page → Understand solution
+2. Sign up → Commit to trying
+3. Family setup → Get everyone involved
+4. Calendar → Plan first week
+5. First walk → Proof it works
+
+BUSINESS GOAL: Active subscription
+USER GOAL: Family harmony without nagging
+
+Each step serves the journey. Nothing extra.
+```
+
+---
+
+## Next Step
+
+With all 5 questions answered, you have:
+
+- ✅ Core feature (what to design)
+- ✅ Entry point (where to start)
+- ✅ Mental state (how they feel)
+- ✅ Mutual success (where to end)
+- ✅ Shortest path (how to get there)
+
+**→ Proceed to [Step 7: Reference Trigger Map](07-reference-trigger-map.md)**
+
+Before sketching, identify the relevant Trigger Map context for this scenario.
+
+---
+
+[← Back to Guide](00-SCENARIO-INIT-GUIDE.md)