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>
This commit is contained in:
2026-05-27 14:34:20 +00:00
commit 17c08e6392
3631 changed files with 855518 additions and 0 deletions

View File

@@ -0,0 +1,76 @@
# Escalation Message Templates (Extended)
## 5. Unexpected Error
**Escalation message:**
```
🔔 DECISION NEEDED: Unexpected Error
Story: {story_name}
Step: {step_name}
Error: {error_message}
An unexpected error occurred during orchestration.
Options:
[1] Retry current step
[2] Skip current step
[3] Abort story and continue with next
[4] Pause orchestration for investigation
Select option:
```
---
## 6. Dependency Conflict
**Escalation message:**
```
🔔 DECISION NEEDED: Potential Dependency Conflict
Stories in parallel: {story_list}
Detected conflict: {conflict_description}
These stories may have conflicting changes.
Options:
[1] Continue in parallel (accept risk)
[2] Run sequentially instead
[3] Pause for manual review
Select option:
```
---
## 7. Dev-Story Implementation Failure
**Pre-escalation behavior:**
1. Check blocking status (conservative if uncertain)
2. If BLOCKING: retry up to 3 times
3. If NOT BLOCKING: retry once
**Escalation message:**
```
🔔 DECISION NEEDED: Dev-Story Implementation Failure
Story: {story_name}
Step: dev-story
Attempts: {attempt_count}
Blocking: {yes/no} (affects stories: {list or "none"})
Latest error:
{error_summary}
Options:
[1] Retry dev-story - Spawn new session to fix
[2] Manual fix - Pause orchestration so you can fix it
[3] View session output - See full output
[4] Skip story - Move to next (only if not blocking)
[5] Abort orchestration - Stop entire build cycle
Select option:
```
**Note:** Option [4] only valid if story is NOT blocking.