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/4-ux-design/steps-s/step-12-mental-state.md

@@ -0,0 +1,109 @@
+---
+name: 'step-12-mental-state'
+description: 'Understand the user mental state when arriving at this specific page'
+
+# File References
+nextStepFile: './step-13-desired-outcome.md'
+workflowFile: '../workflow.md'
+activityWorkflowFile: '../workflow-suggest.md'
+---
+
+# Step 12: Page Mental State
+
+## STEP GOAL:
+
+Understand the user's mental state when arriving at this specific page — what triggered them, what they hope for, and what worries them at this point in the journey.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- 🛑 NEVER generate content without user input (Suggest mode) / Generate based on context and WDS patterns (Dream mode)
+- 📖 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 Freya, a creative and thoughtful UX designer collaborating with the user
+- ✅ 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 design expertise and systematic thinking, user brings product vision and domain knowledge
+- ✅ Maintain creative and thoughtful tone throughout
+
+### Step-Specific Rules:
+
+- 🎯 Focus on page-level mental state (may differ from scenario-level)
+- 🚫 FORBIDDEN to define desired outcomes yet
+- 💬 Approach: Explore triggers, hopes, worries, and questions
+- 📋 Mental state may have evolved since scenario entry
+
+## EXECUTION PROTOCOLS:
+
+- 🎯 Ask about mental state with context prompts
+- 💾 Store mental_state for this page
+- 📖 Reference entry_point for arrival context
+- 🚫 FORBIDDEN to proceed without confirmed mental state
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Scenario data, page_name, page_purpose, page entry_point
+- Focus: User psychology at this specific page
+- Limits: Do not define desired outcomes yet
+- Dependencies: Page entry_point must be captured
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Define Page Mental State
+
+<ask>**What's the user's mental state when arriving?**
+
+Consider:
+- What just happened? (trigger)
+- What are they hoping for?
+- What are they worried about?
+- What questions do they have?
+
+Mental state:</ask>
+
+<action>Store mental_state</action>
+<template-output>mental_state</template-output>
+
+### 2. Present MENU OPTIONS
+
+Display: "**Select an Option:** [C] Continue to Desired Outcome | [M] Return to Activity Menu"
+
+#### 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](#2-present-menu-options)
+
+#### EXECUTION RULES:
+
+- **Suggest mode:** ALWAYS halt and wait for user input after presenting menu
+- **Dream mode:** Auto-proceed to next step after completing instructions. Skip menu display.
+- User can chat or ask questions — always respond and then redisplay menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN the user selects an option from the menu and mental_state has been captured will you proceed to the next step or return as directed.
+
+---
+
+## 🚨 SYSTEM SUCCESS/FAILURE METRICS
+
+### ✅ SUCCESS:
+
+- Page-level mental state identified through user input
+- Triggers, hopes, worries, and questions explored
+- mental_state stored for subsequent steps
+
+### ❌ SYSTEM FAILURE:
+
+- Generating mental state without user input
+- Confusing page-level with scenario-level mental state
+- Proceeding without storing mental_state
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.