@atlashub/smartstack-cli 4.39.0 → 4.40.0

package/package.json

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

package/templates/skills/dev-start/SKILL.md

@@ -278,7 +278,9 @@ If `--frontend-only`: skip backend checks.
 
 ## Step 5: Launch backend
 
-If NOT already running and NOT `--frontend-only`:
+Track whether the backend was just launched: `BACKEND_JUST_LAUNCHED=true/false`. This is used in Step 7 for cache invalidation.
+
+If NOT already running and NOT `--frontend-only` (set `BACKEND_JUST_LAUNCHED=true`):
 
 ```bash
 # cd into the API directory first
@@ -313,8 +315,10 @@ Use `Bash(run_in_background=true)` so it runs in background.
 
 ## Step 7: Handle admin password
 
-1. If `.claude/dev-session.json` exists and contains a password and `--reset` NOT specified -> reuse stored credentials
-2. If `--reset` OR no stored password:
+**Cache invalidation rule:** If the backend was just launched in Step 5 (i.e., it was NOT already running), the cache is STALE because `MigrateAsync()` + `HasData()` may have re-seeded the admin user with the default password hash, overwriting any previously set password. In this case, ALWAYS run a fresh admin reset regardless of `dev-session.json`.
+
+1. If `.claude/dev-session.json` exists and contains a password AND `--reset` NOT specified AND the backend was already running (NOT launched in Step 5) -> reuse stored credentials
+2. If `--reset` OR no stored password OR backend was just launched in Step 5:
    a. If backend was just launched, wait for it to be UP first.
       Run the full wait in a **single bash command** to avoid multiple tool calls:
       ```bash
@@ -335,9 +339,9 @@ Use `Bash(run_in_background=true)` so it runs in background.
       If `/scalar` does not respond after 30s, warn the user and attempt the reset anyway.
    b. Run admin reset using the connection string extracted from appsettings (Step 3):
       ```bash
-      smartstack admin reset --connection "{CONN_STR}" --force --json
+      smartstack admin reset --connection '{CONN_STR}' --force --json
       ```
-      **IMPORTANT:** Always pass `--connection` with the full connection string. Without it, the CLI shows an interactive environment picker that blocks execution.
+      **IMPORTANT:** Always pass `--connection` with the full connection string (single-quoted to avoid shell expansion). Without it, the CLI shows an interactive environment picker that blocks execution.
    c. Parse JSON output to extract email and password
    d. Write `.claude/dev-session.json`:
       ```json
@@ -380,7 +384,7 @@ Use `Bash(run_in_background=true)` so it runs in background.
 1. **NEVER debug or fix code** - This skill ONLY starts processes. If the backend or frontend fails to start, display the error and STOP. Do NOT attempt to: clean/restore/rebuild, upgrade packages, inspect DLLs, clear NuGet cache, read .csproj files, or any other diagnostic/repair action. The user will fix the issue themselves.
 2. **Fail-fast on crash** - After launching backend in background, wait 5s then check TaskOutput. If the process already exited or shows errors, report and STOP immediately.
 3. **Backend must be READY before admin reset** - First poll the port (netstat), then poll the `/scalar` endpoint (HTTP 200/302) to confirm the API is fully initialized. Kestrel binds the port before the app finishes starting, so port-only checks are insufficient.
-4. **Admin reset requires --connection** - Always pass `--connection "{CONN_STR}"` to avoid the interactive environment picker.
+4. **Admin reset requires --connection** - Always pass `--connection '{CONN_STR}'` (single-quoted to avoid shell expansion) to avoid the interactive environment picker.
 5. **Read config files in parallel** - When reading appsettings, .env, and launchSettings, use multiple Read calls in a single message.
 6. **Cross-worktree support** - Detect the correct API directory regardless of which worktree we're in.
 7. **No MCP required** - This skill only uses bash commands and the `smartstack` CLI.