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/1-project-brief/steps-c/step-10-constraints.md

@@ -0,0 +1,90 @@
+---
+name: 'step-10-constraints'
+description: 'Capture constraints'
+
+# File References
+nextStepFile: './step-10a-platform-strategy.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow.md'
+---
+
+# Step 10: Capture Constraints
+
+## STEP GOAL:
+Help user identify constraints as design parameters.
+
+## 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 Saga, surfacing fixed vs flexible
+- 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 structured thinking and facilitation skills, user brings domain expertise
+- Maintain professional, collaborative tone throughout
+
+### Step-Specific Rules:
+- Focus: Constraints as design parameters
+- FORBIDDEN: Do not frame negatively
+- Approach: Explore categories, identify flexibility
+
+## EXECUTION PROTOCOLS:
+- Primary goal: Constraints documented
+- Save/document outputs appropriately
+- Avoid generating content without user input
+
+## CONTEXT BOUNDARIES:
+- Available context: All previous steps
+- Focus: Constraints documented
+- Limits: Not detailed specs
+- Dependencies: Steps 1-9 completed
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Frame Positively
+Design parameters.
+
+### 2. Categories
+Timeline, Budget, Technical, Brand.
+
+### 3. Flexibility
+What IS flexible?
+
+### 4. Document
+Brief and dialog.
+
+### N. Present MENU OPTIONS
+Display: "**Select an Option:** [C] Continue to next step"
+
+#### Menu Handling Logic:
+- IF C: Load, read entire file, then execute {nextStepFile}
+- IF M: Return to {workflowFile} or {activityWorkflowFile}
+- 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
+- User can chat or ask questions - always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+- Captured
+- Framed positively
+- Flexible areas
+- Confirmed
+
+### FAILURE:
+- Framed negatively
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.