@mmerterden/multi-agent-pipeline 14.2.2 → 15.1.0

package/pipeline/skills/shared/README.md

@@ -2,24 +2,24 @@
 
 Single source of truth for skills delivered to both Claude Code (`~/.claude/skills/`) and Copilot CLI (`~/.copilot/skills/`) by the installer.
 
-**Total:** 201 skills (52 core + 149 external). Auto-generated by `scripts/gen-skills-index.mjs`  -  do not edit by hand.
+**Total:** 205 skills (54 core + 151 external). Auto-generated by `scripts/gen-skills-index.mjs`  -  do not edit by hand.
 
 ## Directory layout
 
-- **`core/`**  -  52 `multi-agent*` orchestration skills that are pipeline-critical. Edits here are core-code changes.
-- **`external/`**  -  149 iOS / Android / generic skills imported from the upstream skill library. Mirrors of third-party guidance.
-- Install destination stays flat: both trees flatten into `~/.claude/skills/` and `~/.copilot/skills/`. See ADR-0006 for the rationale.
+- **`core/`**  -  54 `multi-agent*` orchestration skills that are pipeline-critical. Edits here are core-code changes.
+- **`external/`**  -  151 iOS / Android / generic skills imported from the upstream skill library. Mirrors of third-party guidance.
+- Install destinations (ADR-0009): Claude Code gets NO local copy of `external/` - it loads those skills from the `multi-agent-plugins` marketplace, namespaced (`ai-<stack>-toolkit:<name>`); only the two compliance catalogs from `core/` land in `~/.claude/skills/`. Copilot CLI and Codex CLI receive a flat copy filtered to the enabled stacks. `external/` remains the single authoring source that `build-stack-plugins.mjs` publishes from.
 
 Source layout is logical grouping only  -  skill discovery at runtime is unchanged.
 
 ## Categories
 
-- [Pipeline Orchestration](#pipeline-orchestration)  -  52
-- [iOS / Apple Ecosystem](#ios-apple-ecosystem)  -  89
+- [Pipeline Orchestration](#pipeline-orchestration)  -  54
+- [iOS / Apple Ecosystem](#ios-apple-ecosystem)  -  90
 - [Android / Kotlin](#android-kotlin)  -  13
 - [Web / Frontend](#web-frontend)  -  10
 - [Backend / API](#backend-api)  -  11
-- [Cross-cutting](#cross-cutting)  -  26
+- [Cross-cutting](#cross-cutting)  -  27
 
 ## Pipeline Orchestration
 
@@ -29,10 +29,11 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 | [`google-play-compliance`](./core/google-play-compliance/) | `core` | Google Play Store publication compliance  -  bundletool + aapt2 + apksigner orchestration + 21-rule policy catalog with Play Console error c |
 | [`multi-agent`](./core/multi-agent/) | `core` | Task orchestrator: runs the full pipeline from a Jira ID or GitHub Issue URL  -  analysis → plan → TDD development → parallel review (Fable  |
 | [`multi-agent-analysis`](./core/multi-agent-analysis/) | `core` | Standalone feature-spec analysis (v3 template). Platform-agnostic concept layer with repo-driven convention extraction and per-platform Pass |
-| [`multi-agent-analysis-resolve`](./core/multi-agent-analysis-resolve/) | `core` | Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time. Proposes up to 3 source-labeled answer candida |
+| [`multi-agent-analysis-resolve`](./core/multi-agent-analysis-resolve/) | `core` | Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time: up to 3 source-labeled answer candidates per r |
 | [`multi-agent-autopilot`](./core/multi-agent-autopilot/) | `core` | Launch any task in autopilot mode: skips every confirmation, runs end-to-end autonomously. Use when a task should run end to end with no con |
 | [`multi-agent-build-optimize`](./core/multi-agent-build-optimize/) | `core` | Wrapper that dispatches to xcode-build-orchestrator on iOS repos. Benchmarks the current Xcode build, runs compilation / project / SPM analy |
 | [`multi-agent-channels`](./core/multi-agent-channels/) | `core` | Multi-channel reporter  -  Jira/Confluence/Wiki/PR description. Multi-select channels + content, humanizer pass, reviewer-preserving Bitbuck |
+| [`multi-agent-complaint-analysis`](./core/multi-agent-complaint-analysis/) | `core` | Customer-complaint triage. Ingests complaints (paste, csv/xlsx/txt/json file, Jira issue, Confluence URL), fetches Graylog evidence per trx/ |
 | [`multi-agent-create-jira`](./core/multi-agent-create-jira/) | `core` | Create a standards-compliant Jira issue (Task / Bug / Story): asks the type, mines project conventions, drafts from a standard template with |
 | [`multi-agent-design-check`](./core/multi-agent-design-check/) | `core` | Mock-mode vs Figma design audit (iOS / Android, local-only). Pick repo + module, gate on mock support, enumerate every state driver into a c |
 | [`multi-agent-dev`](./core/multi-agent-dev/) | `core` | Fast development mode: Init → Dev (Opus) → Review → Test → Commit → Report. Analysis and planning are skipped, review is not. Use when the w |
@@ -53,9 +54,11 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 | [`multi-agent-log`](./core/multi-agent-log/) | `core` | Show the agent-log.md for the given task. With no ID, shows the most recent task. Use when asked what a task did, or to read its log. |
 | [`multi-agent-manual-test`](./core/multi-agent-manual-test/) | `core` | Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 5 standalone (the UI Bug Hunter lives at multi-agent-te |
 | [`multi-agent-prune-logs`](./core/multi-agent-prune-logs/) | `core` | Delete per-task project logs under ~/.claude/logs/multi-agent (filter by age/project/task). Audit trail + metrics are preserved. Dry-run fir |
+| [`multi-agent-prune-prompts`](./core/multi-agent-prune-prompts/) | `core` | Zero-base prompt review: measure the always-on instruction footprint, classify every rule block, propose keep/trial-removal/delete; applies  |
 | [`multi-agent-purge`](./core/multi-agent-purge/) | `core` | ⚠️ Wipes every worktree, branch, log, and state file. Irreversible; asks for double confirmation. Use when every worktree, branch, log and s |
 | [`multi-agent-refactor`](./core/multi-agent-refactor/) | `core` | Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, research th |
 | [`multi-agent-resume`](./core/multi-agent-resume/) | `core` | Resume a stopped or failed task from the phase where it left off. Use when a task stopped or failed and should carry on from where it left o |
+| [`multi-agent-resume-local`](./core/multi-agent-resume-local/) | `core` | Continue already-done LOCAL work through the pipeline tail: Review → Build+Test → Commit/PR → Report (technical analysis + Jira test-scenari |
 | [`multi-agent-review`](./core/multi-agent-review/) | `core` | Run parallel review on a branch diff or a Pull Request: 2 models on Claude Code (Fable + Sonnet), 3 models on Copilot CLI (GPT + Opus + Sonn |
 | [`multi-agent-review-issue`](./core/multi-agent-review-issue/) | `core` | Assess whether a GitHub issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / sta |
 | [`multi-agent-review-jira`](./core/multi-agent-review-jira/) | `core` | Assess whether a Jira issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / stack |
@@ -64,8 +67,7 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 | [`multi-agent-scan`](./core/multi-agent-scan/) | `core` | Skill security scan: walks local skill directories against a tiered pattern catalog. Use when local skill directories need checking for unsa |
 | [`multi-agent-search`](./core/multi-agent-search/) | `core` | Log search across every agent-log.md with smart ranking and filters. Optional --semantic flag queries the per-repo triage corpus. Use when s |
 | [`multi-agent-setup`](./core/multi-agent-setup/) | `core` | First-run setup wizard: keychain token discovery, Git Identity onboarding, and pipeline preparation. Use when the pipeline is being set up f |
-| [`multi-agent-ship`](./core/multi-agent-ship/) | `core` | Continue already-done LOCAL work through the pipeline tail: Review → Build+Test → Commit/PR → Report (technical analysis + Jira test-scenari |
-| [`multi-agent-stack`](./core/multi-agent-stack/) | `core` | Select the active stack for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json (ios/android/mobile/backend/fr |
+| [`multi-agent-stack`](./core/multi-agent-stack/) | `core` | Select the active stack(s) for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json. Multi-select: pass several |
 | [`multi-agent-status`](./core/multi-agent-status/) | `core` | Show every multi-agent task's ID, phase, branch, and status. Use when asked what is running, or for an overview of every task. |
 | [`multi-agent-store-ready`](./core/multi-agent-store-ready/) | `core` | Pre-submission store readiness for a built package, iOS and Android, local-only. Three symmetric gates per platform: a static package audit, |
 | [`multi-agent-sync`](./core/multi-agent-sync/) | `core` | One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and the dev-toolkit MCP server. Use whe |
@@ -119,6 +121,7 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 | [`ios-debugger-agent`](./external/ios-debugger-agent/) | `external` | Debug the current iOS project on a booted simulator with XcodeBuildMCP. Use when an iOS bug has to be reproduced and diagnosed on a booted s |
 | [`ios-developer`](./external/ios-developer/) | `external` | Develop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimiz |
 | [`ios-localization`](./external/ios-localization/) | `external` | Implement, review, or improve localization and internationalization in iOS/macOS apps  -  String Catalogs (.xcstrings), generated localizabl |
+| [`ios-module-structure`](./external/ios-module-structure/) | `external` | The ios-module-structure rule registry: stable-ID rules over where a declaration lives, what its file is called and what its folder must con |
 | [`ios-networking`](./external/ios-networking/) | `external` | Build, review, or improve networking code in iOS/macOS apps using URLSession with async/await, structured concurrency, and modern Swift patt |
 | [`ios-security`](./external/ios-security/) | `external` | Secure iOS apps with Keychain Services, CryptoKit encryption, biometric authentication (Face ID, Touch ID), Secure Enclave key storage, LACo |
 | [`ios-simulator`](./external/ios-simulator/) | `external` | Manages iOS Simulator devices and tests app behaviour with xcrun simctl: device lifecycle, app install and launch, push notification and loc |
@@ -242,6 +245,7 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 | [`github-actions-templates`](./external/github-actions-templates/) | `external` | Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications. Use when a GitHub Actions workflow has  |
 | [`help-skills`](./external/help-skills/) | `external` | Mevcut tum iOS/Swift skill'lerini listeler ve ne ise yaradiklarini aciklar. Use when asked which iOS or Swift skills are available and what  |
 | [`humanizer`](./external/humanizer/) | `external` | \| |
+| [`localization-reuse-map`](./external/localization-reuse-map/) | `external` | >- |
 | [`pdfkit`](./external/pdfkit/) | `external` | Display and manipulate PDF documents using PDFKit. Use when embedding PDFView to show PDF files, creating or modifying PDFDocument instances |
 | [`search-first`](./external/search-first/) | `external` | \| |
 | [`skill-creator`](./external/skill-creator/) | `external` | Author and refine skills for a plugin/toolkit efficiently. Use when creating a new skill, trimming or splitting an existing one, writing a s |

package/pipeline/skills/shared/core/multi-agent-analysis-resolve/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: multi-agent-analysis-resolve
 language: en
-description: "Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time. Proposes up to 3 source-labeled answer candidates per row (from evidence / from repo / AI reasoned), merges the chosen answer into the target body section, and updates the doc in place with a changelog bump. Companion to multi-agent-analysis. Use when an analysis document's open questions and risks need answering row by row before development starts."
+description: "Resolve the Section 20 Risks and Open Questions of an analysis v3 document one row at a time: up to 3 source-labeled answer candidates per row (evidence / repo / AI reasoned), chosen answer merged into the target section, doc updated in place with a changelog bump. Same locked decisions as /multi-agent:analysis. Use when an analysis document's open questions need answering before development starts."
 user-invocable: true
 argument-hint: "[path/to/analysis/<feature>-<platform>.md] [--autonomous]"
 ---

package/pipeline/skills/shared/core/multi-agent-build-optimize/SKILL.md

@@ -39,7 +39,7 @@ Thin wrapper around the vendored `xcode-build-orchestrator` skill so iOS users d
 ## Detailed implementation
 
 Full steps: `$HOME/.claude/commands/multi-agent/build-optimize/SKILL.md`.
-Upstream attribution: `$HOME/.claude/skills/NOTICE-xcode-build-skills.md`.
+Upstream attribution: ai-ios-toolkit plugin NOTICE (xcode build skills).
 
 ## Notes
 

package/pipeline/skills/shared/core/multi-agent-complaint-analysis/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: multi-agent-complaint-analysis
+language: en
+description: "Customer-complaint triage. Ingests complaints (paste, csv/xlsx/txt/json file, Jira issue, Confluence URL), fetches Graylog evidence per trx/conversation id, correlates read-only against the selected client + BFF repos; per complaint: client/bff root cause + fix plan + dev prompt, or core routing recommendation, or insufficient-evidence. Report only, no dev chaining. Use when customer-reported errors need layer triage."
+user-invocable: true
+argument-hint: "[\"<run-name>\"] [--file <path>] [<jira-id | jira-url | confluence-url> ...]"
+---
+
+# multi-agent-complaint-analysis - Customer Complaint Triage
+
+**Input**: $ARGUMENTS (optional run name, optional `--file <path>`, optional Jira ids / Confluence URLs; remaining free text = pasted complaints)
+
+Triage of customer-reported errors across the layers the team owns. Per complaint: Graylog evidence by trx/conversation id, read-only repo correlation, and a verdict. Core failures get a routing recommendation to the backend core team, never a fix analysis. **Independent and read-only**: no branches, worktrees, commits, PRs, or dev chaining - the run ends at the report.
+
+## When to use
+
+- A batch of customer complaints / store reviews / support tickets needs to be mapped to responsible layers (ios / android / web / mobile-bff / web-bff vs backend core)
+- Production error reports carry trxId / conversationId values worth pulling from Graylog
+- The team needs a forwardable routing record for core-side failures
+
+## Key rules
+
+- Graylog is the primary evidence in this command (deliberate departure from the dev pipeline's advisory-only rule); a failed fetch degrades that complaint to `insufficient-evidence`, never halts the run.
+- Ids are never guessed: complaints without trx/conv ids trigger a supply-or-skip prompt.
+- Complaint text is redacted at intake (email / phone / card / national-id / PNR shapes); raw PII never reaches state or any output.
+- Core is a residual classification, not a repo: no core-repo grepping, no fix speculation.
+- Client/bff verdicts carry a development handoff: a fix plan referencing the existing architecture (`file:line` reuse-first steps) plus a fenced English dev prompt ready for the dev pipeline or a Jira description. The command still never runs dev itself.
+- Output default is Local file; Confluence / Jira are posted only on request. Never closes or transitions issues.
+
+## Flow
+
+| Phase | Action |
+|---|---|
+| 0. Intake | Run name + account picker + repo multi-select + layer-tag confirmation + multi-source complaint ingestion (`lib/parse-complaints.sh`) + id confirmation loop |
+| 1. Graylog | Per-complaint `lib/fetch-graylog.sh --trx/--conv`; credential/host failure degrades and continues |
+| 2. Correlate | Extract signals (endpoints, error codes, exceptions, source services) from Graylog hits; read-only grep across selected repos |
+| 3. Triage | Verdict per complaint: `client:<layer>` / `bff:<layer>` (citations + fix plan grounded in the existing architecture + ready-to-run dev prompt) or `core` (routing recommendation) or `insufficient-evidence` |
+| 4. Draft | Render 8-section report, humanizer pass, punctuation gate |
+| 4.5 Output picker | Local file (default) / Confluence page / Jira comment (asked only after the draft exists) |
+| 5. Dispatch | `validate-complaint-doc.mjs` gate, write/post, verdict-count summary. **Stop.** |
+
+Pickers route through `lib/ask-choice.sh` per the picker contract.
+
+## Detailed implementation
+
+Full steps: the Claude-side command doc for `complaint-analysis` (same phase structure and locked decisions).
+Report template: `complaint-analysis-template.md` (8 sections; routing section required per core verdict).
+State schema: `schemas/complaint-analysis-spec.schema.json`.
+Report gate: `scripts/validate-complaint-doc.mjs` (front-matter, sections, verdict tokens, routing entries, punctuation, redaction-leak scan).

package/pipeline/skills/shared/core/multi-agent-dev/SKILL.md

@@ -70,4 +70,4 @@ Before writing anything outward-facing  -  PR body, Jira comment, Confluence pag
 
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.

package/pipeline/skills/shared/core/multi-agent-dev-autopilot/SKILL.md

@@ -62,4 +62,4 @@ Before writing anything outward-facing  -  PR body, Jira comment, Confluence pag
 
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.

package/pipeline/skills/shared/core/multi-agent-dev-local/SKILL.md

@@ -42,4 +42,4 @@ Before writing anything outward-facing  -  PR body, Jira comment, Confluence pag
 
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.

package/pipeline/skills/shared/core/multi-agent-dev-local-autopilot/SKILL.md

@@ -48,4 +48,4 @@ Before writing anything outward-facing  -  PR body, Jira comment, Confluence pag
 
 ## Intake warnings (`--dev` family)
 
-Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:ship`, not a second Dev pass). Read that section rather than reasoning about it from scratch.
+Two checks belong at the top of every `--dev` run and are specified once in `$HOME/.claude/multi-agent-refs/phases/modes.md` "Intake warnings shared by the whole `--dev` family": an analysis document supplied to a mode that skips Analysis and Planning, and a branch that already carries the work (which wants `/multi-agent:resume-local`, not a second Dev pass). Read that section rather than reasoning about it from scratch.

package/pipeline/skills/shared/core/multi-agent-ios-coding-standard/SKILL.md

@@ -10,9 +10,9 @@ argument-hint: "[module name or path]"
 
 **Input**: $ARGUMENTS  -  optionally a module name or path. When absent, Phase 1 discovers and asks.
 
-This routine is the **procedure**. The rules live in the `ios-coding-standard` skill, whose registry is
+This routine is the **procedure**. The rules live in the `ai-ios-toolkit:ios-coding-standard` skill, whose registry is
 `references/rules.yml` and whose teaching doc is `references/STANDARD.md`. Load that
-skill first; it is installed on every host and carried by the iOS stack plugin, so
+skill first; Claude Code loads it from the iOS stack plugin, Copilot/Codex from their local copy, so
 there is one registry rather than a copy per CLI. Never restate a rule here  -  cite its ID. A rule that is not in the
 registry is not a rule; if the audit needs one, propose it as `status: proposed` and say so.
 

package/pipeline/skills/shared/core/multi-agent-prune-prompts/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: multi-agent-prune-prompts
+language: en
+description: "Zero-base prompt review: measure the always-on instruction footprint, classify every rule block, propose keep/trial-removal/delete; applies only approved rows. Use when a new model ships or instructions have accumulated."
+user-invocable: true
+argument-hint: "[--report-only]"
+---
+
+# multi-agent prune-prompts - Zero-Base Prompt Review
+
+Instruction files only grow. Every rule was added because some model once got
+something wrong, and nobody deletes a rule once a workaround ships. A newer
+model needs fewer of them; the ones it no longer needs are pure context tax on
+every session, and stale rules actively mislead.
+
+The discipline this command applies (after Boris Cherny's advice): on a model
+upgrade, assume ZERO instructions are needed, and let each line earn its way
+back. A line earns its way back only after the model gets the same thing wrong
+repeatedly (three strikes) WITHOUT it. Instructions are a cache of past model
+failures; a new model invalidates that cache.
+
+## Flow
+
+### 1. MEASURE - the always-on footprint
+
+Estimate tokens (chars/4) for each layer the model carries into every session:
+
+```bash
+wc -c "$HOME/.claude/CLAUDE.md" 2>/dev/null
+wc -c "$HOME"/.claude/rules/*.md 2>/dev/null
+find "$PWD" -maxdepth 2 -name "CLAUDE.md" -exec wc -c {} + 2>/dev/null
+```
+
+Report a table: layer, file, estimated tokens, share of total. Flag any single
+file above ~2,000 estimated tokens.
+
+### 2. CLASSIFY - what kind of line is each rule
+
+Walk CLAUDE.md + each rules/ file section by section. Classify every
+instruction block:
+
+| Class | Meaning | Default verdict |
+|---|---|---|
+| **Constraint** | Facts the model cannot infer (hosts, key names, branch formats, team conventions) | keep |
+| **Failure patch** | "Never do X" added after a model did X | trial removal - the current model may not need it |
+| **Restatement** | Something the model does correctly anyway (write tests, guard early) | delete |
+| **Stale** | References files, commands or workflows that no longer exist | delete |
+
+For failure patches, note WHEN the patch was added if git history shows it -
+a patch older than the current model's release is the strongest removal
+candidate.
+
+### 3. REPORT - the zero-base proposal
+
+One table, every block accounted for: file, section, class, verdict
+(keep / trial-removal / delete), and the one-line reason. Never a sample -
+if a section is not in the table, the review did not happen.
+
+With `--report-only`, stop here.
+
+### 4. APPLY - only what the user approves
+
+Present the table, ask which verdicts to apply (all deletes / all
+trial-removals too / pick rows). For approved rows, edit the files. Trial
+removals move the block into `~/.claude/rules/.pruned/<file>.md` with a
+dated header rather than deleting outright, so a strike-out can be reverted
+by moving the block back.
+
+### 5. THE THREE-STRIKE RULE going forward
+
+After a prune, when the model gets something wrong that a removed rule used
+to cover, do NOT restore it on the first miss. Record the miss (the
+`.pruned/` file has a `strikes:` line per block). Restore the line only on
+the third occurrence of the SAME failure. One line back at a time - never
+the whole file.
+
+## Boundaries
+
+- Never touches skill bodies or command files - those load on demand and are
+  not part of the always-on footprint. The lint gate (`lint-skills.mjs`)
+  owns their budgets.
+- Never touches `multi-agent-preferences.json` or anything under `logs/`.
+- Applies nothing without explicit approval on the report table.