@atlashub/smartstack-cli 3.18.0 → 3.19.0

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

@@ -468,11 +468,79 @@ Auto-added:
 
 ---
 
+---
+
+## 10. Entity Classification Patterns
+
+> **Usage:** Loaded by step-01-cadrage (section 4d-bis) to accelerate entity scoring.
+> **Full reference:** `references/entity-architecture-decision.md` (scoring grid, decision tree, section patterns)
+> These patterns provide quick pre-classification. Full scoring is still required to confirm.
+
+### 10.1 Toujours Module Dedie (score typique >= 11)
+
+| Entite | Domaines typiques | Pourquoi module dedie |
+|--------|-------------------|-----------------------|
+| Clients/Customers | CRM, Ventes, Facturation | Hub relationnel central, multi-acteur, lifecycle complet |
+| Employes/Employees | RH, Temps, Paie | Acteur central, donnees sensibles, multi-workflows |
+| Projets/Projects | Gestion, Temps, Facturation | Lifecycle complexe, multi-ressources, reporting |
+| Commandes/Orders | Ventes, Logistique | Workflow d'approbation, etats multiples, sous-entites |
+| Factures/Invoices | Finance, Ventes | Obligations legales, workflow complexe |
+| Contrats/Contracts | Juridique, RH, Ventes | Lifecycle avec echeances, obligations, renouvellement |
+| Produits/Products | Commerce, Inventaire | Catalogue avec variantes, tarification, stock |
+
+**Section pattern for module dedie:**
+- Section `list` (TOUJOURS) : grille + create en modale + clic vers detail
+- Page detail avec onglets : Infos + onglets relationnels
+- Sections additionnelles UNIQUEMENT si : dashboard, approve, import, rapport
+
+### 10.2 Souvent Sous-entite du Parent (score typique 4-6)
+
+| Entite | Module parent typique | Pourquoi sous-entite |
+|--------|----------------------|-----------------------|
+| Adresses | Clients, Employes | Composant du parent, pas d'autonomie fonctionnelle |
+| Notes/Commentaires | Tout module | Sous-objet universel, lie au contexte parent |
+| Pieces jointes/Documents | Tout module | Stockage lie au parent, pas de lifecycle propre |
+| Lignes de commande | Commandes | Composant structurel, pas de sens seul |
+| Tags/Labels | Tout module | Categorisation simple, configurable |
+| Contacts (d'un client) | Clients | Personnes liees a l'entite parente |
+
+**Presentation dans le parent:** Onglet dans la page detail du module parent
+
+### 10.3 Toujours Config List (score typique 0-3)
+
+| Entite | Pourquoi config list |
+|--------|---------------------|
+| Pays, Villes | Reference geographique stable, rarement modifiee |
+| Devises | Reference systeme, standard ISO |
+| Statuts (types enumeres) | Enum ou lookup, admin-only, < 20 valeurs |
+| Unites de mesure | Reference technique stable |
+| Codes postaux | Reference externe, pas de CRUD utilisateur |
+| Types/Categories simples | Flat list sans hierarchie, configurable par admin |
+| Codes d'imputation | Reference comptable, admin-managed, stable |
+
+> **Override rule:** Peut etre promu si le client exprime un besoin de hierarchie (> 2 niveaux), de workflow, ou de permissions specifiques.
+
+### 10.4 Decision Rapide par Domaine
+
+> **Lors de l'approfondissement, si le domaine de l'application est identifie, utiliser ce tableau pour pre-classifier les entites referenciees.**
+
+| Domaine de l'app | Entites typiquement CORE (module) | Entites typiquement SUPPORT (sous-entite/config) |
+|-------------------|-----------------------------------|--------------------------------------------------|
+| **Gestion du temps** | Employes, Projets, Activites, Absences | Codes d'imputation, Types d'absence, Departements |
+| **CRM / Ventes** | Clients, Contacts, Opportunites, Devis | Secteurs, Sources, Etapes de vente |
+| **E-commerce** | Produits, Commandes, Clients, Factures | Categories, Tailles, Couleurs, Devises |
+| **RH** | Employes, Contrats, Conges, Evaluations | Postes, Departements, Types de contrat |
+| **Gestion de projets** | Projets, Taches, Ressources, Jalons | Statuts, Priorites, Types de tache |
+| **Finance** | Factures, Paiements, Budgets, Ecritures | Comptes, Journaux, Periodes |
+| **Logistique** | Entrepots, Mouvements, Expeditions | Transporteurs, Unites, Zones |
+
+---
+
 ## 9. Versioning & Updates
 
-**Catalog Version:** 1.0.0
-**Last Updated:** 2025-02-01
-**Next Review:** 2025-05-01
+**Catalog Version:** 2.0.0
+**Last Updated:** 2026-02-11
+**Next Review:** 2026-05-11
 **Maintained By:** SmartStack Team
 
 Changes will be tracked in `templates/patterns/suggestion-catalog-changelog.md`.

package/templates/skills/business-analyse/references/cadrage-pre-analysis.md

@@ -76,14 +76,17 @@ When the problem domain is identified, pre-load domain-specific needs:
 
 For each detected module, anticipate sections (Level 4) and resources (Level 5) based on feature type:
 
-| Feature type | Standard sections | Standard resources per section |
-|-------------|------------------|------------------------------|
-| data-centric | list, detail, create, edit | {entity}-grid, {entity}-form, {entity}-card |
-| workflow | list, detail, create, edit, approve, history | {entity}-grid, {entity}-form, approval-panel, status-timeline |
-| reporting | dashboard, detail, export | summary-chart, kpi-cards, export-panel |
-| integration | list, detail, config, sync, logs | sync-status-grid, config-form, log-viewer |
-
-**Always check:** Does the user's description imply additional sections beyond the standard set? (e.g., "reports" → dashboard + export, "calendar view" → calendar section)
+| Feature type | Sections (functional zones) | Resources (in list section) | Detail page tabs |
+|-------------|---------------------------|---------------------------|------------------|
+| data-centric | list | {entity}-grid, {entity}-filters, {entity}-form | Infos, {relations} |
+| workflow | list, approve | {entity}-grid, {entity}-filters, {entity}-form, approval-queue | Infos, {relations}, Historique |
+| reporting | dashboard | summary-chart, kpi-cards, export-panel | — |
+| integration | list | sync-status-grid, config-form, log-viewer | Infos, Config, Logs |
+
+> **RULE:** Sections = functional zones only (`list`, `dashboard`, `approve`, `import`, `rapport`, `planning`).
+> `create`/`edit` = actions (modal/drawer) within the `list` page. `detail` = tabbed page reached by clicking a row in `list`.
+
+**Always check:** Does the user's description imply additional functional sections? (e.g., "reports" → `dashboard`, "calendar view" → `planning`, "approval workflow" → `approve`)
 
 ## Output Format (Internal Only)
 

package/templates/skills/business-analyse/references/cadrage-structure-cards.md

@@ -64,15 +64,17 @@
   "module": "Users",
   "ucRef": "UC-UM-001",
   "notes": "Foundation module, must be implemented first",
-  "anticipatedSections": ["list", "detail", "create", "edit"],
-  "anticipatedResources": ["user-grid", "user-form", "user-card"]
+  "anticipatedSections": ["list", "dashboard"],
+  "anticipatedResources": ["user-grid", "user-filters", "user-form"],
+  "detailTabs": ["Informations", "Roles", "Historique"]
 }
 ```
 **MANDATORY fields:** `item`, `category`, `module`
-**OPTIONAL fields:** `ucRef`, `notes`, `anticipatedSections`, `anticipatedResources`
+**OPTIONAL fields:** `ucRef`, `notes`, `anticipatedSections`, `anticipatedResources`, `detailTabs`
 **category values:** `mustHave`, `shouldHave`, `couldHave`, `outOfScope`, `implicit` (camelCase)
-**anticipatedSections:** Array of section codes (Level 4) — e.g., `["list", "detail", "create", "edit", "dashboard", "export"]`
-**anticipatedResources:** Array of resource codes (Level 5) — e.g., `["user-grid", "user-form", "user-card"]`
+**anticipatedSections:** Array of section codes (Level 4) — functional zones ONLY: `["list", "dashboard", "approve", "import", "rapport", "planning"]`. NEVER `create`, `edit`, or `detail` (those are actions/pages within `list`).
+**anticipatedResources:** Array of resource codes (Level 5) — e.g., `["user-grid", "user-filters", "user-form"]`
+**detailTabs:** Array of tab names for the detail page (reached by clicking a row in `list`) — e.g., `["Informations", "Roles", "Historique"]`
 **FORBIDDEN fields:** Do NOT use `id`, `feature`, `priority`. Use `item` + `category`.
 
 ## codebaseContext

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

@@ -14,27 +14,55 @@ const FEATURE_DATA = {
     analysisMode: master.metadata.analysisMode || "interactive" // always "interactive" — analysis is always interactive
   },
   cadrage: {
-    goal: master.cadrage.goal,
-    vision: master.cadrage.vision,
-    success_criteria: master.cadrage.success_criteria,
+    // CONTEXT SECTION — merged from problem/asIs/toBe (lean cadrage)
+    context: {
+      problem: master.cadrage.problem || "",           // flat string from feature.json
+      trigger: master.cadrage.trigger || "",            // flat string from feature.json
+      currentSituation: master.cadrage.asIs || "",      // flat string from feature.json
+      desiredSituation: master.cadrage.toBe || "",      // flat string from feature.json
+      painPoints: (master.cadrage.stakeholders || []).flatMap(s => s.painPoints || []),
+      acceptanceCriteria: (master.cadrage.acceptanceCriteria || []).map(c => c.criterion)
+    },
     scope: {
       // CONVERT feature.json keys to HTML keys:
       // mustHave → vital, shouldHave → important, couldHave → optional, outOfScope → excluded
-      vital: master.globalScope.mustHave || [],
-      important: master.globalScope.shouldHave || [],
-      optional: master.globalScope.couldHave || [],
-      excluded: master.globalScope.outOfScope || []
+      vital: (master.cadrage.globalScope?.mustHave || master.cadrage.coverageMatrix?.filter(i => i.category === "mustHave") || [])
+        .map(item => typeof item === 'string' ? { name: item, description: "" } : { name: item.item || item, description: item.notes || "" }),
+      important: (master.cadrage.globalScope?.shouldHave || master.cadrage.coverageMatrix?.filter(i => i.category === "shouldHave") || [])
+        .map(item => typeof item === 'string' ? { name: item, description: "" } : { name: item.item || item, description: item.notes || "" }),
+      optional: (master.cadrage.globalScope?.couldHave || master.cadrage.coverageMatrix?.filter(i => i.category === "couldHave") || [])
+        .map(item => typeof item === 'string' ? { name: item, description: "" } : { name: item.item || item, description: item.notes || "" }),
+      excluded: (master.cadrage.globalScope?.outOfScope || master.cadrage.coverageMatrix?.filter(i => i.category === "outOfScope") || [])
+        .map(item => typeof item === 'string' ? { name: item, description: "" } : { name: item.item || item, description: item.notes || "" })
     },
-    constraints: master.cadrage.constraints || [],
-    risks: master.cadrage.risks || [],
-    stakeholders: master.stakeholders || []
+    risks: (master.cadrage.risks || []).map(r => ({
+      description: r.description,
+      probability: r.probability,
+      impact: r.impact,
+      mitigation: r.mitigation
+    })),
+    stakeholders: (master.cadrage.stakeholders || []).map(s => ({
+      role: s.role,
+      function: s.function,
+      tasks: s.tasks || [],
+      frequency: s.frequency || "",
+      access: s.involvement || "",
+      frustrations: (s.painPoints || []).join("\n")
+    }))
   },
   modules: [
+    // FOR EACH module in master.modules[]:
     {
-      moduleCode: module.code,
-      moduleName: module.name,
-      moduleDescription: module.description || "",
-      // ... per-module fields from feature.json
+      code: module.code,                              // PascalCase key (e.g., "GestionTemps")
+      name: module.name || module.code,               // Display name (e.g., "Gestion du temps") — MANDATORY
+      description: module.description || "",
+      featureType: module.featureType || "data-centric",
+      priority: module.priority || "must",
+      estimatedComplexity: module.estimatedComplexity || "medium",
+      entities: module.entities || [],
+      anticipatedSections: module.anticipatedSections || [],
+      dependencies: module.dependencies || [],
+      dependents: module.dependents || []
     }
   ],
   moduleSpecs: {

package/templates/skills/business-analyse/references/deploy-modes.md

@@ -20,7 +20,7 @@ Simplified handoff with minimal scope:
 - 3 core SeedData entries (omit some optional ones)
 - Basic prd.json with simplified sections
 - Lightweight progress.txt
-- Display `/ralph-loop -r` command for later use
+- Display `/ralph-loop` command for later use
 
 ### Delta Mode (use_case = refactoring)
 

package/templates/skills/business-analyse/references/entity-architecture-decision.md

@@ -0,0 +1,218 @@
+# Entity Architecture Decision Reference
+
+> **Loaded by:** step-01-cadrage (section 4d-bis)
+> **Purpose:** Provide a structured decision framework for entity placement in the C/A/M/S/R hierarchy
+> **Mode:** ULTRATHINK — all scoring is internal reasoning, only the recommendation is shown to the client
+
+---
+
+## 1. Entity Scoring Grid (5 criteria, 0-3 each)
+
+For EACH referenced entity detected during approfondissement, score silently:
+
+| Critere | 0 (Lookup) | 1 (Composant) | 2 (Module leger) | 3 (Module complet) |
+|---------|-----------|---------------|-------------------|---------------------|
+| **Cycle de vie** | Statique (rarement modifie, admin-only) | CRUD basique (creer, modifier, supprimer) | CRUD + etats/transitions simples | Lifecycle complet (etats multiples, transitions, approbations, archivage) |
+| **Nombre d'acteurs** | Admin seul | 1 role utilisateur | 2-3 roles distincts | 4+ roles avec permissions differenciees |
+| **Relations** | Lookup (0-1 FK entrantes) | Composant (1-3 FK) | Hub (3-5 FK entrantes/sortantes) | Pivot (5+ FK, central dans le graphe de donnees) |
+| **Volume prevu** | < 50 entrees stables | 50-500 entrees | 500-5000 entrees | 5000+ ou croissance continue |
+| **Autonomie fonctionnelle** | Pas de sens seul (ex: code postal) | Sens uniquement dans le contexte parent | Pourrait etre utilise seul | Domaine metier independant (ex: Clients, Projets) |
+
+### Interpretation du score total (0-15)
+
+| Score | Classification | Action |
+|-------|---------------|--------|
+| **0-3** | **Config list** (lookup table) | Table de reference administrable. Pas de module, pas de section. Gere dans la config admin. |
+| **4-6** | **Gere dans l'app** (sous-entite) | L'entite est geree comme composant du module parent. Accessible via un onglet dans la page detail du parent. |
+| **7-10** | **Module leger** | Module avec section `list` principale. Peu de sections fonctionnelles additionnelles. |
+| **11-15** | **Module complet dedie** | Module avec section `list` + sections fonctionnelles riches (dashboard, rapports, workflows). |
+
+---
+
+## 2. Domain Coherence Decision Tree
+
+> **CRITICAL:** Evaluer la coherence domaine AVANT le scoring. Une entite PERIPHERAL avec un score eleve reste un risque de scope creep.
+
+```
+L'entite {E} est-elle CORE pour cette application ?
+│
+├── CORE (sans {E}, l'application perd son sens)
+│   │   Exemples : Projets dans une app de gestion du temps,
+│   │              Clients dans un CRM,
+│   │              Employes dans une app RH
+│   │
+│   └── Score >= 7 ? → Module dedie (RECOMMANDE avec haute confiance)
+│   └── Score 4-6 ? → Section/onglet dans le module principal
+│   └── Score 0-3 ? → Config list (rare pour une entite CORE)
+│
+├── SUPPORT (utile, enrichit l'app, mais pas central)
+│   │   Exemples : Departements dans une app de gestion du temps,
+│   │              Fournisseurs dans un CRM orientee ventes,
+│   │              Categories dans un module produits
+│   │
+│   ├── Deja gere ailleurs dans l'ecosysteme ? → Systeme externe (RECOMMANDE)
+│   └── Pas encore gere ?
+│       └── Score >= 7 ? → Module leger (confiance MOYENNE, alerter sur le scope)
+│       └── Score 4-6 ? → Section/onglet du module qui en a le plus besoin
+│       └── Score 0-3 ? → Config list (RECOMMANDE)
+│
+└── PERIPHERAL (tangentiel au domaine applicatif)
+    │   Exemples : Comptabilite dans une app de gestion du temps,
+    │              Logistique dans un CRM,
+    │              Facturation dans une app RH (sauf si paie)
+    │
+    └── TOUJOURS → Config list ou Systeme externe (RECOMMANDE)
+        Avertir : "Cette entite sort du perimetre applicatif.
+                   Risque de scope creep si integree comme module."
+```
+
+---
+
+## 3. Pre-classified Entity Patterns
+
+> **Raccourcis de scoring** : ces patterns accelerent l'analyse en fournissant une classification par defaut.
+> Le scoring complet reste necessaire pour confirmer ou overrider.
+
+### 3a. Toujours Module Dedie (score typique >= 11)
+
+| Entite | Domaines typiques | Pourquoi module dedie |
+|--------|-------------------|-----------------------|
+| Clients/Customers | CRM, Ventes, Facturation | Hub relationnel central, multi-acteur, lifecycle complet avec etats |
+| Employes/Employees | RH, Temps, Paie | Acteur central avec donnees sensibles, multi-workflows (conges, evaluations) |
+| Projets/Projects | Gestion, Temps, Facturation | Lifecycle complexe (ouvert → en cours → cloture), multi-ressources, reporting |
+| Commandes/Orders | Ventes, Logistique | Workflow d'approbation, etats multiples, sous-entites (lignes) |
+| Factures/Invoices | Finance, Ventes | Obligations legales, workflow complexe, etats fiscaux |
+| Contrats/Contracts | Juridique, RH, Ventes | Lifecycle avec echeances, obligations, renouvellement automatique |
+| Produits/Products | Commerce, Inventaire | Catalogue avec variantes, tarification, stock |
+
+### 3b. Souvent Sous-entite du Parent (score typique 4-6)
+
+| Entite | Module parent typique | Pourquoi sous-entite |
+|--------|----------------------|-----------------------|
+| Adresses | Clients, Employes | Composant du parent, pas de sens sans le parent |
+| Notes/Commentaires | Tout module | Sous-objet universel, pas d'autonomie fonctionnelle |
+| Pieces jointes/Documents | Tout module | Stockage lie au parent, pas de lifecycle propre |
+| Lignes de commande | Commandes | Composant structurel de la commande |
+| Tags/Labels | Tout module | Categorisation simple, admin-configurable |
+| Contacts (d'un client) | Clients | Personnes liees a l'entite parente |
+
+### 3c. Toujours Config List (score typique 0-3)
+
+| Entite | Pourquoi config list |
+|--------|---------------------|
+| Pays, Villes | Reference geographique stable, rarement modifiee |
+| Devises | Reference systeme, standard ISO |
+| Statuts (types enumeres) | Enum ou lookup, admin-only, < 20 valeurs |
+| Unites de mesure | Reference technique stable |
+| Codes postaux | Reference externe, pas de CRUD utilisateur |
+| Types/Categories simples | Flat list sans hierarchie, configurable par admin |
+
+> **Override rule:** Une entite pre-classifiee "config list" peut etre promue en "module leger" si le client exprime un besoin de hierarchie (> 2 niveaux), de workflow, ou de permissions specifiques.
+
+---
+
+## 4. Section Pattern for Modules
+
+> **REGLE FONDAMENTALE : Les sections representent des zones fonctionnelles, PAS des operations CRUD.**
+
+### Le pattern de navigation SmartStack
+
+```
+Module
+├── Section: list
+│   └── Page principale avec grille/table
+│   └── Action "Creer" (ouvre formulaire en modale/drawer DANS cette page)
+│   └── Clic sur une ligne → navigation vers la page detail
+│   └── Resources : {entity}-grid, {entity}-filters, {entity}-form
+│
+├── (detail = page de detail avec onglets, accessible depuis list)
+│   └── Onglet Info → informations principales (lecture + edition)
+│   └── Onglet {relation} → sous-entites liees (ex: Lignes, Contacts, Documents)
+│   └── Onglet Historique → journal d'activite
+│   └── Resources : {entity}-detail, {entity}-tabs, {relation}-panel
+│
+├── Section: dashboard (SI KPIs/reporting necessaire)
+│   └── Vue d'ensemble avec cartes KPI, graphiques, activite recente
+│   └── Resources : {entity}-kpi-cards, {entity}-charts, {entity}-activity
+│
+├── Section: approve (SI workflow d'approbation)
+│   └── File d'attente d'approbation, timeline de statut
+│   └── Resources : approval-queue, status-timeline
+│
+├── Section: import (SI import en masse)
+│   └── Upload fichier, mapping colonnes, preview, execution
+│   └── Resources : import-upload, import-mapping, import-preview
+│
+└── Section: rapport (SI reporting specifique au module)
+    └── Rapports configurables, export, planification
+    └── Resources : report-builder, report-export
+```
+
+### Ce qui n'est JAMAIS une section
+
+| PAS une section | C'est quoi en realite |
+|-----------------|----------------------|
+| `create` | Action (bouton) dans la page `list`, ouvre un formulaire en modale/drawer |
+| `edit` | Action dans la page detail, bascule les champs en mode edition |
+| `detail` | Page de detail accessible par navigation depuis `list` (pas une section menu) |
+| `delete` | Action avec confirmation dans la page `list` ou `detail` |
+| `search` | Composant de filtrage integre dans la section `list` |
+
+### Regles de proposition de sections
+
+| Condition detectee | Section a proposer |
+|--------------------|--------------------|
+| Module avec entites | `list` (TOUJOURS — section par defaut obligatoire) |
+| KPIs, indicateurs, ou role manager | `dashboard` |
+| Workflow de validation/approbation | `approve` |
+| Volume > 100 ou import mentionne | `import` |
+| Reporting specifique au module | `rapport` |
+| Planification temporelle | `planning` / `calendar` |
+| Visualisation geographique | `map` |
+
+---
+
+## 5. Architecture Proposal Template
+
+> **Utiliser ce template quand la recommandation est "Module dedie".**
+
+```markdown
+### Architecture proposee : {ModuleName}
+
+| Niveau | Valeur | Justification |
+|--------|--------|---------------|
+| Context | `business` | Contexte metier standard |
+| Application | `{ApplicationCode}` | {Nom de l'application en cours d'analyse} |
+| Module | `{ModuleCode}` | {Pourquoi ce decoupage : autonomie fonctionnelle, domaine distinct, cycle de vie propre} |
+
+**Sections fonctionnelles :**
+
+| Section | Justification | Resources |
+|---------|---------------|-----------|
+| `list` | Page principale de gestion des {entity_plural} | {entity}-grid, {entity}-filters, {entity}-form |
+| {section_2} | {pourquoi cette section est necessaire pour CE module} | {resources} |
+| ... | ... | ... |
+
+**Onglets de la page detail :**
+
+| Onglet | Contenu | Pourquoi |
+|--------|---------|----------|
+| Informations | Fiche principale de l'{entity} | Toujours present |
+| {relation_1} | {sous-entites ou entites liees} | {pourquoi cet onglet} |
+| Historique | Journal des modifications | Toujours present si audit requis |
+
+**Impact sur le graphe de dependances :**
+- {ModuleName} sera une dependance de : {list of modules that reference this entity}
+- {ModuleName} depend de : {list of modules it references, or "aucun (module fondation)"}
+- Position dans le tri topologique : couche {N}
+```
+
+---
+
+## 6. Confidence Levels
+
+| Confiance | Quand | Presentation au client |
+|-----------|-------|------------------------|
+| **HAUTE** | Pre-classification match + Score coherent + Domaine CORE | "Je recommande fortement..." + option en premier avec "(Recommande)" |
+| **MOYENNE** | Score dans la zone grise (6-8) ou domaine SUPPORT | "Mon analyse suggere..." + option en premier avec "(Suggere)" |
+| **BASSE** | Informations insuffisantes ou domaine PERIPHERAL | "Plusieurs options sont possibles..." + pas de recommandation, options neutres |

package/templates/skills/business-analyse/references/robustness-checks.md

@@ -317,7 +317,8 @@ Status: READY FOR DEVELOPMENT ✓
 Next Steps:
   1. Address warnings (optional, recommended)
   2. Review progress tracker: .ralph/progress.txt
-  3. Launch development: /ralph-loop -r
+  3. Launch development: /ralph-loop
+     (Use /ralph-loop -r ONLY to resume an interrupted loop)
 ═══════════════════════════════════════════════════════════════
 ```
 

package/templates/skills/business-analyse/references/spec-auto-inference.md

@@ -29,24 +29,78 @@
 | datetime | DatePicker | entity.required | — |
 | bool | Toggle | — | default: false |
 
-## Auto-Generated Sections by featureType
-
-| featureType | Sections generated |
-|---|---|
-| data-centric | list, create, detail |
-| workflow | list, create, detail, edit |
-| integration | list, detail, config |
-| reporting | dashboard |
-| full-module | list, create, detail, edit, dashboard |
-
-## Section Generation Rules
-
-1. **list section:** SmartTable with all non-long-text attributes as columns, actions = [view, edit, delete], defaultSort = { createdAt, desc }
-2. **create section:** SmartForm with all writable attributes as fields, component inferred from type
-3. **detail section:** DetailCard with all attributes + child SmartTable for each 1:N relationship
-4. **edit section:** Same as create but pre-filled (mode: edit)
+## Auto-Generated UI Components by featureType
+
+> **RULE:** Sections = functional zones only. `create`/`edit` are actions within `list`. `detail` is a tabbed page reached from `list`.
+
+| featureType | Sections (functional zones) | List page includes | Detail page tabs |
+|---|---|---|---|
+| data-centric | list | grid, filters, create form (modal) | Infos, {relations} |
+| workflow | list, approve | grid, filters, create form (modal) | Infos, {relations}, Historique |
+| integration | list | grid, filters, config form | Infos, Config, Logs |
+| reporting | dashboard | — | — |
+| full-module | list, dashboard | grid, filters, create form (modal) | Infos, {relations}, Historique |
+
+## Component Generation Rules
+
+1. **list section:** SmartTable with all non-long-text attributes as columns, actions = [view, edit, delete], defaultSort = { createdAt, desc }. Create action opens SmartForm in modal/drawer.
+2. **create form (in list):** SmartForm with all writable attributes as fields, component inferred from type. Opens as modal/drawer from the list page.
+3. **detail page (from list click):** TabPanel with: Info tab (all attributes), relation tabs (child SmartTable for each 1:N relationship), History tab (if auditable). See "Detail Page Tab Auto-Inference" below for exact rules.
+4. **edit (in detail):** Same form as create but pre-filled (mode: edit). Inline in the detail page Info tab.
 5. **dashboard section:** Trigger 3d (dashboard specification)
 
+## Detail Page Tab Auto-Inference
+
+> **RULE:** Every module with a `list` section MUST have a companion detail page. Tabs are inferred from multiple sources.
+
+### Tab sources (merged in order)
+
+| Priority | Source | Tabs generated |
+|----------|--------|----------------|
+| 1 | `coverageMatrix[].detailTabs` (from cadrage) | Exact tab names as specified by client |
+| 2 | Entity `relationships[]` where `type = "1:N"` | One tab per child relationship (SmartTable) |
+| 3 | Entity has `lifeCycles[]` | History tab (Timeline) |
+| 4 | Always present | Info tab (first position) |
+
+### Merge algorithm
+
+```
+detailTabs = []
+
+# 1. Always add Info tab first
+detailTabs.push({ code: "info", label: "Informations", content: DetailCard })
+
+# 2. If cadrage specified detailTabs, use those names
+IF coverageMatrix[module].detailTabs EXISTS:
+  FOR EACH tabName IN detailTabs:
+    IF tabName matches a 1:N relationship entity → SmartTable tab
+    ELIF tabName == "Historique"/"History" → Timeline tab
+    ELSE → custom DetailCard tab (contents TBD in step-03b)
+
+# 3. If no cadrage tabs, auto-infer from relationships
+ELSE:
+  FOR EACH rel IN entity.relationships WHERE rel.type == "1:N":
+    detailTabs.push({ code: rel.target (kebab-case), label: rel.target (plural), content: SmartTable })
+
+# 4. Add History tab if auditable
+IF entity has lifeCycles:
+  detailTabs.push({ code: "history", label: "Historique", content: Timeline })
+```
+
+### Detail section auto-generation
+
+When auto-generating the detail section, create:
+- `specification.sections[]` entry with `code: "detail"`, `navigation: "hidden"`, route `/business/{app}/{module}/detail/:id`
+- `specification.uiWireframes[]` entry with `section: "detail"` and ASCII mockup showing all tabs
+- Resources: `{module}-detail-header` (DetailHeader), `{module}-detail-tabs` (TabPanel), `{module}-info-card` (DetailCard), one `{module}-{relation}-grid` per relation tab, `{module}-history` (Timeline if auditable)
+
+### Detail page navigation wiring
+
+The detail page is NOT a sidebar entry. Navigation is handled by:
+- **From list**: row click action `navigate:detail` → `/business/{app}/{module}/detail/{id}`
+- **Back button**: detail header → `/business/{app}/{module}/list`
+- **Route registration**: route MUST be registered in frontend routing with `:id` parameter
+
 ## Status/Lifecycle Enhancement
 
 If entity has a status/enum field AND lifeCycles exists: