@mmerterden/multi-agent-pipeline 8.6.1 → 10.0.6

package/pipeline/commands/multi-agent/refs/channels/pr-review-actions.md

@@ -1,6 +1,6 @@
-# Channel adapter — Pull Request review actions
+# Channel adapter  -  Pull Request review actions
 
-> Canonical contract for the PR-actions branch of `/multi-agent:review`. The PR-side artifacts are **per-finding inline comments + an explicit approve / needs-work decision** — never a single monolithic description comment.
+> Canonical contract for the PR-actions branch of `/multi-agent:review`. The PR-side artifacts are **per-finding inline comments + an explicit approve / needs-work decision**  -  never a single monolithic description comment.
 
 ## When this fires
 
@@ -8,7 +8,7 @@
 review.input.kind === "pr"   (PR URL, #N, or repo#N input)
 ```
 
-Branch-only invocations (`/multi-agent:review feature/foo`) do NOT post anything — chat-only summary is the only artifact.
+Branch-only invocations (`/multi-agent:review feature/foo`) do NOT post anything  -  chat-only summary is the only artifact.
 
 ## The decision rule
 
@@ -21,23 +21,23 @@ After triage, count the `accepted` findings by severity:
 | 0 | ≥1 | any | **NEEDS WORK / REQUEST CHANGES** | one per accepted blocking + important |
 | ≥1 | any | any | **NEEDS WORK / REQUEST CHANGES** | one per accepted blocking + important |
 
-**Hard rule — no monolithic description comment.** "Post one big advisory comment with verdict + tables + finding sections" is forbidden. Every finding that warrants posting MUST be an inline comment anchored to `file:line`. The verdict itself is the review state (APPROVED / NEEDS_WORK), not a comment body.
+**Hard rule  -  no monolithic description comment.** "Post one big advisory comment with verdict + tables + finding sections" is forbidden. Every finding that warrants posting MUST be an inline comment anchored to `file:line`. The verdict itself is the review state (APPROVED / NEEDS_WORK), not a comment body.
 
 **Suggestions never block and never get inline comments by default.** They only appear in the chat summary. Inline-posting suggestions floods the PR for taste-level concerns; reserve PR comments for blocking + important.
 
 ## Inline comment template (per finding)
 
-Body language follows `prefs.global.outputLanguage`. Both forms below are 1:1 — pick the matching one at render time.
+Body language follows `prefs.global.outputLanguage`. Both forms below are 1:1  -  pick the matching one at render time.
 
 ### Turkish (outputLanguage = "tr")
 
 ```markdown
-{severityEmoji} **{severityLabelTr}** — {issueTr}
+{severityEmoji} **{severityLabelTr}**  -  {issueTr}
 
 **Öneri:** {fixTr}
 
 {Optional rule reference, e.g.:}
-_apple-archive-compliance / no-force-unwrap — Guideline 2.1.1_
+_apple-archive-compliance / no-force-unwrap  -  Guideline 2.1.1_
 
 ---
 🤖 _Multi-Agent Review · iteration #{iterationNumber}_
@@ -50,7 +50,7 @@ Severity labels (TR):
 ### English (outputLanguage = "en")
 
 ```markdown
-{severityEmoji} **{severityLabelEn}** — {issueEn}
+{severityEmoji} **{severityLabelEn}**  -  {issueEn}
 
 **Suggestion:** {fixEn}
 
@@ -71,7 +71,7 @@ Severity labels (EN):
 | GitHub | `POST /repos/{owner}/{repo}/pulls/{n}/comments` | `path` + `line` (right side) + `commit_id` |
 | Bitbucket Server | `POST /rest/api/1.0/projects/{key}/repos/{slug}/pull-requests/{id}/comments` with `anchor: { path, line, lineType: "ADDED", fileType: "TO" }` | `path` + `line` |
 
-If a finding's `line` falls outside the diff (review of unchanged code), the anchor is dropped and the comment becomes a top-level PR comment instead — same body, no inline anchor.
+If a finding's `line` falls outside the diff (review of unchanged code), the anchor is dropped and the comment becomes a top-level PR comment instead  -  same body, no inline anchor.
 
 ## Decision endpoints
 
@@ -86,28 +86,30 @@ The Bitbucket needs-work pattern keeps the user as REVIEWER role; status flip is
 
 1. Decide: APPROVE vs NEEDS_WORK from the table above.
 2. If NEEDS_WORK: post one inline comment per accepted blocking + important finding, in `outputLanguage`.
-3. Set the review state (APPROVE / NEEDS_WORK) — this is the durable verdict signal.
+3. Set the review state (APPROVE / NEEDS_WORK)  -  this is the durable verdict signal.
 4. The chat summary still prints regardless (live conversation). Suggestions go to chat only.
 
-Comments and the decision are paired — the decision is set AFTER comments are posted so reviewers see the inlines before the state flag.
+Comments and the decision are paired  -  the decision is set AFTER comments are posted so reviewers see the inlines before the state flag.
 
 ## Hard prohibitions
 
-- No monolith description comment (no "## 🔍 Multi-Agent Review — PR #N" body).
+- No monolith description comment (no "## 🔍 Multi-Agent Review  -  PR #N" body).
 - No `Closes #` / `Fixes #` / `Resolves #` keywords in any comment.
-- No em-dashes (`—`) in free-form reviewer prose (the `issue` / `fix` body text); use ` · ` or `→`. The em-dash in the fixed inline template (severity label separator, e.g. `**Blocker** — {issue}`) is part of the rendered shape, not prose, and is allowed.
+- No em-dashes (` - `) in free-form reviewer prose (the `issue` / `fix` body text); use ` · ` or `→`. The em-dash in the fixed inline template (severity label separator, e.g. `**Blocker**  -  {issue}`) is part of the rendered shape, not prose, and is allowed.
 - No model vendor names in comment prose; the chat-side table column header is the only place they may appear.
 - No suggestion-severity inline comments. Suggestions are chat-only.
-- No mixing languages in one comment body — pick `outputLanguage` and stick to it.
+- No mixing languages in one comment body  -  pick `outputLanguage` and stick to it.
 
 ## Idempotency
 
 Each `/multi-agent:review` invocation:
-- Posts new inline comments (does not edit prior runs' comments — preserves audit trail).
-- Sets review state via the appropriate endpoint (PUT/POST) — overwrites prior state for the same user.
+- Posts new inline comments (does not edit prior runs' comments  -  preserves audit trail).
+- Sets review state via the appropriate endpoint (PUT/POST)  -  overwrites prior state for the same user.
 
 If the user re-runs review and findings shrink (e.g., from 3 important → 0), the state flips from NEEDS_WORK → APPROVED automatically.
 
+The `iteration #N` footer is derived live from the PR itself: `post-pr-review.sh` scans the existing comments for the highest `iteration #N` and posts the next run as `N+1` (falling back to `1` on a fresh PR). Standalone `/multi-agent:review` runs use a new TASK_ID each time, so the PR comments  -  not agent-state  -  are the cross-run source of truth for the counter.
+
 ## Provider auto-detection
 
 ```bash
@@ -123,7 +125,7 @@ Unknown providers fall back to chat-only with a warning: "Provider not recognize
 
 ## Pairing with the chat summary
 
-The chat-side summary ALWAYS prints with the verdict table (per-model breakdown for parallel runs). The summary stays in chat; the PR receives inline comments per finding + the state flag — the two channels do not mirror each other.
+The chat-side summary ALWAYS prints with the verdict table (per-model breakdown for parallel runs). The summary stays in chat; the PR receives inline comments per finding + the state flag  -  the two channels do not mirror each other.
 
 ## Drift detection
 

package/pipeline/commands/multi-agent/refs/channels/pr.md

@@ -1,4 +1,4 @@
-# Channel adapter — PR description
+# Channel adapter  -  PR description
 
 > Detailed contract for the `pr` channel of `/multi-agent:channels`. Split out of `channels.md` in v8.0.0; the parent doc keeps a one-line summary and a link here.
 
@@ -6,7 +6,7 @@ The PR adapter rewrites the pull request description with the body assembled in
 
 ## Required body structure
 
-The PR description targets code reviewers — it stays technical. Every adapter run assembles the body from the same fixed set of sections in the same order. Section headings render in `prefs.global.outputLanguage` (the body **text** is bilingual-aware); section keys and order are stable.
+The PR description targets code reviewers  -  it stays technical. Every adapter run assembles the body from the same fixed set of sections in the same order. Section headings render in `prefs.global.outputLanguage` (the body **text** is bilingual-aware); section keys and order are stable.
 
 | # | Section key | Heading (`tr`) | Heading (`en`) | Required? |
 |---|---|---|---|---|
@@ -19,23 +19,23 @@ The PR description targets code reviewers — it stays technical. Every adapter
 
 ### Section content rules
 
-**`summary`** — 1-3 sentences in `outputLanguage`. The "why" of the change. Past tense, no marketing voice. Code identifiers stay verbatim.
+**`summary`**  -  1-3 sentences in `outputLanguage`. The "why" of the change. Past tense, no marketing voice. Code identifiers stay verbatim.
 
-**`changes`** — bullet list, one item per logically distinct change. Each bullet starts with the touched component and ends with a one-line "what". Use the stack's native file extensions / module paths — the example below shows the **shape**, not a stack lock-in:
+**`changes`**  -  bullet list, one item per logically distinct change. Each bullet starts with the touched component and ends with a one-line "what". Use the stack's native file extensions / module paths  -  the example below shows the **shape**, not a stack lock-in:
 
 ```markdown
 ## Changes
 
-- `<path/to/file.ext>` — <one-line description of what changed>
-- `<path/to/another.ext>` — <one-line description>
-- `<path/to/test.ext>` — <which scenarios were added/updated>
+- `<path/to/file.ext>`  -  <one-line description of what changed>
+- `<path/to/another.ext>`  -  <one-line description>
+- `<path/to/test.ext>`  -  <which scenarios were added/updated>
 ```
 
-Across stacks the same shape produces, for example: `LoginView.swift — …` (iOS), `LoginScreen.kt — …` (Android), `login-form.tsx — …` (frontend), `auth_service.py — …` (backend). File paths and symbol names are NOT translated — only the trailing description sentence follows `outputLanguage`.
+Across stacks the same shape produces, for example: `LoginView.swift  -  ...` (iOS), `LoginScreen.kt  -  ...` (Android), `login-form.tsx  -  ...` (frontend), `auth_service.py  -  ...` (backend). File paths and symbol names are NOT translated  -  only the trailing description sentence follows `outputLanguage`.
 
-**`architecture`** — only when the change involves a non-trivial decision (new abstraction, pattern change, data flow shift, dependency direction). Format: short paragraph stating the decision and the alternative considered. Skip the section entirely for mechanical refactors / dependency bumps / formatting passes.
+**`architecture`**  -  only when the change involves a non-trivial decision (new abstraction, pattern change, data flow shift, dependency direction). Format: short paragraph stating the decision and the alternative considered. Skip the section entirely for mechanical refactors / dependency bumps / formatting passes.
 
-**`verification`** — what the reviewer should run to confirm the change works. Commands first, manual steps next. Pick the commands for the project's stack — the pipeline supports iOS (Swift/Xcode), Android (Gradle), frontend (npm/pnpm/yarn), and backend (varies: pytest/jest/go test/etc). Do not hardcode one stack in the body; emit only the commands relevant to the repos touched by this PR.
+**`verification`**  -  what the reviewer should run to confirm the change works. Commands first, manual steps next. Pick the commands for the project's stack  -  the pipeline supports iOS (Swift/Xcode), Android (Gradle), frontend (npm/pnpm/yarn), and backend (varies: pytest/jest/go test/etc). Do not hardcode one stack in the body; emit only the commands relevant to the repos touched by this PR.
 
 Skeleton (the adapter fills the body with the actual stack-appropriate lines at write-time; the template lists the shape only):
 
@@ -48,11 +48,11 @@ Skeleton (the adapter fills the body with the actual stack-appropriate lines at
 - Manual: <one or more user-facing steps the reviewer can follow without setup>
 ```
 
-Multi-repo PRs (one PR per repo) emit verification commands for that repo's stack only — never mix iOS + Android commands into a single PR body.
+Multi-repo PRs (one PR per repo) emit verification commands for that repo's stack only  -  never mix iOS + Android commands into a single PR body.
 
-**`dependencies`** — only when `Package.swift` / `Podfile` / `build.gradle` / `package.json` changed. Each entry: `package@old → new — reason`.
+**`dependencies`**  -  only when `Package.swift` / `Podfile` / `build.gradle` / `package.json` changed. Each entry: `package@old → new  -  reason`.
 
-**`related`** — flat list, plain text. Examples:
+**`related`**  -  flat list, plain text. Examples:
 
 ```markdown
 ## Related
@@ -69,7 +69,7 @@ Never use `Closes #N`, `Fixes #N`, `Resolves PROJ-X`. Issues require 4-approval
 
 ```
 1. Read agent-state.json (taskId, contextLinks, identity, language).
-2. Build section bodies in markdown — summary first, then in the table order, skipping conditional sections that don't apply.
+2. Build section bodies in markdown  -  summary first, then in the table order, skipping conditional sections that don't apply.
 3. Run the assembled body through the `humanizer` skill.
 4. Apply Multi-repo cross-links (## Related PRs prepend when projects.length > 1).
 5. Dispatch per the Behaviour-by-remote table.
@@ -79,8 +79,8 @@ Never use `Closes #N`, `Fixes #N`, `Resolves PROJ-X`. Issues require 4-approval
 
 | Remote | API | Reviewer handling |
 |---|---|---|
-| GitHub | `gh pr edit --body-file` | Reviewers are independent of the body — no extra payload required. |
-| Bitbucket | `PUT /rest/api/1.0/projects/{P}/repos/{R}/pull-requests/{id}` | MUST re-send `reviewers`, `fromRef`, `toRef`, `draft`, `version` — server-side defaulting wipes any field that is omitted. |
+| GitHub | `gh pr edit --body-file` | Reviewers are independent of the body  -  no extra payload required. |
+| Bitbucket | `PUT /rest/api/1.0/projects/{P}/repos/{R}/pull-requests/{id}` | MUST re-send `reviewers`, `fromRef`, `toRef`, `draft`, `version`  -  server-side defaulting wipes any field that is omitted. |
 
 ## Reviewer-preserving Bitbucket payload (required)
 
@@ -113,27 +113,27 @@ When `state.projects[].length > 1`, `channels-multi-repo.sh render-pr <state> <b
 - The **primary** target's body lists every extra as `Related: <url>`.
 - Each **extra** target's body lists the primary as `Part of: <url>`.
 
-Single-repo tasks return one entry from `channels-multi-repo.sh targets …` with empty `crossLinks`, so the loop is shape-stable.
+Single-repo tasks return one entry from `channels-multi-repo.sh targets ...` with empty `crossLinks`, so the loop is shape-stable.
 
 ## Version mismatch handling
 
 The Bitbucket REST API returns `409 Conflict` if `version` is stale. Adapter behaviour:
 
 1. Refetch PR JSON, retry the PUT once with the new `version`.
-2. Second mismatch → fail this adapter, log reason, return `{status: "failed", reason: "version conflict"}`. Other adapters keep running — non-blocking by Step 6 contract.
+2. Second mismatch → fail this adapter, log reason, return `{status: "failed", reason: "version conflict"}`. Other adapters keep running  -  non-blocking by Step 6 contract.
 
 ## Flags that affect this adapter
 
 | Flag | Effect |
 |---|---|
 | `--append` | Body merged with existing description instead of replaced. |
-| `--ready` | If PR is draft, promote to READY after the description PUT succeeds (uses `gh pr ready` / Bitbucket `PUT … {draft: false}` sharing the reviewer-preserving payload). |
+| `--ready` | If PR is draft, promote to READY after the description PUT succeeds (uses `gh pr ready` / Bitbucket `PUT ... {draft: false}` sharing the reviewer-preserving payload). |
 | `--dry-run` | Generated body printed to stdout, no PUT issued. |
 
 ## Hard rules (must not regress)
 
-- Real newlines, no HTML entities — heredoc + `jq --rawfile` + `curl --data-binary @file`. Never embed `\n` literally; Bitbucket stores the literal `\n` characters.
+- Real newlines, no HTML entities  -  heredoc + `jq --rawfile` + `curl --data-binary @file`. Never embed `\n` literally; Bitbucket stores the literal `\n` characters.
 - Section order is fixed: `summary` → `changes` → `architecture` (cond.) → `verification` → `dependencies` (cond.) → `related`. Conditional sections may be omitted but never reordered or inserted between fixed ones.
-- Humanizer pass runs **after** body assembly and **before** dispatch — every body line carries technical, non-AI tone. References at least one symbol/file/line drawn from the diff or pipeline log.
+- Humanizer pass runs **after** body assembly and **before** dispatch  -  every body line carries technical, non-AI tone. References at least one symbol/file/line drawn from the diff or pipeline log.
 - Body content language follows `prefs.global.outputLanguage`. Code identifiers, file paths, branch names, PR titles, commands, type names, and `Closes/Fixes`-style keywords stay verbatim English. The template file (this doc) is English because `promptLanguage="en"` is locked; the body is rendered in the user's language at write-time.
-- No body markers (`<!-- channels:start -->`) — channels does a full replace each run.
+- No body markers (`<!-- channels:start -->`)  -  channels does a full replace each run.

package/pipeline/commands/multi-agent/refs/channels/wiki.md

@@ -1,8 +1,8 @@
-# Channel adapter — Wiki
+# Channel adapter  -  Wiki
 
 > Detailed contract for the `wiki` channel of `/multi-agent:channels`. Split out of `channels.md` in v8.0.0; the parent doc keeps a one-line summary and a link here. Full Case A/Case B handling lives in `refs/wiki-capture.md`.
 
-The Wiki adapter generates component documentation pages — main page, platform sub-pages (iOS / Android), screenshots, and index updates. It is the only channel gated by **task type** (`component` only) and the only one that writes to a separate repo (the wiki repo configured in `figma-config.json`).
+The Wiki adapter generates component documentation pages  -  main page, platform sub-pages (iOS / Android), screenshots, and index updates. It is the only channel gated by **task type** (`component` only) and the only one that writes to a separate repo (the wiki repo configured in `figma-config.json`).
 
 ## Precondition gate
 
@@ -10,23 +10,23 @@ The Wiki adapter generates component documentation pages — main page, platform
 state.taskType === "component"  AND  figmaConfig.wiki.enabled === true
 ```
 
-If both are met → **Case A** (preconditions met) — proceed to scope multi-select.
-Otherwise → **Case B** (preconditions missing) — show the menu from `refs/wiki-capture.md` (setup / skip / disable / manual-note).
+If both are met → **Case A** (preconditions met)  -  proceed to scope multi-select.
+Otherwise → **Case B** (preconditions missing)  -  show the menu from `refs/wiki-capture.md` (setup / skip / disable / manual-note).
 
-In multi-repo tasks, wiki scope is the **primary** repo's `figma-config.wikiRepo` (single repo). Extras are not written to wiki — their PRs link back via the `## Related PRs` block injected by the PR adapter.
+In multi-repo tasks, wiki scope is the **primary** repo's `figma-config.wikiRepo` (single repo). Extras are not written to wiki  -  their PRs link back via the `## Related PRs` block injected by the PR adapter.
 
-## Case A — scope multi-select
+## Case A  -  scope multi-select
 
 ```
-Wiki'de ne güncelleyeyim?
-  [x] Ana component sayfası  ({Name}.md — variants, overview, testing IDs, a11y, analytics)
-  [x] iOS sub-page           ({Name}-iOS.md — initializer, usage, Code Connect)
-  [x] Screenshots            (assets/ — Figma LTR+RTL+light+dark + iOS snapshot)
+What should I update in the wiki?
+  [x] Main component page    ({Name}.md  -  variants, overview, testing IDs, a11y, analytics)
+  [x] iOS sub-page           ({Name}-iOS.md  -  initializer, usage, Code Connect)
+  [x] Screenshots            (assets/  -  Figma LTR+RTL+light+dark + iOS snapshot)
   [x] Index updates          (_Sidebar.md + ComponentImplementationStatus.md)
-  [ ] Diğer                  (adapter dispatch'i skip et, agent-log'a "manual wiki override" düş)
+  [ ] Other                  (skip the adapter dispatch, log "manual wiki override" to agent-log)
 ```
 
-Defaults reflect `prefs.global.wikiScope` — saved selection from the prior run.
+Defaults reflect `prefs.global.wikiScope`  -  saved selection from the prior run.
 
 ## Adapter dispatch
 
@@ -36,7 +36,7 @@ The selected scope routes to a platform skill:
 |---|---|---|
 | iOS / SwiftUI | `pipeline/skills/figma-ios/figma-component-wiki` | Reads `Configuration` + `+Modifiers` from the source, captures Figma screenshots via MCP / REST, runs Snapshot tests for iOS dark/light/RTL. |
 | Android / Compose | `pipeline/skills/figma-android/figma-component-wiki` | Reads Compose composables + previews, runs Paparazzi screenshots if available, otherwise generates from layout inspector. |
-| Generic | `pipeline/skills/figma-common/figma-component-wiki` | Used when `state.platform` is unknown (fallback path — typically a flag). |
+| Generic | `pipeline/skills/figma-common/figma-component-wiki` | Used when `state.platform` is unknown (fallback path  -  typically a flag). |
 
 Full per-skill contract: `refs/wiki-capture.md`.
 
@@ -44,23 +44,23 @@ Full per-skill contract: `refs/wiki-capture.md`.
 
 When the adapter writes pages **AND** `state.jiraId` is set **AND** `prefs.global.wikiToJiraComment === true`, the adapter posts a humanizer-passed summary as an additional Jira comment (component name + variant count + wiki URL).
 
-This comment is **independent** of the main `jira` channel comment — both can coexist on the same issue. Full triad contract: `refs/issue-jira-triad.md`.
+This comment is **independent** of the main `jira` channel comment  -  both can coexist on the same issue. Full triad contract: `refs/issue-jira-triad.md`.
 
 ## Wiki adapter modes (figma-config.wiki.mode)
 
 | Mode | Where pages live | When to choose |
 |---|---|---|
-| `submodule` | Wiki repo cloned under `Wiki/` inside the host project | Internal projects with Bitbucket — wiki repo is a submodule, commits land via PR. |
-| `in-repo` | Pages directly in the host repo (`docs/components/<Name>/…`) | Open-source projects without a separate wiki — Markdown lives in `docs/`. |
+| `submodule` | Wiki repo cloned under `Wiki/` inside the host project | Internal projects with Bitbucket  -  wiki repo is a submodule, commits land via PR. |
+| `in-repo` | Pages directly in the host repo (`docs/components/<Name>/...`) | Open-source projects without a separate wiki  -  Markdown lives in `docs/`. |
 | `github-wiki` | GitHub-managed `<repo>.wiki.git` | GitHub-hosted projects using the built-in Wiki feature. |
 | `separate-repo` | Independent wiki repo cloned to `~/.cache/multi-agent/wiki/<repo>/` | When the wiki repo is not a submodule of the host but lives under the same org. |
 
-Adapter implementation chooses the right git push target + commit message format based on `mode`. All four modes use the same content generation pipeline — only the commit / push step differs.
+Adapter implementation chooses the right git push target + commit message format based on `mode`. All four modes use the same content generation pipeline  -  only the commit / push step differs.
 
 ## Hard rules (must not regress)
 
 - Wiki adapter is the **only** channel allowed to skip silently when its precondition gate fails. PR / Jira / Confluence always run when selected.
 - Per the `figma-pipeline.md` rules, every component wiki page must include a variant matrix, accessibility identifiers, analytics events, and 3-layer test summary.
-- Screenshots cover light/dark + LTR/RTL — wiki adapter refuses to commit if any quadrant is missing.
+- Screenshots cover light/dark + LTR/RTL  -  wiki adapter refuses to commit if any quadrant is missing.
 - Body content language follows `prefs.global.outputLanguage`. Code identifiers, file paths, type names, design token names, and wiki markup stay verbatim across languages. The template (this doc) is English because `promptLanguage="en"` is locked.
-- Autopilot always pauses at the channels menu (per `phase-7-report.md` autopilot contract) — even in autopilot mode the user gets to confirm wiki scope.
+- Autopilot always pauses at the channels menu (per `phase-7-report.md` autopilot contract)  -  even in autopilot mode the user gets to confirm wiki scope.

package/pipeline/commands/multi-agent/refs/component-dispatch.md

@@ -1,6 +1,6 @@
 # Component Dispatch (Phase 3 short-circuit)
 
-> **TLDR** — When `taskType === "component"` (Figma URL in task description or instruction-driven figma workflow), multi-agent Phase 3 **does not run the TDD loop**. It delegates the entire phase to the `figma-to-component` skill and relays its subphases 3.0 – 3.8 via the existing phase-tracker contract. Implementation lives in the skill; multi-agent's job is classification, dispatch, and state report.
+> **TLDR**  -  When `taskType === "component"` (Figma URL in task description or instruction-driven figma workflow), multi-agent Phase 3 **does not run the TDD loop**. It delegates the entire phase to the `figma-to-component` skill and relays its subphases 3.0 - 3.8 via the existing phase-tracker contract. Implementation lives in the skill; multi-agent's job is classification, dispatch, and state report.
 
 This doc is referenced from `refs/phases/phase-3-dev.md`. Keeping it separate lets `phase-3-dev.md` remain tight (it's already the largest phase doc) and gives the orchestrator-report contract a stable URL for both Claude-side and Copilot-side implementations.
 
@@ -23,16 +23,16 @@ android           → pipeline/skills/figma-android/figma-to-component/
 web, multi-*      → HALT with clear error (no web target)
 ```
 
-If the chosen skill directory is missing, **halt with a user-visible error**. Do not silently fall back to TDD — a component task ran through the bugfix path would produce wrong artefacts and waste review cycles.
+If the chosen skill directory is missing, **halt with a user-visible error**. Do not silently fall back to TDD  -  a component task ran through the bugfix path would produce wrong artefacts and waste review cycles.
 
 ## Dispatch call
 
 Emit `→ dispatching figma-to-component <componentName>` via the progress contract, then launch a single agent invocation on the orchestrator skill with:
 
-- `figmaUrl` — primary positional argument
-- `agentState` — the path to `agent-state.json` so the orchestrator enriches `state.phases["3"].subphases[]`
-- `progressVerbosity` — forced to `verbose` when multi-agent runs in `mode: "autopilot"`; otherwise inherits `prefs.global.settings.progressVerbosity`
-- `mode` — `"dev"` for `--dev` runs; `"full"` otherwise
+- `figmaUrl`  -  primary positional argument
+- `agentState`  -  the path to `agent-state.json` so the orchestrator enriches `state.phases["3"].subphases[]`
+- `progressVerbosity`  -  forced to `verbose` when multi-agent runs in `mode: "autopilot"`; otherwise inherits `prefs.global.settings.progressVerbosity`
+- `mode`  -  `"dev"` for `--dev` runs; `"full"` otherwise
 
 ## Subphase contract
 
@@ -50,7 +50,7 @@ The orchestrator writes each of its 8 subphases to `state.phases["3"].subphases[
 }
 ```
 
-Multi-agent's `phase-tracker` reads this array without any component-specific code — the tracker UI renders one row per subphase under the Phase 3 row. No new phase-tracker field is required.
+Multi-agent's `phase-tracker` reads this array without any component-specific code  -  the tracker UI renders one row per subphase under the Phase 3 row. No new phase-tracker field is required.
 
 ## Multi-repo report
 
@@ -60,7 +60,7 @@ When multi-repo mode is active (`state.projects.length > 1`), the orchestrator r
 - View / Configuration / Modifiers / Preview → `repos.components`
 - Wiki markdown → `repos.wiki` (if `wiki.mode === submodule` or `separate-repo`) or `repos.components/.wiki/components/` (if `wiki.mode === in-repo`)
 
-Multi-agent does **not** split the component task into per-repo Phase 3 runs — the orchestrator is aware of the repo graph and sequences writes correctly (e.g. token writes to `common` precede component reads in `components`).
+Multi-agent does **not** split the component task into per-repo Phase 3 runs  -  the orchestrator is aware of the repo graph and sequences writes correctly (e.g. token writes to `common` precede component reads in `components`).
 
 ## Failure + resume
 
@@ -75,10 +75,10 @@ On orchestrator failure (subphase hits a build/test error that can't auto-fix, o
 
 When multi-agent is invoked with `--dev` (fast path: Init → Dev → Commit → Report), the orchestrator receives `mode: "dev"` and is allowed to elide:
 
-- Subphase 5C (unit tests) — structural + snapshot are still required
-- Subphase 7 (wiki) — can be deferred; Phase 7 in multi-agent will ask the user whether to run it post-commit
+- Subphase 5C (unit tests)  -  structural + snapshot are still required
+- Subphase 7 (wiki)  -  can be deferred; Phase 7 in multi-agent will ask the user whether to run it post-commit
 
-Phase 4 reviewer-skipping is **not** Phase 3's concern — Phase 4 decides based on `mode: "dev"` itself.
+Phase 4 reviewer-skipping is **not** Phase 3's concern  -  Phase 4 decides based on `mode: "dev"` itself.
 
 ## Cross-CLI parity
 

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

@@ -0,0 +1,179 @@
+---
+description: "Convention fallback defaults for /multi-agent:analysis Phase 2b Pass B. Activated only when repo evidence is none and standards binding is silent. Each application of a default opens a risk row in Section 20."
+---
+
+# Convention Defaults - Pass B Fallback Reference
+
+`/multi-agent:analysis` Phase 1c extracts conventions from each selected repo (folder structure, class naming, state model, test naming, accessibility identifier, localization key, DI registration). When `confidence == "none"` AND the standards binding source (`evidence.standards[]`) does not provide an explicit rule, Pass B falls back to the platform defaults catalogued here. Every applied default emits a row in Section 20 Risks of the rendered document.
+
+> **Language**: This file is read as a system prompt. Prose stays English. Examples carry generic placeholder names (`Foo`, `Bar`); the runtime substitutes the actual feature slug.
+
+> **Locked decision 23**: Applying a default is never silent. Pass B writes a footnote on the rendered cell pointing to this file and lists "convention fallback applied" in Section 20.
+
+## How the fallback chain works
+
+```
+Phase 1c extract -> confidence == "none" or "low"
+   |
+   v
+Read evidence.standards[]
+   |
+   +--- match found: cite standards file, use that pattern
+   |
+   v
+Read conventions-defaults.md (this file)
+   |
+   v
+Apply platform default + open Section 20 risk row
+```
+
+## C1 - Folder Structure
+
+| Platform | Default pattern | Example | Rationale |
+|---|---|---|---|
+| 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 |
+
+## C2 - Class Naming
+
+### C2a stateHolderNaming
+
+| Platform | Default pattern | Example |
+|---|---|---|
+| iOS | `<Feature>ViewModel` | `PassengerFlightViewModel` |
+| Android | `<Feature>ViewModel` | `PassengerFlightViewModel` |
+| Backend | not applicable | (services replace state holders) |
+| Frontend | `use<Feature>` hook | `usePassengerFlight` |
+
+### C2b viewNaming
+
+| Platform | Default pattern | Example |
+|---|---|---|
+| iOS | `<Feature>View` | `PassengerFlightView` |
+| Android | `<Feature>Screen` | `PassengerFlightScreen` |
+| Backend | not applicable | |
+| Frontend | `<Feature>Page` | `PassengerFlightPage` |
+
+### C2c navigatorNaming
+
+| Platform | Default pattern | Example | Notes |
+|---|---|---|---|
+| 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 |
+
+### C2d useCaseNaming
+
+| Platform | Default pattern | Example |
+|---|---|---|
+| iOS | `<Verb><Feature>UseCase` | `FetchPassengerFlightUseCase` |
+| Android | `<Verb><Feature>UseCase` | `FetchPassengerFlightUseCase` |
+| Backend | `<Feature>Service` | `PassengerFlightService` |
+| Frontend | hook with side effect | `usePassengerFlightQuery` |
+
+### C2e repositoryNaming
+
+| Platform | Default pattern | Example |
+|---|---|---|
+| 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` |
+
+### C2f dtoNaming
+
+| Platform | Default pattern | Example |
+|---|---|---|
+| iOS | `<Feature>RequestDTO`, `<Feature>ResponseDTO` | `PassengerFlightRequestDTO`, `PassengerFlightResponseDTO` |
+| Android | `<Feature>Dto` | `PassengerFlightDto` |
+| Backend | Pydantic `<Feature>In`, `<Feature>Out` | `PassengerFlightIn`, `PassengerFlightOut` |
+| Frontend | TypeScript `<Feature>Dto` | `PassengerFlightDto` |
+
+## C3 - UI State Model
+
+| Platform | Default | Example |
+|---|---|---|
+| 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'; ... }` |
+
+## C4 - Test Method Naming
+
+| Platform | Default pattern | Example |
+|---|---|---|
+| iOS Swift Testing | `@Test func <scenario>_<expected>()` | `@Test func fetch_validInput_returnsIdle()` |
+| 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', ...)` |
+
+## C5 - Accessibility Identifier
+
+| Platform | Default pattern | Example | Rationale |
+|---|---|---|---|
+| 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 |
+
+## C6 - Localization Key
+
+| Platform | Default pattern | Example | Notes |
+|---|---|---|---|
+| 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 |
+
+## C8 - SwiftUI Preview macro (iOS only)
+
+| Platform | Default pattern | Example | Rationale |
+|---|---|---|---|
+| iOS Swift 5.9+ | `#Preview` macro | `#Preview("Default") { FooView(viewModel: .preview(.idle)) }` | Modern Xcode 15+ Canvas binding, less boilerplate, supports named previews |
+| 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) | |
+
+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).
+
+## C7 - Dependency Injection
+
+| Platform | Default | Example | Rationale |
+|---|---|---|---|
+| 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 |
+
+## Risk row template (Section 20)
+
+When Pass B applies any default from this file, it emits the following row in Section 20 Risks of the rendered document:
+
+```markdown
+| <Cell name>: convention fallback applied | Pass B (auto) | Open |
+```
+
+With a follow-up question in the cell footnote:
+
+```
+^[fallback: conventions-defaults.md:C<n>; repo evidence none, standards binding silent. Confirm or override before dev.]
+```
+
+The follow-up triggers a human decision: keep the default, override to a different pattern, or update the standards binding source so the question disappears next time.
+
+## Maintenance
+
+When the team standardizes on a different default, update this file directly and rebuild the affected analyses. Avoid storing defaults inline in `analysis-template.md` or `analysis.md`; the indirection through this file keeps the source of truth visible and reviewable.
+
+## Locked decisions that govern this file
+
+- Locked 21: platform-agnostic template + Pass B render
+- Locked 22: convention extraction mandatory (Phase 1c)
+- Locked 23: convention fallback opens a risk row
+- Locked 24: every Pass B cell carries a footnote
+- Locked 28: SwiftUI Preview block mandatory for iOS SwiftUI views (Section 13.6, C8 convention)