@christianmaf80/agentic-workflow 1.41.0-beta.11 → 1.42.0

package/dist/agent/templates/task-metrics.md

@@ -8,31 +8,31 @@ related_task: <taskId>-<taskTitle>
 
 # Task Metrics — <taskId>-<taskTitle>
 
-## Identificacion del agente (OBLIGATORIA)
-Primera linea del documento:
-`<icono> **<nombre-agente>**: <mensaje>`
+## Agent Identification (MANDATORY)
+First line of the document:
+`<icon> **<agent-name>**: <message>`
 
-## 1. Agentes evaluados
+## 1. Evaluated Agents
 - Agent A
 - Agent B
 
 ---
 
-## 2. Puntuacion por agente (0-10)
+## 2. Score per Agent (0-10)
 - **Agent A**: score
-  - Justificacion
+  - Justification
 - **Agent B**: score
-  - Justificacion
+  - Justification
 
 ---
 
-## 3. Puntuacion global de la tarea
-- Promedio ponderado: score
-- Observaciones
+## 3. Overall Task Score
+- Weighted average: score
+- Observations
 
 ---
 
-## 4. Validación del Desarrollador
-- Aprobado: [SI/NO]
-- Puntuación del desarrollador (0-5): 
-- Comentarios: 
+## 4. Developer Validation
+- Approved: [SI/NO]
+- Developer score (0-5): 
+- Comments: 

package/dist/agent/templates/task.md

@@ -7,27 +7,26 @@ strategy: {{task.strategy}}
 
 # Task (Template)
 
-## Identificación
+## Identification
 - id: {{task.id}}
 - title: {{task.title}}
 - scope: candidate | current
 - owner: architect-agent
 
-## Origen
+## Origin
 - created_from:
   - workflow: tasklifecycle
   - source: init / tasklifecycle
   - candidate_path: artifacts.candidate.task
 
-## Descripción de la tarea
+## Task Description
 {{task.description}}
 
-## Objetivo
+## Objective
 {{task.goal}}
 
-## Estado del ciclo de vida (FUENTE ÚNICA DE VERDAD)
+## Lifecycle State (SINGLE SOURCE OF TRUTH)
 
-<!-- RUNTIME:START task-state -->
 ```yaml
 task:
   id: "{{task.id}}"
@@ -39,9 +38,6 @@ task:
     current: "phase-0-acceptance-criteria"
     validated_by: "architect-agent"
     updated_at: "{{timestamp}}"
-  delegation:
-    active_agent: "architect-agent"
-    history: []
   lifecycle:
     phases:
       phase-0-acceptance-criteria:
@@ -97,45 +93,34 @@ task:
             completed: false
             validated_by: null
             validated_at: null
-      short-phase-1-analisis:
+      short-phase-1-brief:
         completed: false
         validated_by: null
         validated_at: null
-      short-phase-2-plan:
+      short-phase-2-implementation:
         completed: false
         validated_by: null
         validated_at: null
-      short-phase-3-implementation:
-        completed: false
-        validated_by: null
-        validated_at: null
-      short-phase-4-qa-results:
+      short-phase-3-closure:
         completed: false
         validated_by: null
         validated_at: null
 ```
-<!-- RUNTIME:END -->
-
----
-
-## Registro de delegación
-- Cualquier cambio de agente **DEBE** registrarse en `task.delegation.history`.
-- La entrada mínima incluye: `from`, `to`, `approved_by`, `approved_at`, `reason`.
 
 ---
 
-## 2. Definición y Alcance (Contrato)
+## 2. Definition and Scope (Contract)
 - **Acceptance Criteria**: [acceptance.md](file:///{{task.acceptance_path}})
 - **Alias**: `task.acceptance`
 
 ---
 
-## Reglas contractuales
-- Este fichero es la **fuente única de verdad** del estado de la tarea.
-- El campo `task.phase.current` **SOLO puede ser modificado por `architect-agent`**.
-- El campo `task.lifecycle.phases.*` **SOLO puede ser marcado como completed por `architect-agent`**.
-- Una fase **NO puede marcarse como completed** si no es la fase actual.
-- El avance de fase requiere:
-  1. Marcar la fase actual como `completed: true`
-  2. Validación explícita del architect
-  3. Actualización de `task.phase.current` a la siguiente fase
+## 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/templates/todo-item.md

@@ -2,44 +2,44 @@
 artifact: todo_item
 owner: architect-agent
 status: open | in-progress | done | cancelled
-priority: alta | media | baja
+priority: high | medium | low
 ---
 
-# TODO: <título breve>
+# TODO: <short title>
 
-## Origen
-- **Detectado en tarea**: <taskId>-<taskTitle>
-- **Fase**: <phase donde se detectó>
-- **Fecha**: <ISO-8601>
-- **Agente**: <agente que lo detectó>
+## Origin
+- **Detected in task**: <taskId>-<taskTitle>
+- **Phase**: <phase where detected>
+- **Date**: <ISO-8601>
+- **Agent**: <agent that detected it>
 
-## Descripción
-<Descripción clara de la mejora propuesta>
+## Description
+<Clear description of the proposed improvement>
 
-## Justificación
-<Por qué es importante hacer este cambio>
+## Justification
+<Why it is important to make this change>
 
-## Impacto estimado
-- **Complejidad**: baja | media | alta
-- **Áreas afectadas**: <componentes/workflows/templates>
+## Estimated Impact
+- **Complexity**: low | medium | high
+- **Affected areas**: <components/workflows/templates>
 
-## Criterio de aceptación
-- [ ] <Condición verificable 1>
-- [ ] <Condición verificable 2>
+## Acceptance Criterion
+- [ ] <Verifiable condition 1>
+- [ ] <Verifiable condition 2>
 
-## Notas
-<Información adicional relevante>
+## Notes
+<Additional relevant information>
 
 ---
 
-## Historial
+## History
 ```yaml
 history:
   - action: created
     date: <ISO-8601>
-    by: <agente>
+    by: <agent>
   # - action: started | completed | cancelled
   #   date: <ISO-8601>
-  #   by: <agente>
-  #   task: <taskId donde se implementó>
+  #   by: <agent>
+  #   task: <taskId where implemented>
 ```

package/dist/agent/workflows/coding/coding-backend.md

@@ -0,0 +1,147 @@
+---
+id: workflow.coding.backend
+description: On-demand coding workflow for the Backend layer. Invoked by architect-agent during Phase 4 implementation.
+owner: backend
+version: 1.0.0
+severity: PERMANENT
+trigger:
+  commands: ["coding-backend"]
+blocking: true
+---
+
+# WORKFLOW: coding.backend
+
+## Input (REQUIRED)
+- Agent task file assigned by architect:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-backend-<taskName>.md`
+- Constitution loaded:
+  - `constitution.backend` (MANDATORY)
+  - `constitution.clean_code` (MANDATORY)
+- Role activated:
+  - `roles.backend`
+
+> [!IMPORTANT]
+> **This is an on-demand workflow.** It is invoked by `architect-agent` during Phase 4 as part of the implementation plan. The architect defines the execution order of coding workflows.
+
+## Output (REQUIRED)
+- Implementation report using `templates.coding.layer_report`:
+  - Embedded in the agent task file under "Implementation Report"
+- All code changes passing compilation
+
+---
+
+## Objective (ONLY)
+- Implement the **backend layer** of the assigned task following `constitution.backend`.
+- Generate a detailed implementation report.
+- Present to developer for Gate approval.
+
+> This workflow **ONLY** implements backend logic.
+> This workflow **NEVER** imports `vscode` or DOM APIs.
+> This workflow **NEVER** communicates directly with View.
+
+---
+
+## Mandatory Steps
+
+### 0. Activate role
+- Activate `roles.backend` and use mandatory agent prefix in all messages.
+
+### 1. Verify inputs
+- Agent task file exists and has Input section completed by architect.
+- Constitution `constitution.backend` loaded.
+- Constitution `constitution.clean_code` loaded.
+- If missing → **FAIL**.
+
+### 2. Analyze the task
+- Read the agent task Input (objective, scope, dependencies).
+- Complete the "Reasoning" section of the agent task:
+  - Analyze objective
+  - Consider options
+  - Document decision and justification
+
+### 3. Implement
+- Write code following `constitution.backend`:
+  - **Extend AbstractServer** from `core/backend`.
+  - **No vscode imports** — logic must be IDE-decoupled.
+  - **Transport agnostic** — use abstract adapters.
+  - **Error handling** — return `{ error, code }`, no raw exceptions.
+  - **Response format** — strictly typed JSON.
+- Write code following `constitution.clean_code`.
+
+### 4. Self-validate
+- Verify all constitution rules are satisfied:
+  - [ ] Extends `AbstractServer` (if applicable)
+  - [ ] No `vscode` or `dom` imports
+  - [ ] Error handling via structured responses
+  - [ ] No direct View communication
+  - [ ] Clean code principles applied
+- Run compilation: `npm run compile`
+- If compilation fails → fix before proceeding.
+
+### 5. Generate implementation report
+- Complete the "Implementation Report" section using `templates.coding.layer_report`:
+  - **Who**: Agent identity and role
+  - **How**: Technical details, specifications, diagrams if needed
+  - **Why**: Justification and reasoning
+  - **Results**: What was achieved, compilation status
+  - **E2E Test Indications**: Scenarios for e2e testing
+
+### 6. Present to developer (Gate)
+- Present completed task with report to developer.
+- Request approval: **SI / NO**
+
+### 7. Register Gate
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+### 8. Evaluate Gate
+- If `decision == SI` → go to **Step 9 (PASS)**.
+- If `decision == NO`:
+  - Mark task as `failed`.
+  - Define corrective actions.
+  - **Do NOT advance** until resolved.
+  - Go to **Step 10 (FAIL)**.
+
+### 9. PASS (only if Gate approved)
+- Mark agent task as `completed`.
+- Update agent task file:
+  ```yaml
+  execution:
+    status: completed
+    completed_at: <ISO-8601>
+  ```
+- Update the coding layer report with final status.
+- Return control to `architect-agent` for next workflow in the sequence.
+
+---
+
+## FAIL (MANDATORY)
+
+### 10. Declare workflow as NOT completed
+Cases:
+- Missing inputs or constitution.
+- Compilation failure not resolved.
+- Constitution violation detected.
+- Gate = NO without resolution.
+
+Actions:
+- Identify the failure point.
+- Define corrective actions.
+- Iterate until Gate PASS.
+
+---
+
+## Gate (REQUIRED)
+
+Requirements (all mandatory):
+1. Code compiles without errors.
+2. All `constitution.backend` rules are satisfied.
+3. All `constitution.clean_code` rules are satisfied.
+4. Implementation report is complete (all 5 sections).
+5. Developer Gate PASS (`decision == SI`).
+6. Agent task file starts with backend agent prefix.

package/dist/agent/workflows/coding/coding-background.md

@@ -0,0 +1,149 @@
+---
+id: workflow.coding.background
+description: On-demand coding workflow for the Background/Orchestration layer. Invoked by architect-agent during Phase 4 implementation.
+owner: background
+version: 1.0.0
+severity: PERMANENT
+trigger:
+  commands: ["coding-background"]
+blocking: true
+---
+
+# WORKFLOW: coding.background
+
+## Input (REQUIRED)
+- Agent task file assigned by architect:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-background-<taskName>.md`
+- Constitution loaded:
+  - `constitution.background` (MANDATORY)
+  - `constitution.clean_code` (MANDATORY)
+- Role activated:
+  - `roles.background`
+
+> [!IMPORTANT]
+> **This is an on-demand workflow.** It is invoked by `architect-agent` during Phase 4 as part of the implementation plan. The architect defines the execution order of coding workflows.
+
+## Output (REQUIRED)
+- Implementation report using `templates.coding.layer_report`:
+  - Embedded in the agent task file under "Implementation Report"
+- All code changes passing compilation
+
+---
+
+## Objective (ONLY)
+- Implement the **background/orchestration layer** of the assigned task following `constitution.background`.
+- Generate a detailed implementation report.
+- Present to developer for Gate approval.
+
+> This workflow **ONLY** implements orchestration logic.
+> This workflow is the **ONLY** layer authorized to import `vscode`.
+> This workflow manages the **Backend ↔ View bridge** via Messaging.
+
+---
+
+## Mandatory Steps
+
+### 0. Activate role
+- Activate `roles.background` and use mandatory agent prefix in all messages.
+
+### 1. Verify inputs
+- Agent task file exists and has Input section completed by architect.
+- Constitution `constitution.background` loaded.
+- Constitution `constitution.clean_code` loaded.
+- If missing → **FAIL**.
+
+### 2. Analyze the task
+- Read the agent task Input (objective, scope, dependencies).
+- Complete the "Reasoning" section of the agent task:
+  - Analyze objective
+  - Consider options
+  - Document decision and justification
+
+### 3. Implement
+- Write code following `constitution.background`:
+  - **Orchestration**: Manage flow between VS Code, Backend, and View.
+  - **Registration**: All modules register via `App.register(id, provider)`.
+  - **Messaging**: Use `core/messaging` for View communication (MANDATORY).
+  - **Type safety**: Use shared `Message` interface from `core/types`.
+  - **Lifecycle**: Respect VS Code activation/deactivation.
+  - **Dependency injection**: Inject services into providers.
+- Write code following `constitution.clean_code`.
+
+### 4. Self-validate
+- Verify all constitution rules are satisfied:
+  - [ ] Modules registered via `App.register()`
+  - [ ] View communication via `core/messaging` only
+  - [ ] Typed `Message` payloads
+  - [ ] VS Code lifecycle respected
+  - [ ] Gateway role: only layer with `vscode` side-effects
+  - [ ] Clean code principles applied
+- Run compilation: `npm run compile`
+- If compilation fails → fix before proceeding.
+
+### 5. Generate implementation report
+- Complete the "Implementation Report" section using `templates.coding.layer_report`:
+  - **Who**: Agent identity and role
+  - **How**: Technical details, specifications, diagrams if needed
+  - **Why**: Justification and reasoning
+  - **Results**: What was achieved, compilation status
+  - **E2E Test Indications**: Scenarios for e2e testing
+
+### 6. Present to developer (Gate)
+- Present completed task with report to developer.
+- Request approval: **SI / NO**
+
+### 7. Register Gate
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+### 8. Evaluate Gate
+- If `decision == SI` → go to **Step 9 (PASS)**.
+- If `decision == NO`:
+  - Mark task as `failed`.
+  - Define corrective actions.
+  - **Do NOT advance** until resolved.
+  - Go to **Step 10 (FAIL)**.
+
+### 9. PASS (only if Gate approved)
+- Mark agent task as `completed`.
+- Update agent task file:
+  ```yaml
+  execution:
+    status: completed
+    completed_at: <ISO-8601>
+  ```
+- Update the coding layer report with final status.
+- Return control to `architect-agent` for next workflow in the sequence.
+
+---
+
+## FAIL (MANDATORY)
+
+### 10. Declare workflow as NOT completed
+Cases:
+- Missing inputs or constitution.
+- Compilation failure not resolved.
+- Constitution violation detected.
+- Gate = NO without resolution.
+
+Actions:
+- Identify the failure point.
+- Define corrective actions.
+- Iterate until Gate PASS.
+
+---
+
+## Gate (REQUIRED)
+
+Requirements (all mandatory):
+1. Code compiles without errors.
+2. All `constitution.background` rules are satisfied.
+3. All `constitution.clean_code` rules are satisfied.
+4. Implementation report is complete (all 5 sections).
+5. Developer Gate PASS (`decision == SI`).
+6. Agent task file starts with background agent prefix.

package/dist/agent/workflows/coding/coding-integration.md

@@ -0,0 +1,174 @@
+---
+id: workflow.coding.integration
+description: On-demand coding workflow for integrating the 3 layers of a module (Backend, Background, View). Invoked by architect-agent during Phase 4 after layer-specific workflows.
+owner: architect-agent
+version: 1.0.0
+severity: PERMANENT
+trigger:
+  commands: ["coding-integration"]
+blocking: true
+---
+
+# WORKFLOW: coding.integration
+
+## Input (REQUIRED)
+- Agent task file assigned by architect:
+  - `.agent/artifacts/<taskId>-<taskTitle>/agent-tasks/<N>-architect-integration-<taskName>.md`
+- All applicable layer coding workflows completed and approved:
+  - `coding-backend` report (if applicable)
+  - `coding-background` report (if applicable)
+  - `coding-view` report (if applicable)
+- Constitutions loaded (ALL):
+  - `constitution.backend` (MANDATORY)
+  - `constitution.background` (MANDATORY)
+  - `constitution.view` (MANDATORY)
+  - `constitution.clean_code` (MANDATORY)
+
+> [!IMPORTANT]
+> **This workflow runs AFTER all layer-specific coding workflows.** It validates that the 3 layers communicate correctly and comply with all constitutions. The architect is the owner.
+
+## Output (REQUIRED)
+- Integration report using `templates.coding.integration_report`:
+  - Embedded in the agent task file under "Implementation Report"
+- All layers passing compilation and integration validation
+
+---
+
+## Objective (ONLY)
+- Validate and ensure **optimal communication** between the 3 layers of the module.
+- Verify **constitution compliance** across all layers.
+- Generate a detailed **integration report**.
+- Present to developer for Gate approval.
+
+> This workflow validates **inter-layer contracts**.
+> This workflow ensures **no constitution violations** exist across boundaries.
+> This workflow is the **final validation** before Phase 4 closure.
+
+---
+
+## Mandatory Steps
+
+### 0. Activate role
+- Activate `architect-agent` and use mandatory prefix in all messages.
+
+### 1. Verify inputs
+- All applicable layer coding workflows have Gate PASS.
+- All layer reports exist and are complete.
+- All 4 constitutions loaded.
+- If missing → **FAIL**.
+
+### 2. Review layer reports
+- Read each layer's implementation report.
+- Identify:
+  - Communication touchpoints between layers.
+  - Shared contracts (Message types, API interfaces).
+  - Potential constitution violations at boundaries.
+
+### 3. Validate communication paths
+- **View → Background**: Via `core/messaging` Event Bus only.
+  - [ ] No direct `vscode.postMessage` from View.
+  - [ ] Typed `Message` payloads.
+- **Background → Backend**: Via abstract transport or direct invocation.
+  - [ ] No `vscode` leaking into Backend.
+  - [ ] Structured error responses from Backend.
+- **Background → View**: Via `core/messaging` response path.
+  - [ ] Reactive UI updates on state change.
+- **View → Backend**: FORBIDDEN.
+  - [ ] No direct imports or calls between View and Backend.
+
+### 4. Validate constitution compliance
+For each constitution, verify cross-layer boundaries:
+
+#### Backend (`constitution.backend`)
+- [ ] Extends `AbstractServer` (if applicable)
+- [ ] No `vscode` or `dom` imports
+- [ ] Transport agnostic
+- [ ] No direct View communication
+
+#### Background (`constitution.background`)
+- [ ] Modules registered via `App.register()`
+- [ ] Uses `core/messaging` for View communication
+- [ ] Manages lifecycle correctly
+- [ ] Gateway role maintained (only layer with `vscode` side-effects)
+
+#### View (`constitution.view`)
+- [ ] Lit components with `@customElement`
+- [ ] Triad structure (index/html/styles)
+- [ ] No business logic
+- [ ] Communication via Messaging wrapper only
+
+### 5. Integration validation
+- Run full compilation: `npm run compile`
+- Verify no type errors at layer boundaries.
+- If issues found → create corrective sub-task.
+
+### 6. Generate integration report
+- Complete the "Implementation Report" section using `templates.coding.integration_report`:
+  - **Communication validation matrix**: Results of Step 3
+  - **Constitution compliance**: Results of Step 4
+  - **Cross-layer sequence diagrams**: Key interaction flows (mermaid)
+  - **E2E Test Indications**: Integration test scenarios
+  - **Issues found and resolutions**: If any
+
+### 7. Present to developer (Gate)
+- Present integration report with all evidence to developer.
+- Request approval: **SI / NO**
+
+### 8. Register Gate
+```yaml
+approval:
+  developer:
+    decision: SI | NO
+    date: <ISO-8601>
+    comments: <optional>
+```
+
+### 9. Evaluate Gate
+- If `decision == SI` → go to **Step 10 (PASS)**.
+- If `decision == NO`:
+  - Identify failing layer(s).
+  - Create corrective sub-task for specific layer workflow.
+  - Re-run integration after correction.
+  - Go to **Step 11 (FAIL)**.
+
+### 10. PASS (only if Gate approved)
+- Mark integration task as `completed`.
+- Update agent task file:
+  ```yaml
+  execution:
+    status: completed
+    completed_at: <ISO-8601>
+  ```
+- Update the integration report with final assessment: `PASS`.
+- Return control to `architect-agent` for **Phase 4 closure** (Gate final de Phase 4).
+
+---
+
+## FAIL (MANDATORY)
+
+### 10. Declare workflow as NOT completed
+Cases:
+- Layer workflows not completed or not approved.
+- Constitution violation at layer boundaries.
+- Compilation failure.
+- Direct View→Backend communication detected.
+- Gate = NO without resolution.
+
+Actions:
+- Identify the exact layer and violation.
+- Delegate corrective action to the appropriate layer workflow.
+- Re-run integration validation after fix.
+- Iterate until Gate PASS.
+
+---
+
+## Gate (REQUIRED)
+
+Requirements (all mandatory):
+1. All layer coding workflows have Gate PASS.
+2. All communication paths validated (Step 3 checklist).
+3. All constitutions satisfied at cross-layer boundaries (Step 4 checklist).
+4. Full compilation passes without errors.
+5. Integration report is complete (all sections).
+6. Developer Gate PASS (`decision == SI`).
+7. No direct View→Backend communication exists.