@atlashub/smartstack-cli 3.28.0 → 3.30.0

package/templates/skills/business-analyse/references/agent-module-prompt.md

@@ -24,12 +24,17 @@ Your mission: specify module "{moduleCode}" completely and autonomously.
 ## Mode: PROPOSE & REVIEW (Autonomous)
 
 You work WITHOUT user interaction:
-- Do NOT use AskUserQuestion — you make all decisions autonomously
+- **ABSOLUTE PROHIBITION: NEVER use AskUserQuestion** — not in ANY step (03a1, 03a2, 03b, 03c, 03d)
+- The step files you load contain AskUserQuestion calls — these are for INLINE MODE ONLY
+- When you see `AskUserQuestion` in a step file → replace with ULTRATHINK autonomous decision
+- When you see `Ask via AskUserQuestion` → decide autonomously based on context
+- When you see validation options (Auto-corriger, Réviser, etc.) → auto-correct silently
 - Use ULTRATHINK to reason about every design choice
 - Base decisions on the context below + SmartStack conventions
 - Write the specification to feature.json via ba-writer operations
 - Send a structured proposal summary to the team lead when done
 - Wait for approval or revision feedback
+- In step-03d: SKIP section 12 (Loop Decision) entirely → go to section 12-bis (Agent Mode)
 
 ## Module Context
 
@@ -132,17 +137,19 @@ Execute ALL compilation sections:
 - Functional Requirements
 - Permission matrix (CRUD per entity + module admin)
 - Navigation seed data (7 arrays — CRITICAL)
-- i18n keys (4 languages: fr, en, nl, de)
+- i18n keys (4 languages: fr, en, it, de)
 - API endpoints summary
 
-**CRITICAL for seed data — 7 mandatory arrays:**
-1. navigationModules (1 entry)
-2. navigationSections (1 per section)
-3. navigationResources (1+ per section)
-4. navigationTranslations (4 languages × all entries)
-5. permissions (CRUD per entity)
-6. rolePermissions (admin=all, manager=most, contributor=create+read+update, viewer=read)
-7. permissionConstants (C# constant names)
+**CRITICAL for seed data — 9 mandatory arrays:**
+1. navigationApplications (1 entry — application-level, created ONCE per app)
+2. applicationRoles (4 entries — admin, manager, contributor, viewer)
+3. navigationModules (1 entry per module)
+4. navigationSections (1 per section)
+5. navigationResources (1+ per section)
+6. navigationTranslations (4 languages × all entries)
+7. permissions (wildcard + CRUD per module — {path, action, description} format)
+8. rolePermissions (admin=wildcard, manager=CRU, contributor=CR, viewer=R)
+9. permissionConstants (C# constant names)
 
 ### Step 5: Validate & Propose (step-03d-validate.md)
 Load: `templates/skills/business-analyse/steps/step-03d-validate.md`
@@ -221,7 +228,29 @@ SendMessage({
   summary: "{moduleCode} module complete"
 })
 
-Then STOP — do not proceed to next module. The team lead handles ordering.
+Then WAIT for the team lead to send you a `shutdown_request`.
+Do NOT proceed to next module — the team lead handles module ordering.
+
+### Shutdown handling (MANDATORY):
+
+When you receive a message with `type: "shutdown_request"` from the team lead:
+→ Extract the `requestId` from the JSON message
+→ IMMEDIATELY respond with:
+
+```
+SendMessage({
+  type: "shutdown_response",
+  request_id: "{requestId from the shutdown_request}",
+  approve: true
+})
+```
+
+This terminates your process. Do NOT output any text after sending `shutdown_response`.
+
+**IMPORTANT:** Do NOT confuse APPROVED with shutdown. The sequence is:
+1. Team lead sends `APPROVED:{moduleCode}` → you update status + send `MODULE_COMPLETE`
+2. Team lead sends `shutdown_request` → you respond with `shutdown_response approve: true` → you terminate
+These are TWO separate steps. Never try to self-terminate or call `shutdown_response` without a `shutdown_request`.
 
 ## ID Naming Convention
 

package/templates/skills/business-analyse/references/consolidation-structural-checks.md

@@ -23,7 +23,7 @@
 | `specification.seedDataBusiness` | YES | Must define reference/lookup seed data for testing (types, categories, statuses) |
 | `specification.gherkinScenarios` | YES | Must be `{feature, scenarios[]}` (NOT flat array) |
 | `specification.navigation` | YES | Must have entries[] |
-| `specification.i18nKeys[]` | YES | Must have >=1 key with fr, en, nl, de |
+| `specification.i18nKeys[]` | YES | Must have >=1 key with fr, en, it, de |
 | `validation` | YES | Must have completenessChecks, consistencyChecks, semanticChecks, decision |
 
 ## B. Field Name Conformity
@@ -46,7 +46,8 @@
 | BR | `BR-(VAL\|CALC\|WF\|SEC\|DATA)-{PREFIX}-\d{3}` | BR-VAL-RM-001 |
 | UC | `UC-{PREFIX}-\d{3}` | UC-RM-001 |
 | FR | `FR-{PREFIX}-\d{3}` | FR-RM-001 |
-| Permissions | `business.{app}.{module}.{resource}.{action}` | business.freebike.repairs.create |
+| Permissions (module) | `business.{app}.{module}.{action}` | business.freebike.repairs.create |
+| Permissions (section) | `business.{app}.{module}.{section}.{action}` | business.freebike.repairs.dashboard.read |
 
 ## D. Cross-Module ID Uniqueness
 
@@ -71,7 +72,7 @@ FOR each region: IF missing position or components[] -> ERROR
 
 ```
 FOR each navigationModules[].code:
-  FOR each language in [fr, en, nl, de]:
+  FOR each language in [fr, en, it, de]:
     IF NOT EXISTS navigationTranslations[] with moduleCode AND language -> ERROR
 ```
 

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

@@ -37,7 +37,7 @@ Focused handoff for changes:
 |-------|-----------|
 | All modules missing handoff data | Return to step-05a-handoff.md. Handoff MUST be written to each module feature.json. |
 | prd.json generation failed | Verify ss derive-prd command is installed and feature.json path is correct. |
-| progress.txt incomplete | Ensure all 5 CORE SeedData entries are present per module. Check topological order. |
+| progress.txt incomplete | Ensure all CORE SeedData entries are present: 2 app-level (NavigationApplication + ApplicationRoles) + per module (NavigationModule + NavigationSections + Permissions + Roles). Check topological order. |
 | BA manifest not found | Create docs/business/index.json if missing. Use schema provided in section 3. |
 | Manifest entries incorrect | Verify appCode, moduleCode, and version match feature.json metadata exactly. |
 | ba-interactive.html is too small (< 100KB) | FEATURE_DATA not serialized correctly. Verify JSON structure. Re-run FEATURE_DATA build. |

package/templates/skills/business-analyse/references/handoff-file-templates.md

@@ -90,16 +90,16 @@ From `specification.uiWireframes[]`, `specification.dashboards[]` and `analysis.
 
 ## 4.6 SeedData Files
 
-**OBLIGATORY: 6 CORE (1 app-level + 5 per module) + business per module:**
+**OBLIGATORY: 2 app-level CORE + per module CORE (NavigationModule + NavigationSections + Permissions + Roles) + business per module:**
 
 ```json
 "seedData": [
   { "path": "src/Infrastructure/Persistence/Seeding/Data/NavigationApplicationSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.navigationApplications", "module": "shared", "description": "Application-level navigation seed data. Created ONCE per application (FIRST). Provides ApplicationId for modules and roles." },
+  { "path": "src/Infrastructure/Persistence/Seeding/Data/ApplicationRolesSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.rolePermissions", "module": "shared", "description": "Application-scoped role definitions (admin, manager, contributor, viewer). Created ONCE per application. Provides role entries for SeedRolesAsync()." },
   { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/NavigationModuleSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.navigationModules", "module": "{moduleCode}" },
+  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/NavigationSectionSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.navigationSections", "module": "{moduleCode}", "description": "MANDATORY when sections defined. Seeds section-level navigation entries (list, dashboard, etc.) with full absolute routes." },
   { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/PermissionsSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.permissions", "module": "{moduleCode}" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/RolesSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.roles", "module": "{moduleCode}" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/TenantSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.tenants", "module": "{moduleCode}" },
-  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/UserSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.users", "module": "{moduleCode}" },
+  { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/RolesSeedData.cs", "type": "SeedData", "category": "core", "source": "specification.seedDataCore.rolePermissions", "module": "{moduleCode}" },
   { "path": "src/Infrastructure/Persistence/Seeding/Data/{ModuleName}/{Entity}SeedData.cs", "type": "SeedData", "category": "business", "source": "specification.seedDataBusiness.{module}", "module": "{moduleCode}" }
 ]
 ```

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

@@ -17,7 +17,7 @@ This document consolidates all robustness checks implemented across the business
 
 Ensures each module has ALL required components before being marked as "specified". Prevents incomplete modules from reaching step-04 consolidation.
 
-### Checks (30 total)
+### Checks (31 total)
 
 #### SECTION 1: Data Model (3 checks)
 
@@ -50,38 +50,41 @@ Ensures each module has ALL required components before being marked as "specifie
 | # | Check | Minimum | Blocking | Rationale |
 |---|-------|---------|----------|-----------|
 | 4.1 | Permissions count | ≥5 | YES | CRUD (4) + 1 business action minimum |
-| 4.2 | Permission format | `business.{app}.{module}.{resource}.{action}` | YES | Wrong format breaks RBAC system |
+| 4.2 | Permission format | Module: `business.{app}.{module}.{action}` or Section: `business.{app}.{module}.{section}.{action}` | YES | Wrong format breaks RBAC system |
 | 4.3 | Role permissions | All roles have ≥1 permission | YES | Roles without permissions are useless |
 
-#### SECTION 5: UI & Navigation (3 checks)
+#### SECTION 5: UI & Navigation (4 checks)
 
 | # | Check | Minimum | Blocking | Rationale |
 |---|-------|---------|----------|-----------|
 | 5.1 | Sections count | ≥2 | YES | Modules need list + form minimum |
 | 5.2 | Wireframes count | 1 per section | YES | EVERY section MUST have wireframe |
 | 5.3 | Navigation entries | ≥1 | YES | Module must be accessible in menu |
+| 5.4 | Navigation route patterns | No `/list` or `/detail/:id` suffixes | YES | list route = module route (index), detail route = module + /:id. FORBIDDEN: `/module/list`, `/module/detail/:id` |
 
 #### SECTION 6: I18N & Messages (3 checks)
 
 | # | Check | Minimum | Blocking | Rationale |
 |---|-------|---------|----------|-----------|
 | 6.1 | i18n keys count | ≥42 | YES | Entities, fields, messages, validation, navigation |
-| 6.2 | i18n languages | All keys have 4 languages (fr/en/nl/de) | YES | Missing translations break multi-language |
+| 6.2 | i18n languages | All keys have 4 languages (fr/en/it/de) | YES | Missing translations break multi-language |
 | 6.3 | Messages count | ≥4 | YES | 1 success, 1 error, 1 warning, 1 info minimum |
 
 #### SECTION 7: Seed Data (2 checks)
 
 | # | Check | Minimum | Blocking | Rationale |
 |---|-------|---------|----------|-----------|
-| 7.1 | CORE seed data sections | All 5 sections present | YES | Missing CORE data breaks deployment |
+| 7.1 | CORE seed data sections | All 7 sections present | YES | Missing CORE data breaks deployment |
 | 7.2 | Business seed data | Template defined | NO (WARNING) | Helps with testing |
 
 **CORE sections required:**
 1. `navigationModules`
-2. `navigationTranslations`
-3. `permissions`
-4. `rolePermissions`
-5. `permissionConstants`
+2. `navigationSections`
+3. `navigationResources`
+4. `navigationTranslations`
+5. `permissions`
+6. `rolePermissions`
+7. `permissionConstants`
 
 #### SECTION 8: API Endpoints (2 checks)
 

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

@@ -90,15 +90,15 @@ IF entity has lifeCycles:
 ### 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.sections[]` entry with `code: "detail"`, `navigation: "hidden"`, route `/business/{app}/{module}/: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`
+- **From list**: row click action `navigate:detail` → `/business/{app}/{module}/{id}`
+- **Back button**: detail header → `/business/{app}/{module}`
 - **Route registration**: route MUST be registered in frontend routing with `:id` parameter
 
 ## Status/Lifecycle Enhancement

package/templates/skills/business-analyse/references/team-orchestration.md

@@ -85,13 +85,21 @@ Task({
 - Reason: later modules may reference entities/FKs from earlier modules
 - **Future optimization**: modules in the same dependency layer with no cross-refs COULD run in parallel
 
+### 2d. After Spawning — Wait for Agent Message
+
+After calling `Task()` to spawn the module agent, the team lead **MUST WAIT** for the agent to send a message.
+Messages from teammates are delivered automatically — do NOT poll or re-spawn.
+
+The agent will send `PROPOSAL_READY:{moduleCode}` when its specification is complete.
+This may take several minutes. The team lead does nothing until the message arrives.
+
 ---
 
 ## 3. Propose & Review Protocol
 
 ### 3a. Team Lead Receives PROPOSAL_READY
 
-After the agent finishes specifying a module, it sends:
+The module agent sends this message when specification is complete:
 
 ```
 PROPOSAL_READY:{moduleCode}
@@ -130,9 +138,9 @@ PROPOSAL_READY:{moduleCode}
 - ...
 ```
 
-### 3b. Team Lead Presents to User
+### 3b. Present to User and Handle Response
 
-Format the proposal for user review:
+**Step 1:** Format and display the proposal:
 
 ```
 ═══════════════════════════════════════════════════════════
@@ -144,7 +152,7 @@ Format the proposal for user review:
 ─────────────────────────────────────────────────────────
 ```
 
-Then ask user via AskUserQuestion:
+**Step 2:** Ask the user via AskUserQuestion:
 
 ```
 Validez-vous cette specification ?
@@ -154,9 +162,9 @@ Options:
   3. "Voir detail" → team lead reads module feature.json and displays full content
 ```
 
-### 3c. Approval Flow
+**Step 3 — IMMEDIATELY after AskUserQuestion returns, handle the response:**
 
-**If user approves:**
+**IF user selected "Valider" (approve):**
 ```
 SendMessage({
   type: "message",
@@ -165,9 +173,12 @@ SendMessage({
   summary: "{moduleCode} approved by user"
 })
 ```
-→ Agent writes final status, sends MODULE_COMPLETE, and shuts down.
+→ CRITICAL: You MUST send this message. Do NOT skip this step.
+→ Then WAIT for the agent to send `MODULE_COMPLETE:{moduleCode}` (see §4).
 
-**If user requests modifications:**
+**IF user selected "Modifier" (revision):**
+→ Ask user for specific feedback via AskUserQuestion
+→ Then send:
 ```
 SendMessage({
   type: "message",
@@ -176,14 +187,14 @@ SendMessage({
   summary: "{moduleCode} revision requested"
 })
 ```
-→ Agent applies changes, re-validates, sends new PROPOSAL_READY.
+→ Then WAIT for the agent to send a new `PROPOSAL_READY` → go back to Step 1.
 
-**If user wants to see detail:**
-→ Team lead reads module feature.json via ba-reader.readSection({feature_id, section})
-→ Displays relevant sections in detail
-→ Re-asks validation question
+**IF user selected "Voir detail":**
+→ Read module feature.json via ba-reader.readSection({feature_id, section})
+→ Display relevant sections in detail
+→ Go back to Step 2 (re-ask the validation question)
 
-### 3d. Revision Limits
+### 3c. Revision Limits
 
 - Max **3 revision cycles** per module
 - After 3 rejections: team lead asks user if they want to switch to **inline interactive mode** for this module
@@ -192,30 +203,42 @@ SendMessage({
 
 ---
 
-## 4. Module Completion & Advancement
+## 4. Module Completion & Agent Shutdown
+
+When the team lead receives `MODULE_COMPLETE:{moduleCode}` from the agent, execute these steps **IN ORDER**:
 
-When agent sends MODULE_COMPLETE:
+### 4a. Update Tracking
 
 ```javascript
-// Update tracking
 teamContext.completedModules.push(moduleCode);
 teamContext.currentModuleIdx++;
 
-// Update master feature.json
 ba-writer.advanceModuleLoop({feature_id});
 ba-writer.updateModuleStatus({feature_id, moduleCode, status: "specified"});
 
-// Display progress
 Display: "✓ Module {moduleCode} specified ({completedModules.length}/{moduleOrder.length})"
+```
+
+### 4b. Shutdown Agent (MANDATORY — do NOT skip)
+
+**IMMEDIATELY** after receiving MODULE_COMPLETE, send shutdown_request to terminate the agent:
 
-// Shutdown agent
+```
 SendMessage({
   type: "shutdown_request",
   recipient: "mod-{moduleCode}",
   content: "Module complete, shutting down"
-});
+})
 ```
 
+The agent will respond with `shutdown_response approve: true` and terminate.
+**Wait for the agent to confirm shutdown** before spawning the next agent.
+
+> **WARNING:** If you skip this step, the agent will remain running indefinitely.
+> The agent CANNOT self-terminate — it NEEDS this shutdown_request from you.
+
+### 4c. Next Module or Consolidation
+
 If more modules remain → spawn next module agent (go to §2).
 If all modules complete → proceed to §5 (Consolidation).
 
@@ -346,13 +369,21 @@ Display final status to user. If quality gate PASS → ready for /ralph-loop.
 After handoff complete:
 
 ```javascript
-// Shutdown any remaining agents
-for (const agentName of ["consolidation", "handoff"]) {
+// Safety net: shutdown ALL remaining agents (module agents + consolidation + handoff)
+// Module agents should already be shut down in §4b, but this catches any missed ones.
+const allAgents = [
+  ...teamContext.moduleOrder.map(m => `mod-${m}`),
+  "consolidation",
+  "handoff"
+];
+
+for (const agentName of allAgents) {
   SendMessage({
     type: "shutdown_request",
     recipient: agentName,
     content: "Workflow complete"
   });
+  // Ignore errors for already-terminated agents
 }
 
 // Delete team
@@ -361,6 +392,9 @@ TeamDelete();
 Display: "═══ Business-analyse complete — Team cleaned up ═══"
 ```
 
+> **Note:** Sending shutdown_request to an already-terminated agent is harmless.
+> This safety net ensures no orphan agents remain running.
+
 ---
 
 ## 8. Error Recovery

package/templates/skills/business-analyse/references/ui-resource-cards.md

@@ -8,7 +8,7 @@
 {
   "code": "list",
   "labels": { "fr": "Liste", "en": "List", "it": "Elenco", "de": "Liste" },
-  "route": "/business/{app}/{module}/list",
+  "route": "/business/{app}/{module}",
   "icon": "list",
   "permission": "business.{app}.{module}.read",
   "wireframe": "{module}-list",
@@ -81,7 +81,7 @@
 {
   "code": "detail",
   "labels": { "fr": "Détail", "en": "Detail", "it": "Dettaglio", "de": "Detail" },
-  "route": "/business/{app}/{module}/detail/:id",
+  "route": "/business/{app}/{module}/:id",
   "icon": "file-text",
   "permission": "business.{app}.{module}.read",
   "wireframe": "{module}-detail",
@@ -238,7 +238,7 @@ A wireframe without `componentMapping` or `layout` will FAIL validation in step
     "type": "page",
     "regions": [
       { "id": "header", "position": "top", "components": [
-        { "type": "BackButton", "target": "/business/{app}/{module}/list" },
+        { "type": "BackButton", "target": "/business/{app}/{module}" },
         { "type": "DetailHeader", "resourceRef": "{module}-detail-header" },
         { "type": "StatusBadge", "resourceRef": "{module}-status" }
       ]},

package/templates/skills/business-analyse/references/validation-checklist.md

@@ -115,10 +115,10 @@ const checklist = {
   },
 
   permissionFormat: {
-    check: "All permissions use full format: business.{app}.{module}.{resource}.{action}",
+    check: "All permissions use correct format: module-level business.{app}.{module}.{action} or section-level business.{app}.{module}.{section}.{action}",
     status: validatePermissionFormat() ? "PASS" : "FAIL",
     blocking: true,
-    details: "Wrong format breaks RBAC system"
+    details: "Wrong format breaks RBAC system. Module-level = 4 segments, section-level = 5 segments."
   },
 
   rolePermissions: {
@@ -168,6 +168,24 @@ const checklist = {
     details: "Module must be accessible in menu"
   },
 
+  navigationRoutePatterns: {
+    check: "Navigation routes do NOT contain CRUD suffixes (/list, /detail/:id)",
+    status: (() => {
+      const allRoutes = [
+        ...(specification.seedDataCore?.navigationSections || []).map(s => s.route),
+        ...(specification.sections || []).map(s => s.route),
+        ...(specification.navigation?.entries || []).map(e => e.route)
+      ].filter(Boolean);
+      const forbidden = allRoutes.filter(r => r.match(/\/list$/) || r.match(/\/detail\/:id$/));
+      return forbidden.length === 0 ? "PASS" : "FAIL";
+    })(),
+    blocking: true,
+    details: "FORBIDDEN: /module/list (use /module), /module/detail/:id (use /module/:id). " +
+             "list route = module route (React Router index route). " +
+             "detail route = module route + /:id (React Router :id child). " +
+             "Other sections (dashboard, approve) add /{section} normally."
+  },
+
   // SECTION 6: I18N & MESSAGES (BLOCKING)
   i18nKeys: {
     minimum: 42,  // Realistic minimum for a module
@@ -178,7 +196,7 @@ const checklist = {
   },
 
   i18nLanguages: {
-    check: "All i18n keys have 4 languages (fr, en, nl, de)",
+    check: "All i18n keys have 4 languages (fr, en, it, de)",
     status: validateI18nCompleteness() ? "PASS" : "FAIL",
     blocking: true,
     details: "Missing translations break multi-language support"

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

@@ -26,7 +26,7 @@
           "id": { "type": "string", "pattern": "^UC-[A-Z]{2,4}-\\d{3}$", "description": "Module-prefixed UC ID (e.g., UC-RM-001)" },
           "name": { "type": "string" },
           "primaryActor": { "type": "string" },
-          "permission": { "type": "string", "description": "business.{app}.{module}.{action}" },
+          "permission": { "type": "string", "description": "Module-level: business.{app}.{module}.{action} or section-level: business.{app}.{module}.{section}.{action}" },
           "preconditions": { "type": "array", "items": { "type": "string" } },
           "postconditions": { "type": "array", "items": { "type": "string" } },
           "mainScenario": { "type": "array", "items": { "type": "string" } },
@@ -82,7 +82,7 @@
             "type": "object",
             "required": ["path", "action"],
             "properties": {
-              "path": { "type": "string", "description": "business.{app}.{module}.{action}" },
+              "path": { "type": "string", "description": "Module-level: business.{app}.{module}.{action} or section-level: business.{app}.{module}.{section}.{action}" },
               "action": { "type": "string", "enum": ["read", "create", "update", "delete", "export", "import", "admin", "*"] },
               "description": { "type": "string" }
             }
@@ -382,8 +382,36 @@
     },
     "seedDataCore": {
       "type": "object",
-      "description": "7 mandatory SmartStack core SeedData definitions (modules, sections, resources, translations, permissions, rolePermissions, permissionConstants)",
+      "description": "9 mandatory SmartStack core SeedData definitions (navigationApplications, applicationRoles, modules, sections, resources, translations, permissions, rolePermissions, permissionConstants)",
       "properties": {
+        "navigationApplications": {
+          "type": "array",
+          "description": "Level 2 (Application) navigation entry for core.nav_Applications table. Created ONCE per application (FIRST). Provides ApplicationId for modules and roles.",
+          "items": {
+            "type": "object",
+            "required": ["code", "label", "icon", "route"],
+            "properties": {
+              "code": { "type": "string", "description": "Application code (PascalCase, e.g., HumanResources)" },
+              "label": { "type": "string", "description": "Application label in default language" },
+              "icon": { "type": "string", "description": "Lucide icon name" },
+              "route": { "type": "string", "description": "Full route path (e.g., /business/human-resources)" },
+              "sort": { "type": "integer", "description": "Display order" }
+            }
+          }
+        },
+        "applicationRoles": {
+          "type": "array",
+          "description": "Application-scoped role definitions (admin, manager, contributor, viewer). Created ONCE per application. Used by SeedRolesAsync() in IClientSeedDataProvider.",
+          "items": {
+            "type": "object",
+            "required": ["code", "name", "permissions"],
+            "properties": {
+              "code": { "type": "string", "description": "Role code (e.g., admin, manager, contributor, viewer)" },
+              "name": { "type": "string", "description": "Human-readable role name" },
+              "permissions": { "type": "string", "description": "Permission level: wildcard(*), CRU, CR, R" }
+            }
+          }
+        },
         "navigationModules": {
           "type": "array",
           "items": {
@@ -406,7 +434,7 @@
             "type": "object",
             "required": ["code", "label", "icon", "route", "parentCode", "permission"],
             "properties": {
-              "code": { "type": "string", "description": "Section code (list, detail, create, dashboard)" },
+              "code": { "type": "string", "description": "Section code (list, detail, dashboard, approve, import, etc.)" },
               "label": { "type": "string", "description": "Section label in default language (fr)" },
               "icon": { "type": "string", "description": "Lucide icon name" },
               "route": { "type": "string", "description": "Full route path" },
@@ -486,7 +514,7 @@
         "type": "object",
         "required": ["code", "labels", "route", "permission", "wireframe", "useCases", "resources"],
         "properties": {
-          "code": { "type": "string", "description": "Section code (kebab-case: list, detail, create, dashboard)" },
+          "code": { "type": "string", "description": "Section code (kebab-case: list, detail, dashboard, approve, import, etc.)" },
           "labels": {
             "type": "object",
             "properties": {

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

@@ -17,6 +17,18 @@ next_step: steps/step-03b-ui.md
 - **ID NAMING RULE:** All IDs MUST include module prefix (BR-{CAT}-{PREFIX}-{NNN}, OBJ-{PREFIX}-{NNN}, etc.)
 - **SCHEMA CONFORMITY RULE:** ALL data MUST fit within feature-schema.json structure
 
+## MODE DETECTION (inherited from step-03a1)
+
+> **CRITICAL: Re-check your execution mode before proceeding.**
+
+**IF you are running as a TEAM AGENT** (your prompt contains `PROPOSE & REVIEW` or `team-lead` as recipient):
+  → **NEVER** use `AskUserQuestion` — replace ALL user interactions with ULTRATHINK autonomous decisions
+  → You are in autonomous mode — make all choices based on decomposition data + SmartStack conventions
+  → Do NOT present options to the user — you PROPOSE to the team lead via SendMessage, not to the user
+
+**IF you are running in the MAIN CONVERSATION** (classic inline mode):
+  → Normal interactive mode — use `AskUserQuestion` as documented below
+
 ## YOUR TASK
 
 Define the module's analysis section: objectives, entities (with attributes and relationships), business rules, process flow, and data lifecycle.

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

@@ -14,6 +14,18 @@ next_step: steps/step-03c-compile.md
 - ALWAYS use ULTRATHINK mode
 - This step is EXECUTED ONCE PER MODULE, after step-03a1-setup.md and step-03a2-analysis.md
 - **WIREFRAME RULE:** Every section MUST have a wireframe in `specification.uiWireframes[]`. No section without a validated mockup.
+
+## MODE DETECTION (inherited from step-03a1)
+
+> **CRITICAL: Re-check your execution mode before proceeding.**
+
+**IF you are running as a TEAM AGENT** (your prompt contains `PROPOSE & REVIEW` or `team-lead` as recipient):
+  → **NEVER** use `AskUserQuestion` — replace ALL wireframe validations with ULTRATHINK self-review
+  → Generate wireframes autonomously, self-validate them, move on
+  → Do NOT ask the user to validate mockups — the team lead handles review after PROPOSAL_READY
+
+**IF you are running in the MAIN CONVERSATION** (classic inline mode):
+  → Normal interactive mode — display wireframes then ask for validation via `AskUserQuestion`
 - **ID NAMING RULE (MANDATORY, NO EXCEPTION):**
   All IDs MUST include a module prefix to guarantee application-wide uniqueness.
   The prefix is derived from the module code initials (2-4 chars):
@@ -243,7 +255,7 @@ A wireframe without `componentMapping` or `layout` will FAIL validation in step
 
 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`
+- **Back button**: navigates to `/business/{app}/{module}`
 - **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
@@ -261,7 +273,7 @@ Transition buttons are contextual: only show actions allowed from the current st
 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`.
+6. **Create the detail section** in `specification.sections[]` with `navigation: "hidden"` and route `/business/{app}/{module}/: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