siesa-agents 2.1.25 → 2.1.26-dev.1

package/bmad-core/data/bmad-kb.md

@@ -181,7 +181,7 @@ npx bmad-method install
 
 ## Core Configuration (core-config.yaml)
 
-**New in V4**: The `bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
+**New in V4**: The `.bmad-core/core-config.yaml` file is a critical innovation that enables BMad to work seamlessly with any project structure, providing maximum flexibility and backwards compatibility.
 
 ### What is core-config.yaml?
 

package/bmad-core/data/frontend-standards.md

@@ -23,7 +23,7 @@
 - **Shadcn/ui + Radix UI**: Component library foundation
 
 ### Framework Selection Rules
-- **Default**: Always use Next.js 14+ with App Router
+- **Default**: Always use Next.js 16+ with App Router
 - **Exception**: Only use pure React + Vite when user specifically requests offline-first functionality
 - **Reasoning**: Next.js provides better DX, built-in optimization, and easier deployment while maintaining PWA capabilities
 

package/bmad-core/data/technical-preferences-ux.md

@@ -4,7 +4,7 @@
 Based on Frontend Development Standards and Clean Architecture Implementation
 
 ### Technology Stack
-- **Framework**: Next.js 14+ with App Router
+- **Framework**: Next.js 16+ with App Router
 - **Language**: TypeScript (strict mode)
 - **Styling**: TailwindCSS + Shadcn/ui + Radix UI
 - **State Management**: Zustand

package/bmad-core/data/technical-preferences.md

@@ -2,4 +2,109 @@
 
 # User-Defined Preferred Patterns and Preferences
 
-None Listed
+## Backend Preferences (.NET 10)
+
+### Framework & Language
+- **MANDATORY**: .NET 10 with C# Minimal API
+- **API Style**: Minimal API (lightweight, modern approach)
+- **NO** MVC Controllers - Use Minimal API endpoints only
+
+### Database
+- **MANDATORY**: PostgreSQL for all microservices
+- **ORM**: Entity Framework Core 10 (primary - matches .NET 10 version)
+- **LINQ Extensions**: linq2db, DynamicLinq, LinqKit for advanced queries
+- **Primary Keys**: UUID (Guid) for ALL entities - NO exceptions
+- **Migrations**: EF Core 10 Migrations for schema version control
+- **DateTime Types**: 
+  - **MANDATORY**: Use `DateTimeOffset` for ALL timestamp fields (CreatedAt, UpdatedAt, etc.)
+  - **FORBIDDEN**: NEVER use `DateTime` for timestamp fields in entities or DTOs
+  - **Rationale**: PostgreSQL uses TIMESTAMP WITH TIME ZONE which maps to DateTimeOffset
+  - **Date Only**: Use `DateOnly` for date-only fields (BirthDate, ExpenseDate)
+  - **Time Only**: Use `TimeOnly` for time-only fields (OpeningTime, ClosingTime)
+
+### Validation
+- **MANDATORY**: FluentValidation for all DTOs and commands
+
+### API Documentation
+- **MANDATORY**: Scalar for API documentation
+- **FORBIDDEN**: Do NOT use Swagger/Swashbuckle
+
+### Architecture
+- **Pattern**: Clean Architecture + DDD
+- **Microservices**: Each service with independent PostgreSQL database
+- **No Shared Databases**: Services communicate via APIs or events
+- **CQRS**: Command/Query separation in Application layer
+
+### Testing
+- **Framework**: xUnit (MANDATORY)
+- **TDD**: Test-Driven Development approach required
+- **Unit Tests**: EF Core InMemory for fast tests
+- **Integration Tests**: PostgreSQL Test Containers for real scenarios
+- **Coverage**: Aim for >80% code coverage
+
+### PDF Generation
+- **Library**: QuestPDF for document generation
+- **Testing**: Snapshot/output validation for PDF tests
+
+### Code Quality
+- **Analyzers**: Enable .NET code analyzers
+- **Format**: Use `dotnet format` for code style
+- **EditorConfig**: Enforce coding standards
+
+### Localization
+- **i18n/l10n**: Built-in .NET localization support
+- **Resources**: Use .resx files for translations
+
+### Development Environment
+- **Local Development**: Direct execution with `dotnet run`
+- **PostgreSQL Local**: Use local PostgreSQL instance or cloud dev DB
+
+### Production Deployment
+- **Containerization**: Docker for production deployments
+- **Orchestration**: Kubernetes or Docker Compose
+- **Each Service**: Independent container with health checks
+
+## Frontend Preferences (Next.js 16)
+
+### Framework
+- **Default**: Next.js 16 with TypeScript and App Router
+- **Exception**: Pure React + Vite only for offline-first scenarios
+
+### State Management
+- **Zustand**: Preferred for global state
+
+### UI Components
+- **shadcn/ui**: Component library
+- **Radix UI**: Primitives
+- **TailwindCSS v4**: Styling
+
+### Testing
+- **Vitest**: Test runner
+- **React Testing Library**: Component testing
+- **MSW**: API mocking
+
+### Validation
+- **Zod**: Schema validation
+- **React Hook Form**: Form management
+
+## Cross-Stack Preferences
+
+### Communication
+- **REST API**: Primary communication protocol
+- **gRPC**: For high-performance inter-service calls
+- **Message Broker**: RabbitMQ or Azure Service Bus for async events
+
+### Security
+- **Authentication**: JWT tokens
+- **Authorization**: Role-based access control
+- **HTTPS**: Mandatory for all environments
+
+### Logging & Monitoring
+- **Structured Logging**: Use ILogger in .NET
+- **Correlation IDs**: Track requests across services
+- **Health Checks**: Implement health endpoints for all services
+
+### Error Handling
+- **Problem Details**: RFC 7807 for error responses
+- **Global Exception Handler**: Middleware for centralized error handling
+- **Validation Errors**: Return 400 with detailed validation messages

package/bmad-core/data/technology-stack.md

@@ -3,7 +3,7 @@
 ## Frontend Stack
 
 ### Framework
-- **Next.js 15** with TypeScript (App Router)
+- **Next.js 16** with TypeScript (App Router)
   - Default framework unless explicitly told otherwise
   - Built-in Turbopack/Webpack for building
   - File-based routing with App Router
@@ -79,3 +79,157 @@ Start with user needs and work backward to implementation
 
 ### MCP Shadcn Available
 Use MCP to install Shadcn components instead of creating manually
+
+## Backend Stack
+
+### Core Framework & Language
+- **.NET 10**
+- **C# Minimal API** - Lightweight and modern API approach
+- **Entity Framework Core 10** - ORM for data access (matches .NET 10 version)
+- **FluentValidation** - Validation for models and DTOs
+- **linq2db** - Ultra-lightweight, high-performance ORM for complex optimized queries
+- **DynamicLinq** - Dynamic query construction from strings (runtime filters)
+- **LinqKit** - Composable and reusable LINQ expressions with type safety
+
+### ORM Strategy & When to Use Each Tool
+
+#### Entity Framework Core 10 (Primary ORM)
+**Use for:**
+- Standard CRUD operations
+- DDD entities with tracking (Aggregate Roots, Domain Events)
+- Simple to moderate queries
+- Queries that participate in aggregate lifecycle
+- Navigation properties and relationships
+- Change tracking scenarios
+
+#### linq2db
+**Ultra-lightweight ORM for maximum performance and SQL control**
+
+✔ **Use when:**
+- Need highly optimized complex queries
+- Advanced subqueries and complex projections
+- Multiple joins with dynamic conditions
+- Queries that EF Core cannot translate efficiently
+- Endpoints require extreme performance:
+  - Dashboards
+  - Analytics
+  - Fast transactional reports
+  - High data volumes
+- Microservice requires pure queries without tracking (linq2db operates naturally without tracking → faster)
+- EF Core generates inefficient SQL and you need alternatives without changing stack
+- Want SQL nearly as efficient as hand-written, but without explicit SQL
+
+🚫 **Do NOT use when:**
+- Need complete DDD entities (aggregate roots, tracking, events)
+- Query participates in aggregate lifecycle
+- Only need simple filters or trivial pagination
+
+#### DynamicLinq
+**Dynamic query generation from strings for runtime filters**
+
+✔ **Use when:**
+- Microservice offers dynamic filter system:
+  - Example: `?filter=Age > 30 AND Country == "CO"`
+  - Example: `?sort=Name desc`
+- Building simplified OData-style API without using OData
+- Generic queries over tables
+- Variable column searches
+- Data explorers or configurable grids
+- Want to avoid manually generating Expression Trees (DynamicLinq is much simpler)
+
+🚫 **Do NOT use when:**
+- Filters are fully controlled in code
+- Don't want to interpret expressions at runtime
+- Require strict security (DynamicLinq requires sanitization)
+- Need maximum performance (use LinqKit or linq2db instead)
+
+#### LinqKit
+**Composable dynamic predicates with type safety**
+
+✔ **Use when:**
+- Have complex business rules in queries
+- Composable predicates example:
+  ```csharp
+  IsActive
+  RequiresApproval
+  BelongsToOrganization(user.OrgId)
+  ```
+- Want dynamic filters with type safety (no strings → expressions)
+- Combine multiple expressions in a single `Where()`:
+  - Especially useful in DDD repositories with:
+    - Multiple criteria
+    - Conditional searches
+    - Reusable queries
+- Need EF Core to translate the resulting expression (LinqKit is 100% compatible with EF Core)
+- Want to enhance EF Core when it fails to compose complex expressions
+
+🚫 **Do NOT use when:**
+- Filters are extremely simple
+- Query is highly dynamic and text-based (use DynamicLinq)
+- Need maximum performance (use linq2db)
+
+### Architecture & Design Patterns
+- **TDD (Test-Driven Development)** - Test-driven development approach
+- **DDD (Domain-Driven Design)** - Domain-oriented design
+- **Clean Architecture** - Clean architecture with layer separation
+- **Microservices** - Distributed services architecture
+- **REST API** - Primary communication protocol
+
+### Database & Data Management
+- **PostgreSQL** - Primary relational database (mandatory)
+- **Database per Microservice** - Each microservice has its own isolated database
+- **Primary Keys UUID** - Universal unique identifiers for all entities
+- **EF Core 10 Migrations** - Entity Framework migrations package for schema version control
+
+### Testing
+- **xUnit** - Unit and integration testing framework
+- **EF Core 10 InMemory** - In-memory database for fast tests
+- **PostgreSQL Test Containers** - PostgreSQL containers for real integration tests
+
+### Additional Libraries
+- **QuestPDF** - PDF document generation
+- **DynamicLinq** - Dynamic LINQ query construction
+- **LinqKit** - LINQ expression composition
+
+### API Documentation
+- **Scalar** - Modern API documentation (DO NOT use Swagger)
+
+### Infrastructure & DevOps
+- **Docker Ready** - Containerized applications ready for deployment (production only)
+- **Local Development** - Without Docker, direct execution with dotnet CLI
+- **Multiculture** - Support for internationalization (i18n) and localization (l10n)
+
+## Backend Core Principles
+
+### Clean Architecture First
+Strict separation of:
+- Domain layer (Entities, Value Objects, Aggregates, Domain Services)
+- Application layer (Commands, Queries, DTOs, Interfaces)
+- Infrastructure layer (Repositories, EF Core, External Services)
+- Presentation layer (Minimal API Endpoints)
+
+### Domain-Driven Design
+Business logic drives architecture decisions
+
+### Test-Driven Development
+- Write tests before or alongside implementation
+- xUnit for all backend tests
+- High test coverage requirement
+
+### Microservices Isolation
+- Each service is independent
+- Own PostgreSQL database per service
+- No shared databases between services
+
+### UUID Primary Keys
+All entities must use UUIDs (Guid in C#) as primary keys for distributed system compatibility
+
+### Type Safety
+Leverage C# strong typing for compile-time safety
+
+### Security by Design
+Implement security at every layer
+
+### Docker for Production Only
+- Development: dotnet run locally
+- Production: Docker containers

package/bmad-core/tasks/apply-qa-fixes.md

@@ -16,8 +16,8 @@ Implement fixes based on QA results (gate and assessments) for a specific story.
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "2.2"
-  - qa_root: from `bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
-  - story_root: from `bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
+  - qa_root: from `.bmad-core/core-config.yaml` key `qa.qaLocation` (e.g., `docs/project/qa`)
+  - story_root: from `.bmad-core/core-config.yaml` key `devStoryLocation` (e.g., `docs/project/stories`)
 
 optional:
   - story_title: '{title}' # derive from story H1 if missing
@@ -45,7 +45,7 @@ optional:
 
 ### 0) Load Core Config & Locate Story
 
-- Read `bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
+- Read `.bmad-core/core-config.yaml` and resolve `qa_root` and `story_root`
 - Locate story file in `{story_root}/{epic}.{story}.*.md`
   - HALT if missing and ask for correct story id/path
 
@@ -113,7 +113,7 @@ Status Rule:
 
 ## Blocking Conditions
 
-- Missing `bmad-core/core-config.yaml`
+- Missing `.bmad-core/core-config.yaml`
 - Story file not found for `story_id`
 - No QA artifacts found (neither gate nor assessments)
   - HALT and request QA to generate at least a gate file (or proceed only with clear developer-provided fix list)

package/bmad-core/tasks/create-doc.md

@@ -23,6 +23,58 @@ When this task is invoked:
 
 If a YAML Template has not been provided, list all templates from .bmad-core/templates or ask the user to provide another.
 
+## CRITICAL: Title Preservation Rule
+
+**MANDATORY REQUIREMENTS FOR ALL SECTION TITLES:**
+
+1. **Preserve exact title text** - Copy section titles character-by-character from the YAML template
+2. **NO NUMBERS** - Never add numeric prefixes (1., 2., 3., etc.) to section titles
+3. **ENGLISH ONLY** - Never translate section titles to other languages
+4. **NO MODIFICATIONS** - Do not rephrase, reword, or alter section titles in any way
+5. **Template is the source of truth** - The title field in the YAML template is definitive
+
+**Examples:**
+- ✅ CORRECT: `# High Level Architecture`
+- ❌ WRONG: `# 2. High Level Architecture`
+- ❌ WRONG: `# Arquitectura de Alto Nivel`
+- ❌ WRONG: `# High-Level Architecture Overview`
+- ❌ WRONG: `# 2. Arquitectura de Alto Nivel`
+
+**This rule applies to:**
+- Main section headings (# Title)
+- Subsection headings (## Title)
+- All levels of nested sections
+
+**VIOLATION INDICATOR:** If you add numbers, translate, or modify any section title from the template, you have violated this rule.
+
+## CRITICAL: Document Language Rule
+
+**ALL DOCUMENT CONTENT MUST BE WRITTEN IN ENGLISH:**
+
+Regardless of what language you use to converse with the user, ALL documentation artifacts must be written entirely in English.
+
+**This applies to:**
+- Section titles (already covered by Title Preservation Rule)
+- Section content and descriptions
+- Examples and code comments
+- Table contents and headers
+- Bullet points and numbered lists
+- Technical specifications
+- User stories and acceptance criteria
+- All other documentation text
+
+**Examples:**
+- ✅ CORRECT: "The system must support user authentication"
+- ❌ WRONG: "El sistema debe soportar autenticación de usuarios"
+- ✅ CORRECT: "Epic 1: Foundation and Infrastructure"
+- ❌ WRONG: "Epic 1: Fundación e Infraestructura"
+
+**IMPORTANT DISTINCTION:**
+- **Conversation with user:** Use user's preferred language (Spanish, English, etc.)
+- **Document content:** ALWAYS English, no exceptions
+
+**VIOLATION INDICATOR:** If any document content (titles, descriptions, examples, etc.) is written in a language other than English, you have violated this rule.
+
 ## CRITICAL: Mandatory Elicitation Format
 
 **When `elicit: true`, this is a HARD STOP requiring user interaction:**
@@ -56,6 +108,7 @@ If a YAML Template has not been provided, list all templates from .bmad-core/tem
    - Process each section one at a time:
      - Skip if condition unmet
      - Check agent permissions (owner/editors)
+     - **PRESERVE EXACT TITLE from template (no numbers, no translation)**
      - Draft content using section instruction
      - Present content + detailed rationale
      - **IF elicit: true** → MANDATORY 1-9 options format
@@ -118,6 +171,7 @@ User can type `#yolo` to toggle to YOLO mode (process sections in batches withou
    - Process each sub-batch separately with pauses
 
 3. **Process EACH batch:**
+   - **PRESERVE EXACT TITLES from template (no numbers, no translation)**
    - Generate content for batch sections
    - Save to file
    - STOP and tell user: "✅ Batch X/Y complete: Sections A-B saved. Type 'continue'."
@@ -138,6 +192,9 @@ User can type `#yolo` to toggle to YOLO mode (process sections in batches withou
 - Ask yes/no questions for elicitation
 - Use any format other than 1-9 numbered options
 - Create new elicitation methods
+- Add numbers to section titles (1., 2., etc.)
+- Translate section titles from English
+- Modify or rephrase section titles from the template
 
 **✅ ALWAYS:**
 
@@ -145,3 +202,5 @@ User can type `#yolo` to toggle to YOLO mode (process sections in batches withou
 - Select options 2-9 from data/elicitation-methods only
 - Provide detailed rationale explaining decisions
 - End with "Select 1-9 or just type your question/feedback:"
+- Preserve exact section titles from YAML template without modification
+- Keep all section titles in English as defined in template

package/bmad-core/tasks/create-entity.md

@@ -108,8 +108,8 @@ For each domain event:
 - Integration with application layer
 - Serialization for external systems
 
-### Step 7: Generate Prisma Schema
-Update Prisma schema with:
+### Step 7: Generate Entity Framework Configuration
+Create EF Core entity configuration with:
 - Entity table definition
 - Proper field types and constraints
 - Relationships with other entities
@@ -129,5 +129,5 @@ Create comprehensive tests:
 - Business rules properly enforced
 - Value objects provide type safety
 - Domain events properly implemented
-- Prisma schema updated
+- Entity Framework Core configuration created
 - Comprehensive test coverage

package/bmad-core/tasks/create-next-story.md

@@ -11,7 +11,7 @@ To identify the next logical story based on project progress and epic definition
 ### 0. Load Core Configuration and Check Workflow
 
 - Load `.bmad-core/core-config.yaml` from the project root
-- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
+- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy it from GITHUB .bmad-core/core-config.yaml and configure it for your project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure core-config.yaml before proceeding."
 - Extract key configurations: `devStoryLocation`, `prd.*`, `architecture.*`, `workflow.*`
 
 ### 1. Identify Next Story for Preparation

package/bmad-core/tasks/create-service.md

@@ -65,7 +65,7 @@ src/modules/{service-name}/
 │       └── {entity}.domain-service.ts
 └── infrastructure/
     ├── repositories/
-    │   └── prisma-{entity}.repository.ts
+    │   └── {Entity}Repository.cs
     ├── services/
     │   └── {external-service}.adapter.ts
     └── events/
@@ -89,7 +89,7 @@ For each use case:
 - Define repository and service interfaces (ports)
 
 ### Step 5: Generate Infrastructure Layer
-- Implement Prisma repository adapters
+- Implement Entity Framework Core repository adapters
 - Create external service adapters
 - Implement event handlers
 - Configure dependency injection
@@ -112,7 +112,7 @@ For each use case:
 ## Completion Criteria
 - Service follows hexagonal architecture patterns
 - All layers properly separated and tested
-- Prisma schema updated and migrated
+- Entity Framework Core migrations created and applied
 - API endpoints documented in Swagger
 - Tests cover all critical paths
 - Dependencies properly injected

package/bmad-core/tasks/nfr-assess.md

@@ -9,11 +9,11 @@ Quick NFR validation focused on the core four: security, performance, reliabilit
 ```yaml
 required:
   - story_id: '{epic}.{story}' # e.g., "1.3"
-  - story_path: `bmad-core/core-config.yaml` for the `devStoryLocation`
+  - story_path: `.bmad-core/core-config.yaml` for the `devStoryLocation`
 
 optional:
-  - architecture_refs: `bmad-core/core-config.yaml` for the `architecture.architectureFile`
-  - technical_preferences: `bmad-core/core-config.yaml` for the `technicalPreferences`
+  - architecture_refs: `.bmad-core/core-config.yaml` for the `architecture.architectureFile`
+  - technical_preferences: `.bmad-core/core-config.yaml` for the `technicalPreferences`
   - acceptance_criteria: From story file
 ```
 

package/bmad-core/tasks/qa-gate.md

@@ -16,7 +16,7 @@ Generate a standalone quality gate file that provides a clear pass/fail decision
 
 ## Gate File Location
 
-**ALWAYS** check the `bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
+**ALWAYS** check the `.bmad-core/core-config.yaml` for the `qa.qaLocation/gates`
 
 Slug rules:
 
@@ -126,7 +126,7 @@ waiver:
 
 ## Output Requirements
 
-1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `bmad-core/core-config.yaml`
+1. **ALWAYS** create gate file at: `qa.qaLocation/gates` from `.bmad-core/core-config.yaml`
 2. **ALWAYS** append this exact format to story's QA Results section:
 
    ```text

package/bmad-core/tasks/review-story.md

@@ -186,7 +186,7 @@ NFR assessment: qa.qaLocation/assessments/{epic}.{story}-nfr-{YYYYMMDD}.md
 **Template and Directory:**
 
 - Render from `../templates/qa-gate-tmpl.yaml`
-- Create directory defined in `qa.qaLocation/gates` (see `bmad-core/core-config.yaml`) if missing
+- Create directory defined in `qa.qaLocation/gates` (see `.bmad-core/core-config.yaml`) if missing
 - Save to: `qa.qaLocation/gates/{epic}.{story}-{slug}.yml`
 
 Gate file structure:

package/bmad-core/tasks/scaffold-backend.md

@@ -1,9 +1,9 @@
 # Scaffold Backend Microservice
 
 ## Purpose
-Generate complete microservice structure with Hexagonal Architecture + DDD principles using NestJS.
+Generate complete microservice structure with Clean Architecture + DDD principles using .NET 10.
 
-**CRITICAL**: Always use NestJS 10+ with TypeScript, Prisma ORM, and strict hexagonal architecture patterns. No raw queries allowed - use Prisma for all database operations.
+**CRITICAL**: Always use .NET 10 with C# and Entity Framework Core. Follow Clean Architecture patterns strictly. No raw SQL allowed - use EF Core for all database operations.
 
 ## Task Configuration
 ```yaml
@@ -62,16 +62,20 @@ apps/{service-name}/
 │   ├── main.ts
 │   └── app.module.ts
 ├── test/
-├── prisma/
-│   ├── schema.prisma
+├── Microservicio.Infrastructure/
+│   ├── Persistence/
+│   │   ├── EF/
+│   │   │   ├── DbContexts/
+│   │   │   └── Migrations/
 │   └── migrations/
 └── package.json
 ```
 
-### Step 3: Setup NestJS Configuration
-- Initialize NestJS application with TypeScript
+### Step 3: Setup .NET Configuration
+- Initialize .NET 10 solution and projects
+- Configure C# language features
 - Configure Nx workspace if not exists
-- Setup Prisma with selected database
+- Setup Entity Framework Core with selected database provider
 - Configure dependency injection container
 - Setup validation with class-validator
 - Configure Swagger/OpenAPI documentation
@@ -83,7 +87,7 @@ For each bounded context:
 - Generate base domain entities with DDD patterns
 - Create application ports (interfaces)
 - Setup infrastructure adapters
-- Create Prisma schema definitions
+- Create Entity Framework Core entity configurations
 - Generate initial use cases
 
 ### Step 5: Setup Shared Infrastructure
@@ -104,7 +108,7 @@ For each bounded context:
 ## Completion Criteria
 - MonoRepo structure follows hexagonal architecture
 - All dependencies properly configured
-- Prisma schema generated and migrated
+- Entity Framework Core migrations generated and applied
 - TypeScript compiles without errors
 - Initial tests pass
 - Swagger documentation accessible

package/bmad-core/tasks/scaffold-frontend.md

@@ -3,7 +3,7 @@
 ## Purpose
 Generate complete frontend project structure with Clean Architecture + DDD principles.
 
-**CRITICAL**: Always use Next.js 14+ with App Router as the default framework. Only use pure React + Vite when user explicitly mentions offline-first functionality or specifically requests non-Next.js setup.
+**CRITICAL**: Always use Next.js 16+ with App Router as the default framework. Only use pure React + Vite when user explicitly mentions offline-first functionality or specifically requests non-Next.js setup.
 
 ## Task Configuration
 ```yaml
@@ -49,7 +49,7 @@ src/
 ```
 
 ### Step 3: Setup Configuration Files
-- Initialize Next.js 14+ project with TypeScript
+- Initialize Next.js 16+ project with TypeScript
 - Configure Next.js config for App Router
 - Setup TailwindCSS + Shadcn/ui integration
 - Configure Vitest for testing (with Next.js)

package/bmad-core/templates/architecture-tmpl.yaml

@@ -161,7 +161,7 @@ sections:
         examples:
           - "| **Language** | TypeScript | 5.3.3 | Primary development language | Strong typing, excellent tooling, team expertise |"
           - "| **Runtime** | Node.js | 20.11.0 | JavaScript runtime | LTS version, stable performance, wide ecosystem |"
-          - "| **Framework** | NestJS | 10.3.2 | Backend framework | Enterprise-ready, good DI, matches team patterns |"
+          - "| **Framework** | .NET 10 | 10.0 | Backend framework | Enterprise-ready, excellent DI, proven patterns |"\n          - "| **ORM** | Entity Framework Core | 10.0 | Data access | Type-safe, migrations support, LINQ queries |"
 
   - id: data-models
     title: Data Models
@@ -636,7 +636,7 @@ sections:
 
       2. **If backend/API project**:
          - Hand off to **Backend Agent (@backend)** for microservices implementation
-         - Backend agent will scaffold with NestJS + Hexagonal Architecture + DDD
+         - Backend agent will scaffold with .NET 10 + Clean Architecture + DDD + Entity Framework Core
          - Use `*scaffold` to create microservices with proper domain boundaries
 
       3. **For all projects**:

package/bmad-core/templates/front-end-architecture-tmpl.yaml

@@ -44,7 +44,7 @@ sections:
          - Use this analysis to ensure your frontend architecture aligns with the starter's patterns
 
       3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:
-         - **DEFAULT RECOMMENDATION**: Next.js 14+ with App Router (recommended for most projects)
+         - **DEFAULT RECOMMENDATION**: Next.js 16+ with App Router (recommended for most projects)
          - Based on specific requirements, suggest alternatives:
            - React with offline-first: Vite + React + Workbox
            - Vue projects: Vue CLI, Nuxt.js, Vite + Vue

package/bmad-core/templates/story-tmpl.yaml

@@ -5,7 +5,7 @@ template:
   version: 2.0
   output:
     format: markdown
-    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.md
+    filename: docs/stories/{{epic_num}}.{{story_num}}.{{story_title_short}}.story.md
     title: "Story {{epic_num}}.{{story_num}}: {{story_title_short}}"
 
 workflow:

package/bmad-core/user-guide.md

@@ -501,7 +501,7 @@ When creating custom web bundles or uploading to AI platforms, include your `tec
 
 ## Core Configuration
 
-The `bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
+The `.bmad-core/core-config.yaml` file is a critical config that enables BMad to work seamlessly with differing project structures, more options will be made available in the future. Currently the most important is the devLoadAlwaysFiles list section in the yaml.
 
 ### Developer Context Files
 

package/claude/commands/BMad/agents/analyst.md

@@ -23,7 +23,7 @@ REQUEST-RESOLUTION: Match user requests to your commands/dependencies flexibly (
 activation-instructions:
   - STEP 1: Read THIS ENTIRE FILE - it contains your complete persona definition
   - STEP 2: Adopt the persona defined in the 'agent' and 'persona' sections below
-  - STEP 3: Load and read `bmad-core/core-config.yaml` (project configuration) before any greeting
+  - STEP 3: Load and read `.bmad-core/core-config.yaml` (project configuration) before any greeting
   - STEP 4: Greet user with your name/role and immediately run `*help` to display available commands
   - DO NOT: Load any other agent files during activation
   - ONLY load dependency files when user selects them for execution via command or request of a task