@atlashub/smartstack-cli 1.16.0 → 1.18.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "1.16.0",
+  "version": "1.18.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/db-deploy.md

@@ -4,12 +4,17 @@ description: EF Core database deploy - apply pending migrations
 color: green
 model: haiku
 tools: Bash, Glob
+steps:
+  - steps/shared/step-00-init.md
+  - steps/db/step-deploy.md
 ---
 
 # EF Core Database Deploy Agent
 
 Applies pending migrations to the local database.
 
+**Progressive Steps:** Load `steps/db/step-deploy.md` for detailed instructions.
+
 ## Workflow
 
 1. **Verify** appsettings.Local.json exists

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

@@ -4,12 +4,17 @@ description: EF Core database reset - drop and recreate (DESTRUCTIVE)
 color: red
 model: sonnet
 tools: Bash, Glob, Read
+steps:
+  - steps/shared/step-00-init.md
+  - steps/db/step-reset.md
 ---
 
 # EF Core Database Reset Agent
 
 **WARNING: Destructive operation - deletes all data!**
 
+**Progressive Steps:** Load `steps/db/step-reset.md` for detailed instructions.
+
 > **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.
 
 ## Workflow

package/templates/agents/efcore/db-seed.md

@@ -4,12 +4,17 @@ description: EF Core database seed - populate test data
 color: yellow
 model: haiku
 tools: Bash, Glob, Read
+steps:
+  - steps/shared/step-00-init.md
+  - steps/db/step-seed.md
 ---
 
 # EF Core Database Seed Agent
 
 Populates the database with test data.
 
+**Progressive Steps:** Load `steps/db/step-seed.md` for detailed instructions.
+
 ## Workflow
 
 1. **Detect** available seeding method:

package/templates/agents/efcore/db-status.md

@@ -5,12 +5,17 @@ color: blue
 model: haiku
 tools: Bash, Glob
 mcp: mcp__smartstack__check_migrations
+steps:
+  - steps/shared/step-00-init.md
+  - steps/db/step-status.md
 ---
 
 # EF Core Database Status Agent
 
 Fast check of EF Core migration state using **SmartStack MCP**.
 
+**Progressive Steps:** Load `steps/db/step-status.md` for detailed instructions.
+
 ## Workflow
 
 1. **Invoke MCP** for migration list and naming validation

package/templates/agents/efcore/migration.md

@@ -4,12 +4,20 @@ description: EF Core migration manager - orchestrates MCP for naming (1 per feat
 color: magenta
 model: sonnet
 tools: Bash, Glob, Read, Edit
+steps:
+  - steps/shared/step-00-init.md
+  - steps/migration/step-00-init.md
+  - steps/migration/step-01-check.md
+  - steps/migration/step-02-create.md
+  - steps/migration/step-03-validate.md
 ---
 
 # EF Core Migration Agent
 
 Orchestrates migration creation with the "1 migration per feature" rule.
 
+**Progressive Steps:** Load `steps/migration/` for detailed instructions.
+
 > **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.

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

@@ -4,12 +4,21 @@ description: EF Core snapshot rebaser - resync ModelSnapshot with develop
 color: yellow
 model: sonnet
 tools: Bash, Glob, Read, Edit
+steps:
+  - steps/shared/step-00-init.md
+  - steps/rebase-snapshot/step-00-init.md
+  - steps/rebase-snapshot/step-01-backup.md
+  - steps/rebase-snapshot/step-02-fetch.md
+  - steps/rebase-snapshot/step-03-create.md
+  - steps/rebase-snapshot/step-04-validate.md
 ---
 
 # EF Core Rebase-Snapshot Agent
 
 Rebases ModelSnapshot on develop to resolve conflicts.
 
+**Progressive Steps:** Load `steps/rebase-snapshot/` for detailed instructions.
+
 ## Workflow
 
 1. **Backup** all migrations
@@ -21,35 +30,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
-rm -f Migrations/*Feature_*.cs
-rm -f Migrations/*Feature_*.Designer.cs
+# Delete branch migrations only
+rm -f Migrations/*${BRANCH_TYPE}_*.cs
+rm -f Migrations/*${BRANCH_TYPE}_*.Designer.cs
 
-# Regenerate
-dotnet ef migrations add Feature_1_7_0_Consolidated
+# Regenerate with MCP naming - OBLIGATOIRE
+mcp__smartstack__suggest_migration({ description: "...", context: DBCONTEXT_TYPE })
+# Résultat: core_v1.7.0_001_UserAuthConsolidated
+
+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

@@ -4,22 +4,33 @@ description: EF Core migration squasher - combine multiple migrations into one
 color: magenta
 model: sonnet
 tools: Bash, Glob, Read
+steps:
+  - steps/shared/step-00-init.md
+  - steps/squash/step-00-init.md
+  - steps/squash/step-01-backup.md
+  - steps/squash/step-02-fetch.md
+  - steps/squash/step-03-create.md
+  - steps/squash/step-04-validate.md
 ---
 
 # EF Core Squash Agent
 
-Consolide plusieurs migrations en une seule, en récupérant le ModelSnapshot de la branche parente.
+Consolide plusieurs migrations en une seule, en récupérant le ModelSnapshot **ET les migrations** de la branche parente.
+
+**Progressive Steps:** Load `steps/squash/` for detailed instructions.
 
 ## Principe Fondamental
 
 ```
-RÈGLE D'OR: Toujours récupérer le snapshot de la branche PARENTE
+RÈGLE D'OR: Récupérer SNAPSHOT + MIGRATIONS de la branche PARENTE
 
-feature/* → snapshot de develop
-develop   → snapshot de main
-release/* → snapshot de main
-hotfix/*  → snapshot de main
+feature/* → snapshot + migrations de develop
+develop   → snapshot + migrations de main
+release/* → snapshot + migrations de main
+hotfix/*  → snapshot + migrations de main
 main      → BLOQUÉ (jamais squash)
+
+⚠️ Ne JAMAIS récupérer uniquement le snapshot sans les migrations!
 ```
 
 ## Workflow
@@ -28,36 +39,56 @@ main      → BLOQUÉ (jamais squash)
 2. **List**: Migrations propres à cette branche (pas héritées)
 3. **Confirm**: Demander validation utilisateur
 4. **Backup**: Sauvegarder tous les fichiers
-5. **Fetch**: Récupérer ModelSnapshot de branche parente
-6. **Delete**: Supprimer migrations de la branche
-7. **Create**: Créer migration consolidée
+5. **Fetch**: Récupérer **ModelSnapshot ET migrations** de branche parente (CRUCIAL!)
+6. **Delete**: Supprimer migrations de la branche UNIQUEMENT
+7. **Create**: Créer migration consolidée (MCP obligatoire)
 8. **Validate**: Build + script OK
 
 ## Commandes Clés
 
 ```bash
-# Déterminer branche parente
-determine_base_branch  # → BASE_BRANCH, BRANCH_TYPE
+# Déterminer branche parente et DbContext
+determine_base_branch   # → BASE_BRANCH, BRANCH_TYPE
+detect_efcore_project   # → $DBCONTEXT, $DBCONTEXT_TYPE, $SCHEMA
 
 # 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 + MIGRATIONS de la branche parente
+# ═══════════════════════════════════════════════════════════════════════════
 git fetch origin "$BASE_BRANCH"
+
+# 1. Récupérer le ModelSnapshot
 git checkout "origin/$BASE_BRANCH" -- Migrations/*ModelSnapshot.cs
+echo "✅ Snapshot récupéré de origin/$BASE_BRANCH"
+
+# 2. Récupérer TOUTES les migrations de la branche parente
+# ⚠️ OBLIGATOIRE: Sans ça, les migrations de develop/main seront perdues!
+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
+  echo "  ✅ $base_name récupéré"
+done
+echo "✅ $(echo "$BASE_MIGS" | wc -l) migrations récupérées de origin/$BASE_BRANCH"
 
 # 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
+# $DBCONTEXT_TYPE = "core" ou "extensions" (de detect_efcore_project)
+mcp__smartstack__suggest_migration({ description: "...", context: DBCONTEXT_TYPE })
+# Résultat: core_v1.9.0_001_Description
+
+dotnet ef migrations add "$MIGRATION_NAME_FROM_MCP" --context "$DBCONTEXT"
 
 # Valider
 dotnet build && dotnet ef migrations script --idempotent > /dev/null
@@ -69,7 +100,9 @@ dotnet build && dotnet ef migrations script --idempotent > /dev/null
 - [ ] main/master = BLOQUÉ
 - [ ] User confirmation obtenue
 - [ ] Backup créé
-- [ ] Snapshot parent récupéré
+- [ ] **Snapshot parent récupéré** (origin/$BASE_BRANCH)
+- [ ] **Migrations parent récupérées** (fichiers .cs ET .Designer.cs)
+- [ ] Migrations de la branche supprimées (pas celles héritées!)
 - [ ] Build OK après squash
 - [ ] Script générable
 
@@ -77,9 +110,16 @@ dotnet build && dotnet ef migrations script --idempotent > /dev/null
 
 ```
 SQUASH - {current_branch}
-  Base:   {BASE_BRANCH} (snapshot récupéré)
-  Avant:  {N} migrations (propres à cette branche)
-  Apres:  1 migration consolidée
+  Base:   origin/{BASE_BRANCH}
+
+  Récupéré de {BASE_BRANCH}:
+    ✅ ModelSnapshot
+    ✅ {N} migrations (fichiers .cs + .Designer.cs)
+
+  Consolidé:
+    Avant:  {M} migrations (propres à cette branche)
+    Après:  1 migration ({MIGRATION_NAME} via MCP)
+
   Backup: .claude/gitflow/backup/migrations/squash_{timestamp}/
 
 Prochains: /efcore:db-reset, /efcore:db-deploy

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
 ```
 
 ---

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

@@ -12,13 +12,18 @@ model: haiku
 
 ---
 
-## STEP 1: Détecter Configuration
+## STEP 1: Détecter Configuration et DbContext
 
 ```bash
-detect_efcore_project
+detect_efcore_project   # Appelle detect_dbcontext() automatiquement
 detect_environment
+
+echo "DbContext: $DBCONTEXT ($DBCONTEXT_TYPE)"
+echo "Schema: $SCHEMA"
 ```
 
+**Si DbContext non détecté :** Afficher le status des DEUX contextes.
+
 ---
 
 ## STEP 2: Invoquer MCP
@@ -26,7 +31,10 @@ detect_environment
 ```json
 {
   "tool": "mcp__smartstack__check_migrations",
-  "parameters": { "branch": "<current_branch>" }
+  "parameters": {
+    "branch": "<current_branch>",
+    "projectPath": "<auto-detect>"
+  }
 }
 ```
 
@@ -37,7 +45,10 @@ Extraire: `migrations[]`, `conflicts[]`
 ## STEP 3: Tester Connexion
 
 ```bash
-CONNECTION_OK=$(dotnet ef database list 2>&1)
+CONNECTION_OK=$(dotnet ef database list \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" 2>&1)
 ```
 
 ---
@@ -45,8 +56,15 @@ CONNECTION_OK=$(dotnet ef database list 2>&1)
 ## STEP 4: Compter Migrations
 
 ```bash
-APPLIED=$(dotnet ef migrations list | grep -v "(Pending)" | wc -l)
-PENDING=$(dotnet ef migrations list | grep "(Pending)" | wc -l)
+APPLIED=$(dotnet ef migrations list \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" | grep -v "(Pending)" | wc -l)
+
+PENDING=$(dotnet ef migrations list \
+  --context "$DBCONTEXT" \
+  --project "$INFRA_PROJECT" \
+  --startup-project "$STARTUP_PROJECT" | grep "(Pending)" | wc -l)
 ```
 
 ---