@atlashub/smartstack-cli 4.49.0 → 4.51.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "4.49.0",
+  "version": "4.51.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/skills/apex/SKILL.md

@@ -171,6 +171,36 @@ Execute incremental SmartStack development using the APEX methodology. This skil
 
 </execution_rules>
 
+<execution_guarantee>
+
+## Execution Guarantee (CRITICAL — read before ANY step)
+
+> **The user is NOT watching. There is NOBODY to answer your questions. Stopping is a FAILURE.**
+
+When APEX runs (especially in `-d` delegate mode or `-a` auto mode), the execution is **fully autonomous**. The user has launched the command and walked away. Any pause, question, or numbered option list is a **dead end** — nobody will respond.
+
+**YOU MUST NOT:**
+- Stop to ask the user a question between layers
+- Present numbered options ("Would you like to: 1. Continue... 2. Generate... 3. Stop...")
+- Pause between layers to summarize progress and wait for confirmation
+- Stop because the work seems "large" or "complex" — that is expected
+- Add "Let me know if you want me to continue" at any point
+
+**YOU MUST:**
+- After Layer N completes, **IMMEDIATELY** load the next sub-step file. No pause, no summary, no question.
+- Execute the full pipeline: Layer 0 → Layer 1 → Layer 2 → Layer 3 → Layer 4 → step-04, with **ZERO pauses** between layers
+- Treat each "Load `steps/step-03X-...md`" instruction as a **mandatory immediate action**, not a suggestion
+- Continue even if a layer produced warnings (only a build gate failure after max retries is a valid stop)
+
+**The ONLY valid reasons to stop:**
+1. A build gate fails after maximum retries (3 attempts)
+2. ALL layers are completed and step-04 (eXamine) is done
+3. The user presses Ctrl+C
+
+**Anything else — including "being helpful" by asking — is a VIOLATION of the execution guarantee.**
+
+</execution_guarantee>
+
 <error_handling>
 
 ## Error Handling Strategy

package/templates/skills/apex/steps/step-03-execute.md

@@ -65,6 +65,13 @@ BEFORE starting Layer N:
 
 ## Layer Dispatch
 
+> **CRITICAL RULES — LAYER EXECUTION GUARANTEE**
+>
+> - **NEVER** stop between layers. NEVER ask the user. NEVER present numbered options between layers.
+> - The pipeline is sequential and mandatory: **0 → 1 → 2 → 3 → 4 → step-04**, with **ZERO pauses**.
+> - After each sub-step completes, IMMEDIATELY load the next one. No summary, no confirmation request.
+> - Stopping between layers is a **VIOLATION** of the execution guarantee defined in SKILL.md.
+
 Load each sub-step sequentially:
 
 | Layer | Sub-step | Content |

package/templates/skills/apex/steps/step-03a-layer0-domain.md

@@ -136,6 +136,9 @@ feat({module}): [domain+infra] {short description}
 
 ---
 
-## NEXT SUB-STEP
+## NEXT SUB-STEP (MANDATORY — IMMEDIATE)
+
+> **DO NOT STOP.** DO NOT ask the user. DO NOT present options. IMMEDIATELY load the next sub-step.
+> Stopping here is a VIOLATION of the execution guarantee.
 
 Load `steps/step-03b-layer1-seed.md`

package/templates/skills/apex/steps/step-03b-layer1-seed.md

@@ -254,6 +254,9 @@ feat({module}): [seed] navigation, permissions, roles
 
 ---
 
-## NEXT SUB-STEP
+## NEXT SUB-STEP (MANDATORY — IMMEDIATE)
+
+> **DO NOT STOP.** DO NOT ask the user. DO NOT present options. IMMEDIATELY load the next sub-step.
+> Stopping here is a VIOLATION of the execution guarantee.
 
 Load `steps/step-03c-layer2-backend.md`

package/templates/skills/apex/steps/step-03c-layer2-backend.md

@@ -348,6 +348,9 @@ test({module}): backend unit and integration tests
 
 ---
 
-## NEXT SUB-STEP
+## NEXT SUB-STEP (MANDATORY — IMMEDIATE)
+
+> **DO NOT STOP.** DO NOT ask the user. DO NOT present options. IMMEDIATELY load the next sub-step.
+> Stopping here is a VIOLATION of the execution guarantee.
 
 Load `steps/step-03d-layer3-frontend.md`

package/templates/skills/apex/steps/step-03d-layer3-frontend.md

@@ -329,6 +329,9 @@ test({module}): frontend form tests
 
 ---
 
-## NEXT SUB-STEP
+## NEXT SUB-STEP (MANDATORY — IMMEDIATE)
+
+> **DO NOT STOP.** DO NOT ask the user. DO NOT present options. IMMEDIATELY load the next sub-step.
+> Stopping here is a VIOLATION of the execution guarantee.
 
 Load `steps/step-03e-layer4-devdata.md`

package/templates/skills/business-analyse/patterns/suggestion-catalog.md

@@ -27,6 +27,7 @@ Suggests companion modules based on primary module type:
 | **Notifications** | notification, alert, email, message, broadcast | Templates, Channels, Scheduling, Preferences | Notification systems need template management, multi-channel support, scheduling |
 | **Reporting** | report, dashboard, analytics, BI, metrics | Dashboards, Exports, Scheduling, AlertRules | Reporting needs visualization, scheduled distribution, and data export |
 | **API Management / Integrations** | api, external, integration, webhook, export, data-export, machine-to-machine | ExternalApps, DataExportEndpoints, ExportAccess, AuditLogs, ApiKeys | API platforms need app registration, key management, granular endpoint access, rate limiting, and audit logging |
+| **Client Portal** | portal, external, client, fournisseur, partenaire, tiers | MyRequests, ClientDashboard, PortalNotifications | Les utilisateurs externes ont besoin de vues self-service, suivi de statut et soumission limitée |
 
 ---
 
@@ -48,6 +49,7 @@ Suggests standard sections based on detected conditions:
 | **Report generation** | Reporting Engine | Automated business reporting | Add section with template library, scheduling, distribution |
 | **External integrations** | Integration Layer | System-to-system communication | Add section with API specifications, webhook handling, sync strategy |
 | **Regulatory compliance** | Compliance & Audit | Legal/industry requirements | Add section with audit logging, data retention, retention periods |
+| **Utilisateurs externes / portail détecté** | Sections portail client | Les utilisateurs externes ont besoin d'un espace dédié simplifié | Pour chaque module "shared" : suggérer section portal-specific (ex: `my-requests`, `portal-dashboard`) avec permissions read-only ou write limitée. Pour modules "external" : s'assurer que les sections ont une UX adaptée portail (navigation simplifiée, pas de fonctions admin). |
 
 ---
 

package/templates/skills/business-analyse/questionnaire/02-stakeholders-scope.md

@@ -88,6 +88,7 @@
 | Question | Si la réponse est vague | Relance recommandée |
 |----------|------------------------|---------------------|
 | Q2.1 (utilisateurs) | Un seul type mentionné | "Pensez aux différents moments de la journée : qui saisit ? Qui consulte les rapports ? Qui gère les cas particuliers ?" |
+| Q2.1 (utilisateurs) | Utilisateurs hors entreprise mentionnés (clients, fournisseurs, partenaires) | "Ces utilisateurs externes accéderont-ils via un espace dédié (portail) ou la même interface que vos employés ?" |
 | Q2.5 (tâches) | Tâches génériques | "Quand il arrive le matin et ouvre le système, quelle est sa première action ?" |
 | Q2.9 (restrictions) | Réponse ambiguë | "Un employé voit-il les données salariales ? Un manager voit-il uniquement son équipe ou toute l'entreprise ?" |
 | Q2.13 (indispensable) | Tout est indispensable | "Si vous ne pouviez garder que 3 fonctionnalités pour un premier lancement, lesquelles ?" |
@@ -103,6 +104,7 @@
 | Tout est vital (> 10 vitaux) | Classification non réfléchie | Appliquer le test de classification : "Si on enlevait X, le système aurait-il encore de la valeur ?" |
 | Aucune exclusion identifiée | Périmètre non borné | "Y a-t-il des aspects qui relèvent d'un autre projet ou d'une version future ?" |
 | Parcours linéaire sans alternative | Seul le cas idéal est décrit | "Que se passe-t-il à l'étape X si la condition Y n'est pas remplie ?" |
+| "Nos clients doivent pouvoir..." ou "Les fournisseurs voient..." | Utilisateurs externes accédant au système | Déclencher détection portail : classifier les profils en interne/externe. SmartStack gère le déploiement multi-tenant automatiquement. |
 
 ---
 

package/templates/skills/business-analyse/schemas/application-schema.json

@@ -66,6 +66,12 @@
           "type": "string",
           "description": "Lucide icon name for application navigation entry (e.g., users, shopping-cart). Confirmed in step-02."
         },
+        "portalMode": {
+          "type": "string",
+          "enum": ["internal-only", "portal-only", "dual"],
+          "default": "internal-only",
+          "description": "Whether the app serves internal users, external portal users, or both"
+        },
         "workflow": {
           "type": "object",
           "description": "Iterative module loop state",
@@ -126,7 +132,12 @@
               "involvement": { "type": "string", "enum": ["approver", "decision-maker", "consulted", "informed", "end-user"] },
               "tasks": { "type": "array", "items": { "type": "string" } },
               "frequency": { "type": "string" },
-              "painPoints": { "type": "array", "items": { "type": "string" } }
+              "painPoints": { "type": "array", "items": { "type": "string" } },
+              "audience": {
+                "type": "string",
+                "enum": ["internal", "external", "shared"],
+                "description": "Whether this stakeholder is internal, external portal user, or both"
+              }
             }
           }
         },
@@ -204,6 +215,11 @@
                 "type": "array",
                 "items": { "type": "string" },
                 "description": "Anticipated resources (Level 5) for this requirement — e.g., user-grid, user-form, user-card"
+              },
+              "audience": {
+                "type": "string",
+                "enum": ["internal", "external", "shared"],
+                "description": "Target audience. Only set when portalMode is 'dual'."
               }
             }
           }
@@ -257,6 +273,11 @@
             "type": "string",
             "enum": ["simple", "medium", "complex"]
           },
+          "audience": {
+            "type": "string",
+            "enum": ["internal", "external", "shared"],
+            "description": "Target audience. Derived from coverage matrix."
+          },
           "anticipatedSections": {
             "type": "array",
             "description": "Anticipated sections (Level 4) with their resources (Level 5), from cadrage coverage matrix",
@@ -266,6 +287,20 @@
               "properties": {
                 "code": { "type": "string", "description": "Section code (e.g., list, detail, create, edit, dashboard)" },
                 "description": { "type": "string" },
+                "sectionType": {
+                  "type": "string",
+                  "enum": ["primary", "functional", "view", "embedded"],
+                  "description": "Section classification: primary (menu entry), functional (independent), view (sub-page of parent), embedded (widget in parent)"
+                },
+                "permissionMode": {
+                  "type": "string",
+                  "enum": ["crud", "custom", "read-only", "inherit"],
+                  "description": "Permission model: crud (standard CRUD), custom (section-specific), read-only, inherit (from parent)"
+                },
+                "parentSectionCode": {
+                  "type": ["string", "null"],
+                  "description": "Parent section code for view/embedded sections (e.g., 'list'). Null for primary/functional sections."
+                },
                 "resources": {
                   "type": "array",
                   "items": { "type": "string" },

package/templates/skills/business-analyse/schemas/sections/specification-schema.json

@@ -516,6 +516,20 @@
         "required": ["code", "labels", "route", "permission", "wireframe", "useCases", "resources"],
         "properties": {
           "code": { "type": "string", "description": "Section code (kebab-case: list, detail, dashboard, approve, import, etc.)" },
+          "sectionType": {
+            "type": "string",
+            "enum": ["primary", "functional", "view", "embedded"],
+            "description": "Section classification: primary (menu entry), functional (independent), view (sub-page of parent), embedded (widget in parent)"
+          },
+          "permissionMode": {
+            "type": "string",
+            "enum": ["crud", "custom", "read-only", "inherit"],
+            "description": "Permission model: crud (standard CRUD), custom (section-specific), read-only, inherit (from parent)"
+          },
+          "parentSectionCode": {
+            "type": ["string", "null"],
+            "description": "Parent section code for view/embedded sections (e.g., 'list'). Null for primary/functional sections."
+          },
           "labels": {
             "type": "object",
             "properties": {
@@ -531,6 +545,11 @@
           "wireframe": { "type": "string", "description": "Reference to uiWireframes[].screen" },
           "useCases": { "type": "array", "items": { "type": "string" } },
           "businessRules": { "type": "array", "items": { "type": "string" } },
+          "audience": {
+            "type": "string",
+            "enum": ["internal", "external", "shared"],
+            "description": "Target audience. Inherited from module unless overridden."
+          },
           "resources": {
             "type": "array",
             "description": "Level 5 (Resource) components within this section",

package/templates/skills/business-analyse/steps/step-00-init.md

@@ -122,10 +122,10 @@ existing_projects: array of { projectName, projectId, applications[], version }
 ## Step 3b: Early Multi-Application Detection from Prompt (NEW)
 
 > **Detect multi-app structure BEFORE asking for a single application name.**
-> When the user's prompt explicitly describes multiple applications, we must recognize this immediately
-> and set `workflow.mode = "project"` to avoid doing cadrage for a single app.
+> When the user's prompt describes multiple applications or spans multiple business domains,
+> we must recognize this immediately and set `workflow.mode = "project"` to avoid doing cadrage for a single app.
 
-**Detection patterns (ANY match = multi-app detected):**
+### Tier 1 — Explicit patterns (ANY match = multi-app detected)
 
 French patterns:
 - "une application X ... une application Y" (two occurrences of "une application")
@@ -138,30 +138,65 @@ English patterns:
 - "application #1: ... application #2: ..." (numbered)
 - "first app ... second app"
 
-If ANY of these patterns is found in `{feature_description}`, set `isMultiApp = true`.
+If ANY of these patterns is found in `{feature_description}`:
+→ `isMultiApp = true`, `detectionTier = "explicit"`
 
-**IF multi-app detected:**
+### Tier 2 — Domain diversity analysis (when Tier 1 does not match)
 
-1. Extract candidate applications from the prompt:
+ULTRATHINK: Analyze `{feature_description}` to extract distinct business domains.
 
-**Extraction algorithm (3 steps):**
+**Definition:** A "domain" is an autonomous business perimeter with its own entities and processes (e.g., HR, CRM, Finance, Projects, Sales, Inventory).
+
+**Algorithm:**
+1. List all business domains mentioned or implied in the description
+2. Classify each domain:
+   - **DISTINCT** — has its own entities, processes, and lifecycle (e.g., HR vs CRM)
+   - **RELATED** — is a sub-domain of another (e.g., Payroll is a sub-domain of HR)
+3. Count DISTINCT domains only
+
+**Threshold:** 2+ DISTINCT domains → `isMultiApp = true`, `detectionTier = "domain-diversity"`
+
+**False positive protection:**
+- "RH complet avec employés, congés, paie, pointage" = 1 domain (HR) with 4 modules, NOT 4 domains
+- "HR and Payroll management" = 1 domain (HR) with 2 modules — Payroll is RELATED to HR
+- "gestion commerciale avec devis, commandes et facturation" = 1 domain (Sales) with 3 modules
+- Only count as DISTINCT when domains have genuinely independent entity models and processes
+
+### Extraction algorithm (depends on detection tier)
+
+**IF Tier 1 (explicit):**
 
 1. **Identify boundaries:** Split the prompt at each "une application" / "an application" occurrence. Each block = one candidate.
 2. **Extract per candidate:** For each block, derive `name` (application name), `description` (summary of purpose), and `modules[]` (listed modules/features).
-   - Example result: `[{ name: "RH", description: "gestion des employes, conges, temps", modules: ["Employes", "Conges", "Temps"] }, ...]`
+   - Example: `[{ name: "RH", description: "gestion des employés, congés, temps", modules: ["Employés", "Congés", "Temps"] }, ...]`
 3. **Detect shared modules:** Collect all module names across all candidates. Any module appearing in more than one candidate is a shared module.
    - Example: `sharedModules = ["Temps"]` (appears in both RH and Projet)
 
-3. Display detection result and confirm:
+**IF Tier 2 (domain-diversity):**
+
+1. Each DISTINCT domain = 1 candidate application:
+   - `name` = short domain label (e.g., "RH", "CRM", "Finance")
+   - `description` = user's expressed need for that domain
+   - `modules[]` = sub-functionalities mentioned (can be empty → "(à définir au cadrage)")
+2. Group RELATED sub-domains under their parent DISTINCT domain as modules
+3. **Detect shared modules:** Same logic as Tier 1 — modules appearing in multiple candidates
+
+### Confirmation dialogue
+
+Display detection result:
 
 ```
-{language == "fr"
-  ? "### Détection multi-application\n\nJ'ai détecté **{candidates.length} applications** dans votre description :"
-  : "### Multi-application detection\n\nI detected **{candidates.length} applications** in your description:"}
+{detectionTier == "explicit"
+  ? (language == "fr"
+    ? "### Détection multi-application\n\nJ'ai détecté **{candidates.length} applications** dans votre description :"
+    : "### Multi-application detection\n\nI detected **{candidates.length} applications** in your description:")
+  : (language == "fr"
+    ? "### Détection multi-application\n\nVotre description couvre **{candidates.length} domaines métier distincts**. Chaque domaine pourrait constituer une application séparée :"
+    : "### Multi-application detection\n\nYour description covers **{candidates.length} distinct business domains**. Each domain could be a separate application:")}
 
 | # | Application | Modules identifiés |
 |---|-------------|-------------------|
-{for each candidate: index | name | modules.join(", ")}
+{for each candidate: index | name | modules.join(", ") || "(à définir au cadrage)"}
 
 {sharedModules.length > 0
   ? "⚠️ **Modules partagés détectés :** {sharedModules.join(', ')} — ces modules apparaissent dans plusieurs applications. Ils pourraient constituer une application transversale dédiée."
@@ -177,6 +212,8 @@ options:
     description: "{language == 'fr' ? 'Créer un projet avec les applications identifiées' : 'Create a project with the identified applications'}"
   - label: "{language == 'fr' ? 'Extraire les modules partagés' : 'Extract shared modules'}" (only if sharedModules.length > 0)
     description: "{language == 'fr' ? 'Créer une application dédiée pour {sharedModules.join(', ')} ({candidates.length + 1} applications au total)' : 'Create a dedicated app for {sharedModules.join(', ')} ({candidates.length + 1} total)'}"
+  - label: "{language == 'fr' ? 'Regrouper certains domaines' : 'Regroup some domains'}" (only if detectionTier == "domain-diversity")
+    description: "{language == 'fr' ? 'Fusionner des domaines en moins d\\'applications' : 'Merge domains into fewer applications'}"
   - label: "{language == 'fr' ? 'Application unique' : 'Single application'}"
     description: "{language == 'fr' ? 'Tout regrouper en une seule application avec plusieurs modules' : 'Group everything into one application with multiple modules'}"
 ```
@@ -193,6 +230,19 @@ shared_modules_extracted: boolean  # true if user chose extraction
 → Skip step 4 (application name) — applications will be confirmed in step-01-cadrage
 → Continue to step 5 (language selection)
 
+**IF "Regrouper certains domaines" (Tier 2 only):**
+
+Ask via AskUserQuestion:
+```
+question: "{language == 'fr' ? 'Comment souhaitez-vous regrouper ces domaines ? (ex: \"RH + Paie ensemble, CRM seul\")' : 'How would you like to regroup these domains? (e.g., \"HR + Payroll together, CRM alone\")'}"
+header: "Regroupement"
+```
+
+Process user response:
+1. Parse the grouping instructions (natural language)
+2. Rebuild `candidate_applications` based on the specified groups
+3. Re-display the confirmation dialogue with the updated candidates
+
 **IF "Application unique":**
 
 ```yaml
@@ -201,7 +251,7 @@ workflow_mode: "application"
 
 → Continue to step 4 normally
 
-**IF no multi-app patterns detected:**
+**IF no multi-app detected (neither Tier 1 nor Tier 2):**
 → Continue to step 4 normally
 
 ## Step 4: Determine Application Name

package/templates/skills/business-analyse/steps/step-01-cadrage.md

@@ -239,6 +239,44 @@ Ask in 1-2 batches. After each batch:
 - If "no restrictions" → probe: "Are there sensitive data (salary, contracts, personal info) that should be restricted to specific roles?"
 - If tasks are generic → ask for a concrete scenario: "Walk me through a typical day"
 
+#### 4b-bis. Détection Portail Client (ULTRATHINK — après batch stakeholders)
+
+Analyser les réponses stakeholders pour signaux d'utilisateurs externes :
+
+```
+EXTERNAL_SIGNALS = ["client", "customer", "fournisseur", "supplier", "partenaire",
+  "partner", "portail", "portal", "externe", "external", "tiers", "third-party",
+  "organisation cliente"]
+```
+
+SI un profil stakeholder match EXTERNAL_SIGNALS :
+  → Stocker dans `{pre_analysis}`: `_portalDetected: true`
+  → Poser la question via AskUserQuestion :
+
+```
+question: "{language == 'fr'
+  ? 'J\'ai détecté des utilisateurs externes ({profiles}). Votre application comportera-t-elle un portail client en plus de la partie interne ?'
+  : 'I detected external users ({profiles}). Will your application include a client portal in addition to the internal part?'}"
+header: "Portail client"
+options:
+  - label: "{language == 'fr' ? 'Oui, portail + interne' : 'Yes, portal + internal'}"
+    description: "{language == 'fr' ? 'L\'application servira des utilisateurs internes ET externes via un portail dédié' : 'The app will serve internal AND external users via a dedicated portal'}"
+  - label: "{language == 'fr' ? 'Non, interne uniquement' : 'No, internal only'}"
+    description: "{language == 'fr' ? 'Seuls les employés internes utiliseront l\'application' : 'Only internal employees will use the application'}"
+  - label: "{language == 'fr' ? 'Non, portail uniquement' : 'No, portal only'}"
+    description: "{language == 'fr' ? 'L\'application est exclusivement destinée aux utilisateurs externes' : 'The application is exclusively for external users'}"
+```
+
+| Réponse | Action |
+|---------|--------|
+| **Oui, portail + interne** | `_portalMode = "dual"` → Follow-up : classifier chaque stakeholder comme `audience: "internal" \| "external" \| "shared"` |
+| **Portail uniquement** | `_portalMode = "portal-only"` |
+| **Interne uniquement** | `_portalMode = "internal-only"` (défaut, pas d'action supplémentaire) |
+
+> **Note SmartStack :** Le déploiement multi-tenant est géré automatiquement par SmartStack. La partie interne et la partie portail seront déployées sur des tenants séparés.
+
+SI aucun profil ne match EXTERNAL_SIGNALS → `_portalMode = "internal-only"` (défaut silencieux, rien à demander).
+
 #### 4c. Functional Scope (ALWAYS — from `questionnaire/02-stakeholders-scope.md`)
 
 **Mandatory minimum:** Q2.13 (in-scope), Q2.15 (exclusions), Q2.16 (main journey).
@@ -596,6 +634,14 @@ BEFORE transitioning to step-02:
    - List anticipated resources (Level 5) for each section
    - List detail page tabs — for entities accessible via click from `list`
 
+   **SI `_portalMode === "dual"` :**
+   - Chaque entrée `coverageMatrix` reçoit `audience: "internal" | "external" | "shared"`
+   - Règles de dérivation :
+     - Items mentionnés uniquement par stakeholders internes → `"internal"`
+     - Items mentionnés uniquement par stakeholders externes → `"external"`
+     - Items mentionnés par les deux ou cross-cutting → `"shared"`
+   - Afficher colonne "Audience" dans le tableau de la matrice
+
 4. **RECONCILIATION CHECK (MANDATORY — BLOCKING):**
 
    > **Every explicitly requested item MUST appear in the coverage matrix.**
@@ -641,12 +687,13 @@ ba-writer.enrichSection({
   subsection: "cadrage.json",
   data: {
     metadata: {
-      tablePrefix: "{from Phase 5, section 6b — validated prefix, e.g., rh_}"
+      tablePrefix: "{from Phase 5, section 6b — validated prefix, e.g., rh_}",
+      portalMode: "{_portalMode || 'internal-only'}"
     },
     problem: {from Phase 3, section 4a — Q1.1 answer or refined problem},
     asIs: {from Phase 3, section 4a — Q1.4 answer},
     toBe: {from Phase 3, section 4a — Q1.8 answer},
-    stakeholders: [{from Phase 3, section 4b}],
+    stakeholders: [{from Phase 3, section 4b — each with audience: "internal"|"external"|"shared" if portalMode is "dual"}],
     globalScope: {
       inScope: [{from Phase 3, section 4c + Phase 4 accepted suggestions + coverage matrix}],
       outOfScope: [{from Phase 3, section 4c — Q2.15 exclusions}]

package/templates/skills/business-analyse/steps/step-02-structure.md

@@ -70,6 +70,9 @@ For each module:
   - Description
   - FeatureType (data-centric | workflow | reporting | integration | full-module)
   - Entities (preliminary list)
+  - Audience ("internal" | "external" | "shared") — if portalMode = "dual"
+    → Derived from coverageMatrix: if ALL items of the module are internal → "internal",
+      if ALL external → "external", else → "shared"
 ```
 
 ### 3. Section & Resource Anticipation
@@ -89,18 +92,20 @@ For each section:
 
 **Section classification rules:**
 
-| sectionType | permissionMode | When to use | Examples |
-|---|---|---|---|
-| `primary` | `crud` | Main entry point of the module, visible in menu | list |
-| `functional` | `crud` or `custom` | Independent functional section with own access control | approve, import, planning |
-| `view` | `inherit` | Subordinate view reached from a primary section | detail, edit |
-| `embedded` | `read-only` | Widget or tab embedded in another section | dashboard (when embedded in module) |
+| sectionType | permissionMode | When to use | Parent | Examples |
+|---|---|---|---|---|
+| `primary` | `crud` | Main entry point of the module, visible in menu | none | list |
+| `functional` | `crud` or `custom` | Independent functional section with own access control | none | approve, import, planning |
+| `view` | `inherit` | Sub-page reached from a primary/functional section (e.g., click a row) | `parentSectionCode` | detail, edit |
+| `embedded` | `read-only` | Widget or tab embedded in another section | `parentSectionCode` | dashboard (when embedded in module) |
+
+**Parent-child rule:** `view` and `embedded` sections MUST specify `parentSectionCode` — the code of the section they are reached from. A detail page is NOT a sibling of list; it is a **child** of list (user clicks a row in the list to reach the detail).
 
 Common patterns:
-- **Data-centric module**: list (`primary`/`crud`) + detail (`view`/`inherit`)
-- **Workflow module**: list (`primary`/`crud`) + detail (`view`/`inherit`) + approve (`functional`/`custom`)
-- **Reporting module**: dashboard (`primary`/`read-only`) + detail (`view`/`inherit`)
-- **Full module**: list (`primary`/`crud`) + detail (`view`/`inherit`) + dashboard (`embedded`/`read-only`)
+- **Data-centric**: list (`primary`/`crud`) → detail (`view`/`inherit`, parent: list)
+- **Workflow**: list (`primary`/`crud`) → detail (`view`/`inherit`, parent: list) + approve (`functional`/`custom`)
+- **Reporting**: dashboard (`primary`/`read-only`) → detail (`view`/`inherit`, parent: dashboard)
+- **Full module**: list (`primary`/`crud`) → detail (`view`/`inherit`, parent: list) + dashboard (`embedded`/`read-only`, parent: list)
 
 ### 4. Dependency Graph
 
@@ -139,21 +144,40 @@ For EACH identified element, ask yourself:
 - Does the form need tabs?
 - Are there missing filter components?
 
+**Split audience (if portalMode = "dual"):**
+- Pour chaque module "shared" : le portail voit-il les MÊMES données ou un sous-ensemble filtré ?
+- Y a-t-il des sections qui ne doivent apparaître QUE dans le portail ? (ex: "Mes demandes")
+- Y a-t-il des sections qui ne doivent apparaître QUE en interne ? (ex: reporting admin)
+
 ### 6. Present to User
 
 Display the complete hierarchy for validation:
 
+**Tree nesting rules:**
+- `view` sections are **indented under their parent** (the section they are reached from)
+- `functional` and `primary` sections stay at module level
+- `embedded` sections are indented under their parent section
+- Tabs are indented under detail
+
 ```
 [App: HumanResources]
   ├── [Module: Employees]
-  │   ├── list → SmartTable (employees-grid)
-  │   └── detail → SmartForm (employee-form)
+  │   ├── list (primary/crud) → employees-grid, employees-filters
+  │   │   └── detail (view/inherit) → employee-form
+  │   │       └── Tabs: Infos, Contrats
   ├── [Module: Absences]
-  │   ├── list → SmartTable (absences-grid)
-  │   ├── detail → SmartForm (absence-form)
-  │   └── calendar → SmartKanban (absences-calendar)
+  │   ├── list (primary/crud) → absences-grid, absences-filters
+  │   │   └── detail (view/inherit) → absence-form
+  │   └── calendar (functional) → absences-calendar
   └── [Module: Reports]
-      └── dashboard → SmartDashboard (hr-dashboard)
+      └── dashboard (primary/read-only) → hr-dashboard
+
+IF portalMode = "dual", annotate each module with its audience:
+
+[App: ServiceManagement]
+  ├── [Module: Projects] [partagé]
+  ├── [Module: TimeTracking] [interne]
+  └── [Module: ClientDashboard] [portail]
 ```
 
 Ask: "Does this structure match your vision? Any missing modules, sections, or resources?"
@@ -181,7 +205,7 @@ Write via ba-writer:
       "entities": ["Employee", "Contract"],
       "anticipatedSections": [
         { "code": "list", "label": "Liste", "sectionType": "primary", "permissionMode": "crud", "resources": [{ "code": "employees-grid", "type": "SmartTable" }] },
-        { "code": "detail", "label": "Fiche", "sectionType": "view", "permissionMode": "inherit", "resources": [{ "code": "employee-form", "type": "SmartForm" }] }
+        { "code": "detail", "label": "Fiche", "sectionType": "view", "permissionMode": "inherit", "parentSectionCode": "list", "resources": [{ "code": "employee-form", "type": "SmartForm" }] }
       ]
     }
   ],

package/templates/skills/business-analyse/steps/step-04-consolidate.md

@@ -330,6 +330,175 @@ Les types possibles : `functional`, `business-rule`, `performance`, `security`.
 
 Les critères d'acceptation sont écrits dans `validation.json` au même niveau que `globalRiskAssessment`.
 
+### 7ter. Naming Audit (MANDATORY)
+
+> **Challenge all names before final approval.** Every code, label, and route generated
+> during the BA must be reviewed for coherence, convention compliance, and clarity.
+
+**7ter-a. Collect all names from the BA:**
+
+```javascript
+const namingRegistry = {
+  application: {
+    label: application_name,
+    code: applicationCode,              // PascalCase
+    route: toKebabCase(applicationCode)  // kebab-case
+  },
+  modules: completedModules.map(m => ({
+    label: m.name,
+    code: m.code,                        // PascalCase
+    route: toKebabCase(m.code)           // kebab-case
+  })),
+  entities: completedModules.flatMap(m =>
+    m.entities.map(e => ({
+      name: e.name,                      // PascalCase (C# class name)
+      module: m.code,
+      tableName: e.tableName || pluralize(e.name)  // Plural convention
+    }))
+  ),
+  permissionRoots: [...new Set(
+    permissionPaths.map(p => p.path.split('.').slice(0, 2).join('.'))
+  )]
+};
+```
+
+**7ter-b. Display naming recap table:**
+
+```
+═══════════════════════════════════════════════════════════════
+  NAMING AUDIT — {application_name}
+═══════════════════════════════════════════════════════════════
+
+APPLICATION
+| Label | Code (PascalCase) | Route (kebab-case) |
+|-------|-------------------|--------------------|
+| {application_name} | {applicationCode} | /{route} |
+
+MODULES
+| # | Label | Code (PascalCase) | Route (kebab-case) |
+|---|-------|-------------------|--------------------|
+{for each module: index | label | code | /app-route/module-route}
+
+ENTITIES
+| Entity (PascalCase) | Module | Table (plural) |
+|----------------------|--------|----------------|
+{for each entity: name | module | tableName}
+
+PERMISSION ROOTS
+{for each root: path}
+═══════════════════════════════════════════════════════════════
+```
+
+**7ter-c. Coherence checks:**
+
+```javascript
+const namingIssues = [];
+
+// 1. Duplicate entity names across modules
+const entityNames = namingRegistry.entities.map(e => e.name);
+const duplicates = entityNames.filter((n, i) => entityNames.indexOf(n) !== i);
+if (duplicates.length > 0) {
+  namingIssues.push({ severity: "ERROR", issue: `Duplicate entity names: ${[...new Set(duplicates)].join(', ')}` });
+}
+
+// 2. Module code vs label coherence (code should derive logically from label)
+for (const mod of namingRegistry.modules) {
+  if (!mod.code || mod.code.length < 2) {
+    namingIssues.push({ severity: "ERROR", issue: `Module "${mod.label}" has invalid code: "${mod.code}"` });
+  }
+}
+
+// 3. Permission root alignment with module codes
+for (const root of namingRegistry.permissionRoots) {
+  const [appSegment, moduleSegment] = root.split('.');
+  const matchingModule = namingRegistry.modules.find(m =>
+    m.code.toLowerCase() === moduleSegment.toLowerCase()
+  );
+  if (!matchingModule) {
+    namingIssues.push({ severity: "WARNING", issue: `Permission root "${root}" has no matching module code` });
+  }
+}
+
+// 4. Route collision detection
+const allRoutes = namingRegistry.modules.map(m =>
+  `/${namingRegistry.application.route}/${m.route}`
+);
+const routeDuplicates = allRoutes.filter((r, i) => allRoutes.indexOf(r) !== i);
+if (routeDuplicates.length > 0) {
+  namingIssues.push({ severity: "ERROR", issue: `Route collisions: ${routeDuplicates.join(', ')}` });
+}
+```
+
+**7ter-d. MCP validation:**
+
+```
+mcp__smartstack__validate_conventions({
+  checks: ["tables"],
+  context: {
+    applicationCode: applicationCode,
+    modules: namingRegistry.modules.map(m => m.code),
+    entities: namingRegistry.entities.map(e => e.name)
+  }
+})
+
+→ Merge MCP findings into namingIssues[]
+```
+
+**7ter-e. Present findings and confirm:**
+
+```
+IF namingIssues.length > 0:
+  Display issues table:
+  | # | Severity | Issue |
+  |---|----------|-------|
+  {for each issue}
+```
+
+Ask via AskUserQuestion:
+```
+question: "{language == 'fr'
+  ? 'Validez-vous les noms ci-dessus pour l\\'ensemble de l\\'application ?'
+  : 'Do you approve all the names above for the entire application?'}"
+header: "Naming Audit"
+options:
+  - label: "{language == 'fr' ? 'Approuvé' : 'Approved'}"
+    description: "{language == 'fr' ? 'Tous les noms sont corrects' : 'All names are correct'}"
+  - label: "{language == 'fr' ? 'Renommer certains éléments' : 'Rename some elements'}"
+    description: "{language == 'fr' ? 'Corriger des noms avant de finaliser' : 'Fix names before finalizing'}"
+```
+
+**IF "Renommer certains éléments":**
+
+Ask via AskUserQuestion (open-ended):
+```
+question: "{language == 'fr'
+  ? 'Quels éléments souhaitez-vous renommer ? (ex: \"Module Ventes → Commerce\", \"Entity Invoice → BillingDocument\")'
+  : 'Which elements do you want to rename? (e.g., \"Module Sales → Commerce\", \"Entity Invoice → BillingDocument\")'}"
+header: "Renaming"
+```
+
+Process user response:
+1. Parse rename instructions
+2. Update `applicationCode`, module codes, entity names, permission paths accordingly in JSON files via ba-writer
+3. Re-run 7ter-c and 7ter-d checks on updated names
+4. Re-display the naming recap table for final confirmation
+
+**IF "Approuvé":**
+→ Store naming audit result in `validation.json`:
+```javascript
+ba-writer.enrichSection({
+  featureId: {feature_id},
+  section: "namingAudit",
+  data: {
+    auditedAt: now(),
+    issues: namingIssues,
+    approved: true,
+    renames: []  // or list of applied renames
+  }
+});
+```
+→ Continue to section 8
+
 ### 8. Consolidation Summary Display
 
 ```
@@ -449,6 +618,7 @@ ba-writer.enrichSection({
       `E2E flows: ${e2eFlows.length} identified`,
       `Global risk: ${risks.length > 0 ? 'MEDIUM' : 'LOW'}`,
       `Semantic checks: PASSED`,
+      `Naming audit: ${namingIssues.length} issues found, APPROVED`,
       `Client approval: APPROVED`
     ]
   }
@@ -508,6 +678,7 @@ BA workflow complete. Next steps:
 - ✓ No circular dependencies
 - ✓ Permission coherence validated
 - ✓ Semantic checks: 0 errors
+- ✓ Naming audit completed and approved
 - ✓ Client approval obtained (or auto-approved for single module)
 - ✓ Consolidation section written to validation.json
 - ✓ Status updated to "consolidated"

package/templates/skills/business-analyse-html/html/ba-interactive.html

@@ -2394,6 +2394,13 @@ let data = {{FEATURE_DATA}};
 const ORIGINAL_DATA = JSON.parse(JSON.stringify(data));
 const EMBEDDED_ARTIFACTS = {{EMBEDDED_ARTIFACTS}};
 
+// CRITICAL: Initialize top-level structures FIRST to prevent TypeError crashes
+data.cadrage = data.cadrage || {};
+data.modules = data.modules || [];
+data.dependencies = data.dependencies || [];
+data.handoff = data.handoff || {};
+data.cadrage.stakeholders = data.cadrage.stakeholders || [];
+
 // Initialize applications array (multi-app support)
 data.applications = data.applications || [];
 
@@ -2454,8 +2461,10 @@ data.moduleSpecs = data.moduleSpecs || {};
     if (!data.moduleSpecs[m.code]) {
         data.moduleSpecs[m.code] = { useCases: [], businessRules: [], entities: [], permissions: [], notes: '' };
     }
-    // Ensure anticipatedSections array exists
-    m.anticipatedSections = m.anticipatedSections || [];
+    // Ensure anticipatedSections array exists and normalize strings to objects
+    m.anticipatedSections = (m.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, description: '', resources: [] } : s;
+    });
     m.applicationCode = m.applicationCode || '';
     // Initialize screens array for interface specs
     if (!data.moduleSpecs[m.code].screens) {
@@ -2767,7 +2776,9 @@ function renderModuleNavItem(mod) {
     var ucCount = (spec.useCases || []).length;
     var brCount = (spec.businessRules || []).length;
     var entCount = (spec.entities || []).length;
-    var sections = mod.anticipatedSections || [];
+    var sections = (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, resources: [] } : s;
+    });
     var groupId = 'mod-' + code;
     var collapsed = navCollapseState[groupId] === true;
 
@@ -3957,7 +3968,9 @@ function refreshAllPermGrids() {
 
 function renderModuleStructure(code) {
     const mod = data.modules.find(m => m.code === code);
-    const sections = mod ? (mod.anticipatedSections || []) : [];
+    const sections = mod ? (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, description: '', resources: [] } : s;
+    }) : [];
 
     if (sections.length === 0) {
         return '<div class="card" style="text-align:center;padding:2rem;color:var(--text-muted);">' +
@@ -4036,7 +4049,9 @@ function renderModuleStructure(code) {
 /* ---------- Section-Grouped Rendering (Hierarchical Mode) ---------- */
 
 function renderSectionGroupedItems(mod, itemsKey, code, renderFn) {
-    var sections = mod.anticipatedSections || [];
+    var sections = (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, resources: [] } : s;
+    });
     var html = '';
     sections.forEach(function(section) {
         var items = section[itemsKey] || [];
@@ -4059,7 +4074,9 @@ function renderModuleMockups(code) {
     var screens = spec.screens || [];
     var wireframes = EMBEDDED_ARTIFACTS?.wireframes?.[code] || [];
     var mod = data.modules.find(function(m) { return m.code === code; });
-    var sections = mod ? (mod.anticipatedSections || []) : [];
+    var sections = mod ? (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, resources: [] } : s;
+    }) : [];
 
     // Priority 1: HTML mockups from screens[] specs
     if (screens.length > 0) {

package/templates/skills/business-analyse-html/html/src/scripts/01-data-init.js

@@ -6,6 +6,13 @@ let data = {{FEATURE_DATA}};
 const ORIGINAL_DATA = JSON.parse(JSON.stringify(data));
 const EMBEDDED_ARTIFACTS = {{EMBEDDED_ARTIFACTS}};
 
+// CRITICAL: Initialize top-level structures FIRST to prevent TypeError crashes
+data.cadrage = data.cadrage || {};
+data.modules = data.modules || [];
+data.dependencies = data.dependencies || [];
+data.handoff = data.handoff || {};
+data.cadrage.stakeholders = data.cadrage.stakeholders || [];
+
 // Initialize applications array (multi-app support)
 data.applications = data.applications || [];
 
@@ -66,8 +73,10 @@ data.moduleSpecs = data.moduleSpecs || {};
     if (!data.moduleSpecs[m.code]) {
         data.moduleSpecs[m.code] = { useCases: [], businessRules: [], entities: [], permissions: [], notes: '' };
     }
-    // Ensure anticipatedSections array exists
-    m.anticipatedSections = m.anticipatedSections || [];
+    // Ensure anticipatedSections array exists and normalize strings to objects
+    m.anticipatedSections = (m.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, description: '', resources: [] } : s;
+    });
     m.applicationCode = m.applicationCode || '';
     // Initialize screens array for interface specs
     if (!data.moduleSpecs[m.code].screens) {

package/templates/skills/business-analyse-html/html/src/scripts/02-navigation.js

@@ -149,7 +149,9 @@ function renderModuleNavItem(mod) {
     var ucCount = (spec.useCases || []).length;
     var brCount = (spec.businessRules || []).length;
     var entCount = (spec.entities || []).length;
-    var sections = mod.anticipatedSections || [];
+    var sections = (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, resources: [] } : s;
+    });
     var groupId = 'mod-' + code;
     var collapsed = navCollapseState[groupId] === true;
 

package/templates/skills/business-analyse-html/html/src/scripts/05-render-specs.js

@@ -611,7 +611,9 @@ function refreshAllPermGrids() {
 
 function renderModuleStructure(code) {
     const mod = data.modules.find(m => m.code === code);
-    const sections = mod ? (mod.anticipatedSections || []) : [];
+    const sections = mod ? (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, description: '', resources: [] } : s;
+    }) : [];
 
     if (sections.length === 0) {
         return '<div class="card" style="text-align:center;padding:2rem;color:var(--text-muted);">' +
@@ -690,7 +692,9 @@ function renderModuleStructure(code) {
 /* ---------- Section-Grouped Rendering (Hierarchical Mode) ---------- */
 
 function renderSectionGroupedItems(mod, itemsKey, code, renderFn) {
-    var sections = mod.anticipatedSections || [];
+    var sections = (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, resources: [] } : s;
+    });
     var html = '';
     sections.forEach(function(section) {
         var items = section[itemsKey] || [];
@@ -713,7 +717,9 @@ function renderModuleMockups(code) {
     var screens = spec.screens || [];
     var wireframes = EMBEDDED_ARTIFACTS?.wireframes?.[code] || [];
     var mod = data.modules.find(function(m) { return m.code === code; });
-    var sections = mod ? (mod.anticipatedSections || []) : [];
+    var sections = mod ? (mod.anticipatedSections || []).map(function(s) {
+        return typeof s === 'string' ? { code: s, name: s, resources: [] } : s;
+    }) : [];
 
     // Priority 1: HTML mockups from screens[] specs
     if (screens.length > 0) {

package/templates/skills/business-analyse-html/references/data-build.md

@@ -51,7 +51,10 @@ const FEATURE_DATA = {
       featureType: module.featureType || "data-centric",
       estimatedComplexity: module.estimatedComplexity || "medium",
       entities: module.entities || [],
-      anticipatedSections: module.anticipatedSections || [],
+      // NORMALIZE: source may have strings (coverageMatrix) or objects (module schema)
+      anticipatedSections: (module.anticipatedSections || []).map(s =>
+        typeof s === 'string' ? { code: s, name: s, description: '', resources: [] } : s
+      ),   // ALWAYS [{code, name, description, resources[]}]
       dependencies: module.dependencies || [],
       dependents: module.dependents || []
     }

package/templates/skills/business-analyse-html/references/data-mapping.md

@@ -57,7 +57,10 @@ Build a JSON object following this **exact mapping** from index.json to the HTML
     description: m.description || "",
     featureType: m.featureType || "data-centric",
     entities: m.entities || [],
-    anticipatedSections: m.anticipatedSections || [],    // [{code, description, resources[]}]
+    // NORMALIZE: source may have strings (coverageMatrix) or objects (module schema)
+    anticipatedSections: (m.anticipatedSections || []).map(s =>
+      typeof s === 'string' ? { code: s, name: s, description: '', resources: [] } : s
+    ),   // ALWAYS [{code, name, description, resources[]}]
     dependencies: m.dependencies || [],
     dependents: m.dependents || [],
     estimatedComplexity: m.estimatedComplexity || "medium",

package/templates/skills/business-analyse-html/steps/step-02-build-data.md

@@ -89,7 +89,11 @@ modules: master.modules.map(m => ({
   description: m.description || "",
   featureType: m.featureType || "data-centric",
   entities: m.entities || [],
-  anticipatedSections: m.anticipatedSections || [],
+  anticipatedSections: (m.anticipatedSections || []).map(s =>
+    typeof s === 'string'
+      ? { code: s, name: s, description: "", resources: [] }
+      : { code: s.code || s.name || "", name: s.label || s.name || s.code || "", description: s.description || "", resources: s.resources || [], route: s.route || "", permission: s.permission || "" }
+  ),
   dependencies: m.dependencies || [],
   dependents: m.dependents || [],
   estimatedComplexity: m.estimatedComplexity || "medium",
@@ -135,6 +139,50 @@ moduleSpecs[moduleCode] = {
   permissions: buildPermissionKeys(mod.permissions),
   apiEndpoints: mod.usecases?.apiEndpoints || []
 }
+
+// BUILD screens[] for HTML interactive mockups (SmartTable/SmartForm rendering)
+const flatScr = mod.screens?.screens || [];
+let screens = [];
+if (flatScr.length > 0) {
+  const bySec = {};
+  flatScr.forEach(s => {
+    const sec = s.section || "default";
+    if (!bySec[sec]) bySec[sec] = {
+      sectionCode: sec,
+      sectionLabel: s.sectionLabel || s.sectionDescription || sec,
+      resources: []
+    };
+    bySec[sec].resources.push({
+      code: s.screen || s.name || "",
+      label: s.sectionLabel || s.description || s.screen || "",
+      type: s.componentType || "unknown",
+      columns: (s.columns || []).map(c => ({
+        field: c.code || c.field || "", label: c.label || c.code || "",
+        type: c.type || c.dataType || "text", sortable: !!c.sortable
+      })),
+      filters: (s.filters || []).map(f =>
+        typeof f === 'string' ? f : (f.label || f.filterLabel || f.code || f.filterCode || "")),
+      fields: [],
+      tabs: (s.tabs || []).map(t => ({
+        label: t.label || t.tabLabel || t.code || "",
+        fields: (t.fields || []).map(f => ({
+          field: f.code || f.fieldCode || f.field || "",
+          label: f.label || f.code || "",
+          type: f.type || f.dataType || "text",
+          required: !!f.required
+        }))
+      })),
+      actions: (s.actions || []).map(a =>
+        typeof a === 'string' ? a : (a.code || a.label || a.actionCode || "")),
+      kpis: s.kpis || [],
+      options: s.options || [],
+      permission: s.permission || "",
+      notes: s.description || ""
+    });
+  });
+  screens = Object.values(bySec);
+}
+moduleSpecs[moduleCode].screens = screens;
 ```
 
 > See `references/data-mapping.md` for `buildPermissionKeys()` implementation.
@@ -156,6 +204,57 @@ FEATURE_DATA.modules.forEach(m => {
 
 > This step is CRITICAL for the HTML viewer to display UC/BR grouped by section.
 
+### Post-Build Self-Check (MANDATORY — BLOCKING)
+
+After enriching anticipatedSections, run this self-check to detect data loss:
+
+```javascript
+// SELF-CHECK: compare source file counts vs FEATURE_DATA counts
+const errors = [];
+FEATURE_DATA.modules.forEach(m => {
+  const spec = FEATURE_DATA.moduleSpecs[m.code];
+  const source = collected_data.modules[m.code];
+  if (!spec) { errors.push(`MISSING moduleSpecs[${m.code}]`); return; }
+
+  const srcUC = (source?.usecases?.useCases || []).length;
+  const bltUC = (spec.useCases || []).length;
+  if (srcUC > 0 && bltUC === 0)
+    errors.push(`${m.code}: useCases EMPTY but source has ${srcUC}`);
+
+  const srcBR = (source?.rules?.rules || []).length;
+  const bltBR = (spec.businessRules || []).length;
+  if (srcBR > 0 && bltBR === 0)
+    errors.push(`${m.code}: businessRules EMPTY but source has ${srcBR}`);
+
+  const srcEnt = (source?.entities?.entities || []).length;
+  const bltEnt = (spec.entities || []).length;
+  if (srcEnt > 0 && bltEnt === 0)
+    errors.push(`${m.code}: entities EMPTY but source has ${srcEnt}`);
+});
+
+if (errors.length > 0) {
+  Display("⛔ SELF-CHECK FAILED — data loss detected:");
+  errors.forEach(e => Display("  - " + e));
+  // FIX: re-map the failing modules from collected_data before continuing
+}
+```
+
+> If self-check detects errors, you MUST re-read the source data and re-build the failing moduleSpecs entries.
+> Do NOT proceed with empty arrays when source data exists.
+
+**dependencies[] (TOP-LEVEL — CRITICAL for HTML navigation):**
+```javascript
+dependencies: (master.consolidation?.crossModuleInteractions || master.dependencyGraph?.edges || []).map(i => ({
+  from: i.fromModule || i.from || "",
+  to: i.toModule || i.to || "",
+  description: i.description || ""
+}))
+```
+
+> **WARNING:** `data.dependencies` is used by the sidebar (navigation), module rendering, consolidation views,
+> handoff summary, and export. If this array is missing, the entire HTML page crashes with a TypeError.
+> ALWAYS include it, even if empty (`dependencies: []`).
+
 **consolidation:**
 ```javascript
 consolidation: {
@@ -223,6 +322,31 @@ for (const section of sections) {
   }
 }
 
+// Source C: screens without mockup → auto-generate text description as wireframe fallback
+const screensWithoutMockup = flatScreens.filter(s => !s.mockup && !s.mockupFormat);
+for (const screen of screensWithoutMockup) {
+  const type = screen.componentType || "";
+  let desc = "";
+  if (type.includes("Table") || type.includes("Grid")) {
+    const cols = screen.columns || [];
+    desc = "Tableau avec " + cols.length + " colonnes : " + cols.map(c => c.label || c.code).join(", ");
+  } else if (type.includes("Form")) {
+    const tabs = screen.tabs || [];
+    desc = "Formulaire " + (tabs.length > 0 ? "avec " + tabs.length + " onglet(s)" : "");
+  } else if (type.includes("Dashboard")) {
+    desc = "Tableau de bord avec KPIs";
+  } else if (type.includes("Kanban")) {
+    desc = "Vue Kanban";
+  }
+  if (desc) {
+    rawWireframes.push({
+      screen: screen.screen || "", section: screen.section || "",
+      mockupFormat: "text", mockup: desc,
+      description: screen.sectionDescription || "", elements: [], componentMapping: []
+    });
+  }
+}
+
 // STEP 2: Map to HTML format (RENAME: mockupFormat → format, mockup → content)
 wireframes: {
   [moduleCode]: rawWireframes.map(wf => ({
@@ -287,6 +411,7 @@ dependencyGraph: {
 - FEATURE_DATA.moduleSpecs must have ONE entry per module
 - cadrage.scope uses HTML keys (inscope/outofscope)
 - Wireframe fields use format/content (NOT mockupFormat/mockup)
+- Per-module: useCases/businessRules/entities count must match source (empty when source has data = BUG)
 
 ## NEXT STEP
 

package/templates/skills/business-analyse-html/steps/step-04-verify.md

@@ -8,7 +8,7 @@ model: opus
 
 ## YOUR TASK
 
-Run 5 blocking validations on the generated HTML file and display the completion summary.
+Run 6 blocking validations on the generated HTML file and display the completion summary.
 
 ---
 
@@ -53,6 +53,40 @@ FOR each module in FEATURE_DATA.modules:
     BLOCKING_ERROR("Module {module.code} not in wireframes")
 ```
 
+**Check 6 — Per-module data completeness (source vs HTML):**
+```
+FOR each module in FEATURE_DATA.modules:
+  Read source: docs/{app}/{module.code}/business-analyse/v{version}/usecases.json
+  sourceUCCount = count of useCases in source file
+  htmlUCCount = count in FEATURE_DATA.moduleSpecs[module.code].useCases
+  IF sourceUCCount > 0 AND htmlUCCount === 0:
+    BLOCKING_ERROR("Module {module.code}: 0 useCases in HTML but {sourceUCCount} in source")
+
+  Read source: docs/{app}/{module.code}/business-analyse/v{version}/rules.json
+  sourceBRCount = count of rules in source file
+  htmlBRCount = count in FEATURE_DATA.moduleSpecs[module.code].businessRules
+  IF sourceBRCount > 0 AND htmlBRCount === 0:
+    BLOCKING_ERROR("Module {module.code}: 0 businessRules in HTML but {sourceBRCount} in source")
+```
+
+**Check 7 — No runtime crash (CRITICAL — validates page won't be blank):**
+```
+Open ba-interactive.html and search for the FEATURE_DATA JSON block.
+Verify these MANDATORY top-level fields exist:
+  - "modules": [...]          (array, can be empty)
+  - "dependencies": [...]     (array, can be empty)
+  - "cadrage": {...}          (object with stakeholders[], scope{})
+  - "moduleSpecs": {...}      (object, one key per module)
+  - "consolidation": {...}    (object)
+
+IF "dependencies" is missing from FEATURE_DATA:
+  Add: "dependencies": [] to the FEATURE_DATA object in the HTML
+  (This is the #1 cause of blank HTML pages — TypeError on data.dependencies.length crashes all JS)
+
+IF "modules" is missing:
+  BLOCKING_ERROR("FEATURE_DATA.modules missing — page will crash")
+```
+
 > **IF any check fails:** fix the issue and re-run the failing step before completing.
 
 ---