@atlashub/smartstack-cli 1.14.3 → 1.17.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "1.14.3",
+  "version": "1.17.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, APEX, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",
@@ -70,19 +70,23 @@
     "health": "node dist/index.js doctor --json"
   },
   "dependencies": {
+    "bcryptjs": "^2.4.3",
     "chalk": "^5.3.0",
     "cli-table3": "^0.6.3",
     "commander": "^12.0.0",
     "fs-extra": "^11.2.0",
     "inquirer": "^9.2.12",
     "jsonwebtoken": "^9.0.3",
+    "mssql": "^11.0.1",
     "ora": "^8.0.1",
     "zod": "^3.22.4"
   },
   "devDependencies": {
+    "@types/bcryptjs": "^2.4.6",
     "@types/fs-extra": "^11.0.4",
     "@types/inquirer": "^9.0.7",
     "@types/jsonwebtoken": "^9.0.10",
+    "@types/mssql": "^9.1.5",
     "@types/node": "^20.10.6",
     "@typescript-eslint/eslint-plugin": "^6.18.0",
     "@typescript-eslint/parser": "^6.18.0",

package/templates/agents/efcore/migration.md

@@ -1,6 +1,6 @@
 ---
 name: efcore-migration
-description: EF Core migration manager - create with smart naming (1 per feature)
+description: EF Core migration manager - orchestrates MCP for naming (1 per feature)
 color: magenta
 model: sonnet
 tools: Bash, Glob, Read, Edit
@@ -8,10 +8,24 @@ tools: Bash, Glob, Read, Edit
 
 # EF Core Migration Agent
 
-Manages migration creation with the "1 migration per feature" rule.
+Orchestrates migration creation with the "1 migration per feature" rule.
+
+> **IMPORTANT:** Cet agent **ORCHESTRE** uniquement. Le nommage est **DÉLÉGUÉ AU MCP**.
 
 > **CLAUDE INSTRUCTION:** The `AskUserQuestion({...})` blocks are instructions to use the `AskUserQuestion` tool **interactively**. You MUST execute the tool with these parameters to get the user's response BEFORE continuing.
 
+## Principe : Délégation au MCP
+
+```
+┌─────────────────┐      ┌─────────────────┐      ┌─────────────────┐
+│  Agent (CLI)    │─────▶│  MCP            │─────▶│  dotnet ef      │
+│  Orchestre      │      │  Génère le nom  │      │  Crée migration │
+└─────────────────┘      └─────────────────┘      └─────────────────┘
+```
+
+**INTERDIT :** Calculer le nom de migration dans cet agent.
+**OBLIGATOIRE :** Appeler `mcp__smartstack__suggest_migration` pour obtenir le nom.
+
 ## Dual DbContext Architecture
 
 SmartStack uses two separate DbContexts with separate migration histories:
@@ -29,53 +43,51 @@ SmartStack uses two separate DbContexts with separate migration histories:
 ## Workflow
 
 1. **Detect** DbContext type (Core vs Extensions)
-2. **Analyze** current branch (feature/hotfix/release)
-3. **Extract** version from package.json or *.csproj
+2. **Ask** user for migration description
+3. **Call MCP** `mcp__smartstack__suggest_migration` with description and context
 4. **Search** for existing migration for this branch
 5. **If exists**: propose to recreate (delete + create)
-6. **Generate** name: `{context}_v{version}_{sequence}_{Description}`
-7. **Create** migration with `dotnet ef migrations add --context {DbContext}`
-8. **Validate** generated content
+6. **Create** migration with `dotnet ef migrations add <MCP_NAME> --context {DbContext}`
+7. **Validate** generated content
+
+## Naming : Délégation MCP
 
-## Naming Pattern
+**TOUJOURS appeler le MCP pour le nommage :**
 
 ```
-{context}_v{version}_{sequence}_{Description}
+mcp__smartstack__suggest_migration({
+  description: "<user_description>",
+  context: "core" | "extensions"
+})
 ```
 
-**Core migrations:**
-- `core_v1.8.0_001_CreateAuthUsers`
-- `core_v1.8.0_002_AddEntraSync`
+Le MCP retourne le nom complet conforme : `{context}_v{version}_{sequence}_{Description}`
 
-**Extensions migrations:**
+**Exemples de noms générés par le MCP :**
+- `core_v1.8.0_001_CreateAuthUsers`
 - `ext_v1.0.0_001_CreateOrders`
-- `ext_v1.0.0_002_AddOrderItems`
 
 ## Commands
 
 ```bash
-# Branch
-git branch --show-current
-
-# Version
-grep -oP '"version":\s*"\K[^"]+' package.json
-
 # Existing migrations for Core
 find Migrations -name "core_*.cs" | grep -v Designer | grep -v Snapshot
 
 # Existing migrations for Extensions
 find Persistence/Migrations -name "ext_*.cs" | grep -v Designer | grep -v Snapshot
 
-# Create Core migration
-dotnet ef migrations add $MIGRATION_NAME --context CoreDbContext -o Persistence/Migrations
+# Create Core migration (use MCP_NAME from suggest_migration)
+dotnet ef migrations add $MCP_NAME --context CoreDbContext -o Persistence/Migrations
 
-# Create Extensions migration
-dotnet ef migrations add $MIGRATION_NAME --context ExtensionsDbContext -o Persistence/Migrations
+# Create Extensions migration (use MCP_NAME from suggest_migration)
+dotnet ef migrations add $MCP_NAME --context ExtensionsDbContext -o Persistence/Migrations
 
-# Delete
+# Delete existing migration
 rm Persistence/Migrations/*${OLD_NAME}*.cs
 ```
 
+> **Note:** `$MCP_NAME` est obtenu via l'appel MCP, jamais calculé localement.
+
 ## Context Detection
 
 If unable to auto-detect:

package/templates/agents/efcore/rebase-snapshot.md

@@ -21,35 +21,55 @@ Rebases ModelSnapshot on develop to resolve conflicts.
 ## Key Commands
 
 ```bash
+# Détection projet et DbContext
+detect_efcore_project   # → $DBCONTEXT, $DBCONTEXT_TYPE, $SCHEMA
+determine_base_branch   # → $BASE_BRANCH, $BRANCH_TYPE
+
 # Backup
 BACKUP_DIR=".claude/gitflow/backup/migrations/rebase_$(date +%Y%m%d_%H%M%S)"
 mkdir -p "$BACKUP_DIR"
 cp Migrations/*.cs "$BACKUP_DIR/"
 
-# Reset snapshot to develop
-git checkout origin/develop -- Migrations/*ModelSnapshot.cs
+# Reset snapshot to parent branch (develop ou main selon contexte)
+git fetch origin "$BASE_BRANCH"
+git checkout "origin/$BASE_BRANCH" -- Migrations/*ModelSnapshot.cs
+
+# Récupérer les migrations de la branche parente
+BASE_MIGS=$(git ls-tree -r --name-only "origin/$BASE_BRANCH" -- Migrations/ | grep "\.cs$" | grep -v "Designer\|Snapshot")
+for base_mig in $BASE_MIGS; do
+  base_name=$(basename "${base_mig%.cs}")
+  git checkout "origin/$BASE_BRANCH" -- "Migrations/${base_name}.cs" 2>/dev/null || true
+  git checkout "origin/$BASE_BRANCH" -- "Migrations/${base_name}.Designer.cs" 2>/dev/null || true
+done
+
+# Delete branch migrations only
+rm -f Migrations/*${BRANCH_TYPE}_*.cs
+rm -f Migrations/*${BRANCH_TYPE}_*.Designer.cs
 
-# Delete branch migrations
-rm -f Migrations/*Feature_*.cs
-rm -f Migrations/*Feature_*.Designer.cs
+# Regenerate with MCP naming - OBLIGATOIRE
+mcp__smartstack__suggest_migration({ description: "...", context: DBCONTEXT_TYPE })
+# Résultat: core_v1.7.0_001_UserAuthConsolidated
 
-# Regenerate
-dotnet ef migrations add Feature_1_7_0_Consolidated
+dotnet ef migrations add "$MIGRATION_NAME" --context "$DBCONTEXT"
 
 # Validate
 dotnet build
 ```
 
-## Migration Naming
+## Migration Naming (via MCP)
+
+**OBLIGATOIRE : Utiliser le MCP pour le nommage**
 
 ```
-{Type}_{Version}_{BranchName}_{Description}
+{context}_v{version}_{sequence}_{Description}
 
-Feature_1_7_0_UserAuth_Consolidated
-Hotfix_1_6_2_LoginFix_Fix
-Release_1_7_0_Initial
+core_v1.7.0_001_UserAuthConsolidated
+core_v1.6.2_001_LoginFixFix
+core_v1.7.0_001_ReleaseInitial
 ```
 
+> **INTERDIT :** Pattern ancien `Feature_1_7_0_UserAuth_Consolidated`
+
 ## Safety Checks
 
 - [ ] Clean working directory

package/templates/agents/efcore/squash.md

@@ -40,24 +40,34 @@ main      → BLOQUÉ (jamais squash)
 determine_base_branch  # → BASE_BRANCH, BRANCH_TYPE
 
 # Identifier migrations propres à la branche
-BASE_MIGS=$(git ls-tree -r --name-only "origin/$BASE_BRANCH" -- Migrations/)
+BASE_MIGS=$(git ls-tree -r --name-only "origin/$BASE_BRANCH" -- Migrations/ | grep "\.cs$" | grep -v "Designer\|Snapshot")
 LOCAL_MIGS=$(find Migrations -name "*.cs" | grep -v Designer | grep -v Snapshot)
 
 # Backup
 BACKUP_DIR=".claude/gitflow/backup/migrations/squash_$(date +%Y%m%d_%H%M%S)"
 mkdir -p "$BACKUP_DIR" && cp Migrations/*.cs "$BACKUP_DIR/"
 
-# CRUCIAL: Récupérer snapshot parent
+# CRUCIAL: Récupérer snapshot ET migrations de la branche parente
 git fetch origin "$BASE_BRANCH"
 git checkout "origin/$BASE_BRANCH" -- Migrations/*ModelSnapshot.cs
 
+# Récupérer les migrations de la branche parente (pour ne pas les perdre)
+for base_mig in $BASE_MIGS; do
+  base_name=$(basename "${base_mig%.cs}")
+  git checkout "origin/$BASE_BRANCH" -- "Migrations/${base_name}.cs" 2>/dev/null || true
+  git checkout "origin/$BASE_BRANCH" -- "Migrations/${base_name}.Designer.cs" 2>/dev/null || true
+done
+
 # Supprimer migrations de la branche uniquement
 for mig in $BRANCH_ONLY_MIGRATIONS; do
   rm -f "Migrations/${mig}"*
 done
 
-# Créer migration consolidée
-dotnet ef migrations add "${BRANCH_TYPE}_${NAME}_Consolidated"
+# Créer migration consolidée - UTILISER MCP OBLIGATOIRE
+mcp__smartstack__suggest_migration({ description: "...", context: "core" })
+# Résultat: core_v1.0.0_001_Description
+
+dotnet ef migrations add "$MIGRATION_NAME_FROM_MCP"
 
 # Valider
 dotnet build && dotnet ef migrations script --idempotent > /dev/null

package/templates/agents/mcp-healthcheck.md

@@ -0,0 +1,161 @@
+---
+name: mcp-healthcheck
+description: Verifies MCP server availability, version and configuration before operations
+color: cyan
+model: haiku
+tools: Bash, Read, Write, Glob
+---
+
+# MCP Health Check Agent
+
+Validates that SmartStack MCP is properly configured and up-to-date before any operation.
+
+## Status File
+
+Location: `.claude/mcp-status.json`
+
+```json
+{
+  "lastCheck": "2024-01-15T10:30:00Z",
+  "mcpVersion": "1.5.0",
+  "mcpPath": "D:\\01 - projets\\SmartStack.mcp",
+  "status": "ok",
+  "tools": ["validate_conventions", "scaffold_extension", "check_migrations", "..."]
+}
+```
+
+## Workflow
+
+### 1. Check Status File Age
+
+```bash
+# Read last check timestamp
+cat .claude/mcp-status.json 2>/dev/null | grep lastCheck
+```
+
+**Decision:**
+- File missing → Full check required
+- Last check > 7 days → Full check required
+- Last check ≤ 7 days → Quick validation only
+
+### 2. Quick Validation (≤ 7 days)
+
+Test MCP connectivity with a lightweight call:
+
+```
+Call: mcp__smartstack__validate_conventions with checks=["tables"]
+Expected: Response without connection error
+```
+
+If fails → Run full check
+
+### 3. Full Check (> 7 days or missing)
+
+#### 3.1 Verify MCP Server Configuration
+
+```bash
+# Check Claude Code MCP config
+cat ~/.claude/settings.json | grep -A 20 "smartstack"
+```
+
+#### 3.2 Test MCP Tools Availability
+
+Call each critical tool to verify availability:
+
+| Tool | Test Call |
+|------|-----------|
+| `validate_conventions` | `checks=["tables"]` |
+| `suggest_migration` | `description="test"` |
+| `check_migrations` | (no params) |
+
+#### 3.3 Check MCP Version
+
+```bash
+# Read MCP package.json
+cat "D:\\01 - projets\\SmartStack.mcp\\package.json" | grep version
+```
+
+#### 3.4 Compare with Latest Release
+
+```bash
+# Check npm registry for latest version
+npm view @anthropic/smartstack-mcp version 2>/dev/null || echo "Not published"
+```
+
+### 4. Update Status File
+
+```javascript
+Write(".claude/mcp-status.json", {
+  lastCheck: new Date().toISOString(),
+  mcpVersion: "<detected_version>",
+  mcpPath: "<configured_path>",
+  status: "ok" | "error",
+  tools: ["<available_tools>"],
+  errors: ["<any_errors>"] // if status = error
+})
+```
+
+## Output Format
+
+### Success
+```
+MCP HEALTH CHECK
+  Status: ✓ OK
+  Version: 1.5.0 (latest)
+  Last check: 2024-01-15
+  Tools available: 12/12
+```
+
+### Warning (outdated)
+```
+MCP HEALTH CHECK
+  Status: ⚠️ UPDATE AVAILABLE
+  Current: 1.4.0
+  Latest: 1.5.0
+  Action: Run `cd SmartStack.mcp && git pull`
+```
+
+### Error
+```
+MCP HEALTH CHECK
+  Status: ❌ ERROR
+  Issue: MCP server not responding
+  Action: Verify MCP configuration in Claude Code settings
+```
+
+## Integration
+
+This agent should be called:
+1. **Before any MCP-dependent operation** (scaffold, validate, migrate)
+2. **On CLI installation/update**
+3. **Manually via `/mcp:healthcheck`**
+
+## Caching Logic
+
+```
+┌─────────────────────┐
+│  Operation Start    │
+└──────────┬──────────┘
+           ▼
+┌─────────────────────┐
+│ Read mcp-status.json│
+└──────────┬──────────┘
+           ▼
+    ┌──────────────┐
+    │ File exists? │
+    └──────┬───────┘
+           │
+     No ───┼─── Yes
+           │     │
+           ▼     ▼
+    ┌──────────────────┐
+    │   > 7 days old?  │
+    └──────┬───────────┘
+           │
+     Yes ──┼─── No
+           │     │
+           ▼     ▼
+┌──────────────┐  ┌──────────────┐
+│  Full Check  │  │ Quick Check  │
+└──────────────┘  └──────────────┘
+```

package/templates/commands/efcore/_shared.md

@@ -16,6 +16,94 @@ detect_efcore_project() {
   STARTUP_PROJECT=$(find . -name "*.Api.csproj" -o -name "*Web.csproj" | head -1)
   INFRA_PROJECT=$(find . -name "*Infrastructure.csproj" | head -1)
   [ -z "$INFRA_PROJECT" ] && INFRA_PROJECT="$CSPROJ"
+
+  # Appeler la détection du DbContext
+  detect_dbcontext
+}
+```
+
+---
+
+## Détection DbContext (Core vs Extensions)
+
+SmartStack utilise **deux DbContext séparés** avec des historiques de migration distincts :
+
+| Context | DbContext | Schema | History Table |
+|---------|-----------|--------|---------------|
+| `core` | `CoreDbContext` | `core` | `core.__EFMigrationsHistory` |
+| `extensions` | `ExtensionsDbContext` | `extensions` | `extensions.__EFMigrationsHistory` |
+
+```bash
+detect_dbcontext() {
+  # 1. Vérifier si SmartStack.Domain existe → CoreDbContext
+  if find . -type d -name "SmartStack.Domain" | grep -q .; then
+    DBCONTEXT="CoreDbContext"
+    DBCONTEXT_TYPE="core"
+    SCHEMA="core"
+    echo "DbContext détecté: CoreDbContext (SmartStack.Domain trouvé)"
+    return
+  fi
+
+  # 2. Vérifier si projet client avec NuGet SmartStack → ExtensionsDbContext
+  if find . -name "*.csproj" -exec grep -l "SmartStack\." {} \; | grep -qv "SmartStack\."; then
+    DBCONTEXT="ExtensionsDbContext"
+    DBCONTEXT_TYPE="extensions"
+    SCHEMA="extensions"
+    echo "DbContext détecté: ExtensionsDbContext (Client avec NuGet SmartStack)"
+    return
+  fi
+
+  # 3. Vérifier les DbContext présents dans le code
+  CORE_CTX=$(find . -name "*.cs" -exec grep -l "CoreDbContext" {} \; 2>/dev/null | head -1)
+  EXT_CTX=$(find . -name "*.cs" -exec grep -l "ExtensionsDbContext" {} \; 2>/dev/null | head -1)
+
+  if [ -n "$CORE_CTX" ] && [ -z "$EXT_CTX" ]; then
+    DBCONTEXT="CoreDbContext"
+    DBCONTEXT_TYPE="core"
+    SCHEMA="core"
+  elif [ -z "$CORE_CTX" ] && [ -n "$EXT_CTX" ]; then
+    DBCONTEXT="ExtensionsDbContext"
+    DBCONTEXT_TYPE="extensions"
+    SCHEMA="extensions"
+  else
+    # 4. Les deux existent ou aucun trouvé → demander à l'utilisateur
+    DBCONTEXT=""
+    DBCONTEXT_TYPE=""
+    SCHEMA=""
+    echo "⚠️ DbContext non détecté automatiquement"
+    echo "→ Utiliser AskUserQuestion pour demander à l'utilisateur"
+  fi
+}
+```
+
+**Variables exportées :**
+
+| Variable | Valeurs possibles | Description |
+|----------|-------------------|-------------|
+| `$DBCONTEXT` | `CoreDbContext` / `ExtensionsDbContext` | Nom du DbContext |
+| `$DBCONTEXT_TYPE` | `core` / `extensions` | Type pour le MCP |
+| `$SCHEMA` | `core` / `extensions` | Schéma de base de données |
+
+**Si détection échoue, demander à l'utilisateur :**
+
+```javascript
+AskUserQuestion({
+  questions: [{
+    question: "Quel DbContext utiliser pour cette migration ?",
+    header: "DbContext",
+    options: [
+      { label: "CoreDbContext", description: "Entités SmartStack (User, Role, Navigation...)" },
+      { label: "ExtensionsDbContext", description: "Entités client spécifiques" }
+    ],
+    multiSelect: false
+  }]
+})
+
+// Puis définir les variables selon la réponse
+if (answer === "CoreDbContext") {
+  DBCONTEXT="CoreDbContext"; DBCONTEXT_TYPE="core"; SCHEMA="core";
+} else {
+  DBCONTEXT="ExtensionsDbContext"; DBCONTEXT_TYPE="extensions"; SCHEMA="extensions";
 }
 ```
 
@@ -155,6 +243,8 @@ determine_base_branch() {
 
 ## Convention Nommage Migration
 
+**OBLIGATOIRE : Utiliser le MCP pour le nommage**
+
 Pattern: `{context}_v{version}_{sequence}_{Description}`
 
 | Contexte | Version | Séquence | Description | Exemple |
@@ -162,6 +252,33 @@ Pattern: `{context}_v{version}_{sequence}_{Description}`
 | core | 1.2.0 | 001 | AddUserRoles | `core_v1.2.0_001_AddUserRoles` |
 | extensions | 1.3.0 | 001 | AddCustomFields | `extensions_v1.3.0_001_AddCustomFields` |
 
+**Appel MCP OBLIGATOIRE :**
+
+```javascript
+// TOUJOURS appeler le MCP pour obtenir le nom conforme
+mcp__smartstack__suggest_migration({
+  description: "Add User Roles",      // Description courte
+  context: DBCONTEXT_TYPE             // "core" ou "extensions" (de detect_dbcontext)
+})
+
+// Résultat: core_v1.2.0_001_AddUserRoles
+```
+
+**Création migration avec le nom MCP :**
+
+```bash
+# $MIGRATION_NAME = résultat du MCP
+# $DBCONTEXT = CoreDbContext ou ExtensionsDbContext (de detect_dbcontext)
+
+dotnet ef migrations add "$MIGRATION_NAME" \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  -o Persistence/Migrations
+```
+
+> **INTERDIT :** Calculer le nom de migration manuellement. Toujours déléguer au MCP.
+
 ---
 
 ## Règle d'Or: 1 Migration par Feature

package/templates/commands/efcore/db-deploy.md

@@ -21,10 +21,28 @@ Afficher: fichiers disponibles, environnement sélectionné, connexion cible.
 
 ---
 
-## STEP 1: Détecter Projet
+## STEP 1: Détecter Projet et DbContext
 
 ```bash
-detect_efcore_project
+detect_efcore_project   # Appelle detect_dbcontext() automatiquement
+echo "DbContext: $DBCONTEXT ($DBCONTEXT_TYPE)"
+```
+
+**Si DbContext non détecté automatiquement :**
+
+```javascript
+AskUserQuestion({
+  questions: [{
+    question: "Quel DbContext déployer ?",
+    header: "DbContext",
+    options: [
+      { label: "CoreDbContext", description: "Migrations du schéma core" },
+      { label: "ExtensionsDbContext", description: "Migrations du schéma extensions" },
+      { label: "Les deux", description: "Déployer core puis extensions" }
+    ],
+    multiSelect: false
+  }]
+})
 ```
 
 ---
@@ -32,7 +50,11 @@ detect_efcore_project
 ## STEP 2: Vérifier Migrations Pending
 
 ```bash
-PENDING_COUNT=$(dotnet ef migrations list --json | grep -c '"applied": false')
+PENDING_COUNT=$(dotnet ef migrations list \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  --json | grep -c '"applied": false')
 ```
 
 ---
@@ -40,9 +62,15 @@ PENDING_COUNT=$(dotnet ef migrations list --json | grep -c '"applied": false')
 ## STEP 3: Appliquer
 
 ```bash
-dotnet ef database update --configuration Release --verbose
+dotnet ef database update \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  --verbose
 ```
 
+> **Note :** Si "Les deux" sélectionné, exécuter pour CoreDbContext puis ExtensionsDbContext.
+
 ---
 
 ## Résumé

package/templates/commands/efcore/db-reset.md

@@ -81,18 +81,54 @@ backup_database  # Fonction de _shared.md
 
 ---
 
+## STEP 2.5: Détection DbContext
+
+```bash
+detect_efcore_project   # Appelle detect_dbcontext() automatiquement
+echo "DbContext: $DBCONTEXT"
+```
+
+**Si DbContext non détecté ou plusieurs contextes :**
+
+```javascript
+AskUserQuestion({
+  questions: [{
+    question: "Quel DbContext reset ? (ou 'both' pour les deux)",
+    header: "DbContext",
+    options: [
+      { label: "CoreDbContext", description: "Reset schéma core uniquement" },
+      { label: "ExtensionsDbContext", description: "Reset schéma extensions uniquement" },
+      { label: "Les deux", description: "Reset complet (core + extensions)" }
+    ],
+    multiSelect: false
+  }]
+})
+```
+
+---
+
 ## STEP 3: Drop Database
 
 ```bash
-dotnet ef database drop --project "$INFRA_PROJECT" --startup-project "$STARTUP_PROJECT" --force
+dotnet ef database drop \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  --force
 ```
 
+> **Note :** Si "Les deux" sélectionné, exécuter pour CoreDbContext puis ExtensionsDbContext.
+
 ---
 
 ## STEP 4: Recreate + Apply
 
 ```bash
-dotnet ef database update --project "$INFRA_PROJECT" --startup-project "$STARTUP_PROJECT" --verbose
+dotnet ef database update \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" \
+  --verbose
 ```
 
 ---