@mmerterden/multi-agent-pipeline 16.10.0 → 16.11.0

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.
 
@@ -55,7 +55,7 @@ Phases 1-3 (Analysis / Planning / Dev) are skipped by design  -  `ship` treats t
 - **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:
   - 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

@@ -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/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/commands/multi-agent/update/SKILL.md

@@ -184,7 +184,7 @@ A git clone of the pipeline repo is a maintainer workspace, kept in sync by `/mu
 ```
 Current: v15.6.0   Latest: v15.6.1
   -> npm pack @{npm-scope}/multi-agent-pipeline@15.6.1
-  -> node install.js --all (53 commands, 245 scripts, 208 skills)
+  -> node install.js --all (53 commands, 263 scripts, 210 skills)
   -> migrate-prefs.mjs (0 changes  -  already v2.6.0)
 
 ✓ Updated: v15.6.0 → v15.6.1

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

package/pipeline/multi-agent-refs/_account-picker.md

@@ -31,7 +31,7 @@ First step of every `multi-agent` flow **that touches a remote provider**.
    - Breadcrumb (per `$HOME/.claude/multi-agent-refs/picker-contract.md` Step narration): before the question, print the narrator line `<localized: "Step 1/N: account selection">` (`N` = total Phase 0 steps for the active flow).
    - `header`: "Account" (English chip)
    - `question`: `<localized: "Which account should this run use?">`
-   - one option per account: `label` = account label (English), `description` = providers in `outputLanguage`
+   - one option per account: `label` = the account name verbatim (a proper noun, never translated), `description` = providers in `outputLanguage`
    ```
    [1/N] {question}
      > {label}   ({providers})

package/pipeline/multi-agent-refs/_dev-context.md

@@ -48,9 +48,9 @@ Selects extra repos the pipeline may touch beyond the primary repo(s)  -  typica
 
 4. **Empty submit**  -  user picks nothing → `extras=[]`, primary repo(s) only.
 
-## Frontend repos  -  `frontendRepos`
+## Web repos  -  `webRepos`
 
-Frontend repos are rarely submodules of the app repo, so submodule detection never finds them. `prefs.projects[<key>].frontendRepos[]` is the primary source for them and is merged into the candidate list alongside the detected submodules. Only `/multi-agent:analysis` used to read this key, which meant the pipeline's own dev-context picker could not offer a frontend repo at all.
+Web repos are rarely submodules of the app repo, so submodule detection never finds them. `prefs.projects[<key>].webRepos[]` (or the pre-rename `frontendRepos[]`) is the primary source for them and is merged into the candidate list alongside the detected submodules. Only `/multi-agent:analysis` used to read this key, which meant the pipeline's own dev-context picker could not offer a web repo at all.
 
 ## Pref override  -  `editableRelatedRepos`
 

package/pipeline/multi-agent-refs/_input-parser.md

@@ -6,7 +6,7 @@ description: "Internal  -  input type detection for multi-agent dispatcher."
 
 The top-level `multi-agent` command classifies user arguments per the rules below.
 
-> **Language**: Schema reference only  -  no user-facing text. Picker `label` + `header` always English (`promptLanguage` is locked to `"en"`); `question` + `description` follow `outputLanguage` per the `rules.md` matrix. Commit messages, branch names and PR titles stay English; PR/Jira/Confluence **bodies** follow `outputLanguage`.
+> **Language**: Schema reference only  -  no user-facing text. Picker `header` is always English (`promptLanguage` is locked to `"en"`); `question` + `label` + `description` follow `outputLanguage` per the `rules.md` matrix. Commit messages, branch names and PR titles stay English; PR/Jira/Confluence **bodies** follow `outputLanguage`.
 
 ## Type Table
 

package/pipeline/multi-agent-refs/analysis/evidence.md

@@ -4,7 +4,7 @@
 
 ### Phase 1 - Fetch & extract (parallel)
 
-For each entry in `state.analysisSpec.contextLinks[]`, fan out by `type`. Entries tagged `binding: true` (Q5 inputs) land in `evidence.standards[]` regardless of underlying source type so Section 7 can iterate them as one set.
+For each entry in `state.analysisSpec.contextLinks[]`, fan out by `type`. Entries tagged `binding: true` (Standards-question inputs) land in `evidence.standards[]` regardless of underlying source type so Section 7 can iterate them as one set.
 
 | type | Command | Output bucket |
 |------|---------|---------------|
@@ -12,7 +12,7 @@ For each entry in `state.analysisSpec.contextLinks[]`, fan out by `type`. Entrie
 | confluence | `~/.claude/lib/fetch-confluence.sh <url>` | `state.analysisSpec.evidence.confluence[]` |
 | figma | **MUST** establish the Figma access tier per Locked decision #12. Tier 1 (preferred): call `mcp__claude_ai_Figma__get_design_context` (primary), `mcp__claude_ai_Figma__get_screenshot`, `mcp__claude_ai_Figma__get_metadata` for every node ID; auth failure runs `authenticate` + `complete_authentication` then retries. Tier 2 (fallback): `GET https://api.figma.com/v1/files/{fileKey}/nodes?ids={nodeId}` for design context and `GET /v1/images/{fileKey}?ids={nodeId}&format=png&scale=2` for screenshots, with PAT from `~/.claude/lib/credential-store.sh get <logical-key>` (logical key = `prefs.global.keychainMapping.figma`); canonical component resolves via repo `*.figma.swift` / `*.figma.kt` mapping. Tier 3 (last resort): user-attached screenshot, `codeConnectSnippets: []`, forced Open Question. Capture each `CodeConnectSnippet` block verbatim when on Tier 1 (component name + modifier chain). **Annotation capture (when the project `figma-config` has `annotations.enabled`):** on Tier 1, walk the `annotations[]` the `get_design_context` payload returns for each node (read `label` / `labelMarkdown`); on Tier 2, run `~/.claude/lib/fetch-figma-annotations.sh --file-key <fileKey> --node-id <ids> --lang-prefixes <config.annotations.langPrefixes>`. Parse each annotation by the configured language prefixes (prefixed `TR:/EN:` wins, else line1/line2, else single) and persist to `annotations[]`. The annotation is the authoritative copy for its node (Locked 3); the visible text layer is a placeholder. Persist `state.figmaAccess.tier`. See Locked decision #12 and `$HOME/.claude/rules/figma-pipeline.md` "MUST: Figma access - 3-tier fallback chain". | `state.analysisSpec.evidence.figma[]` (records: `nodeId`, `screenshotUrl`, `codeConnectSnippets[]`, `tokens[]`, `textLayers[]`, `annotations[]`, `tier`; see `analysis-spec.schema.json`) |
 | jira | `gh api` or Jira REST API for issue summary | `state.analysisSpec.evidence.jira[]` |
-| document | `~/.claude/lib/fetch-document.sh <path-or-url>` (`.docx` via python3 stdlib, `.md` / `.txt` read directly, `.pdf` only when `pdftotext` exists). Exit `6` is a soft skip, not a failure: record the file with `fetched: false` so Section 21 still cites it as referenced-but-not-fetched. | `state.analysisSpec.evidence.documents[]`, or `evidence.standards[]` when `binding: true` |
+| document | `~/.claude/lib/fetch-document.sh <path-or-url>` (`.docx` via the python3 standard library  -  `python-docx` is never imported and must not be installed  -  `.md` / `.txt` read directly, `.pdf` only when `pdftotext` exists). Exit `6` is a soft skip, not a failure: record the file with `fetched: false` so Section 21 still cites it as referenced-but-not-fetched. | `state.analysisSpec.evidence.documents[]`, or `evidence.standards[]` when `binding: true` |
 | generic-doc | WebFetch on demand | `state.analysisSpec.evidence.confluence[]` (generic bucket) unless `binding: true` -> `evidence.standards[]` |
 | `local-file` | `Read` (no fetch) on tilde-expanded absolute path | `state.analysisSpec.evidence.standards[]` |
 | `wiki` | `git clone --depth 1 https://github.com/<owner>/<repo>.wiki.git /tmp/<repo>-wiki`, then `Read /tmp/<repo>-wiki/<PageName>.md` (`-` decoded back to space in PageName). Fallback chain: `gh api repos/<owner>/<repo>/contents/<file>.md` for repo-hosted docs if wiki repo is 404. | `state.analysisSpec.evidence.standards[]` |
@@ -61,7 +61,7 @@ After Phase 1 finishes, run a deeper scan per repo to enable Section 7's reuse-f
 | iOS | `Domains/`, `Common/`, `Core/`, `App/` |
 | Android | `app/src/`, `feature/`, `core/`, `common/` |
 | Backend | `src/`, `api/`, `services/` |
-| Frontend | `src/`, `app/`, `components/`, `features/`, `lib/` (override with `prefs.projects[<key>].frontendRoots[]`) |
+| Web | `src/`, `app/`, `components/`, `features/`, `lib/` (override with `prefs.projects[<key>].webRoots[]`, or the pre-rename `frontendRoots[]`) |
 
 Skip dirs (always): `.build`, `DerivedData`, `Pods`, `node_modules`, `.next`, `build/`, `.gradle`, `vendor/`.
 
@@ -91,7 +91,7 @@ If `wc -l < $CANDIDATES` exceeds 200, record `fetchWarnings += "feature-name too
 | tokens | `*Token` enums under `UIAssetTokens/Generated/` | `Theme.kt` / `tokens.ts` / `tailwind.config.*` |
 | localizationKeys | `LocalizationStringKeys.swift` public enum + cases | `strings.xml` keys / `i18n/*.json` keys |
 | testingIdentifiers | `ui-testing-identifiers.json` | `testTag` strings / `data-testid` constants |
-| analyticsEvents | Generated `AnalyticsEvents/*.swift` + `Analytics.logEvent\(` call sites | Equivalent Android / Frontend / Backend telemetry |
+| analyticsEvents | Generated `AnalyticsEvents/*.swift` + `Analytics.logEvent\(` call sites | Equivalent Android / Web / Backend telemetry |
 
 **Tagging rule** for each row: