@mmerterden/multi-agent-pipeline 16.31.1 → 17.1.0

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

@@ -9,7 +9,7 @@ Called with no args or `help`, show the usage guide in the user's preferred lang
 
 ## Language resolution
 
-Help is the assistant's own explanation to the user  -  render it in `prefs.global.outputLanguage`, falling back to `prefs.global.promptLanguage` on prefs files written before it existed. Two valid values: `"en"` (default) and `"tr"`; missing or malformed → `"en"`.
+Help is the assistant's own explanation to the user - render it in `prefs.global.outputLanguage` (falling back to `promptLanguage`). Language rule: `rules.md`.
 
 ```bash
 PREFS="$HOME/.claude/multi-agent-preferences.json"
@@ -23,9 +23,9 @@ Render **exactly one** of the two blocks below  -  the one matching `LANG`. Neve
 ## Render when `LANG == "en"`  -  English guide
 
 ```
-+----------------------------------------------------------+
++----------------------------------+
 |             Multi-Agent Task Orchestrator                |
-+----------------------------------------------------------+
++----------------------------------+
 
 5 different input types supported  -  all enter the same flow:
 
@@ -35,7 +35,7 @@ Render **exactly one** of the two blocks below  -  the one matching `LANG`. Neve
   /multi-agent "#316"                              -> GitHub Issue #
   /multi-agent "bug/feature description"           -> Free-text
 
-------------------------------------------------------------
+------------------------------
 
 How It Works (Phase 0  -  Interactive Flow):
 
@@ -48,7 +48,7 @@ How It Works (Phase 0  -  Interactive Flow):
   7. INSTRUCTION Auto-detect if .instructions/ exists (figma etc.)
   8. WORKSPACE   Create worktree (default) or local branch (--local)
 
-------------------------------------------------------------
+------------------------------
 
 Pipeline (after Phase 0)  -  shown as visual cards in terminal:
 
@@ -77,7 +77,7 @@ Pipeline (after Phase 0)  -  shown as visual cards in terminal:
 
   Every step is logged. Error in any phase -> pause -> resume to continue.
 
-------------------------------------------------------------
+------------------------------
 
 Modes:
 
@@ -95,7 +95,7 @@ Four pipeline entries:
 
   /multi-agent:resume-local [jira-id] [autopilot]     Continue already-done LOCAL work: Review → Build+Test → PR → Jira analysis + test scenarios (no dev)
 
-------------------------------------------------------------
+------------------------------
 
 Status & Resume:
 
@@ -106,8 +106,11 @@ Status & Resume:
   /multi-agent:steer #id "..."  Correct a running task without stopping it (applied at the next phase)
   /multi-agent:prune-logs     Delete per-task project logs (audit + metrics kept; age/project/task filters, dry-run first)
   /multi-agent:prune-prompts  Zero-base prompt review: measure always-on instruction footprint, propose keep/trial/delete per rule (report first, apply on approval)
-  /multi-agent:garbage-collect  Sweep leftover /tmp scratch from past runs (dry-run first)
+  /multi-agent:garbage-collect  Sweep run residue; --abandoned reaps stopped runs
   /multi-agent:purge          Worktree + logs  -  full reset (double confirm)
+  /multi-agent:autopilot-on   Continuous mode on this machine: pick repos, labelled items run to a PR
+  /multi-agent:autopilot-status  Running, queued, awaiting an answer, today's PRs
+  /multi-agent:autopilot-off  Stop picking work up (running work finishes; --now stops it)
 
 Post-Hoc & Side-Channel:
 
@@ -116,11 +119,11 @@ Post-Hoc & Side-Channel:
   /multi-agent:review         Parallel review of a PR or branch diff; no URL -> pick open GitHub/Bitbucket PRs
   /multi-agent:review-jira    Grade a Jira issue's pipeline-readiness -> comment the gaps on it
   /multi-agent:review-issue   Grade a GitHub issue's pipeline-readiness -> comment the gaps on it
-  /multi-agent:analysis ["analysis-name"]  Feature-spec analysis (Figma + Swagger + Confluence + repos). Asks the standard first: global (23-section dev handoff) or corporate (IG→UC→FG requirements doc). Stack optional; References built from the evidence record
+  /multi-agent:analysis ["name"]  Feature-spec analysis (Figma + Swagger + Confluence + repos). Asks the standard first: global (23-section dev handoff) or corporate (IG→UC→FG requirements doc). Stack optional; References built from the evidence record
   /multi-agent:analysis-resolve [doc]      Resolve Section 20 open questions of an analysis doc, one at a time with source-labeled candidates
   /multi-agent:review-analysis [doc]  Review a written analysis; findings cite the rule they break
   /multi-agent:analysis-jira [doc]    A final analysis -> a Jira story tree; coverage two-way, existing nodes skipped
-  /multi-agent:complaint-analysis ["run-name"] [--file path]  Customer-complaint triage: Graylog evidence per trx/conv id + read-only repo correlation → client/bff root cause + fix plan + dev prompt, or core routing recommendation
+  /multi-agent:complaint-analysis ["run-name"]  Customer-complaint triage: Graylog evidence per trx/conv id + read-only repo correlation → client/bff root cause + fix plan + dev prompt, or core routing recommendation
   /multi-agent:build-optimize iOS-only Xcode build perf wrapper → benchmark + analyze + recommend-first .build-benchmark/optimization-plan.md
   /multi-agent:create-jira ["desc"] [figma-url] [swagger-url]  Create a Jira Task/Bug/Story matching team conventions (asks type + mining + active sprint + auto-sizing sections + preview & approval)
   /multi-agent:diff-explain   Map a Phase 4 triage finding back to specific diff lines
@@ -130,7 +133,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:doctor         Would a run work here? Layout, prefs, credentials, hooks; exit code is the verdict
   /multi-agent:refactor       Best practices + bug hunt + upstream drift + toolkit MCP research -> one plan, approval, dev + sync
   /multi-agent:refactor backlog  Decide the friction already recorded about the pipeline itself, nothing re-derived
-  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep]  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: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.
@@ -144,7 +147,7 @@ Setup & Maintenance:
   /multi-agent:update         Pull latest pipeline + reinstall + run migrations
   /multi-agent:uninstall      Uninstall pipeline from every CLI (--all-data also clears settings, logs, memory + knowledge; tokens always intact)
 
-------------------------------------------------------------
+------------------------------
 
 Plugins & tools (called directly, no wrappers):
 
@@ -158,7 +161,7 @@ Plugins & tools (called directly, no wrappers):
                    *_accessibility_audit). Use them instead of guessing about on-screen
                    state. Its registration survives uninstall. Not registered = silent no-op.
 
-------------------------------------------------------------
+------------------------------
 
 Routines (your own reusable jobs):
 
@@ -167,7 +170,7 @@ Routines (your own reusable jobs):
   /multi-agent:forget [name]  Remove a saved routine
 <!-- ROUTINES_DYNAMIC: after printing the static lines above, read prefs.global.routines; if non-empty, append one indented line per routine "  /multi-agent:<name>   <description>" under a "Your saved routines:" subheading, in outputLanguage. If empty, print "  (none yet - use /multi-agent:save)". -->
 
-------------------------------------------------------------
+------------------------------
 
 Interactive Launchers:
 
@@ -180,7 +183,7 @@ Interactive Launchers:
     3. Autopilot: yes/no
     4. Pipeline starts with the selected issue
 
-------------------------------------------------------------
+------------------------------
 
 UI Testing (standalone  -  not part of pipeline phases):
 
@@ -222,7 +225,7 @@ Design Check (mock-mode vs Figma, local-only):
   # COVERAGE GATE: every target is audited or skipped WITH a concrete reason; anything else reports
   # INCOMPLETE with the missing ids. "Needs a scenario/launch-arg" is not a reason, reaching it is the job.
 
-------------------------------------------------------------
+------------------------------
 
 Setup:
 
@@ -236,7 +239,7 @@ Setup:
   5. Missing Tokens  -  standard key names + ready-to-paste commands
   6. Verify  -  re-scan, confirm ready
 
-------------------------------------------------------------
+------------------------------
 
 Key Features:
 
@@ -263,7 +266,7 @@ Quality & Telemetry (advisory, on by default  -  flip prefs.global.* to disable)
   Per-Persona      Dispatch reads `preferredModel` from the persona file; override per call via
                    PHASE_MODEL_OVERRIDE; ladder fable -> opus -> sonnet -> haiku
 
-------------------------------------------------------------
+------------------------------
 
 Examples:
 
@@ -290,7 +293,7 @@ Examples:
   /multi-agent:create-jira "Profile screen empty state" https://figma.com/design/abc?node-id=1-2
   /multi-agent:create-jira "Login crash on iOS 17, see attached log"
 
-------------------------------------------------------------
+------------------------------
 
 Logs: $HOME/.claude/logs/multi-agent/{project}/{task-id}/
 ```
@@ -300,9 +303,9 @@ Logs: $HOME/.claude/logs/multi-agent/{project}/{task-id}/
 ## Render when `LANG == "tr"`  -  Türkçe rehber
 
 ```
-+----------------------------------------------------------+
++----------------------------------+
 |             Multi-Agent Görev Orkestratörü               |
-+----------------------------------------------------------+
++----------------------------------+
 
 5 farklı girdi tipi desteklenir  -  hepsi aynı akışa girer:
 
@@ -312,7 +315,7 @@ Logs: $HOME/.claude/logs/multi-agent/{project}/{task-id}/
   /multi-agent "#316"                              -> GitHub Issue #
   /multi-agent "bug/özellik açıklaması"            -> Serbest metin
 
-------------------------------------------------------------
+------------------------------
 
 Nasıl Çalışır (Phase 0  -  İnteraktif Akış):
 
@@ -325,7 +328,7 @@ Nasıl Çalışır (Phase 0  -  İnteraktif Akış):
   7. INSTRUCTION .instructions/ varsa otomatik algıla (figma vs.)
   8. WORKSPACE   Worktree yarat (default) ya da local branch (--local)
 
-------------------------------------------------------------
+------------------------------
 
 Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
 
@@ -354,7 +357,7 @@ Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
 
   Her adım loglanır. Herhangi bir fazdaki hata -> pause -> resume ile devam et.
 
-------------------------------------------------------------
+------------------------------
 
 Modlar:
 
@@ -371,7 +374,7 @@ Dört pipeline girişi:
 
   /multi-agent:resume-local [jira-id] [autopilot]     Lokalde biten işi sürdür: Review → Build+Test → PR → Jira teknik analiz + test senaryoları (dev yok)
 
-------------------------------------------------------------
+------------------------------
 
 Status & Resume:
 
@@ -382,8 +385,11 @@ Status & Resume:
   /multi-agent:steer #id "..."  Koşan task'ı durdurmadan düzelt (sonraki fazda uygulanır)
   /multi-agent:prune-logs     Task bazlı proje log'larını sil (audit + metrics korunur; yaş/proje/task filtresi, önce dry-run)
   /multi-agent:prune-prompts  Sıfır-tabanlı prompt incelemesi: sürekli yüklü talimat yükünü ölç, kural başına tut/dene/sil öner (önce rapor, onayla uygula)
-  /multi-agent:garbage-collect  Geçmiş koşumların /tmp artıklarını süpür (önce dry-run)
+  /multi-agent:garbage-collect  Koşu artığını süpür; --abandoned durmuş koşuları toplar
   /multi-agent:purge          Worktree + log'lar  -  tam reset (çift onay)
+  /multi-agent:autopilot-on   Bu makinede sürekli mod: repo seç, etiketli maddeler PR'a kadar koşar
+  /multi-agent:autopilot-status  Koşan, sıradaki, cevap bekleyen, bugünkü PR'lar
+  /multi-agent:autopilot-off  Yeni madde alma (koşan iş biter; --now onu da durdurur)
 
 Post-Hoc & Side-Channel:
 
@@ -395,7 +401,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:complaint-analysis ["run-adı"] [--file yol]  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: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)
   /multi-agent:diff-explain   Phase 4 triage bulgusunu diff satırlarına eşle
@@ -404,7 +410,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:scan           Skill güvenlik taraması (tiered pattern catalog)
   /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] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep]  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: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.
@@ -418,7 +424,7 @@ Setup & Maintenance:
   /multi-agent:update             En son pipeline'ı çek + reinstall + migration çalıştır
   /multi-agent:uninstall          Pipeline'ı tüm CLI'lerden kaldır (--all-data ayar, log, hafıza + bilgi tabanını da siler; token'a dokunulmaz)
 
-------------------------------------------------------------
+------------------------------
 
 Plugin'ler ve tool'lar (doğrudan çağrılır, sarmalayıcı yok):
 
@@ -432,16 +438,16 @@ Plugin'ler ve tool'lar (doğrudan çağrılır, sarmalayıcı yok):
                    android_apk_audit, *_accessibility_audit). Ekrandaki durumu tahmin etmek
                    yerine bunları kullan. Kaydı uninstall'dan sağ çıkar. Kayıtlı değilse sessizce devre dışı.
 
-------------------------------------------------------------
+------------------------------
 
 Rutinler (kendi tekrar eden işlerin):
 
   /multi-agent:save [ad]          Sık yaptığın bir işi yeniden kullanılabilir /multi-agent:<ad> komutu olarak kaydet
   /multi-agent:routines           Kayıtlı rutinlerini ve ne yaptıklarını listele
   /multi-agent:forget [ad]        Kayıtlı bir rutini kaldır
-<!-- ROUTINES_DYNAMIC: yukarıdaki statik satırlardan sonra prefs.global.routines'i oku; boş değilse her rutin için "  /multi-agent:<ad>   <açıklama>" satırını "Kayıtlı rutinlerin:" alt başlığı altında ekle (outputLanguage). Boşsa "  (henüz yok - /multi-agent:save kullan)" yaz. -->
+<!-- ROUTINES_DYNAMIC: same rule as the EN block above. -->
 
-------------------------------------------------------------
+------------------------------
 
 İnteraktif Launcher'lar:
 
@@ -454,7 +460,7 @@ Rutinler (kendi tekrar eden işlerin):
     3. Autopilot: evet/hayır
     4. Pipeline seçilen issue ile başlar
 
-------------------------------------------------------------
+------------------------------
 
 UI Testing (standalone  -  pipeline fazlarından bağımsız):
 
@@ -496,7 +502,7 @@ Design Check (mock-mod vs Figma, yalnızca lokal):
   # KAPSAM GEÇİDİ: her hedef ya denetlenir ya da SOMUT gerekçeyle atlanır; başka her durum eksik hedef
   # id'leriyle EKSİK raporlanır. "Senaryo/launch-arg gerektirir" gerekçe değil, oraya ulaşmak koşunun işi.
 
-------------------------------------------------------------
+------------------------------
 
 Setup:
 
@@ -510,7 +516,7 @@ Setup:
   5. Eksik Token'lar  -  standart key isimleri + ready-to-paste komutlar
   6. Doğrulama  -  yeniden tarama, hazır mı kontrol
 
-------------------------------------------------------------
+------------------------------
 
 Temel Özellikler:
 
@@ -536,7 +542,7 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   Per-Persona      Reviewer/agent dispatch persona dosyasından `preferredModel` okur;
                    per-call override PHASE_MODEL_OVERRIDE ile; merdiven fable -> opus -> sonnet -> haiku
 
-------------------------------------------------------------
+------------------------------
 
 Örnekler:
 
@@ -563,7 +569,7 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   /multi-agent:create-jira "Profil ekranı empty state" https://figma.com/design/abc?node-id=1-2
   /multi-agent:create-jira "iOS 17'de login crash, log ekte"
 
-------------------------------------------------------------
+------------------------------
 
 Log'lar: $HOME/.claude/logs/multi-agent/{project}/{task-id}/
 ```

package/pipeline/commands/multi-agent/manual-test/SKILL.md

@@ -51,5 +51,5 @@ Lets you switch to the task branch for manual testing in Xcode before the PR is
      ```json
      {"criteria":[{"spec":"<quote>","source":"analysis 15.2 | plan task 3 | user","observed":"<what was seen>","verdict":"pass|fail|not-tested","reason":"<required when not-tested>","screenshot":"<path or null>"}],"verdict":"passed|failed"}
      ```
-     then run `node $HOME/.claude/scripts/evidence-gate.mjs --claim manual --status passed --evidence "$WORKTREE/.pipeline/manual-test.json"`, adding `--require-screenshot` when `state.visualEvidence.required` is true (a passing criterion then has to name a screenshot that is actually on disk). Exit 1 means the "ok" is not accepted: name the criterion that is missing evidence and wait for the next reply. Exit 0 → `phase-tracker.sh update 5 completed` + `phase-tracker.sh meta 5 Result "local test passed (user)"`, recreate the worktree, continue to Phase 6. Full contract: `$HOME/.claude/multi-agent-refs/phases/phase-5-test.md` step 5.
+     then run `node $HOME/.claude/scripts/evidence-gate.mjs --claim manual --status passed --evidence "$WORKTREE/.pipeline/manual-test.json"`, adding `--require-screenshot` when `state.visualEvidence.required` is true (a passing criterion then has to name a screenshot that is actually on disk). Exit 1 means the "ok" is not accepted: name the criterion that is missing evidence and wait for the next reply. Exit 0 → `phase-tracker.sh update 5 completed` + `phase-tracker.sh meta 5 Result "local test passed (user)"`, recreate the worktree, continue to Phase 6. Full contract: `$HOME/.claude/multi-agent-refs/phases/phase-5-test.md` step 5, whose "UI flow video, when Phase 3 produced none" block applies here too: invoked standalone, this command is the only phase that ran, so if `visualEvidence.required` is set and `visualEvidence.video.file` is empty, the recording has to happen here or nowhere.
    - **Fix needed** → `phase-tracker.sh now 5 "applying fix: <summary>"`, recreate the worktree, apply the fix

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

@@ -817,13 +817,21 @@ Stack skills ship as versioned plugins in the `{owner}/multi-agent-plugins` mark
    ```bash
    claude marketplace add {owner}/multi-agent-plugins 2>/dev/null || true
    ```
-2. Detect the project stack from markers and enable the matching plugin(s) plus the two always-on plugins in the project's `.claude/settings.json` `enabledPlugins`:
-   - `.xcodeproj` / `Package.swift` / `*.xcworkspace` → `ai-ios-toolkit`
-   - `build.gradle` / `settings.gradle` → `ai-android-toolkit`
-   - `package.json` with `react`/`next` → `ai-frontend-toolkit`
-   - `requirements.txt` / `pyproject.toml` / server `package.json` → `ai-backend-toolkit`
-   - **no clear marker → default `ai-ios-toolkit`**
-   `ai-common-toolkit@multi-agent-plugins` and `ai-analyst-toolkit@multi-agent-plugins` are always set `true` alongside the stack plugin: neither is stack-specific.
+2. Ask the detector, then derive. No marker list here: a second list is a second
+   answer, and this one defaulted to `ai-ios-toolkit` when nothing matched - how
+   a Next.js site and several Node CLIs ended up with the iOS toolkit.
+
+   ```bash
+   eval "$(bash $HOME/.claude/lib/stack-detect.sh "$PROJECT_ROOT")"   # MA_STACKS, MA_STACK_WHY
+   node -e 'import(process.env.HOME+"/.claude/scripts/_stack-routing.mjs").then(m=>
+     console.log(m.pluginsForStacks(process.argv[1].split(" ").filter(Boolean)).plugins.join(" ")))' "$MA_STACKS"
+   ```
+
+   Report `MA_STACK_WHY` with the result. `ai-common-toolkit` and
+   `ai-analyst-toolkit` are in every answer, the empty one included: neither is
+   stack-specific. **No marker matched is an answer** - those two, not a guess.
+   A name the marketplace does not carry is dropped with `dropped[]` naming it,
+   so a toolkit that was never shipped is caught before it fails to load.
 3. Report the enabled set. To change later, run `/multi-agent:stack <ios|android|web|backend|...>` in the repo. Pipeline Phase 1 auto-detects the stack for its own routing regardless of enablement.
 
 The marketplace repo name (`multi-agent-plugins`) is generic; a different org points `{owner}` at its own fork - nothing in the pipeline is coupled to a specific account.

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

@@ -29,17 +29,26 @@ This replaces the old `stack-swap.sh` mechanic that physically moved skill direc
 
 ## Stack → plugin map
 
-| Stack | Plugins enabled (all `@multi-agent-plugins`) |
-|---|---|
-| `ios` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-ios-toolkit` |
-| `android` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-android-toolkit` |
-| `web` / `frontend` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-frontend-toolkit` |
-| `backend` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-backend-toolkit` |
-| `mobile` | common + `ai-ios-toolkit` + `ai-android-toolkit` |
-| `fullstack` | common + `ai-frontend-toolkit` + `ai-backend-toolkit` |
-| `all` | common + all four stack toolkits |
-
-Multiple args union their plugin sets: `ios backend` → common + iOS + backend.
+Derived, not listed. `pluginsForStacks()` in `scripts/_stack-routing.mjs` owns
+it, and this file deliberately carries no copy: the mapping was written out by
+hand in four places, and every copy is a chance to get the one asymmetry wrong -
+the detector says `web`, the marketplace ships `ai-frontend-toolkit`.
+
+```bash
+node -e 'import(process.env.HOME+"/.claude/scripts/_stack-routing.mjs").then(m=>{
+  const st=process.argv.slice(1).flatMap(a=>m.expandStackArg(a));
+  if(!st.length){console.error("Unknown stack. One of: "+m.KNOWN_STACKS.join(" ")+" mobile fullstack all");process.exit(1);}
+  const r=m.pluginsForStacks(st);
+  if(r.dropped.length) console.error("not in the marketplace, dropped: "+r.dropped.join(" "));
+  console.log(r.plugins.join(" "));
+})' "$@"
+```
+
+`ai-common-toolkit` and `ai-analyst-toolkit` are in every answer, including the
+empty one: neither is stack-specific. Multiple args union their sets, and the
+aliases (`frontend`, `mobile`, `fullstack`, `all`) expand in the module so
+`/multi-agent:stack mobile` cannot mean one thing here and another in the
+installer.
 
 ## Behaviour
 
@@ -70,13 +79,6 @@ if ! claude marketplace list 2>/dev/null | grep -q "$MP"; then
     || echo "note: add the marketplace once with: claude marketplace add {owner}/multi-agent-plugins"
 fi
 
-COMMON="ai-common-toolkit@${MP}"
-ANALYST="ai-analyst-toolkit@${MP}"
-IOS="ai-ios-toolkit@${MP}"
-ANDROID="ai-android-toolkit@${MP}"
-WEB="ai-frontend-toolkit@${MP}"
-BACKEND="ai-backend-toolkit@${MP}"
-
 # Enable-mode only: with zero args the write rules below would set every stack
 # toolkit to false (nothing but the always-on pair is in $ON), silently wiping the repo's
 # selection. No args belongs to the picker / status path (Behaviour step 1).
@@ -85,20 +87,17 @@ if [ "$#" -eq 0 ]; then
   exit 0
 fi
 
-# resolve every arg through the alias table, union the ON set
-ON="$COMMON $ANALYST"
-for ARG in "$@"; do
-  case "$ARG" in
-    ios)              ON="$ON $IOS" ;;
-    android)          ON="$ON $ANDROID" ;;
-    web|frontend)     ON="$ON $WEB" ;;
-    backend)          ON="$ON $BACKEND" ;;
-    mobile)           ON="$ON $IOS $ANDROID" ;;
-    fullstack)        ON="$ON $WEB $BACKEND" ;;
-    all)              ON="$ON $IOS $ANDROID $WEB $BACKEND" ;;
-    *) echo "Unknown stack '$ARG'. One of: ios android mobile backend web fullstack all"; exit 1 ;;
-  esac
-done
+# resolve every arg and derive the ON set - one owner, see the map above.
+# The marketplace suffix is appended INSIDE node: `$ON` is a single string, and
+# re-splitting it in the shell to suffix each name is the zsh word-splitting trap
+# (`printf %s@x $ON` suffixes the whole string, not each word).
+ON=$(MP="$MP" node -e 'import(process.env.HOME+"/.claude/scripts/_stack-routing.mjs").then(m=>{
+  const st=process.argv.slice(1).flatMap(a=>m.expandStackArg(a));
+  if(!st.length){console.error("Unknown stack. One of: "+m.KNOWN_STACKS.join(" ")+" mobile fullstack all");process.exit(1);}
+  const r=m.pluginsForStacks(st);
+  if(r.dropped.length) console.error("not in the marketplace, dropped: "+r.dropped.join(" "));
+  console.log(r.plugins.map(p=>p+"@"+process.env.MP).join(" "));
+})' "$@") || exit 1
 ```
 
 After resolving `$ON`, edit `.claude/settings.json` (create `{ "enabledPlugins": {} }` if absent) so that:

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

@@ -22,7 +22,23 @@ Show every active and completed task as a table.
 3. **Parse state**  -  for each task:
    - `taskId`, `branch`, `currentPhase`, `status`, `startedAt`, `autopilot`
 
-4. **Render as a table**:
+3b. **Sort into three groups, and label them.** `in_progress` alone cannot tell
+   a run that is waiting for you from one that died, and on this machine that
+   difference covered 20 runs: 3 were holding at Phase 6/7 with their PR already
+   open, 11 were left at a Phase 0 question with nothing built, 6 stopped
+   mid-development. One "in progress" label for all three is what made a
+   finished job and a crashed one share a row.
+
+   | Group | Test | Action offered |
+   |---|---|---|
+   | Waiting on you | `status == "awaiting_input"`, or a `pr.url`, or phase 6/7 | `resume #N` - the work landed, it needs your answer |
+   | Stopped mid-development | anything else past phase 0 | `resume #N` or `kill #N` |
+   | Left at a question | phase 0 | `garbage-collect --abandoned` - nothing was built |
+
+   A run with no `status` is **not** placed in any group. Unknown is not a
+   finding, and calling it dead is the same false claim in the other direction.
+
+4. **Render as a table**, grouped per 3b, with the group as a section heading:
    ```
    🤖 Multi-Agent Tasks
 

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

@@ -1,7 +1,7 @@
 ---
 description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and the multi-agent-toolkit MCP server. Use when work is finished and should be propagated across Claude Code, Copilot CLI, the repos, the website and the multi-agent-toolkit server."
 description-tr: "Tüm multi-agent ekosisteminin tek atımlık senkronu: Claude Code, Copilot CLI, pipeline repo, website ve multi-agent-toolkit MCP sunucusu."
-argument-hint: "[release] [multi-agent-toolkit] [--platform=<macos|linux|windows>]"
+argument-hint: "[release] [multi-agent-toolkit]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, WebFetch
 ---
 
@@ -9,7 +9,7 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, WebFetch
 
 **One command. Full ecosystem sync. No arguments needed.**
 
-When invoked, it synchronizes all targets in order. It detects what changed, updates only the stale ones, and returns a result report. The host platform (macOS / Linux / Windows) is auto-detected; all dispatch commands stay platform-agnostic through `~/.claude/lib/credential-store.sh`.
+When invoked, it synchronizes all targets in order. It detects what changed, updates only the stale ones, and returns a result report. macOS only (ADR-0012); credential access goes through `~/.claude/lib/credential-store.sh` so no call site names the keychain backend.
 
 **Input**: $ARGUMENTS (optional)
 
@@ -18,7 +18,6 @@ When invoked, it synchronizes all targets in order. It detects what changed, upd
 | (none) | Full ecosystem sync: Claude Code, Copilot CLI, pipeline repo, website, multi-agent-toolkit MCP server. |
 | `release` | Full sync + version bump + tag + npm publish + website deploy (plus the multi-agent-toolkit ship path) |
 | `multi-agent-toolkit` | Run Step 3d only: gate, commit and publish the companion MCP server |
-| `--platform=<macos\|linux\|windows>` | Override automatic platform detection. For CI / cross-platform smoke. |
 | `"change description"` | Apply the description to every target at once |
 
 ## Targets
@@ -32,25 +31,32 @@ When invoked, it synchronizes all targets in order. It detects what changed, upd
 | 4 | Website | `{owner}/{website-host}` | <- version + features |
 | 5 | multi-agent-toolkit MCP server | resolved from `prefs.global.devToolkit` or the `mcpServers` registration | own repo: gate, commit, publish |
 
-## Platform Support (macOS / Linux / Windows)
+## Platform Support (macOS only)
 
-The sync skill must run on all three platforms. Commands go through the platform-agnostic shell layer; the following compatibility rules are preserved for every target:
+v17.0.0 removed Linux and Windows (ADR-0012). `package.json` declares
+`os: ["darwin"]`, which npm enforces on the root package, so this tree cannot be
+installed elsewhere - a detection table for hosts that cannot run the installer
+would be a table the agent executes against a case that no longer exists.
 
-| Platform | Detection | Implication |
-|---|---|---|
-| macOS | `[[ "$OSTYPE" == "darwin"* ]]` | Default. BSD `stat -f %m`, `security` for Keychain. |
-| Linux | `[[ "$OSTYPE" == "linux"* ]]` | GNU `stat -c %Y`, `secret-tool` for Keychain (libsecret). |
-| Windows (Git Bash / MSYS2) | `[[ "$OSTYPE" == "msys" \|\| "$OSTYPE" == "cygwin" ]]` | `~` resolves to `/c/Users/<name>`. Powershell `CredentialManager` for Keychain. POSIX paths inside Git Bash. |
-| Windows (WSL) | `grep -qi microsoft /proc/version` | Linux toolchain inside WSL. Hostname format `WSL2-...`. |
-
-**Cross-platform contract for synced shell scripts:**
+**Contract for synced shell scripts.** The runtime is BSD userland and bash 3.2,
+and that is a stricter constraint than "cross-platform", not a looser one:
 
 1. Path handling: always quote (`"$f"`); use `$HOME`, never `/Users/...`.
-2. Timestamps: try BSD `stat -f` first, fall back to GNU `stat -c`  -  both already covered by `~/.claude/lib/repo-cache.sh` pattern.
-3. `find` traversal: include `-prune` for `node_modules`, `Pods`, `.build`, `DerivedData`, `.next`  -  same on every platform.
-4. Sed / awk: prefer POSIX-portable invocations. Avoid GNU-only `-i` without `''` on macOS or `-r` (use `-E` instead).
-5. Keychain I/O: always via `~/.claude/lib/credential-store.sh get|set`  -  never call `security` / `secret-tool` / `gcm` directly.
-6. Verification: after Step 3 (REPO), run `bash -n` on every shell script in `pipeline/lib/` and `pipeline/scripts/` to surface portability regressions early.
+2. `grep -P` is banned. BSD grep has no `-P`: it exits 2, and with `2>/dev/null`
+   that reads as "found nothing". Two gates have already shipped green for
+   exactly this reason. Use `-E`.
+3. Timestamps: `stat -c %Y` FIRST, then `stat -f %m`. GNU-first ordering is
+   required because `stat -f` is a valid GNU flag (`--file-system`) that
+   succeeds and prints something that is not a timestamp.
+4. Hashes: `sha256sum || shasum`, in that order. The gate fails a file that
+   names either alone.
+5. `find` traversal: `-prune` for `node_modules`, `Pods`, `.build`,
+   `DerivedData`, `.next`.
+6. Sed / awk: POSIX-portable. `-E`, never `-r`; `sed -i ''` on BSD.
+7. Keychain I/O: always via `~/.claude/lib/credential-store.sh get|set`, never
+   `security` directly - the wrapper is what keeps a secret off argv.
+8. Verification: after Step 3 (REPO), `bash -n` every shell script in
+   `pipeline/lib/` and `pipeline/scripts/`.
 
 ## Default Behavior (no arguments)
 
@@ -58,10 +64,9 @@ Run every step automatically:
 
 ```
 Step 0: DOCTOR      doctor.mjs  -  exit 2 or 4 stops the sync
-Step 1: PLATFORM    Detect macOS / Linux / Windows (Git Bash / WSL); export PLATFORM env
 Step 1.5: DETECT    Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 53 sub-command skills)
-Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 53 specs as refs + 8 agent TOML)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 56 sub-command skills)
+Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 56 specs as refs + 8 agent TOML)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub, bash -n on all sh)
 Step 3c: PLUGINS    pipeline shared/external -> multi-agent-plugins marketplace (rebuild knowledge/,
                      bump changed plugins' patch version, commit + push the plugins repo)
@@ -167,7 +172,7 @@ Step 0 gate rules and why: `features/doctor.md`.
 Unlike the Copilot step, this one does **not** hand-copy files. The Codex tree is a
 *transform* of the Claude tree, not a mirror of it, and the transform is real work:
 
-- the 53 sub-command specs become reference files, because Codex silently truncates
+- the 56 sub-command specs become reference files, because Codex silently truncates
   its skills block (see `cross-cli-contract.md` 2.6 for the measurement)
 - every `$HOME/.claude/...` reference to a CLI-owned tree is retargeted, with
   `agents/<persona>.md` becoming `.toml` and the dispatcher becoming the router skill
@@ -482,20 +487,21 @@ When invoked with the `release` argument:
 ## Sub-Command Sync (Claude Code <-> Copilot CLI Skills)
 
 This runs on the Claude <-> Copilot axis. Codex is NOT synced here: it receives the
-same 53 specs as reference files rather than as peer skills, via Step 2b -  see
+same 56 specs as reference files rather than as peer skills, via Step 2b -  see
 `cross-cli-contract.md` 2.6 for why the parity axis differs per host.
 
 | Claude Code | Copilot CLI |
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}/SKILL.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**53 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**56 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
-analysis, analysis-jira, analysis-resolve, autopilot, build-optimize, channels,
-complaint-analysis, create-jira, design-check, doctor, diff-explain, feedback,
-forget, garbage-collect, graph, help, ios-coding-standard, issue, jira,
-kill, language, local, local-autopilot, log, manual-test, prune-logs,
+analysis, analysis-jira, analysis-resolve, autopilot, autopilot-off,
+autopilot-on, autopilot-status, build-optimize, channels, complaint-analysis,
+create-jira, design-check, diff-explain, doctor, feedback, forget,
+garbage-collect, graph, help, ios-coding-standard, issue, jira, kill,
+language, local, local-autopilot, log, manual-test, prune-logs,
 prune-prompts, purge, refactor, resume, resume-local, review,
 review-analysis, review-issue, review-jira, routines, save, scan, search,
 setup, stack, status, steer, store-ready, sync, test, test-accessibility,

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

@@ -196,7 +196,7 @@ A git clone of the pipeline repo is a maintainer workspace, kept in sync by `/mu
 ```
 Current: v15.6.0   Latest: v15.6.1
   -> npm pack @{npm-scope}/multi-agent-pipeline@15.6.1
-  -> node install.js --all (53 commands, 263 scripts, 210 skills)
+  -> node install.js --all (56 commands, 263 scripts, 210 skills)
   -> migrate-prefs.mjs (0 changes  -  already v2.6.0)
 
 ✓ Updated: v15.6.0 → v15.6.1