docs: update all documentation and add AI tooling configs

- Rewrite README.md with current architecture, features and stack
- Update docs/API.md with all current endpoints (corporate, BI, client 360)
- Update docs/ARCHITECTURE.md with cache, modular queries, services, ETL
- Update docs/GUIA-USUARIO.md for all roles (admin, corporate, agente)
- Add docs/INDEX.md documentation index
- Add PROJETO.md comprehensive project reference
- Add BI-CCC-Implementation-Guide.md
- Include AI agent configs (.claude, .agents, .gemini, _bmad)
- Add netbird VPN configuration
- Add status report

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

_bmad/wds/workflows/0-project-setup/templates/folder-guides/00-trigger-map.template.md

@@ -0,0 +1,66 @@
+# Trigger Map: {{project_name}}
+
+> Connect business goals to user psychology — understand why people act, not just what they do.
+
+**Created:** {{date}}
+**Phase:** 2 — Trigger Mapping
+**Agent:** Saga (Analyst)
+
+---
+
+## What Belongs Here
+
+The Trigger Map reveals the human forces behind product decisions through five workshops:
+
+1. **Business Goals** — What the business needs to achieve
+2. **Target Groups** — Who the users are (with alliterative persona names)
+3. **Driving Forces** — What motivates and frightens each persona (positive + negative)
+4. **Prioritization** — Which forces matter most (scored by frequency, intensity, fit)
+5. **Feature Impact** — How product features address the highest-priority forces
+
+This folder feeds directly into Phase 4 (UX Scenarios). Every page spec should trace back to a driving force documented here.
+
+**Learn more:**
+- WDS Course Module 06: Trigger Mapping — Connect Business Goals to User Psychology
+- WDS Course Module 06, Lessons 4–8: The Five Workshops
+
+---
+
+## For Agents
+
+**Workflow:** `_bmad/wds/workflows/2-trigger-mapping/workflow.md`
+**Agent trigger:** `TM` (Saga)
+**Templates:** `_bmad/wds/workflows/2-trigger-mapping/templates/`
+
+**Before writing anything in this folder:**
+1. Read the Product Brief in `A-Product-Brief/` — trigger mapping builds on it
+2. Load the workflow and follow the five workshop sequence
+3. Use Dialog mode — personas emerge from conversation, not invention
+
+**File naming:** Number all documents with a two-digit prefix: `01-business-goals.md`, `02-lars-the-loyal.md`, etc. One file per persona. Update the Documents table below as each file is created.
+
+**Harm:** Inventing personas without discovery. Fabricated driving forces produce scenarios that solve imaginary problems. The user pays to correct work that should never have been written.
+
+**Help:** Uncovering real psychology through conversation. When driving forces are authentic, every downstream design decision has a clear "why."
+
+---
+
+## Documents
+
+_This section will be updated as documents are created during Phase 2._
+
+| # | Document | Purpose | Status |
+|---|----------|---------|--------|
+| 01 | Business Goals | Vision, objectives, metrics | Not started |
+| 02+ | Persona files | One per target group | Not started |
+| — | Feature Impact Analysis | Forces × features scoring | Not started |
+
+---
+
+## Trigger Map Visualization
+
+_A mermaid diagram connecting goals → platform → personas → forces will be added here during Phase 2._
+
+---
+
+_Created using Whiteport Design Studio (WDS) methodology_