apt-mcp-agent-setup 1.3.25 → 1.3.27

package/src/templates/windsurfrules.md

@@ -55,7 +55,7 @@ If the specialized MCP tool `code_search` or other core MCP tools (e.g., `recall
 
 ### 🛠️ ENFORCED DEVELOPER PIPELINES (MANDATORY — MCP TOOL GATE)
 
-Before writing any code or implementing features, you MUST follow one of the two enforced pipelines below.
+Before writing any code or implementing features, you MUST follow one of the three enforced pipelines below.
 **After completing each step, call the `pipeline_checkpoint` MCP tool to record progress.**
 **Before starting any step, call `pipeline_status` to verify the previous step is completed.**
 
@@ -82,6 +82,15 @@ Skipping steps or executing out-of-order is a **P0 protocol violation** — the
 4. **`/to-issues`** → Create tracking issues for the fix and any follow-up work.
 5. **`/tdd`** → Write regression tests first, then implement the fix.
 
+#### 🔧 Hotfix Pipeline (2 steps — for small, isolated changes ≤3 files)
+```
+/verify-scope → /fix-and-test
+```
+1. **`/verify-scope`** → Confirm change is small (≤3 files, no new API, no dependency changes). Provide scope justification in summary.
+2. **`/fix-and-test`** → Apply fix + write regression test if applicable.
+
+**When to use hotfix:** typos, config values, minor CSS, off-by-one errors, missing imports, small bug fixes with obvious root cause. If the change grows beyond scope, reset and escalate to `bugfix` or `feature` pipeline.
+
 **ENFORCEMENT PROTOCOL:**
 - After each step completion → call `pipeline_checkpoint(pipeline, step, "completed", summary)`
 - Before each step start → call `pipeline_status()` to verify previous step is done