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/5-agentic-development/workflow-evolution.md

@@ -0,0 +1,64 @@
+---
+name: evolution
+description: Add features to existing products through targeted changes
+---
+
+# [E] Evolution — Add Features to Existing Product
+
+**Goal:** Incrementally add features to an existing product with minimal disruption.
+
+**When to use:** Existing product needs new functionality. Changes should be targeted, not a complete rewrite.
+
+---
+
+## CORE PRINCIPLES
+
+- **Backward compatible** — Existing functionality must keep working. Every change is verified against what already exists.
+- **Feature flags if needed** — When a change is risky or requires staged rollout, use feature flags to decouple deployment from activation.
+- **Incremental delivery** — Ship in small, verifiable increments. Each commit should leave the system in a working state.
+
+---
+
+## INITIALIZATION
+
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
+
+### Essential Guides
+
+- **[Execution Principles](data/guides/EXECUTION-PRINCIPLES.md)** — Document-first, plan-then-execute
+- **[Session Protocol](data/guides/SESSION-PROTOCOL.md)** — Read dialog, verify plan, present status
+- **[Inline Testing Guide](data/guides/INLINE-TESTING-GUIDE.md)** — Baseline capture before modifying existing features
+
+---
+
+## STEPS
+
+Execute steps in `./steps-e/`:
+
+| Step | File | Purpose |
+|------|------|---------|
+| 01 | step-01-scope-change.md | Define what changes vs what stays |
+| 02 | step-02-analyze-impact.md | Analyze impact on existing code |
+| 03 | step-03-plan-implementation.md | Plan incremental implementation |
+| 04 | step-04-implement.md | Implement changes |
+| 05 | step-05-verify-and-document.md | Verify, regression check, document |
+
+**Flow:** 01 → 02 → 03 → 04 → 05
+
+### Critical Rules
+
+- **ALWAYS** map what is new vs what is modified vs what is untouched before coding
+- **ALWAYS** capture baseline state of existing features before modifying them
+- **ALWAYS** verify backward compatibility at each commit
+- **ALWAYS** plan incremental commits — never one giant change
+- **NEVER** break existing functionality to add new functionality
+- **NEVER** skip impact analysis — surprises in production are expensive
+
+---
+
+## AFTER COMPLETION
+
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Evolution: [what was evolved/added]`
+2. Suggest acceptance testing (Phase 5 [T]) to validate the changes