@mmerterden/multi-agent-pipeline 16.21.0 → 16.24.0

package/README.md

@@ -89,7 +89,7 @@ Depth, autopilot and `--local` are the only knobs on the run itself; everything
 
 ## Commands
 
-`/multi-agent` plus 55 sub-commands. `/multi-agent:help` renders the same catalog in your terminal, in your `outputLanguage`.
+`/multi-agent` plus 51 sub-commands. `/multi-agent:help` renders the same catalog in your terminal, in your `outputLanguage`.
 
 ### Pipeline entries
 
@@ -187,8 +187,6 @@ Depth, autopilot and `--local` are the only knobs on the run itself; everything
 | `/multi-agent:uninstall` | Remove the pipeline from every CLI. Keychain tokens always left intact |
 | `/multi-agent:help` | This catalog, in the terminal, in your `outputLanguage` |
 
-Four names are kept only as redirects: `:dev` and `:dev-local` point at `/multi-agent` and `:local` answered Short, and `:dev-autopilot` / `:dev-local-autopilot` have no equivalent - "fast plus unattended" was removed in v16.0.0.
-
 ### Subagents
 
 Eight are installed alongside the commands and dispatched by the phases: `explorer` and `task-clarifier` (Phase 0-1), `ios-architect` / `android-architect` / `backend-architect` (Phase 2), `dev-critic` (Phase 3), `code-reviewer` and `security-auditor` (Phase 4).
@@ -209,17 +207,17 @@ This enables the matching plugin (+ the shared `ai-common` plugin) in the repo's
 
 ## Tool support
 
-The pipeline runs natively on **Claude Code**, **Copilot CLI** and **Codex CLI** - all three install from the same `pipeline/` source and get the same 55 commands.
+The pipeline runs natively on **Claude Code**, **Copilot CLI** and **Codex CLI** - all three install from the same `pipeline/` source and get the same 51 commands.
 
 | Tool | Flag | What it installs |
 |---|---|---|
 | Claude Code | `--claude` (default) | slash commands + skills + agents + three `PreToolUse` hooks (secret scan, agent-guard, read-size gate) |
-| Copilot CLI | `--copilot` | instructions + 55 sub-command skills + scripts |
-| Codex CLI | `--codex` | one router skill + 55 specs as refs + 8 agent TOML + `AGENTS.md` block + `codex mcp add` |
+| Copilot CLI | `--copilot` | instructions + 51 sub-command skills + scripts |
+| Codex CLI | `--codex` | one router skill + 51 specs as refs + 8 agent TOML + `AGENTS.md` block + `codex mcp add` |
 
 Filter skills by stack with `--platform=ios\|android\|all`.
 
-**Why Codex gets one skill and not 55.** Codex assembles every discovered skill's name
+**Why Codex gets one skill and not 51.** Codex assembles every discovered skill's name
 and description into a single prompt block and drops entries when it overflows, with no
 error. Measured on 0.145: installing one plugin that declares 142 skills surfaced only
 75 of them and evicted an unrelated user skill. So on Codex the pipeline ships a single

package/README.tr.md

@@ -89,7 +89,7 @@ Koşunun kendisinde ayarlanabilen tek şey derinlik, autopilot ve `--local`; ger
 
 ## Komutlar
 
-`/multi-agent` ve 55 alt komut. `/multi-agent:help` aynı katalogu terminalde, `outputLanguage` ayarına göre gösterir.
+`/multi-agent` ve 51 alt komut. `/multi-agent:help` aynı katalogu terminalde, `outputLanguage` ayarına göre gösterir.
 
 ### Pipeline girişleri
 
@@ -187,8 +187,6 @@ Koşunun kendisinde ayarlanabilen tek şey derinlik, autopilot ve `--local`; ger
 | `/multi-agent:uninstall` | Pipeline'ı her CLI'dan kaldırır. Keychain token'larına hiç dokunmaz |
 | `/multi-agent:help` | Bu katalog, terminalde, `outputLanguage`'ine göre |
 
-Dört ad yalnızca yönlendirme olarak duruyor: `:dev` ve `:dev-local` sırasıyla `/multi-agent` ve `:local` çalıştırıp Short seçmeye yönlendirir, `:dev-autopilot` ile `:dev-local-autopilot` ise karşılıksız - "hızlı artı gözetimsiz" v16.0.0'da kaldırıldı.
-
 ### Alt agent'lar
 
 Komutlarla birlikte sekiz agent kurulur ve fazlar bunları çağırır: `explorer` ve `task-clarifier` (Faz 0-1), `ios-architect` / `android-architect` / `backend-architect` (Faz 2), `dev-critic` (Faz 3), `code-reviewer` ve `security-auditor` (Faz 4).
@@ -209,17 +207,17 @@ Bu, ilgili plugin'i (+ ortak `ai-common` plugin'ini) repo'nun `.claude/settings.
 
 ## Araç desteği
 
-Pipeline **Claude Code**, **Copilot CLI** ve **Codex CLI** üzerinde native çalışır - üçü de aynı `pipeline/` kaynağından kurulur ve aynı 55 komutu alır.
+Pipeline **Claude Code**, **Copilot CLI** ve **Codex CLI** üzerinde native çalışır - üçü de aynı `pipeline/` kaynağından kurulur ve aynı 51 komutu alır.
 
 | Araç | Bayrak | Ne kurar |
 |---|---|---|
 | Claude Code | `--claude` (varsayılan) | slash komutları + skill'ler + agent'lar + üç `PreToolUse` hook'u (secret scan, agent-guard, okuma-boyutu geçidi) |
-| Copilot CLI | `--copilot` | talimatlar + 55 alt-komut skill'i + script'ler |
-| Codex CLI | `--codex` | bir router skill + ref olarak 55 spec + 8 agent TOML + `AGENTS.md` bloğu + `codex mcp add` |
+| Copilot CLI | `--copilot` | talimatlar + 51 alt-komut skill'i + script'ler |
+| Codex CLI | `--codex` | bir router skill + ref olarak 51 spec + 8 agent TOML + `AGENTS.md` bloğu + `codex mcp add` |
 
 Skill'leri stack'e göre filtrele: `--platform=ios\|android\|all`.
 
-**Codex neden 55 değil de tek bir skill alıyor.** Codex, keşfettiği her skill'in adını
+**Codex neden 51 değil de tek bir skill alıyor.** Codex, keşfettiği her skill'in adını
 ve açıklamasını tek bir prompt bloğuna toplar ve blok taştığında girdileri hatasızca
 düşürür. 0.145 üzerinde ölçüldü: 142 skill deklare eden bir plugin kurulduğunda sadece
 75'i yüzeye çıktı ve alakasız bir kullanıcı skill'i tahliye edildi. Bu yüzden Codex'te

package/docs/architecture.md

@@ -117,7 +117,7 @@ graph TB
     end
 
     subgraph "Pipeline Specs"
-        CMD[commands/<br/>55 command files]
+        CMD[commands/<br/>51 command files]
         AGT[agents/<br/>8 agent personas]
         RUL[rules/<br/>12 domain rules]
         PHS[multi-agent-refs/phases/<br/>phase specs + contracts]
@@ -169,8 +169,8 @@ revisions of this diagram - Codex CLI and the two independently-shipped repos
 ```mermaid
 graph TD
     CC["Claude Code<br/>(source of truth)"]
-    COP["Copilot CLI<br/>(instructions + 55 skills)"]
-    COD["Codex CLI<br/>(1 router skill + 55 refs)"]
+    COP["Copilot CLI<br/>(instructions + 51 skills)"]
+    COD["Codex CLI<br/>(1 router skill + 51 refs)"]
     REPO["Pipeline Repo<br/>(npm package)"]
     WEB["Website"]
     PLUGREPO["multi-agent-plugins<br/>(5 stack plugins, own repo)"]

package/docs/ecosystem.md

@@ -5,7 +5,7 @@ separately, wired together at install time and at run time:
 
 | Repo | What it owns | Ships as |
 |---|---|---|
-| **`multi-agent-pipeline`** (this repo) | Orchestration: the 8-phase flow, the 55 slash commands, quality gates, review/triage, cross-CLI parity | npm package (`@mmerterden/multi-agent-pipeline`), installs itself onto Claude Code / Copilot CLI / Codex CLI |
+| **`multi-agent-pipeline`** (this repo) | Orchestration: the 8-phase flow, the 51 slash commands, quality gates, review/triage, cross-CLI parity | npm package (`@mmerterden/multi-agent-pipeline`), installs itself onto Claude Code / Copilot CLI / Codex CLI |
 | **`multi-agent-plugins`** | Stack knowledge: per-platform component/lifecycle skills (iOS, Android, Frontend, Backend) + shared knowledge | Claude Code marketplace, 5 independently-versioned plugins |
 | **`multi-agent-toolkit-mcp`** | The pipeline's hands on devices and browsers: 80 MCP tools across 6 categories (simulator/emulator control, accessibility audit, store compliance, web automation, Figma-vs-mock design audit, an agent-DSL batch runner) | npm package, registered as a standard stdio MCP server on every host |
 
@@ -18,7 +18,7 @@ Either can be swapped or removed without touching the other two's source.
 graph LR
     subgraph PIPE ["multi-agent-pipeline (orchestrator)"]
         direction TB
-        PHASES["8 phases · 55 commands"]
+        PHASES["8 phases · 51 commands"]
         GATES["deterministic gates + review triage"]
     end
 
@@ -64,8 +64,8 @@ only those:
 graph TD
     CC["Claude Code<br/>~/.claude/commands/multi-agent/<br/>(source of truth)"]
 
-    CC -->|"Step 2: copy + reformat<br/>55 sub-command skills"| COP["Copilot CLI<br/>~/.copilot/skills/"]
-    CC -->|"Step 2b: transform<br/>(install.js --codex)"| COD["Codex CLI<br/>1 router skill + 55 refs<br/>+ 8 agent TOML"]
+    CC -->|"Step 2: copy + reformat<br/>51 sub-command skills"| COP["Copilot CLI<br/>~/.copilot/skills/"]
+    CC -->|"Step 2b: transform<br/>(install.js --codex)"| COD["Codex CLI<br/>1 router skill + 51 refs<br/>+ 8 agent TOML"]
     CC -->|"Step 3: genericize<br/>(strip personal data)"| REPO["multi-agent-pipeline repo<br/>pipeline/"]
     CC -->|"Step 4: version + feature sync"| WEB["Website<br/>projects.ts / i18n.tsx"]
 
@@ -153,7 +153,7 @@ measurements behind this table):
 
 | | Claude Code | Copilot CLI | Codex CLI |
 |---|---|---|---|
-| **Pipeline commands** | 55 slash-command skills, native | 55 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 55 command specs as reference files - Codex silently truncates its skills block past a few dozen entries, so sub-commands are not peer skills here |
+| **Pipeline commands** | 51 slash-command skills, native | 51 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 51 command specs as reference files - Codex silently truncates its skills block past a few dozen entries, so sub-commands are not peer skills here |
 | **Stack plugins** | Marketplace plugin, loaded natively, resolved by `.claude/settings.json` enabled-list | Enabled plugin's authored skills copied flat into `~/.copilot/skills/`; `knowledge/` **not** re-copied (already delivered via `shared/external`) | Copied as reference files under `~/.codex/multi-agent-refs/skills/`, plugin-prefixed on name clash (e.g. `architecture` → `ai-ios-toolkit-architecture`) |
 | **Component dispatch (Phase 3)** | Marketplace plugin's `create-component`/`create-screen` skill via the Skill tool | No plugin loader - the enabled stack plugin's authored skills (incl. `create-component`) are copied flat into `~/.copilot/skills/` at install time (the old frozen `figma-*` copies are pruned, they were never a fallback) | Not part of the enforced parity axis; classification + state-shape must match, skill *inventory* does not |
 | **multi-agent-toolkit-mcp** | `claude mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` | `copilot mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` | `codex mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` (skipped with a warning if `codex` isn't on `PATH`) |

package/install/templates/copilot-instructions.md

@@ -32,7 +32,7 @@
 
 Depth is the question, not a command: Full runs all 8 phases, Short is
 Init -> Dev(Opus) -> Review -> Test -> Commit -> Report. Review is never
-skipped either way. The multi-agent-dev* names were removed in v16.0.0.
+skipped either way.
 
 ## Language axes (en/tr)
 
@@ -111,7 +111,11 @@ or, on machines with Claude Code also installed:
 ## Progress Tracking - required
 
 Every phase boundary MUST call the cross-CLI tracker. The tracker is the single source of truth
-for user-visible phase progress on Copilot CLI (no TaskCreate native UI here). Banner is optional flair.
+for user-visible phase progress on Copilot CLI (no native task widget here). Banner is optional flair.
+
+Copilot CLI has no TaskCreate equivalent, so the bordered card IS the widget - and Copilot
+collapses tool output, so a card left in stdout never reaches the user. **Reprint the card
+inside your reply at every phase boundary.** `phase-tracker.sh tiles` says so and prints it.
 
 ```bash
 # Bootstrap once at Phase 0 start - initialize all 8 phase tiles:
@@ -119,6 +123,7 @@ bash ~/.copilot/scripts/phase-tracker.sh init "$TASK_ID"
 for p in 0:Init 1:Analysis 2:Planning 3:Dev 4:Review 5:Test 6:Commit 7:Report; do
   bash ~/.copilot/scripts/phase-tracker.sh add "${p%%:*}" "${p#*:}"
 done
+bash ~/.copilot/scripts/phase-tracker.sh tiles
 
 # At each phase boundary - update status. Tracker stamps started_at on first
 # transition to in_progress, completed_at on terminal status (completed/failed/skipped).
@@ -129,6 +134,16 @@ done
 bash ~/.copilot/scripts/phase-tracker.sh update <N> in_progress
 bash ~/.copilot/scripts/phase-tracker.sh update <N> completed    # or failed / skipped
 
+# `update <N> completed` EXITS 3 for phases 1-4 when no tokens were recorded for
+# that phase: record model + tokens first, then re-run the same update. A phase
+# that genuinely ran no LLM call completes with `--no-llm`. Each update prints a
+# `-- NEXT (required) --` block naming what to reprint and the narration line.
+
+# At the end of the run, print the closing report (per-phase elapsed, tokens,
+# model, USD, totals) next to the work summary, and reprint both in your reply:
+bash ~/.copilot/scripts/phase-tracker.sh report
+bash ~/.copilot/scripts/render-work-summary.sh "$TASK_ID"
+
 # After every LLM dispatch, record its token cost against the active phase (v5.5.0):
 bash ~/.copilot/scripts/phase-tracker.sh tokens <N> <input_tokens> <output_tokens>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "16.21.0",
+  "version": "16.24.0",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",

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

@@ -91,7 +91,6 @@ Lib scripts (`~/.claude/lib/`):
 | `language [en\|tr]` | Show or set the assistant `outputLanguage` (explanations and chat replies). `promptLanguage` is locked to `en` and is not toggleable. No arg = show current `outputLanguage`. With `en` or `tr` = set and persist `outputLanguage`. External payloads (commits, PR bodies, Jira) stay English. |
 | `setup` | Keychain token + Git Identity onboarding |
 | `--local` | No worktree  -  works directly on local branch |
-| `--dev` and `dev-*` | **Removed in v16.0.0.** Depth is the Phase 0 Step 7.5 question, not a flag. Print the redirect and continue at `/multi-agent` (or `:local`) with Short selected; for the two autopilot names there is no equivalent, so print the stub's two options and stop. |
 | `autopilot` | Skip user confirmations, auto commit/PR |
 | No args / `help` | Show usage guide |
 
@@ -124,10 +123,6 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 | `build-optimize` | `$HOME/.claude/commands/multi-agent/build-optimize/SKILL.md` |
 | `local` | `$HOME/.claude/commands/multi-agent/local/SKILL.md` |
 | `local-autopilot` | `$HOME/.claude/commands/multi-agent/local-autopilot/SKILL.md` |
-| `dev` | `$HOME/.claude/commands/multi-agent/dev/SKILL.md` |
-| `dev-autopilot` | `$HOME/.claude/commands/multi-agent/dev-autopilot/SKILL.md` |
-| `dev-local` | `$HOME/.claude/commands/multi-agent/dev-local/SKILL.md` |
-| `dev-local-autopilot` | `$HOME/.claude/commands/multi-agent/dev-local-autopilot/SKILL.md` |
 | `create-jira` | `$HOME/.claude/commands/multi-agent/create-jira/SKILL.md` (loads `$HOME/.claude/multi-agent-refs/generate-issue.md`) |
 | `stack` | `$HOME/.claude/commands/multi-agent/stack/SKILL.md` |
 | `language` | Handled inline  -  set/show prompt language in preferences |

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

@@ -95,11 +95,6 @@ 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)
 
-Removed in v16.0.0:
-  :dev -> /multi-agent + Short · :dev-local -> :local + Short
-  :dev-autopilot and :dev-local-autopilot have no equivalent  -  fast plus
-  unattended is gone; pick unattended-and-Full or fast-and-attended.
-
 ------------------------------------------------------------
 
 Status & Resume:
@@ -372,11 +367,6 @@ 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)
 
-v16.0.0'da kaldırılanlar:
-  :dev -> /multi-agent + Kısa · :dev-local -> :local + Kısa
-  :dev-autopilot ve :dev-local-autopilot'un karşılığı yok  -  hızlı+gözetimsiz
-  bitti; ya gözetimsiz-ve-Tam ya hızlı-ve-insan-başında seçilir.
-
 ------------------------------------------------------------
 
 Status & Resume:

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

@@ -1,6 +1,6 @@
 ---
-description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to dev/dev-local. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
-description-tr: "Bir iOS modulunu paylasilan kodlama-standardi registry'sine (99 sabit-ID kural) gore denetler, duzeltme plani cikarir, sonra dev/dev-local'e devreder. Bir modulde standart gecisi icin, ya da bir review'un gorus yerine kural ID'si istedigi durumda kullan."
+description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent or :local. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
+description-tr: "Bir iOS modulunu paylasilan kodlama-standardi registry'sine (99 sabit-ID kural) gore denetler, duzeltme plani cikarir, sonra /multi-agent veya :local'e devreder. Bir modulde standart gecisi icin, ya da bir review'un gorus yerine kural ID'si istedigi durumda kullan."
 argument-hint: "[module name or path]"
 allowed-tools: Skill, Bash, Read, Edit, Write, AskUserQuestion
 ---

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

@@ -67,7 +67,7 @@ Depth is a separate axis, asked at Phase 0 Step 7.5 rather than encoded in the c
 
 ## Delegation
 
-Orchestrator routing: the routing table in `$HOME/.claude/commands/multi-agent/SKILL.md` resolves `local-autopilot` as the union of the `dev-local` + `autopilot` mode mixins. Contract details: `$HOME/.claude/multi-agent-refs/phases/phase-0-init.md` Step 6 (local branch) + `$HOME/.claude/multi-agent-refs/phases/phase-2-planning.md` Step 5 (autopilot gate skip + safety classifier).
+Orchestrator routing: the routing table in `$HOME/.claude/commands/multi-agent/SKILL.md` resolves `local-autopilot` as the union of the `local` + `autopilot` mode mixins. Contract details: `$HOME/.claude/multi-agent-refs/phases/phase-0-init.md` Step 6 (local branch) + `$HOME/.claude/multi-agent-refs/phases/phase-2-planning.md` Step 5 (autopilot gate skip + safety classifier).
 ## Required: outward-facing payload contracts
 
 Before writing anything outward-facing  -  PR body, Jira comment, Confluence page, closing report  -  load `$HOME/.claude/multi-agent-refs/payload-contracts.md`. It names the canonical section set for each payload, the markup dialect per surface (PR body is Markdown, Jira is wiki markup  -  mixing them is a defect), and the token/duration numbers the closing report must carry. Improvising a payload shape from memory is the most common failure of the short modes.

package/pipeline/commands/multi-agent/resume-local/SKILL.md

@@ -12,7 +12,7 @@ You already did the work locally  -  wrote code on the current branch and maybe
 
 ## When to use it
 
-- You ran `dev-local` / `local` (which skip Review + Test) and now want the full quality tail on the same branch.
+- You ran `:local` and answered Short (which skips Review + Test) and now want the full quality tail on the same branch.
 - You hand-coded or hand-tested a change and want review + build/test + PR + Jira write-up without re-running dev.
 - You want the "reviewed, built, tested, PR'd, documented on Jira" finish with a single command.
 
@@ -47,7 +47,7 @@ Phases 1-3 (Analysis / Planning / Dev) are skipped by design  -  `ship` treats t
 1. **Project + branch:** detect project (cwd), current branch (`git branch --show-current`). No worktree; work stays on the current branch.
 2. **Base + diff:** resolve base branch in order: `--base <arg>` → `figma-config.project.baseBranch` → `develop` → the branch's upstream/merge-base. The **work under review** is `git diff <base>...HEAD` PLUS uncommitted working-tree changes (`git status`). Abort with a clear message if the diff is empty (`ERR: no local work to finish on <branch> vs <base>`).
 3. **Task binding:** Jira id from the `--`/positional arg, else parse the branch name (`bugfix/PROJ-XXXX` / `feature/PROJ-XXXX`); `taskType` inferred from the diff (bugfix/feature/refactor/chore) for the report wording. GitHub issue `#N` from branch/arg when present.
-4. **Prior state (optional):** if an `agent-state.json` / tracker-state exists for this branch (left by a prior `dev-local`/`local` run), load its analysis summary + Jira/issue binding to enrich the report; otherwise synthesize a minimal state over the diff. Never require a prior full-pipeline run.
+4. **Prior state (optional):** if an `agent-state.json` / tracker-state exists for this branch (left by a prior `:local` run), load its analysis summary + Jira/issue binding to enrich the report; otherwise synthesize a minimal state over the diff. Never require a prior full-pipeline run.
 5. Persist state under `.claude/logs/multi-agent/{project}/{taskId}/` (same as `--local`).
 
 ## Phase execution (reuse the existing phase contracts)

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

@@ -59,8 +59,8 @@ Run every step automatically:
 ```
 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 + 55 sub-command skills)
-Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 55 specs as refs + 8 agent TOML)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 51 sub-command skills)
+Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 51 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)
@@ -166,7 +166,7 @@ If nothing is stale → report "All targets up to date" and stop.
 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 55 sub-command specs become reference files, because Codex silently truncates
+- the 51 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
@@ -480,25 +480,25 @@ 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 55 specs as reference files rather than as peer skills, via Step 2b -  see
+same 51 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` |
 
-**55 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**51 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
 analysis, analysis-resolve, autopilot, build-optimize, channels,
-complaint-analysis, create-jira, design-check, dev, dev-autopilot, dev-local,
-dev-local-autopilot, diff-explain, 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, test-dark-mode,
-test-dynamic-type, test-screenshots, testflight-validation, uninstall, update
+complaint-analysis, create-jira, design-check, diff-explain, 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,
+test-dark-mode, test-dynamic-type, test-screenshots, testflight-validation,
+uninstall, update
 ```
 
 **NOT synced**: `$HOME/.claude/multi-agent-refs/*`  -  lazy-load references, Claude Code specific

package/pipeline/multi-agent-refs/channels/jira.md

@@ -20,6 +20,13 @@ Every Jira comment posted by this adapter follows the same section order. Sectio
 
 **`summary`**  -  2-5 sentences in `outputLanguage`. What changed, why, and the user-visible impact. No "we", no marketing tone. Past tense (the work is done at the time the comment goes up).
 
+**Visual evidence inside these two sections.** When `state.visualEvidence` carries artefacts, they render INSIDE `summary` and `test_scenarios` - never as a fourth section, which the fixed section order forbids. Upload first (`jira-attach.sh <issue> <file>...`), then reference by the returned filename:
+
+- `summary`, after its sentences: one line naming the pair in `outputLanguage` (`Düzeltme öncesi / Düzeltme sonrası`), then the thumbnails on the next line - `!<file>-before.png|thumbnail! !<file>-after.png|thumbnail!`.
+- `test_scenarios`, under the scenario the recording demonstrates: `!<file>-flow.mp4!` plus one line stating the tier used.
+
+A `gaps[]` entry prints its reason on the line where the artefact would have been (`Düzeltme öncesi: ticket'ta görsel yok`). Never an empty thumbnail, never a silent omission. Contract: `$HOME/.claude/multi-agent-refs/features/visual-evidence.md`.
+
 **`test_scenarios`**  -  Given/When/Then numbered list. One scenario per acceptance criterion. The heading and scenario text are rendered in `outputLanguage` at write-time; the template itself (this file) shows the English skeleton:
 
 ```markdown

package/pipeline/multi-agent-refs/channels/pr.md

@@ -14,9 +14,10 @@ The PR description targets code reviewers  -  it stays technical. Every adapter
 | 2 | `changes` | `## Değişiklikler` | `## Changes` | always |
 | 3 | `architecture` | `## Mimari Kararlar` | `## Architecture Decisions` | when a non-trivial design choice was made |
 | 4 | `verification` | `## Doğrulama` | `## Verification` | always |
-| 5 | `risk` | `## Risk ve Güvenlik` | `## Risk and Security` | when `state.diffRisk.signals` carries a high-stakes signal (`security_path`, `migration`, `public_api`, `no_test_change`, `test_lines_removed`) |
-| 6 | `dependencies` | `## Bağımlılıklar` | `## Dependencies` | when deps added/removed/bumped |
-| 7 | `related` | `## İlgili` | `## Related` | always (Jira/issue ref; never `Closes/Fixes`) |
+| 5 | `visuals` | `## Görsel Kanıt` | `## Visual Evidence` | when `state.visualEvidence.required` |
+| 6 | `risk` | `## Risk ve Güvenlik` | `## Risk and Security` | when `state.diffRisk.signals` carries a high-stakes signal (`security_path`, `migration`, `public_api`, `no_test_change`, `test_lines_removed`) |
+| 7 | `dependencies` | `## Bağımlılıklar` | `## Dependencies` | when deps added/removed/bumped |
+| 8 | `related` | `## İlgili` | `## Related` | always (Jira/issue ref; never `Closes/Fixes`) |
 
 ### Section content rules
 
@@ -62,6 +63,18 @@ Multi-repo PRs (one PR per repo) emit verification commands for that repo's stac
 - Rollback: feature flag <name> | git revert <sha> | none, and why
 ```
 
+**`visuals`**  -  only when `state.visualEvidence.required`. The images live on the Jira issue as attachments; this section exists so a reviewer opening the PR knows they are there and what each one shows. Filenames, not raw URLs - a Jira attachment URL is auth-gated and renders as a broken image for anyone reading the PR outside a Jira session.
+
+```markdown
+## Visual Evidence
+
+- Before: `<before-filename>` (attached to PROJ-XXXXX)
+- After: `<after-filename>` (attached to PROJ-XXXXX)
+- Flow video: `<flow-filename>`, tier <N> (attached to PROJ-XXXXX)
+```
+
+Every `state.visualEvidence.gaps[]` entry becomes its own line with the reason instead of a filename (`- Before: none  -  the ticket carries no image attachment`). Phase 6 Step 3 blocks on a required artefact that is neither listed nor explained. Contract: `$HOME/.claude/multi-agent-refs/features/visual-evidence.md`.
+
 **`dependencies`**  -  only when `Package.swift` / `Podfile` / `build.gradle` / `package.json` changed. Each entry: `package@old → new  -  reason`.
 
 **`related`**  -  flat list, plain text. Examples:

package/pipeline/multi-agent-refs/cross-cli-contract.md

@@ -6,18 +6,18 @@
 
 ---
 
-## 1. Command Inventory (55 files, 51 live commands)
+## 1. Command Inventory (51 commands)
 
 ```
 analysis, analysis-resolve, autopilot, build-optimize, channels,
-complaint-analysis, create-jira, design-check, dev, dev-autopilot, dev-local,
-dev-local-autopilot, diff-explain, 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, test-dark-mode,
-test-dynamic-type, test-screenshots, testflight-validation, uninstall, update
+complaint-analysis, create-jira, design-check, diff-explain, 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,
+test-dark-mode, test-dynamic-type, test-screenshots, testflight-validation,
+uninstall, update
 ```
 
 Categories:
@@ -25,15 +25,12 @@ Categories:
 - **Interactive pickers** (single-purpose, not modes): `jira`, `issue`
 - **Issue generator** (one-shot, no worktree, asks type Task/Bug/Story, hard approval gate before create): `create-jira`
 - **Pipeline entries**: `autopilot`, `local`, `local-autopilot` (plus the bare `/multi-agent` in the dispatcher). Depth is not a command: `/multi-agent` and `local` ask Full or Short at Phase 0 Step 7.5; the two autopilot entries never ask and always run Full.
-- **Retired stubs** (v16.0.0, deleted next minor  -  they print a redirect and run no phase): `dev`, `dev-local` redirect to the picker entries with Short; `dev-autopilot`, `dev-local-autopilot` have no equivalent, because fast-plus-unattended no longer exists
 - **Tail modes** (run the pipeline tail over already-done local work): `resume-local`
 - **Ops commands** (one-shot, no worktree): `status`, `log`, `kill`, `steer`, `purge`, `uninstall`, `resume`, `review`, `review-jira`, `review-issue`, `analysis`, `analysis-resolve`, `complaint-analysis`, `build-optimize`, `channels`, `scan`, `search`, `diff-explain`, `garbage-collect`, `graph`, `prune-logs`, `prune-prompts`
 - **Local audits** (worktree only to build; no commit, push, PR or channels): `design-check`, `testflight-validation`, `ios-coding-standard`. `testflight-validation` additionally never invokes `altool --upload-app`  -  a validation run must not be able to ship a build by accident.
 - **Meta-ops**: `setup`, `sync`, `update`, `help`, `refactor`, `test`, `stack`, `manual-test`, `language`
 - **Routines** (user-defined routine registry; the routines they create are local-only and never synced): `save`, `routines`, `forget`
 
-The count is 55 files and 51 live commands until the four stubs are deleted, at which point both numbers become 51. A stub is still installed and still invocable, so counting it as absent would be wrong; counting it as a command would be worse.
-
 > **Inventory drift is a contract violation.** Adding a slash command under `pipeline/commands/multi-agent/` without updating this list + its counterpart Copilot dir (`pipeline/skills/shared/core/multi-agent-<cmd>/`) is a merge blocker. `smoke-commands-skills-parity.sh` enforces command ↔ skill directory parity; `smoke-cross-cli-behavior.sh` enforces behavior parity. This doc is the authoritative command list  -  bump the count + table together.
 
 ### 1.1 Figma / component work (plugin-based on Claude Code; NOT parity-enforced)
@@ -244,6 +241,7 @@ argument-hint: "<input hint>"
 
 | Concept | Claude Code | Copilot CLI | Codex CLI |
 |---|---|---|---|
+| Print the registration calls | `phase-tracker.sh tiles` (emits the TaskCreate list) | `phase-tracker.sh tiles` (emits the reprint instruction) | `phase-tracker.sh tiles` (emits the update_plan payload) |
 | Register a phase | `TaskCreate` tool call with subject/description | `phase-tracker.sh add <N> <name>` | `update_plan` step, `status: pending` |
 | Mark a phase in-progress | `TaskUpdate` → `in_progress` | `phase-tracker.sh update <N> in_progress` | `update_plan` step → `in_progress` |
 | Mark a phase complete | `TaskUpdate` → `completed` | `phase-tracker.sh update <N> completed` | `update_plan` step → `completed` |

package/pipeline/multi-agent-refs/features/visual-evidence.md

@@ -0,0 +1,172 @@
+# Visual evidence  -  before/after screenshots and the UI flow video
+
+A UI fix that reads as three changed files in a diff is not reviewable. The
+reviewer cannot see what was wrong, and the tester cannot see what to look for.
+This contract makes the pipeline carry the picture: the state the reporter saw,
+the state the fix produces, and where possible a recording of the flow running.
+
+The artefacts live as **Jira attachments** and are referenced from two places -
+the Phase 7 Jira comment, where the picture belongs next to the work summary and
+the test scenarios, and the PR body, which tells the reviewer they exist.
+
+Consumers: Phase 3 (capture), Phase 5 (video, preferred host), Phase 6 (blocker),
+`channels/jira.md` and `channels/pr.md` (render). Gate: `smoke-visual-evidence.sh`.
+
+## 1. When it is required
+
+Decided mechanically from `taskType` plus the changed-file list, never from the
+model's reading of the task. A file counts as UI by stack:
+
+| Stack | UI file test |
+|---|---|
+| iOS | `.swift` declaring `: View`, `: ViewController`, or under a `Views/` path |
+| Android | `.kt` with `@Composable`, or declaring `: Activity` / `: Fragment` |
+| Web | `.tsx` / `.jsx` / `.vue` / `.svelte` |
+
+| Case | Before | After | Video |
+|---|---|---|---|
+| `taskType` is `bugfix` AND a UI file changed | required | required | when a tier allows |
+| Design work: `taskType` is `component`, or Figma was referenced, or a UI file was **added** | not applicable | required | when a tier allows |
+| Anything else | - | - | - |
+
+`state.visualEvidence.required` records the verdict and which rule produced it.
+Nothing about this section is optional-by-omission: when it is required and an
+artefact is absent, the absence is written down with its reason (section 5).
+
+## 2. Before  -  the reporter's screenshot, or nothing
+
+**The pipeline does not build the old state to photograph it.** Reproducing a
+pre-fix screen costs a second build and a second launch on every UI bug, to
+recreate evidence the reporter has usually already attached.
+
+So: Phase 0 already fetches the issue. Any image attachment on it (`.png`,
+`.jpg`, `.jpeg`, `.gif`, `.heic`) is downloaded to `$WORKTREE/.pipeline/evidence/`
+and recorded as `state.visualEvidence.before[]`. More than one is kept - a bug
+reported on two platforms has two.
+
+No image on the ticket means no "before". Record the gap
+(`before_missing: "ticket carries no image attachment"`) and continue. The
+section still renders, saying so.
+
+## 3. After  -  Phase 3, not Phase 5
+
+Phase 5 is the natural home: the simulator is already up. It is also **dropped by
+every `autopilot` and `--local` entry** (`phase-5-test.md` TLDR), so a capture
+that lives only there produces nothing for unattended runs - which are exactly
+the runs where nobody watched the screen.
+
+The capture therefore happens in **Phase 3, after the build+test gate passes**,
+which is in every mode's phase set. Phase 5 may add richer evidence on top; it is
+never the only source.
+
+```bash
+bash $HOME/.claude/scripts/capture-evidence.sh after \
+  --task "$TASK_ID" --platform "$PLATFORM" --label "<screen-slug>"
+```
+
+The script boots the device if needed, launches the built app, cleans the status
+bar (`ios_status_bar preset:clean` / the Android equivalent) so the frame carries
+no clock, carrier or battery noise, captures at device resolution, downscales to
+at most 1242px wide, and writes
+`$WORKTREE/.pipeline/evidence/<TASK_ID>-<label>-after.png`.
+
+A clean status bar is not cosmetic: without it two captures of the same screen
+differ by the clock, which makes every "after" look like a change.
+
+## 4. Video  -  three tiers, resolved once per repo
+
+The flow source, in order: a UI test flow written on the ticket wins; otherwise
+the Phase 5 test scenarios are the flow. Human-written beats generated, the same
+rule the "before" follows.
+
+The tier is probed once and stored in `state.visualEvidence.videoTier`:
+
+| Tier | Condition | Mechanism |
+|---|---|---|
+| 1 | The repo has a UI test target (XCUITest / Espresso) **and** it can be seeded with test data | Run that test, record the screen for its duration. Most faithful, and it is a test that already runs in CI |
+| 2 | A runnable build exists | Drive the flow with `mcp__multi-agent-toolkit__agent_run_steps` and record with `ios_record_video` / `android_record_screen`. **No test target needed** |
+| 3 | No runnable build (library / SPM package / backend) | Skip, with the reason recorded |
+
+Tier 2 is why "can every repo do this" answers yes in practice: any app that can
+be launched can be driven. A repo without a UI test target loses fidelity, not
+the recording.
+
+Preferred host is **Phase 5** - the device is already up and a human is present
+to confirm the flow is the right one. In a mode without Phase 5, tier 2 runs at
+the end of Phase 3 instead. Tier 1 always runs where the test runs.
+
+Duration is capped by `visualEvidence.maxVideoSeconds` (default 60), read via
+`capture-evidence.sh limits` so the number lives in one place rather than in two
+documents. A flow that needs longer is not a review artefact, it is a debugging
+session.
+
+`visualEvidence.enabled` turns the whole feature off - capture, upload, both
+render sections and the Phase 6 blocker with it.
+
+## 5. Size, and what happens when it does not fit
+
+Jira's attachment ceiling is an instance setting, so it is a preference:
+`visualEvidence.maxAttachmentMb` (default `10`).
+
+Order of attempts, each one recorded:
+
+1. Upload as captured.
+2. On `413` or a local size overrun: re-encode. Video drops to 720p and a lower
+   bitrate; PNG converts to JPEG at quality 80. **Reducing quality is allowed;
+   dropping the artefact is not.**
+3. Still over: replace the video with a four-frame contact sheet (start, two
+   midpoints, end) as a single PNG, and say in the caption that the recording
+   exceeded the limit.
+
+Never silently attach nothing.
+
+## 6. Rendering
+
+### Jira comment (`channels/jira.md`)
+
+The comment's section order is fixed and nothing may be inserted between the
+three sections. The evidence goes **inside** two of them:
+
+- `summary`  -  after the summary sentences, the before/after pair as a Jira wiki
+  thumbnail row: `!<TASK>-<label>-before.png|thumbnail! !<TASK>-<label>-after.png|thumbnail!`
+  preceded by one line naming which is which in `outputLanguage`
+  (`Düzeltme öncesi / Düzeltme sonrası`).
+- `test_scenarios`  -  the flow video attached under the scenario it demonstrates:
+  `!<TASK>-flow.mp4!`, one line stating the tier used.
+
+Missing artefacts print their reason on the same line, never an empty frame.
+
+### PR body (`channels/pr.md`)
+
+A `visuals` section whose job is to tell the reviewer the evidence exists and
+where it lives - the images themselves stay on the ticket:
+
+```markdown
+## Görsel Kanıt
+
+- Düzeltme öncesi: <before-filename> (PROJ-123 ekinde)
+- Düzeltme sonrası: <after-filename> (PROJ-123 ekinde)
+- Akış videosu: <flow-filename>, tier <N> (PROJ-123 ekinde)
+```
+
+## 7. Blocker
+
+When section 1 says required and `state.visualEvidence` carries neither an
+artefact nor a recorded reason for its absence, **Phase 6 Step 3 blocks** - the
+same shape as the `risk` section blocker. A recorded reason is enough to pass:
+the gate is against silence, not against an honest "no image on the ticket".
+
+## 8. State
+
+```json
+"visualEvidence": {
+  "required": true,
+  "requiredBy": "bugfix + ui-file-changed",
+  "platform": "ios",
+  "before": [{"file": "...", "source": "ticket", "jiraFilename": "...", "url": "..."}],
+  "after":  [{"file": "...", "capturedAt": "phase-3", "jiraFilename": "...", "url": "..."}],
+  "videoTier": 2,
+  "video": {"file": "...", "seconds": 41, "jiraFilename": "...", "url": "..."},
+  "gaps": [{"what": "before", "reason": "ticket carries no image attachment"}]
+}
+```