@atlashub/smartstack-cli 3.37.0 → 3.39.0

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

@@ -29,8 +29,8 @@ All BA outputs are stored in up to **three levels** of feature.json, enriched pr
 > **Backward compatibility:** If only 1 application is identified, the project level is NOT created. The application-level feature.json remains the master (current behavior).
 
 ### Application-Level (Master)
-**Path:** `docs/{context}/{app}/business-analyse/v{X.Y}/feature.json`
-**Schema:** `docs/{context}/{app}/business-analyse/schemas/application-schema.json` (deployed to project by step-00)
+**Path:** `docs/{app}/business-analyse/v{X.Y}/feature.json`
+**Schema:** `docs/{app}/business-analyse/schemas/application-schema.json` (deployed to project by step-00)
 **$schema:** `"../schemas/application-schema.json"` (relative in feature.json)
 
 | Step | Section enriched | Status after |
@@ -42,11 +42,9 @@ All BA outputs are stored in up to **three levels** of feature.json, enriched pr
 | 04-consolidation | consolidation | consolidated |
 | 05-handoff | (per-module handoff) | handed-off |
 
-> **{context}** = `business` (default) | `platform` | `personal` — determined per application. In standalone mode, always `business`.
-
 ### Module-Level (Per Module)
-**Path:** `docs/{context}/{app}/{module}/business-analyse/v{X.Y}/feature.json`
-**Schema:** `docs/{context}/{app}/business-analyse/schemas/feature-schema.json` (deployed to project by step-00)
+**Path:** `docs/{app}/{module}/business-analyse/v{X.Y}/feature.json`
+**Schema:** `docs/{app}/business-analyse/schemas/feature-schema.json` (deployed to project by step-00)
 **$schema:** `"../../../business-analyse/schemas/feature-schema.json"` (relative in feature.json)
 
 | Step | Section enriched | Status after |
@@ -61,7 +59,7 @@ All BA outputs are stored in up to **three levels** of feature.json, enriched pr
 - **ba-writer**: Writes/updates feature.json (create, enrichSection, updateStatus, createVersion, createApplicationFeature, createProjectFeature, enrichApplicationRegistry, advanceModuleLoop, advanceApplicationLoop)
 - **ba-reader**: Reads feature.json (findFeature, findProjectFeature, readSection, answerQuestion, getSummaryForSkill, readApplicationContext, getCompletedModulesSummary, getCompletedApplicationsSummary)
 
-**Schemas:** Deployed to project at `docs/{context}/{app}/business-analyse/schemas/` (10 files, including project-schema.json). Source: `schemas/` in skill directory. Every feature.json includes `$schema` relative reference.
+**Schemas:** Deployed to project at `docs/{app}/business-analyse/schemas/` (10 files, including project-schema.json). Source: `schemas/` in skill directory. Every feature.json includes `$schema` relative reference.
 
 ### Workflow Modes
 
@@ -73,35 +71,34 @@ All BA outputs are stored in up to **three levels** of feature.json, enriched pr
 
 ---
 
-## 5-Level Navigation Hierarchy (SmartStack)
+## 4-Level Navigation Hierarchy (SmartStack)
 
 > **This is the structuring principle of the entire BA workflow.**
 
 The BA aligns with the SmartStack navigation hierarchy:
 
 ```
-Level 1: Context (business)
-  Level 2: Application (Sales)
-       Level 3: Module (Customers)
-            Level 4: Section (list)              ← sidebar nav
-                 Level 5: Resource (customer-grid)
-                 Level 5: Resource (customer-filters)
-            Level 4: Section (detail) [hidden]   ← reached by row click, route :id
-                 Level 5: Resource (customer-detail-header)
-                 Level 5: Resource (customer-detail-tabs)
-                 Level 5: Resource (customer-info-card)
-                 Level 5: Resource (customer-orders-grid)   ← relation tab
-                 Level 5: Resource (customer-history)        ← audit tab
-       Level 3: Module (Orders)
-            Level 4: Section (list)              ← sidebar nav
-            Level 4: Section (detail) [hidden]   ← reached by row click
-            Level 4: Section (approve)           ← sidebar nav (workflow)
+Level 1: Application (Sales)
+     Level 2: Module (Customers)
+          Level 3: Section (list)              ← sidebar nav
+               Level 4: Resource (customer-grid)
+               Level 4: Resource (customer-filters)
+          Level 3: Section (detail) [hidden]   ← reached by row click, route :id
+               Level 4: Resource (customer-detail-header)
+               Level 4: Resource (customer-detail-tabs)
+               Level 4: Resource (customer-info-card)
+               Level 4: Resource (customer-orders-grid)   ← relation tab
+               Level 4: Resource (customer-history)        ← audit tab
+     Level 2: Module (Orders)
+          Level 3: Section (list)              ← sidebar nav
+          Level 3: Section (detail) [hidden]   ← reached by row click
+          Level 3: Section (approve)           ← sidebar nav (workflow)
 ```
 
-**CRITICAL — Application identification (Level 2):**
+**CRITICAL — Application identification (Level 1):**
 The application is formally identified in step-01b (ALWAYS, even for single-app mode):
 - Code: PascalCase (e.g., "HumanResources")
-- Route: kebab-case (e.g., "/business/human-resources")
+- Route: kebab-case (e.g., "/human-resources")
 - Icon: Lucide icon name
 - Sort order: position in navigation
 This creates the `seedDataCore.navigationApplications` entry that links modules to their parent application.
@@ -109,24 +106,24 @@ The `seedDataCore.applicationRoles` entries are also built from `cadrage.applica
 
 | BA Phase | Levels treated | What is defined |
 |----------|---------------|-----------------|
-| Cadrage (step-01) | Context + Application | Problem, stakeholders, scope, application-level roles |
+| Cadrage (step-01) | Application | Problem, stakeholders, scope, application-level roles |
 | Decomposition (step-02) | Modules | Module list, dependencies, processing order |
-| Specification (step-03) | Module -> Sections -> Resources | Entities, BR, UC, permissions, ASCII/SVG mockups per section |
+| Specification (step-03) | Module → Sections → Resources (levels 2-3-4) | Entities, BR, UC, permissions, ASCII/SVG mockups per section |
 | Consolidation (step-04) | Cross-module | Interactions, permission coherence, E2E flows |
 | Handoff (step-05) | All levels | Implementation mapping, prd.json |
 
 ### Route patterns
 ```
-/business/{application}/{module}                         ← list section (= module route, NO /list suffix)
-/business/{application}/{module}/:id                     ← detail page (= module route + /:id, NO /detail prefix)
-/business/{application}/{module}/{section}               ← other sidebar sections (dashboard, approve, import, etc.)
+/{application}/{module}                         ← list section (= module route, NO /list suffix)
+/{application}/{module}/:id                     ← detail page (= module route + /:id, NO /detail prefix)
+/{application}/{module}/{section}               ← other sidebar sections (dashboard, approve, import, etc.)
 ```
 
 **Detail page routing:**
 - The detail page uses a parameterized route with `:id`
 - It is NOT registered as a sidebar navigation entry (`navigation: "hidden"`)
 - It is reached by clicking a row in the `list` section (action: `navigate:detail`)
-- The back button navigates to `/business/{application}/{module}`
+- The back button navigates to `/{application}/{module}`
 - Route MUST be registered in frontend routing (App.tsx) alongside the list route
 
 > **ROUTE SPECIAL CASES (list and detail sections):**
@@ -165,29 +162,6 @@ The `seedDataCore.applicationRoles` entries are also built from `cadrage.applica
 
 ---
 
-## Business Context Validation
-
-```
-validate_business_context(context, workflow_mode):
-  IF workflow_mode === "project" THEN
-    // In project mode, applications can target any context
-    IF context IN ['business', 'platform', 'personal'] THEN
-      RETURN true
-    END IF
-    ERROR "Invalid context '${context}'. Allowed: business, platform, personal"
-    RETURN false
-  ELSE
-    // In standalone mode, only business context is allowed
-    IF context IN ['platform', 'personal', 'system'] THEN
-      ERROR "BA restricted to 'business' context in standalone mode. Use multi-application project mode for other contexts."
-      RETURN false
-    END IF
-    RETURN true
-  END IF
-```
-
-**CRITICAL:** In standalone mode (single application), BA works ONLY for the `business` context. In project mode (multi-application), each application can target `business`, `platform`, or `personal` contexts.
-
 ---
 
 ## Feature Directory Structure
@@ -199,35 +173,34 @@ docs/
           project-schema.json
       v1.0/
           feature.json                    <- PROJECT master ($schema: ../schemas/project-schema.json)
-  {context}/                              <- "business" | "platform" | "personal"
-    {application}/
-        business-analyse/
-            schemas/                      <- JSON SCHEMAS (deployed by step-00)
-                feature-schema.json
-                application-schema.json
-                project-schema.json
-                sections/
-                    analysis-schema.json
-                    discovery-schema.json
-                    handoff-schema.json
-                    metadata-schema.json
-                    specification-schema.json
-                    validation-schema.json
-                shared/
-                    common-defs.json
-            v1.0/
-                feature.json              <- APPLICATION master ($schema: ../schemas/application-schema.json)
-        {module1}/
-            business-analyse/
-                v1.0/
-                    feature.json          <- MODULE detail ($schema: ../../../business-analyse/schemas/feature-schema.json)
-        {module2}/
-            business-analyse/
-                v1.0/
-                    feature.json          <- MODULE detail
+  {application}/
+      business-analyse/
+          schemas/                        <- JSON SCHEMAS (deployed by step-00)
+              feature-schema.json
+              application-schema.json
+              project-schema.json
+              sections/
+                  analysis-schema.json
+                  discovery-schema.json
+                  handoff-schema.json
+                  metadata-schema.json
+                  specification-schema.json
+                  validation-schema.json
+              shared/
+                  common-defs.json
+          v1.0/
+              feature.json                <- APPLICATION master ($schema: ../schemas/application-schema.json)
+      {module1}/
+          business-analyse/
+              v1.0/
+                  feature.json            <- MODULE detail ($schema: ../../../business-analyse/schemas/feature-schema.json)
+      {module2}/
+          business-analyse/
+              v1.0/
+                  feature.json            <- MODULE detail
 ```
 
-> In standalone mode (single app), `{context}` is always `business` and the project-level directory is NOT created.
+> In standalone mode (single app), the project-level directory is NOT created.
 
 **Ralph Loop Integration (generated by step-05):**
 
@@ -263,12 +236,12 @@ generate_project_id():
 
 | Level | Format | Example |
 |-------|--------|---------|
-| Module | `{context}.{app}.{module}.{action}` | `business.human-resources.employees.read` |
-| Section | `{context}.{app}.{module}.{section}.{action}` | `business.human-resources.employees.departments.read` |
+| Module | `{app}.{module}.{action}` | `human-resources.employees.read` |
+| Section | `{app}.{module}.{section}.{action}` | `human-resources.employees.departments.read` |
 
 > **Rule:** Use module-level permissions for standard CRUD. Use section-level permissions only when a section requires distinct access control (e.g., dashboard, approve, import).
 >
-> **CRITICAL — All segments use kebab-case:** Multi-word codes MUST have hyphens. `human-resources`, NOT `humanresources`. Matches NavRoute convention. SmartStack.app ref: `business.support-client.my-tickets.read`
+> **CRITICAL — All segments use kebab-case:** Multi-word codes MUST have hyphens. `human-resources`, NOT `humanresources`. Matches NavRoute convention. SmartStack.app ref: `support-client.my-tickets.read`
 
 | Action | Permission | Usage |
 |--------|------------|-------|
@@ -297,8 +270,8 @@ generate_project_id():
 
 | Type | Path |
 |------|------|
-| BA Feature | `docs/business/{app}/{module}/business-analyse/v{X.Y}/feature.json` |
-| User Guide | `docs/business/{app}/{module}/user-guide/v{X.Y}/guide.json` |
+| BA Feature | `docs/{app}/{module}/business-analyse/v{X.Y}/feature.json` |
+| User Guide | `docs/{app}/{module}/user-guide/v{X.Y}/guide.json` |
 | i18n | `web/smartstack-web/src/i18n/locales/{lang}/` |
 
 ---
@@ -397,7 +370,6 @@ Le champ `language` dans `feature.json.metadata.language` definit la langue :
 {
   "project": "{Name}",
   "lastFeatureId": 0,
-  "context": "business",
   "language": "fr",
   "standards": ["BABOK-v3", "IEEE-830"],
   "contact": "support@atlshub.ch"

package/templates/skills/business-analyse/questionnaire/04-data.md

@@ -45,10 +45,10 @@
 >
 > | Concept | ❌ Wrong (entity attribute) | ✅ Correct (RBAC) |
 > |---------|---------------------------|-------------------|
-> | User role | `User.Role` property | Permission set `business.{app}.{module}.*` |
+> | User role | `User.Role` property | Permission set `{app}.{module}.*` |
 > | Access level | `User.AccessLevel` enum | Permission matrix per role |
-> | Is admin | `User.IsAdmin` boolean | `business.{app}.{module}.admin` permission |
-> | Can edit | `User.CanEdit` boolean | `business.{app}.{module}.update` permission |
+> | Is admin | `User.IsAdmin` boolean | `{app}.{module}.admin` permission |
+> | Can edit | `User.CanEdit` boolean | `{app}.{module}.update` permission |
 >
 > When Q4.2 asks for "important attributes", **exclude** any role/permission/access concept.
 

package/templates/skills/business-analyse/questionnaire/06-security.md

@@ -27,7 +27,7 @@
 
 ## Platform Permission
 
-**Format:** `business.{application}.{module}.{action}`
+**Format:** `{application}.{module}.{action}`
 
 | Action | Permission |
 |--------|------------|

package/templates/skills/business-analyse/questionnaire/13-cross-module.md

@@ -34,7 +34,7 @@
 | Event notification | MediatR notification | `OrderCreatedNotification` |
 | Cross-module query | Read-only DTO from other module | `IClientQueryService` |
 | Navigation link | Menu entry in NavRoute | `business/{app}/{module}` |
-| Shared permission | Permission hierarchy | `business.{app}.*` covers all modules |
+| Shared permission | Permission hierarchy | `{app}.*` covers all modules |
 
 ## Elicitation Guide
 

package/templates/skills/business-analyse/react/application-viewer.md

@@ -1,9 +1,9 @@
 # Application-Level Business Analyse Viewer
 
 > **Usage:** React component for application-level BA documentation within SmartStack web app
-> **Route:** `/docs/business/{app}` (application overview)
-> **Data source:** `docs/business/{app}/business-analyse/v{X.Y}/feature.json` (scope: "application")
-> **Linked to:** Module viewers at `/docs/business/{app}/{module}`
+> **Route:** `/docs/{app}` (application overview)
+> **Data source:** `docs/{app}/business-analyse/v{X.Y}/feature.json` (scope: "application")
+> **Linked to:** Module viewers at `/docs/{app}/{module}`
 
 ---
 
@@ -23,7 +23,7 @@ interface ApplicationAnalyseViewerProps {
 ```typescript
 // In app router configuration
 {
-  path: '/docs/business/:app',
+  path: '/docs/:app',
   component: ApplicationAnalyseViewer,
   exact: true
 }
@@ -88,7 +88,7 @@ Grid/cards layout showing all modules:
 └─────────────────────┘  └─────────────────────┘
 ```
 
-Each card links to the module viewer: `/docs/business/{app}/{module}`
+Each card links to the module viewer: `/docs/{app}/{module}`
 
 Status colors:
 - ✓ Specified (green)
@@ -141,10 +141,10 @@ Per-Module Permission Paths:
 ┌──────────────┬──────────────────────────────────────────┐
 │ Module       │ Permission Paths                         │
 ├──────────────┼──────────────────────────────────────────┤
-│ Customers    │ business.sales.customers.{read|create|…} │
-│ Products     │ business.sales.products.{read|create|…}  │
-│ Orders       │ business.sales.orders.{read|create|…}    │
-│ Invoices     │ business.sales.invoices.{read|create|…}  │
+│ Customers    │ sales.customers.{read|create|…}           │
+│ Products     │ sales.products.{read|create|…}            │
+│ Orders       │ sales.orders.{read|create|…}              │
+│ Invoices     │ sales.invoices.{read|create|…}            │
 └──────────────┴──────────────────────────────────────────┘
 ```
 
@@ -198,14 +198,14 @@ Cross-module permission matrix display.
 ## Data Loading
 
 ```typescript
-import type { ApplicationFeatureJson } from '../types/business-analyse';
+import type { ApplicationFeatureJson } from '../types/docs';
 
 export async function loadApplicationFeature(
   app: string,
   version: string
 ): Promise<ApplicationFeatureJson> {
   const response = await fetch(
-    `/docs/business/${app}/business-analyse/v${version}/feature.json`
+    `/docs/${app}/business-analyse/v${version}/feature.json`
   );
   return response.json();
 }
@@ -214,7 +214,7 @@ export async function listApplicationVersions(
   app: string
 ): Promise<string[]> {
   const response = await fetch(
-    `/api/docs/business/${app}/business-analyse/versions`
+    `/api/docs/${app}/business-analyse/versions`
   );
   return response.json();
 }

package/templates/skills/business-analyse/react/components.md

@@ -2,8 +2,8 @@
 
 > **Usage:** React component that renders feature.json directly
 > **Loaded in:** step-05b-deploy.md
-> **Data source (module):** `docs/business/{app}/{module}/business-analyse/v{X.Y}/feature.json`
-> **Data source (application):** `docs/business/{app}/business-analyse/v{X.Y}/feature.json`
+> **Data source (module):** `docs/{app}/{module}/business-analyse/v{X.Y}/feature.json`
+> **Data source (application):** `docs/{app}/business-analyse/v{X.Y}/feature.json`
 > **Related:** `react/application-viewer.md` for application-level view
 > **Context7:** /facebook/react, /lucide-icons/lucide-react
 
@@ -12,7 +12,7 @@
 ## BusinessAnalyseViewer Component
 
 ```tsx
-// web/smartstack-web/src/pages/docs/business/[app]/[module]/BusinessAnalyseViewer.tsx
+// web/smartstack-web/src/pages/docs/[app]/[module]/BusinessAnalyseViewer.tsx
 
 import { useState, useEffect } from 'react';
 import { Link, useParams } from 'react-router-dom';
@@ -33,8 +33,8 @@ import {
   BookOpen,
   Target
 } from 'lucide-react';
-import type { FeatureJson, FeatureStatus } from '@/types/business-analyse';
-import { loadFeature, listVersions } from '@/services/businessAnalyse';
+import type { FeatureJson, FeatureStatus } from '@/types/docs';
+import { loadFeature, listVersions } from '@/services/docs';
 
 // Status Badge Component (supports both module and application statuses)
 function StatusBadge({ status }: { status: FeatureStatus }) {
@@ -173,11 +173,7 @@ export function BusinessAnalyseViewer() {
           {t('breadcrumb.docs', 'Documentation')}
         </Link>
         <span>/</span>
-        <Link to="/docs/business" className="hover:text-[var(--color-primary-600)]">
-          {t('breadcrumb.business', 'Business')}
-        </Link>
-        <span>/</span>
-        <Link to={`/docs/business/${app}`} className="hover:text-[var(--color-primary-600)]">
+        <Link to={`/docs/${app}`} className="hover:text-[var(--color-primary-600)]">
           {feature.metadata.application}
         </Link>
         <span>/</span>
@@ -535,14 +531,14 @@ export function BusinessAnalyseViewer() {
       {/* Navigation Footer */}
       <div className="flex justify-between pt-6 border-t border-[var(--border-color)]">
         <Link
-          to={`/docs/business/${app}`}
+          to={`/docs/${app}`}
           className="flex items-center gap-2 text-[var(--text-secondary)] hover:text-[var(--color-primary-600)]"
         >
           <ArrowRight className="w-4 h-4 rotate-180" />
           {t('nav.backToApp', 'Back to Application')}
         </Link>
         <Link
-          to="/docs/business"
+          to="/docs"
           className="flex items-center gap-2 text-[var(--color-primary-600)]"
         >
           {t('nav.allModules', 'All Modules')}