apt-mcp-agent-setup 1.3.26 → 2.0.1

package/src/templates/copilot-instructions.md

@@ -26,8 +26,8 @@ Single-context layout — one `CONTEXT.md` + `docs/adr/` at the repo root. See `
 
 **You have `apt-mcp-agent` MCP tools available. You MUST use them:**
 - **Before ANY code search**: use `explore_code` or `code_search` — NOT grep_search for code symbols
-- **Before ANY code change**: call `pipeline_status` — NO PIPELINE = NO CODE EDITS
-- **After each pipeline step**: call `pipeline_checkpoint` to record progress
+- **Before executable changes**: call `pipeline_status`, then `pipeline_start` or `pipeline_use`
+- **After each pipeline step**: call `pipeline_checkpoint` with required `task` and `runId`
 - **Session start**: call `read_knowledge` + `pipeline_status`
 
 Ignoring these tools and using only built-in IDE tools is a **P0 protocol violation**.
@@ -55,9 +55,9 @@ 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.
-**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.**
+Before writing any code or implementing features, you MUST follow one of the three enforced pipelines below.
+**Start or bind a run with `pipeline_start(pipeline, task, workspace)` or `pipeline_use(task, runId)`.**
+**After each step call `pipeline_checkpoint(task, runId, step, status="completed", summary)`.**
 
 Content-only documentation changes that do not affect executable behavior are exempt from PRD, issue, and TDD pipeline steps. Agent contracts such as `AGENTS.md`, `SKILL.md`, trigger maps, pipeline definitions, and runtime configuration are operational and are not exempt.
 Skipping steps or executing out-of-order is a **P0 protocol violation** — the tool will REJECT invalid transitions.
@@ -82,10 +82,19 @@ 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
-- To start a new cycle → call `pipeline_reset()` to clear previous state
+- After each step completion → call `pipeline_checkpoint(task, runId, step, "completed", summary)`
+- Before each step start → call `pipeline_status(task, runId)`
+- To cancel a run → call `pipeline_reset(task, runId, confirm=true)`; history is preserved
 - The MCP tool enforces ordering at runtime — out-of-order calls are **rejected with error**
 
 

package/src/templates/cursorrules.mdc

@@ -32,8 +32,8 @@ Single-context layout — one `CONTEXT.md` + `docs/adr/` at the repo root. See `
 
 **You have `apt-mcp-agent` MCP tools available. You MUST use them:**
 - **Before ANY code search**: use `explore_code` or `code_search` — NOT grep_search for code symbols
-- **Before ANY code change**: call `pipeline_status` — NO PIPELINE = NO CODE EDITS
-- **After each pipeline step**: call `pipeline_checkpoint` to record progress
+- **Before executable changes**: call `pipeline_status`, then `pipeline_start` or `pipeline_use`
+- **After each pipeline step**: call `pipeline_checkpoint` with required `task` and `runId`
 - **Session start**: call `read_knowledge` + `pipeline_status`
 
 Ignoring these tools and using only built-in IDE tools is a **P0 protocol violation**.
@@ -55,9 +55,9 @@ 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.
-**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.**
+Before writing any code or implementing features, you MUST follow one of the three enforced pipelines below.
+**Start or bind a run with `pipeline_start(pipeline, task, workspace)` or `pipeline_use(task, runId)`.**
+**After each step call `pipeline_checkpoint(task, runId, step, status="completed", summary)`.**
 
 Content-only documentation changes that do not affect executable behavior are exempt from PRD, issue, and TDD pipeline steps. Agent contracts such as `AGENTS.md`, `SKILL.md`, trigger maps, pipeline definitions, and runtime configuration are operational and are not exempt.
 Skipping steps or executing out-of-order is a **P0 protocol violation** — the tool will REJECT invalid transitions.
@@ -82,10 +82,19 @@ 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
-- To start a new cycle → call `pipeline_reset()` to clear previous state
+- After each step completion → call `pipeline_checkpoint(task, runId, step, "completed", summary)`
+- Before each step start → call `pipeline_status(task, runId)`
+- To cancel a run → call `pipeline_reset(task, runId, confirm=true)`; history is preserved
 - The MCP tool enforces ordering at runtime — out-of-order calls are **rejected with error**
 
 ---

package/src/templates/mcp-tools.md

@@ -1,5 +1,18 @@
 # MCP Tools — Decision Tree & Conventions
 
+## Developer pipeline 2.0
+
+- Start: `pipeline_start(pipeline, task, workspace)` with a canonical lowercase task ID.
+- Resume: `pipeline_use(task, runId)` binds the MCP session and project-scoped backends to the run workspace.
+- Progress: `pipeline_checkpoint(task, runId, step, status="completed", summary)` only accepts the next step.
+- Inspect: `pipeline_status()` lists current runs; task and runId inspect one run without rebinding.
+- Cancel: `pipeline_reset(task, runId, confirm=true)` preserves state and ledger history.
+- Finish: `pipeline_prepare_merge(task, runId)` never merges, pushes, publishes, or deletes a branch.
+
+Git projects share pipeline state through the Git common directory. Non-Git projects use `.agents/pipelines` and can run in place. Git bootstrap for a managed worktree always requires a read-only preview and direct user confirmation.
+
+Pipeline enforcement covers proxied MCP tools only. Native host shell and file tools must follow the returned `workspacePath` explicitly.
+
 ## 🔍 Tool Selection — When to Use What
 
 ### Code Search & Navigation

package/src/templates/windsurfrules.md

@@ -26,8 +26,8 @@ Single-context layout — one `CONTEXT.md` + `docs/adr/` at the repo root. See `
 
 **You have `apt-mcp-agent` MCP tools available. You MUST use them:**
 - **Before ANY code search**: use `explore_code` or `code_search` — NOT grep_search for code symbols
-- **Before ANY code change**: call `pipeline_status` — NO PIPELINE = NO CODE EDITS
-- **After each pipeline step**: call `pipeline_checkpoint` to record progress
+- **Before executable changes**: call `pipeline_status`, then `pipeline_start` or `pipeline_use`
+- **After each pipeline step**: call `pipeline_checkpoint` with required `task` and `runId`
 - **Session start**: call `read_knowledge` + `pipeline_status`
 
 Ignoring these tools and using only built-in IDE tools is a **P0 protocol violation**.
@@ -55,9 +55,9 @@ 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.
-**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.**
+Before writing any code or implementing features, you MUST follow one of the three enforced pipelines below.
+**Start or bind a run with `pipeline_start(pipeline, task, workspace)` or `pipeline_use(task, runId)`.**
+**After each step call `pipeline_checkpoint(task, runId, step, status="completed", summary)`.**
 
 Content-only documentation changes that do not affect executable behavior are exempt from PRD, issue, and TDD pipeline steps. Agent contracts such as `AGENTS.md`, `SKILL.md`, trigger maps, pipeline definitions, and runtime configuration are operational and are not exempt.
 Skipping steps or executing out-of-order is a **P0 protocol violation** — the tool will REJECT invalid transitions.
@@ -82,10 +82,19 @@ 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
-- To start a new cycle → call `pipeline_reset()` to clear previous state
+- After each step completion → call `pipeline_checkpoint(task, runId, step, "completed", summary)`
+- Before each step start → call `pipeline_status(task, runId)`
+- To cancel a run → call `pipeline_reset(task, runId, confirm=true)`; history is preserved
 - The MCP tool enforces ordering at runtime — out-of-order calls are **rejected with error**