@atlashub/smartstack-cli 4.18.0 → 4.20.0

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

@@ -1,691 +0,0 @@
----
-name: step-03d-validate
-description: Per-module validation, write feature.json, incremental HTML deploy, loop decision
-model: sonnet
-next_step: steps/step-03a1-setup.md OR steps/step-04a-collect.md (conditional)
----
-
-> **Context files:** `_shared.md` | `_module-loop.md` | `_rules.md`
-
-# Step 3d: Validation & Loop
-
-## MANDATORY EXECUTION RULES
-
-- ALWAYS use ULTRATHINK mode
-- This step VALIDATES the specification from step-03c, writes it to feature.json, and decides loop continuation
-- ALWAYS verify specification completeness before writing
-- ALL communication in `{language}`
-- ALWAYS run the iteration safety guard BEFORE the loop decision (max 30 modules hard cap, 15 warning)
-
-## 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` in ANY phase below
-  → Phase 3: if validation fails, AUTO-CORRECT silently (no user options)
-  → Phase 6: **SKIP section 12** — go directly to section 12-bis (Agent Mode)
-  → After writing feature.json, send `PROPOSAL_READY` to team lead via SendMessage
-  → NEVER present options/menus to the user — you are an autonomous agent
-
-**IF you are running in the MAIN CONVERSATION** (classic inline mode):
-  → Normal interactive mode — use `AskUserQuestion` as documented
-  → Section 12-bis does NOT apply to you
-
-- **Rules:** See `_rules.md` § "ID Naming Convention" (MANDATORY, NO EXCEPTION)
-
-## YOUR TASK
-
-Validate the module specification for completeness and consistency, write to feature.json, deploy incremental HTML, and decide whether to loop to the next module or proceed to consolidation.
-
----
-
-## Phase 1: AUTO-FIX (silent — no output)
-
-> **Apply all auto-fix rules BEFORE validation. No user interaction, no display.**
-
-**1a. Wireframe field names** — Apply `_rules.md` § "Auto-Fix: Wireframe Field Names":
-- For each wireframe in `specification.uiWireframes` (or `specification.wireframes`):
-  - Rename `title` → `screen`, `name` → `screen`, `ascii` → `mockup`, `content` → `mockup` (only if canonical field absent)
-- Store normalized wireframes under `specification.uiWireframes`
-
-**1b. Entity attribute types** — Apply `_rules.md` § "Auto-Fix: Entity Attribute Type Inference":
-- For each entity attribute missing a `type` field, infer from the name pattern table
-- Normalize free-text `validation` into structured `maxLength` where applicable
-- Default `required` to `true` if undefined
-- Log count of auto-fixed attributes as a warning (defense-in-depth — step-03c should have caught these)
-
----
-
-## Phase 2: VALIDATE (single pass)
-
-> **CRITICAL:** Checks MUST count ACTUAL elements in arrays, NOT declarative values.
-> A check that reports PASS when the array is empty is a LIE and BLOCKS downstream quality.
-> **Minimums:** See `_rules.md` § "Minimum Counts (Authoritative)" for all thresholds.
-
-Run ALL checks in a single pass. Each check has: name | minimum | blocking? | how to verify.
-
-### Completeness Checks
-
-| Check | Min | Blocking | How to verify |
-|-------|-----|----------|---------------|
-| entities | ≥ 2 | YES | `analysis.entities.length >= 2` |
-| entity attributes (each) | ≥ 3 | YES | Every entity has `attributes.length >= 3` |
-| entitySchemaFormat | attributes[] not fields[] | YES | `analysis.entities.every(e => e.attributes?.length > 0)` — no `tableName` or `primaryKey` |
-| entityAttributeTypes | ALL have `type` | YES | `analysis.entities.every(e => e.attributes.every(a => a.type))` |
-| actors | ≥ 2 | YES | `specification.actors.length >= 2` |
-| useCases | ≥ 6 | YES | `specification.useCases.length >= 6` |
-| functionalRequirements | ≥ 4 | YES | `specification.functionalRequirements.length >= 4` |
-| permissionMatrix | ≥ 5 perms, ≥ 2 roles | YES | `permissionMatrix.permissions.length >= 5 && permissionMatrix.roleAssignments.length >= 2` |
-| sections | ≥ 2 | YES | `specification.sections.length >= 2` |
-| wireframes | 1 per section | YES | `uiWireframes.length >= sections.length` (check BOTH key names) |
-| wireframeSchema | All required fields | YES | Every wireframe has: `screen`, `section`, `mockupFormat`, `elements[]` (non-empty), `componentMapping[]`, `layout` (object), `permissionsRequired[]` |
-| navigation | entries[] present | YES | `specification.navigation?.entries?.length >= 1` |
-| seedDataCore | 9 arrays present | YES | See seedDataCore detail below |
-| messages | ≥ 4 | YES | `specification.messages.length >= 4` |
-| validations | ≥ 1 | YES | `specification.validations.length >= 1` |
-| apiEndpoints | ≥ 5 | YES | `specification.apiEndpoints.length >= 5` |
-| i18nKeys | ≥ 42 leaves, 4 langs | YES | All leaf keys have fr/en/it/de |
-| gherkinScenarios | array, ≥ 1 entry | YES | `Array.isArray(gherkinScenarios) && gherkinScenarios.length >= 1` |
-| gherkinCount | ≥ 2 scenarios | NO (WARN) | Total scenario count across all entries |
-| lifeCycles | ≥ 1 (if entity has status) | YES | `specification.lifeCycles.length >= 1` if applicable |
-| dataLifecycle | present | YES | `analysis.dataLifecycle !== undefined` |
-| navigationIcons | non-null | YES | All navigation modules have non-null icon |
-
-**seedDataCore detail:** Verify all 9 arrays per `_rules.md` § "Minimum Counts":
-
-| Array | Min (1st module) | Min (2nd+ module) |
-|---|---|---|
-| navigationApplications | 1 | 0 |
-| applicationRoles | 1 | 0 |
-| navigationModules | 1 | 1 |
-| navigationSections | 1 | 1 |
-| navigationResources | 1 | 1 |
-| navigationTranslations | 2 | 2 |
-| permissions | 1 | 1 |
-| rolePermissions | 1 | 1 |
-| permissionConstants | 1 | 1 |
-
-### Consistency Checks
-
-| Check | Blocking | Rule |
-|-------|----------|------|
-| UC-FR linkage | YES | Every UC has ≥ 1 linked FR |
-| FR-BR linkage | NO (WARN) | Every FR has ≥ 1 linked BR |
-| BR references valid | YES | All BR references exist in `analysis.businessRules` |
-| Actors in permissions | YES | All actors appear in `permissionMatrix` |
-| Permission path format | YES | Module-level `{app}.{module}.{action}` or section-level `{app}.{module}.{section}.{action}` |
-| rolePermissions paths | YES | All paths match `permissions` paths |
-| API route prefix | YES | Consistent prefix across endpoints |
-
-### Convention Checks
-
-| Check | Blocking | Rule |
-|-------|----------|------|
-| UC ID format | YES | `UC-{PREFIX}-{NNN}` with module prefix |
-| FR ID format | YES | `FR-{PREFIX}-{NNN}` |
-| BR ID format | YES | `BR-{CAT}-{PREFIX}-{NNN}` |
-| Entity names | YES | PascalCase |
-| Field names | YES | camelCase |
-| Permission paths | YES | Dot-separated lowercase |
-| Navigation routes | YES | No `/list` or `/detail/:id` suffixes |
-
-### Format Checks
-
-> See `_rules.md` § "Format Checks" for canonical rules.
-
-| Check | Blocking | Rule |
-|-------|----------|------|
-| gherkinFormat | YES | Array `[{feature, scenarios}]`, not single object |
-| gherkinContent | YES | Each entry has `feature` (string) + `scenarios` (array) |
-| validationFormat | YES | `validations[].rules` is array, not singular string |
-| messageFormat | YES | `messages[]` has `message` field |
-| wireframeFields | YES | Uses `screen` (not `title`/`name`), `mockup` (not `ascii`/`content`) |
-
-### Failure Handling
-
-IF any blocking check fails:
-- **CONDITIONAL LOAD:** Read `references/validation-checklist.md` for detailed fix guidance
-- Display table of failures with details and fix recommendations
-- **BLOCKING ERROR:** Module specification incomplete → fix all failures before proceeding
-
-IF all blocking checks pass:
-- Display warning count (non-blocking)
-- Proceed to Phase 3
-
----
-
-## Phase 3: DECIDE + WRITE VALIDATION
-
-### 3a. Decision
-
-> **TEAM AGENT MODE:** If running as team agent, SKIP AskUserQuestion. On FAIL → auto-correct silently. On PASS → proceed directly. NEVER present options to the user.
-
-**INLINE MODE ONLY (main conversation):**
-
-IF validation PASS:
-  Display summary, ask client for confirmation
-
-IF validation FAIL:
-  Display errors, offer:
-  ```
-  options:
-    - label: "Auto-corriger"
-      description: "Corriger automatiquement les erreurs détectées"
-    - label: "Réviser manuellement"
-      description: "Revenir aux sections problématiques"
-    - label: "Forcer la validation"
-      description: "Accepter malgré les erreurs (risqué)"
-  ```
-
-### 3b. Write Module Validation Section (MANDATORY)
-
-> **The module feature.json MUST have a `validation` section recording the results of Phase 2.**
-
-```
-ba-writer.enrichSection({
-  featureId: {module_feature_id},
-  section: "validation",
-  data: {
-    validatedAt: "{ISO timestamp}",
-    completenessChecks: [
-      { "section": "useCases", "count": {count}, "minimum": 6, "status": "PASS|FAIL" },
-      { "section": "functionalRequirements", "count": {count}, "minimum": 4, "status": "PASS|FAIL" },
-      { "section": "wireframes", "count": {count}, "minimum": {section_count}, "status": "PASS|FAIL" },
-      { "section": "seedDataCore", "count": 9, "minimum": 9, "status": "PASS|FAIL" }
-    ],
-    consistencyChecks: [
-      { "check": "UC-FR linkage", "passed": {n}, "warnings": {n}, "errors": {n}, "status": "PASS|FAIL" },
-      { "check": "BR references valid", "passed": {n}, "warnings": {n}, "errors": {n}, "status": "PASS|FAIL" },
-      { "check": "Permission path format", "passed": {n}, "warnings": {n}, "errors": {n}, "status": "PASS|FAIL" }
-    ],
-    conventionChecks: [
-      { "check": "ID naming with module prefix", "status": "PASS|FAIL", "details": "..." },
-      { "check": "Entity names PascalCase", "status": "PASS|FAIL", "details": "..." }
-    ],
-    semanticChecks: [
-      { "check": "orphan-permissions", "module": "{currentModule}", "status": "PASS|WARNING|ERROR", "details": "...", "autoFixed": false },
-      { "check": "uc-sans-fr", "module": "{currentModule}", "status": "PASS|WARNING|ERROR", "details": "...", "autoFixed": false },
-      { "check": "missing-wireframes", "module": "{currentModule}", "status": "PASS|WARNING|ERROR", "details": "...", "autoFixed": false }
-    ],
-    warnings: ["List of non-blocking warnings"],
-    decision: {
-      "approved": true,
-      "reason": "All checks passed",
-      "approvalMode": "standard",
-      "approvedBy": "Client",
-      "approvedAt": "{ISO timestamp}"
-    }
-  }
-})
-```
-
----
-
-## Phase 4: SUMMARY + WRITE FEATURE.JSON
-
-### 4a. Module Summary with Roles & Permissions
-
-Display comprehensive summary:
-
-```
-═══════════════════════════════════════════════════════════
-  MODULE SPÉCIFIÉ: {currentModule} ({currentModuleIndex + 1}/{total})
-═══════════════════════════════════════════════════════════
-
-| Aspect | Valeur |
-|--------|--------|
-| Entités | {count} ({entity names}) |
-| Business Rules | {count} (VAL: X, CALC: Y, WF: Z) |
-| Use Cases | {count} (UC-001 → UC-NNN) |
-| Exigences | {count} FRs |
-| Sections | {count} ({section names}) |
-| Maquettes | {count} wireframes |
-| Permissions | {count} paths |
-| Tests Gherkin | {count} scénarios |
-| Messages | {count} |
-
-### Rôles & Permissions pour {currentModule}
-| Rôle | Permissions |
-|------|------------|
-| {App} Admin | {app}.{module}.* |
-| {App} Manager | read, create, update, assign |
-| {App} Contributor | read, create, update |
-| {App} Viewer | read |
-
-→ Validation: {PASS/FAIL}
-═══════════════════════════════════════════════════════════
-
-{IF validation PASS}:
-  → Module validé automatiquement
-  → Passage automatique au module suivant (Phase 6)
-
-{IF validation FAIL}:
-  → Afficher les erreurs et offrir les options de correction (Phase 3)
-```
-
-> **Anti-Premature-Completion Guard:** NEVER say "the analysis is complete" or "ready for /ralph-loop" at this point.
-> Step-03d is the END of SPECIFICATION, NOT the end of the BA workflow.
-> Steps 04a → 04b → 04c (consolidation) + 05a → 05b → 05c (handoff) are STILL REQUIRED.
-> **FORBIDDEN phrases:** "L'analyse métier est complète", "Prêt pour /ralph-loop", "Vous pouvez maintenant lancer /ralph-loop"
-> **REQUIRED phrasing:** "Module {name} spécifié. {Remaining} modules restants." or "Tous les modules spécifiés. Passage à la consolidation (étapes 04a-04c)..."
-
-### 4b. Write Module Feature.json
-
-```
-// Write analysis section with ALL subsections
-ba-writer.enrichSection({
-  featureId: {module_feature_id},
-  section: "analysis",
-  data: {
-    objectives: [{id, objective, metric, target}],       // from 6a
-    entities: [{name, description, attributes, relationships}],  // from 6b — SCHEMA FORMAT
-    businessRules: [{id, name, category, statement, priority, conditions, examples, testability}],  // from 7 — SCHEMA FORMAT
-    processFlow: {entryPoints, mainFlow, decisionPoints, alternativeFlows},  // from 6c
-    dataLifecycle: {retentionPeriod, archiveStrategy, gdprCompliance, states}  // from 6d
-  }
-})
-
-// Write specification section with ALL subsections
-ba-writer.enrichSection({
-  featureId: {module_feature_id},
-  section: "specification",
-  data: {
-    actors: [{role, description, permissions}],                   // 8a
-    useCases: [{id, name, primaryActor, permission, mainScenario, linkedRules}],  // 8b
-    functionalRequirements: [{id, statement, priority, linkedRules, linkedUseCases, acceptanceCriteria}],  // 8c
-    permissionMatrix: {permissions: [], roleAssignments: []},     // 8d
-    navigation: {entries: []},                                    // 8e
-    seedDataCore: {navigationApplications, applicationRoles, navigationModules, navigationSections, navigationResources, navigationTranslations, permissions, rolePermissions, permissionConstants},  // 8f (9 arrays)
-    gherkinScenarios: [{feature, scenarios: [{name, tags, given, when, then}]}],  // 8g
-    validations: [{entity, field, rules, errorMessageKey}],       // 8h
-    messages: [{code, type, title, message, i18nKey}],            // 8i
-    lifeCycles: [{entity, field, initialState, states: [{id, displayName, color, allowedTransitions, isTerminal}], transitions}],  // 8j
-    apiEndpoints: [{method, path, permission, requestDto, responseDto, description}],  // 8k
-    i18nKeys: {...},                                              // 8l
-    sections: [{code, labels, route, icon, permission, wireframe, useCases, businessRules, resources}],  // from 3a-bis
-    dashboards: [{code, title, kpis, filters, refreshMode}],     // from 3d
-    uiWireframes: [{screen, section, mockup, elements, actions, componentMapping, layout}]  // from 3b
-  }
-})
-
-// Write validation results from Phase 3
-// (Already written in Phase 3b above)
-
-ba-writer.updateStatus({module_feature_id}, "specified")
-
-// Update master
-ba-writer.updateModuleStatus({feature_id}, {currentModule.code}, "specified")
-```
-
----
-
-## Phase 5: VERIFY (bash)
-
-> **CRITICAL:** The validation checks in Phase 2 are interpreted by the model — they can be "passed" incorrectly.
-> This bash check reads the REAL file on disk and provides an objective verification.
->
-> **Canonical acceptance criteria (AC-01 to AC-17):** See [references/acceptance-criteria.md](../references/acceptance-criteria.md).
-> The script below EXTENDS those criteria with step-03d-specific checks:
-> - Navigation entries present (`specification.navigation.entries`)
-> - `analysis.dataLifecycle` section present
-> - `validation` section recorded
-> - i18n 4-language completeness (AC-18)
->
-> If you need the standalone script (for debugging or handoff gate), use the one in `acceptance-criteria.md`.
-
-```bash
-MODULE_JSON="{module_feature_json_path}"
-node -e "
-const fs = require('fs');
-const data = JSON.parse(fs.readFileSync(process.argv[1], 'utf-8'));
-const spec = data.specification || {};
-const analysis = data.analysis || {};
-const wf = spec.uiWireframes || spec.wireframes || [];
-const sections = spec.sections || [];
-const checks = [
-  ['entities >= 2',          (analysis.entities||[]).length,          2],
-  ['useCases >= 2',          (spec.useCases||[]).length,              2],
-  ['FRs >= 4',               (spec.functionalRequirements||[]).length,4],
-  ['wireframes >= 1',        wf.length,                               1],
-  ['wireframes >= sections', wf.length,                               sections.length],
-  ['sections >= 1',          sections.length,                          1],
-  // CP-02: modules 2+ may have navigationApplications=[] and applicationRoles=[] (correct per _rules.md)
-  // Minimum = 9 for first module, 7 for subsequent modules
-  ['seedDataCore arrays', (() => { const sdc=spec.seedDataCore||{}; return Object.keys(sdc).filter(k=>Array.isArray(sdc[k])&&sdc[k].length>0).length; })(), (() => { const sdc=spec.seedDataCore||{}; const hasApp=(sdc.navigationApplications||[]).length>0||(sdc.applicationRoles||[]).length>0; return hasApp?9:7; })()],
-  ['gherkin is array',       Array.isArray(spec.gherkinScenarios)?1:0, 1],
-  ['apiEndpoints >= 1',      (spec.apiEndpoints||[]).length,           1],
-  ['messages >= 4',          (spec.messages||[]).length,               4],
-  ['validations >= 1',       (spec.validations||[]).length,            1],
-  ['navigation entries',     (spec.navigation?.entries||[]).length,    1],
-  ['dataLifecycle',          analysis.dataLifecycle ? 1 : 0,           1],
-  ['validation section',     data.validation ? 1 : 0,                  1]
-];
-// AC-18: i18n 4 languages check
-const i18n = spec.i18nKeys || {};
-const i18nLangs = ['fr','en','it','de'];
-let i18nMissing = 0;
-function checkI18nLeaf(obj) {
-  if (typeof obj !== 'object' || obj === null) return;
-  const hasLang = i18nLangs.some(l => typeof obj[l] === 'string');
-  if (hasLang) { i18nLangs.forEach(l => { if (!obj[l]) i18nMissing++; }); }
-  else { Object.values(obj).forEach(v => checkI18nLeaf(v)); }
-}
-checkI18nLeaf(i18n);
-checks.push(['i18n 4 languages (missing keys)', 0, i18nMissing > 10 ? 1 : 0]);
-
-const fails = checks.filter(c => c[1] < c[2]);
-fails.forEach(f => console.error('FAIL: ' + f[0] + ' = ' + f[1] + ' (min: ' + f[2] + ')'));
-if (i18nMissing > 0 && i18nMissing <= 10) { console.warn('WARNING: ' + i18nMissing + ' i18n leaf keys missing translations (IT/DE)'); }
-// Check wireframe content
-const emptyWf = wf.filter(w => !w.mockup && !w.ascii && !w.content);
-if (emptyWf.length > 0) { fails.push(['wireframe content', 0, 1]); console.error('FAIL: ' + emptyWf.length + ' wireframes have EMPTY content'); }
-// Check entity attribute types
-const badAttrs = (analysis.entities||[]).flatMap(e => (e.attributes||[]).filter(a => !a.type).map(a => e.name+'.'+a.name));
-if (badAttrs.length > 0) { fails.push(['attr.type', 0, 1]); console.error('FAIL: attributes without type: ' + badAttrs.join(', ')); }
-// AC-15: Validation rules format
-const badRules = (spec.validations||[]).filter(v => v.rules && !Array.isArray(v.rules));
-if (badRules.length > 0) { fails.push(['AC-15: rules not array', badRules.length, 0]); console.error('FAIL: AC-15: ' + badRules.length + ' validations have rules as string'); }
-// AC-16: Messages must have message field
-const noMsg = (spec.messages||[]).filter(m => !m.message);
-if (noMsg.length > 0) { fails.push(['AC-16: message missing', noMsg.length, 0]); console.error('FAIL: AC-16: ' + noMsg.length + ' messages missing message field'); }
-// AC-17: Gherkin content structure
-if (Array.isArray(spec.gherkinScenarios)) { const badG = spec.gherkinScenarios.filter(g => !g.feature || !Array.isArray(g.scenarios)); if (badG.length > 0) { fails.push(['AC-17: gherkin content', badG.length, 0]); console.error('FAIL: AC-17: ' + badG.length + ' gherkin entries invalid'); } }
-if (fails.length > 0) { console.error('BLOCKING: ' + fails.length + ' acceptance criteria failed'); process.exit(1); }
-console.log('PASS: All acceptance criteria met');
-" "$MODULE_JSON"
-```
-
-IF this check FAILS:
-- Identify which criteria failed from the output
-- Fix the corresponding data (re-read from conversation context, re-generate, or re-run the step that produces it)
-- Re-write to feature.json
-- Re-run this check until PASS
-
----
-
-## Phase 6: DEPLOY + ROUTE
-
-### 6a. Deploy Incremental Interactive HTML (MANDATORY)
-
-> **After each module is specified, deploy/update the interactive HTML document with all available data.**
-> The client can review completed modules while the next module is being specified.
-
-See [references/validate-incremental-html.md](../references/validate-incremental-html.md) for the complete deployment process (read sources, build FEATURE_DATA, replace placeholders, write HTML).
-
-Uses the **same mapping** as step-05b-deploy.md — only difference is `moduleSpecs` only includes completed modules.
-
----
-
-### 6b. Iteration Safety Guard (MAX MODULES CHECK)
-
-> **DEFENSIVE CHECK — Run BEFORE loop decision to prevent infinite loops.**
-
-```
-// Read loop state from feature.json
-const moduleOrder = metadata.workflow.moduleOrder || [];
-const completedModules = metadata.workflow.completedModules || [];
-const currentModuleIndex = metadata.workflow.currentModuleIndex || 0;
-const totalModules = moduleOrder.length;
-
-// Guard thresholds
-const MAX_MODULES_WARN = 15;
-const MAX_MODULES_BLOCK = 30;
-
-IF totalModules > MAX_MODULES_BLOCK:
-  BLOCKING ERROR:
-  "Module count ({totalModules}) exceeds maximum allowed ({MAX_MODULES_BLOCK}).
-   This is likely a decomposition error. Return to step-02-decomposition.md
-   and consolidate or split into multiple applications."
-  STOP — do not continue loop
-
-IF totalModules > MAX_MODULES_WARN:
-  WARNING (non-blocking):
-  "Module count ({totalModules}) is high. Consider whether some modules
-   could be grouped or split into separate applications.
-   Continuing with {totalModules - completedModules.length} modules remaining."
-
-// Sanity check: currentModuleIndex should never exceed totalModules
-IF currentModuleIndex >= totalModules AND completedModules.length < totalModules:
-  BLOCKING ERROR:
-  "Loop state inconsistency: currentModuleIndex ({currentModuleIndex}) >= totalModules ({totalModules})
-   but only {completedModules.length} modules are marked complete.
-   Fix: Check metadata.workflow in feature.json and correct the state manually."
-  STOP
-```
-
----
-
-### 6c. Loop Decision (section 12)
-
-> **TEAM AGENT MODE: SKIP THIS ENTIRE SECTION.** If you are a team agent (your prompt contains `PROPOSE & REVIEW`), go directly to **section 12-bis** below. Section 12 is for inline mode ONLY. You MUST NOT load the next step or advance the module loop — the team lead handles orchestration.
-
-**INLINE MODE ONLY (main conversation):**
-
-```
-ba-writer.advanceModuleLoop({feature_id})
-→ Increments currentModuleIndex
-→ Updates completedModules
-→ Updates currentModule
-
-IF currentModuleIndex < moduleOrder.length:
-  Display: "→ Module suivant: {nextModule} ({currentModuleIndex + 1}/{total})"
-  Load: steps/step-03a1-setup.md
-
-IF currentModuleIndex >= moduleOrder.length:
-  ba-writer.updateStatus({feature_id}, "specified")
-
-  // CHECKPOINT: Save progress BEFORE transition (protects against context exhaustion)
-  ba-writer.enrichSection({
-    featureId: {feature_id},
-    section: "metadata.workflow",
-    data: {
-      lastCompletedStep: "step-03d-validate",
-      allModulesSpecified: true
-    }
-  })
-
-  // CHECK: Are we in project mode (multi-application)?
-  IF workflow.mode === "project":
-    // APPLICATION LOOP: Check if more applications remain
-    projectFeature = ba-reader.findProjectFeature()
-    ba-writer.updateApplicationStatus(projectId, currentApp.code, "specified")
-    ba-writer.advanceApplicationLoop(projectId)
-
-    IF projectFeature.metadata.workflow.currentApplicationIndex + 1 < projectFeature.metadata.workflow.applicationOrder.length:
-      nextApp = projectFeature.metadata.workflow.applicationOrder[currentApplicationIndex + 1]
-      Display: "═══ Application {currentApp.name} terminée ({N}/{total}). Prochaine : {nextApp} ═══"
-      Display: "⚠ NE PAS lancer /ralph-loop — d'autres applications et la consolidation sont encore nécessaires."
-      // Load step-02 for next application's module decomposition
-      Load: steps/step-02-decomposition.md
-    ELSE:
-      Display: "═══ Toutes les applications spécifiées! Passage à la consolidation cross-application... ═══"
-      Display: "⚠ NE PAS lancer /ralph-loop — la consolidation et le handoff sont encore nécessaires."
-      ba-writer.updateStatus(projectId, "specified")
-      Load: steps/step-04a-collect.md
-  ELSE:
-    // SINGLE APPLICATION: Current behavior
-    Display: "═══ Tous les modules spécifiés! Passage à la consolidation (04a→04c) puis handoff (05a→05c)... ═══"
-    Display: "⚠ NE PAS lancer /ralph-loop — la consolidation et le handoff sont encore nécessaires."
-
-    // MANDATORY TRANSITION — DO NOT STOP HERE
-    // If context is near exhaustion, the checkpoint above ensures the user
-    // can resume with /business-analyse and it will route to step-04a automatically.
-    Load: steps/step-04a-collect.md
-```
-
----
-
-## 12-bis. Agent Mode: Send Proposal to Team Lead
-
-**IF running as TEAM AGENT (autonomous mode — detected in step-03a1 MODE DETECTION):**
-
-After all validation checks PASS and module feature.json is written:
-
-### A. Build Structured Summary
-
-Read the written module feature.json via ba-reader and build:
-
-```
-## Module: {moduleCode} — Specification Summary
-
-### Entities ({count})
-| Entity | Key Attributes | Relationships |
-|--------|---------------|---------------|
-| {name} | {attr1} ({type}), {attr2} ({type}), ... | → {relatedEntity} (FK) |
-
-### Sections ({count})
-| Section | Description | Resources |
-|---------|-------------|-----------|
-| {code} | {description} | {resource1}, {resource2}, ... |
-
-### Use Cases ({count})
-- {UC-ID}: {title}
-
-### Business Rules ({count})
-- {BR-ID}: {title} ({category})
-
-### Permissions
-- {permission.path}: {roles with access}
-
-### Seed Data Counts
-- Modules: {n} | Sections: {n} | Resources: {n}
-- Translations: {n} | Permissions: {n} | Role mappings: {n} | Constants: {n}
-
-### Wireframes
-- {section}: {1-line description of layout and key components}
-```
-
-### B. Send Proposal
-
-```
-SendMessage({
-  type: "message",
-  recipient: "team-lead",
-  content: "PROPOSAL_READY:{moduleCode}\n\n{structured_summary}",
-  summary: "{moduleCode} specification ready for review"
-})
-```
-
-### C. Wait for Response
-
-**WAIT** for team lead to respond:
-
-- **`APPROVED:{moduleCode}`** → Proceed to step D (Module Complete)
-- **`REVISION:{moduleCode}\n{feedback}`** → Apply changes:
-  1. Read the feedback
-  2. Update the relevant sections in feature.json via ba-writer
-  3. Re-run validation checks (Phase 2)
-  4. Re-build summary and send new `PROPOSAL_READY`
-  5. Max **3 revision cycles** — after 3, send `ERROR:{moduleCode}:Max revisions reached` and stop
-
-### D. Module Complete
-
-After approval:
-
-```
-ba-writer.updateModuleStatus({feature_id}, {moduleCode}, "specified")
-```
-
-```
-SendMessage({
-  type: "message",
-  recipient: "team-lead",
-  content: "MODULE_COMPLETE:{moduleCode}",
-  summary: "{moduleCode} module complete"
-})
-```
-
-Then WAIT — the team lead will send you a `shutdown_request`.
-Do NOT loop to next module. The team lead handles module ordering and will spawn a new agent for the next module.
-
-### E. Shutdown (MANDATORY)
-
-When you receive a `shutdown_request` from the team lead:
-
-```
-SendMessage({
-  type: "shutdown_response",
-  request_id: "{requestId from the shutdown_request message}",
-  approve: true
-})
-```
-
-This terminates your process. Do NOT output any text after `shutdown_response`.
-
-**Sequence reminder:** APPROVED → MODULE_COMPLETE → shutdown_request → shutdown_response (4 separate steps, never skip).
-
----
-
-## SINGLE-MODULE MODE
-
-When only 1 module in moduleOrder:
-
-- Same full validation flow
-- Skip cross-module references (section 5)
-- After validation → direct to step-04a-collect.md (auto-consolidation)
-
----
-
-## RESUME SUPPORT
-
-IF the step is resumed (e.g., after interruption):
-
-```
-Read metadata.workflow.currentModuleIndex
-Read metadata.workflow.currentModule
-→ Resume at the correct module
-→ If module has partial data, show what exists and continue from there
-```
-
----
-
-## CONTEXT MANAGEMENT
-
-| Loaded | Not Loaded |
-|--------|------------|
-| _shared.md | Other module feature.json (full) |
-| _rules.md | Questionnaires not needed |
-| feature-schema.json | Templates |
-| Completed modules summary (100 lines max) | React viewer files |
-
----
-
-## STATE VARIABLES
-
-| Variable | Description |
-|----------|-------------|
-| `{currentModule}` | Current module being specified |
-| `{currentModuleIndex}` | Index in moduleOrder |
-| `{completedModules}` | Array of already specified module codes |
-| `{module_feature_id}` | Feature ID for the module-level feature.json |
-
----
-
-## SUCCESS METRICS
-
-- Module specification validation PASS
-- Per-module validation results recorded in feature.json
-- Client confirmed module specification
-- Module feature.json written with all sections
-- Master updated with module status
-- Interactive HTML deployed/updated with completed module data (incremental)
-- Loop advanced correctly or consolidation phase initiated
-
----
-
-## FAILURE MODES
-
-- Validation FAIL → offer auto-correct / manual revise / force
-- Client rejects → revise specific sections via step-03a or step-03b
-- Cross-module reference error → clarify with client
-- Interruption → resumable via workflow state
-
----
-
-## NEXT STEP
-
-Conditional:
-
-- IF modules remaining → Load `steps/step-03a1-setup.md`
-- IF all modules done → Load `steps/step-04a-collect.md`