@mmerterden/multi-agent-pipeline 17.0.0 → 17.1.0

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

@@ -0,0 +1,74 @@
+---
+description: "Show what continuous mode is doing here: what runs at which phase, what is queued, what waits for an answer, what PRs it opened today. Use when asked whether autopilot is on."
+description-tr: "Sürekli modun ne yaptığını gösterir: ne koşuyor hangi fazda, sırada ne var, ne cevap bekliyor, bugün hangi PR'lar açıldı."
+argument-hint: "[--subjects]  -  --subjects prints one widget line per in-flight item"
+---
+
+# multi-agent autopilot-status  -  what is it doing
+
+```bash
+bash "$HOME/.claude/scripts/autopilot-status.sh" ${ARGUMENTS}
+```
+
+That script is the **only** producer. The menu bar indicator, this command and
+the session-start hook all render the same `status.json` it writes, because the
+moment each computes its own answer they start disagreeing - which is the failure
+this whole area was built around: a run reading `in_progress` while its PR was
+already open.
+
+## What the output means
+
+| Line | Meaning |
+|---|---|
+| `KAPALI` with repos selected | the selection is kept, launchd holds no job. `autopilot-on` starts it again without re-asking |
+| `kurulu değil` | never configured on this machine; nothing has been written |
+| `Koşuyor` | in flight now. Phase and elapsed come from the run's own state, not from a guess |
+| `Cevap bekliyor` | the item was not mature enough, the open questions were posted as a comment, and it resumes on its own once answered |
+| `config açık ama launchd'de iş yok` | the failure a `resume` command would have hidden: an OS update dropped the plist, or it was booted out. Re-run `autopilot-on` |
+
+An empty queue is reported with the reason - no item carries the label yet - and
+not as an error. That is the most common "why is nothing happening", and it is
+not a fault.
+
+## The menu bar indicator
+
+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
+elapsed time and the stack, then the queue, then what is waiting, then the PRs of
+the last day - each one clickable.
+
+The indicator only **draws**. It cannot start, stop or change a run: control
+stays here, where it is confirmed. It disappears from the list the moment an item
+finishes, and the item reappears under `Raporlar` with its PR.
+
+No `swiftc` means no indicator and nothing else changes.
+
+## Watching the queue before anything runs
+
+The queue can be read dry, with no scheduling and nothing dispatched:
+
+```bash
+node "$HOME/.claude/scripts/autopilot-intake.mjs" --dry-run | jq '{queued: [.queued[].id], awaiting: [.awaiting[].id], dropped: [.dropped[] | {id, reason}]}'
+```
+
+This is the honest way to decide whether to arm the runner: it queries the same
+sources, applies the same ordering and the same attempt history, and writes
+nothing at all. `dropped` is the part worth reading - it is where "why is my
+issue not being picked up" is answered, one reason per item.
+
+## `--subjects`
+
+One line per in-flight item, shaped for the native task widget, with the numbers
+travelling **inside** the subject string because the widget takes exactly one
+string per row:
+
+```
+PROJ-1234 · Full · Faz 3/8 Dev · ios
+PROJ-1199 · cevap bekliyor
+```
+
+Honest limit, worth saying rather than discovering: that widget belongs to the
+session that calls `TaskUpdate`, and it refreshes when that session takes a turn -
+when you type, or when a hook fires. It is a view, not a live counter. The menu
+bar indicator is the one that updates on its own.

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

@@ -159,16 +159,39 @@ Non-interactive in three cases  -  menu skipped entirely, flag values or prefs u
 
 For each selected **content** source, produce one section body. Each section runs through the `humanizer` skill separately (Jira / Confluence / PR tones differ).
 
+**The Jira body is not the PR body.** Jira is read by the person who filed the
+ticket and by whoever tests it, so its comment carries the four sections
+`channels/jira.md` fixes - `summary` (`Geliştirme Özeti`), `test_scenarios`
+(`Test Senaryoları`), `impact` (`Etki Analizi`) and `context_refs`
+(`Bağlantılar`) - and nothing else. Technical sections go to the PR and to
+Confluence, where the reader is a code reviewer. A shipped Jira comment once
+explained a hash-table mutation across three paragraphs of class names; it was
+correct, and it was the wrong document. When `jira` is a selected channel, drop
+the technical sections from its body rather than converting them: the PR link on
+line 1 is how a Jira reader reaches the detail.
+
+`impact` is not a technical section in disguise. It answers four questions -
+what was wrong, what was changed, which areas must be tested, what else is
+affected - in the same plain register as the summary, and it is the part a test
+lead reads before deciding how wide to test.
+
 | Content option | Generated section |
 |---|---|
 | Normal analiz | `### Analysis`  -  impact summary from Phase 1, risks from Phase 4 (pipeline-log source, high-level only) |
-| Teknik analiz | `### Technical Details`  -  Changes (what/why per file group), Architecture (structural decisions, pattern changes), Dependencies (new imports/frameworks/packages). Source: Phase 2 planning + Phase 3 dev log + `git diff --stat`. Same shape as PR body's Technical Details  -  gives Jira/Confluence readers the code-reviewer view without making them click into the PR. |
+| Teknik analiz | `### Technical Details`  -  Changes (what/why per file group), Architecture (structural decisions, pattern changes), Dependencies (new imports/frameworks/packages). Source: Phase 2 planning + Phase 3 dev log + `git diff --stat`. **PR and Confluence only** - never rendered into a Jira comment. |
 | Test senaryoları | `### Test Scenarios`  -  precondition / steps / expected table (4-8 rows), user perspective |
 | Auto-diff | Old enrich Output Template verbatim  -  Root Cause / Solution / Changed Files / Test Scenarios |
 | Manuel not | `### Notes`  -  user-provided paragraph, or LLM-split into subsections if `--message` is plain text and long |
 | Cost özeti | `### Cost Summary`  -  per-phase token tally + est. USD table. Source: `phase-tracker.sh` phase status + optional OTel spans. See "Cost summary generation" below. |
 | Yapılan iş özeti | `### Work Summary`  -  executive one-screen summary: task + branch + base + PR, scope delivered (done/[pending] per Phase 2 task), changed files with +/- counts (capped at 20 rows), review outcome (accepted/deferred/rejected + approved), phase tick strip. Source: `agent-state.json` + `phase-tracker.json` + `git diff --numstat base...HEAD`. See "Work summary generation" below. |
 
+**The content options are sources, not the body's shape.** Which sections a PR
+body carries and in what order is fixed by `channels/pr.md` (`summary` →
+`technical` → `architecture` → `impact` → `test_scenarios` → `visuals` → `risk`
+→ `dependencies` → `build` → `related`); the options below choose what gets
+gathered to fill them. A content option left unselected means a section has no
+source, not that the section may be reordered or renamed.
+
 **Output template (aggregated across selected content options):**
 
 ```markdown
@@ -197,9 +220,13 @@ For each selected **content** source, produce one section body. Each section run
 | `path/to/File.ext` | +N / -M |
 
 ### Test Scenarios                  ← if "Test senaryoları" OR "Auto-diff" selected
-| # | Precondition | Steps | Expected | Status |
-|---|--------------|-------|----------|--------|
-| 1 | ...          | ...   | ...      | To Test|
+**1. {what this scenario exercises}**
+1. {step the tester performs}
+2. **Expected:** {what they should see}
+
+**2. {regression scenario}**
+1. {step}
+2. **Expected:** {what should still behave as before}
 
 ### Notes                           ← if "Manuel not" selected
 {user message}
@@ -240,13 +267,7 @@ If no cached report exists, skip silently  -  this is augmentation, not a gate.
 
 **Work summary generation:**
 
-Emitted only when `reportContent.workSummary === true` and at least one of (`agent-state.json`, `--branch` flag) is available. The shell adapter is `$HOME/.claude/scripts/render-work-summary.sh <taskId>`:
-
-1. **Task header**  -  `taskId`, `branch`, `baseBranch`, `prNumber` from `agent-state.json` (or explicit flags for post-hoc invocation).
-2. **Scope delivered**  -  Phase 2 `planTodos[]` / `tasks[]` rendered as `done` (status=done) or `pending` (anything else) rows. Task id + title shown; `(deferred  -  rationale)` appended if the task's `status` is `"deferred"`.
-3. **Changed files**  -  `git -C $WORKTREE diff --numstat $baseBranch...HEAD`. Shows `` `path` (+add / -del) `` per row, capped at 20 with a `_... +N more files not shown_` footer when exceeded. Total adds/dels + file count in section header.
-4. **Review outcome**  -  from `reviewConsensus` (pre-v6.1) or `phases["4"].triage`: `{accepted} accepted · {deferred} deferred · {rejected} rejected · approved={bool}`. Hidden entirely when all three buckets are empty (normal for a run that never reached Phase 4).
-5. **Phase tick strip**  -  single line from the tracker state (`render-work-summary.sh` resolves worktree/artifacts copies, then `$HOME/.claude/logs/multi-agent/{taskId}/tracker-state.json`): `0 Init [done] · 1 Analysis [done] · 2 Planning [done] · 3 Dev [done] · 4 Review [done] · 5 Test skipped · 6 Commit [done] · 7 Report active`. Marks: `done` completed · `active` in_progress · `failed` failed · `skipped` skipped · `·` pending.
+Emitted only when `reportContent.workSummary === true` and at least one of (`agent-state.json`, `--branch` flag) is available. The shell adapter is `$HOME/.claude/scripts/render-work-summary.sh <taskId>`, and that script's own header is the spec for what it emits - task header, scope delivered, changed files, review outcome, phase strip - including the caps and the hidden-when-empty rules. Re-stating those five steps here gave the pipeline two specifications of one script, and the prose one is the copy that rots. Exit 2 means the state was unreadable: skip the section, do not substitute a hand-written one.
 
 **Output template:**
 
@@ -369,7 +390,15 @@ Aggregated Markdown from Step 5 → PR description. GitHub uses `gh pr edit --bo
 Full contract: [`$HOME/.claude/multi-agent-refs/channels/pr.md`]($HOME/.claude/multi-agent-refs/channels/pr.md)  -  Bitbucket payload assembly snippet, version-mismatch retry, `--ready` promotion, multi-repo cross-link block.
 
 #### Adapter: Jira comment
-Body converted to Jira wiki markup (`### ...` → `*...*`, `- [ ] ...` → `# ...`, `` `x` `` → `{{x}}`, tables to `||h||h|| |c|c|`); first line is the PR URL. The converted body then goes through `node "$HOME/.claude/scripts/jira-wiki-escape.mjs"` (required, not optional  -  Jira renders `:)` `(x)` `(!)` `(/)` as emoticon images, and a Swift selector like `login(source:input:)` ends in `:)`). POST `/rest/api/2/issue/{id}/comment` via heredoc + `jq --rawfile` + `curl --data-binary @file`, from the escaped file. Token resolved from `keychainMapping.jira`.
+Sections: `summary` + `test_scenarios` + `impact` + `context_refs` only - the technical ones go to the PR and Confluence (`channels/jira.md` fixes the order). The PR URL goes on line 1, above the first heading. The wiki-markup conversion table lives in that same ref and only there: the four-row summary that used to sit here mapped `### ...` to `*...*`, which is italic, not a heading - a shrunken copy of a table is a second answer, and it was the wrong one.
+
+Then post it - do not assemble the request:
+
+```bash
+bash "$HOME/.claude/lib/jira-publish.sh" --issue "$JIRA_ID" --body-file "$F" --target comment
+```
+
+The publisher escapes every body (Jira renders `:)` `(x)` `(!)` `(/)` as emoticon images, and a Swift selector like `login(source:input:)` ends in `:)`) and resolves the token from `keychainMapping.jira` without putting it on argv. The hand-rolled `jq`+`curl` this replaced kept the escape as a separate step, and a shipped comment turned `hash(into:)` into a smiley.
 
 Full contract: [`$HOME/.claude/multi-agent-refs/channels/jira.md`]($HOME/.claude/multi-agent-refs/channels/jira.md)  -  full conversion table, multi-repo PR-list prepend, Wiki→Jira triad interaction.
 

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