siesa-agents 2.1.44 → 2.1.46-alpha.4

package/README.md

@@ -11,15 +11,20 @@ Paquete para instalar y configurar el ecosistema **BMAD v6** con los agentes esp
 Esta versión está diseñada y optimizada para el siguiente stack tecnológico empresarial:
 
 **Frontend:**
-- Next.js 16 con TypeScript (App Router)
+- Vite 7+ como bundler (builds rápidos, HMR instantáneo)
+- TanStack Router 1+ (file-based routing, type-safe)
+- React 18+ con TypeScript (strict mode)
+- TanStack Query 5+ para server state
+- Zustand 5+ para client state
 - Shadcn/ui + Radix UI + TailwindCSS v4
-- Zustand para state management
 - React Hook Form + Zod para formularios
+- Vitest para testing
+- Preparado para microfrontends con Module Federation
 
 **Backend:**
 - .NET 10 con C# Minimal API
 - Entity Framework Core 10 + linq2db + LinqKit
-- PostgreSQL como base de datos primaria
+- PostgreSQL 18+ como base de datos primaria
 - Arquitectura de Microservicios
 
 **Principios Arquitectónicos:**
@@ -27,25 +32,6 @@ Esta versión está diseñada y optimizada para el siguiente stack tecnológico
 - Test-Driven Development (TDD)
 - Database per Microservice
 
-## Sistema de Publicación Automática
-
-Este proyecto cuenta con un sistema de CI/CD automatizado que maneja las publicaciones de manera inteligente:
-
-### Versiones Estables (`latest`)
-- **Rama**: `npm-package`
-- **Propósito**: Versiones oficiales para producción
-- **Funcionamiento**: Cada commit en esta rama incrementa automáticamente la versión y la publica en npm
-
-### Versiones de Desarrollo (`dev`)
-- **Rama**: `developer`
-- **Propósito**: Versiones de prueba y desarrollo
-- **Funcionamiento**: Incrementa automáticamente el contador de desarrollo
-
-### Flujo de Trabajo
-1. **Desarrollo**: Trabaja en la rama `developer` para cambios experimentales
-2. **Estable**: Mueve cambios finalizados a `npm-package` para versiones oficiales
-3. **Automático**: El sistema maneja todo el versionado sin intervención manual
-
 ## Instalación
 
 ### Instalación única con npx (Recomendado)
@@ -105,8 +91,8 @@ El sistema detectará automáticamente que ya existe una instalación y la actua
 
 ## Requisitos
 
-- Node.js >= 14.0.0
-- npm >= 6.0.0
+- Node.js >= 20.0.0
+- npm >= 8.0.0 (o pnpm >= 8.0.0 recomendado)
 - Python >= 3.7 (requerido para hooks de Claude Code)
 
 ## Estructura de archivos instalados

package/bmad/_config/workflow-manifest.csv

@@ -17,7 +17,7 @@ name,description,module,path
 "code-review","Perform an ADVERSARIAL Senior Developer code review that finds 3-10 specific problems in every story. Challenges everything: code quality, test coverage, architecture compliance, security, performance. NEVER accepts `looks good` - must find minimum issues and can auto-fix with user approval.","bmm","_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
 "correct-course","Navigate significant changes during sprint execution by analyzing impact, proposing solutions, and routing for implementation","bmm","_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
 "create-story","Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking","bmm","_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
+"dev-story","Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria","bmm","_bmad/bmm/workflows/4-implementation/dev-story/workflow.md"
 "retrospective","Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic","bmm","_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
 "sprint-planning","Generate and manage the sprint status tracking file for Phase 4 implementation, extracting all epics and stories from epic files and tracking their status through the development lifecycle","bmm","_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
 "sprint-status","Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow.","bmm","_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml"
@@ -43,3 +43,4 @@ name,description,module,path
 "innovation-strategy","Identify disruption opportunities and architect business model innovation. This workflow guides strategic analysis of markets, competitive dynamics, and business model innovation to uncover sustainable competitive advantages and breakthrough opportunities.","cis","_bmad/cis/workflows/innovation-strategy/workflow.yaml"
 "problem-solving","Apply systematic problem-solving methodologies to crack complex challenges. This workflow guides through problem diagnosis, root cause analysis, creative solution generation, evaluation, and implementation planning using proven frameworks.","cis","_bmad/cis/workflows/problem-solving/workflow.yaml"
 "storytelling","Craft compelling narratives using proven story frameworks and techniques. This workflow guides users through structured narrative development, applying appropriate story frameworks to create emotionally resonant and engaging stories for any purpose.","cis","_bmad/cis/workflows/storytelling/workflow.yaml"
+"sync-epics-stories","Synchronize Bmad generated epics and stories documentation with Jira","bmm","_bmad/bmm/workflows/sync-epics-stories/workflow.md"

package/bmad/bmm/agents/dev.md

@@ -61,7 +61,7 @@ You must fully embody this agent's persona and follow all activation instruction
   <menu>
     <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
     <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
-    <item cmd="DS or fuzzy match on dev-story" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml">[DS] Execute Dev Story workflow (full BMM path with sprint-status)</item>
+    <item cmd="DS or fuzzy match on dev-story" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.md">[DS] Execute Dev Story workflow (full BMM path with sprint-status)</item>
     <item cmd="CR or fuzzy match on code-review" workflow="{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml">[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)</item>
     <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
     <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>

package/bmad/bmm/data/git-flow-siesa.md

@@ -0,0 +1,50 @@
+# Protocolo de Git: Creación de Ramas y Commits - SiesaTeams
+
+Este documento establece el flujo obligatorio para la creación de ramas y el estándar de mensajes de commit para asegurar el cumplimiento de la gobernanza.
+
+---
+
+## 1. Validación de Rama Padre (Feature)
+Para cualquier desarrollo de funcionalidad (**feature**), la rama de origen debe ser estrictamente `develop`.
+
+**Procedimiento del Agente:**
+1. Validar que se encuentra en: `develop`.
+2. Ejecutar: `git checkout develop && git pull origin develop`.
+3. Confirmar que no hay cambios pendientes antes de ramificar.
+
+---
+
+## 2. Nomenclatura de la Rama
+La estructura del nombre debe seguir el formato:
+`rama-padre-team-owner-rq-descripcion`.
+
+**Parámetros Sugeridos:**
+* **Rama Padre:** `develop`.
+* **Team:** (Debe coincidir con un prefijo válido, ej: `legacy-erp-nomina`).
+* **Owner:** `gaduranb` (Basado en el correo corporativo gaduranb@siesa.com).
+* **RQ:** Número de requerimiento asignado.
+* **Descripción:** Breve, en minúsculas y con guiones.
+
+**Ejemplo de comando:**
+`git checkout -b develop-legacy-erp-nomina-gaduranb-rq1234-nueva-interfaz`.
+
+---
+
+## 3. Estándar de Mensajes de Commit
+Se adopta el formato de **Conventional Commits** para mejorar la legibilidad y automatización.
+
+| Tipo | Formato del Mensaje | Uso |
+| :--- | :--- | :--- |
+| **Feature** | `feat: descripción clara del cambio` | Nuevas funcionalidades. |
+| **Fix** | `fix: descripción del error corregido` | Corrección de errores (bugs). |
+
+**Ejemplos:**
+* `git commit -m "feat: implementar validación de identidad mediante SSO"`.
+* `git commit -m "fix: corregir cálculo de nómina en rama legacy"`.
+
+---
+
+## 4. Reglas de Oro de Gobernanza
+* **Todo en Minúsculas:** Los nombres de ramas y repositorios no deben contener mayúsculas.
+* **Protección de Ramas:** `main` y `develop` están protegidas; el push directo está prohibido.
+* **Nota:** Esta automatización solo podrá crear las ramas como se indica y realizar push a las mismas en caso de ser necesario.

package/bmad/bmm/workflows/2-plan-workflows/create-ux-design/steps/step-11-component-strategy.md

@@ -109,7 +109,13 @@ Define component library strategy and design custom components not covered by th
 - `{company_standards_path}/frontend-standards.md`
 - Check if siesa-ui-kit documentation exists in project
 
-"Before we analyze components, let me load the company standards and siesa-ui-kit to ensure we follow Siesa's component guidelines."
+🔴 **MANDATORY - Load siesa-ui-kit Component Inventory:**
+- Fetch the component catalog from: `https://siesa-ui-kit.pages.dev/llms.txt`
+- This file contains the complete, up-to-date list of all available siesa-ui-kit components with their descriptions, variants, and capabilities
+- Parse and use this inventory as the **authoritative source** for determining which components are available in siesa-ui-kit
+- If the URL is unreachable, warn the user: "⚠️ No se pudo acceder al catálogo de siesa-ui-kit en llms.txt. Por favor verificar conectividad o proporcionar la lista de componentes manualmente."
+
+"Before we analyze components, let me load the company standards and the **siesa-ui-kit component catalog** to ensure we follow Siesa's component guidelines and use all available components."
 
 ### 2. Analyze Component Coverage (siesa-ui-kit FIRST)
 

package/bmad/bmm/workflows/3-solutioning/create-architecture/data/company-standards/architecture-patterns.md

@@ -7,26 +7,34 @@
 
 ### Folder Structure
 
-Next.js 16 App Router Structure with Clean Architecture + DDD:
+Vite + TanStack Router Structure with Clean Architecture + DDD:
 
 ```
-├── app/                         # Next.js App Router directory
-│   ├── (dashboard)/            # Route groups for dashboard
-│   ├── sales/                  # Routes for sales module
-│   │   ├── quotes/             # Quote management pages
-│   │   └── invoices/           # Invoice pages
-│   ├── inventory/              # Inventory routes
-│   ├── globals.css             # Global styles
-│   ├── layout.tsx              # Root layout component
-│   ├── page.tsx               # Home page
-│   ├── loading.tsx            # Global loading UI
-│   └── not-found.tsx          # 404 page
-│
 ├── src/
-│   ├── modules/                # Business modules following DDD
-│   │   ├── sales/              # Sales module
-│   │   │   ├── quotes/         # Quote domain
-│   │   │   │   ├── cart/       # Shopping cart feature
+│   ├── main.tsx                     # React entry point
+│   ├── router.tsx                   # TanStack Router config
+│   ├── routeTree.gen.ts             # Auto-generated (DO NOT EDIT)
+│   ├── globals.css                  # Global styles + Tailwind
+│   │
+│   ├── routes/                      # TanStack Router file-based routing
+│   │   ├── __root.tsx               # Root layout (providers)
+│   │   ├── index.tsx                # Home redirect
+│   │   ├── _auth.tsx                # Public layout (pathless)
+│   │   ├── _auth/
+│   │   │   └── login.tsx            # /login
+│   │   ├── _app.tsx                 # Protected layout (pathless)
+│   │   └── _app/
+│   │       ├── dashboard.tsx        # /dashboard
+│   │       ├── sales/
+│   │       │   ├── quotes.tsx       # /sales/quotes
+│   │       │   └── invoices.tsx     # /sales/invoices
+│   │       └── inventory/
+│   │           └── products.tsx     # /inventory/products
+│   │
+│   ├── modules/                     # Business modules following DDD
+│   │   ├── sales/                   # Sales module
+│   │   │   ├── quotes/              # Quote domain
+│   │   │   │   ├── cart/            # Shopping cart feature
 │   │   │   │   │   ├── domain/
 │   │   │   │   │   │   ├── entities/
 │   │   │   │   │   │   ├── repositories/
@@ -41,29 +49,43 @@ Next.js 16 App Router Structure with Clean Architecture + DDD:
 │   │   │   │   │   │   ├── api/
 │   │   │   │   │   │   └── adapters/
 │   │   │   │   │   └── presentation/
-│   │   │   │   │       └── components/    # Only components, pages in app/
-│   │   │   │   └── products/              # Products feature
-│   │   │   └── billing/                   # Billing domain
-│   │   ├── inventory/                     # Inventory module
-│   │   └── users/                         # User module
+│   │   │   │   │       └── components/
+│   │   │   │   └── products/        # Products feature
+│   │   │   └── billing/             # Billing domain
+│   │   ├── inventory/               # Inventory module
+│   │   └── users/                   # User module
 │   │
 │   ├── shared/
-│   │   ├── components/         # Reusable UI components
-│   │   ├── hooks/              # Shared hooks
-│   │   ├── utils/              # Utility functions
-│   │   ├── types/              # Common TypeScript types
-│   │   └── constants/          # App constants
+│   │   ├── components/              # Reusable UI components
+│   │   │   └── ui/                  # shadcn/ui components
+│   │   ├── hooks/                   # Shared hooks
+│   │   ├── lib/                     # Utilities (utils.ts, api-client.ts)
+│   │   ├── types/                   # Common TypeScript types
+│   │   └── constants/               # App constants
 │   │
-│   ├── providers/              # React context providers
-│   ├── store/                  # Global Zustand stores
-│   └── middleware.ts           # Next.js middleware
+│   ├── app/                         # Global configuration
+│   │   ├── providers/               # React context providers
+│   │   └── store/                   # Global Zustand stores
+│   │
+│   └── infrastructure/              # Global external services
+│       ├── api/                     # API configuration
+│       ├── storage/                 # IndexedDB, localStorage
+│       └── pwa/                     # PWA configuration
 │
-├── lib/                        # Next.js utilities and configurations
-├── components/                 # Global UI components (alternative to src/shared)
-├── public/                     # Static assets and PWA manifest
-└── styles/                     # Additional stylesheets
+├── public/                          # Static assets and PWA manifest
+├── index.html                       # Vite entry point
+└── vite.config.ts                   # Vite + TanStack Router plugin config
 ```
 
+### TanStack Router Conventions
+
+| Prefix | Effect | Example |
+|--------|--------|---------|
+| `_` | Pathless layout (no URL segment) | `_app.tsx` → layout only |
+| `.` | Flat routing (nested without folders) | `orders.$id.tsx` → `/orders/:id` |
+| `-` | Ignored by router (colocated files) | `-components/` |
+| `$` | Dynamic parameter | `$orderId.tsx` → `:orderId` |
+
 ### Core Principles
 
 #### Clean Architecture First
@@ -71,7 +93,7 @@ Strict separation of:
 - **Domain layer** - Business entities, repositories interfaces, domain services, and types
 - **Application layer** - Use cases, hooks, and state management (Zustand stores)
 - **Infrastructure layer** - Repository implementations, API clients, and adapters
-- **Presentation layer** - UI components (pages go in `app/`, components in `presentation/`)
+- **Presentation layer** - UI components in `presentation/`, routes in `routes/`
 
 #### Domain-Driven Design
 Business logic drives architecture decisions. Organize by business modules and domains, not technical layers.
@@ -83,7 +105,7 @@ Build complex UIs from simple, reusable components.
 Leverage TypeScript for compile-time safety and developer experience.
 
 #### Performance by Design
-- Lazy loading
+- Lazy loading (automatic with TanStack Router)
 - Memoization
 - Bundle optimization
 
@@ -107,11 +129,16 @@ Use MCP to install Shadcn components instead of creating manually.
 
 ### Framework Selection Rules
 
-**Default**: Always use Next.js 16 with App Router unless explicitly told otherwise.
+**Default**: Always use Vite + TanStack Router with TypeScript.
 
-**Exceptions**: Only use pure React + Vite when user specifically mentions offline-first functionality or requests non-Next.js setup.
+**Microfrontends**:
+- **DEFAULT**: Vite + Single-SPA (`vite-plugin-single-spa` + `single-spa-react`) para todos los módulos de negocio
+- **EXCEPCIÓN**: Vite + Module Federation SOLO para módulos transversales/compartidos explícitamente marcados por el ingeniero
 
-**Reasoning**: Next.js provides better developer experience, built-in optimization, and easier deployment while maintaining PWA capabilities.
+**Reasoning**:
+- Single-SPA proporciona aislamiento completo (CSS, JS, lifecycle), mejor hot reload, y error boundaries built-in
+- Module Federation solo se usa cuando hay necesidad explícita de compartir código entre MFEs
+- Ver `vite-config-standard.md` para configuración detallada
 
 ## Backend Architecture
 
@@ -388,9 +415,11 @@ app.MapScalarApiReference();  // NOT app.UseSwagger()
 ## Summary
 
 ### Frontend
-- **Framework**: Next.js 16 with TypeScript and App Router
+- **Bundler**: Vite 5+
+- **Router**: TanStack Router (file-based, type-safe)
+- **Framework**: React 18+ with TypeScript (strict mode)
 - **Architecture**: Clean Architecture + DDD
-- **State**: Zustand
+- **State**: Zustand (client) + TanStack Query (server)
 - **UI**: shadcn/ui + Radix UI + TailwindCSS v4
 - **Testing**: Vitest + React Testing Library
 - **Validation**: Zod + React Hook Form
@@ -412,4 +441,4 @@ app.MapScalarApiReference();  // NOT app.UseSwagger()
 3. **Test-Driven Development** - Tests before/alongside implementation
 4. **Database per Microservice** - Complete isolation between services
 5. **Type Safety** - TypeScript (frontend) and C# (backend) strong typing
-6. **Docker for Production** - Local development without containers
+6. **Docker for Production** - Local development without containers