@atlashub/smartstack-cli 3.18.0 → 3.19.0

package/templates/skills/business-analyse/steps/step-03a1-setup.md

@@ -6,6 +6,7 @@ next_step: steps/step-03a2-analysis.md
 ---
 
 > **Context files:** `_shared.md` | `_elicitation.md` | `_architecture.md` | `_module-loop.md`
+> **Reference (5-bis):** `references/entity-architecture-decision.md` — Entity scoring, domain coherence, section patterns
 
 # Step 3a1: Setup - Module Initialization
 
@@ -198,31 +199,36 @@ Total: {N} requirements mapped to this module
 
 For each module, propose standard sections based on module type:
 
-| Module Type | Typical Sections |
-|-------------|-----------------|
-| data-centric | list, detail, create, edit |
-| workflow | list, detail, create, edit, approve, history |
-| integration | list, detail, config, sync, logs |
-| reporting | dashboard, detail, export, schedule |
-| full-module | list, detail, create, edit, approve, history, reports, settings |
+> **RULE:** Sections = functional zones only. `list` is ALWAYS present (default).
+> `create`/`edit` = actions within the `list` page (modal/drawer). `detail` = tabbed page from list click.
+
+| Module Type | Sections (functional zones) | Detail page tabs (from list click) |
+|-------------|---------------------------|-----------------------------------|
+| data-centric | list | Infos, {relations} |
+| workflow | list, approve | Infos, {relations}, Historique |
+| integration | list | Infos, Config, Logs, Sync |
+| reporting | dashboard | — |
+| full-module | list, dashboard, approve | Infos, {relations}, Historique |
+
+**Section `list` is automatic and ALWAYS included.** Ask ONLY about additional functional sections:
 
 Ask via AskUserQuestion:
 
 ```
-question: "Quelles sections le module {currentModule} doit-il avoir ?"
+question: "{language == 'fr'
+  ? 'Le module {currentModule} aura une page liste (avec création et détail par onglets). Quelles sections fonctionnelles supplémentaires souhaitez-vous ?'
+  : 'Module {currentModule} will have a list page (with create and tabbed detail). Which additional functional sections do you want?'}"
 header: "Sections"
 multiSelect: true
 options:
-  - label: "Liste"
-    description: "Page de liste avec filtres, tri et pagination"
-  - label: "Détail"
-    description: "Page de détail d'un enregistrement"
-  - label: "Création/Édition"
-    description: "Formulaire de création et de modification"
-  - label: "Validation/Approbation"
-    description: "Workflow de validation avec changement de statut"
   - label: "Dashboard"
-    description: "Tableau de bord avec KPIs, graphiques (Recharts) et métriques clés"
+    description: "{language == 'fr' ? 'Tableau de bord avec KPIs, graphiques et métriques clés' : 'Dashboard with KPIs, charts and key metrics'}"
+  - label: "Validation/Approbation"
+    description: "{language == 'fr' ? 'File d\'approbation avec workflow de changement de statut' : 'Approval queue with status change workflow'}"
+  - label: "Import en masse"
+    description: "{language == 'fr' ? 'Import CSV/Excel avec mapping et validation' : 'CSV/Excel import with mapping and validation'}"
+  - label: "{language == 'fr' ? 'Aucune (liste seule)' : 'None (list only)'}"
+    description: "{language == 'fr' ? 'Le module n\'a besoin que de la page liste avec détail' : 'Module only needs the list page with detail'}"
 ```
 
 #### 3a-depth. Determine Specification Depth
@@ -285,7 +291,7 @@ See [references/spec-auto-inference.md](../references/spec-auto-inference.md) fo
 - Entity attribute → SmartTable column mapping (9 type rules)
 - Entity attribute → SmartForm field mapping (8 type rules)
 - Auto-generated sections per featureType (5 types)
-- Section generation rules (list, create, detail, edit, dashboard)
+- Component generation rules (list section, create form in modal, detail page with tabs, dashboard section)
 - Status/lifecycle enhancement rules
 
 Write auto-generated sections to `specification.sections[]` via ba-writer.enrichSection()
@@ -351,40 +357,124 @@ options:
 
 #### 5-bis. Unresolved Entity Dependencies (New Module Detection)
 
-> **When an entity reference is detected that does NOT belong to any completed or planned module, apply the Entity Sourcing Pattern from step-01-cadrage (section 4d-bis).**
+> **When an entity reference is detected that does NOT belong to any completed or planned module, apply the SAME intelligent Entity Sourcing Pattern as step-01-cadrage (section 4d-bis).**
+> **Reference:** Load [references/entity-architecture-decision.md](../references/entity-architecture-decision.md) for scoring grid, decision tree, and section patterns.
 
 For each entity referenced by {currentModule} that is NOT covered by any existing/planned module:
 
+##### A. ULTRATHINK: Silent Analysis (NO output to client)
+
+> **Same intelligence as cadrage 4d-bis. Score the entity, assess domain coherence, recommend.**
+
+```
+ULTRATHINK — Entity Architecture Analysis for {entity_name} (discovered during specification of {currentModule}):
+
+1. DOMAIN COHERENCE
+   - Application domain: {app_description}
+   - Entity fit: CORE | SUPPORT | PERIPHERAL
+   - Justification: {1 sentence}
+
+2. ENTITY SCORING (5 criteria, 0-3 each — from scoring grid in reference)
+   - Lifecycle:  {score}/3
+   - Actors:     {score}/3
+   - Relations:  {score}/3
+   - Volume:     {score}/3
+   - Autonomy:   {score}/3
+   - TOTAL:      {total}/15 → {classification}
+
+3. PRE-CLASSIFICATION CHECK (from entity patterns in reference, section 10 of suggestion-catalog)
+   - Match? → {yes: which pattern | no: use scoring}
+
+4. RECOMMENDATION
+   - Option: {in_this_module | new_module | external_system | config_list}
+   - Confidence: HIGH | MEDIUM | LOW
+   - Reasoning: {1-2 sentences}
+
+5. IF recommendation = new_module → PRE-BUILD ARCHITECTURE
+   - Module code: {PascalCase}
+   - Section `list` + detail page tabs
+   - Additional sections (ONLY functional zones)
+   - Impact on dependency graph
+```
+
+##### B. Present Analysis & Recommendation
+
+**BEFORE AskUserQuestion, display as markdown:**
+
+```
+### {language == "fr" ? "Analyse" : "Analysis"} : {entity_plural}
+
+{language == "fr"
+  ? "Pendant la spécification de **{currentModule}**, j'ai détecté une référence aux **{entity_plural}** qui ne font partie d'aucun module existant."
+  : "During specification of **{currentModule}**, I detected a reference to **{entity_plural}** not covered by any existing module."}
+
+{language == "fr" ? "**Mon analyse :**" : "**My analysis:**"}
+- {language == "fr" ? "Cohérence domaine" : "Domain coherence"} : **{CORE|SUPPORT|PERIPHERAL}** — {justification}
+- {language == "fr" ? "Score de complexité" : "Complexity score"} : **{score}/15** ({classification})
+- **{language == "fr" ? "Recommandation" : "Recommendation"}** : **{recommended_option}** — {reasoning}
+```
+
+**IF recommendation = new_module AND confidence >= MEDIUM, ALSO display the architecture proposal** (same format as cadrage 4d-bis Phase 2: Context/Application/Module table + Sections table + Detail tabs table + Impact).
+
+##### C. Ask with Recommended Option First
+
 ```
 question: "{language == 'fr'
-  ? 'Les {entity_plural} référencés par {currentModule} ne font partie d\'aucun module. Comment les gérer ?'
-  : '{entity_plural} referenced by {currentModule} are not part of any module. How should they be managed?'}"
+  ? 'Comment souhaitez-vous gérer les {entity_plural} ?'
+  : 'How do you want to manage {entity_plural}?'}"
 header: "{entity_name}"
 options:
-  - label: "{language == 'fr' ? 'Dans ce module' : 'In this module'}"
+  (ORDER: recommended option FIRST with "(Recommandé)"/"(Recommended)", then remaining 3)
+
+  IF recommendation = new_module:
+  - label: "{language == 'fr' ? 'Nouveau module dédié (Recommandé)' : 'New dedicated module (Recommended)'}"
     description: "{language == 'fr'
-      ? 'Gérer les {entity_plural} comme une section/entité de {currentModule}'
-      : 'Manage {entity_plural} as a section/entity of {currentModule}'}"
-  - label: "{language == 'fr' ? 'Nouveau module dédié' : 'New dedicated module'}"
+      ? 'Module {ModuleCode} avec page liste, détail par onglets, permissions dédiées'
+      : '{ModuleCode} module with list page, tabbed detail, dedicated permissions'}"
+  - label: "{language == 'fr' ? 'Dans ce module' : 'In this module'}"
     description: "{language == 'fr'
-      ? 'Créer un module complet avec CRUD, permissions et navigation'
-      : 'Create a full module with CRUD, permissions and navigation'}"
+      ? 'Onglet dans la page détail de {currentModule}'
+      : 'Tab in {currentModule} detail page'}"
   - label: "{language == 'fr' ? 'Système externe' : 'External system'}"
-    description: "{language == 'fr'
-      ? 'Import ou API depuis un autre système'
-      : 'Import or API from another system'}"
+    description: "..."
   - label: "{language == 'fr' ? 'Liste de référence' : 'Reference list'}"
+    description: "..."
+
+  IF recommendation = config_list:
+  - label: "{language == 'fr' ? 'Liste de référence (Recommandé)' : 'Reference list (Recommended)'}"
     description: "{language == 'fr'
       ? 'Table de lookup configurable par l\'admin'
       : 'Admin-configurable lookup table'}"
+  - (3 remaining options in logical order)
+
+  IF recommendation = in_this_module:
+  - label: "{language == 'fr' ? 'Dans ce module (Recommandé)' : 'In this module (Recommended)'}"
+    description: "{language == 'fr'
+      ? 'Onglet dans la page détail de {currentModule}'
+      : 'Tab in {currentModule} detail page'}"
+  - (3 remaining options)
+
+  IF confidence = LOW:
+  (all 4 options in neutral order, NO "(Recommandé)" tag)
 ```
 
+##### D. Process Answer
+
+| Choice | Action |
+|--------|--------|
+| **Dans ce module** | Entity becomes a sub-entity of {currentModule}. Add as a **tab in the detail page**. Add to this module's `analysis.entities[]`. |
+| **Nouveau module dédié** | Add new module to master `modules[]` via ba-writer with proposed architecture (sections, detail tabs, dependencies). The `list` section is ALWAYS the main section. Additional sections ONLY for functional zones. |
+| **Système externe** | Flag for integration. Add to `coverageMatrix` as integration. |
+| **Liste de référence** | Lookup table, admin-managed. No module, no section. |
+
 **IF "Nouveau module dédié" is selected:**
 1. Add new module to master `modules[]` via ba-writer (status: "pending", sortOrder: after current module)
 2. Update dependency graph: current module depends on the new module
-3. **WARNING:** The new module will need specification AFTER the current one. Display:
+3. **Display:**
    ```
-   "⚠ Nouveau module '{entity_name}' ajouté. Il sera spécifié après {currentModule}."
+   "{language == 'fr'
+     ? '⚠ Nouveau module {ModuleCode} ajouté au graphe de dépendances. Il sera spécifié après {currentModule}.'
+     : '⚠ New module {ModuleCode} added to dependency graph. It will be specified after {currentModule}.'}"
    ```
 4. Update `metadata.workflow.moduleOrder` to include the new module (inserted after its dependents)
 

package/templates/skills/business-analyse/steps/step-03a2-analysis.md

@@ -6,6 +6,7 @@ next_step: steps/step-03b-ui.md
 ---
 
 > **Context files:** `_shared.md` | `_elicitation.md` | `_architecture.md` | `_module-loop.md`
+> **Reference (check 7):** `references/entity-architecture-decision.md` — Entity scoring for unresolved relationship targets
 
 # Step 3a2: Analysis - Entities & Business Logic
 
@@ -151,6 +152,13 @@ Before proceeding to step-03b-ui.md, VERIFY:
 4. **Module status in master** = "in-progress" (set by section 2 above)
 5. **Master modules[].featureJsonPath** for this module ≠ null (set by ba-writer.create)
 6. **Sections identified** with clear roles and entities assigned
+7. **Unresolved relationship targets (BLOCKING)** — For EACH entity's `relationships[].target`:
+   - Check if the target entity exists in THIS module's `entities[]`
+   - OR in a completed/planned module's `entities[]`
+   - OR is a known config list / external system reference
+   - **IF unresolved:** Apply the Entity Sourcing Pattern from step-03a1 section 5-bis
+     (ULTRATHINK scoring + domain coherence + recommendation + AskUserQuestion)
+   - This catches entities discovered DURING analysis that weren't identified in setup
 
 **IF any check fails → FIX before proceeding.** Do NOT load step-03b-ui with incomplete data.
 

package/templates/skills/business-analyse/steps/step-03b-ui.md

@@ -199,6 +199,64 @@ A wireframe without `componentMapping` or `layout` will FAIL validation in step
 
 > **IF client rejects a mockup:** Revise and re-propose until validated. Do NOT proceed without client approval on the layout.
 
+### 3b-detail. Generate Detail Page Wireframe (MANDATORY for each list section)
+
+> **BLOCKING RULE:** Every module with a `list` section MUST also have a detail page wireframe. The detail page is NOT a separate navigation entry — it is reached by clicking a row in the list. Its wireframe goes in `specification.uiWireframes[]` with `section: "detail"`.
+
+**Procedural sequence (MANDATORY):**
+
+1. **Determine detail tabs** from these sources (in priority order):
+   a. `coverageMatrix[].detailTabs` from cadrage (if specified)
+   b. Entity relationships: one tab per 1:N relationship (SmartTable of children)
+   c. Auto-inferred: Info tab (always first), History tab (if entity has lifeCycles)
+
+2. **Generate** an ASCII mockup for the detail page with tabbed layout:
+
+```
+╔═══════════════════════════════════════════════════════════╗
+║  ← Retour à la liste                                     ║
+╠═══════════════════════════════════════════════════════════╣
+║  {Entity} : {code} — {name}          ● {Statut}  [✏️ 🗑️] ║
+╠═══════════════════════════════════════════════════════════╣
+║  [ Informations ]  [ {Relation1} ]  [ Historique ]        ║
+╠═══════════════════════════════════════════════════════════╣
+║                                                           ║
+║  ┌── Informations ────────────────────────────────────┐   ║
+║  │  Code         │ VAL-001                            │   ║
+║  │  Nom          │ Exemple de nom                     │   ║
+║  │  Type         │ Standard                           │   ║
+║  │  Responsable  │ Jean Dupont                        │   ║
+║  │  Date début   │ 15.01.2026                         │   ║
+║  │  Description  │ Lorem ipsum dolor sit amet...      │   ║
+║  └────────────────────────────────────────────────────┘   ║
+║                                          [ Modifier ]     ║
+║                                                           ║
+╚═══════════════════════════════════════════════════════════╝
+```
+
+Adaptation rules for the detail mockup:
+- **Header**: entity code + name + status badge (if lifeCycles) + action buttons (edit, delete)
+- **Back button**: navigates to `/business/{app}/{module}/list`
+- **Tabs**: one per identified tab (Info + relations + history)
+- **Info tab content**: all entity attributes as label:value pairs (read-only by default)
+- **Edit button**: toggles the Info tab into SmartForm edit mode
+- **Relation tab content**: show a SmartTable for each 1:N child entity filtered by parent ID
+- **History tab content**: Timeline/audit log (only if entity has lifeCycles)
+
+3. **For entities with state machine (lifeCycles)**, add transition buttons in the header:
+```
+║  {Entity}: {code} — {name}    ● Brouillon  [Soumettre] [✏️] ║
+```
+Transition buttons are contextual: only show actions allowed from the current state.
+
+4. **Display** the detail mockup in conversation with header `### {Module} — Détail — Wireframe` and validate with client alongside the list wireframe.
+
+5. **Store** in `specification.uiWireframes[]` with `section: "detail"`.
+   See [references/ui-resource-cards.md](../references/ui-resource-cards.md) "Detail Page Wireframe" for exact JSON format.
+
+6. **Create the detail section** in `specification.sections[]` with `navigation: "hidden"` and route `/business/{app}/{module}/detail/:id`.
+   See [references/ui-resource-cards.md](../references/ui-resource-cards.md) "Detail Page section" for exact JSON format.
+
 ### 3b-bis. Wireframe-to-Component Mapping
 
 After client validates the mockup, map each wireframe element to a SmartStack React component:
@@ -212,6 +270,10 @@ After client validates the mockup, map each wireframe element to a SmartStack Re
 | ActionButton | `Button` + `RequirePermission` | Always wrapped in permission check |
 | StatusBadge | `StatusBadge` | Uses entity lifecycle states |
 | DetailCard | `EntityDetailCard` | Standard detail layout |
+| DetailHeader | `EntityDetailHeader` | Entity title + status badge + actions |
+| BackButton | `BackButton` | Navigate back to list |
+| TabPanel | `Tabs` | Tabbed content container |
+| Timeline | `AuditTimeline` | History/audit log display |
 | Form | `SmartForm` | FluentValidation-backed |
 | KpiCard | `StatCard` (Recharts) | Dashboard KPI display |
 | Chart:bar/line/pie | Recharts `BarChart`/`LineChart`/`PieChart` | CSS variables for colors |
@@ -248,9 +310,9 @@ For EACH wireframe generated in 3b, generate a `layout` object alongside the ASC
 
 For each section, identify what resources/components are needed:
 
-- List section → DataGrid, FilterBar, SearchInput, ExportButton
-- Detail section → DetailCard, StatusBadge, ActionButtons, Timeline
-- Create section → Form, ValidationMessages, SubmitButton
+- List section → DataGrid, FilterBar, SearchInput, ExportButton, CreateButton
+- Detail page (from list click) → BackButton, DetailHeader, StatusBadge, TabPanel, DetailCard, SmartForm (edit mode), SmartTable (relation tabs), Timeline (history tab)
+- Create (in list) → SmartForm (modal/drawer), ValidationMessages, SubmitButton
 - Approve section → StatusTransitionPanel, CommentBox, ApproveRejectButtons
 - Dashboard section → StatCard, RechartsChart (Bar/Line/Pie/Area), DashboardGrid, FilterBar
 
@@ -269,8 +331,9 @@ See [references/ui-dashboard-spec.md](../references/ui-dashboard-spec.md) for th
 
 Before proceeding to step-03c-compile.md, VERIFY:
 
-1. **Wireframes displayed and validated** — ALL wireframes were output as visible ASCII art in the conversation AND validated by the client via AskUserQuestion
-2. **Wireframes exist for all sections** in `specification.uiWireframes[]`
+1. **Wireframes displayed and validated** — ALL wireframes (list AND detail) were output as visible ASCII art in the conversation AND validated by the client via AskUserQuestion
+2. **Wireframes exist for all sections** in `specification.uiWireframes[]` — INCLUDING a `section: "detail"` wireframe for every module that has a `list` section
+2b. **Detail page companion check (BLOCKING)** — For EACH section with `code: "list"`, verify there is a matching wireframe with `section: "detail"` AND a section with `code: "detail"` + `navigation: "hidden"` + route containing `:id`. Missing detail page = FAIL.
 3. **All wireframes have componentMapping** with smarter mapping rules
 4. **All wireframes have layout** with regions and resourceRef references
 5. **All resource references** in layout.regions[].components[].resourceRef exist in sections[].resources[]

package/templates/skills/business-analyse/steps/step-05a-handoff.md

@@ -304,7 +304,104 @@ Total endpoints = count of specification.apiEndpoints[] across all modules.
    "✓ Handoff module {i+1}/{N} : {moduleCode} ({fileCount} fichiers, {brCount} BRs mappées)"
 ```
 
-#### 7b. Master Handoff (after ALL modules written successfully)
+#### 7b. Generate seedDataCore (MANDATORY for master feature.json)
+
+> **The seedDataCore provides ralph-loop with the exact navigation, permissions, and translations to seed.**
+> Without seedDataCore, ralph-loop must INVENT this data — leading to inconsistencies.
+
+```
+// Derive seedDataCore from modules[], applicationRoles[], and coverageMatrix[]
+
+const seedDataCore = {
+  navigationModules: master.modules.map((m, i) => ({
+    code: m.code,
+    label: m.name || m.code,
+    description: m.description,
+    icon: null,  // set by ralph-loop
+    iconType: "lucide",
+    route: `/business/${master.metadata.application.toLowerCase()}/${m.code.toLowerCase()}`,
+    displayOrder: (i + 1) * 10
+  })),
+
+  navigationSections: master.modules.flatMap(m =>
+    (m.anticipatedSections || []).map((s, j) => ({
+      moduleCode: m.code,
+      code: s.code,
+      label: s.description?.split(':')[0] || s.code,
+      description: s.description || "",
+      route: s.code === "detail" ? null : `/${s.code}`,
+      displayOrder: (j + 1) * 10,
+      navigation: s.code === "detail" ? "hidden" : "visible"
+    }))
+  ),
+
+  navigationResources: master.cadrage.coverageMatrix
+    .filter(cm => cm.module && cm.anticipatedResources?.length > 0)
+    .flatMap(cm =>
+      cm.anticipatedResources.map((r, k) => ({
+        moduleCode: cm.module,
+        sectionCode: cm.anticipatedSections?.[0] || "list",
+        code: r,
+        label: r.replace(/-/g, ' ').replace(/\b\w/g, c => c.toUpperCase()),
+        displayOrder: (k + 1) * 10
+      }))
+    ),
+
+  navigationTranslations: master.modules.flatMap(m => {
+    const langs = ["fr", "en"];  // minimum required
+    return langs.map(lang => ({
+      moduleCode: m.code,
+      language: lang,
+      label: lang === master.metadata.language ? (m.name || m.code) : m.code,
+      description: lang === master.metadata.language ? m.description : ""
+    }));
+  }),
+
+  permissions: master.cadrage.applicationRoles.flatMap(role =>
+    master.modules.map(m => ({
+      role: role.role,
+      module: m.code,
+      pattern: role.permissionPattern.replace('*', `${m.code.toLowerCase()}.*`),
+      level: role.level
+    }))
+  ),
+
+  rolePermissions: master.cadrage.applicationRoles.map(role => ({
+    role: role.role,
+    level: role.level,
+    permissions: master.modules.map(m => `business.${master.metadata.application.toLowerCase()}.${m.code.toLowerCase()}.${
+      role.level === 'admin' ? '*' :
+      role.level === 'manager' ? 'read,create,update,validate' :
+      role.level === 'contributor' ? 'read,create,update' : 'read'
+    }`)
+  })),
+
+  permissionConstants: master.modules.flatMap(m =>
+    ['Read', 'Create', 'Update', 'Delete', 'Validate', 'Export'].map(action => ({
+      module: m.code,
+      action: action,
+      constant: `${master.metadata.application}${m.code}${action}`,
+      path: `business.${master.metadata.application.toLowerCase()}.${m.code.toLowerCase()}.${action.toLowerCase()}`
+    }))
+  )
+};
+
+ba-writer.enrichSection({
+  featureId: {feature_id},
+  section: "seedDataCore",
+  data: seedDataCore
+})
+```
+
+**POST-CHECK (non-blocking):**
+```
+IF seedDataCore.navigationModules.length !== master.modules.length:
+  WARNING: seedDataCore has ${seedDataCore.navigationModules.length} nav modules but ${master.modules.length} modules exist
+IF seedDataCore.permissions.length === 0:
+  WARNING: seedDataCore has 0 permissions — applicationRoles may be missing
+```
+
+#### 7c. Master Handoff (after ALL modules written + seedDataCore generated)
 
 ```
 ba-writer.enrichSection({
@@ -329,7 +426,7 @@ ba-writer.enrichSection({
 })
 ```
 
-#### 7c. Final Verification (BLOCKING)
+#### 7d. Final Verification (BLOCKING)
 
 ```
 count = 0

package/templates/skills/business-analyse/steps/step-05b-deploy.md

@@ -326,6 +326,37 @@ After writing the HTML file, verify:
    fi
    ```
 
+7. **WIREFRAME KEY ALIGNMENT** — wireframe keys MUST match module codes exactly
+   ```
+   FOR each module in FEATURE_DATA.modules:
+     moduleCode = module.code  (e.g., "GestionTemps")
+     IF EMBEDDED_ARTIFACTS.wireframes[moduleCode] is undefined OR empty:
+       BLOCKING_ERROR("Wireframe key mismatch: module code '${moduleCode}' not found in EMBEDDED_ARTIFACTS.wireframes")
+       BLOCKING_ERROR("Available wireframe keys: ${Object.keys(EMBEDDED_ARTIFACTS.wireframes).join(', ')}")
+       → FIX: Rename the wireframe key to match module.code exactly
+   ```
+   > **Why this matters:** The HTML renders wireframes via `EMBEDDED_ARTIFACTS.wireframes[code]`. If the key doesn't match the module code (e.g., "TimeTracking" vs "GestionTemps"), the wireframes tab shows "Aucune maquette disponible" even though data exists.
+
+8. **MODULE COMPLETENESS** — every module must have spec data AND wireframes in HTML
+   ```
+   FOR each module in master.modules[]:
+     IF FEATURE_DATA.moduleSpecs[module.code] is undefined:
+       BLOCKING_ERROR("Module '${module.code}' missing from FEATURE_DATA.moduleSpecs")
+     IF EMBEDDED_ARTIFACTS.wireframes[module.code] is undefined:
+       BLOCKING_ERROR("Module '${module.code}' missing from EMBEDDED_ARTIFACTS.wireframes")
+     IF module.featureJsonPath is null:
+       BLOCKING_ERROR("Module '${module.code}' has no per-module feature.json (featureJsonPath is null)")
+
+   expectedModules = master.modules.map(m => m.code).sort()
+   specModules = Object.keys(FEATURE_DATA.moduleSpecs).sort()
+   wireframeModules = Object.keys(EMBEDDED_ARTIFACTS.wireframes).sort()
+
+   IF expectedModules.join(',') !== specModules.join(','):
+     BLOCKING_ERROR("Module mismatch: expected [${expectedModules}] but moduleSpecs has [${specModules}]")
+   IF expectedModules.join(',') !== wireframeModules.join(','):
+     BLOCKING_ERROR("Module mismatch: expected [${expectedModules}] but wireframes has [${wireframeModules}]")
+   ```
+
 **IF ANY CHECK FAILS → DO NOT PROCEED. Fix the data mapping and regenerate.**
 
 ---
@@ -366,7 +397,10 @@ Effort:    {total_days} days ({total_hours} hours)
 
   5. Une fois validé, lancer le développement:
 
-     /ralph-loop -r
+     /ralph-loop
+
+     Note: /ralph-loop -r sert UNIQUEMENT à reprendre une boucle interrompue.
+           Après un /business-analyse, toujours utiliser /ralph-loop (sans -r).
 
 ═══════════════════════════════════════════════════════════════
 ```

package/templates/skills/business-analyse/steps/step-05c-ralph-readiness.md

@@ -607,7 +607,10 @@ Next Steps:
 
   3. When ready, launch development:
 
-     /ralph-loop -r
+     /ralph-loop
+
+     Note: Use /ralph-loop -r ONLY to resume an interrupted loop.
+           After a fresh /business-analyse, always use /ralph-loop (without -r).
 
   4. Ralph-loop will:
      - Process modules in topological order: [{module list}]

package/templates/skills/business-analyse/steps/step-06-review.md

@@ -262,7 +262,8 @@ Artifacts regenerated:
 
 NEXT STEPS:
 1. Open the new ba-interactive.html to verify corrections
-2. Run /ralph-loop -r to start development from the updated analysis
+2. Run /ralph-loop to start development from the updated analysis
+   (Use /ralph-loop -r ONLY to resume an interrupted loop)
 ═══════════════════════════════════════════════════════════════
 ```
 

package/templates/skills/business-analyse/templates/tpl-handoff.md

@@ -12,7 +12,7 @@
 > **Version:** {version}
 > **Validated Specs:** feature.json (validation.decision = APPROVED)
 > **Source:** `docs/business/{app}/{module}/business-analyse/v{version}/feature.json`
-> **Implementation:** `/ralph-loop -r`
+> **Implementation:** `/ralph-loop`
 
 ## DEVELOPER INSTRUCTIONS
 
@@ -20,9 +20,10 @@ This document is a self-contained prompt for Claude Code.
 
 **Lancement:**
 ```
-/ralph-loop -r
+/ralph-loop
 ```
-> Pre-generated `.ralph/prd.json` with atomic task breakdown.
+> Ralph-loop auto-detects BA artifacts and derives PRD task breakdowns.
+> Use `/ralph-loop -r` only to resume an interrupted loop.
 
 ---
 
@@ -178,6 +179,6 @@ From: `feature.specification.seedDataCore` (5 core files), `feature.specificatio
 
 **Lancement:**
 ```bash
-/ralph-loop -r
+/ralph-loop
 ```
 ```

package/templates/skills/business-analyse/templates/tpl-launch-displays.md

@@ -34,7 +34,10 @@ Effort:    {total_days} days ({total_hours} hours)
   3. Si retours --> relancer /business-analyse pour une nouvelle itération
   4. Une fois validé, lancer le développement:
 
-     /ralph-loop -r
+     /ralph-loop
+
+     Note: /ralph-loop -r sert UNIQUEMENT à reprendre une boucle interrompue.
+           Après un /business-analyse, toujours utiliser /ralph-loop (sans -r).
 
 ═══════════════════════════════════════════════════════════════
 ```

package/templates/skills/business-analyse/templates-frd.md

@@ -353,7 +353,7 @@ Feature: {FEAT-XXX} {Feature Name}
 > **Module:** business/{application}/{module}
 > **Version:** 1.0
 > **Validated Specs:** Specification v1.0 (validation.json)
-> **Implementation:** `/ralph-loop -r`
+> **Implementation:** `/ralph-loop`
 
 ## DEVELOPER INSTRUCTIONS
 
@@ -361,9 +361,10 @@ This document is a self-contained prompt for Claude Code.
 
 **Lancement:**
 ```
-/ralph-loop -r
+/ralph-loop
 ```
-> Pre-generated `.ralph/prd.json` with atomic task breakdown.
+> Ralph-loop auto-detects BA artifacts and derives PRD task breakdowns.
+> Use `/ralph-loop -r` only to resume an interrupted loop.
 
 ---
 
@@ -459,7 +460,7 @@ FRONTEND:
 
 **Lancement:**
 ```bash
-/ralph-loop -r
+/ralph-loop
 ```
 ```
 

package/templates/skills/gitflow/references/start-local-config.md

@@ -50,11 +50,14 @@ EOF
 }
 ```
 
-## 7b. Frontend: .env.local + npm script
+## 7b. Frontend: .env.standalone + npm script
+
+> **IMPORTANT**: Vite 7+ forbids `"local"` as a mode name (conflicts with `.env.local` suffix).
+> The Vite mode is `standalone`, but the npm script stays `local` for user convenience.
 
 ```bash
 [ -n "$WEB_DIR" ] && [ -f "$WEB_DIR/package.json" ] && {
-  cat > "$WEB_DIR/.env.local" << EOF
+  cat > "$WEB_DIR/.env.standalone" << EOF
 VITE_API_URL=http://localhost:${API_PORT}
 VITE_APP_ENV=local
 VITE_DEBUG=true
@@ -66,7 +69,7 @@ EOF
       const fs = require('fs');
       const pkg = JSON.parse(fs.readFileSync('$WEB_DIR/package.json', 'utf8'));
       if (!pkg.scripts.local) {
-        pkg.scripts.local = 'vite --mode local --port ${WEB_PORT}';
+        pkg.scripts.local = 'vite --mode standalone --port ${WEB_PORT}';
         fs.writeFileSync('$WEB_DIR/package.json', JSON.stringify(pkg, null, 2) + '\n');
       }
     "

package/templates/skills/gitflow/steps/step-start.md

@@ -190,7 +190,7 @@ fi
 See [references/start-local-config.md](../references/start-local-config.md) for the full configuration:
 - **Port generation:** Unique ports per branch (API: 5200+, Web: 5300+) based on branch name hash
 - **7a. Backend:** `appsettings.Local.json` (DB connection, SmartStack config, Kestrel port)
-- **7b. Frontend:** `.env.local` + `npm run local` script
+- **7b. Frontend:** `.env.standalone` + `npm run local` script (Vite mode=standalone, not "local" which conflicts with .env.local in Vite 7+)
 - **7c. Backend:** `launchSettings.json` Local profile with unique port
 - **7d. Summary:** Display configured DB name, API port, Web port
 
@@ -276,7 +276,7 @@ See [references/start-local-config.md](../references/start-local-config.md) for
 - Worktree set up (if enabled)
 - Backend local config created: `appsettings.Local.json` (if .NET API detected)
 - Backend launch profile created: `launchSettings.json` Local profile with unique port (if .NET API detected)
-- Frontend local config created: `.env.local` + `npm run local` script (if web project detected)
+- Frontend local config created: `.env.standalone` + `npm run local` script (if web project detected)
 - Ports synchronized between backend and frontend (unique per branch)
 - State stored for subsequent steps