@atlashub/smartstack-cli 4.80.0 → 5.0.0

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

@@ -1,117 +0,0 @@
-# Specification: Auto-Inference Rules
-
-> Reference for step-03-specify.md — convention/override depth auto-generation from entity definitions.
-
-## Entity Attribute → SmartTable Column
-
-| Attribute Type | Column Format | Sortable | Filterable | Notes |
-|---|---|---|---|---|
-| string + unique | text | yes | yes | clickAction: navigate:detail |
-| string | text | yes | yes | — |
-| enum / status | badge | yes | yes (multi-select) | colorMap from lifeCycles if exists |
-| FK:Entity | text (join .name) | yes | yes (EntityLookup) | Display related entity name, filter via searchable EntityLookup |
-| decimal | currency | yes | no | — |
-| int | number | yes | no | — |
-| datetime | date-relative | yes | yes (date-range) | — |
-| bool | boolean | yes | yes (toggle) | — |
-| text (long) | — | no | no | Hidden in table, visible in detail |
-
-## Entity Attribute → SmartForm Field
-
-| Attribute Type | Component | Required from | Notes |
-|---|---|---|---|
-| string | Input | entity.required | — |
-| string (multiline) | TextArea | entity.required | rows: 4 |
-| enum | Select | entity.required | source: enum name |
-| FK:Entity | EntityLookup | entity.required | source: target entity, searchable. Component: `@/components/ui/EntityLookup`. NEVER plain text input for FK Guid fields. Backend API MUST support `?search=` param. See `smartstack-frontend.md` section 6. |
-| FK:User (person role) | `EntityLookup` | entity.required | searchable dropdown searching Users by name + email. `<EntityLookup apiEndpoint="/api/administration/users" mapOption={(user) => ({id: user.id, label: `${user.firstName} ${user.lastName}`, sublabel: user.email})} />` |
-| decimal | NumberInput | entity.required | — |
-| int | NumberInput | entity.required | — |
-| datetime | DatePicker | entity.required | — |
-| bool | Toggle | — | default: false |
-
-## Auto-Generated UI Components by featureType
-
-> **RULE:** Sections are functional, not CRUD-based. `create`/`edit` are separate pages with own URL routes (`/create` and `/:id/edit`). `detail` is a tabbed page reached from `list`.
-
-| featureType | Sections (functional) | permissionMode | List page includes | Form pages | Detail page tabs |
-|---|---|---|---|---|---|
-| data-centric | list | `crud` | grid, filters, create button | `/create` page, `/:id/edit` page | Infos, {relations} |
-| data-centric | (detail — implicit) | `inherit` | — | — | — |
-| workflow | list | `crud` | grid, filters, create button | `/create` page, `/:id/edit` page | Infos, {relations}, Historique |
-| workflow | approve | `custom:approve,reject` | — | — | — |
-| integration | list | `crud` | grid, filters, config button | `/create` page, `/:id/edit` page | Infos, Config, Logs |
-| reporting | dashboard | `read-only` | — | — | — |
-| full-module | list | `crud` | grid, filters, create button | `/create` page, `/:id/edit` page | Infos, {relations}, Historique |
-| full-module | dashboard | `read-only` | — | — | — |
-
-> **RULE:** `detail` is NEVER a section with its own permission set. It is always `sectionType: view`, `permissionMode: inherit`. Detail pages inherit permissions from their parent module.
-
-## Component Generation Rules
-
-1. **list section:** SmartTable with all non-long-text attributes as columns, actions = [view, edit, delete], defaultSort = { createdAt, desc }. Create button navigates to `/create` page. Edit action navigates to `/:id/edit` page.
-2. **create page (`/create` route):** SmartForm (full page) with all writable attributes as fields, component inferred from type. Back button + form + submit. NEVER a modal.
-3. **edit page (`/:id/edit` route):** Same form as create but pre-filled with entity data. Full page with back button. NEVER a modal or inline toggle.
-4. **detail page (from list click):** TabPanel with: Info tab (all attributes read-only + edit button navigating to `/:id/edit`), relation tabs (child SmartTable for each 1:N relationship), History tab (if auditable). See "Detail Page Tab Auto-Inference" below for exact rules.
-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-03)
-
-# 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 `/{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` → `/{app}/{module}/{id}`
-- **Back button**: detail header → `/{app}/{module}`
-- **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:
-- list section: status column gets `format: badge`, `colorMap: stateMachine:{Entity}`
-- list section: rowActions get `showWhen` conditions based on state machine transitions
-- detail section: add StatusBadge resource + transition action buttons
-
-Write auto-generated sections to `specification.sections[]` via `ba-writer.enrichSection()`

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

@@ -1,108 +0,0 @@
----
-name: step-01-screens
-description: Define sections and resources with detailed UI specs per module
-model: opus
-next_step: steps/step-02-wireframes.md
----
-
-# Step 01 — Screens (Define Sections & Resources)
-
-## Objective
-
-For each module, define all sections and resources with detailed interface specifications: SmartTable columns, SmartForm fields with types, SmartDashboard KPIs, SmartKanban columns, SmartFilter filters, SmartCard layouts.
-
-## Context Recovery
-
-Re-read session variables (do NOT rely on LLM memory from prior skill invocation):
-```javascript
-const config = readJSON('.business-analyse/config.json').currentFeature;
-const { id: feature_id, docsDir: docs_dir, projectSlug, application: application_name,
-        applicationCode, language } = config;
-
-// Path helpers (ba-006)
-function toKebabCase(code) {
-  return code.replace(/([a-z0-9])([A-Z])/g, '$1-$2').replace(/([A-Z]+)([A-Z][a-z])/g, '$1-$2').toLowerCase();
-}
-function resolveModuleDir(appCode, moduleCode) {
-  return `${docs_dir}/${toKebabCase(appCode)}/${toKebabCase(moduleCode)}`;
-}
-```
-
-> **screens.json output (ba-006):** Written to `resolveModuleDir(appCode, moduleCode)/screens.json`
-> Example: `docs/projet-rh/v1.0/human-resources/employees/screens.json`
-
-## Prerequisites
-
-- `/business-analyse` completed (entities, usecases, permissions exist)
-- Module index.json accessible via ba-reader
-
-## Execution
-
-### 1. Load Analysis Data
-
-For each module (in dependency order from index.json):
-
-```
-Load via ba-reader:
-  - entities.json → entity attributes with types, relationships
-  - usecases.json → actor actions, CRUD operations
-  - permissions.json → role matrix, permission paths
-  - index.json → anticipatedSections from step-02
-```
-
-### 2. Define Sections & Resources
-
-For each module, transform anticipatedSections into detailed screen specs.
-
-> **SmartComponent templates & canonical output format:**
-> Load: `/references/smartcomponents-templates.md`
-> - All SmartComponent JSON examples (SmartTable, SmartForm, SmartDashboard, SmartKanban, SmartFilter, SmartCard)
-> - Canonical screens.json output format with `sections[]` wrapper
-
-### 3. Column/Field Type Mapping & Business Rules
-
-Map entity attribute types to UI component types and apply business rules for computed fields, lookups, and workflows.
-
-> **Type mapping, readonly rules, computed attribute handling, lookup detection, and workflow auto-detection:**
-> Load: `/references/screens-type-mapping.md`
-> - Column/field type mapping table
-> - Computed attribute rules (readonly on edit, absent on create)
-> - Readonly field rules (boolean only, no string values)
-> - SmartForm section location rules (list vs detail)
-> - Lookup field entity requirement (SmartForm + SmartFilter)
-> - SmartKanban auto-detection rule for workflow entities (status enum >= 3 options)
-> - SmartFilter mandatory rule for list sections with SmartTable
-
-### 4. Write screens.json
-
-For each module, write via ba-writer using the canonical `sections[]` format:
-
-> **CANONICAL FORMAT (MANDATORY):** screens.json MUST use the `sections[]` wrapper with `sectionCode`, `sectionLabel`, and `resources[]`.
-> The flat `screens[]` format is **DEPRECATED**.
-> All downstream consumers (business-analyse-html, business-analyse-handoff, business-analyse-develop) expect `sections[]`.
->
-> Load full format with examples: `/references/smartcomponents-templates.md`
-
-Update `index.json` with screens.json hash and status.
-
-## Validation Summary
-
-Run POST-CHECK validation after writing ALL screens.json files:
-
-> Load: `/references/screens-post-check.md`
-> - Complete validation script (10 checks: 8 BLOCKING + 2 WARNING)
-> - CHECK 1: Section resources (at least 1 per section)
-> - CHECK 2-3: Entity + permission references
-> - CHECK 4-5: SmartTable/SmartForm attribute references
-> - CHECK 6: Lookup field entity requirement
-> - CHECK 7: Computed attribute readonly handling
-> - CHECK 8: SmartFilter lookup entity requirement
-> - CHECK 9: SmartFilter mandatory for list sections with SmartTable
-> - CHECK 10: SmartKanban auto-detection for workflow entities
-
-**BLOCKING** errors must be fixed before proceeding to step-02.
-**WARNING** errors should be reviewed but do not block progress.
-
-## Transition
-
--> Step 02 (wireframes) — Generate visual mockups for each screen

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

@@ -1,155 +0,0 @@
----
-name: step-02-wireframes
-description: Generate wireframes (ASCII/HTML mockups) for each screen defined in step-01
-model: opus
-next_step: steps/step-03-navigation.md
----
-
-# Step 02 — Wireframes (Generate Mockups)
-
-## Objective
-
-Generate visual wireframes for each screen defined in screens.json. Each wireframe provides a concrete representation of the UI layout, component placement, and user interactions.
-
-## Prerequisites
-
-- Step 01 (screens) completed
-- screens.json exists for each module with detailed section/resource specs
-
-## Execution
-
-### 1. Load Screen Specs
-
-For each module, read screens.json via ba-reader.
-
-### 2. Generate Wireframes per Resource
-
-For each resource in each section, generate a wireframe object:
-
-**SmartTable wireframe:**
-```json
-{
-  "mockupFormat": "ascii",
-  "mockup": "+----------------------------------------------------------+\n| [Departement v] [Statut v]        [+ Nouveau employe]    |\n+------+----------------+---------------+--------+---------+\n| Code | Nom complet    | Departement   | Statut | Actions |\n+------+----------------+---------------+--------+---------+\n| E001 | Dupont Marie   | RH            | Actif  | [E] [S] |\n| E002 | Martin Pierre  | IT            | Conge  | [E] [S] |\n+------+----------------+---------------+--------+---------+\n| << 1 2 3 ... 10 >>                           25 par page |\n+----------------------------------------------------------+",
-  "elements": ["FilterBar", "DataGrid", "Pagination", "ActionButtons"],
-  "actions": ["filter", "sort", "create", "edit", "delete", "export"],
-  "componentMapping": [
-    { "wireframeElement": "FilterBar", "reactComponent": "SmartFilter" },
-    { "wireframeElement": "DataGrid", "reactComponent": "SmartTable" },
-    { "wireframeElement": "Pagination", "reactComponent": "SmartPagination" },
-    { "wireframeElement": "ActionButtons", "reactComponent": "SmartToolbar" }
-  ],
-  "layout": {
-    "type": "vertical",
-    "regions": ["filters", "grid", "pagination"]
-  },
-  "permissionsRequired": ["{AppCode}.{ModuleCode}.Read"]
-}
-```
-
-**SmartForm wireframe:**
-```json
-{
-  "mockupFormat": "ascii",
-  "mockup": "+----------------------------------------------------------+\n| Fiche Employe                              [Sauvegarder] |\n+----------------------------------------------------------+\n| [Informations] [Contrats] [Documents]                    |\n+----------------------------------------------------------+\n| Prenom:      [_______________]  Nom: [_______________]   |\n| Email:       [_______________]  Tel: [_______________]   |\n| Departement: [Selectionnez v ]  Poste: [_____________]   |\n| Date embauche: [__ /__ /____]   Statut: [Actif      v]  |\n+----------------------------------------------------------+",
-  "elements": ["TabBar", "FormFields", "SaveButton"],
-  "actions": ["save", "cancel", "tab-switch"],
-  "componentMapping": [
-    { "wireframeElement": "TabBar", "reactComponent": "SmartTabs" },
-    { "wireframeElement": "FormFields", "reactComponent": "SmartForm" },
-    { "wireframeElement": "SaveButton", "reactComponent": "SmartButton" }
-  ],
-  "layout": {
-    "type": "vertical",
-    "regions": ["header", "tabs", "form-body", "actions"]
-  },
-  "permissionsRequired": ["{AppCode}.{ModuleCode}.Update"]
-}
-```
-
-**SmartDashboard wireframe:**
-```json
-{
-  "mockupFormat": "ascii",
-  "mockup": "+----------------------------------------------------------+\n| Tableau de bord RH                                       |\n+-------------+-------------+-------------+----------------+\n| Total actifs| En conge    | Nouveaux    | Taux rotation  |\n|    156      |     12      |      8      |    3.2%        |\n+-------------+-------------+-------------+----------------+\n| [Repartition par dept (pie)]  [Evolution effectifs (bar)]|\n+----------------------------------------------------------+",
-  "elements": ["KPICards", "PieChart", "BarChart"],
-  "actions": ["filter-period", "export-report"],
-  "componentMapping": [
-    { "wireframeElement": "KPICards", "reactComponent": "SmartKPI" },
-    { "wireframeElement": "PieChart", "reactComponent": "SmartChart" },
-    { "wireframeElement": "BarChart", "reactComponent": "SmartChart" }
-  ],
-  "layout": {
-    "type": "grid",
-    "regions": ["kpi-row", "charts-row"]
-  },
-  "permissionsRequired": ["{AppCode}.{ModuleCode}.Read"]
-}
-```
-
-### 3. Enrich screens.json with Wireframes
-
-For each module, update screens.json to embed wireframes at the resource level:
-
-```json
-{
-  "sections": [
-    {
-      "sectionCode": "list",
-      "sectionLabel": "Liste des employes",
-      "resources": [
-        {
-          "code": "employees-grid",
-          "type": "SmartTable",
-          "columns": [ /* ... */ ],
-          "wireframe": {
-            "mockupFormat": "ascii",
-            "mockup": "...",
-            "elements": [...],
-            "componentMapping": [...],
-            "layout": {...}
-          }
-        }
-      ]
-    }
-  ]
-}
-```
-
-### 4. Write Updated screens.json
-
-Write via ba-writer for each module. Update index.json hashes.
-
-## Consumer Contract (wireframe field names)
-
-> **IMPORTANT:** Downstream consumers (`/business-analyse-html`) depend on these EXACT field names.
-> Any rename requires updating `business-analyse-html/steps/step-02-build-data.md` (wireframe mapping).
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `mockupFormat` | `"ascii"` \| `"html"` | Wireframe rendering format |
-| `mockup` | string | Wireframe content (ASCII art or HTML) |
-| `elements` | string[] | UI element names |
-| `componentMapping` | object[] | Wireframe element → React component mapping |
-| `layout` | object | Layout type and regions |
-| `permissionsRequired` | string[] | Permission paths needed |
-
-> **INTERDICTION:** `componentMapping` MUST use the canonical object format:
-> ```json
-> [{ "wireframeElement": "FilterBar", "reactComponent": "SmartFilter" }]
-> ```
-> The shorthand `[{ "FilterBar": "SmartFilter" }]` is **NOT valid** and will break downstream consumers.
-> Each entry MUST have both `wireframeElement` and `reactComponent` keys.
-
-## Validation
-
-- [ ] Every resource has a wireframe object
-- [ ] Every wireframe has a non-empty `mockup` field
-- [ ] Every wireframe has `elements[]` and `componentMapping[]`
-- [ ] Wireframe `permissionsRequired` references valid permission paths
-- [ ] All wireframes have `mockupFormat` set ("ascii" or "html")
-- [ ] Every `componentMapping` entry uses canonical format (`wireframeElement` + `reactComponent` keys, no shorthand)
-
-## Transition
-
--> Step 03 (navigation) — Define the complete navigation tree

package/templates/skills/business-analyse-design/steps/step-03-navigation.md

@@ -1,189 +0,0 @@
----
-name: step-03-navigation
-description: Define the complete navigation tree (routes, menus, breadcrumbs)
-model: opus
----
-
-# Step 03 — Navigation (Navigation Tree)
-
-## Objective
-
-Define the complete navigation tree for the project: routes, menus, breadcrumbs per application. Supports multi-app projects (uses `applications[]` array).
-
-## Prerequisites
-
-- Step 01 (screens) and Step 02 (wireframes) completed
-- screens.json exists for each module with sections and resources
-
-## Execution
-
-### 1. Load All Screens
-
-Read screens.json for every module via ba-reader. Collect all sections and resources.
-
-### 2. Build Navigation Tree
-
-Build the navigation hierarchy following SmartStack conventions:
-
-> **Route depth:** Max 3 segments: `/{app-code}/{module-code}/{section-code}`.
-> Use `:id` for detail sections (e.g., `/rh/employees/:id`).
-> Resources are components WITHIN a page, NOT separate routes.
-
-```
-Project
-  |-- Application 1 (e.g., HumanResources)
-  |   |-- Module 1 (e.g., Employees)
-  |   |   |-- Section "list"   → /rh/employees       (isDefault, showInMenu)
-  |   |   |-- Section "detail" → /rh/employees/:id   (showInMenu: false)
-  |   |   |-- Section "dashboard" → /rh/employees/dashboard (showInMenu)
-  |   |-- Module 2 (e.g., Absences)
-  |-- Application 2 (e.g., Billing)
-      |-- ...
-```
-
-### 3. Generate navigation.json
-
-> **Multi-app format is MANDATORY.** Even for single-app projects, use `applications[]` (array of 1).
-
-```json
-{
-  "applications": [
-    {
-      "code": "{AppCode}",
-      "name": "{AppName}",
-      "icon": "app-icon",
-      "route": "/{app-code}",
-      "modules": [
-        {
-          "code": "{ModuleCode}",
-          "name": "{ModuleName}",
-          "icon": "module-icon",
-          "route": "/{app-code}/{module-code}",
-          "permission": "{AppCode}.{ModuleCode}.Read",
-          "sections": [
-            {
-              "code": "{sectionCode}",
-              "label": "{sectionLabel}",
-              "route": "/{app-code}/{module-code}/{section-code}",
-              "icon": "section-icon",
-              "isDefault": false,
-              "showInMenu": true,
-              "resources": [
-                {
-                  "code": "{resourceCode}",
-                  "type": "{SmartTable|SmartForm|SmartDashboard|SmartKanban|SmartFilter}",
-                  "permission": "{AppCode}.{ModuleCode}.{Action}"
-                }
-              ]
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "menuItems": [
-    {
-      "label": "{AppName}",
-      "icon": "app-icon",
-      "route": "/{app-code}",
-      "children": [
-        {
-          "label": "{ModuleName}",
-          "icon": "module-icon",
-          "route": "/{app-code}/{module-code}",
-          "permission": "{AppCode}.{ModuleCode}.Read",
-          "children": [
-            {
-              "label": "{sectionLabel}",
-              "route": "/{app-code}/{module-code}/{section-code}",
-              "permission": "{AppCode}.{ModuleCode}.Read"
-            }
-          ]
-        }
-      ]
-    }
-  ],
-  "breadcrumbs": {
-    "/{app-code}/{module-code}/{section-code}": [
-      { "label": "{AppName}", "route": "/{app-code}" },
-      { "label": "{ModuleName}", "route": "/{app-code}/{module-code}" },
-      { "label": "{sectionLabel}", "route": "" }
-    ]
-  }
-}
-```
-
-**Section properties:**
-
-| Property | Type | Description |
-|----------|------|-------------|
-| `isDefault` | boolean | Default section for the module (typically `list`). Only ONE per module. |
-| `showInMenu` | boolean | `true` = visible in sidebar menu, `false` = accessible by navigation only (e.g., detail pages) |
-
-**menuItems rules:**
-
-| Rule | Description |
-|------|-------------|
-| App-level items have NO `permission` | Applications are visible to all authenticated users; permissions gate modules/sections |
-| Single visible section = no `children` | If a module has only ONE section with `showInMenu: true`, render a direct link (no submenu) |
-| Only `showInMenu: true` sections | Detail sections (`showInMenu: false`) are NOT included in menuItems |
-
-**Route conventions:**
-
-| Level | Format | Example |
-|-------|--------|---------|
-| Application | `/{app-code}` | `/rh` |
-| Module | `/{app-code}/{module-code}` | `/rh/employees` |
-| Section (list/default) | `/{app-code}/{module-code}` | `/rh/employees` (isDefault) |
-| Section (named) | `/{app-code}/{module-code}/{section-code}` | `/rh/employees/dashboard` |
-| Section (detail) | `/{app-code}/{module-code}/:id` | `/rh/employees/:id` |
-
-> **Max 3 segments.** Resources are components within a page, NOT separate routes.
-
-### 4. Write navigation.json
-
-Write via ba-writer at project level: `{docs_dir}/navigation.json` (e.g., `docs/projet-rh/v1.0/navigation.json`).
-Update index.json with navigation.json reference.
-
-## Validation
-
-- [ ] Every module in index.json has a corresponding navigation entry
-- [ ] Every section with `showInMenu: true` has a corresponding menu item
-- [ ] Every route is unique (no duplicates across all applications)
-- [ ] Module/section-level menu items have valid permission references
-- [ ] App-level menu items have NO permission (visible to all)
-- [ ] Breadcrumbs cover ALL routes (every route in `applications[].modules[].sections[]` must have a breadcrumb entry)
-- [ ] `isDefault: true` is set on exactly ONE section per module
-- [ ] Routes use max 3 segments (+ `:id` for detail)
-- [ ] Single-section modules have no `children` in menuItems
-
-## Completion Summary
-
-```
-================================================================
-  UI DESIGN COMPLETE
-================================================================
-
-| Module          | Sections | Resources | Wireframes |
-|-----------------|----------|-----------|------------|
-| {moduleCode}    | {count}  | {count}   | {count}    |
-| ...             | ...      | ...       | ...        |
-
-| Artifact        | Path                              |
-|-----------------|-----------------------------------|
-| screens.json    | {docs_dir}/{app-kebab}/{module-kebab}/screens.json |
-| navigation.json | {docs_dir}/navigation.json                        |
-
-NEXT STEPS:
-1. Run /business-analyse-html to produce the interactive HTML with mockups
-2. Client reviews the HTML (mockups, ERD, permission matrix)
-3. Run /business-analyse-review to apply corrections
-================================================================
-```
-
-## Status Update
-
-After writing all screens and navigation, update the application status:
-```javascript
-ba-writer.updateStatus({feature_id}, "designed")
-```