@christianmaf80/agentic-workflow 1.24.0-beta.3 → 1.25.0-beta.3

package/dist/agent/artifacts/14-re-implement-setup-config-d1/researcher/research.md

@@ -0,0 +1,113 @@
+---
+artifact: research
+phase: phase-1-research
+owner: researcher-agent
+status: approved
+related_task: 14-re-implement-setup-config-d1
+---
+
+# Research Report — 14-Re-implement Setup/Config (D1)
+
+## Agent Identification (MANDATORY)
+🔬 **researcher-agent**: Researching Secure Storage and Material Design UI.
+
+> [!CAUTION]
+> **PERMANENT RULE**: This document is ONLY documentation.
+> The researcher-agent documents findings WITHOUT analyzing, WITHOUT recommending, WITHOUT proposing solutions.
+> Analysis belongs to Phase 2.
+
+## 1. Executive Summary
+- **Problem investigated**: How to implement a secure, persistent configuration system and a Google Material Design UI in VS Code.
+- **Research objective**: Identify the correct storage APIs for secrets vs generic settings and confirm the toolchain for Lit + Material 3 implementation.
+- **Key findings**:
+  - **Secrets (API Keys)**: MUST use `vscode.SecretStorage`.
+  - **Generic Settings**: `vscode.GlobalState` or `vscode.WorkspaceConfiguration`.
+  - **UI**: `@material/web` provides official Google Material 3 components compatible with Lit.
+
+---
+
+## 2. Detected Needs
+1.  **Secure Storage**: Secure encryption for OAuth tokens and API keys.
+2.  **Persistence**: Settings must survive restart.
+3.  **UI Fidelity**: Strict adherence to "Google Material Design" (not just VS Code native look).
+4.  **Isolation**: Core layer must mediate access; UI cannot read secrets directly.
+
+---
+
+## 3. Technical Findings
+
+### Secure Storage Mechanism
+- **Generic Settings** (Language, Theme, Model):
+  - **`vscode.ExtensionContext.globalState`**: Best for extension-specific state that doesn't need to be edited by the user in `settings.json`. Syncs across machines if configured.
+  - **`vscode.workspace.getConfiguration`**: Best if we want users to edit settings via standard VS Code Settings UI.
+  - **Finding**: Given the requirement for a *custom* UI, `globalState` acts better as a controlled database, whereas `getConfiguration` might conflict if the user edits `settings.json` manually.
+
+- **Secrets** (API Keys):
+  - **`vscode.ExtensionContext.secrets`**: Uses system keychain (macOS Keychain, Windows Credential Manager).
+  - **Constraint**: Asynchronous API (`get`, `store`, `delete`).
+  - **Security**: Data is encrypted at rest.
+
+### Google Material Design with Lit
+- **Library**: [`@material/web`](https://github.com/material-components/material-web) (Material 3).
+- **Integration**:
+  - Published as standard Web Components.
+  - Fully compatible with Lit (`import '@material/web/button/filled-button.js'`).
+  - **Constraint**: Material 3 uses CSS variables that might clash or look out of place in VS Code's theme unless carefully scoped or themed.
+  - **Alternative**: VS Code Webview UI Toolkit (VS Code native look), but user specifically requested **Google Material Design**.
+
+### Event Bus Architecture
+- **Pattern**: Request/Response.
+- **Flow**:
+  1. UI sends `GetSettingsRequest`.
+  2. Background (Core) reads `SecretStorage` + `GlobalState`.
+  3. Background returns `SettingsPayload` (with masked keys for display).
+  4. UI renders.
+  5. UI sends `SaveSettingsRequest` (with new plain text keys if changed).
+  6. Background writes to storages.
+
+---
+
+## 4. Relevant APIs
+- `context.secrets.store(key, value)` / `context.secrets.get(key)`
+- `context.globalState.update(key, value)` / `context.globalState.get(key)`
+- `webview.postMessage` / `webview.onDidReceiveMessage`
+
+---
+
+## 5. Multi-browser Compatibility
+- **Storage**: VS Code APIs abstract the underlying OS storage. Works in Web/Codespaces (Secrets are stored in server-side browser storage or mocked).
+- **UI**: Web Components are standard and work in all modern webviews.
+
+---
+
+## 6. Detected AI-first Opportunities
+- **Auto-configuration**: The system could potentially detect standard keys in `process.env` or `.env` files to pre-fill the setup (optional, not in strict scope but possible).
+
+---
+
+## 7. Identified Risks
+1.  **Material 3 vs VS Code Theme**:
+    - **Risk**: Material 3 has its own color system. It might not respect VS Code's High Contrast or Dark/Light theme switching automatically.
+    - **Severity**: Medium. Requires explicit CSS variable mapping (`--md-sys-color-primary: var(--vscode-button-background)`).
+
+2.  **Secret Persistence**:
+    - **Risk**: Secrets are improperly cached in memory or passed to the UI in plain text.
+    - **Mitigation**: Never send plain text keys to UI *unless* explicitly revealing (which is discouraged). Send masks (e.g., `sk-...XXXX`).
+
+---
+
+## 8. Sources
+- [VS Code Extension API: SecretStorage](https://code.visualstudio.com/api/references/vscode-api#SecretStorage)
+- [Material Web (M3)](https://github.com/material-components/material-web)
+- [Lit Documentation](https://lit.dev)
+
+---
+
+## 9. Developer Approval (MANDATORY)
+```yaml
+approval:
+  developer:
+    decision: SI
+    date: 2026-02-16T12:18:19+01:00
+    comments: "Approved via chat"
+```

package/dist/agent/artifacts/14-re-implement-setup-config-d1/task.md

@@ -0,0 +1,107 @@
+---
+id: 14
+title: Re-implement Setup/Config (D1)
+owner: architect-agent
+strategy: long
+---
+
+# Task (Definitive)
+
+## Identification
+- id: 14
+- title: Re-implement Setup/Config (D1)
+- scope: current
+- owner: architect-agent
+
+## Origin
+- created_from:
+  - workflow: tasklifecycle-long
+  - source: init
+  - candidate_path: artifacts.candidate.task
+
+## Task Description
+Re-implement the Setup and Configuration domain (D1) as a **Standalone Module**.
+The App Shell must be refactored to support a **Tab-based Module System** (Settings, Chat, History, Agents).
+The Settings Module will be responsible for its own data (LLM Registry, Keys) and UI, exposing only necessary state (Active Model) to the system.
+
+## Objective
+1. Define `Module` Interface in Core.
+2. Implement Tab-based Navigation in App Shell.
+3. Implement `SettingsModule` with Lit+Material UI.
+4. implementations must use **Scaffolding Skill**.
+
+## Lifecycle State (SINGLE SOURCE OF TRUTH)
+
+```yaml
+task:
+  id: "14"
+  title: "Re-implement Setup/Config (D1)"
+  strategy: "long"
+  artifacts:
+    supplemental: []
+  phase:
+    current: "phase-4-implementation"
+    validated_by: "architect-agent"
+    updated_at: "2026-02-16T18:30:00+01:00"
+  lifecycle:
+    phases:
+      phase-0-acceptance-criteria:
+        completed: true
+        validated_by: "architect-agent"
+        validated_at: "2026-02-16T12:14:51+01:00"
+      phase-1-research:
+        completed: true
+        validated_by: "architect-agent"
+        validated_at: "2026-02-16T12:18:19+01:00"
+      phase-2-analysis:
+        completed: true
+        validated_by: "architect-agent"
+        validated_at: "2026-02-16T16:02:19+01:00"
+      phase-3-planning:
+        completed: true
+        validated_by: "architect-agent"
+        validated_at: "2026-02-16T18:18:27+01:00"
+      phase-4-implementation:
+        completed: false
+        validated_by: null
+        validated_at: null
+      phase-5-verification:
+        completed: false
+        validated_by: null
+        validated_at: null
+      phase-6-results-acceptance:
+        completed: false
+        validated_by: null
+        validated_at: null
+      phase-7-evaluation:
+        completed: false
+        validated_by: null
+        validated_at: null
+      phase-8-commit-push:
+        completed: false
+        validated_by: null
+        validated_at: null
+    subflows:
+      components:
+        create: []
+        refactor: []
+        delete: []
+```
+
+---
+
+## 2. Definition and Scope (Contract)
+- **Acceptance Criteria**: [acceptance.md](file:///.agent/artifacts/14-re-implement-setup-config-d1/acceptance.md)
+- **Alias**: `task.acceptance`
+
+---
+
+## Contractual Rules
+- This file is the **single source of truth** of the task state.
+- The `task.phase.current` field can **ONLY be modified by `architect-agent`**.
+- The `task.lifecycle.phases.*` field can **ONLY be marked as completed by `architect-agent`**.
+- A phase **CANNOT be marked as completed** if it is not the current phase.
+- Phase advancement requires:
+  1. Marking the current phase as `completed: true`
+  2. Explicit architect validation
+  3. Updating `task.phase.current` to the next phase

package/dist/agent/artifacts/14-re-implement-setup-config-d1/verification/walkthrough.md

@@ -0,0 +1,37 @@
+# Walkthrough: Task 14 - Re-implement Setup/Config (D1)
+
+## 1. Scaffolding Infrastructure
+- **Tool**: Yeoman Generator implemented in `src/cli/skills/scaffolding`.
+- **Capability**: Generates new Agentic Modules with standard structure (Backend, View, Index).
+- **Compliance**:
+  - **ESM**: Generator uses ES Modules.
+  - **Naming**: Classes named after Module (e.g., `Settings`, not `SettingsService`).
+  - **View**: Separated Logic (`index.ts`) and Templates (`templates/main/html.ts`, `css.ts`).
+
+## 2. Settings Module Implementation
+- **Location**: `src/extension/modules/settings`.
+- **Backend**: `Settings` class handles `LLMModelConfig` and persistence.
+- **View**: `Settings` class using Lit + Material Web Components.
+  - **Templates**: Located in `view/templates/main`.
+  - **Components**: `model-list` (display) and `model-form` (edit).
+- **Integration**:
+  - **App Shell**: `AppBackground` imports `Settings` and delegates messages.
+  - **Context**: `ExtensionContext` passed for Secret Storage access.
+
+## 3. Core Services
+- **ConfigurationService**: Wrapper for `vscode.workspace.getConfiguration`.
+- **SecretStorageService**: Wrapper for `vscode.SecretStorage`.
+- **Module Interface**: `IModule` definition for standardization.
+
+## 4. Verification
+### Compilation
+- Project compiles successfully with `npm run compile`.
+- strict linting rules applied (except for excluded templates).
+
+### Generator Test
+- Validated `scaffold-module` workflow by generating a test module (`test-mod`).
+- Verified strict file structure and template replacement.
+
+## Next Steps
+- **Manual Verification**: Run extension in VS Code to test UI.
+- **Phase 5**: Proceed to formal verification if needed (integration tests).

package/dist/agent/artifacts/2-scaffold-vscode-chat-ai-panel/acceptance.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: acceptance
-source: agentic-system-structure
----
-
 🏛️ **architect-agent**: Acceptance criteria definidos para el scaffolding del chat AI en la extension de VS Code.
 
 # Acceptance Criteria — 2-scaffold-vscode-chat-ai-panel

package/dist/agent/artifacts/2-scaffold-vscode-chat-ai-panel/task.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: task
-source: agentic-system-structure
----
-
 # Task (Template)
 
 ## Identificación

package/dist/agent/artifacts/3-new-vscode-agentic-activitybar-chat/acceptance.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: acceptance
-source: agentic-system-structure
----
-
 🏛️ **architect-agent**: Acceptance criteria definidos para nuevo proyecto vscode-agentic.
 
 # Acceptance Criteria — 3-new-vscode-agentic-activitybar-chat

package/dist/agent/artifacts/3-new-vscode-agentic-activitybar-chat/task.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: task
-source: agentic-system-structure
----
-
 # Task (Template)
 
 ## Identificación

package/dist/agent/artifacts/4-copiar-estructura-agentic-cliente/acceptance.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: acceptance
-source: agentic-system-structure
----
-
 # Acceptance Criteria — 4-copiar-estructura-agentic-cliente
 
 🏛️ **architect-agent**: Consolidando criterios de aceptacion para copia completa de `.agent` en cliente.

package/dist/agent/artifacts/4-copiar-estructura-agentic-cliente/architect/implementation.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: implementation
-source: agentic-system-structure
----
-
 # Informe de Implementacion — 4-copiar-estructura-agentic-cliente
 
 🏛️ **architect-agent**: Implementacion verificada para copia completa de `.agent` en cliente.

package/dist/agent/artifacts/5-reestructurar-src-para-extension-vscode/acceptance.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: acceptance
-source: agentic-system-structure
----
-
 # Acceptance Criteria — 5-reestructurar-src-para-extension-vscode
 
 🏛️ **architect-agent**: Definición de criterios de aceptación para la reestructuración de src y scaffolding de extensión VSCode.

package/dist/agent/artifacts/5-reestructurar-src-para-extension-vscode/agent-tasks/1-dev-agent-reestructurar-carpetas.md

@@ -64,7 +64,7 @@ execution:
 
 ### Cambios realizados
 - Creado directorio `src/agentic-system-structure`.
-- Movido `src/cli`, `src/infrastructure`, `src/rules`, `src/templates`, `src/workflows`, `src/artifacts`, `src/index.md` a la nueva ubicación.
+- Movido `src/cli`, `src/core`, `src/rules`, `src/templates`, `src/workflows`, `src/artifacts`, `src/index.md` a la nueva ubicación.
 
 ### Decisiones técnicas
 - Uso de `mv` con múltiples argumentos para atomizar la operación.

package/dist/agent/artifacts/5-reestructurar-src-para-extension-vscode/task.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: task
-source: agentic-system-structure
----
-
 # Task: Reestructurar src para Extensión VSCode
 
 ## Identificación

package/dist/agent/artifacts/6-release-beta-11/task.md

@@ -1,9 +1,3 @@
----
-kind: artifact
-name: task
-source: agentic-system-structure
----
-
 # Task: Release Beta 1.18.0-beta.11
 
 ## Identificación

package/dist/agent/artifacts/7-extension-vscode-webview/acceptance.md

@@ -0,0 +1,70 @@
+# Acceptance Criteria — task-20260130-extension-vscode-webview-Crear extensión VS Code con webview en activity bar
+
+## Identificacion del agente (OBLIGATORIA)
+Primera linea del documento:
+`<icono> **<nombre-agente>**: <mensaje>`
+
+🏛️ **architect-agent**: Acceptance criteria definidos para la extensión VS Code con webview.
+
+## 1. Definición Consolidada
+Crear una extensión de VS Code dentro de `src/extension` que agregue un contenedor en la activity bar con **icono propio** (SVG minimalista) y muestre una vista basada en WebviewViewProvider con script y estado básico “Hello world”. La jerarquía de vistas estará en `src/extension/views` y un `index.ts` ESM exportará las vistas (inicialmente `MainChatView`). Debe declarar compatibilidad con la última versión estable de VS Code.
+
+## 2. Respuestas a Preguntas de Clarificación
+> Esta sección documenta las respuestas del desarrollador a las 5 preguntas formuladas por el architect-agent.
+
+| # | Pregunta (formulada por architect) | Respuesta (del desarrollador) |
+|---|-----------------------------------|-------------------------------|
+| 1 | ¿Nombre del viewsContainers.activitybar.id y del views.<container>.id? | `viewsContainers.activitybar.id = main` y `views.<container>.id = mainView`. |
+| 2 | ¿Contenido mínimo esperado del Webview? | WebviewViewProvider con script y estado básico “Hello world”. |
+| 3 | ¿Qué vistas concretas en `src/extension/views/` y export desde `index.ts`? | `MainChatView` desde `./main-view` y exportado en `views/index.ts`. |
+| 4 | ¿Versión exacta de VS Code para `engines.vscode`? | Última estable (propuesta `^1.108.2`). |
+| 5 | ¿Activación de la extensión? | `onView` cuando se clickea el botón en la activity bar. |
+
+---
+
+## 3. Criterios de Aceptación Verificables
+> Listado de criterios derivados de las respuestas anteriores que deben ser verificados en la Fase 5.
+
+1. Alcance:
+   - La extensión agrega un contenedor en activity bar con **icono propio** y una vista webview asociada.
+
+2. Entradas / Datos:
+   - Estructura en `src/extension` con `views` y `views/index.ts` ESM exportando `MainChatView`.
+
+3. Salidas / Resultado esperado:
+   - WebviewViewProvider funcional con script y estado básico “Hello world”.
+   - Contribuciones declaradas en `package.json` para activity bar y view.
+   - Icono SVG minimalista ubicado en `media/` y referenciado por el contenedor.
+
+4. Restricciones:
+   - Compatibilidad declarada en `engines.vscode` con la versión estable más reciente.
+   - Activación por `onView` y no por `*`.
+   - Icono debe seguir estilo minimalista recomendado para Activity Bar.
+
+5. Criterio de aceptación (Done):
+   - La extensión carga la vista desde activity bar sin errores y el webview muestra el estado básico.
+
+---
+
+## Aprobación (Gate 0)
+Este documento constituye el contrato de la tarea. Su aprobación es bloqueante para pasar a Phase 1.
+
+```yaml
+approval:
+  developer:
+    decision: SI # SI | NO
+    date: 2026-01-30T16:19:16Z
+    comments: null
+```
+
+---
+
+## Historial de validaciones (Phase 0)
+```yaml
+history:
+  - phase: "phase-0-acceptance-criteria"
+    action: "completed"
+    validated_by: "architect-agent"
+    timestamp: "2026-01-30T15:51:57Z"
+    notes: "Acceptance criteria definidos"
+```

package/dist/agent/artifacts/7-extension-vscode-webview/agent-scores.md

@@ -0,0 +1,24 @@
+---
+artifact: agent_scores
+owner: architect-agent
+status: ongoing
+---
+
+# Agent Scores
+
+## 1. Resumen por agente
+- **vscode-specialist**
+  - score: 6
+  - notas: Implementación completa de extensión base.
+- **qa-agent**
+  - score: 6
+  - notas: Verificación manual registrada.
+- **architect-agent**
+  - score: 7
+  - notas: Gestión de gates y trazabilidad.
+
+---
+
+## 2. Meta
+- Ultima actualizacion: 2026-01-30T16:45:36Z
+- Ultima actualizacion: 2026-01-30T16:48:22Z

package/dist/agent/artifacts/7-extension-vscode-webview/agent-tasks/1-vscode-specialist-scaffold-extension.md

@@ -0,0 +1,99 @@
+---
+artifact: agent_task
+phase: phase-4-implementation
+owner: vscode-specialist
+status: completed
+related_task: 7-extension-vscode-webview
+task_number: 1
+---
+
+# Agent Task — 1-vscode-specialist-scaffold-extension
+
+## Identificacion del agente (OBLIGATORIA)
+Primera linea del documento:
+`<icono> **<nombre-agente>**: <mensaje>`
+
+🧩 **vscode-specialist**: Scaffolding de la estructura base de extension.
+
+## Input (REQUIRED)
+- **Objetivo**: Reintroducir carpeta `src/extension` con estructura mínima (extension y views).
+- **Alcance**: Crear archivos base y exports ESM.
+- **Dependencias**: Ninguna.
+
+---
+
+## Reasoning (OBLIGATORIO)
+
+### Análisis del objetivo
+- Crear estructura base de extension siguiendo ESM y separar views.
+
+### Opciones consideradas
+- **Opción A**: Crear `extension.ts` con registro de provider y `views/index.ts` exportando view.
+- **Opción B**: Crear solo `extension.ts` sin folder `views`.
+
+### Decisión tomada
+- Opción elegida: A
+- Justificación: Alineado con acceptance (estructura `views/index.ts`).
+
+---
+
+## Output (REQUIRED)
+- **Entregables**:
+  - `src/extension/extension.ts`
+  - `src/extension/views/index.ts`
+  - `src/extension/views/main-view.ts`
+- **Evidencia requerida**:
+  - Archivos creados y compilación sin errores.
+
+---
+
+## Execution
+
+```yaml
+execution:
+  agent: "vscode-specialist"
+  status: completed
+  started_at: 2026-01-30T16:32:40Z
+  completed_at: 2026-01-30T16:33:35Z
+```
+
+---
+
+## Implementation Report
+
+### Cambios realizados
+- Creado `src/extension/extension.ts` con activación y registro de view.
+- Creado `src/extension/views/main-view.ts` con `MainChatView` y HTML base.
+- Creado `src/extension/views/index.ts` con exports ESM.
+
+### Decisiones técnicas
+- Uso de `WebviewViewProvider` con HTML mínimo y script inline con nonce.
+
+### Evidencia
+- `npm run build` OK (sin errores de TS tras instalar `@types/vscode`).
+
+### Desviaciones del objetivo
+- Ninguna.
+
+---
+
+## Gate (REQUIRED)
+
+```yaml
+approval:
+  developer:
+    decision: SI
+    date: 2026-01-30T16:37:10Z
+    comments: null
+```
+
+---
+
+## Reglas contractuales
+
+1. Esta tarea **NO puede marcarse como completada** sin Gate PASS (`decision: SI`).
+2. Si Gate FAIL (`decision: NO`):
+   - El arquitecto define acciones correctivas.
+   - Se genera una nueva tarea de corrección si procede.
+3. El agente asignado **NO puede modificar** el Input ni el Output definidos por el arquitecto.
+4. El Gate es **síncrono y bloqueante**: el flujo se detiene hasta obtener respuesta del desarrollador.

package/dist/agent/artifacts/7-extension-vscode-webview/agent-tasks/2-vscode-specialist-update-manifest.md

@@ -0,0 +1,101 @@
+---
+artifact: agent_task
+phase: phase-4-implementation
+owner: vscode-specialist
+status: completed
+related_task: 7-extension-vscode-webview
+task_number: 2
+---
+
+# Agent Task — 2-vscode-specialist-update-manifest
+
+## Identificacion del agente (OBLIGATORIA)
+Primera linea del documento:
+`<icono> **<nombre-agente>**: <mensaje>`
+
+🧩 **vscode-specialist**: Actualizacion de manifest para Activity Bar y activation events.
+
+## Input (REQUIRED)
+- **Objetivo**: Configurar `package.json` con contribution points, activation events y engines.
+- **Alcance**: `contributes.viewsContainers`, `contributes.views`, `activationEvents`, `engines.vscode`, `main`.
+- **Dependencias**: Estructura de `src/extension` creada.
+
+---
+
+## Reasoning (OBLIGATORIO)
+
+### Análisis del objetivo
+- El manifest debe declarar el contenedor, la view y la activación onView con IDs coherentes.
+
+### Opciones consideradas
+- **Opción A**: IDs `main` (container) y `mainView` (view) con `onView:mainView`.
+- **Opción B**: Usar IDs más largos y específicos.
+
+### Decisión tomada
+- Opción elegida: A
+- Justificación: Alineado con acceptance y simplicidad.
+
+---
+
+## Output (REQUIRED)
+- **Entregables**:
+  - `package.json` actualizado.
+- **Evidencia requerida**:
+  - `package.json` con `engines.vscode` y `activationEvents` correctos.
+
+---
+
+## Execution
+
+```yaml
+execution:
+  agent: "vscode-specialist"
+  status: completed
+  started_at: 2026-01-30T16:33:40Z
+  completed_at: 2026-01-30T16:34:20Z
+```
+
+---
+
+## Implementation Report
+
+### Cambios realizados
+- `package.json` actualizado con:
+  - `main: ./dist/extension/extension.js`
+  - `engines.vscode: ^1.108.2`
+  - `activationEvents: ["onView:mainView"]`
+  - `contributes.viewsContainers.activitybar` con id `main` y `icon`
+  - `contributes.views.main` con id `mainView`
+  - `files` incluye `dist/extension` y `media`
+
+### Decisiones técnicas
+- Se fijó `^1.108.2` en `engines.vscode` para última estable.
+
+### Evidencia
+- Manifest visible en `package.json`.
+
+### Desviaciones del objetivo
+- Ninguna.
+
+---
+
+## Gate (REQUIRED)
+
+```yaml
+approval:
+  developer:
+    decision: SI
+    date: 2026-01-30T16:37:32Z
+    comments: null
+```
+
+---
+
+## Reglas contractuales
+
+1. Esta tarea **NO puede marcarse como completada** sin Gate PASS (`decision: SI`).
+2. Si Gate FAIL (`decision: NO`):
+   - El arquitecto define acciones correctivas.
+   - Se genera una nueva tarea de corrección si procede.
+3. El agente asignado **NO puede modificar** el Input ni el Output definidos por el arquitecto.
+4. El Gate es **síncrono y bloqueante**: el flujo se detiene hasta obtener respuesta del desarrollador.