hotfixlisted

# Hotfix Apply a targeted fix with minimal ceremony. This pipeline is intentionally abbreviated — use it only when the problem is already diagnosed and the change is small and well-understood. > **When to use `/debug` instead:** If you don't yet know the root cause, use `/debug` to diagnose first, then return here to apply the fix. ## 1. Confirm the fix is in scope for hotfix Before starting, confirm all of the following are true: - The **root cause** is known - The fix touches **3 or fewer files** and fewer than **50 lines of logic** - **No new dependencies** are introduced - **No schema changes** are required - The fix does not introduce a new architectural pattern If any of these are false, use `/implement` instead — state which condition failed and why. ## 2. Branch setup Run `git branch --show-current`. - If on `main` or `master`: create a `hotfix/<brief-slug>` branch immediately. Do not proceed on main. - If already on a non-main branch: confirm it is the correct branch for this fix. No worktree isolation. The engineer works directly on the hotfix branch. ## 3. Engineer — direct fix Route to the appropriate engineer based on file type: | File type | Engineer | |-----------|----------| | `.cs` / .NET | **csharp-engineer** | | `.ts` / `.vue` | **frontend-engineer** | | `.ts` in an MCP server | **mcp-engineer** | | SQL / migration | **database-engineer** | Pass: - Exact files to change - Root cause and the intended fix - How to verify (test command or manual r