@atlashub/smartstack-cli 4.18.0 → 4.19.0

package/templates/skills/business-analyse/steps/step-03c-compile.md

@@ -1,516 +0,0 @@
----
-name: step-03c-compile
-description: Module specification compilation - actors, use cases, FRs, permissions, navigation, seed data, Gherkin, i18n
-model: opus
-next_step: steps/step-03d-validate.md
----
-
-> **Context files:** `_shared.md` | `_module-loop.md` | `_rules.md`
-
-# Step 3c: Specification Compilation
-
-## MANDATORY EXECUTION RULES
-
-- ALWAYS use ULTRATHINK mode
-- This step COMPILES the specification from the interactive phase (step-03a) into feature.json
-- ALWAYS validate specification completeness before writing
-- ALL communication in `{language}`
-- NEVER skip per-module validation
-- **Rules:** See `_rules.md` § "ID Naming Convention" and § "Schema Conformity" (MANDATORY, NO EXCEPTION)
-
-## YOUR TASK
-
-Compile all data collected in step-03a (data) and step-03b (UI) into the module specification: generate actors, use cases, functional requirements, permission matrix, navigation, seed data, Gherkin scenarios, validations, messages, lifecycle, API endpoints, and i18n keys.
-
----
-
-### 8. Full Specification
-
-Generate the complete specification for this module. **Each subsection below includes a STRUCTURE CARD showing the EXACT JSON format. Follow them precisely.**
-
-> **Reference:** Load `references/compilation-structure-cards.md` for all STRUCTURE CARD definitions and type inference guidance.
-
-#### ENTITY ATTRIBUTE SCHEMA (MANDATORY — applies to ALL entities in section 6b of step-03a)
-
-> **CRITICAL:** Entity attributes MUST use STRUCTURED properties, not free-text validation strings.
-> The ralph-loop needs parseable types to generate correct C# code.
-
-**MANDATORY fields:** `name`, `type`
-**type values:** `string`, `int`, `long`, `decimal`, `double`, `bool`, `DateTime`, `DateOnly`, `TimeOnly`, `Guid`, `enum:{EnumName}`, `byte[]`
-
-The reference includes:
-- Detailed STRUCTURE CARD for entity attributes (with FK examples)
-- Type inference priority table for auto-fixing missing types
-- BaseEntity inheritance rules (tenantId, createdAt, updatedAt, createdBy, updatedBy)
-
-#### ENTITY ATTRIBUTE FORMAT POST-CHECK (BLOCKING — runs for EVERY module including the first)
-
-> **CRITICAL:** This check ensures EVERY entity attribute has a structured `type` field.
-> It runs for ALL modules, not just modules 2+. The first module is NOT exempt.
-> Without `type`, ralph-loop cannot generate correct C# properties, EF configurations, or validators.
-
-**Reference:** Load `references/compilation-structure-cards.md` § "Type Inference Priority Table" for the complete auto-fix logic and inference patterns.
-
-After compiling entities for this module:
-1. Verify every entity attribute has a `type` field (not free-text only)
-2. Apply auto-fix logic (infer from validation string or attribute name patterns)
-3. Normalize free-text validation into structured maxLength/validation properties
-4. Ensure required defaults to true if absent
-
----
-
-#### 8a-8l. Specification Structure Cards
-
-> **Reference:** Load `references/compilation-structure-cards.md` for all STRUCTURE CARD definitions.
-
-The reference includes detailed JSON templates for:
-- **8a. Actors** — role and permissions mapping
-- **8b. Use Cases** — UC-{PREFIX}-NNN format with scenarios
-- **8c. Functional Requirements** — FR-{PREFIX}-NNN format
-- **8d. Permission Matrix** — role assignments and paths
-- **8e. Navigation** — module, sections, and resources
-- **8f. SeedData Core** — 9 mandatory arrays
-- **8g. Gherkin Scenarios** — BDD format (MUST be array)
-- **8h. Validations** — field rules and error keys
-- **8i. Messages** — success/error/warning/info types
-- **8j. Entity Lifecycle** — state machines
-- **8k. API Endpoints** — RESTful routes
-- **8l. i18n Keys** — 4 languages (fr, en, it, de)
-
-#### 8b. Use Cases (UC-{PREFIX}-NNN)
-
-Per section: list, create, read, update, delete, approve, etc.
-
-> **STRUCTURE CARD: specification.useCases[]**
-> ```json
-> {
->   "id": "UC-{PREFIX}-001",
->   "name": "Create Order",
->   "primaryActor": "Sales Representative",
->   "permission": "{app}.{module}.create",
->   "preconditions": ["Customer exists", "Products in stock"],
->   "postconditions": ["Order created with Draft status"],
->   "mainScenario": [
->     "1. User navigates to creation form",
->     "2. User fills in required fields",
->     "3. System validates data (BR-VAL-{PREFIX}-001)",
->     "4. System creates the record",
->     "5. System displays confirmation"
->   ],
->   "alternativeScenarios": [
->     { "name": "Validation failure", "steps": ["1. System detects invalid data", "2. System highlights errors"] }
->   ],
->   "errorScenarios": [
->     { "name": "Server error", "steps": ["1. System shows error message", "2. Data preserved for retry"] }
->   ],
->   "linkedRules": ["BR-VAL-{PREFIX}-001", "BR-WF-{PREFIX}-002"]
-> }
-> ```
-> **MANDATORY fields:** `id`, `name`, `primaryActor`, `permission`, `mainScenario`, `linkedRules`
-> **FORBIDDEN fields:** Do NOT use `actor` (use `primaryActor`), `linkedBRs` (use `linkedRules`), `linkedFRs` (not in UC, FRs link to UCs instead)
-
-#### 8c. Functional Requirements (FR-{PREFIX}-NNN)
-
-Linked to BRs and UCs.
-
-> **STRUCTURE CARD: specification.functionalRequirements[]**
-> ```json
-> {
->   "id": "FR-{PREFIX}-001",
->   "statement": "System MUST validate customer budget before order creation",
->   "priority": "must|should|could",
->   "linkedRules": ["BR-VAL-{PREFIX}-001"],
->   "linkedUseCases": ["UC-{PREFIX}-001"],
->   "acceptanceCriteria": [
->     "Order rejected if total > budget",
->     "Error message displayed with remaining budget"
->   ]
-> }
-> ```
-> **MANDATORY fields:** `id`, `statement`, `priority`, `linkedUseCases`
-> **FORBIDDEN fields:** Do NOT use `name`/`description` (use `statement` with System MUST/SHOULD/COULD format), `linkedUCs` (use `linkedUseCases`), `linkedBRs` (use `linkedRules`)
-
-#### 8d. Permission Matrix
-
-Roles × resources × operations with full paths.
-
-> **STRUCTURE CARD: specification.permissionMatrix**
-> ```json
-> {
->   "permissions": [
->     { "path": "{app}.{module}.read", "action": "read", "description": "View records" },
->     { "path": "{app}.{module}.create", "action": "create", "description": "Create new records" },
->     { "path": "{app}.{module}.update", "action": "update", "description": "Update existing records" },
->     { "path": "{app}.{module}.delete", "action": "delete", "description": "Delete records" },
->     { "path": "{app}.{module}.export", "action": "export", "description": "Export data" },
->     { "path": "{app}.{module}.dashboard.read", "action": "read", "description": "View dashboard (section-level)" }
->   ],
->   "roleAssignments": [
->     { "role": "{App} Admin", "permissions": ["{app}.{module}.read", "{app}.{module}.create", "{app}.{module}.update", "{app}.{module}.delete", "{app}.{module}.export", "{app}.{module}.dashboard.read"] },
->     { "role": "{App} Manager", "permissions": ["{app}.{module}.read", "{app}.{module}.create", "{app}.{module}.update", "{app}.{module}.dashboard.read"] },
->     { "role": "{App} Viewer", "permissions": ["{app}.{module}.read"] }
->   ]
-> }
-> ```
-> **STRUCTURE:** Object with 2 arrays: `permissions[]` and `roleAssignments[]`
-> **Permission levels:** Module-level = `{app}.{module}.{action}` (3 segments). Section-level = `{app}.{module}.{section}.{action}` (4 segments, for sections needing distinct access like dashboard, approve, import).
-> **FORBIDDEN:** Do NOT use a flat array with `resource`/`roles` fields. Always use the nested structure above.
-
-#### 8e. Navigation
-
-Module → Sections → Resources (levels 2-3-4 of the hierarchy).
-
-> **STRUCTURE CARD: specification.navigation**
-> ```json
-> {
->   "entries": [
->     { "level": "module", "code": "{module}", "labels": {"fr": "...", "en": "...", "it": "...", "de": "..."}, "route": "/{app}/{module}", "icon": "list" },
->     { "level": "section", "code": "list", "labels": {"fr": "Liste", "en": "List", "it": "Elenco", "de": "Liste"}, "route": "/{app}/{module}", "icon": "list" },
->     { "level": "section", "code": "dashboard", "labels": {"fr": "Tableau de bord", "en": "Dashboard", "it": "Cruscotto", "de": "Dashboard"}, "route": "/{app}/{module}/dashboard", "icon": "chart-bar", "isNew": true }
->   ]
-> }
-> ```
-
-#### 8e-POST-CHECK: Navigation Enforcement (BLOCKING)
-
-> **CRITICAL:** `specification.navigation.entries[]` is MANDATORY. If absent, auto-generate from sections.
-
-**Auto-generation rule:** If `specification.navigation.entries[]` is empty or absent, generate it from `specification.sections[]`:
-
-1. Create a module-level entry: `level: "module"`, `code: {module}`, labels in 4 languages, `route: /{app}/{module}`, `icon: "list"`
-2. For each section in `specification.sections[]`, create a section-level entry:
-   - `code` = section.code
-   - `labels` = section.name (or section.code) in all 4 languages
-   - `route` = section.route (or `/{app}/{module}/{section.code}`)
-   - `icon` = section.icon (or `"file-text"` default)
-3. **Language completeness:** For every entry, verify all 4 languages (fr, en, it, de) exist in `labels`. If missing, copy from `en` → `fr` → first available value.
-
-#### 8f. SeedData Core
-
-9 MANDATORY typed arrays — each with structured objects, NOT flat strings or objects.
-
-> **STRUCTURE CARD: specification.seedDataCore**
-> ```json
-> {
->   "navigationApplications": [
->     { "code": "{app}", "label": "{Application Name}", "icon": "{icon}", "route": "/{app-kebab}", "sort": 1 }
->   ],
->   "applicationRoles": [
->     { "code": "admin", "name": "{App} Admin", "permissions": "*" },
->     { "code": "manager", "name": "{App} Manager", "permissions": "CRU" },
->     { "code": "contributor", "name": "{App} Contributor", "permissions": "CR" },
->     { "code": "viewer", "name": "{App} Viewer", "permissions": "R" }
->   ],
->   "navigationModules": [
->     { "code": "{module}", "label": "{Module Name}", "icon": "list", "route": "/{app}/{module}", "parentCode": "{app}", "sort": 1 }
->   ],
->   "navigationSections": [
->     { "code": "list", "label": "Liste", "icon": "List", "route": "/{app}/{module}", "parentCode": "{module}", "permission": "{app}.{module}.read", "sort": 1 },
->     { "code": "detail", "label": "Détail", "icon": "FileText", "route": "/{app}/{module}/:id", "parentCode": "{module}", "permission": "{app}.{module}.read", "sort": 2, "navigation": "hidden" },
->     { "code": "dashboard", "label": "Dashboard", "icon": "BarChart", "route": "/{app}/{module}/dashboard", "parentCode": "{module}", "permission": "{app}.{module}.dashboard.read", "sort": 3 }
->   ],
->   "navigationResources": [
->     { "code": "{module}-grid", "type": "SmartTable", "entity": "{Entity}", "parentCode": "list", "permission": "{app}.{module}.read" },
->     { "code": "{module}-detail-card", "type": "DetailCard", "entity": "{Entity}", "parentCode": "detail", "permission": "{app}.{module}.read" }
->   ],
->   "navigationTranslations": [
->     { "moduleCode": "{module}", "language": "fr", "label": "..." },
->     { "moduleCode": "{module}", "language": "en", "label": "..." },
->     { "moduleCode": "{module}", "language": "it", "label": "..." },
->     { "moduleCode": "{module}", "language": "de", "label": "..." }
->   ],
->   "permissions": [
->     { "path": "{app}.{module}.read", "action": "read", "description": "View {module}" },
->     { "path": "{app}.{module}.create", "action": "create", "description": "Create {module}" },
->     { "path": "{app}.{module}.dashboard.read", "action": "read", "description": "View {module} dashboard (section-level)" }
->   ],
->   "rolePermissions": [
->     { "role": "{App} Admin", "permissionPath": "{app}.{module}.*" },
->     { "role": "{App} Manager", "permissionPath": "{app}.{module}.read" }
->   ],
->   "permissionConstants": [
->     { "constantName": "{Module}Read", "path": "{app}.{module}.read" },
->     { "constantName": "{Module}Create", "path": "{app}.{module}.create" }
->   ]
-> }
-> ```
-> **MANDATORY:** All 9 arrays must be present. Each element must be an object, NOT a string.
-> **NOTE:** `navigationApplications` and `applicationRoles` are populated from the application identity confirmed in step-01b. They are written ONCE for the first module processed and remain empty `[]` for subsequent modules.
-> **CRITICAL:** `navigationSections` and `navigationResources` are DERIVED from `specification.sections[]` — use the transform algorithm below (section 8f-bis).
-> **IMPORTANT:** `create` and `edit` are NEVER sections — they are action pages reached via buttons. Do NOT include them in `navigationSections`. Only include actual sidebar sections (list, dashboard, approve, import, etc.) and hidden route sections (detail).
-> **FORBIDDEN:** Do NOT use `navigationModule` (singular string), `permissions` as flat string array, `rolePermissions` as flat object, `permissionsConstants` as comma-separated string.
->
-> **FORBIDDEN in navigation routes:**
-> - `/{app}/{module}/list` → use `/{app}/{module}` (list IS the module route)
-> - `/{app}/{module}/detail/:id` → use `/{app}/{module}/:id`
-> - Navigation routes must match React Router paths exactly
-
-#### 8f-bis. Transform Sections into Navigation SeedData
-
-> **CRITICAL:** `navigationSections` and `navigationResources` must be generated from `specification.sections[]`.
-> This ensures the navigation hierarchy (Module → Section → Resource) is complete in the database.
-
-**Transform algorithm (2 steps):**
-
-**Step 1 — Sections → navigationSections:** For each section in `specification.sections[]` (indexed from 0), create one entry:
-
-| Field | Source |
-|---|---|
-| `code` | `section.code` (e.g., "list", "detail", "dashboard") |
-| `label` | `section.labels.fr` (default language) |
-| `icon` | `section.icon` (Lucide icon name) |
-| `route` | `section.route` (full route path) |
-| `parentCode` | `metadata.module` (module code) |
-| `permission` | `section.permission` |
-| `sort` | index + 1 (1-based display order) |
-
-**Step 2 — Resources → navigationResources:** For each resource in each section's `resources[]`, create one entry:
-
-| Field | Source |
-|---|---|
-| `code` | `resource.code` (e.g., "employees-grid") |
-| `type` | `resource.type` (e.g., "SmartTable", "SmartForm") |
-| `entity` | `resource.entity` (e.g., "Employee") |
-| `parentCode` | `section.code` (parent section code) |
-| `permission` | `resource.permission` (optional, can inherit from section) |
-
-**Write seedDataCore to specification:**
-
-```
-ba-writer.enrichSection({
-  feature_id,
-  section: "specification",
-  data: {
-    seedDataCore: {
-      navigationApplications: [ ... ],            // FROM step-01b identity (only for first module, else [])
-      applicationRoles: [ ... ],                  // FROM cadrage.applicationRoles (only for first module, else [])
-      navigationModules: [ ... ],
-      navigationSections: navigationSections,     // DERIVED
-      navigationResources: navigationResources,   // DERIVED
-      navigationTranslations: [ ... ],
-      permissions: [ ... ],
-      rolePermissions: [ ... ],
-      permissionConstants: [ ... ]
-    }
-  }
-})
-```
-
-> **NOTE:** This step writes ONLY seedDataCore. The FULL specification write (actors, useCases, wireframes, sections, etc.) happens in step-03d section 11.
-> ALL data from 8a-8l MUST be carried forward to step-03d. Do NOT discard in-memory data.
-
-**Validation:**
-
-- EVERY section in `specification.sections[]` MUST appear in `navigationSections`
-- EVERY resource in `specification.sections[].resources[]` MUST appear in `navigationResources`
-- Total count: `navigationSections.length === specification.sections.length`
-- Total count: `navigationResources.length === sum(sections[].resources.length)`
-
-#### 8g. Gherkin Scenarios
-
-BDD acceptance tests per UC.
-
-> **STRUCTURE CARD: specification.gherkinScenarios[]**
-> ```json
-> {
->   "feature": "{Module} Management",
->   "scenarios": [
->     {
->       "name": "Create a new record with valid data",
->       "tags": ["@{module}", "@create", "@smoke"],
->       "given": ["An authenticated user with role Manager", "No existing record with code 'TEST-001'"],
->       "when": ["The user fills the creation form", "The user submits the form"],
->       "then": ["The record is created with Draft status", "A success message is displayed"]
->     }
->   ]
-> }
-> ```
-> **STRUCTURE:** MUST be an ARRAY of objects (NOT a single object). Each object has `feature` string + `scenarios[]` array. Each scenario has `given`, `when`, `then` as ARRAYS of strings.
-> **FORBIDDEN:** Do NOT use flat arrays of `{uc, scenario, given, when, then}` where given/when/then are single strings.
-> **FORBIDDEN:** Do NOT use a single object `{feature, scenarios}` — MUST be an ARRAY `[{feature, scenarios}]` even with one feature.
-
-#### 8h. Validations
-
-Field validation rules per entity.
-
-> **STRUCTURE CARD: specification.validations[]**
-> ```json
-> {
->   "entity": "Order",
->   "field": "amount",
->   "rules": ["required", "decimal", "min:0.01", "max:999999.99"],
->   "errorMessageKey": "validation.{module}.amount.invalid"
-> }
-> ```
-> **MANDATORY fields:** `entity`, `field`, `rules` (array), `errorMessageKey`
-> **FORBIDDEN fields:** Do NOT use `rule` (singular string) or `message` (use `errorMessageKey`).
-
-#### 8i. Business Messages
-
-Minimum 4: success, error CRUD, error validation, error permission.
-
-> **STRUCTURE CARD: specification.messages[]**
-> ```json
-> {
->   "code": "{MODULE}-SUCCESS-CREATE",
->   "type": "success|error|warning|info",
->   "title": "Record Created",
->   "message": "The record {code} has been created successfully.",
->   "i18nKey": "message.{module}.created"
-> }
-> ```
-> **MANDATORY fields:** `code`, `type`, `message`, `i18nKey`
-> **FORBIDDEN:** Do NOT omit `title` or `i18nKey`. Every message MUST have an i18n key.
-
-#### 8j. Entity Lifecycle
-
-State machines for entities with status/state.
-**Note:** If depth = full and 3a-state was executed, lifeCycles are already defined. Verify completeness and add any missing states/transitions.
-
-> **STRUCTURE CARD: specification.lifeCycles[]**
-> ```json
-> {
->   "entity": "Order",
->   "field": "status",
->   "initialState": "draft",
->   "states": [
->     { "id": "draft", "displayName": "Brouillon", "color": "gray", "allowedTransitions": ["submitted"], "isTerminal": false },
->     { "id": "submitted", "displayName": "Soumis", "color": "blue", "allowedTransitions": ["approved", "rejected"], "isTerminal": false },
->     { "id": "approved", "displayName": "Approuvé", "color": "green", "allowedTransitions": ["archived"], "isTerminal": false },
->     { "id": "rejected", "displayName": "Rejeté", "color": "red", "allowedTransitions": [], "isTerminal": true },
->     { "id": "archived", "displayName": "Archivé", "color": "purple", "allowedTransitions": [], "isTerminal": true }
->   ],
->   "transitions": [
->     {
->       "from": "draft", "to": "submitted", "action": "submit",
->       "label": { "fr": "Soumettre", "en": "Submit" },
->       "permission": "{app}.{module}.update",
->       "guards": ["BR-VAL-{PREFIX}-001"],
->       "effects": [{ "type": "notification", "target": "role:manager", "template": "{module}-submitted" }],
->       "confirm": true
->     }
->   ]
-> }
-> ```
-> **MANDATORY:** `states` MUST be an array of OBJECTS with `id`, `displayName`, `color`, `allowedTransitions`, `isTerminal`. NEVER use flat string arrays.
-> **Colors:** gray (draft/new), blue (in-progress), green (active/approved), yellow (warning/pending), orange (review), red (error/rejected), purple (archived/terminal)
-> **FORBIDDEN:** Do NOT use `states: ["Active", "Inactive"]` (flat strings), `terminalStates` (use `isTerminal: true` on each state).
-
-#### 8k. API Endpoints
-
-RESTful routes following SmartStack patterns.
-
-> **STRUCTURE CARD: specification.apiEndpoints[]**
-> ```json
-> {
->   "method": "GET|POST|PUT|PATCH|DELETE",
->   "path": "/api/{app}/{module}",
->   "permission": "{app}.{module}.read",
->   "requestDto": "Get{Module}Query",
->   "responseDto": "{Module}Dto[]",
->   "description": "List all records with pagination and filters"
-> }
-> ```
-> **MANDATORY fields:** `method`, `path`, `permission`, `description`
-> **Recommended:** Include `requestDto` and `responseDto` for implementation clarity.
-
-#### 8l. i18n Keys
-
-Translation keys for all UI text (4 languages: fr, en, it, de).
-
-> **STRUCTURE CARD: specification.i18nKeys**
-> **CRITICAL:** ALL leaf translation keys MUST have 4 languages (fr, en, it, de). IT/DE can use shorter translations but MUST exist.
-> ```json
-> {
->   "title": { "fr": "{Module}", "en": "{Module}", "it": "{Module}", "de": "{Module}" },
->   "list": {
->     "title": { "fr": "Liste", "en": "List", "it": "Elenco", "de": "Liste" },
->     "empty": { "fr": "Aucun enregistrement", "en": "No records", "it": "Nessun record", "de": "Keine Einträge" }
->   },
->   "create": { "title": { "fr": "Nouveau", "en": "New", "it": "Nuovo", "de": "Neu" } },
->   "detail": { "title": { "fr": "Détail", "en": "Detail", "it": "Dettaglio", "de": "Detail" } },
->   "buttons": {
->     "create": { "fr": "Créer", "en": "Create", "it": "Crea", "de": "Erstellen" },
->     "edit": { "fr": "Modifier", "en": "Edit", "it": "Modifica", "de": "Bearbeiten" },
->     "delete": { "fr": "Supprimer", "en": "Delete", "it": "Elimina", "de": "Löschen" },
->     "save": { "fr": "Enregistrer", "en": "Save", "it": "Salva", "de": "Speichern" },
->     "cancel": { "fr": "Annuler", "en": "Cancel", "it": "Annulla", "de": "Abbrechen" }
->   },
->   "validation": {
->     "required": { "fr": "Ce champ est requis", "en": "This field is required", "it": "Campo obbligatorio", "de": "Pflichtfeld" }
->   }
-> }
-> ```
-
-#### 8l-POST-CHECK: i18n 4 Languages Enforcement (BLOCKING)
-
-> **CRITICAL:** i18n keys with missing IT/DE translations are a recurring issue.
-> This POST-CHECK walks ALL leaf keys and auto-fills missing translations.
-
-**Auto-fill rule:** Traverse all nodes in `specification.i18nKeys` recursively.
-
-- A **leaf node** is any object that has at least one key among `fr`, `en`, `it`, `de` whose value is a string.
-- For each leaf node, ensure all 4 language keys exist as strings.
-- **Fallback order** for missing languages: copy from `en` → `fr` → first available string value in the node.
-- Log the count of auto-filled translations as a warning.
-
----
-
-## SELF-VERIFICATION (MANDATORY before loading next step)
-
-Before loading step-03d-validate, verify all 12 subsections (8a-8l) are populated:
-
-1. **8a. Actors** - At least 2 roles with permissions
-2. **8b. Use Cases** - At least 2 UCs with complete structure
-3. **8c. Functional Requirements** - At least 4 FRs with linked UCs and BRs
-4. **8d. Permission Matrix** - Resources and role assignments defined
-5. **8e. Navigation** - Module, sections, and resource routes specified
-6. **8f. SeedData Core** - All 9 arrays populated with structured objects (navigationApplications, applicationRoles, navigationModules, navigationSections, navigationResources, navigationTranslations, permissions, rolePermissions, permissionConstants)
-7. **8g. Gherkin Scenarios** - BDD scenarios for each major UC
-8. **8h. Validations** - Field rules with error message keys
-9. **8i. Business Messages** - Minimum 4 messages (success, error CRUD, validation, permission)
-10. **8j. Entity Lifecycle** - State machines with transitions if entity has status
-11. **8k. API Endpoints** - RESTful routes with permissions
-12. **8l. i18n Keys** - Translation keys in 4 languages (fr, en, it, de)
-
-13. **Wireframes present** — `(specification.uiWireframes || specification.wireframes || []).length >= 1` (BLOCKING)
-    Quick check: the wireframe data from step-03b MUST still be in memory OR persisted to feature.json
-
-14. **Wireframes create/edit** — For each data-centric section with a create form, a wireframe `{section}-create` MUST exist (BLOCKING).
-    For each modifiable entity, a wireframe `{section}-edit` SHOULD exist (WARNING if absent).
-    Create/edit wireframes are action-page wireframes — they are NOT separate navigation sections.
-    They describe the full-page form layout (fields, validation, submit/cancel buttons).
-    (step-03b now writes wireframes intermediately). If wireframes are empty:
-    - First, re-read the module feature.json to check if step-03b wrote them
-    - If present in file but not in memory → load them from file
-    - If absent everywhere → **STOP** and reload step-03b to regenerate wireframes
-
-**IF any subsection is missing → STOP and request the missing data before proceeding.**
-
-**ABSOLUTE FORMAT CHECKS (apply to ALL modules, including the first):**
-
-> These checks validate against the canonical schema — NOT comparatively against another module.
-> They run BEFORE the SCHEMA UNIFORMITY comparative check, ensuring the first module has the
-> correct format before being used as baseline for subsequent modules.
-
-> **Rules:** Apply `_rules.md` § "Format Checks" and § "Auto-Fix: Wireframe Field Names" to all specification data before proceeding.
->
-> Specifically: wrap gherkin in array if needed, normalize validation rules to arrays, ensure messages have `message` field, normalize wireframe field names, verify entity attribute types.
-
-**SCHEMA UNIFORMITY CHECK (multi-module mode):**
-IF this is NOT the first module in moduleOrder:
-  Compare THIS module's specification structure against the FIRST specified module:
-  - `gherkinScenarios` MUST be array (not object) in ALL modules
-  - `validations[].rules` MUST be array (not singular `rule`) in ALL modules
-  - `messages[]` MUST have `message` field in ALL modules
-  - `specification.apiEndpoints[]` MUST be present in ALL modules
-  - `specification.i18nKeys` MUST be present in ALL modules
-  - `analysis.entities[].attributes[].type` MUST be present on ALL attributes in ALL modules
-  - IF first module has free-text-only attributes without `type` field → AUTO-FIX with type inference
-  IF any structural divergence detected → AUTO-FIX to match the canonical format before proceeding.
-
----
-
-## NEXT STEP
-
-Load: `steps/step-03d-validate.md`