@mmerterden/multi-agent-pipeline 16.10.1 → 16.12.0

package/CHANGELOG.md

@@ -16,6 +16,64 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [16.12.0] - 2026-08-27
+
+### Added
+
+- **`/multi-agent:analysis` reviews the document before publishing it.** It had no review phase: the only pre-dispatch gate was a structural validator, so nothing ever read what was about to reach Confluence, and one real run published a channel it never searched for, an open question about a frame it never opened, and twenty-three unowned `EKLENECEK` markers. Phase 3.2 runs `phase-4-review.md` Step 0 (the analysis branch that already existed and nothing called) on the draft, before the destination is chosen. Reviewers are subagents holding `analysis/review.md`, never the context that wrote the document, because a context cannot notice a search it never thought to run. A blocking finding returns to synthesis with dispatch closed and never becomes an open question. Locked 36.
+- **Phase 3.3 closes gaps instead of writing them down.** Reachable evidence is searched and never asked about, decisions the user owns are asked, and only external gaps enter the document as `AS-NN` rows with an owner. A gap with neither a `searched, not found` nor an `asked, external` stamp fails the dispatch gate. Autopilot runs both phases; only the asking degrades.
+- **A third reviewer on Claude Code.** Opus fills the slot GPT-5.4 occupies on Copilot and Codex, so every host now runs three: Fable + Opus + Sonnet here. A finding two independent readers both miss is one triage has no chance to catch.
+- **`figma-screenshot.sh --discover-sections`.** One `GET ?depth=3` lists every section whose name matches the feature, with a frame count and a channel guess, folding diacritics so `Elite` and `Elit` are the same word. A channel may no longer be called missing until this returns nothing, and the record must cite the scan (Locked 12). Verified against the file that caused the defect: it returns both the Desktop section and the mobileWeb sibling the run had declared absent.
+- **Four validator gates**: `AS-NN` matched in both directions, `EKLENECEK` without an id, JSON inside a service-table cell, and Turkish diagram labels flattened to ASCII inside a mermaid fence, which the punctuation gate skips.
+
+### Changed
+
+- **"All variants drilled" now means read, not counted** (Locked 19). Visible `TEXT` layers inside each frame's own bounds are extracted, hidden layers and overflowing component boilerplate dropped. A frame can be called out of scope only by quoting its own text, and opening an open question about a frame nobody read fails the gate. One run logged a frame named `08 Payment` as ambiguous while its text spelled out the whole payment step.
+- **Every frame-inventory row gets an embedded image** (Locked 18). The gallery is generated from the inventory rather than hand-picked; narrowing to a canonical subset for page weight is not a call the run makes alone. One run uploaded 34 attachments and embedded 14, and was reported as "frames not uploaded" - the files were there and invisible.
+- **Embedded images carry a display width.** `md2confluence-v3.py --image-width` defaults to 720 with a per-image `![](f.png "width=320")` override; the attachment stays full resolution. A 2x phone export is 750x1624 and took two screen heights at natural size.
+- **Service tables put payloads under the table, not in a cell.** `Request` and `Response` carry one of three states; JSON goes in a fenced block below, field notes in their own table. A whole-unknown contract is one line, not six `EKLENECEK` cells.
+
+### Fixed
+
+- **`md2confluence` re-upload logged one warning per attachment and lost nothing.** The already-exists path was keyed off HTTP 400, and this Confluence Server answers 500 for a duplicate filename, so the update path was unreachable. It looks before creating now; 400, 409 and 500 remain handled as the race they should always have been. `attachments_updated` is counted apart from `attachments_uploaded`, because "0 uploaded, 12 warnings" reads as data loss when nothing was lost.
+- **The mermaid fallback lost every edge in any diagram whose nodes carry labels.** The pattern required the node id to sit next to the arrow, so `A[Basla] --> B` matched nothing - not just labelled branches, the whole flow. Both label syntaxes are captured now and the label is kept (`Evet -> Odeme Yap`), and the source ships beside the list so the diagram is recoverable.
+
+### Internal
+
+- **This release sets the `required` dist-tag.** An install older than 16.12.0 does not produce a worse analysis document, it produces one that has to be redone: no review before publishing, gaps recorded instead of closed, a channel called missing without the file ever being scanned, and frame filenames where the pictures belong. That is the criterion in the Supported Version Gate, so the tag is set rather than left off.
+- The analysis ref ceiling moves 148000 -> 154000 across two raises in one session. Everything that could live outside the count already does: the scan in `figma-screenshot.sh`, the reviewer rubric in `analysis/review.md` which a subagent loads and the orchestrator does not, and all four new gates in `validate-analysis-doc.mjs`. The tree was measured for reclaimable duplication first and had none.
+- `smoke-validate-analysis-doc.sh` replaces four section-number pairing assertions with the `AS-NN` contract in both directions.
+
+
+## [16.11.0] - 2026-08-27
+
+### Changed
+
+- **Picker option labels now follow `outputLanguage`.** Only the `AskUserQuestion` `header` chip stays English, because it is capped at 12 characters and most Turkish equivalents overflow it. A Turkish run used to render a Turkish question with English buttons, which reads as a half-translated dialogue rather than a contract. `rules.md` carries the new per-field matrix; `picker-contract.md` carries what the caller now owns: branch on which option was picked, never on its rendered text, and pass `default` / `ASK_CHOICE_DEFAULT` as a 1-based index. The host's own **Other** row is injected in English and no run can localize it.
+- **`Frontend` is `Web` across the pipeline** - the platform picker, the stack command, the schemas, the conventions tables, the phase docs and `frontend-guide.md`, now `web-guide.md`. The published `ai-frontend-toolkit` plugin id, the `frontendRepos` / `frontendRoots` prefs keys and the `frontend` stack alias all keep working: `web` is canonical and `frontend` still resolves, so nothing written before this release stops loading. `webRepos` / `webRoots` are the new spelling; the old pair is documented as deprecated rather than removed.
+- **A repo-less analysis run keeps its channel split.** It used to flatten everything into one document because there were no repo conventions to project onto. But a phone screen and a browser screen carry different requirements whether or not a repository exists; only the *projection* half of the split needed conventions. Channels are now derived from the evidence (`intake.md` Step 3 carries the signal table) and one document is emitted per channel. `mobile` stays one channel rather than iOS plus Android, since without conventions nothing tells the two apart.
+
+### Fixed
+
+- **The depth question passed a label as `ASK_CHOICE_DEFAULT`.** With labels localized, `"Full"` matches nothing on a Turkish run, `ask-choice.sh` falls through, and a non-TTY silently takes option one - the exact failure Phase 0 Step 7.5 was written to prevent. It passes the index now. Two more sites branched on a literal label (the plan gate and the review post-prompt) and now branch on the option.
+- **The analysis source questions asked all seven in one `AskUserQuestion` call**, which the host rejects at 4. Every run improvised its own grouping, and the improvised split separated the Document question from the Confluence one. The split is fixed at two batches now: what the feature is (Figma, Confluence, Document, Jira), then what constrains it (Swagger, Standards, Firebase). A spec arrives as an attached `.docx` or `.pdf` at least as often as a Confluence page, so both are asked on the same screen.
+- **Questions feeding only the development layer are no longer asked when no platform is selected.** With `platforms[]` empty that layer does not render, so the Standards and UI Tests questions spent the user's attention on answers nothing would consume. Firebase and A11y depth are still asked - they land in Part B, which does render.
+- **Confluence and Jira dispatch had no rule for a repo-less run.** Both were written only for the per-platform case, so "one page per platform" and the `h2. Platform: <X>` separators had nothing to bind to. They now cover the derived channels, and a single channel-agnostic document gets no suffix and no separator.
+- **A Confluence frame gallery shipped filenames where the pictures should be.** The analysis dispatch described the conversion, the attachment upload and the `<ac:image>` injection as three hand-rolled steps, while `md2confluence-v3.py` already implements all three. Hand-rolling is where the image reference got lost. Dispatch calls the script with `--attachments-dir` now and surfaces its `image reference has no matching attachment` warnings instead of reporting a clean publish; the conversion table documents that the converter degrades a missing file to a text link, which is the diagnosis for a page full of filenames.
+- **`language/SKILL.md` claimed PR bodies, Jira comments and wiki pages are always English**, contradicting the `rules.md` matrix that routes all three through `outputLanguage`. Commit messages, PR title prefixes, branch names and identifiers stay English; the bodies a human reads do not.
+- **The analysis command cited the wrong sections for two inputs** - Standards as Section 7 and Firebase as Section 6, where the template puts them at 13.7 and 11.
+
+### Added
+
+- **A `.docx` / `.pdf` / `.md` / `.txt` spec is a first-class analysis source**, asked next to the Confluence question. `fetch-document.sh` reads `.docx` with the Python standard library, so `python-docx` is neither imported nor needed; `.pdf` needs a `pdftotext` binary and degrades to referenced-but-not-fetched without one. `/multi-agent:setup` reports that binary as an advisory dependency, never a halt.
+- **A full command catalog in both READMEs** - 53 sub-commands in nine groups, the 8 subagents, and the two compliance skills that are not commands. The list previously existed only inside `/multi-agent:help`.
+
+### Internal
+
+- The analysis ref ceiling moves 145000 -> 148000. Unlike the v16.6.0 raise this one is not compensating for a measurement error: the tree gained three features and the number is right. About 1.4 kB of new prose was trimmed back before the ceiling was touched.
+- `smoke-language-matrix.sh` and `smoke-language-axis.sh` now assert the new rule in both directions - label follows `outputLanguage`, header stays English - and three more phrasings were added to the contradiction list after one slipped past the old set.
+
+
 ### Fixed
 
 - **The website sync committed under whatever identity the run carried, and the site silently stopped updating.** Step 4 ran a bare `git commit`, so the commit took the active account's address. The deploy platform builds only a commit whose author is a contributor on the project; any other author is accepted by the push and then never built - the deployment is created, reports `readyState: BLOCKED` (rendered by the CLI as `UNKNOWN` with a 0ms build), and the live site keeps serving the previous version. v16.4.0 and v16.5.0 were both pushed that way, neither was ever built, and both syncs reported the website as done.

package/README.md

@@ -62,11 +62,13 @@ One command runs 8 phases, with a gate between the risky ones:
 - **1 · Analysis** - detect the stack, scan the codebase, map impact (Sonnet).
 - **2 · Plan** - write a task breakdown and **stop for your approval** before touching code.
 - **3 · Dev** - TDD: failing test → code → green, following the repo's style + the active stack skills.
-- **4 · Review** - deterministic gates (build / lint / test / secret-scan) must pass first, then a **CLI-aware parallel review** - Claude Code runs 2 models (Fable + Sonnet), Copilot CLI runs 3 (GPT-5.4 + Opus + Sonnet) - and a **Fable triage** keeps only actionable findings; blockers loop back to Phase 3.
+- **4 · Review** - deterministic gates (build / lint / test / secret-scan) must pass first, then a **CLI-aware parallel review** - Claude Code runs 3 models (Fable + Opus + Sonnet), Copilot CLI runs 3 (GPT-5.4 + Opus + Sonnet) - and a **Fable triage** keeps only actionable findings; blockers loop back to Phase 3.
 - **5 · Test** - build + run the suite; success is required (no faked passes).
 - **6 · Commit/PR** - conventional commit, push (must succeed), open a PR (`Ref: #N`, never auto-close).
 - **7 · Report** - technical summary + a Jira comment with test scenarios, posted through the channels layer.
 
+`/multi-agent:analysis` runs its own shorter chain and, since v16.12.0, reviews what it wrote before publishing it: the draft goes through the same three-reviewer set and triage as a code diff, a blocking finding returns it to synthesis with dispatch closed, and the gaps that survive are either searched, asked about, or recorded with an owner. It used to publish behind a structural validator alone.
+
 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). How this repo, the `multi-agent-plugins` marketplace, and the `multi-agent-toolkit-mcp` server compose at install time and at run time is diagrammed in [docs/ecosystem.md](./docs/ecosystem.md).
@@ -83,7 +85,116 @@ 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`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `review-analysis`, `feedback`, `create-jira`, `save`, `routines`, `forget`. 53 commands in all  -  full list: `/multi-agent:help`.
+Depth, autopilot and `--local` are the only knobs on the run itself; everything else is its own command. The full catalog is below.
+
+## Commands
+
+`/multi-agent` plus 53 sub-commands. `/multi-agent:help` renders the same catalog in your terminal, in your `outputLanguage`.
+
+### Pipeline entries
+
+| Command | What it does |
+|---|---|
+| `/multi-agent "task"` | Full pipeline in a worktree. Asks Full or Short depth at Phase 0 |
+| `/multi-agent:local "task"` | Same pipeline on the current branch, no worktree |
+| `/multi-agent:autopilot "task"` | Worktree, no confirmations, always Full |
+| `/multi-agent:local-autopilot "task"` | Current branch, no confirmations, always Full |
+| `/multi-agent:resume-local` | Pipeline tail over work already done locally: Review → Build+Test → Commit/PR → Report. No dev phase |
+
+### Task control
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:status` | Every task's ID, phase, branch and state |
+| `/multi-agent:log [#N]` | Show a task's `agent-log.md` (most recent by default) |
+| `/multi-agent:resume [#N]` | Carry a stopped or failed task on from its last phase |
+| `/multi-agent:kill [#N]` | Stop a task, remove its worktree and branch |
+| `/multi-agent:search` | Ranked search across every task log; `--semantic` queries the triage corpus |
+| `/multi-agent:garbage-collect` | Sweep leftover scratch, orphan worktrees and offloaded payloads. Dry-run first |
+| `/multi-agent:prune-logs` | Delete per-task logs by age / project / task. Audit trail and metrics kept |
+| `/multi-agent:purge` | Wipe every worktree, branch, log and state file. Double confirmation |
+
+### Review
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:review` | Parallel review of a branch diff or a PR; inline comments + approve/needs-work on PR input |
+| `/multi-agent:review-jira` | Grade a Jira issue's readiness for development, comment the gaps |
+| `/multi-agent:review-issue` | Same grading for a GitHub issue |
+| `/multi-agent:review-analysis` | Review a written analysis document; findings cite the Locked rule they break |
+| `/multi-agent:diff-explain` | Map a Phase 4 triage finding back to the diff lines that caused it |
+| `/multi-agent:refactor` | Best-practice extraction + bug hunt + derived-skill drift + toolkit MCP research → one plan |
+| `/multi-agent:scan` | Skill security scan of local skill directories against a tiered pattern catalog |
+| `/multi-agent:prune-prompts` | Zero-base review of the always-on instruction footprint; keep / trial / delete per rule |
+| `/multi-agent:ios-coding-standard` | Audit an iOS module against the 99-rule registry, produce a remediation plan |
+
+### Analysis
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:analysis` | Standalone feature spec: global (23-section handoff) or corporate (IG/UC/FG) profile |
+| `/multi-agent:analysis-resolve` | Answer an analysis doc's Section 20 open questions one row at a time |
+| `/multi-agent:complaint-analysis` | Customer-complaint triage with Graylog evidence: client / bff root cause, or core routing |
+
+### Testing on a device
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:test` | UI Bug Hunter on a booted simulator or emulator: screenshot, tap, analyze |
+| `/multi-agent:test-dark-mode` | Walk every screen light then dark, report contrast and colour bugs |
+| `/multi-agent:test-accessibility` | VoiceOver labels, sub-44pt tap targets, contrast, traits |
+| `/multi-agent:test-dynamic-type` | Re-walk every screen at XL through accessibility-XL, report truncation |
+| `/multi-agent:test-screenshots [locale]` | App Store screenshot set in a locale (defaults to `tr`) |
+| `/multi-agent:manual-test` | Phase 5 standalone: check out the task branch and prepare it for Xcode |
+
+### Design, build and store
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:design-check` | Mock-mode vs Figma audit with a coverage gate; annotated HTML + PDF report |
+| `/multi-agent:store-ready` | Pre-submission gates for iOS and Android: package audit, store validation, policy review |
+| `/multi-agent:testflight-validation` | iOS-pinned alias of `store-ready`. Validates only, never uploads |
+| `/multi-agent:build-optimize` | Benchmark an Xcode build, run the analyzers, produce a recommend-first plan |
+
+### Tickets and reporting
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:jira` | Browse your open Jira issues → pick → branch → mode → launch |
+| `/multi-agent:issue` | Browse unassigned GitHub issues → pick → auto-assign → launch |
+| `/multi-agent:create-jira` | Draft a Task / Bug / Story to the project's own conventions, preview before create |
+| `/multi-agent:channels` | Post the multi-channel report: Jira, Confluence, Wiki, PR description, board status |
+| `/multi-agent:feedback` | Send one message to the maintainer. Only your text is sent, no logs or paths |
+
+### Your own routines
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:save [name]` | Save a recurring job as a reusable `/multi-agent:<name>`. Local-only, never synced |
+| `/multi-agent:routines` | List your saved routines and what each does |
+| `/multi-agent:forget [name]` | Remove a saved routine and its registry entry |
+
+### Setup and maintenance
+
+| Command | What it does |
+|---|---|
+| `/multi-agent:setup` | First-run wizard: keychain token discovery, git identity, pipeline preparation |
+| `/multi-agent:stack [ids]` | Enable the marketplace plugin(s) for this repo. Multi-select |
+| `/multi-agent:language [en\|tr]` | Show or set `outputLanguage`; `promptLanguage` stays English |
+| `/multi-agent:sync` | One-shot sync: Claude Code, Copilot CLI, pipeline repo, website, toolkit MCP |
+| `/multi-agent:update` | Update to the latest published npm release and run migrations |
+| `/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).
+
+### Skills that are not commands
+
+Two compliance skills install on every host and back the store gates: `apple-archive-compliance` (18-rule Apple review scan with ITMS code mapping) and `google-play-compliance` (21-rule Play policy catalog with Console error codes). Everything else stack-shaped - SwiftUI, Compose, backend, frontend - comes from the marketplace plugins described below.
 
 ## Stacks
 
@@ -114,8 +225,8 @@ error. Measured on 0.145: installing one plugin that declares 142 skills surface
 `multi-agent` router and keeps the sub-command specs as reference files that cost
 nothing until read - same commands, same behaviour, a layout the host can actually hold.
 
-Reviewer sets differ because the available models do: Claude Code runs 2 reviewers
-(Fable + Sonnet), Copilot CLI 3 (Opus + GPT-5.4 + Sonnet), Codex CLI 3 (gpt-5.6 at
+Reviewer sets differ because the available models do: Claude Code runs 3 reviewers
+(Fable + Opus + Sonnet), Copilot CLI 3 (Opus + GPT-5.4 + Sonnet), Codex CLI 3 (gpt-5.6 at
 xhigh, gpt-5.4, gpt-5.6 at medium). Codex is single-vendor, so consensus among its three
 is weaker evidence than the same consensus on a two-vendor host, and the triage note
 says so.

package/README.tr.md

@@ -62,11 +62,13 @@ Tek komut 8 fazı çalıştırır, riskli olanlar arasında bir kapı ile:
 - **1 · Analysis** - stack'i tespit et, codebase'i tara, etkiyi haritala (Sonnet).
 - **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.
+- **4 · Review** - önce deterministik kapılar (build / lint / test / secret-scan) geçmeli, sonra bir **CLI-farkında paralel review** - Claude Code 3 model çalıştırır (Fable + Opus + 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.
 
+`/multi-agent:analysis` kendi kısa zincirini koşar ve v16.12.0'dan beri yazdığını yayınlamadan önce review ediyor: taslak, bir kod diff'iyle aynı üç-reviewer setinden ve triyajdan geçiyor, bloklayıcı bulgu dokümanı sentez fazına geri gönderip dispatch'i kapatıyor, hayatta kalan boşluklar ya aranıyor ya sana soruluyor ya da sahibiyle birlikte kayda giriyor. Önceden yalnızca yapısal bir validator'ın arkasından yayınlıyordu.
+
 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 `multi-agent-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.
@@ -78,11 +80,121 @@ Bunun arkasındaki disiplin - sınırlı loop'lar, kanıt kapıları, token-büt
 | Full | `/multi-agent "task"` | Tüm 8 faz, interaktif |
 | Autopilot | `/multi-agent:autopilot "task"` | 7 faz (interaktif Test kapısı atlanır), onaysız |
 | Local | `/multi-agent:local "task"` | İnteraktif Test kapısı hariç tam pipeline, mevcut branch (worktree yok) |
+| Derinlik | Faz 0 Adım 7.5'te sorulur | Full (tüm fazlar) veya Short (Dev → Review → Test → Commit → Report). Komut adı değil  -  `/multi-agent` ve `:local` sorar, iki autopilot girişi de her zaman Full koşar |
 | Ship | `/multi-agent:resume-local` | 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`, `review-analysis`, `feedback`, `create-jira`, `save`, `routines`, `forget`. Toplam 53 komut - tam liste: `/multi-agent:help`.
+Koşunun kendisinde ayarlanabilen tek şey derinlik, autopilot ve `--local`; geri kalan her şey kendi komutu. Tam katalog aşağıda.
+
+## Komutlar
+
+`/multi-agent` ve 53 alt komut. `/multi-agent:help` aynı katalogu terminalde, `outputLanguage` ayarına göre gösterir.
+
+### Pipeline girişleri
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent "task"` | Worktree'de tam pipeline. Faz 0'da Full mu Short mu diye sorar |
+| `/multi-agent:local "task"` | Aynı pipeline, mevcut branch üzerinde, worktree yok |
+| `/multi-agent:autopilot "task"` | Worktree, onay yok, her zaman Full |
+| `/multi-agent:local-autopilot "task"` | Mevcut branch, onay yok, her zaman Full |
+| `/multi-agent:resume-local` | Lokalde bitmiş iş için pipeline kuyruğu: Review → Build+Test → Commit/PR → Report. Dev fazı yok |
+
+### Görev kontrolü
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:status` | Her görevin ID'si, fazı, branch'i ve durumu |
+| `/multi-agent:log [#N]` | Görevin `agent-log.md` dosyası (varsayılan: en son görev) |
+| `/multi-agent:resume [#N]` | Durmuş ya da hata almış görevi kaldığı fazdan sürdürür |
+| `/multi-agent:kill [#N]` | Görevi durdurur, worktree'sini ve branch'ini siler |
+| `/multi-agent:search` | Tüm görev loglarında sıralamalı arama; `--semantic` triyaj corpus'unu sorgular |
+| `/multi-agent:garbage-collect` | Artık scratch, sahipsiz worktree ve offload edilmiş payload'ları süpürür. Önce dry-run |
+| `/multi-agent:prune-logs` | Görev loglarını yaş / proje / görev filtresiyle siler. Denetim izi ve metrikler kalır |
+| `/multi-agent:purge` | Tüm worktree, branch, log ve state dosyalarını siler. Çift onay |
+
+### Review
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:review` | Branch diff'i veya PR üzerinde paralel review; PR girdisinde inline yorum + approve/needs-work |
+| `/multi-agent:review-jira` | Bir Jira issue'sunun geliştirmeye hazırlığını puanlar, eksikleri yorum olarak yazar |
+| `/multi-agent:review-issue` | Aynı puanlama, GitHub issue'su için |
+| `/multi-agent:review-analysis` | Yazılmış analiz dokümanını review eder; bulgular ihlal edilen Locked kuralını gösterir |
+| `/multi-agent:diff-explain` | Faz 4 triyaj bulgusunu onu doğuran diff satırlarına eşler |
+| `/multi-agent:refactor` | Best-practice çıkarımı + bug avı + türetilmiş skill drift'i + toolkit MCP araştırması → tek plan |
+| `/multi-agent:scan` | Yerel skill dizinlerini kademeli desen kataloğuna göre güvenlik taraması |
+| `/multi-agent:prune-prompts` | Sürekli yüklü talimat yükünün sıfır-tabanlı incelemesi; kural başına tut / dene / sil |
+| `/multi-agent:ios-coding-standard` | Bir iOS modülünü 99 kurallık registry'ye göre denetler, düzeltme planı çıkarır |
+
+### Analiz
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:analysis` | Bağımsız özellik spesifikasyonu: global (23 bölümlük doküman) veya kurumsal (IG/UC/FG) profili |
+| `/multi-agent:analysis-resolve` | Analiz dokümanının Bölüm 20 açık sorularını satır satır cevaplar |
+| `/multi-agent:complaint-analysis` | Graylog kanıtıyla şikayet triyajı: client / bff kök neden ya da core'a yönlendirme |
+
+### Cihaz üstü test
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:test` | Açık simülatör veya emülatörde UI Bug Hunter: screenshot, tap, analiz |
+| `/multi-agent:test-dark-mode` | Her ekranı önce light sonra dark gezer, kontrast ve renk hatalarını raporlar |
+| `/multi-agent:test-accessibility` | VoiceOver etiketleri, 44pt altı dokunma alanları, kontrast, trait'ler |
+| `/multi-agent:test-dynamic-type` | Her ekranı XL'den accessibility-XL'e kadar yeniden gezer, kırpılmaları raporlar |
+| `/multi-agent:test-screenshots [dil]` | Bir dilde App Store screenshot seti (varsayılan `tr`) |
+| `/multi-agent:manual-test` | Faz 5'in bağımsız hali: görev branch'ine geçer, Xcode için hazırlar |
+
+### Tasarım, build ve store
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:design-check` | Kapsam geçitli mock-mode vs Figma denetimi; annotasyonlu HTML + PDF rapor |
+| `/multi-agent:store-ready` | iOS ve Android için yayın öncesi kapılar: paket denetimi, store doğrulaması, politika incelemesi |
+| `/multi-agent:testflight-validation` | `store-ready`'nin iOS'a sabitlenmiş hali. Yalnızca doğrular, asla yüklemez |
+| `/multi-agent:build-optimize` | Xcode build'ini ölçer, analizörleri koşar, önce-öneri yaklaşımlı plan üretir |
+
+### Ticket ve raporlama
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:jira` | Açık Jira issue'larını gez → seç → branch → mod → başlat |
+| `/multi-agent:issue` | Atanmamış GitHub issue'larını gez → seç → otomatik ata → başlat |
+| `/multi-agent:create-jira` | Projenin kendi konvansiyonlarına uygun Task / Bug / Story taslağı, oluşturmadan önce önizleme |
+| `/multi-agent:channels` | Çok kanallı raporu gönderir: Jira, Confluence, Wiki, PR açıklaması, board durumu |
+| `/multi-agent:feedback` | Bakımcıya tek mesaj. Yalnızca yazdığın metin gider, log ve yol gitmez |
+
+### Kendi rutinlerin
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:save [ad]` | Tekrar eden bir işi `/multi-agent:<ad>` olarak kaydeder. Local-only, asla sync edilmez |
+| `/multi-agent:routines` | Kaydettiğin rutinleri ve ne yaptıklarını listeler |
+| `/multi-agent:forget [ad]` | Kayıtlı bir rutini ve registry kaydını siler |
+
+### Kurulum ve bakım
+
+| Komut | Ne yapar |
+|---|---|
+| `/multi-agent:setup` | İlk kurulum sihirbazı: keychain token keşfi, git identity, pipeline hazırlığı |
+| `/multi-agent:stack [id]` | Bu repo için marketplace plugin'lerini etkinleştirir. Çoklu seçim |
+| `/multi-agent:language [en\|tr]` | `outputLanguage`'i gösterir veya değiştirir; `promptLanguage` İngilizce kalır |
+| `/multi-agent:sync` | Tek atımlık senkron: Claude Code, Copilot CLI, pipeline repo, website, toolkit MCP |
+| `/multi-agent:update` | npm'deki son yayına günceller ve migration'ları koşar |
+| `/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).
+
+### Komut olmayan skill'ler
+
+İki uyumluluk skill'i her host'a kurulur ve store kapılarını besler: `apple-archive-compliance` (ITMS kod eşlemeli 18 kurallı Apple review taraması) ve `google-play-compliance` (Console hata kodlu 21 kurallı Play politika kataloğu). Stack'e bağlı geri kalan her şey - SwiftUI, Compose, backend, frontend - aşağıda anlatılan marketplace plugin'lerinden gelir.
 
 ## Stack'ler
 
@@ -114,8 +226,8 @@ pipeline tek bir `multi-agent` router gönderir ve alt-komut spec'lerini, okunan
 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
+Reviewer setleri farklı çünkü mevcut modeller farklı: Claude Code 3 reviewer çalıştırır
+(Fable + Opus + 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.

package/docs/adr/0001-three-model-triage.md

@@ -2,6 +2,11 @@
 
 **Status:** Accepted · 2025 · Amended 2026-04 (CLI-aware reviewer set) · Amended 2026-07 (v10.6.0: Fable 5 restored - Reviewer 1 and triage run on Fable on Claude Code; Copilot CLI pins Opus. "Opus" below reads as "the top tier of the day")
 
+> **Superseded in part, v16.12.0.** The reviewer count is now 3 on every host: Opus
+> fills the slot GPT-5.4 occupies on Copilot and Codex, so Claude Code runs
+> Fable + Opus + Sonnet. The reasoning below about a 2-reviewer set on Claude Code
+> is kept as the record of what was decided then, not as current behaviour.
+
 ## Context
 
 Code review is the phase where the pipeline most commonly ships wrong work. A

package/docs/features.md

@@ -12,7 +12,7 @@ Phase 1: Analysis  Stack detection, codebase exploration (parallel Explore agent
 Phase 2: Planning  Task decomposition, architecture review, user approval
 Phase 3: Dev       TDD cycle: test → code → build (Sonnet)
 Phase 4: Review    Deterministic gates + parallel AI review + Fable triage
-                   (Claude Code: Fable + Sonnet · Copilot CLI: GPT-5.4 + Opus + Sonnet)
+                   (Claude Code: Fable + Opus + Sonnet · Copilot CLI: GPT-5.4 + Opus + Sonnet)
 Phase 5: Test      Optional manual testing + on-demand device audits
 Phase 6: Commit    Git commit, push, PR with default reviewers + draft/ready prompt
 Phase 7: Report   External: Jira comment · Wiki + Figma screenshots · Confluence
@@ -134,6 +134,22 @@ Cheap, objective checks run BEFORE any AI token is spent:
 
 If any gate fails, fix first. Don't waste AI tokens reviewing broken code.
 
+### Analysis Document Review (Phase 3.2 + 3.3)
+
+`/multi-agent:analysis` published behind a structural validator alone until v16.12.0: nothing read the
+document before it reached Confluence. Phase 3.2 now runs the same reviewer set and triage a code diff
+gets, on the draft, before the destination is even chosen. Its first question is what the run skipped -
+an input declared missing that nothing searched for, an open question about evidence nobody read, a gap
+with no owner, a scope call made without asking. A blocking finding returns to synthesis with dispatch
+closed; it never becomes an open question, because "the document is wrong" is not something to ask the
+reader.
+
+Phase 3.3 then sorts what is left: reachable evidence is searched (never asked about), decisions the
+user owns are asked with `AskUserQuestion`, and only genuinely external gaps enter the document as
+`AS-NN` rows with an owner. A gap carrying neither a `searched, not found` nor an `asked, external`
+stamp fails the dispatch gate. Autopilot runs both phases; only the asking degrades, into rows stamped
+`autopilot: could not ask`.
+
 ### CLI-Aware Parallel Review + Fable Triage (Phase 4 Steps 2-3)
 
 | Reviewer   | Model               | Focus                             | Where it runs        |
@@ -142,7 +158,7 @@ If any gate fails, fix first. Don't waste AI tokens reviewing broken code.
 | Reviewer 2 | `gpt-5.4`           | Edge cases, different perspective | **Copilot CLI only** |
 | Reviewer 3 | `claude-sonnet-4-6` | Quality + correctness + naming    | Both CLIs            |
 
-The reviewer set is **CLI-aware**: Claude Code dispatches 2 reviewers in parallel (Fable + Sonnet - GPT-5.4 is not available there); Copilot CLI dispatches all 3. Each returns structured JSON for deterministic aggregation. Cross-model diversity catches blind spots that any single model family would miss.
+The reviewer set is **CLI-aware**: Claude Code dispatches 3 reviewers in parallel (Fable + Opus + Sonnet - Opus fills the slot GPT-5.4 takes elsewhere); Copilot CLI dispatches all 3. Each returns structured JSON for deterministic aggregation. Cross-model diversity catches blind spots that any single model family would miss.
 
 **Fable Triage** (Phase 4 Step 3, Opus on Copilot CLI): Evaluates merged raw findings against task scope. Classifies each as `accepted` (fix now), `deferred` (out of scope, log for later), or `rejected` (false positive / noise). Only triage-accepted blocking items loop back to Phase 3.
 

package/install/templates/copilot-instructions.md

@@ -266,7 +266,7 @@ Always, in every mode:
 Stack skill sets ship as versioned plugins in the `multi-agent-plugins` marketplace. Selecting a stack enables the matching plugin(s) in the target repo's `.claude/settings.json` `enabledPlugins`; the `ai-common-toolkit` is always enabled alongside. There is no session-start auto-swap script. Select or change the stack with:
 
 ```bash
-multi-agent-stack [ios|android|mobile|backend|frontend|fullstack|all]
+multi-agent-stack [ios|android|mobile|backend|web|fullstack|all]
 ```
 
 ## UI Bug Hunter

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "16.10.1",
+  "version": "16.12.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/claude-md-template.md

@@ -17,7 +17,7 @@
 2. Planning (Opus) -> spec, task breakdown
 3. Development (Sonnet) -> TDD, code, build
 4. Review -> deterministic gates + parallel review + Fable triage
-   - Claude Code: Opus + Sonnet (2 paralel)
+   - Claude Code: Fable + Opus + Sonnet (3 paralel)
    - Copilot CLI: GPT-5.4 + Opus + Sonnet (3 paralel)
    - Codex CLI: gpt-5.6 (xhigh) + gpt-5.4 + gpt-5.6 (medium) (3 paralel)
 

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

@@ -1,6 +1,6 @@
 ---
 description: "Task orchestrator  -  full pipeline via Jira ID + branch or GitHub Issue URL: analysis, plan, TDD development, parallel review + Fable triage (CLI-aware: 2-model on Claude Code, 3-model on Copilot CLI), commit, log. Use when given a Jira ID, a GitHub issue or a free-text task and the whole pipeline should run."
-description-tr: "Görev orkestratörü - Jira ID + branch veya GitHub Issue URL ile tam pipeline: analiz, plan, TDD geliştirme, paralel review + Fable triyajı (CLI'ya göre: Claude Code'da 2, Copilot CLI'da 3 model), commit, log"
+description-tr: "Görev orkestratörü - Jira ID + branch veya GitHub Issue URL ile tam pipeline: analiz, plan, TDD geliştirme, paralel review + Fable triyajı (CLI'ya göre: Claude Code'da 3, Copilot CLI'da 3 model), commit, log"
 allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet, AskUserQuestion, WebFetch, WebSearch, NotebookEdit, Skill
 ---
 
@@ -12,7 +12,7 @@ Parse the user input and route to the correct sub-command.
 
 **Input**: $ARGUMENTS
 
-> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` from `$HOME/.claude/multi-agent-preferences.json` and render every conversational line in it. `AskUserQuestion` `label`/`header` stay English, but its `question` and option `description`s render in `outputLanguage`; external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
+> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` from `$HOME/.claude/multi-agent-preferences.json` and render every conversational line in it. `AskUserQuestion` renders its `question`, option `label`s and option `description`s in `outputLanguage`; only `header` stays English (<=12-char chip); external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
 
 ## Canonical Invocation (per CLI)
 
@@ -134,7 +134,7 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 | SwiftUI component task (iOS) | `$HOME/.claude/multi-agent-refs/swiftui-guide.md` |
 | Jetpack Compose task (Android) | `$HOME/.claude/multi-agent-refs/android-guide.md` |
 | Backend API task | `$HOME/.claude/multi-agent-refs/backend-guide.md` |
-| Frontend component task | `$HOME/.claude/multi-agent-refs/frontend-guide.md` |
+| Web component task | `$HOME/.claude/multi-agent-refs/web-guide.md` |
 | Phase 1 or Phase 7 (knowledge) | `$HOME/.claude/multi-agent-refs/knowledge.md` |
 | Token lookup needed | `$HOME/.claude/multi-agent-refs/keychain.md` |
 | Audit tools (Phase 5/6) | `$HOME/.claude/multi-agent-refs/audit-guide.md` |
@@ -151,7 +151,7 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 - iOS detected -> load `swiftui-guide.md`
 - Android detected -> load `android-guide.md`
 - Python/Node.js/Go detected -> load `backend-guide.md`
-- React/Vue/Next.js detected -> load `frontend-guide.md`
+- React/Vue/Next.js detected -> load `web-guide.md`
 - Multiple stacks -> load all relevant guides
 
 **Agent definitions** (used in Phase 1 and Phase 4):

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

@@ -12,7 +12,7 @@ This command is **independent** from the orchestrator's Phase 1 analysis (which
 
 **Scope (development analysis, not a screen spec)**: this command produces a *development* analysis  -  what to build, the architecture plan, files to add, the test plan, and which existing components to reuse. It is NOT a design / screen-anatomy specification. The design itself is already produced elsewhere (figma-to-swiftui builds the components and binds them via Code Connect), so the analysis consumes those existing bindings as the source of truth for "what already exists" (see Phase 1b.1) instead of re-deriving the design. Do not grow this command toward exhaustive per-screen layout / gesture / state documentation; keep it development-focused.
 
-> **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English (this file is read as a system prompt). `AskUserQuestion.label` and `header` stay English. `question` and `description` follow `outputLanguage`. The emitted analysis document body follows `outputLanguage` (`tr` or `en`).
+> **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English (this file is read as a system prompt). `AskUserQuestion.question`, `.options[].label` and `.options[].description` follow `outputLanguage`; only `header` stays English (<=12-char chip). The emitted analysis document body follows `outputLanguage` (`tr` or `en`).
 
 ## Locked decisions (do not re-ask)
 
@@ -61,7 +61,7 @@ Full contract: `$HOME/.claude/multi-agent-refs/analysis/evidence.md`. Fetches ev
 
 Full contract: `$HOME/.claude/multi-agent-refs/analysis/synthesis.md`. Pass A builds the platform-agnostic concept layer; Phase 2a previews the resolved conventions for approval (Locked 26); Pass B projects each concept onto the selected platform with a footnote per filled cell (Locked 24).
 
-### Phases 3, 3.5, 4, 5 - Render, publish, report
+### Phases 3, 3.2, 3.3, 3.5, 4, 5 - Render, review, publish, report
 
 Full contract: `$HOME/.claude/multi-agent-refs/analysis/render.md`. Renders one markdown file per platform, runs the **required** `ai-common-toolkit:humanizer` pass, gates on `validate-analysis-doc.mjs` and on the `build-references.mjs --check` references coverage gate (Locked 34), asks for the output destination, dispatches to Local / Confluence / Jira (a Jira issue receives a comment unless the user explicitly asks for the description, which is never overwritten without a backup and a confirmation), then reports and stops. The humanizer pass and the validator are required in every mode; a document that skipped either is not shippable.
 
@@ -106,7 +106,7 @@ When `phase == "cancelled_at_pass_b_preview"`:
 | Path | Reason |
 |------|--------|
 | `~/.claude/lib/submodule-detector.sh` | Phase 0 Step 4 repo discovery |
-| `~/.claude/lib/context-link-extractor.sh` | Phase 0 Step 5/Q6 URL classifier (handles `local-file`, `wiki`, `standards-confluence`, `generic-doc`, `firebase-events:names`, `firebase-events:schema`, `firebase-events:console` types) |
+| `~/.claude/lib/context-link-extractor.sh` | Phase 0 Step 5 source classifier for every question's Other input (handles `local-file`, `document`, `wiki`, `standards-confluence`, `generic-doc`, `firebase-events:names`, `firebase-events:schema`, `firebase-events:console` types) |
 | `~/.claude/lib/fetch-swagger.sh`, `fetch-confluence.sh` | Phase 1 fetchers |
 | Phase 1 wiki fetch chain (inline, no standalone script) | `git clone --depth 1 <repo>.wiki.git` first, `gh api repos/.../contents/<file>.md` second, WebFetch third - see the Phase 1 type table `wiki` row |
 | `~/.claude/lib/extract-conventions.sh` | Phase 1c convention extractor (7 pattern groups, JSON output, confidence levels) |
@@ -122,7 +122,7 @@ When `phase == "cancelled_at_pass_b_preview"`:
 | `$HOME/.claude/lib/jira-publish.sh` | Phase 4 Jira write: comment by default, description only on explicit choice - reads the current description first, backs it up, appends below a rule, refuses a non-empty replace without `--confirm-overwrite` |
 | `$HOME/.claude/scripts/validate-analysis-doc.mjs` | Phase 4 pre-dispatch gate: deterministic check of the emitted per-platform doc (front-matter, never-omitted sections, humanizer punctuation, Full-mode BR traceability) |
 | a project-supplied Confluence-embedded API-table parser (optional) | Parse endpoints from a Confluence page's Request Path / Service Name / Response Body table columns |
-| `~/<project>-Standards.md` | Canonical home-dir standards reference (auto-detected at Q5 option 2; exact filename from `prefs.projects[<project>].standardsFile`) |
+| `~/<project>-Standards.md` | Canonical home-dir standards reference (auto-detected by the Standards question's option 2; exact filename from `prefs.projects[<project>].standardsFile`) |
 | `~/.claude/rules/*.md` | Fallback rules when `evidence.standards[]` is empty |
 
 ## Notes
@@ -131,14 +131,14 @@ When `phase == "cancelled_at_pass_b_preview"`:
 - The minimum possible output (per per-platform file) is `1. Scope` + `7. Development Plan` (both always-present).
 - If Confluence or Jira POST returns 401 / 403 during Phase 4, surface the error and offer Local fallback (the local drafts in `/tmp/` are still on disk; copying them into the repo working tree is always available).
 - The `analysis/` directory is not in `.gitignore`; the user can `git add analysis/` manually. No auto-commit.
-- **Per-platform file naming**: `analysis/<feature>-<platform>.md`. The `<platform>` slug is lowercase, one of `ios | android | backend | frontend`. The `<feature>` slug preserves the user's feature name with whitespace replaced by `-` (e.g. `User Profile` -> `UserProfile` or `Item-Status` depending on input shape; the renderer trims and de-duplicates dashes).
-- **Standards binding (Q5)**: When `evidence.standards[]` is non-empty, every decision in Section 7 must cite the binding source. The renderer enforces this by failing render if any Section 7 architectural decision has no `cite:` reference; the user is prompted to either tighten the source or add a Risk row acknowledging the missing citation.
-- **Firebase ingestion (Q6)**: Console URLs are never fetched (auth-gated). Only `:names` and `:schema` inputs feed `evidence.firebase[]`. Section 6 emits per-platform snippets but the events table itself is shared across all per-platform files (the rules / event vocabulary is one product invariant).
+- **Per-platform file naming**: `analysis/<feature>-<platform>.md`. The `<platform>` slug is lowercase, one of `ios | android | web | backend` for a repo-backed run, or `mobile | web` for the channels a repo-less run derives from its evidence (Locked 35). `web` is the pre-`web` spelling and is still read back for older state and documents. The `<feature>` slug preserves the user's feature name with whitespace replaced by `-` (e.g. `User Profile` -> `UserProfile` or `Item-Status` depending on input shape; the renderer trims and de-duplicates dashes).
+- **Standards binding (the Standards question)**: When `evidence.standards[]` is non-empty, every decision in Section 13 (Architecture Plan, corporate Section 17) must cite the binding source in its 13.7 Standards-binding table. The renderer enforces this by failing render if any architectural decision has no `cite:` reference; the user is prompted to either tighten the source or add a Risk row acknowledging the missing citation.
+- **Firebase ingestion (the Firebase question)**: Console URLs are never fetched (auth-gated). Only `:names` and `:schema` inputs feed `evidence.firebase[]`. Section 11 Analytics (corporate Section 13) emits per-platform snippets but the events table itself is shared across all per-platform files (the rules / event vocabulary is one product invariant).
 - **Wiki access fallback chain**: Phase 1 `wiki` fetcher tries (a) `git clone .wiki.git`, (b) `gh api repos/.../contents/<file>.md`, (c) raw `WebFetch` of the page URL. Only after all three fail does the entry land in `fetchErrors[]`.
 - **Local-file safety**: `local-file` reads are scoped to `~/`, `/Users/`, and the repo's working tree. Paths outside these prefixes are rejected with `WARN: refusing to read <path>; outside allowed roots` to avoid accidental ingestion of unrelated files.
-- **Q5 vs Q3 split**: Q3 (Confluence) collects feature-specific spec pages. Q5 (Standards) collects cross-cutting documentation that constrains the development plan (architecture, coding conventions, navigation pattern). A URL pasted in both questions is de-duplicated by URL and the Q5 entry wins (binding flag is retained).
-- **Workspace coding documentation default**: when Q5 option 2 (Auto-detect) is selected, the probe also reads `prefs.projects[<project>].confluenceStandardsParent` (if set) and looks for child pages whose title starts with `Coding`, `Standards`, `Architecture`, or `Navigation`. If that fetch fails with auth, log a hint that the user should host an offline mirror at `prefs.projects[<project>].standardsFile` (canonical local fallback).
-- **Mixed paste handling**: Q5 / Q6 Other inputs accept comma-separated mixed entries. Whitespace is trimmed; entries are de-duplicated by canonicalised string (lowercase scheme + host + path for URLs; `realpath` for local files; lowercase exact match for event names).
+- **Standards vs Confluence vs Document split**: the Confluence question collects feature-specific spec pages and the Document question the same spec delivered as a `.docx` / `.pdf` / `.md` / `.txt` file  -  both describe what the feature IS and both land in `evidence.documents[]`. The Standards question collects cross-cutting documentation that constrains the development plan (architecture, coding conventions, navigation pattern). A source pasted in more than one of the three is de-duplicated (by URL, or by `realpath` for a local file) and the Standards entry wins, because it retains the binding flag.
+- **Workspace coding documentation default**: when the Standards question's option 2 (Auto-detect) is selected, the probe also reads `prefs.projects[<project>].confluenceStandardsParent` (if set) and looks for child pages whose title starts with `Coding`, `Standards`, `Architecture`, or `Navigation`. If that fetch fails with auth, log a hint that the user should host an offline mirror at `prefs.projects[<project>].standardsFile` (canonical local fallback).
+- **Mixed paste handling**: the Standards and Firebase Other inputs accept comma-separated mixed entries. Whitespace is trimmed; entries are de-duplicated by canonicalised string (lowercase scheme + host + path for URLs; `realpath` for local files; lowercase exact match for event names).
 - **Repo-evidence reuse policy**: Phase 1b's catalogue is consulted by Pass B Section 7 rendering. The `direct-match` tag is the strongest signal; a `same-domain` row becomes an advisory note ("consider adapting existing X in the same feature directory"); `cross-cutting` items become a sentence in the section preamble ("reuse the cross-feature X from Common/"). See Locked decision 11.
 
 ## Required: Phase Tracker Contract

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

@@ -10,7 +10,7 @@ Companion command to `/multi-agent:analysis`. Takes an `analysis/<feature>-<plat
 
 **Core invariant - read this twice:** the analysis doc is authoritative and forward-looking. The resolver never invents an answer; if no source produces a credible candidate, the only options offered are Defer and Other. Each Section 20 row is its own decision; never blend candidates across rows.
 
-> **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English. `AskUserQuestion.label` and `header` stay English; `question` and `description` follow `prefs.global.outputLanguage`. Fragments written INTO the doc follow the doc's own front-matter `language` field (not `outputLanguage`), so a `tr` doc stays uniformly Turkish even when the session language differs.
+> **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English. `AskUserQuestion.question`, `.options[].label` and `.options[].description` follow `prefs.global.outputLanguage`; only `header` stays English (<=12-char chip). Fragments written INTO the doc follow the doc's own front-matter `language` field (not `outputLanguage`), so a `tr` doc stays uniformly Turkish even when the session language differs.
 
 ## Inherited Locked decisions (from /multi-agent:analysis - binding here)
 
@@ -35,7 +35,7 @@ Inherited decisions: `$HOME/.claude/multi-agent-refs/analysis/locked.md`.
 
 ### Phase 0 - Intake
 
-**Step 1 - Doc picker.** If `$ARGUMENTS` has a path, validate it. Otherwise glob `analysis/*-{ios,android,backend,frontend}.md` under cwd (and each repo root from `state.analysisSpec.repos[]` when the session still holds analysis state):
+**Step 1 - Doc picker.** If `$ARGUMENTS` has a path, validate it. Otherwise glob `analysis/*-{ios,android,backend,web}.md` under cwd (and each repo root from `state.analysisSpec.repos[]` when the session still holds analysis state):
 - 1 match: use it; echo the path, no question.
 - 0 or 2+ matches: AskUserQuestion, `header: "Doc"`, question `<localized: "Which analysis document should we resolve?">`, options = matches (max 3) + Other for a free-typed path.
 

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

@@ -8,7 +8,7 @@ argument-hint: '"task"  -  issue URL, Jira ID, free-text, or #id (for resume)'
 
 **Input**: $ARGUMENTS
 
-> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` `label`/`header` stay English, but its `question` and option `description`s render in `outputLanguage`; external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
+> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` renders its `question`, option `label`s and option `description`s in `outputLanguage`; only `header` stays English (<=12-char chip); external payload bodies follow `outputLanguage` too (identifiers, commit messages, branch names stay English). Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
 
 Run the task end-to-end with no confirmations.