Merge develop: fix stale product docs

Author: beyondnetPeru

reference/products/mcp-services/README.es.md

@@ -14,7 +14,7 @@ La superficie instalable exacta se genera desde las fuentes del CLI y no debe ma
 
 | Capacidad | Conteo | Ejemplos |
 |---|:---:|---|
-| **Tools** | 22 | `evolith-validate`, `evolith-composable-validate`, `evolith-gate-evaluate`, `evolith-architecture-validate`, `evolith-phase-advance`, `evolith-metrics` |
+| **Tools** | 25 | `evolith-validate`, `evolith-composable-validate`, `evolith-gate-evaluate`, `evolith-architecture-validate`, `evolith-phase-advance`, `evolith-auto-fix`, `evolith-drift-detect`, `evolith-dora-metrics`, `evolith-metrics` |
 | **Resources** | 7 | `evolith://rulesets`, `evolith://phase-gates`, `evolith://agents`, `evolith://core/version` |
 | **Prompts** | 7 | `evolith/validate-repository`, `evolith/architecture-review`, `evolith/sdlc-handoff`, `evolith/moscow-prioritization` |
 

reference/products/mcp-services/README.md

@@ -14,7 +14,7 @@ The exact, installable surface is generated from the CLI sources and must not be
 
 | Capability | Count | Examples |
 |---|:---:|---|
-| **Tools** | 22 | `evolith-validate`, `evolith-composable-validate`, `evolith-gate-evaluate`, `evolith-architecture-validate`, `evolith-phase-advance`, `evolith-metrics` |
+| **Tools** | 25 | `evolith-validate`, `evolith-composable-validate`, `evolith-gate-evaluate`, `evolith-architecture-validate`, `evolith-phase-advance`, `evolith-auto-fix`, `evolith-drift-detect`, `evolith-dora-metrics`, `evolith-metrics` |
 | **Resources** | 7 | `evolith://rulesets`, `evolith://phase-gates`, `evolith://agents`, `evolith://core/version` |
 | **Prompts** | 7 | `evolith/validate-repository`, `evolith/architecture-review`, `evolith/sdlc-handoff`, `evolith/moscow-prioritization` |
 

reference/products/smart-cli/README.es.md

@@ -73,7 +73,7 @@ Opciones:
   --format <formato>    Formato de salida: json, table, yaml, markdown
   --output <archivo>    Escribir salida a archivo
   --topology <nombre>   Validar contra topología específica (modular-monolith, distributed-modules, microservices)
-  --ruleset <id>        Validar ruleset específico (acl, open-core, inheritance)
+  --ruleset <id>        Validar ruleset específico (acl, open-core, inheritance, satellite-contracts)
   --engine <engine>     Motor de evaluación de políticas: native u opa (por defecto: native)
   --phase <id>          Validar contra fase SDLC específica (f1-f5)
   --manifest <ruta>     Usar manifest de topología para validación
@@ -86,17 +86,17 @@ El sistema de validación es inteligente y flexible — NO rígido. Puedes valid
 
 | Modo | Comando | Qué valida |
 |---|---|---|
-| **SDLC** | `evolith validate --phase f1` | Fase → Gate → Artifacts → Schemas → Rulesets → ADRs → OPA → Blocking |
-| **Arquitectura** | `evolith validate --topology modular-monolith` | Reglas de topología, límites hexagonales, aislamiento de dominio, multi-tenancy |
-| **Ruleset** | `evolith validate --ruleset compliance-baseline` | Ejecución de ruleset específico vía OPA |
-| **ADR** | `evolith validate --adr hexagonal-architecture` | Reglas arquitectónicas específicas de ADR |
-| **Ad-hoc** | `evolith validate --file src/domain/user.ts` | Validación de archivo/componente individual |
-| **Composable** | `evolith validate --topology modular-monolith --ruleset compliance-baseline` | Múltiples puntos de entrada combinados |
+| **SDLC** | `smart-cli validate --phase f1` | Fase → Gate → Artifacts → Schemas → Rulesets → ADRs → OPA → Blocking |
+| **Arquitectura** | `smart-cli validate --topology modular-monolith` | Reglas de topología, límites hexagonales, aislamiento de dominio, multi-tenancy |
+| **Ruleset** | `smart-cli validate --ruleset compliance-baseline` | Ejecución de ruleset específico vía OPA |
+| **ADR** | `smart-cli validate --adr hexagonal-architecture` | Reglas arquitectónicas específicas de ADR |
+| **Ad-hoc** | `smart-cli validate --file src/domain/user.ts` | Validación de archivo/componente individual |
+| **Composable** | `smart-cli validate --topology modular-monolith --ruleset compliance-baseline` | Múltiples puntos de entrada combinados |
 
 **Resolución Inteligente:**
-- `evolith validate` (sin params) → lee `evolith.config.json` para defaults
-- `evolith validate --topology modular-monolith` → infiere reglas de arquitectura para esa topología
-- `evolith validate --phase f1` → resuelve gate-f1 y sus artifacts requeridos
+- `smart-cli validate` (sin params) → lee `evolith.config.json` para defaults
+- `smart-cli validate --topology modular-monolith` → infiere reglas de arquitectura para esa topología
+- `smart-cli validate --phase f1` → resuelve gate-f1 y sus artifacts requeridos
 - El sistema combina todos los inputs proporcionados en el alcance óptimo de validación
 
 **Ejemplo `evolith.config.json` (defaults opcionales):**
@@ -316,6 +316,11 @@ smart-cli mcp serve --transport http --port 3000
 | `evolith-moscow-list` | Listar todos los análisis MoSCoW de un repositorio |
 | `evolith-moscow-validate` | Validar la corrección de un análisis MoSCoW |
 | `evolith-moscow-report` | Generar un reporte markdown desde un análisis MoSCoW |
+| `evolith-auto-fix` | Auto-corregir fallos arquitectónicos vía MCP |
+| `evolith-drift-detect` | Detectar deriva arquitectónica desde topología declarada |
+| `evolith-dora-metrics` | Obtener métricas DORA de ingeniería |
+| `evolith-gate-evaluate` | Evaluar criterios de gate de fase SDLC |
+| `evolith-phase-advance` | Avanzar a la siguiente fase SDLC |
 
 ### Configuración para Cursor AI
 
@@ -418,7 +423,7 @@ smart-cli validate --format markdown
 
 ### Comando no encontrado
 
-Si `evolith` no se encuentra después de la instalación, asegúrate de que el binario global de npm está en tu PATH:
+Si `smart-cli` no se encuentra después de la instalación, asegúrate de que el binario global de npm está en tu PATH:
 
 ```bash
 # Agregar a ~/.bashrc o ~/.zshrc

reference/products/smart-cli/README.md

@@ -73,7 +73,7 @@ Options:
   --format <format>     Output format: json, table, yaml, markdown
   --output <file>       Write output to file
   --topology <name>     Validate against specific topology (modular-monolith, distributed-modules, microservices)
-  --ruleset <id>        Validate specific ruleset (acl, open-core, inheritance)
+  --ruleset <id>        Validate specific ruleset (acl, open-core, inheritance, satellite-contracts)
   --engine <engine>     Policy evaluation engine: native or opa (default: native)
   --phase <id>          Validate against specific SDLC phase (f1-f5)
   --manifest <path>     Use topology manifest for validation
@@ -86,17 +86,17 @@ The validation system is intelligent and flexible — NOT rigid. You can validat
 
 | Mode | Command | What it validates |
 |---|---|---|
-| **SDLC** | `evolith validate --phase f1` | Phase → Gate → Artifacts → Schemas → Rulesets → ADRs → OPA → Blocking |
-| **Architecture** | `evolith validate --topology modular-monolith` | Topology rules, hexagonal limits, domain isolation, multi-tenancy |
-| **Ruleset** | `evolith validate --ruleset compliance-baseline` | Specific ruleset execution via OPA |
-| **ADR** | `evolith validate --adr hexagonal-architecture` | ADR-specific architectural rules |
-| **Ad-hoc** | `evolith validate --file src/domain/user.ts` | Individual file/component validation |
-| **Composable** | `evolith validate --topology modular-monolith --ruleset compliance-baseline` | Multiple entry points combined |
+| **SDLC** | `smart-cli validate --phase f1` | Phase → Gate → Artifacts → Schemas → Rulesets → ADRs → OPA → Blocking |
+| **Architecture** | `smart-cli validate --topology modular-monolith` | Topology rules, hexagonal limits, domain isolation, multi-tenancy |
+| **Ruleset** | `smart-cli validate --ruleset compliance-baseline` | Specific ruleset execution via OPA |
+| **ADR** | `smart-cli validate --adr hexagonal-architecture` | ADR-specific architectural rules |
+| **Ad-hoc** | `smart-cli validate --file src/domain/user.ts` | Individual file/component validation |
+| **Composable** | `smart-cli validate --topology modular-monolith --ruleset compliance-baseline` | Multiple entry points combined |
 
 **Intelligent Resolution:**
-- `evolith validate` (no params) → reads `evolith.config.json` for defaults
-- `evolith validate --topology modular-monolith` → infers architecture rules for that topology
-- `evolith validate --phase f1` → resolves gate-f1 and its required artifacts
+- `smart-cli validate` (no params) → reads `evolith.config.json` for defaults
+- `smart-cli validate --topology modular-monolith` → infers architecture rules for that topology
+- `smart-cli validate --phase f1` → resolves gate-f1 and its required artifacts
 - System combines all provided inputs into optimal validation scope
 
 **Example `evolith.config.json` (optional defaults):**
@@ -310,6 +310,11 @@ The smoke verifies `initialize`, `tools/list`, `resources/list`, `prompts/list`,
 | `evolith-moscow-list` | List all MoSCoW analyses for a repository |
 | `evolith-moscow-validate` | Validate a MoSCoW analysis for correctness |
 | `evolith-moscow-report` | Generate a markdown report from a MoSCoW analysis |
+| `evolith-auto-fix` | Auto-fix architectural failures via MCP |
+| `evolith-drift-detect` | Detect architecture drift from declared topology |
+| `evolith-dora-metrics` | Get DORA engineering metrics |
+| `evolith-gate-evaluate` | Evaluate SDLC phase gate criteria |
+| `evolith-phase-advance` | Advance to next SDLC phase |
 
 ### Cursor AI Configuration
 
@@ -412,7 +417,7 @@ smart-cli validate --format markdown
 
 ### Command not found
 
-If `evolith` is not found after installation, ensure npm's global bin is in your PATH:
+If `smart-cli` is not found after installation, ensure npm's global bin is in your PATH:
 
 ```bash
 # Add to ~/.bashrc or ~/.zshrc