@mmerterden/multi-agent-pipeline 19.1.4 → 20.0.0

package/pipeline/commands/multi-agent/analysis-jira/SKILL.md

@@ -8,6 +8,8 @@ not-for: create-jira, jira
 
 # multi-agent analysis-jira
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **Input**: $ARGUMENTS
 
 Reads an analysis document as a work breakdown and creates the tree. It never

package/pipeline/commands/multi-agent/analysis-resolve/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "[path/to/analysis/<feature>-<platform>.md] [--autonomous]"
 
 # multi-agent analysis-resolve - Open Question Resolver for Analysis Docs
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Companion command to `/multi-agent:analysis`. Takes an `analysis/<feature>-<platform>.md` (template v3) and walks the user through the open rows of Section 20 (Riskler ve Acik Sorular / Risks and Open Questions) one row at a time, proposing source-labeled answer candidates and merging the chosen answer into the proper body section. The pattern follows a spec-resolver approach (walk the open rows, propose source-labeled answer candidates, merge the chosen answer) adapted to the analysis doc contract.
 
 **Core invariant - read this twice:** the analysis doc is authoritative and forward-looking. The resolver never invents an answer; if no source produces a credible candidate, the only options offered are Defer and Other. Each Section 20 row is its own decision; never blend candidates across rows.

package/pipeline/commands/multi-agent/autopilot/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: '"task"  -  issue URL, Jira ID, free-text, or #id (for resume)'
 
 # multi-agent autopilot  -  Autonomous Pipeline
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **Input**: $ARGUMENTS
 
 > **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` renders its `question`, option `label`s and option `description`s in `outputLanguage`; only `header` stays English (<=12-char chip); external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".

package/pipeline/commands/multi-agent/autopilot-on/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "(no arguments  -  opens the repo picker)"
 
 # multi-agent autopilot-on  -  continuous mode, on this machine
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Turns on the mode that picks work up without being asked. **No repo is included
 by default and none is ever added implicitly** - you choose, here, every time.
 

package/pipeline/commands/multi-agent/autopilot-status/SKILL.md

@@ -34,7 +34,7 @@ not a fault.
 
 When `swiftc` was available at `autopilot-on` time, `~/.claude/autopilot/bin/menubar`
 shows the same thing in the top right, refreshing on its own: one row per item
-with its id, whether it is running Full or Short, the phase as a fraction, the
+with its id, the phase as a fraction, the
 elapsed time and the stack, then the queue, then what is waiting, then the PRs of
 the last day - each one clickable.
 

package/pipeline/commands/multi-agent/build-optimize/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "(none - operates on current repo)"
 
 # multi-agent build-optimize - Xcode Build Performance Wrapper
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Wraps the vendored `xcode-build-orchestrator` skill (and its 5 specialist analyzers) so iOS users do not have to remember the orchestrator skill name. Recommend-first: no project files are modified without explicit developer approval. All output lands in `.build-benchmark/` in the current repo.
 
 > **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English (this file is read as a system prompt). `AskUserQuestion.question`, `.options[].label` and `.options[].description` follow `outputLanguage`; only `header` stays English (<=12-char chip). The emitted benchmark plan body (the upstream skill controls it) is English by upstream convention.

package/pipeline/commands/multi-agent/channels/SKILL.md

@@ -355,7 +355,7 @@ Applying the Jira table to the PR body is the recurring failure of this step: it
 
 Secondary artifacts ride along as one-line intents at the bottom of the preview: Wiki page list, wiki → Jira triad comment (when Wiki is selected and the triad is active per `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`), Board status move (`{from} → {to}`), GitHub issue comment + Progress-flag sync (Phase 5 Step 1.5  -  same gate, see `$HOME/.claude/multi-agent-refs/phases/phase-5-report.md`).
 
-**Then a single AskUserQuestion** (`question`/`label`/`description` in `outputLanguage`; `header` English):
+**Then a single AskUserQuestion** (`picker-contract.md`; `question`/`label`/`description` in `outputLanguage`, `header` English):
 
 | Option | Behavior |
 |---|---|

package/pipeline/commands/multi-agent/create-jira/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "[\"<free-text description>\"] [figma-url] [swagger-url]  -  all
 
 # multi-agent create-jira  -  Standards-Compliant Jira Issue Creator
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **Input**: $ARGUMENTS
 
 Creates exactly one Jira issue, and only after explicit approval. The issue type (Task / Bug / Story) is asked at the start of every run. No branches, no commits, no worktrees, no pipeline chaining. The draft learns the target project's conventions from its recent same-type issues (summary format, labels, components, priority norms, test-scenario style) and offers active-sprint placement when a sprint is running.

package/pipeline/commands/multi-agent/design-check/SKILL.md

@@ -67,7 +67,7 @@ In Claude Code also drive the native TaskList widget: fire all `TaskCreate` call
 
 ## STOP-AND-CONFIRM format
 
-Every Phase 0 / Phase 2 decision uses a native `AskUserQuestion` picker (numbered text menus are forbidden - `feedback_native_picker_ui`). Print a `Step <i>/<n>: <what it decides>` breadcrumb before each picker. Confirmation is required even with a single option; state inheritance from a previous run is FORBIDDEN.
+Every Phase 0 / Phase 2 decision uses a native `AskUserQuestion` picker per `picker-contract.md` (numbered text menus are forbidden). Print a `Step <i>/<n>: <what it decides>` breadcrumb before each picker. Confirmation is required even with a single option; state inheritance from a previous run is FORBIDDEN.
 
 ---
 

package/pipeline/commands/multi-agent/forget/SKILL.md

@@ -7,6 +7,8 @@ allowed-tools: Bash, Read, AskUserQuestion
 
 # multi-agent forget  -  Remove a Routine
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Delete a routine the user saved via `/multi-agent:save`. Backed by `$HOME/.claude/scripts/routine-registry.mjs`.
 
 ## Steps

package/pipeline/commands/multi-agent/garbage-collect/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "[--older-than=<minutes>] [--abandoned [--days=N]] [--yes]  -  dr
 
 # multi-agent garbage-collect  -  Sweep /tmp Scratch
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Each run writes ephemeral scratch under `/tmp`: picker state
 (`multi-agent-picker-*`), PR/review diffs (`multi-agent-review-*`), issue
 progress bodies (`issue-progress-*`), channel payloads (`channels-*`),
@@ -62,7 +64,7 @@ deletes nothing until you confirm.
    residue in the index (`.worktrees/{id}` recorded as a "Subproject commit"
    entry by a pre-guard `git add -A`), and a missing `.worktrees/` line in
    `.git/info/exclude`. Registered, healthy worktrees are NEVER touched  -
-   those belong to `/multi-agent:resume-local` / `/multi-agent:kill`.
+   those belong to `/multi-agent:resume` / `/multi-agent:kill`.
 
    - Output says `nothing to do` -> skip silently, no question.
    - Otherwise surface a second `AskUserQuestion` (in `outputLanguage`):
@@ -81,7 +83,7 @@ deletes nothing until you confirm.
 
    `offload-ref.sh` parks build logs, diffs and test output under
    `.multi-agent/refs/<node_id>.md`. In worktree modes that directory dies with
-   the worktree; in the `--local` modes it lands in the real checkout, and
+   the worktree; when the run chose a local workspace it lands in the real checkout, and
    because it is gitignored it never shows up in `git status`. Only files
    matching the node-id shape are touched  -  anything else in that directory is
    left alone, and files inside the grace window are spared so a sweep cannot

package/pipeline/commands/multi-agent/help/SKILL.md

@@ -46,7 +46,7 @@ How It Works (Phase 0  -  Interactive Flow):
   5. BRANCH NAME bugfix/{jiraId} or feature/{jiraId} -> confirm
   6. GIT ID      Select identity from preferences (multiple supported)
   7. INSTRUCTION Auto-detect if .instructions/ exists (figma etc.)
-  8. WORKSPACE   Create worktree (default) or local branch (--local)
+  8. WORKSPACE   Ask where the branch lives: worktree (default) or project root
 
 ------------------------------
 
@@ -55,7 +55,7 @@ Pipeline (after Phase 0)  -  shown as visual cards in terminal:
   Phase 0:   Init       -> The 8 steps above
   Phase 1:   Plan       -> Stack detection + codebase scan, task breakdown, architecture
                           review, Plan Approval Gate (Opus; max 2 clarification rounds,
-                          Full + interactive only  -  a Short run has no plan)
+                          interactive only  -  autopilot has nobody to ask)
   Phase 2:   Dev        -> TDD: test -> code -> build (Sonnet) + build queue, then the
                           Verify exit gate: build, lint, tests, secrets. The build runs
                           ONCE per run and its log carries into Review
@@ -68,11 +68,10 @@ Pipeline (after Phase 0)  -  shown as visual cards in terminal:
 
   Autopilot always pauses at the Phase 5 channels menu (30-min timeout → session ends cleanly).
 
-  Pipeline depth is asked at Phase 0 Step 7.5, not passed as a flag:
-    Full    Plan -> Dev(Sonnet) -> Review -> Commit -> Report
-    Short   Dev(Opus, self-contained) -> Review -> Commit -> Report
-  Short skips Phase 1 only; Review is NEVER skipped. Recommended from taskType:
-  bugfix/chore -> Short, feature/refactor/component -> Full. Autopilot always runs Full.
+  One pipeline. Every mode runs its whole phase set:
+    Plan -> Dev(Sonnet) -> Review -> Commit -> Report
+  What a run costs follows the evidence the task carries, not an answer taken
+  before the evidence exists.
 
   Every step is logged. Error in any phase -> pause -> resume to continue.
 
@@ -82,17 +81,15 @@ Modes:
 
 Four pipeline entries:
 
-  /multi-agent "task"                  Worktree, asks Full or Short
-  /multi-agent:local "task"            No worktree, asks Full or Short
+  /multi-agent "task"                  Worktree
   /multi-agent:autopilot "task"        Worktree, no questions, always Full
-  /multi-agent:local-autopilot "task"  No worktree, no questions, always Full
 
-  --local on the base command is the same as the :local entry.
-  autopilot skips every confirmation INCLUDING the plan gate and the depth
+  Phase 0 Step 5b asks where the branch lives; there is no flag for it.
+  autopilot skips every confirmation INCLUDING the plan gate and the workspace
   question, and auto commit/PR  -  EXCEPT the Phase 5 channels menu, which
   always pauses.
 
-  /multi-agent:resume-local [jira-id] [autopilot]     Continue already-done LOCAL work: Review (build gate) → Commit/PR → Report (no dev)
+  /multi-agent:resume [#id|jira-id] [autopilot]       Pick up unfinished work: a stopped run, or a branch with no run behind it (Review → Commit/PR → Report)
 
 ------------------------------
 
@@ -135,7 +132,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:store-ready [repo] [flags]  Pre-submission store readiness, iOS + Android, local-only: three symmetric gates per platform plus the running-app sweep. A skipped gate is never a pass. Validates only, never uploads.
   /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  iOS-pinned alias of :store-ready. Same three gates, one implementation.
   /multi-agent:ios-coding-standard [module]  Audit an iOS module against the 99-rule coding-standard registry -> remediation
-                              plan + one-page onboarding summary -> hand off to /multi-agent or :local. Read-only, never edits source.
+                              plan + one-page onboarding summary -> hand off to /multi-agent. Read-only, never edits source.
 
 Setup & Maintenance:
 
@@ -182,9 +179,8 @@ Interactive Launchers:
 
   Both follow the same flow after selection:
     1. Branch selection (develop/release/main)
-    2. Depth: Full or Short
-    3. Autopilot: yes/no
-    4. Pipeline starts with the selected issue
+    2. Autopilot: yes/no
+    3. Pipeline starts with the selected issue
 
 ------------------------------
 
@@ -274,7 +270,6 @@ Examples:
   /multi-agent "MOBILE-12345"
 
   # GitHub issue, fast mode, local
-  /multi-agent:local "#42"                                       # then choose Short
 
   # Interactive launchers  -  browse and pick
   /multi-agent:jira                    # Pick from my Jira issues
@@ -284,7 +279,7 @@ Examples:
   /multi-agent:autopilot "LoginView dark mode fix"               # iOS
   /multi-agent "Add pagination to /api/users endpoint"           # Backend
   /multi-agent "Fix bottom nav recomposition in HomeScreen"      # Android
-  /multi-agent "Responsive layout broken on tablet"              # Web, choose Short
+  /multi-agent "Responsive layout broken on tablet"              # Web
 
   # Review current diff only
   /multi-agent:review
@@ -326,7 +321,7 @@ Nasıl Çalışır (Phase 0  -  İnteraktif Akış):
   5. BRANCH NAME bugfix/{jiraId} veya feature/{jiraId} -> onayla
   6. GIT ID      Kimlik seç (prefs'ten; birden fazla desteklenir)
   7. INSTRUCTION .instructions/ varsa otomatik algıla (figma vs.)
-  8. WORKSPACE   Worktree yarat (default) ya da local branch (--local)
+  8. WORKSPACE   Branch nerede yaşayacak: worktree (default) ya da proje kökü
 
 ------------------------------
 
@@ -362,16 +357,14 @@ Modlar:
 
 Dört pipeline girişi:
 
-  /multi-agent "task"                  Worktree var, Tam mı Kısa mı diye sorar
-  /multi-agent:local "task"            Worktree yok, Tam mı Kısa mı diye sorar
+  /multi-agent "task"                  Worktree var
   /multi-agent:autopilot "task"        Worktree var, soru yok, her zaman Tam
-  /multi-agent:local-autopilot "task"  Worktree yok, soru yok, her zaman Tam
 
-  Ana komuta --local eklemek :local girişiyle aynıdır.
+  Faz 0 Adım 5b branch'in nerede yaşayacağını sorar; bayrağı yok.
   autopilot plan kapısı ve derinlik sorusu dahil her onayı atlar, otomatik
   commit/PR açar  -  İSTİSNA: Faz 5 channels menüsü, o her zaman durur.
 
-  /multi-agent:resume-local [jira-id] [autopilot]     Lokalde biten işi sürdür: Review (build kapısı) → Commit/PR → Report (dev yok)
+  /multi-agent:resume [#id|jira-id] [autopilot]       Yarım kalan işi sürdür: duran koşu ya da arkasında koşu olmayan branch (Review → Commit/PR → Report)
 
 ------------------------------
 
@@ -400,6 +393,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:analysis ["analysis-name"]  Feature-spec analizi (Figma + Swagger + Confluence + repolar). Önce standardı sorar: global (23 bölümlük geliştirme dokümanı) veya kurumsal (IG→UC→FG gereksinim dokümanı). Stack opsiyonel; Referanslar kanıt kaydından üretilir
   /multi-agent:analysis-resolve [doc]      Analiz dokümanının Bölüm 20 açık sorularını kaynak etiketli adaylarla teker teker çözer
   /multi-agent:review-analysis [doc]  Yazılmış analizi review eder; bulgular ihlal edilen kuralı gösterir
+  /multi-agent:analysis-jira [doc]    Nihai analiz -> Jira story ağacı; kapsam iki yönlü kontrol edilir, var olan düğümler atlanır
   /multi-agent:complaint-analysis ["run-adı"]  Müşteri şikayeti triyajı: trx/conv id ile Graylog kanıtı + salt-okunur repo eşleştirme → client/bff kök neden + fix planı + dev prompt'u, veya core'a yönlendirme önerisi
   /multi-agent:build-optimize iOS-only Xcode build performance wrapper → benchmark + analiz + recommend-first .build-benchmark/optimization-plan.md
   /multi-agent:create-jira ["açıklama"] [figma-url] [swagger-url]  Takım standartlarına uygun Jira Task/Bug/Story oluştur (tip sorar + convention mining + aktif sprint + auto-sizing bölümler + önizleme & onay)
@@ -407,12 +401,13 @@ Post-Hoc & Side-Channel:
   /multi-agent:graph         Repo kod grafiğini kur ve sorgula (semboller, import'lar, referanslar), LLM'siz
   /multi-agent:search         Task log'larında akıllı arama; --semantic triage corpus'unu sorgular
   /multi-agent:scan           Skill güvenlik taraması (tiered pattern catalog)
+  /multi-agent:doctor         Burada bir koşu çalışır mı? Yerleşim, prefs, kimlik bilgileri, hook'lar; çıkış kodu kararı verir
   /multi-agent:refactor       Uyarlanmış best-practice + bug avı + upstream-drift + multi-agent-toolkit MCP araştırması -> tek plan, onay, dev + sync
   /multi-agent:refactor backlog  Pipeline'ın kendisi hakkında kaydedilmiş sürtünmeyi karara bağlar, sıfırdan türetmez
   /multi-agent:store-ready [repo] [flags]  Yükleme öncesi store hazırlığı, iOS + Android, yalnızca lokal: platform başına 3 simetrik kapı artı çalışan-app sweep'i. Atlanan kapı asla pass sayılmaz. Sadece doğrular, asla yüklemez.
   /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  :store-ready'nin iOS alias'ı. Aynı 3 kapı, tek implementasyon.
   /multi-agent:ios-coding-standard [modül]  Bir iOS modülünü 99 kurallık kodlama-standardı registry'sine göre denetler -> düzeltme
-                              planı + tek sayfalık onboarding özeti -> /multi-agent veya :local'e devreder. Read-only, kaynağı hiç düzenlemez.
+                              planı + tek sayfalık onboarding özeti -> /multi-agent'a devreder. Read-only, kaynağı hiç düzenlemez.
 
 Setup & Maintenance:
 
@@ -550,7 +545,6 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   /multi-agent "MOBILE-12345"
 
   # GitHub issue, hızlı mode, local
-  /multi-agent:local "#42"                                       # sonra Kısa seç
 
   # İnteraktif launcher'lar  -  göz at ve seç
   /multi-agent:jira                    # Jira issue'larımdan seç

package/pipeline/commands/multi-agent/ios-coding-standard/SKILL.md

@@ -1,12 +1,14 @@
 ---
-description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent or :local. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
-description-tr: "Bir iOS modulunu paylasilan kodlama-standardi registry'sine (99 sabit-ID kural) gore denetler, duzeltme plani cikarir, sonra /multi-agent veya :local'e devreder. Bir modulde standart gecisi icin, ya da bir review'un gorus yerine kural ID'si istedigi durumda kullan."
+description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
+description-tr: "Bir iOS modulunu paylasilan kodlama-standardi registry'sine (99 sabit-ID kural) gore denetler, duzeltme plani cikarir, sonra /multi-agent'e devreder. Bir modulde standart gecisi icin, ya da bir review'un gorus yerine kural ID'si istedigi durumda kullan."
 argument-hint: "[module name or path]"
 allowed-tools: Skill, Bash, Read, Edit, Write, AskUserQuestion
 ---
 
 # multi-agent ios-coding-standard  -  Module audit → plan → dev handoff
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **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 `ai-ios-toolkit:ios-coding-standard` skill, whose registry is
@@ -236,10 +238,9 @@ Show a concise version of the plan to the user too.
 
 | Option | What it does |
 |---|---|
-| `/multi-agent:local` | No worktree; branches from the main development branch, fixes on the current checkout |
 | `/multi-agent` | Opens a worktree; fixes on a fresh branch + PR |
 
-Both ask Full or Short at Phase 0 Step 7.5; a standards sweep is usually already scoped, so Short is the common answer.
+Both run the whole pipeline; a standards sweep is usually already scoped, so Phase 1 has little to say and its document is short.
 
 Invoke the chosen command with the plan file as the task input, branching off the repo's main
 development branch (e.g. `chore/<module>-coding-standard`). The dev pipeline applies the fixes,

package/pipeline/commands/multi-agent/issue/SKILL.md

@@ -7,6 +7,8 @@ not-for: jira
 
 # multi-agent issue  -  4-Step Picker (Account → Repos → Issue → Dev Context)
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **Input**: $ARGUMENTS
 
 Fully interactive. Only one optional flag: `autopilot`.

package/pipeline/commands/multi-agent/jira/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "[autopilot]  -  optional: run the pipeline without confirmations
 
 # multi-agent jira  -  4-Step Picker (Account → Project → Issue → Dev Context)
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **Input**: $ARGUMENTS
 
 Fully interactive. Only one optional flag: `autopilot`.

package/pipeline/commands/multi-agent/language/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "[en|tr]  -  sets outputLanguage; omit for interactive picker; us
 
 # multi-agent language  -  Language Preference Toggle
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 **Input**: $ARGUMENTS
 
 Two-axis language preference for the pipeline:

package/pipeline/commands/multi-agent/prune-logs/SKILL.md

@@ -6,6 +6,8 @@ argument-hint: "[--older-than=<days>] [--project=<name>] [--task=<id>] [--yes]"
 
 # multi-agent prune-logs  -  Clear Per-Task Project Logs
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Every run persists a task log dir at
 `~/.claude/logs/multi-agent/<project>/<task>/` (agent-state.json, agent-log.md,
 tracker-state.json, otel-spans.jsonl). These accumulate forever. This prunes

package/pipeline/commands/multi-agent/purge/SKILL.md

@@ -6,6 +6,8 @@ description-tr: "⚠️ Tüm worktree, branch, log ve state dosyalarını siler.
 
 # multi-agent purge  -  Full Reset
 
+> **Pickers follow** `$HOME/.claude/multi-agent-refs/picker-contract.md`: never a one-option call, and branch on the option selected, not on its text.
+
 Reset every multi-agent worktree, its local branch, and the project task
 counter. Nuclear option  -  requires double confirmation. Backed by
 `$HOME/.claude/scripts/purge.sh`, which is safe by default (dry-run, deletes