@mmerterden/multi-agent-pipeline 14.1.1 → 14.2.2

package/CHANGELOG.md

@@ -16,6 +16,168 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [14.2.2] - 2026-08-04
+
+### Added
+
+- **`localization-reuse-map` skill** added to `shared/external` — a per-screen
+  localization-reuse map that ties new/legacy/CMS translation keys together,
+  with follow-up fixes for placeholder rendering, snapshot staleness, and the
+  three gates its initial commit left red.
+- **`docs/ecosystem.md`** — a detailed diagram of how this repo, the
+  `multi-agent-plugins` marketplace, and `dev-toolkit-mcp` compose at install
+  time and run time. `docs/architecture.md` cross-links it.
+- **Turkish README (`README.tr.md`)**, cross-linked from `README.md`.
+- Jira intake now surfaces the **parent issue's description** as a
+  confirmable candidate when the child issue's own description is empty.
+- `payload-contracts` reference doc, consolidating the required-reading list
+  for Phase 6 and 7.
+
+### Fixed
+
+- Corrected stale 44/43-command counts to the real 49 across README,
+  `cross-cli-contract.md`, and both sync/update `SKILL.md` copies; fixed a
+  hardcoded "42 command specs" log line in `install/codex.mjs` to count the
+  actual source tree instead.
+- **`audit-log-rotate.sh` could delete the archive it had just created.**
+  `gzip` preserves the source file's mtime by default, so rotating log
+  content already older than `KEEP_DAYS` produced a `.gz` that inherited
+  that old mtime - and the very next line's retention sweep (`find -mtime
+  +$KEEP_DAYS -delete`) deleted it in the same run, before it was ever read.
+  The archive's mtime is now reset to rotation time, so retention counts
+  from when it was archived, not from the age of the content inside it.
+- The mode banner claimed pickers stay English when they didn't - language +
+  dialect resolution fixed.
+- The cost tracker now reads the same state file `phase-tracker.sh` writes.
+- Jira conversion table pipes are now escaped; Intake warnings render at h2.
+- Copilot mode skills carried a stale review claim and missing payload
+  pointers - corrected.
+- 18 cross-script drift and edge-case bugs resolved from code review.
+- Markup dialect is now chosen per surface for channel posts; the Jira table
+  heading-conversion bug fixed.
+- `localization-reuse-map`: empty-cell placeholder is now a single dash; a
+  stale snapshot no longer reads as an unauthored key.
+
+## [14.2.1] - 2026-07-30
+
+### Changed
+
+- **`testflight-validation` merged into a new `/multi-agent:store-ready`, and the
+  Android side brought to parity.** The iOS archive audit existed twice with
+  identical arguments  -  `ios_app_store_audit({archive_path, rules: "all"})` in the
+  command's Gate 1 and again inside `sim-test.md`'s `store-ready` scenario. Two
+  copies of one call is how the second door grew with no Gate 2, no Gate 3 and no
+  Android equivalent. There is now one implementation.
+  Gates are symmetric per platform, because the failure modes are: a malformed
+  package, a package the store itself refuses, and a policy a human enforces.
+
+  | Gate | iOS | Android |
+  |---|---|---|
+  | 1 Static | `ios_app_store_audit`, 18 rules | `android_apk_audit` + `google-play-compliance`, 21 rules |
+  | 2 Authoritative | `altool --validate-app` | `SKIPPED` |
+  | 3 Policy | `app-store-review` vs source | `play-store-review` vs source |
+
+  Gate 2's asymmetry is reported as an asymmetry rather than smoothed over: Play's
+  authoritative check exists only server-side, through a Publishing API draft edit,
+  and the pipeline ships no client for it. An Android run therefore clears at most
+  2 of 3 and never prints `passed`. `bundletool validate` is Gate 1 and is not
+  promoted to fill the hole.
+  The running-app sweep became Step A rather than a separate errand  -  a build can
+  be structurally perfect and still ship an unreadable screen  -  and it degrades to
+  `SKIPPED (no booted device)` instead of halting the package validation.
+
+  Nothing was removed. `testflight-validation` is a thin iOS-pinned alias (removing
+  a command is a breaking change to the slash-command surface), and
+  `test "store-ready"` still resolves, now as a hand-off. `sim-test.md` keeps only
+  the pointer, so a dark-mode run no longer loads altool and credential-tier prose
+  it never needs.
+
+### Added
+
+- **Four fixed-scenario `test-*` commands.** `/multi-agent:test-dark-mode`,
+  `:test-accessibility`, `:test-dynamic-type` and `:test-screenshots [locale]` pin a
+  scenario the quoted-tag form made you remember and quote. Typing `test-` now
+  autocompletes the matrix list instead of returning a single entry whose tags live
+  only in the help text. The scenario-tag form is unchanged and not deprecated -
+  each command is an alias for it, delegating to the same `sim-test.md`, so there is
+  one implementation and no forked logic. Same pattern the mode aliases already use
+  (`:dev-autopilot` = `--dev autopilot`).
+  `screenshot <lang>` became `test-screenshots [locale]` rather than
+  `test-screenshot-tr`: the locale is a parameter, and freezing one language into a
+  command name buys one command per language. `store-ready` deliberately got no
+  alias - it takes an optional archive path, and its 18-rule audit is the same one
+  `/multi-agent:testflight-validation` runs as its first gate, so the alias would
+  have advertised a second door onto a duplicate.
+
+### Fixed
+
+- **Copilot's `purge` could not see a single worktree.** It discovered them with
+  `find {repo}/.worktrees/ -name "agent-state.json"`, and no worktree carries that
+  file: Phase 0 writes state to `$HOME/.claude/logs/multi-agent/{project}/{task-id}/`.
+  Verified on a repo with two live task worktrees  -  the marker scan returns zero
+  while `purge.sh`'s own directory enumeration finds both. So the skill reported
+  "nothing to purge" as success with real worktrees on disk. The Claude Code command
+  had already been fixed by delegating to `purge.sh`; the Copilot mirror never
+  received that fix, which is the second time a repaired Claude-side surface left its
+  Copilot counterpart behind in this release.
+  It now delegates to the script and explicitly forbids re-introducing a
+  marker-file scan.
+- **The stale log location survived in four more places** after `clear-logs` was
+  redirected. `shared/core/multi-agent` told Phase 0 to create `agent-log.md` and
+  `agent-state.json` inside `.worktrees/PROJ-{id}/`, told `:resume` to look for state
+  there, and printed that path as the report location; `phase-0-init` said "create log
+  dir" without naming one, 49 lines above the line that does. All four now name
+  `$HOME/.claude/logs/multi-agent/{project}/{task-id}/`, the path the tracker,
+  `prune-logs.sh` and `:resume` actually read.
+  `status` and `log` keep their worktree scan as a legacy fallback: it finds nothing
+  on a current tree, but it is harmless and would still serve an old one.
+
+- **`clear-logs` scanned a path nothing writes to, and help advertised it as a
+  slash command that does not exist.** It looked for
+  `.worktrees/PROJ-*/agent-log.md` and `agent-state.json`; Phase 0 has written both
+  to `$HOME/.claude/logs/multi-agent/{project}/{task-id}/` since the layout moved.
+  Against the current tree the scan matches zero files, so the op reported "logs
+  cleared, deleted 0" as success while every real log stayed on disk  -  worse than a
+  missing command, because it reads as done. There was also no `clear-logs` command
+  directory, so the `/multi-agent:clear-logs` entry in the Copilot help pointed at a
+  slash command that was never installed.
+  The name is kept as a redirect to `prune-logs` rather than deleted, so an existing
+  invocation lands somewhere correct. `prune-logs` and `garbage-collect` now appear
+  in the Copilot help, matching the Claude Code side. This is the `finish` → `ship`
+  class of drift the inventory gate's own comment describes, in the files that gate
+  does not parse.
+- **`sim-test.md` advertised two scenarios it never implemented.** `"biometric"` and
+  `"performance"` sat in the activation block with no implementation section, so
+  reaching either fell through to the general sweep and was reported as the scenario
+  asked for. Neither can be built symmetrically today: biometric has `ios_biometric`
+  and no Android counterpart, launch timing has `android_launch_time` and no iOS
+  counterpart, and the file auto-detects platform  -  so each would work on one
+  platform and silently do nothing on the other. Both rows are withdrawn with the
+  reason recorded in place, rather than shipped as half-features or left advertised.
+  Advertised scenarios and implemented sections now match one to one.
+- **`help` never documented two shipped commands.** `testflight-validation` and
+  `ios-coding-standard` existed in the tree, installed correctly, and appeared in no
+  block of `help/SKILL.md` in either language - `ios-coding-standard` was reachable
+  only because it also sat in `prefs.global.routines`, i.e. it read as a personal
+  routine rather than a first-party command. Both are now in the EN and TR Post-Hoc
+  sections. A command absent from help is a command nobody runs.
+- **Rule count drifted between the two language blocks.** The TR block advertised a
+  17-rule iOS store audit against the EN block's 18 and `ios_app_store_audit`'s
+  actual 18. The TR reader was being given a number no code produces.
+
+### Changed
+
+- **`DESC_CEILING` 78000 -> 81000**, with the paired pin in
+  `test/context-budget-gate.test.mjs` moved in the same commit, as that test
+  requires. Not a bump to silence a red gate: at 78000 the surface had **16 bytes**
+  of headroom, so any new command failed regardless of how tersely it was described,
+  while the gate's own average check sat at 320 against its 420 ceiling - the signal
+  that the tree grew rather than that descriptions are padded. The alternative was
+  shaving routing text off eight unrelated `shared/external` skills to fund four
+  commands, which trades a real capability for a cosmetic number. Both the gate and
+  the test now carry the ceiling's history inline so the next raise has to argue for
+  itself. Cost is honest: ~470 always-on tokens per run.
+
 ## [14.1.1] - 2026-07-30
 
 Three defects that all shared one shape: a name written in one place and read in

package/README.md

@@ -6,10 +6,14 @@
 [![Zero Dependencies](https://img.shields.io/badge/dependencies-0-brightgreen)](https://github.com/mmerterden/multi-agent-pipeline/blob/main/package.json)
 [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/mmerterden/multi-agent-pipeline/badge)](https://scorecard.dev/viewer/?uri=github.com/mmerterden/multi-agent-pipeline)
 
+🇹🇷 Türkçe: [README.tr.md](./README.tr.md)
+
 An 8-phase AI development pipeline for **Claude Code**, **Copilot CLI** and **Codex CLI**. Drives a Jira issue or GitHub URL to a merged PR in one command - analysis → plan → TDD → review → test → commit → PR - with multi-repo orchestration, a plan-approval gate, CLI-aware parallel review, and store-compliance checks. Component and Figma-to-code work is dispatched to the per-stack marketplace plugins (iOS/SwiftUI, Android/Compose) rather than bundled, so component skills live in one place.
 
 Runs natively on Claude Code, Copilot CLI and Codex CLI. macOS / Linux / Windows. Zero runtime dependencies.
 
+📐 **[Architecture diagrams](./docs/architecture.md)** - the 8-phase flow, operating modes, review/triage, Figma subphases, component layout. **[Ecosystem diagram](./docs/ecosystem.md)** - how this repo, the `multi-agent-plugins` marketplace and `dev-toolkit-mcp` compose.
+
 ## Quick Start
 
 ```bash
@@ -52,7 +56,7 @@ One command runs 8 phases, with a gate between the risky ones:
 
 Under the hood: each task runs in its own **git worktree** (or the current branch with `:local`), commits use the **git identity routed from the repo's origin URL**, and **multi-repo** tasks get per-repo worktrees plus an integration build. Tokens stay in the OS keychain; nothing is committed or logged. `/multi-agent:review` can also review an existing GitHub/Bitbucket PR - per-finding inline comments anchored to `file:line` + an explicit Approve / Needs-Work state.
 
-The discipline behind all of this - bounded loops, evidence gates, token-budgeted phase docs, immutable tests, fresh-context handoffs - is catalogued in [docs/engineering.md](./docs/engineering.md). The full feature list lives in [docs/features.md](./docs/features.md).
+The discipline behind all of this - bounded loops, evidence gates, token-budgeted phase docs, immutable tests, fresh-context handoffs - is catalogued in [docs/engineering.md](./docs/engineering.md). The full feature list lives in [docs/features.md](./docs/features.md). How this repo, the `multi-agent-plugins` marketplace, and the `dev-toolkit-mcp` server compose at install time and at run time is diagrammed in [docs/ecosystem.md](./docs/ecosystem.md).
 
 ## Modes
 
@@ -66,7 +70,7 @@ The discipline behind all of this - bounded loops, evidence gates, token-budgete
 | Audit | `/multi-agent:design-check` | Mock-mode vs Figma conformance, local-only |
 | Audit | `/multi-agent:testflight-validation` | Pre-submission gates for a TestFlight build: static archive audit → Apple's `altool --validate-app` → Review-Guidelines check. Validates only, never uploads |
 
-Helpers: `setup`, `status`, `resume #N`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `create-jira`, `save`, `routines`, `forget`. 44 commands in all  -  full list: `/multi-agent:help`.
+Helpers: `setup`, `status`, `resume #N`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `create-jira`, `save`, `routines`, `forget`. 49 commands in all  -  full list: `/multi-agent:help`.
 
 ## Stacks
 
@@ -80,17 +84,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 44 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 49 commands.
 
 | Tool | Flag | What it installs |
 |---|---|---|
 | Claude Code | `--claude` (default) | slash commands + skills + agents + `PreToolUse` secret-scan hook |
-| Copilot CLI | `--copilot` | instructions + 44 sub-command skills + scripts |
-| Codex CLI | `--codex` | one router skill + 43 specs as refs + 8 agent TOML + `AGENTS.md` block + `codex mcp add` |
+| Copilot CLI | `--copilot` | instructions + 49 sub-command skills + scripts |
+| Codex CLI | `--codex` | one router skill + 49 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 43.** Codex assembles every discovered skill's name
+**Why Codex gets one skill and not 49.** 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

@@ -0,0 +1,143 @@
+# @mmerterden/multi-agent-pipeline
+
+[![GitHub Release](https://img.shields.io/github/v/release/mmerterden/multi-agent-pipeline?color=blue)](https://github.com/mmerterden/multi-agent-pipeline/releases)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![Node.js](https://img.shields.io/badge/Node.js-18%20%7C%2020%20%7C%2022-green)](https://nodejs.org)
+[![Zero Dependencies](https://img.shields.io/badge/dependencies-0-brightgreen)](https://github.com/mmerterden/multi-agent-pipeline/blob/main/package.json)
+[![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/mmerterden/multi-agent-pipeline/badge)](https://scorecard.dev/viewer/?uri=github.com/mmerterden/multi-agent-pipeline)
+
+🇬🇧 English: [README.md](./README.md)
+
+**Claude Code**, **Copilot CLI** ve **Codex CLI** için 8 fazlı bir AI geliştirme pipeline'ı. Bir Jira issue'sunu veya GitHub URL'sini tek komutla merge edilmiş bir PR'a dönüştürür - analiz → plan → TDD → review → test → commit → PR - çoklu-repo orkestrasyonu, bir plan-onay kapısı, CLI-farkında paralel review ve store-uyumluluk kontrolleriyle birlikte. Component ve Figma-to-code işleri paket içine gömülmek yerine stack başına marketplace plugin'lerine (iOS/SwiftUI, Android/Compose) devredilir, böylece component skill'leri tek bir yerde yaşar.
+
+Claude Code, Copilot CLI ve Codex CLI üzerinde native çalışır. macOS / Linux / Windows. Sıfır runtime dependency.
+
+📐 **[Mimari diyagramları](./docs/architecture.md)** - 8 faz akışı, çalışma modları, review/triage, Figma subphase'leri, component yapısı. **[Ekosistem diyagramı](./docs/ecosystem.md)** - bu repo, `multi-agent-plugins` marketplace'i ve `dev-toolkit-mcp`'nin nasıl bir araya geldiği.
+
+## Hızlı Başlangıç
+
+```bash
+# public registry'den (auth gerekmez)
+npx @mmerterden/multi-agent-pipeline install --all   # Claude Code + Copilot CLI + Codex CLI
+
+# sonra, bir kere:
+/multi-agent:setup          # keychain token taraması + git kimliği + varsayılan stack
+```
+
+Bir görev çalıştır - girdi tipi otomatik algılanır:
+
+```bash
+/multi-agent "PROJ-1234"                              # Jira id → çek, planla, geliştir
+/multi-agent "https://github.com/org/repo/issues/42"  # GitHub issue URL'i
+/multi-agent "my-app#42"                              # repo + issue numarası
+/multi-agent "fix dark-mode contrast on LoginView"    # serbest-metin bug/özellik
+/multi-agent:jira                                     # açık Jira issue'larını gez → seç
+/multi-agent:issue                                    # atanmamış GitHub issue'larını gez → seç
+```
+
+Her girdi aynı kısa intake'ten geçer - **hesap → (repo) → maturity kontrolü → dev-context** - sonra Phase 0'a girer. Bir Jira id'si veya GitHub URL'i hiçbir kod yazılmadan *önce* çekilir ve maturity-kontrol edilir; serbest-metin bu çekimi atlayıp doğrudan planlamaya geçer. Çoklu-repo görevleri dev-context adımında ekstra repo ekler.
+
+Onayları atlamak için `autopilot`, hızlı dev-only yol için `--dev`, ya da worktree olmadan mevcut branch'te çalışmak için `--local` ekle (örn. `/multi-agent:autopilot "PROJ-1234"`).
+
+Sonra `/multi-agent:update` ile güncelle. Kaldırmak için (tokenlar korunur) `npx @mmerterden/multi-agent-pipeline uninstall`.
+
+## Nasıl çalışır
+
+Tek komut 8 fazı çalıştırır, riskli olanlar arasında bir kapı ile:
+
+- **0 · Init** - girdiyi ayrıştır (Jira id / GitHub URL / serbest metin), hesap + repo(lar) seç, issue'yu çek, maturity kontrolü yap.
+- **1 · Analysis** - stack'i tespit et, codebase'i tara, etkiyi haritala (Opus).
+- **2 · Plan** - bir görev kırılımı yaz ve koda dokunmadan önce **onayın için dur**.
+- **3 · Dev** - TDD: başarısız test → kod → yeşil, repo'nun stiline + aktif stack skill'lerine uyarak.
+- **4 · Review** - önce deterministik kapılar (build / lint / test / secret-scan) geçmeli, sonra bir **CLI-farkında paralel review** - Claude Code 2 model çalıştırır (Fable + Sonnet), Copilot CLI 3 (GPT-5.4 + Opus + Sonnet) - ve bir **Fable triage** sadece aksiyon alınabilir bulguları tutar; blocker'lar Phase 3'e geri döner.
+- **5 · Test** - build + suite'i çalıştır; başarı zorunlu (sahte pass yok).
+- **6 · Commit/PR** - conventional commit, push (başarılı olmalı), bir PR aç (`Ref: #N`, asla otomatik kapatma).
+- **7 · Report** - teknik özet + test senaryolarıyla bir Jira yorumu, channels katmanından gönderilir.
+
+Perde arkasında: her görev kendi **git worktree**'sinde çalışır (ya da `:local` ile mevcut branch'te), commit'ler **repo'nun origin URL'inden yönlendirilen git kimliğini** kullanır, ve **çoklu-repo** görevleri repo başına worktree artı bir integration build alır. Tokenlar OS keychain'de kalır; hiçbir şey commit edilmez ya da loglanmaz. `/multi-agent:review` mevcut bir GitHub/Bitbucket PR'ını da review edebilir - `file:line`'a bağlı bulgu-başına inline yorumlar + açık bir Approve / Needs-Work durumu.
+
+Bunun arkasındaki disiplin - sınırlı loop'lar, kanıt kapıları, token-bütçeli faz dokümanları, değişmez testler, taze-context handoff'lar - [docs/engineering.md](./docs/engineering.md)'de kataloglanmıştır. Tam özellik listesi [docs/features.md](./docs/features.md)'te. Bu repo, `multi-agent-plugins` marketplace'i ve `dev-toolkit-mcp` sunucusunun install zamanında ve run zamanında nasıl bir araya geldiği [docs/ecosystem.md](./docs/ecosystem.md)'de diyagramlanmıştır.
+
+## Modlar
+
+| Mod | Komut | Akış |
+|---|---|---|
+| Full | `/multi-agent "task"` | Tüm 8 faz, interaktif |
+| Autopilot | `/multi-agent:autopilot "task"` | Tüm 8 faz, onaysız |
+| Dev | `/multi-agent:dev "task"` | Init → Dev → Review → Test → Commit → Report |
+| Local | `/multi-agent:local "task"` | Tam pipeline, mevcut branch (worktree yok) |
+| Ship | `/multi-agent:ship` | Lokal iş üzerinde review→test→commit→report kuyruğunu çalıştır |
+| Audit | `/multi-agent:design-check` | Mock-mode vs Figma uygunluğu, yalnızca lokal |
+| Audit | `/multi-agent:testflight-validation` | TestFlight build için pre-submission kapıları: statik archive denetimi → Apple'ın `altool --validate-app`'i → Review-Guidelines kontrolü. Yalnızca doğrular, asla yüklemez |
+
+Yardımcılar: `setup`, `status`, `resume #N`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `create-jira`, `save`, `routines`, `forget`. Toplam 49 komut - tam liste: `/multi-agent:help`.
+
+## Stack'ler
+
+Stack skill'leri [`mmerterden/multi-agent-plugins`](https://github.com/mmerterden/multi-agent-plugins) marketplace'inde versiyonlu plugin'ler olarak gönderilir. Repo başına bir stack seç:
+
+```bash
+/multi-agent:stack ios        # veya android / frontend / backend / mobile / all
+```
+
+Bu, ilgili plugin'i (+ ortak `ai-common` plugin'ini) repo'nun `.claude/settings.json`'unda etkinleştirir. Phase 1, routing için stack'i otomatik tespit eder. Yeni repo'lar varsayılan olarak iOS'tur.
+
+## Araç desteği
+
+Pipeline **Claude Code**, **Copilot CLI** ve **Codex CLI** üzerinde native çalışır - üçü de aynı `pipeline/` kaynağından kurulur ve aynı 49 komutu alır.
+
+| Araç | Bayrak | Ne kurar |
+|---|---|---|
+| Claude Code | `--claude` (varsayılan) | slash komutları + skill'ler + agent'lar + `PreToolUse` secret-scan hook'u |
+| Copilot CLI | `--copilot` | talimatlar + 49 alt-komut skill'i + script'ler |
+| Codex CLI | `--codex` | bir router skill + ref olarak 49 spec + 8 agent TOML + `AGENTS.md` bloğu + `codex mcp add` |
+
+Skill'leri stack'e göre filtrele: `--platform=ios\|android\|all`.
+
+**Codex neden 49 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
+pipeline tek bir `multi-agent` router gönderir ve alt-komut spec'lerini, okunana kadar
+hiçbir maliyeti olmayan referans dosyaları olarak tutar - aynı komutlar, aynı davranış,
+host'un gerçekten tutabildiği bir düzen.
+
+Reviewer setleri farklı çünkü mevcut modeller farklı: Claude Code 2 reviewer çalıştırır
+(Fable + Sonnet), Copilot CLI 3 (Opus + GPT-5.4 + Sonnet), Codex CLI 3 (xhigh'da
+gpt-5.6, gpt-5.4, medium'da gpt-5.6). Codex tek-vendor olduğu için üçü arasındaki
+konsensüs, iki-vendor'lu bir host'taki aynı konsensüsten daha zayıf bir kanıttır ve
+triage notu bunu belirtir.
+
+## Token'lar ve entegrasyonlar
+
+`setup` OS keychain'ini tarar ve her token'ı **mantıksal bir isimle** (örn. `jira`) gerçek keychain girdisine eşler - pipeline token'ları bu eşleme üzerinden çözer (`credential-store.sh`), böylece literal keychain isimleri hiçbir sync edilen dosyada görünmez. Token'lar keychain'de kalır (macOS Keychain / Windows Credential Manager / Linux libsecret), **asla commit edilmez ya da loglanmaz**, ve hepsi **opsiyoneldir** - pipeline Phase 0'da ihtiyaç duyduğu herhangi birini sorar.
+
+| Token | Ne için kullanılır | Faz |
+|---|---|---|
+| `jira` | issue'yu çek · rapor yorumunu gönder | 0, 7 |
+| `github` | issue'lar · PR'lar · `gh` auth | 0, 6 |
+| `bitbucket` | PR create/update (reviewer koruyarak) · diff | 6 |
+| `confluence` | analiz / wiki sayfaları yayınla | 7 |
+| `figma` + `figma_mcp` | design context çek | yalnızca analiz |
+| `fortify` | security-scan bulgu kapısı | 4 |
+| `firebase` | Firebase projeleri için Firebase config (base64 JSON) | gerektiğinde |
+| `jenkins` | CI tetikleme / durum | build / deploy |
+| `npm` | paket publish (çoğunlukla CI) | release |
+| `appstore_connect_*` | TestFlight / App Store pre-submission doğrulaması (opsiyonel, iOS) | `testflight-validation` |
+
+**Secret scan**, Claude Code'da bir `PreToolUse` hook'u olarak (bulgu halinde commit'i sert-engeller) ve diğer yerlerde bir pre-push kontrolü olarak çalışır.
+
+## Platform desteği
+
+**macOS**, **Linux** ve **Windows** (Git Bash / WSL) üzerinde çalışır. Shell ve credential erişimi platform-agnostik bir katmandan geçer - keychain otomatik olarak **macOS Keychain**, **Linux libsecret** (`secret-tool`) veya **Windows Credential Manager**'a çözülür, ve script'ler BSD ile GNU araç varyantları arasında fallback yapar. Node.js 18 / 20 / 22.
+
+## Yan repolar
+
+| Repo | Ne olduğu |
+|---|---|
+| [`mmerterden/multi-agent-plugins`](https://github.com/mmerterden/multi-agent-plugins) | Stack-başına skill toolkit'lerinin marketplace'i (iOS / Android / Frontend / Backend + common). `/multi-agent:stack` ilgili plugin'i etkinleştirir. |
+| [`mmerterden/dev-toolkit-mcp`](https://github.com/mmerterden/dev-toolkit-mcp) | UI testing / simulator capture / xcodebuild için MCP sunucusu - Phase 5 UI Bug Hunter'ı güçlendirir. Public npm registry'de [`@mmerterden/dev-toolkit-mcp`](https://www.npmjs.com/package/@mmerterden/dev-toolkit-mcp) olarak yayınlanır; installer her CLI'a onu senin için register eder, böylece `npx` ekstra konfigürasyon olmadan onu çözer. |
+
+## Lisans
+
+MIT - bkz. [LICENSE](./LICENSE). Güvenlik sorunları: bkz. [SECURITY.md](./SECURITY.md) (zafiyetler için public issue açma).

package/docs/architecture.md

@@ -117,12 +117,12 @@ graph TB
     end
 
     subgraph "Pipeline Specs"
-        CMD[commands/<br/>39 command files<br/>(34 user-facing)]
+        CMD[commands/<br/>49 command files]
         AGT[agents/<br/>8 agent personas]
         RUL[rules/<br/>12 domain rules]
         PHS[multi-agent-refs/phases/<br/>phase specs + contracts]
         CMP[skills/shared/core/<br/>orchestration skills<br/>incl. compliance]
-        EXT[skills/shared/external/<br/>143 curated skills<br/>(authoring source for the<br/>multi-agent-plugins marketplace)]
+        EXT["skills/shared/external/<br/>150 curated skills<br/>(authoring source for the<br/>multi-agent-plugins marketplace)"]
     end
 
     subgraph "Quality Gates"
@@ -162,18 +162,33 @@ User Input → Phase 0 (Init)
 
 ## Ecosystem Sync Targets
 
+`/multi-agent:sync` actually walks **five** targets, not the three shown in earlier
+revisions of this diagram — Codex CLI and the two independently-shipped repos
+(`multi-agent-plugins`, `dev-toolkit-mcp`) are real sync targets too:
+
 ```mermaid
 graph TD
     CC["Claude Code<br/>(source of truth)"]
-    COP["Copilot CLI<br/>(instructions + unified skills)"]
+    COP["Copilot CLI<br/>(instructions + 49 skills)"]
+    COD["Codex CLI<br/>(1 router skill + 49 refs)"]
     REPO["Pipeline Repo<br/>(npm package)"]
-    WEB["Website<br/>(optional)"]
-    RC["Remote Control<br/>(optional)"]
+    WEB["Website"]
+    PLUGREPO["multi-agent-plugins<br/>(5 stack plugins, own repo)"]
+    DTK["dev-toolkit-mcp<br/>(own repo, own release cadence)"]
 
-    CC -->|instructions + unified skills| COP
-    CC -->|genericized pipeline/| REPO
+    CC -->|copy + reformat| COP
+    CC -->|transform via install.js --codex| COD
+    CC -->|genericize| REPO
     CC -->|version + features| WEB
-    CC -->|pipeline refs| RC
+    REPO -->|build-stack-plugins.mjs| PLUGREPO
+    DTK -.->|sync only detects + ships, never authors| CC
+
     REPO -->|npm publish| NPM["GitHub Packages"]
     WEB -->|auto-deploy| VERCEL["Vercel"]
+    PLUGREPO -->|git push| MKT["Claude marketplace"]
+    DTK -->|npm publish| NPM2["GitHub Packages (private)"]
 ```
+
+Full detail on how these three repos compose at install time and at run time —
+including the Phase 3 → plugin dispatch contract and the Phase 5 → dev-toolkit MCP
+contract — lives in [`docs/ecosystem.md`](./ecosystem.md).