@mmerterden/multi-agent-pipeline 17.0.0 → 17.3.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:
 
@@ -108,6 +108,9 @@ Status & Resume:
   /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 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:
 
@@ -384,6 +387,9 @@ Status & Resume:
   /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  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/sync/SKILL.md

@@ -65,8 +65,8 @@ Run every step automatically:
 ```
 Step 0: DOCTOR      doctor.mjs  -  exit 2 or 4 stops the sync
 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)
@@ -172,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
@@ -487,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

package/pipeline/lib/autopilot-activation.sh

@@ -0,0 +1,117 @@
+#!/usr/bin/env bash
+# autopilot-activation.sh  -  which repos may this machine pick work up from.
+#
+# The answer is NEVER "all of them" and never "whatever has the label". Measured
+# on one machine: 66 repos grant push, and a good half belong to other people -
+# a colleague's backend, someone's side project. A label is a filter, not a gate:
+# anyone able to open an issue in a repo you happen to have push on could put
+# `agent-queue` on it. The gate is this picker, and the picker is per machine.
+#
+# Two lists come out, and the difference matters:
+#
+#   eligible    push rights AND a checkout on this machine
+#   unavailable push rights, no checkout - LISTED, with that as the reason
+#
+# The second list is printed rather than dropped. Silently hiding 40 repos from a
+# 66-repo answer looks exactly like a permissions problem, and the user then goes
+# looking for a token fault that does not exist.
+#
+# Usage:
+#   bash autopilot-activation.sh list            # TSV: state, nameWithOwner, localPath
+#   bash autopilot-activation.sh list --json
+#   . autopilot-activation.sh; ma_ap_local_path <owner/repo>
+#
+# Exit: 0 on success (including an empty list), 2 on usage, 3 when gh cannot answer.
+
+set -uo pipefail
+
+# Repo roots to search for checkouts. $HOME's immediate children covers the
+# normal layout; MA_AUTOPILOT_REPO_ROOTS overrides it for tests and for anyone
+# who keeps checkouts somewhere else.
+MA_AP_ROOTS="${MA_AUTOPILOT_REPO_ROOTS:-$HOME}"
+
+# owner/repo for a checkout, read from its origin remote. Both URL forms, and a
+# trailing .git is stripped - `git@github.com:o/r.git` and
+# `https://github.com/o/r` are the same repo and a picker that treats them as
+# two shows the user a duplicate they cannot explain.
+ma_ap_remote_slug() {
+  local dir="$1" url
+  url=$(git -C "$dir" remote get-url origin 2>/dev/null) || return 1
+  url="${url%.git}"
+  case "$url" in
+    *github.com[:/]*) printf '%s\n' "${url##*github.com[:/]}" ;;
+    *) return 1 ;;
+  esac
+}
+
+# Every checkout under the roots, as `slug<TAB>path`. One pass, so the lookup
+# below is a grep rather than a walk per repo.
+ma_ap_checkout_index() {
+  local root d slug
+  for root in $MA_AP_ROOTS; do
+    [ -d "$root" ] || continue
+    for d in "$root"/*/; do
+      [ -d "$d/.git" ] || continue
+      slug=$(ma_ap_remote_slug "${d%/}") || continue
+      printf '%s\t%s\n' "$slug" "${d%/}"
+    done
+  done
+}
+
+ma_ap_local_path() { # $1 = owner/repo
+  ma_ap_checkout_index | awk -F'\t' -v s="$1" 'tolower($1)==tolower(s){print $2; exit}'
+}
+
+# Repos the authenticated account may push to.
+#
+# The query string form is deliberate: `gh api user/repos --field affiliation=...`
+# sends the value as a BODY field on a GET, which this endpoint ignores - it
+# answers with the default affiliation and the caller never learns the filter did
+# not apply. Measured: the --field form returned 0 rows here, the query string
+# form returned 66.
+ma_ap_writable_repos() {
+  gh api "user/repos?affiliation=owner,collaborator,organization_member&per_page=100" \
+    --paginate -q '.[] | select(.permissions.push == true) | .full_name' 2>/dev/null
+}
+
+ma_ap_list() {
+  local json="${1:-}" slug path index
+  index=$(ma_ap_checkout_index)
+  local repos
+  repos=$(ma_ap_writable_repos)
+  if [ -z "$repos" ]; then
+    echo "autopilot-activation: gh returned no writable repos - check 'gh auth status'" >&2
+    return 3
+  fi
+
+  local first=1
+  [ "$json" = "--json" ] && printf '['
+  while IFS= read -r slug; do
+    [ -n "$slug" ] || continue
+    path=$(printf '%s\n' "$index" | awk -F'\t' -v s="$slug" 'tolower($1)==tolower(s){print $2; exit}')
+    local state="eligible"
+    [ -z "$path" ] && state="unavailable"
+    if [ "$json" = "--json" ]; then
+      [ "$first" -eq 0 ] && printf ','
+      first=0
+      printf '{"state":"%s","nameWithOwner":"%s","localPath":"%s"}' "$state" "$slug" "$path"
+    else
+      printf '%s\t%s\t%s\n' "$state" "$slug" "$path"
+    fi
+  done <<EOF
+$repos
+EOF
+  [ "$json" = "--json" ] && printf ']\n'
+  return 0
+}
+
+if [ "${BASH_SOURCE[0]:-$0}" = "$0" ]; then
+  case "${1:-}" in
+    list) ma_ap_list "${2:-}" ;;
+    "" | -h | --help) grep -E '^#( |$)' "$0" | sed -E 's/^# ?//' ;;
+    *)
+      echo "autopilot-activation: unknown command ${1}" >&2
+      exit 2
+      ;;
+  esac
+fi