@mmerterden/multi-agent-pipeline 16.10.0 → 16.11.0

package/pipeline/multi-agent-refs/conventions-defaults.md

@@ -34,7 +34,7 @@ Apply platform default + open Section 20 risk row
 | iOS | feature-first + clean arch | `Features/<Feature>/Sources/<Feature>/{Common,Data,Domain,Presentation}/` | Mirrors SwiftPM module boundaries; keeps each feature self-contained |
 | Android | feature module + clean arch | `feature/<feature>/src/main/java/<package>/{data,domain,ui}/` | Standard Now-in-Android pattern, aligns with Gradle module isolation |
 | Backend | layered | `src/{api,services,repositories,schemas,models}/<feature>/` | Standard FastAPI / Express layering, predictable for new contributors |
-| Frontend | feature folder | `src/features/<feature>/{components,hooks,api,types}/` | Standard Next.js / React feature-folder convention |
+| Web | feature folder | `src/features/<feature>/{components,hooks,api,types}/` | Standard Next.js / React feature-folder convention |
 
 ## C2 - Class Naming
 
@@ -45,7 +45,7 @@ Apply platform default + open Section 20 risk row
 | iOS | `<Feature>ViewModel` | `PassengerFlightViewModel` |
 | Android | `<Feature>ViewModel` | `PassengerFlightViewModel` |
 | Backend | not applicable | (services replace state holders) |
-| Frontend | `use<Feature>` hook | `usePassengerFlight` |
+| Web | `use<Feature>` hook | `usePassengerFlight` |
 
 ### C2b viewNaming
 
@@ -54,7 +54,7 @@ Apply platform default + open Section 20 risk row
 | iOS | `<Feature>View` | `PassengerFlightView` |
 | Android | `<Feature>Screen` | `PassengerFlightScreen` |
 | Backend | not applicable | |
-| Frontend | `<Feature>Page` | `PassengerFlightPage` |
+| Web | `<Feature>Page` | `PassengerFlightPage` |
 
 ### C2c navigatorNaming
 
@@ -63,7 +63,7 @@ Apply platform default + open Section 20 risk row
 | iOS | `<Feature>Coordinator` | `PassengerFlightCoordinator` | Conforms to `<Domain>Router` protocol if present |
 | Android | `<Feature>Navigator` | `PassengerFlightNavigator` | Compose Navigation destination |
 | Backend | not applicable | | |
-| Frontend | route file under `app/` | `app/passenger-flight/page.tsx` | Next.js App Router default |
+| Web | route file under `app/` | `app/passenger-flight/page.tsx` | Next.js App Router default |
 
 ### C2d useCaseNaming
 
@@ -72,7 +72,7 @@ Apply platform default + open Section 20 risk row
 | iOS | `<Verb><Feature>UseCase` | `FetchPassengerFlightUseCase` |
 | Android | `<Verb><Feature>UseCase` | `FetchPassengerFlightUseCase` |
 | Backend | `<Feature>Service` | `PassengerFlightService` |
-| Frontend | hook with side effect | `usePassengerFlightQuery` |
+| Web | hook with side effect | `usePassengerFlightQuery` |
 
 ### C2e repositoryNaming
 
@@ -81,7 +81,7 @@ Apply platform default + open Section 20 risk row
 | iOS | `<Feature>Repository` (protocol) + `<Feature>RepositoryImpl` (class) | `PassengerFlightRepository`, `PassengerFlightRepositoryImpl` |
 | Android | `<Feature>Repository` (interface) + `<Feature>RepositoryImpl` (class) | same |
 | Backend | `<Feature>Repository` | `PassengerFlightRepository` |
-| Frontend | `<feature>Api` | `passengerFlightApi` |
+| Web | `<feature>Api` | `passengerFlightApi` |
 
 ### C2f dtoNaming
 
@@ -90,7 +90,7 @@ Apply platform default + open Section 20 risk row
 | iOS | `<Feature>RequestDTO`, `<Feature>ResponseDTO` | `PassengerFlightRequestDTO`, `PassengerFlightResponseDTO` |
 | Android | `<Feature>Dto` | `PassengerFlightDto` |
 | Backend | Pydantic `<Feature>In`, `<Feature>Out` | `PassengerFlightIn`, `PassengerFlightOut` |
-| Frontend | TypeScript `<Feature>Dto` | `PassengerFlightDto` |
+| Web | TypeScript `<Feature>Dto` | `PassengerFlightDto` |
 
 ## C3 - UI State Model
 
@@ -99,7 +99,7 @@ Apply platform default + open Section 20 risk row
 | iOS | sealed enum | `enum PassengerFlightUIState { case loading, idle(...), error(...) }` |
 | Android | sealed interface | `sealed interface PassengerFlightUiState { data object Loading; data class Idle(...); data class Error(...) }` |
 | Backend | not applicable | services do not hold UI state |
-| Frontend | discriminated union | `type PassengerFlightState = { kind: 'loading' } | { kind: 'idle'; ... } | { kind: 'error'; ... }` |
+| Web | discriminated union | `type PassengerFlightState = { kind: 'loading' } | { kind: 'idle'; ... } | { kind: 'error'; ... }` |
 
 ## C4 - Test Method Naming
 
@@ -109,7 +109,7 @@ Apply platform default + open Section 20 risk row
 | iOS XCTest fallback | `test<Scenario>_<Expected>()` | `testFetch_ValidInput_ReturnsIdle()` |
 | Android JUnit5 | `fun <funName>_<scenario>_<expectedBehavior>()` | `fun fetch_validInput_returnsIdle()` |
 | Backend pytest | `def test_<scenario>_<expected>():` | `def test_fetch_valid_input_returns_idle():` |
-| Frontend Vitest | `it('<does X> when <condition>', ...)` | `it('returns idle when input is valid', ...)` |
+| Web Vitest | `it('<does X> when <condition>', ...)` | `it('returns idle when input is valid', ...)` |
 
 ## C5 - Accessibility Identifier
 
@@ -118,7 +118,7 @@ Apply platform default + open Section 20 risk row
 | iOS | dot notation `<feature>.<element>` | `passengerFlight.continueButton` | XCUITest query syntax friendliness |
 | Android | camelCase testTag | `passengerFlightContinueButton` | Compose testTag convention |
 | Backend | OpenAPI operationId camelCase | `fetchPassengerFlight` | Code generation friendly |
-| Frontend | kebab data-testid `<feature>-<element>` | `passenger-flight-continue-button` | DOM attribute readability |
+| Web | kebab data-testid `<feature>-<element>` | `passenger-flight-continue-button` | DOM attribute readability |
 
 ## C6 - Localization Key
 
@@ -127,7 +127,7 @@ Apply platform default + open Section 20 risk row
 | iOS | hierarchical dot PascalCase | `PassengerFlight.ContinueButton` | Matches `Localizable.xcstrings` convention |
 | Android | flat snake_case | `passenger_flight_continue_button` | Matches `strings.xml` convention |
 | Backend | not applicable (server-side messages live in error code tables) | | |
-| Frontend | hierarchical dot camelCase | `passengerFlight.continueButton` | i18next + ICU MessageFormat default |
+| Web | hierarchical dot camelCase | `passengerFlight.continueButton` | i18next + ICU MessageFormat default |
 
 ## C8 - SwiftUI Preview macro (iOS only)
 
@@ -137,7 +137,7 @@ Apply platform default + open Section 20 risk row
 | iOS legacy | `PreviewProvider` struct | `struct FooView_Previews: PreviewProvider { static var previews: some View { FooView(viewModel: .preview(.idle)) } }` | Pre-Swift 5.9 fallback |
 | Android | not applicable | (Compose `@Preview` is handled under C3 / C4 conventions, no separate field) | |
 | Backend | not applicable | | |
-| Frontend | not applicable | (Storybook stories live in `.stories.tsx` files, tracked under C2 conventions) | |
+| Web | not applicable | (Storybook stories live in `.stories.tsx` files, tracked under C2 conventions) | |
 
 Detection: scan up to 10 SwiftUI view files in the candidate set; majority pick wins. Confidence `high` if 5+ matching examples, `medium` if 3-4, `low` if 2, `none` if 0 SwiftUI views found (Pass B then omits Section 13.6 with `(N/A: UIKit-only feature)` note per Locked 29).
 
@@ -148,7 +148,7 @@ Detection: scan up to 10 SwiftUI view files in the candidate set; majority pick
 | iOS | Manual configurator | `<Domain>DependencyConfigurator.register<Feature>()` | Avoids framework lock-in; testable |
 | Android | Hilt module | `@Module @InstallIn(SingletonComponent::class) class <Feature>Module` | Standard Android DI |
 | Backend FastAPI | `Depends(get_<feature>_service)` | `service: PassengerFlightService = Depends(get_passenger_flight_service)` | Native FastAPI pattern |
-| Frontend | hook factory | `usePassengerFlightApi()` returns a memoized client | No framework DI needed |
+| Web | hook factory | `usePassengerFlightApi()` returns a memoized client | No framework DI needed |
 
 ## Risk row template (Section 20)
 

package/pipeline/multi-agent-refs/features/stack-skill-routing.md

@@ -41,7 +41,7 @@ Nothing enabled is not an error: a repo whose stack was never selected legitimat
 no toolkit. Record the no-op with the enabled set that was read, so "none applied" is
 distinguishable from "never looked".
 
-**Not enabled is not an error here**, unlike component dispatch: a repo whose stack was never selected legitimately has no toolkit, and halting would make the pipeline unusable there. Record the no-op and continue. (This paragraph used to say "a backend or web repo legitimately has no toolkit" - that stopped being true when the frontend and backend toolkits shipped, and the sentence outlived the fact by several releases.)
+**Not enabled is not an error here**, unlike component dispatch: a repo whose stack was never selected legitimately has no toolkit, and halting would make the pipeline unusable there. Record the no-op and continue. (This paragraph used to say "a backend or web repo legitimately has no toolkit" - that stopped being true when the web and backend toolkits shipped, and the sentence outlived the fact by several releases.)
 
 Two marketplaces may ship the same toolkit name (a public one and a corporate one). Resolve whichever is enabled and record its **name and version** in the ledger entry, because the routing table and the skill set differ between versions  -  a finding that cites a skill has to be traceable to the version that defined it.
 

package/pipeline/multi-agent-refs/phases/modes.md

@@ -69,7 +69,7 @@ Bu is icin hangi pipeline? / Which pipeline for this task?
   2. Kisa / Short  Dev (self-contained, Opus) -> Review -> Test -> Commit -> Report
 ```
 
-`bugfix` and `chore` recommend Short; `feature`, `refactor` and `component` recommend Full. The recommendation is presented first and passed as `ASK_CHOICE_DEFAULT` on hosts without a native picker, because `ask-choice.sh` picks the first option on a non-TTY and option order is not a contract.
+`bugfix` and `chore` recommend Short; `feature`, `refactor` and `component` recommend Full. The recommendation is presented first and passed as `ASK_CHOICE_DEFAULT` on hosts without a native picker, because `ask-choice.sh` picks the first option on a non-TTY and option order is not a contract. Pass it as the **1-based index** (Full = 1, Short = 2), not as the label: labels render in `outputLanguage`, so a label-valued default matches nothing on a `tr` run.
 
 **Who is asked.** `/multi-agent` and `/multi-agent:local`. Both autopilot entries always run Full without asking.
 

package/pipeline/multi-agent-refs/phases/phase-0-init.md

@@ -35,7 +35,7 @@ Read preferences: `PREFS_FILE="$HOME/.claude/multi-agent-preferences.json"` (if
 OUTPUT_LANG=$(jq -r '.global.outputLanguage // "en"' "$PREFS_FILE" 2>/dev/null || echo en)
 ```
 
-From this point on, everything the user reads renders in `$OUTPUT_LANG`: conversational lines, `AskUserQuestion` `question`/`description`, and external payload bodies (PR/Jira/Confluence). English stays only on `label`/`header`, commit messages, branch names, PR titles, identifiers. Full matrix: `rules.md` "Language Application".
+From this point on, everything the user reads renders in `$OUTPUT_LANG`: conversational lines, `AskUserQuestion` `question`/`label`/`description`, and external payload bodies (PR/Jira/Confluence). English stays only on `header`, commit messages, branch names, PR title prefixes, identifiers. Full matrix: `rules.md` "Language Application".
 
 **Model fallback date gate** (same step, once per run): read `prefs.global.modelFallback`. If `premiumTierUntil` is set and in the past, apply the date-gate trigger from `$HOME/.claude/multi-agent-refs/features/model-fallback.md` - `preferredModel` personas dispatch on `fallbackModel` for this run, with the one-line WARN. Dispatch-error and budget triggers in that contract apply per-dispatch later; nothing else to do here.
 
@@ -270,7 +270,8 @@ Scan `$HOME` (maxdepth 2) for project markers (`.xcodeproj`, `Package.swift`, `b
 6. Sort: `develop*` first, then `release/*`, then `main`/`master`. Surface through the
    **native picker** per `picker-contract.md` (`AskUserQuestion` on Claude Code,
    `ask_choice.sh` on Copilot CLI) - `question` + `description` in `outputLanguage`,
-   `label` English, the recent branch first and marked `(Recommended)`. The ASCII sketch
+   `label` = the branch name verbatim (a proper noun, never translated) with the recent
+   branch first and marked `(Recommended)`. The ASCII sketch
    below is what the options carry, not a menu to print:
 
    ```
@@ -550,11 +551,14 @@ Ask the depth question from `$HOME/.claude/multi-agent-refs/phases/modes.md` "Pi
 
 When the intake carried an analysis document or a Figma reference, say so **inside** the question: Short skips the only two phases that would turn that document into a task breakdown, and the user should learn that before choosing, not after.
 
-**Pass the default explicitly.** `ask-choice.sh` picks the FIRST option on a non-TTY, so relying on option order breaks the first time someone reorders them for readability, on the host where nobody is watching:
+**Pass the default explicitly, as an index.** `ask-choice.sh` picks the FIRST option on a non-TTY, so relying on option order breaks the first time someone reorders them for readability, on the host where nobody is watching. The default must be the 1-based index, never the label: labels follow `outputLanguage` (`rules.md` matrix), so `ASK_CHOICE_DEFAULT="Full"` matches nothing once the options render as `Tam` / `Kisa`, falls through, and silently takes option 1 on a non-TTY  -  the exact failure this step exists to prevent.
 
 ```bash
-ASK_CHOICE_DEFAULT="$DEPTH_RECOMMENDATION" \
-  $HOME/.claude/lib/ask-choice.sh "Which pipeline for this task?" "Full" "Short"
+# Full is option 1, Short is option 2 (modes.md "Pipeline depth")
+DEPTH_DEFAULT_INDEX=1; [ "$DEPTH_RECOMMENDATION" = "short" ] && DEPTH_DEFAULT_INDEX=2
+ASK_CHOICE_DEFAULT="$DEPTH_DEFAULT_INDEX" \
+  $HOME/.claude/lib/ask-choice.sh "<localized: 'Which pipeline for this task?'>" \
+  "<localized: 'Full'>" "<localized: 'Short'>"
 ```
 
 **Persist.** Short sets `state.onlyDevelop = true`; Full leaves it `false`. The key is unchanged - only who sets it changed - so every downstream reader keeps working. Short also flips the Phase 1 and Phase 2 tiles to `skipped` (tracker-contract.md, "Late skip"); pre-marking is forbidden.
@@ -583,7 +587,7 @@ Log: `Phase 0 Step 7.6: test baseline = {green|red|unknown} ({N} pre-existing fa
 3. If `clarityScore >= prefs.clarifyAmbiguous.minScoreToProceed` (default 6) or `stopAndAsk == false` → write `state.clarification` (score + rationale, no questions), proceed to Phase 1 silently.
 4. If `stopAndAsk == true`:
 
-   - **Interactive runs:** render the questions via `AskUserQuestion` (label + header per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix; `outputLanguage` for `question` + `option.description`, English for `label` + `header`). Up to `maxQuestions` questions, each with the recommended option flagged. Persist the user's answers under `state.clarification.userAnswers`.
+   - **Interactive runs:** render the questions via `AskUserQuestion` (per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix; `outputLanguage` for `question` + `option.label` + `option.description`, English for `header`). Up to `maxQuestions` questions, each with the recommended option flagged. Persist the user's answers under `state.clarification.userAnswers`.
    - **Autopilot runs:** follow `clarifyAmbiguous.autopilotMode`:
 
      | Mode  | Behavior |

package/pipeline/multi-agent-refs/phases/phase-2-planning.md

@@ -283,15 +283,16 @@ Then ask for the decision with a **native `AskUserQuestion` picker** (never a ty
 
 - `question`: "Do you approve this plan?" (rendered in `outputLanguage`)
 - `header`: "Plan" (English, <=12 chars)
-- `options`:
-  - `{ label: "Approve", description: "Proceed to development (Phase 3)" }`
-  - `{ label: "Cancel", description: "Pause the task; resume later with :resume" }`
+- `options` (label + description in `outputLanguage`; the names below are the option
+  SEMANTICS, not strings to print):
+  - option 1  -  "Approve": proceed to development (Phase 3)
+  - option 2  -  "Cancel": pause the task; resume later with `:resume`
 
-The picker's built-in **Other** field is the free-text edit channel: the user types an edit request there (e.g. "also look at the auth service but keep LoginView out of scope") instead of typing a keyword. (`option.label` stays English per the language matrix; `question` + `description` follow `outputLanguage`.)
+The picker's built-in **Other** field is the free-text edit channel: the user types an edit request there (e.g. "also look at the auth service but keep LoginView out of scope") instead of typing a keyword. Per the `rules.md` matrix `question`, `label` and `description` all follow `outputLanguage`; only `header` stays English. Branch on which option was picked, never on its rendered text.
 
 Handle the selection:
 
-- **Approve**:
+- **Option 1 (Approve)**:
   - Set `state.phases["2"].planApprovedAt = now()`, bump `planIterations` if not yet set (default 1)
   - Log `🧠 Phase 2: Plan approved (iterations={N}, clarificationRounds={M})`
   - Proceed to Phase 3

package/pipeline/multi-agent-refs/phases/phase-3-dev.md

@@ -132,7 +132,7 @@ For each task (respecting dependency order):
                 release_build_lock ;;
        android) ./gradlew test --tests "{testClass}.{testMethod}" 2>&1 | tail -5 ;;
        backend) pytest "{test_file}::{test_name}" 2>&1 | tail -5 ;;
-       frontend) npm test -- --testPathPattern="{file}" 2>&1 | tail -5 ;;
+       web) npm test -- --testPathPattern="{file}" 2>&1 | tail -5 ;;
      esac
      ```
    - Must fail for the RIGHT reason (expected assertion, not compilation error)
@@ -156,7 +156,7 @@ For each task (respecting dependency order):
    - Only if duplication or naming is poor
    - Re-run tests after refactor → still GREEN
 
-   **Target resolution** (auto-detect once per project, cache in `agent-state.json`; ios resolves scheme + simulator, android resolves module + variant, backend/frontend need none):
+   **Target resolution** (auto-detect once per project, cache in `agent-state.json`; ios resolves scheme + simulator, android resolves module + variant, backend/web need none):
    ```bash
    case "$STACK" in
      ios)     xcodebuild -list -json -project "{projectPath}" 2>/dev/null || xcodebuild -list -json -workspace "{workspacePath}" 2>/dev/null
@@ -170,7 +170,7 @@ For each task (respecting dependency order):
    - **ios, preferred (MCP, multi-agent-toolkit >= 3.0.0)**: `acquire_build_lock` → `mcp__multi-agent-toolkit__ios_xcodebuild({project|workspace, scheme, configuration: "Release", destination: "generic/platform=iOS", derived_data_path: "{worktreePath}/.DerivedData"})` → `release_build_lock`. Returns one line `Build: SUCCESS|FAILURE (E errors, W warnings) [xcresult-<id>]`; on failure drill in via `mcp__multi-agent-toolkit__ios_xcresult({id, mode: "errors"})`, never dump the full log.
    - **ios, fallback (raw)**: same lock pair around `xcodebuild build -scheme "{scheme}" -destination "generic/platform=iOS" -derivedDataPath "{worktreePath}/.DerivedData" 2>&1 | tail -5`.
    - **android**: lock pair around `./gradlew assembleDebug 2>&1 | tail -5` (the Gradle daemon and `build/` outputs contend across parallel worktrees exactly as DerivedData does  -  the lock applies).
-   - **backend / frontend**: `python -m compileall .` / `npm run build --if-present 2>&1 | tail -5`; no lock.
+   - **backend / web**: `python -m compileall .` / `npm run build --if-present 2>&1 | tail -5`; no lock.
 5. If build fails → fix → rebuild (max 3 attempts, track `retryCount` in state).
 6. **Intermediate commit** (after each completed task in the plan):
    ```bash
@@ -222,7 +222,7 @@ release_build_lock() { rm -rf "$BUILD_LOCK"; }
 - Phase 4 Step 1 Gate 1 (build gate before review)
 - Phase 4 Step 1 Gate 3 (test gate before review)
 
-**Android**: same lock discipline  -  the Gradle daemon and `build/` outputs contend across parallel worktrees. **Backend/frontend** (Python, Node.js): no lock needed  -  these build/test in parallel without conflicts.
+**Android**: same lock discipline  -  the Gradle daemon and `build/` outputs contend across parallel worktrees. **Backend/web** (Python, Node.js): no lock needed  -  these build/test in parallel without conflicts.
 
 ---
 

package/pipeline/multi-agent-refs/phases/phase-6-commit.md

@@ -90,17 +90,17 @@ Branch **deterministically**, no implicit fallback. Read `agent-state.json` and
 
 **Standard path (also used as fallback when instructionDriven=true but file missing):**
 
-1. **Local checkout test prompt** (skip in autopilot): If still in worktree AND Phase 5 was skipped, ask the user. Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix: `AskUserQuestion.label` and `header` stay English (UI button + chip contract); `question` and `description` follow `outputLanguage`. Render the picker accordingly:
+1. **Local checkout test prompt** (skip in autopilot): If still in worktree AND Phase 5 was skipped, ask the user. Per `$HOME/.claude/multi-agent-refs/rules.md` Language Application matrix: `question`, `label` and `description` follow `outputLanguage`; only `header` stays English (<=12-char chip). Render the picker accordingly:
    - `question` (in `outputLanguage`)  -  semantically: "Run a quick WIP-checkout test before commit?"
    - `header` (English, ≤12 chars): `"WIP checkout"`
-   - `options` (description in `outputLanguage`, label in English):
-     - label: `"No  -  continue to commit (Recommended)"`, description (in `outputLanguage`): proceed straight to commit + push + PR
-     - label: `"Yes  -  WIP checkout"`, description (in `outputLanguage`): pause so the user can checkout the branch locally and poke around
-   - Default: option 1 (No  -  continue to commit)
-   - If user picks "Yes  -  WIP checkout": follow Phase 5 Steps 2-6. On `"fix:"` → Phase 3. On `"ok"` → resume Phase 6.
+   - `options` (label + description both in `outputLanguage`; the semantics below, not these English strings, are what to render):
+     - option 1  -  semantically "No, continue to commit" marked `(Recommended)`; description: proceed straight to commit + push + PR
+     - option 2  -  semantically "Yes, WIP checkout"; description: pause so the user can checkout the branch locally and poke around
+   - Default: option 1 (by index, not by label  -  the label is localized)
+   - If the user picks option 2 (WIP checkout): follow Phase 5 Steps 2-6. On `"fix:"` → Phase 3. On `"ok"` → resume Phase 6.
 2. Commit confirm prompt (skip in autopilot). Same language matrix:
    - `question` in `outputLanguage` (semantic: "Commit now?")
-   - labels English: `"Commit"`, `"Pause and resume later"`
+   - labels in `outputLanguage`, semantically "Commit" and "Pause and resume later"; branch on the option index, not on the rendered string
    - No → Pause, user can `resume` later. Yes → continue:
 3. If WIP commit exists from Phase 5 or Step 1: `git reset HEAD~1` to unstage, then re-commit properly
 4. Stage changes: `git add` with specific files (NOT `git add -A`  -  avoid sensitive files, `.worktrees/`, agent files)

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

@@ -10,8 +10,8 @@
 `ask_choice(question, options[], { header?, default?, allowFreeText? })`
 
 - `question` - rendered in `outputLanguage`.
-- `options[]` - each `{ label (English), description (outputLanguage) }`.
-- `default` - recommended option (label or 1-based index); used by autopilot / non-interactive runs.
+- `options[]` - each `{ label (outputLanguage), description (outputLanguage) }`. A label naming a branch, an account or another proper noun is passed through verbatim rather than translated.
+- `default` - recommended option, given as a **1-based index**; used by autopilot / non-interactive runs. Labels are localized, so a label-valued default resolves differently on `en` and `tr`.
 - `allowFreeText` - when true, a free-text answer is accepted as an extra channel (e.g. the plan-gate's edit request).
 
 Returns the selected option label (or the free-text string when `allowFreeText` and the user typed instead of choosing).
@@ -33,7 +33,7 @@ This is the surface that makes the native picker show, step by step, what it is
 
 | Platform | Render |
 |---|---|
-| **Claude Code** | native `AskUserQuestion` (question/description in `outputLanguage`, label English); free-text via the built-in **Other** field |
+| **Claude Code** | native `AskUserQuestion` (question/label/description in `outputLanguage`, `header` English); free-text via the built-in **Other** field, which the host injects in English and no run can localize |
 | **Copilot CLI** | `pipeline/lib/ask-choice.sh` (numbered menu); a future MCP elicitation tool can replace this once host support is broad |
 
 ## Universal fallback: `pipeline/lib/ask-choice.sh`
@@ -45,11 +45,36 @@ choice=$(pipeline/lib/ask-choice.sh "Do you approve this plan?" "Approve" "Cance
 ```
 
 - Prints the menu + prompt on **stderr**; echoes ONLY the chosen label on **stdout**.
-- `ASK_CHOICE_DEFAULT=<label|index>` selects without prompting (autopilot / CI).
+- `ASK_CHOICE_DEFAULT=<1-based-index|label>` selects without prompting (autopilot / CI). The script still resolves either, but pipeline callers **must** pass the index: a label is localized copy and stops matching the moment `outputLanguage` changes.
 - No TTY + no default -> picks the first option and never blocks an automated run.
 
 Enforced by `smoke-ask-choice.sh`.
 
+## Localized labels: what the caller owns
+
+`label` is copy the user reads, so it renders in `outputLanguage` like `question`
+and `description`. Three consequences belong to whoever calls the picker:
+
+- **Branch on the choice, not the string.** The returned label is localized, so a
+  literal comparison against an English word resolves differently on `en` and `tr`.
+  Match on which option was selected and map it back to its canonical English value
+  before it reaches `agent-state.json`, a commit message, a branch name or a log line.
+- **Defaults are indices.** Pass `default` and `ASK_CHOICE_DEFAULT` as a 1-based index.
+  Both still accept a label, which is exactly the trap: a label-valued default keeps
+  working until someone switches `outputLanguage`, then silently matches nothing and
+  `ask-choice.sh` falls through to the prompt (or, with no TTY, to option 1).
+- **Proper nouns pass through.** A label naming a branch, an account, a repo or a
+  stack id is rendered verbatim, never translated.
+
+**Reading a spec file.** Every `label: "..."` written in a phase doc, a ref or a
+command spec is the option's semantics, recorded in English because instruction prose
+is English. It is not the string to print. Render it in `outputLanguage` at call time.
+The same goes for prose that names an option (`If the user picks "Cancel"`): it
+identifies which option, not what the button said.
+
+The host injects its own **Other** free-text row in English on every run. Nothing in
+the pipeline can localize it, and no option may depend on its wording.
+
 ## Autopilot / non-interactive contract
 
 In autopilot, `ask_choice` resolves to `default` (or the safe first option) without prompting - identical to how the native gates auto-proceed today. A picker is only surfaced for genuinely ambiguous or destructive decisions, matching the maturity-check model.

package/pipeline/multi-agent-refs/readiness-review.md

@@ -24,7 +24,7 @@ Maturity is generic; add these pipeline-readiness dimensions by reading the fetc
 | Reproduction | Bugs have steps + expected/actual | none (aligns with maturity `no_repro_steps`) |
 | Design reference | UI work links a Figma frame or attaches a screenshot | UI implied but no design source |
 | API contract | backend/integration work names endpoints or a Swagger/OpenAPI ref | data/contract implied, none given |
-| Platform / stack signal | the target stack is inferable (iOS / Android / frontend / backend) | ambiguous - Phase 1 could not route |
+| Platform / stack signal | the target stack is inferable (iOS / Android / web / backend) | ambiguous - Phase 1 could not route |
 | Dependencies | blocking deps/links are called out when they exist | hidden dependency likely |
 
 Only emit a dimension as a gap when its trigger applies (do not demand an API contract on a copy-change task). Merge: `gaps = maturity.blockers + maturity.warnings + rubric gaps`.

package/pipeline/multi-agent-refs/rules.md

@@ -8,8 +8,8 @@ The pipeline has two language axes. Both MUST be applied from the very first tur
 
 | Axis | Source | Used for |
 |---|---|---|
-| `prefs.global.outputLanguage` (default `"en"`) | Read at Phase 0 Step 0 | All assistant-authored conversational text: status updates, findings, phase headers in chat, summaries, error explanations, audit reports, picker `question` + `description` text, anything the user reads outside the structural UI chrome. |
-| `prefs.global.promptLanguage` (locked to `"en"`) | Hard-coded `"en"` | `AskUserQuestion` `label` (button text) + `header` (chip), CLI host error UI, internal contract identifiers. |
+| `prefs.global.outputLanguage` (default `"en"`) | Read at Phase 0 Step 0 | All assistant-authored conversational text: status updates, findings, phase headers in chat, summaries, error explanations, audit reports, picker `question` + `label` + `description` text, anything the user reads outside the structural UI chrome. |
+| `prefs.global.promptLanguage` (locked to `"en"`) | Hard-coded `"en"` | `AskUserQuestion` `header` (the <=12-char chip), CLI host error UI, internal contract identifiers. |
 
 ### Per-field language matrix (canonical)
 
@@ -22,7 +22,7 @@ This is the single source of truth. When a contributor or model is unsure where
 | Phase tracker render labels                  | English (script chrome)           |
 | `AskUserQuestion.question`                   | `outputLanguage`                  |
 | `AskUserQuestion.options[].description`      | `outputLanguage`                  |
-| `AskUserQuestion.options[].label`            | English (UI button contract)      |
+| `AskUserQuestion.options[].label`            | `outputLanguage`                  |
 | `AskUserQuestion.header`                     | English (≤12-char chip)           |
 | Confirmation prompt body (e.g. push y/n)     | `outputLanguage`                  |
 | GitHub issue comment body                    | `outputLanguage`                  |
@@ -41,7 +41,7 @@ This is the single source of truth. When a contributor or model is unsure where
 
 1. At the very start of every run (Phase 0 Step 0, before any status output), call `jq -r '.global.outputLanguage // "en"'` on `$HOME/.claude/multi-agent-preferences.json`. Cache as `OUTPUT_LANG` for the session.
 2. Render every assistant-authored line in `OUTPUT_LANG`. If the user types Turkish but `outputLanguage="en"` is set, follow the pref but suggest `/multi-agent:language tr` once.
-3. `AskUserQuestion` `label` and `header` stay English regardless of `OUTPUT_LANG` (UI contract). `question` and `description` follow `OUTPUT_LANG`  -  the user reads them as conversational copy, not as button affordances.
+3. `AskUserQuestion` `question`, `options[].label` and `options[].description` all follow `OUTPUT_LANG`. Only `header` stays English: a <=12-char chip Turkish overflows. Callers branch on which option was picked, never on its literal text, and pass `default` / `ASK_CHOICE_DEFAULT` as a 1-based index. The host's own **Other** row is always English. Caller rules: `picker-contract.md`.
 4. Always English regardless of either axis: commit messages, PR titles, branch names, code identifiers, agent-state.json values, agent-log.md, reviewer/triage system prompts.
 
 **Failure mode this prevents.** Entering `/multi-agent`, `/multi-agent:autopilot`, `/multi-agent:local`, etc. and switching the assistant's conversational text or picker question copy to English while `outputLanguage="tr"` is set. The user sees a half-English half-Turkish dialogue, flagged as a pipeline bug, not a stylistic choice.

package/pipeline/multi-agent-refs/{frontend-guide.md → web-guide.md}

@@ -1,6 +1,6 @@
-## Frontend Development Guide
+## Web Development Guide
 
-When the task involves frontend development (React, Next.js, Vue), follow these patterns.
+When the task involves web development (React, Next.js, Vue), follow these patterns.
 
 ### Component Architecture
 

package/pipeline/schemas/analysis-output.schema.json

@@ -15,7 +15,7 @@
       "properties": {
         "primary": {
           "type": "string",
-          "enum": ["ios", "android", "backend", "frontend", "mobile", "unknown"],
+          "enum": ["ios", "android", "web", "backend", "mobile", "frontend", "unknown"],
           "description": "Dominant stack inferred from project markers (.xcodeproj, build.gradle, package.json, etc.)."
         },
         "language": {

package/pipeline/schemas/analysis-spec.schema.json

@@ -102,7 +102,7 @@
     "platforms": {
       "type": "array",
       "minItems": 1,
-      "items": { "type": "string", "enum": ["ios", "android", "backend", "frontend"] },
+      "items": { "type": "string", "enum": ["ios", "android", "web", "backend", "mobile", "frontend"] },
       "description": "Platforms selected in Phase 0 step 3 (multi-select)."
     },
     "repos": {
@@ -112,7 +112,7 @@
         "additionalProperties": false,
         "required": ["platform", "name", "canPush"],
         "properties": {
-          "platform": { "type": "string", "enum": ["ios", "android", "backend", "frontend"] },
+          "platform": { "type": "string", "enum": ["ios", "android", "web", "backend", "mobile", "frontend"] },
           "name": { "type": "string", "minLength": 1 },
           "cloneUrl": { "type": ["string", "null"] },
           "canPush": { "type": "boolean" }
@@ -417,7 +417,7 @@
                       "type": "array",
                       "items": {
                         "type": "string",
-                        "enum": ["ios", "android", "backend", "frontend"]
+                        "enum": ["ios", "android", "web", "backend", "mobile", "frontend"]
                       }
                     },
                     "citation": { "type": ["string", "null"] }

package/pipeline/schemas/prefs.schema.json

@@ -1704,13 +1704,29 @@
               "maxItems": 20,
               "description": "Extra writable repos to offer in the dev-context picker beyond auto-detected submodules (iOS/Android/Backend)."
             },
+            "webRepos": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "maxItems": 20,
+              "description": "Web repos for this project, used by /multi-agent:analysis Step 4 (Web is rarely in the iOS/Android submodule tree). Readers fall back to the pre-rename frontendRepos when this is absent."
+            },
+            "webRoots": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "maxItems": 20,
+              "description": "Whitelist source roots for the Web repo-evidence scan (overrides the default src/ app/ components/ features/ lib/). Readers fall back to the pre-rename frontendRoots when this is absent."
+            },
             "frontendRepos": {
               "type": "array",
               "items": {
                 "type": "string"
               },
               "maxItems": 20,
-              "description": "Frontend repos for this project, used by /multi-agent:analysis Step 4 (Frontend is rarely in the iOS/Android submodule tree)."
+              "description": "Deprecated spelling of webRepos, still read so prefs written before the Web rename keep working. Do not write it for new projects."
             },
             "frontendRoots": {
               "type": "array",
@@ -1718,7 +1734,7 @@
                 "type": "string"
               },
               "maxItems": 20,
-              "description": "Whitelist source roots for the Frontend repo-evidence scan (overrides the default src/ app/ components/ features/ lib/)."
+              "description": "Deprecated spelling of webRoots, still read so prefs written before the Web rename keep working. Do not write it for new projects."
             },
             "appStoreConnect": {
               "type": "object",

package/pipeline/scripts/gen-skills-index.mjs

@@ -67,7 +67,7 @@ const titles = {
   pipeline: "Pipeline Orchestration",
   ios: "iOS / Apple Ecosystem",
   android: "Android / Kotlin",
-  web: "Web / Frontend",
+  web: "Web",
   backend: "Backend / API",
   misc: "Cross-cutting",
 };

package/pipeline/scripts/validate-analysis-doc.mjs

@@ -42,9 +42,13 @@
 
 import { readFileSync } from "node:fs";
 
-// "none" is the stack-optional render (Locked 35): a document produced before
-// any repo was chosen. It is a real platform value, not a missing one.
-const KNOWN_PLATFORMS = new Set(["ios", "android", "backend", "frontend", "none"]);
+// A repo-less run (Locked 35) still splits by channel, derived from the evidence:
+// "mobile" and "web" are its platform values. "none" is the narrower case where the
+// evidence describes no interface at all. All three are real values, not missing ones.
+// "web" is the pre-"web" spelling, still accepted so older documents validate.
+const KNOWN_PLATFORMS = new Set([
+  "ios", "android", "web", "backend", "mobile", "frontend", "none",
+]);
 const REQUIRED_FM = ["feature", "platform", "language", "mode", "template_version"];
 
 // Never-omitted sections (Locked 2), matched by bilingual title keyword so the

package/pipeline/scripts/validate-analysis.mjs

@@ -17,7 +17,12 @@
 
 import { readFileSync } from "node:fs";
 
-const ALLOWED_STACKS = new Set(["ios", "android", "backend", "frontend", "mobile", "unknown"]);
+// "frontend" is the pre-v16.11.0 spelling of "web". Kept so a stored Phase 1
+// output, a golden-task fixture or a resumed run written before the rename still
+// validates; new output uses "web". Mirrors analysis-output.schema.json.
+const ALLOWED_STACKS = new Set([
+  "ios", "android", "backend", "web", "mobile", "frontend", "unknown",
+]);
 const ALLOWED_SEVERITIES = new Set(["low", "medium", "high"]);
 
 function readInput() {

package/pipeline/scripts/write-state.mjs

@@ -100,12 +100,26 @@ async function acquireLock(
         /* already gone */
       }
       if (err.code !== "EEXIST") throw err;
-      if (isLockStale(lockPath, staleMs)) {
-        // Holder crashed or the lock outlived any plausible writer  -  reclaim it.
+      // Reclaim by identity, never by path. Between judging a lock stale and
+      // deleting it, the holder can release and a THIRD writer can acquire a
+      // fresh one - and an unlink by path deletes that live lock, after which
+      // two writers hold it and one update is lost. Same failure the PID window
+      // above once caused, at a different point in the loop; it survived because
+      // it only reproduces under load, where the gap is wide enough to lose.
+      //
+      // The inode is the identity: a newly acquired lock is a different file
+      // even at the same path. Delete only if the file we judged is still the
+      // file that is there.
+      const stale = lockIdentityIfStale(lockPath, staleMs);
+      if (stale) {
         try {
-          unlinkSync(lockPath);
+          const now = statSync(lockPath);
+          if (now.ino === stale.ino && now.mtimeMs === stale.mtimeMs) {
+            unlinkSync(lockPath);
+          }
+          // Changed under us: somebody else's live lock. Leave it and retry.
         } catch {
-          /* another writer won the race  -  fall through and retry */
+          /* vanished on its own  -  fall through and retry */
         }
         continue;
       }
@@ -128,28 +142,32 @@ async function acquireLock(
  * @param {number} staleMs
  * @returns {boolean}
  */
-function isLockStale(lockPath, staleMs) {
+function lockIdentityIfStale(lockPath, staleMs) {
   let pid;
   let mtimeMs;
+  let ino;
   try {
     pid = parseInt(readFileSync(lockPath, "utf-8").trim(), 10);
-    mtimeMs = statSync(lockPath).mtimeMs;
+    const st = statSync(lockPath);
+    mtimeMs = st.mtimeMs;
+    ino = st.ino;
   } catch {
     // Lock vanished between EEXIST and our read  -  let the retry re-open it.
-    return false;
+    return null;
   }
-  if (Date.now() - mtimeMs > staleMs) return true;
+  const identity = { ino, mtimeMs };
+  if (Date.now() - mtimeMs > staleMs) return identity;
   // An unreadable PID is NOT proof of staleness. Treating it as such is what
   // let a writer delete a live lock and lose another writer's update. With the
   // link-based acquire above a lock is never observable without its PID, so
   // this can only be genuine corruption - which the staleMs check reclaims
   // anyway, without racing a writer that is merely mid-flight.
-  if (!Number.isInteger(pid) || pid <= 0) return false;
+  if (!Number.isInteger(pid) || pid <= 0) return null;
   try {
     process.kill(pid, 0); // probe liveness without signalling
-    return false; // holder alive
+    return null; // holder alive
   } catch (err) {
-    return err.code === "ESRCH"; // no such process  -  stale
+    return err.code === "ESRCH" ? identity : null; // no such process  -  stale
   }
 }