@mmerterden/multi-agent-pipeline 16.10.1 → 16.12.0

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

@@ -8,7 +8,7 @@ argument-hint: "(none - operates on current repo)"
 
 Wraps the vendored `xcode-build-orchestrator` skill (and its 5 specialist analyzers) so iOS users do not have to remember the orchestrator skill name. Recommend-first: no project files are modified without explicit developer approval. All output lands in `.build-benchmark/` in the current repo.
 
-> **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 benchmark plan body (the upstream skill controls it) is English by upstream convention.
+> **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 benchmark plan body (the upstream skill controls it) is English by upstream convention.
 
 ## When to use
 
@@ -25,7 +25,7 @@ Before dispatch, fail fast on non-iOS repos. Detect iOS context via the standard
 |--------|--------|
 | `*.xcodeproj` or `*.xcworkspace` in cwd | Proceed to dispatch |
 | `Package.swift` only (SwiftPM lib, no Xcode project) | Proceed; orchestrator handles `xcodebuild -package-path` |
-| Android / Backend / Frontend markers only | Surface a short error: "build-optimize is iOS-only. Detected: <stack>. Use the platform-appropriate perf skill (android-performance / web-performance / etc.) instead." Exit. |
+| Android / Backend / Web markers only | Surface a short error: "build-optimize is iOS-only. Detected: <stack>. Use the platform-appropriate perf skill (android-performance / web-performance / etc.) instead." Exit. |
 | No recognizable stack | Surface "no iOS project found in cwd" and exit. |
 
 ## Steps

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

@@ -334,7 +334,7 @@ Applying the Jira table to the PR body is the recurring failure of this step: it
 
 Secondary artifacts ride along as one-line intents at the bottom of the preview: Wiki page list, wiki → Jira triad comment (when Wiki is selected and the triad is active per `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`), Board status move (`{from} → {to}`), GitHub issue comment + Progress-flag sync (Phase 7 Step 1.5  -  same gate, see `$HOME/.claude/multi-agent-refs/phases/phase-7-report.md`).
 
-**Then a single AskUserQuestion** (`question`/`description` in `outputLanguage`; `label`/`header` English):
+**Then a single AskUserQuestion** (`question`/`label`/`description` in `outputLanguage`; `header` English):
 
 | Option | Behavior |
 |---|---|

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

@@ -12,7 +12,7 @@ Triage of customer-reported errors across the layers the team owns (client apps
 
 **Side-effect contract**: may write a local markdown report, post a Confluence page, or add a Jira comment/description - but **never** creates branches, worktrees, commits, or PRs. Stops at the report.
 
-> **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 `outputLanguage`. The report body follows `outputLanguage`; Graylog excerpts, verdict tokens, and external payload metadata stay English.
+> **Language**: Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix - instruction prose stays English. `AskUserQuestion.question`, `.options[].label` and `.options[].description` follow `outputLanguage`; only `header` stays English (<=12-char chip). The report body follows `outputLanguage`; Graylog excerpts, verdict tokens, and external payload metadata stay English.
 
 ## Locked decisions (do not re-ask)
 

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

@@ -10,7 +10,7 @@ argument-hint: "[\"<free-text description>\"] [figma-url] [swagger-url]  -  all
 
 Creates exactly one Jira issue, and only after explicit approval. The issue type (Task / Bug / Story) is asked at the start of every run. No branches, no commits, no worktrees, no pipeline chaining. The draft learns the target project's conventions from its recent same-type issues (summary format, labels, components, priority norms, test-scenario style) and offers active-sprint placement when a sprint is running.
 
-> **Language**: instruction prose here is English. AskUserQuestion `question`/`description` and the issue content (summary + description) follow `prefs.global.outputLanguage`, like every other user-facing payload body (`rules.md` matrix). `label`/`header` stay English.
+> **Language**: instruction prose here is English. AskUserQuestion `question`/`label`/`description` and the issue content (summary + description) follow `prefs.global.outputLanguage`, like every other user-facing payload body (`rules.md` matrix). Only `header` stays English (<=12-char chip).
 
 ## Issue types
 

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

@@ -16,7 +16,7 @@ Local, on-device design-conformance auditor. It runs the app in a **mock mode**
 > 1. **`prefs.global.promptLanguage` is always `en`**  -  this spec and every instruction to the LLM stay English.
 > 2. **`prefs.global.outputLanguage` is user-selectable**  -  applies to conversational lines and the human-readable parts of the report. Pass it to `design_report` as `report.lang`; the engine defaults to English and ships an `en` + `tr` label pack, plus per-key `report.labels` overrides.
 >
-> Regardless of `outputLanguage`, these stay English: `AskUserQuestion` labels/headers, branch names, file paths, code identifiers, log lines. Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
+> Regardless of `outputLanguage`, these stay English: `AskUserQuestion` `header` chips, branch names, file paths, code identifiers, log lines. Option `label`s follow `outputLanguage` like the rest of the picker copy. Full contract: `$HOME/.claude/multi-agent-refs/rules.md` "Language Application".
 
 ## Scope  -  `$ARGUMENTS`
 
@@ -113,7 +113,7 @@ for l in sys.stdin:
    ```
    Branch on `supported`:
    - **`false`** → **HALT**. Show `reason` + that no runtime mock switch / launchable app / mock fixtures were found. Tell the user this module cannot be audited by design-check and stop. Do not fabricate a comparison.
-   - **`"debug-only"`** → surface an `AskUserQuestion` warning: mocks are compiled into the Debug build via `#if DEBUG` DI, so **variants cannot be toggled at launch** - only the default Debug state is comparable. Options: `{ label: "Continue", description: "Audit the single default Debug state only" }`, `{ label: "Cancel", description: "Stop" }`.
+   - **`"debug-only"`** → surface an `AskUserQuestion` warning: mocks are compiled into the Debug build via `#if DEBUG` DI, so **variants cannot be toggled at launch** - only the default Debug state is comparable. Options (label + description in `outputLanguage`): option 1 semantically "Continue"  -  audit the single default Debug state only; option 2 semantically "Cancel"  -  stop.
    - **`true`** → continue. Persist `state.designCheck.mock = <detect result>` (mechanism, activation, variantsHint, evidence).
 5. **SCENARIO INVENTORY (this is the audit's target set)**:
    ```

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

@@ -59,7 +59,7 @@ Pipeline (after Phase 0)  -  shown as visual cards in terminal:
                            only; a Short run has no plan, autopilot may not ask)
   Phase 3:   Dev        -> TDD: test -> code -> build (Sonnet) + build queue
   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: switch to branch, test in Xcode
                           (only /multi-agent has it; every autopilot and local entry drops it)
   Phase 6:   Commit     -> Commit -> push -> PR + issue body update (never auto-closes)
@@ -239,7 +239,7 @@ Setup:
 
 Key Features:
 
-  Multi-Platform   iOS, Android, Backend, Frontend  -  auto-detected
+  Multi-Platform   iOS, Android, Backend, Web  -  auto-detected
   Build Queue      xcodebuild/Gradle serialized with lock file  -  parallel safe
   Stack Aware      Auto-detects iOS/Android/Python/Node/Go/Docker, uses the enabled stack plugin's skills
   Det. Gates       Build + lint + test + secret scan BEFORE AI review
@@ -279,7 +279,7 @@ Examples:
   /multi-agent:autopilot "LoginView dark mode fix"               # iOS
   /multi-agent "Add pagination to /api/users endpoint"           # Backend
   /multi-agent "Fix bottom nav recomposition in HomeScreen"      # Android
-  /multi-agent "Responsive layout broken on tablet"              # Frontend, choose Short
+  /multi-agent "Responsive layout broken on tablet"              # Web, choose Short
 
   # Review current diff only
   /multi-agent:review
@@ -334,7 +334,7 @@ Pipeline (Phase 0'dan sonra)  -  terminalde görsel kart olarak görünür:
                            etkileşimli; Kısa'da plan yok, autopilot soru soramaz)
   Phase 3:   Dev        -> TDD: test -> kod -> build (Sonnet) + build queue
   Phase 4:   Review     -> Deterministik kapılar + paralel 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       -> Opsiyonel: branch'e geç, Xcode'da test
                           (yalnız /multi-agent'ta var; her autopilot ve local girişi düşürür)
   Phase 6:   Commit     -> Commit -> push -> PR + issue body güncelleme (hiç auto-close yok)
@@ -514,7 +514,7 @@ Setup:
 
 Temel Özellikler:
 
-  Multi-Platform   iOS, Android, Backend, Frontend  -  otomatik tespit
+  Multi-Platform   iOS, Android, Backend, Web  -  otomatik tespit
   Build Queue      xcodebuild/Gradle lock file ile seri  -  parallel güvenli
   Stack Aware      iOS/Android/Python/Node/Go/Docker algılanır, etkin stack plugin'inin skilleri kullanılır
   Det. Gates       AI review'dan ÖNCE build + lint + test + secret scan
@@ -554,7 +554,7 @@ Quality & Telemetry (advisory, default açık  -  prefs.global.* ile kapatılabi
   /multi-agent:autopilot "LoginView dark mode fix"               # iOS
   /multi-agent "Add pagination to /api/users endpoint"           # Backend
   /multi-agent "Fix bottom nav recomposition in HomeScreen"      # Android
-  /multi-agent "Responsive layout broken on tablet"              # Frontend, Kısa seç
+  /multi-agent "Responsive layout broken on tablet"              # Web, Kısa seç
 
   # Sadece mevcut diff'i review et
   /multi-agent:review

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

@@ -15,9 +15,9 @@ Two-axis language preference for the pipeline:
 | `promptLanguage` | Interactive prompts during a pipeline run (account picker, project picker, dev-context picker, base-branch picker, branch-name picker, maturity ack, channels picker, Phase 5 test prompt, Phase 6 local-checkout prompt) | `prefs.global.promptLanguage` | **Fixed to `en`**  -  never toggled by this skill |
 | `outputLanguage` | Assistant's explanations, status updates, error messages, and pipeline-generated reports rendered to the user (NOT external payloads) | `prefs.global.outputLanguage` | Toggled by this skill |
 
-**Why promptLanguage is fixed:** it governs the picker's structural chrome only  -  `AskUserQuestion` `label` (button text) and `header` (chip), host error UI, and internal contract identifiers. Those stay English so tooling reads the same across CLIs. Everything a user actually reads follows `outputLanguage`, including the picker `question` and each option's `description`, per the canonical per-field matrix in `multi-agent-refs/rules.md`. A picker whose question is English on a Turkish run is a bug, not the contract.
+**Why promptLanguage is fixed:** it governs the picker's structural chrome only  -  the `AskUserQuestion` `header` chip, host error UI, and internal contract identifiers. The chip stays English because it is capped at 12 characters and most Turkish equivalents overflow it. Everything a user actually reads follows `outputLanguage`: the picker `question`, each option's `label`, and each option's `description`, per the canonical per-field matrix in `multi-agent-refs/rules.md`. A picker whose question or buttons are English on a Turkish run is a bug, not the contract. The host's own **Other** row is injected by the CLI and stays English on every run; nothing in the pipeline can localize it.
 
-**Always English regardless of either field**: commit messages, PR titles/bodies, Jira comments, wiki pages, reviewer/triage system prompts, agent-log.md payloads, confirmation / error UI exposed by the CLI host.
+**Always English regardless of either field**: commit messages, PR title prefixes (`feat:`, `fix:`), branch names, code identifiers, file paths, `agent-state.json` values, `agent-log.md` payloads, reviewer/triage system prompts, and confirmation / error UI exposed by the CLI host. PR descriptions, Jira comments, GitHub issue comments and wiki/Confluence page **bodies** follow `outputLanguage`  -  they are written for a human reader, per the `rules.md` matrix.
 
 **Follows outputLanguage (localized at install/toggle time)**: the slash-command picker `description` shown by the CLI host autocomplete. Repo and npm files always keep the English `description:`; files shipping a `description-tr:` line get swapped in the INSTALLED `~/.claude/commands/multi-agent/` tree by `localize-commands.mjs` (reversible via a `description-en:` sidecar). `/multi-agent:sync` restores English before mirroring back to the repo.
 
@@ -109,5 +109,5 @@ Render in the **new** outputLanguage:
 
 - `setup.md` Step 0  -  first-run language picker (asks only outputLanguage; promptLanguage seeded as `en`)
 - `prefs.schema.json`  -  `global.promptLanguage` (fixed `"en"`) and `global.outputLanguage` definitions
-- `phase-5-test.md`, `phase-6-commit.md`  -  interactive prompts follow the per-field matrix: `question` + `description` in `outputLanguage`, `label` + `header` English
+- `phase-5-test.md`, `phase-6-commit.md`  -  interactive prompts follow the per-field matrix: `question` + `label` + `description` in `outputLanguage`, `header` English
 - `help.md`  -  reads outputLanguage to render its own help text

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

@@ -6,7 +6,7 @@ allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdat
 
 # multi-agent local  -  Full Pipeline, Local Branch
 
-> **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".
 
 The full pipeline in normal mode (Plan Approval Gate + parallel review + triage included), running on the **current branch with no worktree**. Dedicated alias for the `multi-agent "task" --local` flag form. Phase 5 (User Test) is skipped because there is no worktree to check the change out from; the other seven phases all run.
 

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

@@ -9,7 +9,7 @@ allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdat
 
 **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 full pipeline **without a worktree** and **with every confirmation skipped**. Phase 5 (User Test) does not run (no worktree to check out from, and no interaction), so 7 phases execute. The `autopilot + local` combination  -  vs `/multi-agent:autopilot` the only difference is no worktree (work stays on the current branch); vs `/multi-agent:local` the only difference is zero interaction.
 

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

@@ -27,12 +27,12 @@ audit trail and metrics corpus at the log root are always preserved.
 2. **First confirmation**  -  native `AskUserQuestion` picker (no typed keyword),
    in `outputLanguage`, including the dry-run counts:
    - `question`: "Wipe the listed worktrees, branches, and counter?"
-   - `header`: "Purge" · `options`: `{ label: "Continue", description: "Proceed to the final confirmation" }`, `{ label: "Cancel", description: "Abort, change nothing" }`
+   - `header`: "Purge" (English, <=12 chars) · `options` (label + description in `outputLanguage`; the names below are the option SEMANTICS, not strings to print): option 1 "Continue"  -  proceed to the final confirmation; option 2 "Cancel"  -  abort, change nothing
    - **Cancel** → exit.
 
 3. **Second confirmation** (paranoia gate)  -  a second `AskUserQuestion` picker:
    - `question`: "This is irreversible. Permanently wipe every worktree, branch, and state now?" (`outputLanguage`)
-   - `header`: "Confirm" · `options`: `{ label: "Purge permanently", description: "Delete all worktrees, branches, and the counter" }`, `{ label: "Cancel", description: "Abort, change nothing" }`
+   - `header`: "Confirm" (English, <=12 chars) · `options` (label + description in `outputLanguage`; the names below are the option SEMANTICS, not strings to print): option 1 "Purge permanently"  -  delete all worktrees, branches, and the counter; option 2 "Cancel"  -  abort, change nothing
    - Anything other than **Purge permanently** → cancel.
 
 4. **Remote branches**  -  ask once whether to delete the remote branches too;

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

@@ -6,7 +6,7 @@ allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdat
 
 # multi-agent resume-local  -  Take Existing Branch Work Through the Pipeline Tail
 
-> **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".
 
 You already did the work locally  -  wrote code on the current branch and maybe tested it by hand, or committed it outside the pipeline entirely. (As of v14.0.0 a Short run reviews its own output, so this command is for work that had no pipeline run behind it, not a patch for a mode that skipped review.) `/multi-agent:resume-local` picks up from there and runs the **pipeline tail** over that existing local work in one command: parallel review, a build + test success gate, commit/push + PR, then the technical analysis and a **Jira comment with test scenarios**. It does NOT re-develop  -  Analysis / Planning / Dev (phases 1-3) are intentionally skipped; the diff already on the branch IS the input.
 
@@ -34,7 +34,7 @@ You already did the work locally  -  wrote code on the current branch and maybe
 
 ```
 Phase 0: Init          → project/branch detect, resolve base + diff (work-already-done), Jira id, state (NO worktree)
-Phase 4: Review        → deterministic gates + parallel review (Fable + Sonnet) + Fable triage
+Phase 4: Review        → deterministic gates + parallel review (Fable + Opus + Sonnet) + Fable triage
 Phase 5: Build+Test    → stack-aware build gate + run existing tests; SUCCESS required (automated, not the interactive user-test)
 Phase 6: Commit        → commit remaining local changes + push + open PR if none exists
 Phase 7: Report        → technical analysis + Jira comment with test scenarios (channels: Jira / PR / Confluence / Wiki)
@@ -52,10 +52,10 @@ Phases 1-3 (Analysis / Planning / Dev) are skipped by design  -  `ship` treats t
 
 ## Phase execution (reuse the existing phase contracts)
 
-- **Phase 4 Review** - run per `$HOME/.claude/multi-agent-refs/phases/phase-4-review.md` against the resolved diff: deterministic gates (Step 1.x), stack-specific parallel reviewers (Fable + Sonnet on Claude Code; GPT + Opus + Sonnet on Copilot CLI), Fable triage → `triage.accepted`. Blocking/important accepted findings:
+- **Phase 4 Review** - run per `$HOME/.claude/multi-agent-refs/phases/phase-4-review.md` against the resolved diff: deterministic gates (Step 1.x), stack-specific parallel reviewers (Fable + Opus + Sonnet on Claude Code; GPT + Opus + Sonnet on Copilot CLI), Fable triage → `triage.accepted`. Blocking/important accepted findings:
   - interactive: present them and ask (`AskUserQuestion`) whether to fix now (loop back through a minimal Phase-3-style TDD fix) or proceed;
   - `autopilot` (or `prefs.global.resumeLocal.autoFix == true`): auto-fix accepted blocking/important findings, then re-review the fix, before advancing.
-- **Phase 5 Build+Test** - the **automated success gate** (this is what "build+test success" means here; the interactive device user-test is `/multi-agent:manual-test`). Stack-aware: build via `figma-config.build` (iOS scheme / Android gradle / detected backend/frontend build) and run the existing test suite if present (`swift test` / `xcodebuild test` / `./gradlew test` / `pytest` / `npm test` / `vitest`). Require success to advance; on failure, surface logs and (interactive) stop or (autopilot) attempt a bounded fix loop. **If the repo has no tests, report "no tests present" - never fabricate test results.**
+- **Phase 5 Build+Test** - the **automated success gate** (this is what "build+test success" means here; the interactive device user-test is `/multi-agent:manual-test`). Stack-aware: build via `figma-config.build` (iOS scheme / Android gradle / detected backend/web build) and run the existing test suite if present (`swift test` / `xcodebuild test` / `./gradlew test` / `pytest` / `npm test` / `vitest`). Require success to advance; on failure, surface logs and (interactive) stop or (autopilot) attempt a bounded fix loop. **If the repo has no tests, report "no tests present" - never fabricate test results.**
 - **Phase 6 Commit/PR** - per `$HOME/.claude/multi-agent-refs/phases/phase-6-commit.md`: stage + commit any remaining local changes with a conventional message (`{type}(scope): desc [{JIRA_KEY}-{id}]`), push, and open a PR **only if one does not already exist** for the branch. PR body per `$HOME/.claude/multi-agent-refs/rules.md "External System Outputs"` and `$HOME/.claude/rules/git-conventions.md` - `Ref: #N` / `Related: #N`, never `Closes/Fixes/Resolves`; NO AI/bot attribution anywhere.
 - **Phase 7 Report** - per `$HOME/.claude/multi-agent-refs/phases/phase-7-report.md` + `channels.md`: produce the **technical analysis** and **test scenarios**, then post to the configured channels. Default content for `ship`: a Jira **comment** carrying the technical analysis + the test scenarios (and, when the PR was opened, the PR description). Every body runs through the humanizer; bot/tool/AI signatures are FORBIDDEN in comments.
 

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

@@ -1,6 +1,6 @@
 ---
-description: "Run parallel review on a branch's diff or a Pull Request: 2 models on Claude Code (Fable + Sonnet), 3 models on Copilot CLI (GPT + Opus + Sonnet). On PR input, posts per-finding inline comments and sets approve/needs-work review state. Use when a branch diff or a pull request needs reviewing before it merges."
-description-tr: "Bir branch diff'i veya Pull Request üzerinde paralel review koşar: Claude Code'da 2 model (Fable + Sonnet), Copilot CLI'da 3 model (GPT + Opus + Sonnet). PR girdisinde bulgu başına inline yorum atar ve approve/needs-work durumunu işaretler."
+description: "Run parallel review on a branch's diff or a Pull Request: 3 models on Claude Code (Fable + Opus + Sonnet), 3 models on Copilot CLI (GPT + Opus + Sonnet). On PR input, posts per-finding inline comments and sets approve/needs-work review state. Use when a branch diff or a pull request needs reviewing before it merges."
+description-tr: "Bir branch diff'i veya Pull Request üzerinde paralel review koşar: Claude Code'da 3 model (Fable + Opus + Sonnet), Copilot CLI'da 3 model (GPT + Opus + Sonnet). PR girdisinde bulgu başına inline yorum atar ve approve/needs-work durumunu işaretler."
 argument-hint: "[#N | repo#N | PR-URL | branch]  -  optional: PR by number/URL, repo+number, or local branch. Supports GitHub and Bitbucket Server URLs. If omitted (interactive), open GitHub + Bitbucket PRs are listed for multi-select; autopilot falls back to the current branch."
 ---
 
@@ -175,7 +175,7 @@ Scope note: a guide governs only files under its own directory  -  a guide found
 
 ### 3. Launch parallel reviewers  -  host-CLI dependent
 
-**Claude Code (2 in parallel):**
+**Claude Code (3 in parallel):**
 - Agent 1: `claude-fable-5` → security + architecture
 - Agent 2: `claude-sonnet-5` → general quality
 
@@ -242,18 +242,19 @@ Optional opt-out prompt (interactive mode only; autopilot skips and posts):
 ```
 question (outputLanguage): "PR #{N} için review action gönderilsin mi?"
 header   (English):        "Post review"
-options:
-  - label "Post review",  description (outputLanguage): "Bulgular varsa inline yorum + Request changes; yoksa Approve"
-  - label "Chat only",    description (outputLanguage): "Sadece sohbet özetiyle yetin, PR'a dokunma"
-default: option 1 (Post review)
+options (label + description in outputLanguage; semantics, not literals):
+  - option 1  -  "Post review": inline comments + Request changes when there are
+                 findings, Approve when there are none
+  - option 2  -  "Chat only": leave the PR untouched, the chat summary is enough
+default: option 1
 ```
 
 Defaults:
-- Interactive mode: prompt with default `Post review`
+- Interactive mode: prompt with default option 1
 - Autopilot mode: auto-post (no prompt)
 - `--no-comment` / `--no-post` flag: skip the post entirely
 
-If the user picks "Post review":
+If the user picks option 1 (post the review):
 
 ```bash
 bash $HOME/.claude/lib/post-pr-review.sh "$TASK_ID"

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

@@ -16,7 +16,7 @@ Read `$HOME/.claude/multi-agent-refs/analysis/review.md` and execute it:
 
 1. **Resolve** the document from a local path, a Confluence URL or `pageId`, or a Jira key. With no argument, offer the recent analyses from `~/Desktop/multiAgentAnalysis/` and from each selected repo's `analysis/`, newest first.
 2. **Deterministic gates first**: `validate-analysis-doc.mjs` on the document, and `build-references.mjs --check` when the run's state JSON is available (`--state`, or a fresh analysis). Their output is reported verbatim, before any model reads the document. A finding a script already proves does not need an opinion.
-3. **Parallel model review** against the rubric (buildability, evidence, spine, altitude, admitted gaps, contradiction), CLI-aware: 2 models on Claude Code, 3 on Copilot CLI.
+3. **Parallel model review** against the rubric (buildability, evidence, spine, altitude, admitted gaps, contradiction), CLI-aware: 3 models on Claude Code, 3 on Copilot CLI.
 4. **Fable triage** into Blocker / Important / Suggestion, dropping duplicates and anything the document answers elsewhere.
 5. **Report**, naming the profile it judged against and, explicitly, what was NOT checked.
 6. **Output** on request only: chat (default), Confluence comment, Jira comment, or a `-review.md` beside the document.

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

@@ -24,7 +24,7 @@ Ask BEFORE anything else, so every subsequent setup prompt and the rest of the p
 
 | Axis | What it controls | Configurable? |
 |---|---|---|
-| `promptLanguage` | The picker's structural UI chrome only: `AskUserQuestion` `label` (button text) and `header` (chip), plus host error UI and internal contract identifiers | **No  -  fixed to `en`.** Button and chip text stays English so tooling reads the same across CLIs. |
+| `promptLanguage` | Picker chrome only: the `AskUserQuestion` `header` chip, host error UI, internal contract identifiers | **No  -  fixed to `en`.** The chip is capped at 12 chars, which most Turkish equivalents overflow. |
 | `outputLanguage` | The assistant's non-interactive explanations, status updates, error messages, and pipeline-generated reports rendered to the user | Yes  -  set here and changeable later via `/multi-agent:language <en\|tr>` |
 
 `promptLanguage` is seeded as `"en"` and never offered to the user. **External payloads always stay English** (commits, PR titles/bodies, Jira comments, wiki content, reviewer/triage prompts, agent-log.md).
@@ -53,21 +53,20 @@ Select (1-2):
 
 From this point forward, every prompt in Steps 1-6 below follows the canonical
 per-field matrix in `$HOME/.claude/multi-agent-refs/rules.md` ("Language Application"):
-the `question` text and each option's `description` render in `outputLanguage`, while
-`label` and `header` stay English. The wizard's status text and post-setup summary
-render in `outputLanguage`. External payloads remain English.
+`question`, `label` and `description` render in `outputLanguage`; `header` stays
+English. Wizard status and the post-setup summary follow `outputLanguage`. External
+payloads remain English.
 
 > This paragraph used to say every prompt renders in English "per the fixed
 > `promptLanguage`", which contradicted the canonical matrix and produced
 > half-English pickers on Turkish runs: `promptLanguage` governs only the button and
 > chip chrome, never the question a user reads.
 
-### Step 0.5  -  Credential Backend Check
-
-Before discovery, verify the platform's credential backend is available:
+### Step 0.5  -  Dependency check
 
 ```bash
 ~/.claude/lib/credential-store.sh doctor
+command -v pdftotext >/dev/null 2>&1 || echo "pdftotext: MISSING"
 ```
 
 | Output | Action |
@@ -76,6 +75,7 @@ Before discovery, verify the platform's credential backend is available:
 | Linux: `secret-tool ✗ MISSING` | Prompt: `sudo apt install libsecret-tools` (Debian/Ubuntu) or `sudo dnf install libsecret` (Fedora). Re-run setup after install. |
 | Windows: `CredentialManager ✗ MISSING` | Prompt: `Install-Module CredentialManager -Scope CurrentUser -Force` in an elevated PowerShell. Re-run setup. |
 | Platform `unknown` | Halt  -  credential storage cannot proceed. |
+| `pdftotext: MISSING` | Advisory. Print `brew install poppler` (or distro equivalent), continue. `.docx` needs nothing. |
 
 ### Credential Key Naming Rule
 
@@ -316,7 +316,7 @@ Expired / rejected token (401 / 403 mid-run)  -  the Expired-token decision from
   Select:
 ```
 
-Render `question` + `description` in `outputLanguage`; `label` + `header` English. The picked label is a choice, never the secret  -  the value still enters via Step B clipboard.
+Render `question` + `label` + `description` in `outputLanguage`; `header` English. Names below are option semantics, not strings to print. The picked option is a choice, never the secret: the value enters via Step B clipboard.
 
 - **Skip** (missing `[2]` / expired `[3]`) → skip semantics. During setup: `keychainMapping` stays `null`. During Phase 0 / mid-run: abort that service's contribution, warn and continue if non-critical, halt if critical (e.g. Jira token for Jira input).
 - **Add now** / **Regenerate** → proceed to Step B (clipboard save). Regenerate reuses the same `{KEY_NAME}`.
@@ -835,6 +835,6 @@ Stack skills ship as versioned plugins in the `{owner}/multi-agent-plugins` mark
    - `requirements.txt` / `pyproject.toml` / server `package.json` → `ai-backend-toolkit`
    - **no clear marker → default `ai-ios-toolkit`**
    `ai-common-toolkit@multi-agent-plugins` and `ai-analyst-toolkit@multi-agent-plugins` are always set `true` alongside the stack plugin: neither is stack-specific.
-3. Report the enabled set. To change later, run `/multi-agent:stack <ios|android|frontend|backend|...>` in the repo. Pipeline Phase 1 auto-detects the stack for its own routing regardless of enablement.
+3. Report the enabled set. To change later, run `/multi-agent:stack <ios|android|web|backend|...>` in the repo. Pipeline Phase 1 auto-detects the stack for its own routing regardless of enablement.
 
 The marketplace repo name (`multi-agent-plugins`) is generic; a different org points `{owner}` at its own fork - nothing in the pipeline is coupled to a specific account.

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

@@ -1,7 +1,7 @@
 ---
 description: "Select the active stack(s) for this repo by enabling the matching marketplace plugin(s) in .claude/settings.json. Multi-select: pass several stacks (ios backend) or pick them in the native picker. Use when a repo's stack changed or the wrong plugins are enabled for it."
 description-tr: "Bu repo için aktif stack'leri seçer: eşleşen marketplace plugin'lerini .claude/settings.json'da etkinleştirir. Çoklu seçim: birden fazla stack yazılabilir (ios backend) ya da native picker'dan seçilir."
-argument-hint: "[ios|android|frontend|web|backend|mobile|fullstack|all ...]"
+argument-hint: "[ios|android|web|frontend|backend|mobile|fullstack|all ...]"
 allowed-tools: Bash, Read, Edit, Write, AskUserQuestion
 ---
 
@@ -22,8 +22,8 @@ This replaces the old `stack-swap.sh` mechanic that physically moved skill direc
 /multi-agent:stack android         # Compose toolkit + common
 /multi-agent:stack mobile          # alias: ios + android + common
 /multi-agent:stack backend         # Python / Node spec-driven toolkit + common
-/multi-agent:stack frontend        # React / TSX toolkit + common (alias: web)
-/multi-agent:stack fullstack       # alias: frontend + backend + common
+/multi-agent:stack web        # React / TSX toolkit + common (alias: frontend)
+/multi-agent:stack fullstack       # alias: web + backend + common
 /multi-agent:stack all             # all four stack toolkits + common
 ```
 
@@ -33,7 +33,7 @@ This replaces the old `stack-swap.sh` mechanic that physically moved skill direc
 |---|---|
 | `ios` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-ios-toolkit` |
 | `android` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-android-toolkit` |
-| `frontend` / `web` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-frontend-toolkit` |
+| `web` / `frontend` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-frontend-toolkit` |
 | `backend` | `ai-common-toolkit`, `ai-analyst-toolkit`, `ai-backend-toolkit` |
 | `mobile` | common + `ai-ios-toolkit` + `ai-android-toolkit` |
 | `fullstack` | common + `ai-frontend-toolkit` + `ai-backend-toolkit` |
@@ -46,10 +46,10 @@ Multiple args union their plugin sets: `ios backend` → common + iOS + backend.
 1. **No arg → native multi-select picker.** Read `.claude/settings.json` (repo) + `~/.claude/settings.json` (global) to learn the current state, then ask with `AskUserQuestion` (`multiSelect: true`) - NEVER a numbered text menu:
    - `question` (in `outputLanguage`): which stacks should be active in this repo, noting the currently enabled ones
    - `header`: "Stacks" (English, UI contract)
-   - `options` (4): `ios` / `android` / `frontend (web)` / `backend`, each `description` (in `outputLanguage`) naming the plugin it enables and marking the ones already enabled with "(currently on)" / "(şu an açık)"
-   - Map each selected label back to its canonical arg before step 2: the token before any parenthesis (`frontend (web)` → `frontend`).
+   - `options` (4): `ios` / `android` / `web` / `backend`, each `description` (in `outputLanguage`) naming the plugin it enables and marking the ones already enabled with "(currently on)" / "(şu an açık)"
+   - Map each selected label back to its canonical arg before step 2: the token before any parenthesis.
    - Empty selection or cancel → **status mode**: print the currently enabled `@multi-agent-plugins` plugins and exit without modifying anything. Status mode never runs the Implementation block below - that block is enable-mode only.
-2. **Arg(s) present → enable mode.** Accept multiple space-separated stacks. Resolve each through the alias table (`web`→`frontend`, `mobile`→`ios android`, `fullstack`→`frontend backend`, `all`→every stack), union the plugin sets, then write the **current repo's** `.claude/settings.json`.
+2. **Arg(s) present → enable mode.** Accept multiple space-separated stacks. Resolve each through the alias table (`frontend`→`web`, `mobile`→`ios android`, `fullstack`→`web backend`, `all`→every stack), union the plugin sets, then write the **current repo's** `.claude/settings.json`.
 3. **Write rules:**
    - every plugin in the union is set to `true`
    - every stack toolkit **not** in the union is set to `false` (leave non-`@multi-agent-plugins` entries untouched)
@@ -74,7 +74,7 @@ COMMON="ai-common-toolkit@${MP}"
 ANALYST="ai-analyst-toolkit@${MP}"
 IOS="ai-ios-toolkit@${MP}"
 ANDROID="ai-android-toolkit@${MP}"
-FRONTEND="ai-frontend-toolkit@${MP}"
+WEB="ai-frontend-toolkit@${MP}"
 BACKEND="ai-backend-toolkit@${MP}"
 
 # Enable-mode only: with zero args the write rules below would set every stack
@@ -91,13 +91,12 @@ for ARG in "$@"; do
   case "$ARG" in
     ios)              ON="$ON $IOS" ;;
     android)          ON="$ON $ANDROID" ;;
-    frontend|web)     ON="$ON $FRONTEND" ;;
-    "frontend (web)") ON="$ON $FRONTEND" ;;
+    web|frontend)     ON="$ON $WEB" ;;
     backend)          ON="$ON $BACKEND" ;;
     mobile)           ON="$ON $IOS $ANDROID" ;;
-    fullstack)        ON="$ON $FRONTEND $BACKEND" ;;
-    all)              ON="$ON $IOS $ANDROID $FRONTEND $BACKEND" ;;
-    *) echo "Unknown stack '$ARG'. One of: ios android mobile backend frontend web fullstack all"; exit 1 ;;
+    fullstack)        ON="$ON $WEB $BACKEND" ;;
+    all)              ON="$ON $IOS $ANDROID $WEB $BACKEND" ;;
+    *) echo "Unknown stack '$ARG'. One of: ios android mobile backend web fullstack all"; exit 1 ;;
   esac
 done
 ```

package/pipeline/lib/extract-conventions.sh

@@ -6,7 +6,7 @@
 #
 # Usage:
 #   extract-conventions.sh <repo-path> <platform>
-# Platform: ios | android | backend | frontend
+# Platform: ios | android | backend | web  ('frontend' accepted as the pre-rename alias)
 #
 # Output schema (per bucket):
 #   { pattern, example, confidence, evidenceFiles[], alternativeCandidates[] }
@@ -28,9 +28,10 @@ if [ ! -d "$REPO_PATH" ]; then
 fi
 
 case "$PLATFORM" in
-  ios|android|backend|frontend) ;;
+  frontend) PLATFORM=web ;;
+  ios|android|backend|web) ;;
   *)
-    echo "extract-conventions: invalid platform: $PLATFORM (expected ios|android|backend|frontend)" >&2
+    echo "extract-conventions: invalid platform: $PLATFORM (expected ios|android|backend|web)" >&2
     exit 1
     ;;
 esac
@@ -100,7 +101,7 @@ scan_roots() {
         [ -d "$REPO_PATH/$d" ] && roots+=("$REPO_PATH/$d")
       done
       ;;
-    frontend)
+    web)
       for d in src app components features lib hooks pages; do
         [ -d "$REPO_PATH/$d" ] && roots+=("$REPO_PATH/$d")
       done
@@ -341,7 +342,7 @@ bucket_folder_structure() {
         empty_bucket
       fi
       ;;
-    frontend)
+    web)
       local feats
       feats=$(run_find -type d -name 'features' 2>/dev/null | head -10)
       if [ -z "$feats" ]; then
@@ -439,7 +440,7 @@ bucket_state_holder() {
     backend)
       empty_bucket
       ;;
-    frontend)
+    web)
       # Look for hooks (useXxx) or stores
       local files
       files=$(run_find -type f \( -name '*.ts' -o -name '*.tsx' -o -name '*.js' -o -name '*.jsx' \) 2>/dev/null || true)
@@ -480,7 +481,7 @@ bucket_view_naming() {
     backend)
       empty_bucket
       ;;
-    frontend)
+    web)
       local files
       files=$(run_find -type f \( -name '*.tsx' -o -name '*.jsx' \) 2>/dev/null || true)
       if [ -z "$files" ]; then empty_bucket; return; fi
@@ -522,7 +523,7 @@ bucket_navigator_naming() {
     backend)
       empty_bucket
       ;;
-    frontend)
+    web)
       empty_bucket
       ;;
   esac
@@ -542,7 +543,7 @@ bucket_usecase_naming() {
     backend)
       emit_naming_bucket "*.py" "" "Service" "Handler"
       ;;
-    frontend)
+    web)
       # useFooQuery / useFooMutation as a proxy
       local files cnt sample
       files=$(run_find -type f \( -name '*.ts' -o -name '*.tsx' \) 2>/dev/null || true)
@@ -573,7 +574,7 @@ bucket_repository_naming() {
     backend)
       emit_naming_bucket "*.py" "" "Repository" "Dao"
       ;;
-    frontend)
+    web)
       emit_naming_bucket "*.ts" "" "Api" "Client"
       ;;
   esac
@@ -593,7 +594,7 @@ bucket_dto_naming() {
     backend)
       emit_naming_bucket "*.py" "" "Response" "Request" "In" "Out"
       ;;
-    frontend)
+    web)
       emit_naming_bucket "*.ts" "" "Dto" "Response" "Request"
       ;;
   esac
@@ -640,7 +641,7 @@ bucket_ui_state_model() {
       empty_bucket
       return
       ;;
-    frontend)
+    web)
       local hook_files
       hook_files=$(run_find -type f \( -name 'use*.ts' -o -name 'use*.tsx' \) 2>/dev/null | head -50 || true)
       if [ -z "$hook_files" ]; then empty_bucket; return; fi
@@ -689,7 +690,7 @@ bucket_test_method_naming() {
     backend)
       test_files=$(run_find -type f -name 'test_*.py' 2>/dev/null | head -20 || true)
       ;;
-    frontend)
+    web)
       test_files=$(run_find -type f \( -name '*.test.ts' -o -name '*.test.tsx' -o -name '*.spec.ts' -o -name '*.spec.tsx' \) 2>/dev/null | head -20 || true)
       ;;
   esac
@@ -709,7 +710,7 @@ bucket_test_method_naming() {
       backend)
         underscore_count=$((underscore_count + $(count_matches -E '^def +test_[a-z0-9_]+' "$f")))
         ;;
-      frontend)
+      web)
         it_count=$((it_count + $(count_matches -E "(it|test)\\(['\"\`]" "$f")))
         ;;
     esac
@@ -739,7 +740,7 @@ bucket_test_method_naming() {
         empty_bucket
       fi
       ;;
-    frontend)
+    web)
       if [ "$it_count" -gt 0 ]; then
         emit_bucket "it/test sentence" "it('returns error when email invalid', ...)" "$(confidence_for "$it_count")" "$evidence_json" '["describe-it","test-only"]'
       else
@@ -837,7 +838,7 @@ bucket_accessibility_identifier() {
         empty_bucket
       fi
       ;;
-    frontend)
+    web)
       local files ids
       files=$(run_find -type f \( -name '*.tsx' -o -name '*.jsx' \) 2>/dev/null | head -100 || true)
       if [ -z "$files" ]; then empty_bucket; return; fi
@@ -901,7 +902,7 @@ bucket_localization_key() {
       ;;
     backend)
       empty_bucket; return ;;
-    frontend)
+    web)
       local json_files
       json_files=$(run_find -type f -path '*i18n*' -name '*.json' 2>/dev/null | head -5 || true)
       if [ -n "$json_files" ]; then
@@ -1002,7 +1003,7 @@ bucket_di_registration() {
         empty_bucket
       fi
       ;;
-    frontend)
+    web)
       files=$(run_find -type f \( -name '*.tsx' -o -name '*.ts' \) 2>/dev/null || true)
       if [ -z "$files" ]; then empty_bucket; return; fi
       local context_count zustand_count hook_count