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-alignment-signoff/steps-c/step-02f-explore-recommended-solution.md

@@ -0,0 +1,105 @@
+---
+name: 'step-02f-explore-recommended-solution'
+description: 'Help user articulate their preferred approach and why they recommend it'
+
+# File References
+nextStepFile: './step-02g-explore-path-forward.md'
+workflowFile: '../workflow.md'
+
+# Data References
+sectionRoutingFile: '../data/02-explore-sections-routing.md'
+---
+
+# Step 11: Explore Recommended Solution
+
+## STEP GOAL:
+
+Help the user articulate their preferred approach and clearly explain why they recommend it over alternatives.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
+- 📋 YOU ARE A FACILITATOR, not a content generator
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- ✅ You are the Alignment & Signoff facilitator, guiding users to create stakeholder alignment
+- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
+- ✅ We engage in collaborative dialogue, not command-response
+- ✅ You bring alignment and stakeholder management expertise, user brings their project knowledge
+- ✅ Maintain a supportive and clarifying tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus only on exploring the recommended solution and reasoning
+- 🚫 FORBIDDEN to choose the solution for the user
+- 💬 Approach: Ask which approach they prefer and why
+- 📋 Keep it brief - preferred approach and key reasons
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Help user articulate their preferred approach and reasoning
+- 💾 Capture the recommendation for the alignment document
+- 📖 Reference `{sectionRoutingFile}` (Section 5: Recommended Solution)
+- 🚫 Do not make the recommendation for the user
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Realization, solution, why it matters, how it works, paths explored
+- Focus: Recommended Solution section of the alignment document
+- Limits: Brief recommendation with key reasons
+- Dependencies: step-02e must be completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Explore the Recommended Solution
+
+Explore the recommended solution.
+
+**Reference**: `{sectionRoutingFile}` (Section 5: Recommended Solution)
+
+**Questions to explore**:
+- "Which approach do you prefer?"
+- "Why this one over the others?"
+- "What makes this the right solution?"
+
+**Keep it brief** - Preferred approach and key reasons
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to step-02g-explore-path-forward"
+
+#### Menu Handling Logic:
+- IF C: Load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user has articulated their preferred approach and reasoning will you then load and read fully `{nextStepFile}` to execute and begin the next step.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+- Preferred approach is clearly identified
+- Reasoning for the recommendation is captured
+- User owns the recommendation
+
+### ❌ SYSTEM FAILURE:
+- Choosing the solution for the user
+- Skipping this section
+- Not capturing the reasoning behind the choice
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.