@atlashub/smartstack-cli 3.0.0 → 3.1.0

package/package.json

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

package/templates/agents/gitflow/merge.md

@@ -12,9 +12,48 @@ Safe PR merge with review checklist. Supports GitHub and Azure DevOps.
 
 ## EXECUTION SEQUENCE
 
-### 1. Detect Provider and Load PR Context
+### 1. Load GitFlow Config (MANDATORY)
 
 ```bash
+# Find and verify config exists
+CONFIG_FILE=""
+if [ -f ".claude/gitflow/config.json" ]; then
+  CONFIG_FILE=".claude/gitflow/config.json"
+elif [ -f ".gitflow/config.json" ]; then
+  CONFIG_FILE=".gitflow/config.json"
+else
+  # Try develop worktree
+  DEVELOP_PATH=$(git worktree list --porcelain 2>/dev/null | grep -A1 "branch refs/heads/develop" | grep "^worktree " | sed 's/^worktree //')
+  if [ -n "$DEVELOP_PATH" ] && [ -f "$DEVELOP_PATH/.claude/gitflow/config.json" ]; then
+    CONFIG_FILE="$DEVELOP_PATH/.claude/gitflow/config.json"
+  elif [ -n "$DEVELOP_PATH" ] && [ -f "$DEVELOP_PATH/.gitflow/config.json" ]; then
+    CONFIG_FILE="$DEVELOP_PATH/.gitflow/config.json"
+  fi
+fi
+
+# CRITICAL: Block if no config
+if [ -z "$CONFIG_FILE" ] || [ ! -f "$CONFIG_FILE" ]; then
+  echo "❌ GitFlow config not found"
+  echo "→ Run: /gitflow init"
+  exit 1
+fi
+
+# Extract config values
+GF_PROVIDER=$(grep -oP '"provider":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+GF_MAIN_BRANCH=$(grep -oP '"main":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+GF_DEVELOP_BRANCH=$(grep -oP '"develop":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+
+# Validate required values
+if [ -z "$GF_MAIN_BRANCH" ] || [ -z "$GF_DEVELOP_BRANCH" ]; then
+  echo "❌ Invalid GitFlow config (missing branches)"
+  exit 1
+fi
+```
+
+### 2. Detect Provider and Load PR Context
+
+```bash
+# Detect provider
 REMOTE_URL=$(git remote get-url origin 2>/dev/null)
 if [[ "$REMOTE_URL" == *"dev.azure.com"* ]]; then
   GIT_PROVIDER="azuredevops"
@@ -25,12 +64,23 @@ fi
 CURRENT=$(git rev-parse --abbrev-ref HEAD)
 BRANCH_TYPE=$(echo $CURRENT | cut -d'/' -f1)
 
+# Determine target branch (using config values)
+case "$BRANCH_TYPE" in
+  feature) TARGET="$GF_DEVELOP_BRANCH" ;;
+  release) TARGET="$GF_MAIN_BRANCH" ;;
+  hotfix)  TARGET="$GF_MAIN_BRANCH" ;;
+  *)       TARGET="$GF_DEVELOP_BRANCH" ;;
+esac
+
+echo "✓ Config loaded: $CONFIG_FILE"
+echo "✓ Branch: $CURRENT → Target: $TARGET"
+
 # Find PR for current branch
 # GitHub: gh pr list --head "$CURRENT"
 # Azure DevOps: az repos pr list --source-branch "$CURRENT"
 ```
 
-### 2. Determine Merge Strategy
+### 3. Determine Merge Strategy
 
 | Type | Strategy | Delete Branch |
 |------|----------|---------------|
@@ -38,7 +88,7 @@ BRANCH_TYPE=$(echo $CURRENT | cut -d'/' -f1)
 | Release | merge --no-ff | yes |
 | Hotfix | merge --no-ff | yes |
 
-### 3. Review Checklist
+### 4. Review Checklist
 
 Display review checklist:
 - Build status (pass/fail)
@@ -47,7 +97,7 @@ Display review checklist:
 - Conflicts (none/detected)
 - CI status (if available)
 
-### 4. Execute Merge
+### 5. Execute Merge
 
 **GitHub:**
 ```bash
@@ -67,7 +117,7 @@ az repos pr update --id $PR_ID --status completed --squash true --delete-source-
 az repos pr update --id $PR_ID --status completed --squash false --delete-source-branch true
 ```
 
-### 5. Verify Merge
+### 6. Verify Merge
 
 ```bash
 # Force update tracking refs
@@ -78,7 +128,7 @@ git fetch origin --prune --quiet
 MERGED=$(git branch -r --merged origin/$TARGET | grep "$CURRENT" | wc -l)
 ```
 
-### 6. Summary
+### 7. Summary
 
 ```
 PR MERGED

package/templates/agents/gitflow/pr.md

@@ -14,21 +14,68 @@ Create PR with auto-generated description, Azure DevOps and GitHub support.
 
 ## EXECUTION SEQUENCE
 
-### 1. Detect Provider and Branch Context
+### 1. Load GitFlow Config (MANDATORY)
 
 ```bash
-# Detect provider from remote URL
-REMOTE_URL=$(git remote get-url origin 2>/dev/null)
-if [[ "$REMOTE_URL" == *"dev.azure.com"* ]] || [[ "$REMOTE_URL" == *"visualstudio.com"* ]]; then
-  GIT_PROVIDER="azuredevops"
-  # Extract Azure DevOps details
+# Find and verify config exists
+CONFIG_FILE=""
+if [ -f ".claude/gitflow/config.json" ]; then
+  CONFIG_FILE=".claude/gitflow/config.json"
+elif [ -f ".gitflow/config.json" ]; then
+  CONFIG_FILE=".gitflow/config.json"
+else
+  # Try develop worktree
+  DEVELOP_PATH=$(git worktree list --porcelain 2>/dev/null | grep -A1 "branch refs/heads/develop" | grep "^worktree " | sed 's/^worktree //')
+  if [ -n "$DEVELOP_PATH" ] && [ -f "$DEVELOP_PATH/.claude/gitflow/config.json" ]; then
+    CONFIG_FILE="$DEVELOP_PATH/.claude/gitflow/config.json"
+  elif [ -n "$DEVELOP_PATH" ] && [ -f "$DEVELOP_PATH/.gitflow/config.json" ]; then
+    CONFIG_FILE="$DEVELOP_PATH/.gitflow/config.json"
+  fi
+fi
+
+# CRITICAL: Block if no config
+if [ -z "$CONFIG_FILE" ] || [ ! -f "$CONFIG_FILE" ]; then
+  echo "❌ GitFlow config not found"
+  echo "→ Run: /gitflow init"
+  exit 1
+fi
+
+# Extract config values
+GF_PROVIDER=$(grep -oP '"provider":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+GF_MAIN_BRANCH=$(grep -oP '"main":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+GF_DEVELOP_BRANCH=$(grep -oP '"develop":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+GF_REMOTE_URL=$(grep -oP '"remoteUrl":\s*"\K[^"]+' "$CONFIG_FILE" | head -1)
+
+# Validate required values
+if [ -z "$GF_MAIN_BRANCH" ] || [ -z "$GF_DEVELOP_BRANCH" ]; then
+  echo "❌ Invalid GitFlow config (missing branches)"
+  exit 1
+fi
+```
+
+### 2. Detect Provider and Branch Context
+
+```bash
+# Detect provider from config or remote URL
+if [ -z "$GF_PROVIDER" ]; then
+  REMOTE_URL=$(git remote get-url origin 2>/dev/null)
+  if [[ "$REMOTE_URL" == *"dev.azure.com"* ]] || [[ "$REMOTE_URL" == *"visualstudio.com"* ]]; then
+    GIT_PROVIDER="azuredevops"
+  else
+    GIT_PROVIDER="github"
+  fi
+else
+  GIT_PROVIDER="$GF_PROVIDER"
+fi
+
+# Extract Azure DevOps details if needed
+if [ "$GIT_PROVIDER" = "azuredevops" ]; then
+  REMOTE_URL="${GF_REMOTE_URL:-$(git remote get-url origin 2>/dev/null)}"
   [[ "$REMOTE_URL" =~ dev\.azure\.com/([^/]+)/([^/]+)/_git/([^/]+) ]] && {
     AZURE_ORG="${BASH_REMATCH[1]}"
     AZURE_PROJECT="${BASH_REMATCH[2]}"
     AZURE_REPO="${BASH_REMATCH[3]}"
   }
-else
-  GIT_PROVIDER="github"
 fi
 
 # Get current branch (worktree-compatible)
@@ -37,7 +84,21 @@ BRANCH_TYPE=$(echo $CURRENT | cut -d'/' -f1)
 BRANCH_NAME=$(echo $CURRENT | sed 's/.*\///')
 ```
 
-### 2. Determine Target Branch
+### 3. Determine Target Branch
+
+```bash
+# Map branch type to target branch (using config values)
+case "$BRANCH_TYPE" in
+  feature) TARGET="$GF_DEVELOP_BRANCH" ;;
+  release) TARGET="$GF_MAIN_BRANCH" ;;
+  hotfix)  TARGET="$GF_MAIN_BRANCH" ;;
+  *)       TARGET="$GF_DEVELOP_BRANCH" ;;
+esac
+
+echo "✓ Config loaded: $CONFIG_FILE"
+echo "✓ Branch: $CURRENT (type: $BRANCH_TYPE)"
+echo "✓ Target: $TARGET"
+```
 
 | Type | Target | Reason |
 |------|--------|--------|

package/templates/project/appsettings.json.template

@@ -8,7 +8,6 @@
     "EnableDevSeeding": false
   },
   "Jwt": {
-    "Secret": "{{GenerateRandomSecret}}",
     "Issuer": "{{ProjectName}}",
     "Audience": "{{ProjectName}}",
     "AccessTokenExpirationMinutes": 60,
@@ -132,6 +131,10 @@
       "SenderAddress": ""
     }
   },
+  "Zefix": {
+    "Username": "",
+    "Password": ""
+  },
   "Entra": {
     "TenantId": "",
     "ClientId": "",
@@ -140,10 +143,13 @@
     "SyncIntervalMinutes": 60,
     "UseDeltaSync": true,
     "DefaultConflictResolution": "ManualReview",
-    "AutoCreateReferences": true
+    "AutoCreateReferences": true,
+    "BackgroundSyncEnabled": false,
+    "BackgroundSyncIntervalMinutes": 60
   },
   "MultiTenant": {
     "Enabled": true,
+    "EnableB2B": true,
     "EnableB2C": true,
     "SystemTenantSlug": "default",
     "SystemTenantName": "Default Workspace",

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

@@ -1406,33 +1406,7 @@
        DATA STORE
        ============================================ */
     const APP_KEY = 'ba-{{APPLICATION_ID}}';
-    let data = {
-        metadata: {
-            applicationName: '{{APPLICATION_NAME}}',
-            applicationId: '{{APPLICATION_ID}}',
-            version: '{{VERSION}}',
-            createdAt: '{{CREATED_AT}}',
-            lastModified: new Date().toISOString()
-        },
-        cadrage: {
-            problem: {},
-            current: {},
-            vision: {},
-            stakeholders: [],
-            scope: { vital: [], important: [], optional: [], excluded: [] },
-            risks: [],
-            assumptions: '',
-            success: {}
-        },
-        modules: [],
-        dependencies: [],
-        moduleSpecs: {},
-        consolidation: {
-            interactions: [],
-            e2eFlows: []
-        },
-        handoff: {}
-    };
+    let data = {{FEATURE_DATA}};
 
     /* ============================================
        INITIALIZATION

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

@@ -1263,6 +1263,62 @@ ba-writer.updateStatus({module_feature_id}, "specified")
 ba-writer.updateModuleStatus({feature_id}, {currentModule.code}, "specified")
 ```
 
+### 11-bis. Deploy Incremental Interactive HTML (MANDATORY)
+
+> **After each module is specified, deploy/update the interactive HTML document with all available data.**
+> This allows the client to review completed modules while the next module is being specified.
+> The HTML is incrementally enriched: after module 1, only module 1 specs appear; after module 2, both appear; etc.
+
+**Source:** `html/ba-interactive.html` (relative to skill root = `~/.claude/skills/business-analyse/html/`)
+
+**Destination:** `docs/business/{app}/business-analyse/v{version}/ba-interactive.html`
+
+**Steps:**
+
+1. **Read sources:**
+   - Read the HTML template from skill directory
+   - Read the master feature.json (application level — now updated with current module status)
+   - Read EACH completed module's feature.json (including the one just specified)
+
+2. **Build FEATURE_DATA object:**
+
+   > **Use the EXACT SAME mapping defined in step-05-handoff.md section 9d.**
+   > The mapping is identical — the only difference is that `moduleSpecs` only includes completed modules.
+   > Modules not yet specified will NOT appear in `moduleSpecs` (their entry in `modules[]` will show `status: "pending"`).
+
+   Follow step-05 section 9d "Step 2: Build FEATURE_DATA object" for the complete mapping pseudocode:
+   - `metadata`, `cadrage`, `modules[]`, `dependencies[]` → from master feature.json
+   - `moduleSpecs[moduleCode]` → only for modules with status "specified" (completed so far)
+   - `consolidation` → empty `{ interactions: [], e2eFlows: [] }` (not yet consolidated)
+   - `handoff` → empty `{}` (not yet handed off)
+
+3. **Replace placeholders in template:**
+   - Serialize the FEATURE_DATA object as JSON (2-space indentation)
+   - Replace `{{FEATURE_DATA}}` with the serialized JSON
+   - Replace `{{APPLICATION_NAME}}` → `{application_name}`
+   - Replace `{{APPLICATION_ID}}` → `{feature_id}`
+   - Replace `{{VERSION}}` → `{version}`
+   - Replace `{{CREATED_AT}}` → `{ISO timestamp}`
+
+4. **Write and confirm:**
+
+```
+✓ Interactive HTML updated (incremental):
+  Path: docs/business/{app}/business-analyse/v{version}/ba-interactive.html
+  Modules included: {completedModules.length}/{totalModules} specified
+    - {completedModule1}: {uc_count} UCs, {br_count} BRs, {entity_count} entities
+    - {completedModule2}: ...
+  Remaining: {pendingModules.join(', ')} (will be added after specification)
+  → Client can open in browser to review completed modules now.
+```
+
+> **WHY incremental?** The client doesn't have to wait until handoff to start reviewing.
+> While module 2 is being specified, the client can already give feedback on module 1.
+> Each incremental deployment OVERWRITES the previous HTML (latest state always).
+> The FINAL deployment at step-05 (handoff) will include consolidation and handoff data.
+
+---
+
 ### 12. Loop Decision
 
 ```
@@ -1338,6 +1394,7 @@ Read metadata.workflow.currentModule
 - Client confirmed module specification
 - Module feature.json written
 - Master updated with module status
+- **Interactive HTML deployed/updated with completed module data (incremental)**
 - Loop advanced correctly
 
 ## FAILURE MODES

package/templates/skills/business-analyse/steps/step-05-handoff.md

@@ -917,8 +917,10 @@ Status journey: analyze → consolidate → **handed-off**
 
 ### 9d. Deploy Interactive HTML Document (MANDATORY)
 
-> **The interactive HTML document is deployed to the project for client-facing review.**
-> It allows clients to review, edit, and enrich the business analysis directly in their browser.
+> **The interactive HTML document is deployed to the project PRE-POPULATED with ALL analysis data.**
+> The client opens it in a browser and sees the complete analysis (cadrage, modules, entities, UCs, BRs, wireframes, permissions, consolidation).
+> The client can then review, edit, enrich, and export modifications as JSON.
+> That JSON can be re-imported via `/business-analyse -x` to update the feature.json.
 
 **Source:** `html/ba-interactive.html` (relative to skill root = `~/.claude/skills/business-analyse/html/`)
 
@@ -926,27 +928,223 @@ Status journey: analyze → consolidate → **handed-off**
 
 **Deployment steps:**
 
+#### Step 1: Read source data
+
 1. Read the HTML template from skill directory
-2. Replace template placeholders with actual values:
-   - `{{APPLICATION_NAME}}` → `{application_name}`
-   - `{{APPLICATION_ID}}` → `{feature_id}`
-   - `{{VERSION}}` → `{version}`
-   - `{{CREATED_AT}}` → `{ISO timestamp}`
-3. Write the populated HTML to the output directory
-4. Display deployment confirmation:
+2. Read the master feature.json (application level)
+3. Read EACH module feature.json (module level)
+
+#### Step 2: Build FEATURE_DATA object
+
+> **CRITICAL:** The HTML `data` object MUST be pre-populated with ALL analysis data.
+> An empty data object is a **BUG** — the client would see a blank page.
+
+Build a JSON object following this **exact mapping** from feature.json to the HTML data model:
+
+```javascript
+{
+  metadata: {
+    applicationName: master.metadata.application,       // e.g. "RH"
+    applicationId: master.id,                           // e.g. "FEAT-001"
+    version: master.version,                            // e.g. "1.0"
+    createdAt: master.metadata.createdAt,
+    lastModified: master.metadata.updatedAt
+  },
+  cadrage: {
+    problem: {
+      description: master.cadrage.problem,              // string → problem.description
+      trigger: master.cadrage.trigger,                  // string → problem.trigger
+      impactedPeople: "",                               // not in feature.json, client fills
+      history: "",
+      consequences: ""
+    },
+    current: {
+      tools: master.cadrage.asIs,                       // string → current.tools
+      steps: [],                                        // client can add process steps
+      painPoints: master.cadrage.stakeholders
+        .flatMap(s => s.painPoints || []).join("\n"),    // aggregate all painPoints
+      errors: ""
+    },
+    vision: {
+      changes: master.cadrage.toBe,                     // string → vision.changes
+      results: master.cadrage.acceptanceCriteria
+        .map(ac => ac.criterion).join("\n"),             // AC → results (one per line)
+      successSign: ""
+    },
+    stakeholders: master.cadrage.stakeholders.map(s => ({
+      role: s.role,
+      function: s.function || "",
+      tasks: s.tasks || [],
+      frequency: mapFrequency(s.frequency),             // "Quotidien"→"daily", etc.
+      access: mapAccess(s.involvement),                 // "decision-maker"→"admin", "end-user"→"contributor"
+      frustrations: (s.painPoints || []).join("\n")
+    })),
+    scope: {
+      vital: (master.cadrage.globalScope.mustHave || [])
+        .map(item => ({ name: item, description: "" })),      // string[] → {name,description}[]
+      important: (master.cadrage.globalScope.shouldHave || [])
+        .map(item => ({ name: item, description: "" })),
+      optional: (master.cadrage.globalScope.couldHave || [])
+        .map(item => ({ name: item, description: "" })),
+      excluded: (master.cadrage.globalScope.outOfScope || [])
+        .map(item => ({ name: item, description: "" }))
+    },
+    risks: (master.cadrage.risks || []).map(r => ({
+      description: r.description,
+      probability: r.probability,                       // "high" | "medium" | "low"
+      impact: r.impact,
+      mitigation: r.mitigation || ""
+    })),
+    assumptions: "",
+    success: {
+      definition: (master.cadrage.acceptanceCriteria || [])
+        .map(ac => ac.criterion).join("\n"),
+      metrics: "",
+      timeline: "",
+      minimumConditions: ""
+    }
+  },
+  modules: master.modules.map(m => ({
+    code: m.code,
+    name: m.code,                                       // module code as name
+    description: m.description || "",
+    featureType: m.featureType || "data-centric",
+    priority: m.priority || "must",
+    entities: m.entities || [],
+    status: m.status || "handed-off"
+  })),
+  dependencies: (master.dependencyGraph?.edges || []).map(e => ({
+    from: e.from,
+    to: e.to,
+    description: e.description || ""
+  })),
+  moduleSpecs: {
+    // FOR EACH module: read module feature.json, then map:
+    // [moduleCode]: { useCases, businessRules, entities, permissions, notes, mockupNotes }
+  },
+  consolidation: {
+    interactions: (master.consolidation?.crossModuleInteractions || []).map(i => ({
+      from: i.fromModule,
+      to: i.toModule,
+      description: i.description || ""
+    })),
+    e2eFlows: (master.consolidation?.e2eFlows || []).map(f => ({
+      name: f.name,
+      steps: (f.steps || []).map(s => ({ module: s.module, action: s.action })),
+      actors: (f.steps || []).map(s => s.permission).join(", ")
+    }))
+  },
+  handoff: master.handoff || {}
+}
+```
+
+**Module specs mapping** — for EACH module in `master.modules[]`:
+
+1. Read the module feature.json at `master.modules[i].featureJsonPath`
+2. Map to `moduleSpecs[moduleCode]`:
+
+```javascript
+moduleSpecs[moduleCode] = {
+  useCases: (moduleFeature.specification?.useCases || []).map(uc => ({
+    name: uc.name,
+    actor: uc.primaryActor,
+    steps: (uc.mainScenario || []).join("\n"),           // array → newline-separated string
+    alternative: (uc.alternativeScenarios || [])
+      .map(a => a.name + ": " + (a.steps || []).join(", ")).join("\n")
+  })),
+  businessRules: (moduleFeature.analysis?.businessRules || []).map(br => ({
+    name: br.name,
+    category: br.category,                              // "validation"|"calculation"|"workflow"|"security"|"data"
+    statement: br.statement,
+    example: (br.examples || []).map(e => e.input + " → " + e.expected).join("; ")
+  })),
+  entities: (moduleFeature.analysis?.entities || []).map(ent => ({
+    name: ent.name,
+    description: ent.description || "",
+    attributes: (ent.attributes || []).map(a => ({
+      name: a.name,
+      description: a.description || ""
+    })),
+    relationships: (ent.relationships || []).map(r =>
+      r.target + " (" + r.type + ") - " + (r.description || "")
+    )
+  })),
+  permissions: buildPermissionKeys(moduleFeature),      // see below
+  notes: "",
+  mockupNotes: (moduleFeature.specification?.uiWireframes || [])
+    .map(w => "[" + w.screen + "]\n" + w.mockup).join("\n\n")
+}
+```
+
+**Permission keys** — the HTML uses `"Role|Action"` format (e.g. `"RH Admin|Consulter"`):
+
+```javascript
+function buildPermissionKeys(moduleFeature) {
+  const keys = [];
+  const matrix = moduleFeature.specification?.permissionMatrix;
+  if (!matrix) return keys;
+  const actionMap = { read: "Consulter", create: "Creer", update: "Modifier",
+                      delete: "Supprimer", validate: "Valider", export: "Exporter",
+                      submit: "Valider", import: "Creer" };
+  (matrix.roleAssignments || []).forEach(ra => {
+    (ra.permissions || []).forEach(permPath => {
+      const action = permPath.split(".").pop();         // last segment = action
+      const uiAction = actionMap[action] || action;
+      keys.push(ra.role + "|" + uiAction);
+    });
+  });
+  return keys;
+}
+```
+
+**Frequency mapping:**
+```
+"Quotidien" → "daily", "Hebdomadaire" → "weekly", "Mensuel" → "monthly"
+Default: "daily"
+```
+
+**Access mapping (involvement → access):**
+```
+"decision-maker" → "admin", "end-user" with manager-like tasks → "manager"
+"end-user" → "contributor", "observer" → "viewer"
+Default: "contributor"
+```
+
+#### Step 3: Replace placeholders in template
+
+1. Serialize the FEATURE_DATA object as JSON (with 2-space indentation for readability)
+2. Replace `{{FEATURE_DATA}}` with the serialized JSON
+3. Replace `{{APPLICATION_NAME}}` → `{application_name}` (still used in `<title>` and header)
+4. Replace `{{APPLICATION_ID}}` → `{feature_id}` (still used in `APP_KEY`)
+5. Replace `{{VERSION}}` → `{version}`
+6. Replace `{{CREATED_AT}}` → `{ISO timestamp}`
+
+> **NOTE:** `{{APPLICATION_NAME}}`, `{{APPLICATION_ID}}`, `{{VERSION}}`, `{{CREATED_AT}}` still appear
+> in the HTML body (`<title>`, header, `APP_KEY`). They MUST be replaced separately from FEATURE_DATA.
+
+#### Step 4: Write and confirm
+
+1. Write the populated HTML to the output directory
+2. Display deployment confirmation:
 
 ```
 ✓ Interactive HTML deployed:
   Path: docs/business/{app}/business-analyse/v{version}/ba-interactive.html
+  Pre-populated with: {stakeholder_count} stakeholders, {module_count} modules,
+    {total_uc} use cases, {total_br} business rules, {total_entity} entities
   Open in browser to review and edit the business analysis.
   Export JSON and re-import with: /business-analyse -x <exported-json-path>
 ```
 
-**Why deploy at handoff?**
-- The feature.json is complete at this point (all modules specified and consolidated)
-- The client can review the full analysis in an interactive format
+**Why a FINAL deployment at handoff?**
+- Step 03 already deploys the HTML incrementally after each module (partial data)
+- This final deployment adds the COMPLETE data: all modules + consolidation + handoff info
+- The client sees the FULL analysis pre-populated — including cross-module interactions and E2E flows
+- The client can review, edit, and enrich directly in the browser
 - Any client modifications can be re-imported via `-x` extraction mode
 - The HTML is standalone (no server required) with localStorage persistence
+- On first open: pre-populated data displays. After client edits: localStorage overrides
+- **NOTE:** This overwrites the incremental HTML from step-03 with the complete version
 
 ---
 
@@ -1192,7 +1390,7 @@ Before presenting handoff to user:
 - [ ] feature.json updated: handoff section + status "handed-off"
 - [ ] All paths use project namespace from .smartstack/config.json
 - [ ] No invented requirements (everything traced to feature.json)
-- [ ] ba-interactive.html deployed with placeholders replaced
+- [ ] ba-interactive.html deployed PRE-POPULATED with all analysis data (not empty)
 - [ ] BA manifest (docs/business/index.json) updated with current analysis entries
 - [ ] User ready for next agent selection
 

package/templates/skills/gitflow/steps/step-pr.md

@@ -38,13 +38,25 @@ fi
 
 ```bash
 CURRENT=$(git rev-parse --abbrev-ref HEAD)
+BRANCH_TYPE=$(echo $CURRENT | cut -d'/' -f1)
+
+# CRITICAL: Verify config was loaded
+if [ -z "$GF_MAIN_BRANCH" ] || [ -z "$GF_DEVELOP_BRANCH" ]; then
+  echo "❌ GitFlow config not loaded properly"
+  echo "→ Variables GF_MAIN_BRANCH and GF_DEVELOP_BRANCH are empty"
+  exit 1
+fi
 
-case "$CURRENT" in
-  ${GF_FEATURE_PREFIX}*) TARGET_BRANCH="$GF_DEVELOP_BRANCH" ;;
-  ${GF_RELEASE_PREFIX}*) TARGET_BRANCH="$GF_MAIN_BRANCH" ;;
-  ${GF_HOTFIX_PREFIX}*)  TARGET_BRANCH="$GF_MAIN_BRANCH" ;;
-  *)                     TARGET_BRANCH="$GF_DEVELOP_BRANCH" ;;
+# Determine target branch based on type (using config values)
+case "$BRANCH_TYPE" in
+  feature) TARGET_BRANCH="$GF_DEVELOP_BRANCH" ;;
+  release) TARGET_BRANCH="$GF_MAIN_BRANCH" ;;
+  hotfix)  TARGET_BRANCH="$GF_MAIN_BRANCH" ;;
+  *)       TARGET_BRANCH="$GF_DEVELOP_BRANCH" ;;
 esac
+
+echo "✓ Branch: $CURRENT (type: $BRANCH_TYPE)"
+echo "✓ Target: $TARGET_BRANCH"
 ```
 
 ### 3. Check Prerequisites