@raquezha/norpiv 0.0.4 → 0.0.6

package/README.md

@@ -20,7 +20,7 @@ Auxiliary hygiene:
 
 | Command | Purpose | Input / Output Files |
 | :--- | :--- | :--- |
-| `/cleanup` | Declutter Git branches and completed task folders after work is merged/closed. | Prunes finished task folders & resets pointer when safe |
+| `/post-merge-prune` | Delete stale local branches after a PR/MR is merged, prune remote refs, and clean completed task folders. | Post-merge branch cleanup plus safe task-folder cleanup |
 
 ---
 
@@ -51,7 +51,7 @@ Best for trying or handing off RPIV skills without installing the full `nothing`
 
 ```bash
 npx -y skills add raquezha/nothing --full-depth -g -a pi \
-  -s triage frame grill-with-docs plan implement verify sync cleanup update-docs distill \
+  -s triage frame grill-with-docs plan implement verify sync post-merge-prune update-docs distill \
   -y
 ```
 
@@ -84,7 +84,7 @@ Targets:
 
 | Hat | Purpose |
 | :--- | :--- |
-| `pi --rpiv` | Full RPIV workflow. Loads triage, frame, grill-with-docs, plan, implement, verify, sync, cleanup, and update-docs. |
+| `pi --rpiv` | Full RPIV workflow. Loads triage, frame, grill-with-docs, plan, implement, verify, sync, post-merge-prune, and update-docs. |
 | `pi --notes` | Conversation distiller. Saves useful thinking to Obsidian without RPIV ceremony. |
 
 ## 📝 Pre-RPIV note capture
@@ -152,7 +152,7 @@ Obsidian note → /triage → RPIV             (only when ready to commit)
    ```text
    /verify
    /sync
-   /cleanup
+   /post-merge-prune
    ```
 
 ## 🧭 Shared helper scripts

package/bin/norpiv-install.cjs

@@ -136,7 +136,7 @@ function writeCodexAdapter(root, names, sharedNames, opts) {
   const sharedLines = sharedNames.length
     ? `\nShared helpers:\n\n${sharedNames.map((name) => `- ${name}/`).join("\n")}\n`
     : "";
-  const body = `# norpiv RPIV skills for Codex\n\nCodex does not currently auto-load Pi/Claude SKILL.md bundles from npm.\n\nUse these installed skill instructions as a portable RPIV workflow reference:\n\n${names.map((name) => `- ${name}/SKILL.md`).join("\n")}\n${sharedLines}\nCore lifecycle: triage → frame → grill-with-docs → plan → implement → verify → sync → cleanup.\n\nIf your Codex environment supports AGENTS.md discovery, copy or reference this file from your project.\n`;
+  const body = `# norpiv RPIV skills for Codex\n\nCodex does not currently auto-load Pi/Claude SKILL.md bundles from npm.\n\nUse these installed skill instructions as a portable RPIV workflow reference:\n\n${names.map((name) => `- ${name}/SKILL.md`).join("\n")}\n${sharedLines}\nCore lifecycle: triage -> frame -> grill-with-docs -> plan -> implement -> verify -> sync -> post-merge-prune.\n\nIf your Codex environment supports AGENTS.md discovery, copy or reference this file from your project.\n`;
   log(opts, `write Codex adapter ${adapter}`);
   if (!opts.dryRun) fs.writeFileSync(adapter, body);
 }

package/distill/SKILL.md

@@ -180,7 +180,7 @@ If writing fails, output the markdown to stdout so the user can copy it manually
 - Does not require `WORK.md`
 - Does not interact with `.workflow/` directory
 - Does not sync to Jira, GitHub, or GitLab
-- Does not run cleanup
+- Does not run post-merge-prune
 - Does not require any existing task or ticket
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raquezha/norpiv",
-  "version": "0.0.4",
+  "version": "0.0.6",
   "description": "Bundled RPIV workflow skills for Pi, Claude, and Codex-style coding agents",
   "type": "commonjs",
   "bin": {
@@ -8,7 +8,7 @@
   },
   "files": [
     "bin",
-    "cleanup",
+    "post-merge-prune",
     "distill",
     "frame",
     "grill-with-docs",
@@ -44,7 +44,7 @@
       "verify",
       "sync",
       "update-docs",
-      "cleanup",
+      "post-merge-prune",
       "distill"
     ]
   }

package/post-merge-prune/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: post-merge-prune
+description: "Post-merge branch cleanup only. Use after a PR/MR is merged and the local feature branch is stale: prune remote refs and delete local branches already merged into the target branch."
+---
+
+# Skill: post-merge-prune
+
+> [!IMPORTANT]
+> **LLM INSTRUCTION**: This skill is a deliberate post-merge deletion tool. If the user invokes `post-merge-prune`, they want stale local branches removed after merge into the intended target branch. Do not offer a menu of options. Do not ask "Dry run or Execute?". Proceed directly.
+
+Use this skill after a PR/MR has been merged into its intended branch, typically `main`, to remove stale remote-tracking refs and delete the matching local branches because the work is done.
+
+## Goal
+- Switch to the intended target branch (`main` by default).
+- Prune deleted remote branches.
+- Delete local branches that are already merged into the target branch.
+- Optionally remove matching workflow task folders.
+
+## Workflow
+
+### Step 1: Go to the target branch
+- `git checkout main` (or the intended merge target)
+- If the tree is dirty, stash first.
+
+### Step 2: Prune remote-tracking refs
+- `git remote update origin --prune`
+- This removes local refs for remote branches that were deleted after merge.
+
+### Step 3: Delete merged local branches
+Iterate through local branches and delete the ones already merged into the target branch:
+- Use `git branch -d <branch>` for normal merges.
+- If `-d` refuses but `git log main..[branch]` is empty, the branch was squash-merged; use `git branch -D <branch>`.
+- Never delete the active target branch.
+
+### Step 4: Optional workflow cleanup
+If a deleted branch has a matching `.workflow/tasks/*` folder, remove it.
+If `.workflow/active_task.json` points to a deleted task, clear it.
+
+### Step 5: Verify
+- `git branch -a` should no longer show deleted refs.
+- `git branch --merged main` should only show branches you intend to keep.
+- `.workflow/tasks/` should not contain deleted tasks.
+
+## Guardrails
+- **RESOLUTION OVER REPORTING**: If merge status is unclear, check `git branch --merged main` or `git log main..branch` and resolve it.
+- **NO DRY RUNS BY DEFAULT**: Execute the cleanup unless the user explicitly asks for a preview.
+- **SMART DELETE**: If a branch is squash-merged, delete it with `git branch -D` after confirming there are no unique commits left.
+- **ACTIVE BRANCH PROTECTION**: Do not delete the current branch.
+- **UNMERGED WORK**: If a branch has unique commits and no remote, ask once before force-deleting.
+
+## Output Contract
+Return a concise report:
+- **Cleaned**: deleted branches / task folders
+- **Kept**: branches still in use
+- **Working Branch**: the branch left checked out (should be `main`)

package/scripts/get-pi-model.sh

@@ -0,0 +1,27 @@
+#!/bin/bash
+# Deterministically grabs the active Pi model from the current session logs
+
+# Format PWD to match Pi's session directory naming convention
+SAFE_PWD=$(pwd | sed 's/\//-/g' | sed 's/^-/--/')
+TARGET_DIR="$HOME/.pi/agent/sessions/${SAFE_PWD}--"
+
+if [ -d "$TARGET_DIR" ]; then
+    LATEST_FILE=$(ls -t "$TARGET_DIR" | head -n 1 2>/dev/null)
+    if [ -n "$LATEST_FILE" ]; then
+        PROVIDER=$(cat "$TARGET_DIR/$LATEST_FILE" | grep -o '"provider":"[^"]*"' | tail -n 1 | cut -d'"' -f4)
+        MODEL=$(cat "$TARGET_DIR/$LATEST_FILE" | grep -o '"model":"[^"]*"' | tail -n 1 | cut -d'"' -f4)
+        
+        if [ -n "$MODEL" ]; then
+            # If provider exists, prefix it, otherwise just return model
+            if [ -n "$PROVIDER" ]; then
+                echo "$PROVIDER:$MODEL"
+            else
+                echo "UnknownProvider:$MODEL"
+            fi
+            exit 0
+        fi
+    fi
+fi
+
+# Fallback if no active session log can be parsed
+echo "UnknownAgent:UnknownModel"

package/scripts/reposcry-bootstrap.sh

@@ -42,6 +42,30 @@ reposcry_indexed_files() {
   reposcry stats 2>/dev/null | awk '/Files indexed:/ {print $3; exit}'
 }
 
+# Quick health check for Pulse info
+check_pulse() {
+  if ! command -v reposcry >/dev/null 2>&1; then
+    echo "PULSE: Missing (Not installed)"
+    return
+  fi
+  if [[ ! -d .reposcry ]]; then
+    echo "PULSE: Cold (No cache)"
+    return
+  fi
+  local files
+  files=$(reposcry_indexed_files || echo "0")
+  if [[ "$files" == "0" ]]; then
+    echo "PULSE: Cold (Zero files)"
+  else
+    echo "PULSE: Warm ($files files)"
+  fi
+}
+
+if [[ "${1:-}" == "--pulse" ]]; then
+  check_pulse
+  exit 0
+fi
+
 ensure_reposcry_gitignore
 refuse_tracked_reposcry_cache
 

package/scripts/reposcry-task-context.sh

@@ -20,7 +20,15 @@ cd "$REPO_ROOT"
 "$SCRIPT_DIR/reposcry-bootstrap.sh" || true
 
 mkdir -p .reposcry
-BUDGET=${REPOSCRY_CONTEXT_BUDGET:-20000}
+
+# Detect low-token modes (Caveman, etc.)
+DEFAULT_BUDGET=20000
+if [[ "${CAVEMAN_MODE:-off}" != "off" ]] || [[ "${LOW_TOKEN_MODE:-0}" == "1" ]]; then
+  DEFAULT_BUDGET=5000
+  echo "Low-token mode detected: reducing context budget to $DEFAULT_BUDGET"
+fi
+
+BUDGET=${REPOSCRY_CONTEXT_BUDGET:-$DEFAULT_BUDGET}
 OUTPUT_PATH=".reposcry/AI_CONTEXT.md"
 
 echo "Generating RepoScry task context at $OUTPUT_PATH..."

package/scripts/validate_active_task.sh

@@ -289,7 +289,7 @@ if [[ -n "$WORK_MD" && -f "$WORK_MD" ]]; then
 fi
 
 if [[ "$META_STATUS" =~ ^(done|archived)$ ]]; then
-  warn "active pointer references a task with status=$META_STATUS; consider cleanup, archive handling, or reopening intentionally"
+  warn "active pointer references a task with status=$META_STATUS; consider post-merge-prune, archive handling, or reopening intentionally"
 fi
 
 echo
@@ -315,7 +315,7 @@ if [[ -n "$WORK_MD" && -f "$WORK_MD" ]]; then
 fi
 if [[ -n "$META_STATUS" && "$META_STATUS" =~ ^(done|archived)$ ]]; then
   echo "  - Choose intentionally: $TRIAGE_HELPER ${TASK_SOURCE:-local} ${TASK_ID:-task} reopen"
-  echo "  - Or leave closed and run cleanup when appropriate."
+  echo "  - Or leave closed and run post-merge-prune when appropriate."
 fi
 if [[ "$WARNINGS" -eq 0 && "$ERRORS" -eq 0 ]]; then
   echo "  - No fixes suggested."

package/sync/SKILL.md

@@ -128,4 +128,4 @@ Return a concise summary:
 - **Action**: no-op / updated existing status / created new status
 - **Reason**: marker found, body identical, marker missing, etc.
 - **Link**: remote comment/note URL if available
-- **Next step**: review, verify, cleanup, or continue implementation
+- **Next step**: review, verify, post-merge-prune, or continue implementation

package/triage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: triage
-description: "Ingest or resume a tracked/local task in the RPIV workspace. Use when starting or returning to jira:, github:, gitlab:, or local: work and you need canonical WORK.md state without duplicating scaffold."
+description: "Ingest or resume a tracked/local task in the RPIV workspace. Use when starting or returning to jira:, github:, gitlab:, or local: work and you need canonical WORK.md state without duplicating the scaffold."
 ---
 
 # Skill: triage
@@ -8,10 +8,10 @@ description: "Ingest or resume a tracked/local task in the RPIV workspace. Use w
 Start RPIV by creating, resuming, or explicitly reopening a task workspace.
 
 ## Guardrails
-- READ: user argument, `.workflow/active_task.json` when present, target `metadata.json`, and target `WORK.md` when resuming.
-- WRITE: `.workflow/tasks/[source-id]/WORK.md`, `.workflow/tasks/[source-id]/metadata.json`, `.workflow/active_task.json`; optional `.reposcry/` cache files only when RepoScry is installed.
+- READ: user argument, `.workflow/active_task.json` if present, target `metadata.json`, and target `WORK.md` if resuming.
+- WRITE: `.workflow/tasks/[source-id]/WORK.md`, `.workflow/tasks/[source-id]/metadata.json`, `.workflow/active_task.json`; optional `.reposcry/` cache files only if RepoScry is installed.
 - On **create**, initialize required guarded sections only if absent: `[BRIEF]`, `[GRILL]`, `[PLAN]`, `[LOG]`, `[META]`.
-- On **resume**, only update `.workflow/active_task.json`, metadata timestamps/state as needed, `[META]`, and append one concise `[LOG]` entry.
+- On **resume**, only update `.workflow/active_task.json`, metadata timestamps/state as needed, and `[META]`, then append one concise `[LOG]` entry.
 - NEVER: duplicate guarded sections.
 - NEVER: overwrite existing `[BRIEF]`, `[GRILL]`, or `[PLAN]` during triage.
 - NEVER: create `PROBLEM.md`, `PRD.md`, `PLAN.md`, or `EVIDENCE.md`.
@@ -21,49 +21,34 @@ Start RPIV by creating, resuming, or explicitly reopening a task workspace.
 - NEVER: mutate `done` or `archived` tasks unless the user explicitly requested `reopen`, `fresh`, or `reset`.
 
 ## Command forms
-- `/triage local:setup-v2` — auto mode: create if missing, resume if active/blocked.
-- `/triage resume local:setup-v2` — resume existing task; create if missing only when helper reports that behavior.
-- `/triage reopen local:setup-v2` — explicitly reopen a done/archived task and mark it active.
-- `/triage fresh local:setup-v2` — archive/reset the previous task workspace and create a fresh one.
-- `/triage reset local:setup-v2` — alias for fresh/reset behavior when supported by the helper.
 
-## Semantics
-
-### Create
-Use when the target task folder does not exist.
-- Fetch remote issue data for `github:`, `gitlab:`, or `jira:` sources.
-- Create `.workflow/tasks/[source-id]/metadata.json` with at least `id`, `source`, `taskFolder`, `branch`, `status`, `phase`, `createdAt`, `updatedAt`.
-- Create `.workflow/tasks/[source-id]/WORK.md` with guarded RPIV sections.
-- Set `status=active` and `phase=triaged`.
-- Write canonical `.workflow/active_task.json`.
-
-### Resume
-Use when the task exists and `status` is `active`, `blocked`, or missing/legacy.
-- Do not refetch remote data.
-- Do not rewrite the brief, grill notes, or plan.
+### /triage local:setup-v2
+- **Standard/auto mode**: create if missing, resume if active/blocked.
+- Will not rewrite brief, grill notes, or plan.
 - Backfill missing metadata fields without destroying unknown fields.
 - Refresh active pointer and human-readable `[META]`.
 - Append one timestamped `[LOG]` entry such as `Task resumed via /triage`.
 
-### Reopen
-Use only when the user explicitly asks to reopen a task that is `done` or `archived`.
+### /triage local:setup-v2 reopen
+- Use only if user explicitly asks to reopen a task that is `done` or `archived`.
 - Mark `status=active`.
 - Preserve existing `WORK.md` history.
 - Append a `[LOG]` entry explaining the reopen.
 - Recommend returning to the next valid RPIV stage based on existing sections.
 
-### Fresh / reset
-Use only when the user explicitly asks to start over.
-- Preserve or archive the old task workspace before creating a new one when the helper supports it.
-- Create a new task workspace with clean guarded sections.
+### /triage local:setup-v2 fresh / reset
+- Use only if user explicitly asks to start over.
+- Preserve or archive old task workspace before creating new one when helper supports it.
+- Create new task workspace with clean guarded sections.
 - Do not silently delete task history.
 
 ### Refuse
-Use when auto/resume mode targets a `done` or `archived` task.
+- Use when auto/resume mode targets a `done` or `archived` task.
 - Stop instead of mutating.
-- Tell the user to choose `reopen` or `fresh/reset`.
+- Tell user to choose `reopen` or `fresh/reset`.
 
 ## Workflow
+
 1. Parse optional mode and required namespace:
    - `jira:PROJ-123` -> `jira-PROJ-123`
    - `github:42` -> `github-42`
@@ -72,23 +57,24 @@ Use when auto/resume mode targets a `done` or `archived` task.
 2. Run the bundled helper script: `../scripts/triage_helper.sh <source> <id> [mode]`.
    - Preferred absolute path: `<skill_dir>/../scripts/triage_helper.sh`.
 3. Read the resulting active pointer, metadata, and `WORK.md`.
-4. Determine action from helper output and task state: `created`, `resumed`, `reopened`, `refused`, or `fresh/reset`.
-5. Optional RepoScry bootstrap: if the bundled `../scripts/reposcry-bootstrap.sh` is available, run it to seed `.reposcry/` for later `/frame` and `/grill-with-docs`. The helper must ensure `.reposcry/` is ignored, must stop if `.reposcry/` is tracked/staged, and should continue normally when RepoScry is unavailable.
-6. **Technical Pre-check (Repo Pulse)** for created/reopened/resumed tasks:
-   - Extract key filenames, classes, commands, or keywords from the issue/task description.
-   - Verify existence on the current branch when concrete files are named.
-   - Check recent commits or open PRs only when relevant to the named files/scope.
-   - Version-check environment/dependencies only when the task depends on a version claim.
-7. Classify the task: Problem / Proposal.
-8. **Log Findings**: append concise Repo Pulse and classification findings to `[LOG]` only. Do not edit `[BRIEF]`, `[GRILL]`, or `[PLAN]`.
-9. **Branch Guidance**: record the current branch in `[META]`. For `jira:` tasks, also preserve the Jira key in `[META]` and mention that `/implement` must use it in the commit subject. Planning on `main`/`master` is allowed; implementation must use `/implement` branch enforcement.
-10. End by recommending the next valid command:
-   - newly created -> `/frame`
-   - existing with empty `[BRIEF]` -> `/frame`
-   - framed but not grilled -> `/grill-with-docs`
-   - grilled but not planned -> `/plan`
-   - planned -> await explicit `/implement` or `EXECUTE`
-   - refused -> ask user to choose `reopen` or `fresh/reset`
+4. Determine action based on helper output and task state: `created`, `resumed`, `reopened`, `refused`, `fresh/reset`.
+5. Optional RepoScry bootstrap: if bundled `../scripts/reposcry-bootstrap.sh` available, run it to seed `.reposcry/` for later `/frame` and `/grill-with-docs`.
+   - Run `../scripts/reposcry-bootstrap.sh --pulse` to determine "Repo Pulse" (Warm/Cold/Missing) for the output contract.
+   - Run `../scripts/reposcry-bootstrap.sh` to ensure the local cache is initialized.
+   - The helper must ensure `.reposcry/` is ignored, must stop if `.reposcry/` tracked/staged, and continue normally if RepoScry is unavailable.
+6. Verify branch: ensure current branch matches metadata `branch` (or is `main`/`master` for planning).
+7. If task was newly created, infer classification:
+   - `github:`, `gitlab:`, `jira:` labels/type often indicate Problem (bug) or Proposal (feature).
+   - Local tasks default to Proposal unless specified.
+8. If resuming, check `[BRIEF]` and `[PLAN]` completion status.
+9. **Final Guidance**: record current branch in `[META]`. For `jira:` tasks, also preserve the Jira key in `[META]` and mention `/implement` must use it in the commit subject. Planning on `main`/`master` allowed; implementation will use `/implement` branch enforcement.
+10. End by recommending next valid command:
+    - newly created -> `/frame`
+    - existing empty `[BRIEF]` -> `/frame`
+    - framed but not grilled -> `/grill-with-docs`
+    - grilled but not planned -> `/plan`
+    - planned -> await explicit `/implement` or `EXECUTE`
+    - refused -> ask user to choose `reopen` or `fresh/reset`
 
 ## Output contract
 End with:
@@ -97,6 +83,6 @@ End with:
 - **Status**: active / blocked / done / archived / unknown
 - **Phase**: triaged / framed / grilled / planned / implementing / verifying / synced / closed / unknown
 - **Branch**: current branch
-- **Repo Pulse**: Found / Missing / Outdated / Not applicable
+- **Repo Pulse**: Warm / Cold / Missing / Not applicable
 - **Classification**: Problem / Proposal
 - **Next step**: `/frame`, `/grill-with-docs`, `/plan`, `/implement`, or explicit reopen/fresh choice

package/verify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: verify
-description: Verify the active slice or task against WORK.md, quality gates, and review readiness. Use after implementation or manual changes to decide whether work is ready for sync, review, or cleanup.
+description: Verify the active slice or task against WORK.md, quality gates, and review readiness. Use after implementation or manual changes to decide whether work is ready for sync, review, or post-merge-prune.
 ---
 
 # Skill: verify
@@ -19,9 +19,9 @@ The final gate for a slice or task. Verify truth before reporting progress.
 2. Run stated verification commands and available quality gates.
 3. If RepoScry is available, optionally add graph-aware evidence with commands such as `reposcry validate main HEAD` and `reposcry --repo . get_affected_flows main HEAD`. Treat RepoScry as supplemental evidence, not a hard requirement. Verify `.reposcry/` is not staged or tracked before reporting review readiness.
 4. Check for AI artifacts: placeholder comments, fake APIs, dead code, inconsistent naming.
-5. Confirm commit messages include Conventional Commit format and `Assisted-by: [AGENT]:[MODEL] [tools]` when AI contributed.
+5. Confirm commit messages include Conventional Commit format. When AI contributed, you MUST append an `Assisted-by` trailer. Do NOT guess or hallucinate the model name from your system prompt. You must run `bash ~/RQZ/personal/nothing/packages/norpiv/scripts/get-pi-model.sh` and use its exact output to construct the trailer: `Assisted-by: <EXACT_OUTPUT> [tools]`.
 6. If passing, mark the slice checkbox complete in `[PLAN]` and append verification evidence to `[LOG]` (Format: `YYYY-MM-DD hh:mm AM/PM`).
-7. Recommend `/sync` for tracker update, or cleanup if the task is fully merged and user approves.
+7. Recommend `/sync` for tracker update, or `/post-merge-prune` if the task is fully merged and user approves.
 
 ## Output contract
 End with:

package/cleanup/SKILL.md

@@ -1,53 +0,0 @@
----
-name: cleanup
-description: "DIRECT EXECUTION: Immediately prunes local branches and task folders. User activation of this skill constitutes explicit permission to execute deletions. Do not ask for confirmation or offer dry runs unless requested. Reconciles stale Git refs and workflow artifacts."
----
-
-# Skill: cleanup (Durable Repo Hygiene)
-
-> [!IMPORTANT]
-> **LLM INSTRUCTION**: This skill is a DIRECT ACTION tool. If the user invokes "cleanup," they have already granted permission for all standard deletions (merged branches, stale refs, verified tasks). DO NOT offer a menu of options. DO NOT ask "Dry run or Execute?". Proceed directly to Step 1.
-
-A durable, idempotent utility to synchronize the local filesystem and Git state with the project's "Definition of Done," regardless of whether the RPIV workflow is used.
-
-## Pre-conditions (Checkpoints)
-- **Current Branch**: Should ideally be `main` or `master`.
-- **Durable State Source**: `git branch` refs and (optionally) `.workflow/tasks/*/WORK.md`.
-
-## Workflow (Durable Steps)
-
-### Step 1: Remote Reconciliation
-- `git remote update origin --prune`
-- Identify branches deleted on remote.
-
-### Step 2: Analysis (General & Workflow)
-Iterate through all local branches and `.workflow/tasks/*` folders:
-- **STALE BRANCHES**: Local branches merged into `main` (safe to delete) or whose remote is gone.
-- **VERIFIED TASKS**: `.workflow/tasks/*` where `WORK.md` state is `MERGED` or `CLOSED`.
-- **ORPHANS**: Local branches with no remote and no task folder, or task folders with no branch.
-
-### Step 3: Atomic Execution
-1. **Branch Pruning**: 
-   - Use `git branch -d` for merged branches.
-   - **Smart Merge Check**: If `-d` fails, check `git log main..[branch]`. If empty, the branch was squash-merged; use `git branch -D` quietly.
-2. **Artifact Cleanup**: If a `.workflow/tasks/` folder exists for a pruned branch, `rm -rf` it.
-3. **Active Task Reset**: Clear `.workflow/active_task.json` if it points to a deleted task.
-
-### Step 4: Durable Verification (Success Metrics)
-- `git branch -a` must not contain deleted refs.
-- `.workflow/tasks/` must not contain folders for deleted tasks.
-
-## Guardrails & Recovery
-- **RESOLUTION OVER REPORTING**: Do not stall the user with "Ambiguous" lists or menus. If a status is unclear, the agent must check merge status (`git branch --merged` or `git log main..branch`) immediately and resolve it.
-- **NO DRY RUNS BY DEFAULT**: Proceed directly to execution unless a dry run is explicitly requested.
-- **MANDATORY SMART DELETE**: If `git branch -d` fails, the agent MUST check if the diff is empty. If empty (squash-merged), use `git branch -D` quietly.
-- **TRUST THE USER**: If the user says "all done" or "clean it all," skip all safety checks and force-delete everything.
-- **Dirty Tree**: If the working tree is dirty, `git stash` before branch switching and `git stash pop` as the final act.
-- **Unmerged Work**: If a branch has no remote and contains unique commits, the agent **MUST** ask ONCE: "Branch [name] contains unmerged commits and has no remote. Force delete? (y/N)".
-
-## Output Contract
-Return a concise "Durable State Report":
-- **Cleaned**: List of (Task ID + Branch Name) successfully removed.
-- **Skipped/Active**: List of tasks kept and why (e.g., "Contains unmerged commits").
-- **Working Branch**: The branch left active (should be `main`).
-- **Next step**: Ready for `/triage`.