@mmerterden/multi-agent-pipeline 11.2.0 → 11.3.1

package/pipeline/commands/multi-agent/{sync.md → sync/SKILL.md}

@@ -1,5 +1,5 @@
 ---
-description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, website, and remote-control."
+description: "One-shot sync of the entire multi-agent ecosystem: Claude Code, Copilot CLI, pipeline repo, and website."
 argument-hint: "[release] [--platform=<macos|linux|windows>]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, WebFetch
 ---
@@ -8,13 +8,13 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, WebFetch
 
 **One command. Full ecosystem sync. No arguments needed.**
 
-When invoked, it synchronizes all 7 targets in order. It detects what changed, updates only the stale ones, and returns a result report. The host platform (macOS / Linux / Windows) is auto-detected; all dispatch commands stay platform-agnostic through `~/.claude/lib/credential-store.sh`.
+When invoked, it synchronizes all targets in order. It detects what changed, updates only the stale ones, and returns a result report. The host platform (macOS / Linux / Windows) is auto-detected; all dispatch commands stay platform-agnostic through `~/.claude/lib/credential-store.sh`.
 
 **Input**: $ARGUMENTS (optional)
 
 | Arg | Meaning |
 |---|---|
-| (none) | Full ecosystem sync: Claude Code, Copilot CLI, pipeline repo, website, remote-control. |
+| (none) | Full ecosystem sync: Claude Code, Copilot CLI, pipeline repo, website. |
 | `release` | Full sync + version bump + tag + npm publish + website deploy |
 | `--platform=<macos\|linux\|windows>` | Override automatic platform detection. For CI / cross-platform smoke. |
 | `"change description"` | Apply the description to every target at once |
@@ -23,12 +23,10 @@ When invoked, it synchronizes all 7 targets in order. It detects what changed, u
 
 | # | Target | Path | Direction |
 |---|-------|-----|-----|
-| 0 | Figma source (deprecated) | `prefs.global.figmaSource.path` | skip (see memory `feedback_figma_source_deprecated`) |
 | 1 | Claude Code (source of truth) | `~/.claude/commands/multi-agent.md` + `~/.claude/commands/multi-agent/` + `~/.claude/agents/` + `~/.claude/scripts/` + `~/.claude/lib/` | source |
 | 2 | Copilot CLI | `~/.copilot/copilot-instructions.md` + `~/.copilot/skills/` | <- from Claude |
 | 3 | multi-agent-pipeline repo | `~/multi-agent-pipeline/pipeline/` | <- from Claude (genericized) |
 | 4 | Website | `{owner}/{website-host}` | <- version + features |
-| 5 | Remote Control | `{owner}/remote-control` | <- pipeline references |
 
 ## Platform Support (macOS / Linux / Windows)
 
@@ -55,7 +53,6 @@ The sync skill must run on all three platforms. Commands go through the platform
 Run every step automatically:
 
 ```
-Step 0: FIGMA_SYNC  SKIP (deprecated  -  feedback_figma_source_deprecated)
 Step 1: PLATFORM    Detect macOS / Linux / Windows (Git Bash / WSL); export PLATFORM env
 Step 1.5: DETECT    Compare timestamps, find stale targets
 Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 36 sub-command skills)
@@ -63,38 +60,10 @@ Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scr
 Step 3c: PLUGINS    pipeline shared/external -> multi-agent-plugins marketplace (rebuild knowledge/,
                      bump changed plugins' patch version, commit + push the plugins repo)
 Step 4: WEBSITE     Version + phase/model counts -> {website-host} (i18n + projects.ts)
-Step 5: REMOTE      Pipeline references -> remote-control README
-Step 6: Commit      Commit + push all changed repos
-Step 7: Report      Summary: synced targets, platform, changed files, deploy status
+Step 5: Commit      Commit + push all changed repos
+Step 6: Report      Summary: synced targets, platform, changed files, deploy status
 ```
 
-### Step 0  -  Figma source sync (opt-in)
-
-If `prefs.global.figmaSource.path` is set, run a plan-driven figma sync BEFORE any other step:
-
-```bash
-# 1. Once plan:
-bash "$REPO_ROOT/pipeline/scripts/sync-figma-source.sh" --plan
-
-# 2. Review the plan (.last-figma-sync-plan.json), confirm overlay skips,
-#    and approve the figma-ios vs figma-common routing for new upstream skills.
-
-# 3. If approved, apply:
-bash "$REPO_ROOT/pipeline/scripts/sync-figma-source.sh"
-```
-
-- **Plan-driven flow**: `--plan` once rebuilds the "what would change" view  - 
-  upstream skill → local name (post-rename) → target tree (figma-ios vs
-  figma-common) → overlay-skip status. Writes `.last-figma-sync-plan.json`.
-  Apply mode (no flag) executes the plan.
-- Script is idempotent  -  incremental, uses the `lastCommit` watermark.
-- Updates the figma-ios / figma-common skills (transform + placeholder).
-- Files marked `local-overlay: true` are preserved (they appear as `overlaySkip: true` in the plan).
-- figma-android/ trees are NOT touched (no upstream source today).
-- Appends a `### Sync YYYY-MM-DD (@ sha)` block to CHANGELOG.md.
-- The output of this step is committed in Step 3 (REPO).
-- If `figmaSource.path` is unset, the step is silently skipped.
-
 If nothing is stale → report "All targets up to date" and stop.
 
 ## Special inputs
@@ -142,6 +111,7 @@ If nothing is stale → report "All targets up to date" and stop.
    ```
    ~/.claude/commands/multi-agent.md      -> pipeline/commands/multi-agent.md
    ~/.claude/commands/multi-agent/        -> pipeline/commands/multi-agent/
+   ~/.claude/multi-agent-refs/            -> pipeline/multi-agent-refs/   (refs + pickers, non-command)
    ~/.claude/commands/sim-test.md         -> pipeline/commands/sim-test.md
    ~/.claude/agents/*.md                  -> pipeline/agents/
    ```
@@ -150,6 +120,16 @@ If nothing is stale → report "All targets up to date" and stop.
    - `~/.claude/CLAUDE.md`, `~/.claude/rules/`, `~/.claude/knowledge/`
    - `~/.claude/scripts/`  -  EXCEPT `pre-commit-check.sh`, `agent-guard.sh`, `agent-guard.py`, and `build-stack-plugins.mjs` (generic, synced)
    - `~/.claude/settings.json`
+   - **Any `~/.claude/commands/multi-agent/*.md` whose frontmatter has `local-only: true`** — these are user/repo-specific alias wrappers that delegate to a private marketplace plugin (e.g. corporate `ai-ios-engineering-toolkit` skills exposed as `multi-agent:<name>`). Syncing them would leak the private plugin/skill names into the public pipeline. Filter before copy: skip every source file containing `local-only: true`, and after copy assert none reached `pipeline/commands/`.
+     ```bash
+     # backstop: no local-only wrapper may exist in the synced target
+     grep -rl "^local-only: true" ~/multi-agent-pipeline/pipeline/commands/ 2>/dev/null \
+       && { echo "ABORT: local-only wrapper leaked into pipeline/commands"; exit 1; } || true
+     # backstop: no corporate marketplace/skill reference in the synced tree
+     grep -rniE "ai-ios-engineering-toolkit:(create-ui-component|evolve-ui-component|component-wiki|figma-setup|resource-utility)" \
+       ~/multi-agent-pipeline/pipeline/commands/ 2>/dev/null \
+       && { echo "ABORT: corporate reference leaked into pipeline/commands"; exit 1; } || true
+     ```
 
 6. **Cross-platform smoke gate** (final step of the REPO sync, before push):
    ```bash
@@ -233,23 +213,6 @@ git push origin main  # Vercel auto-deploy
 
 ---
 
-## Remote Control Sync (Step 5)
-
-```bash
-REMOTE_DIR="$HOME/remote-control"
-[ ! -d "$REMOTE_DIR" ] && gh repo clone {owner}/remote-control "$REMOTE_DIR"
-cd "$REMOTE_DIR" && git pull origin main
-```
-
-| File | What to sync |
-|-------|--------------|
-| `README.md` | Pipeline feature description |
-| `src/index.ts` | Help text / chip labels (if any) |
-
-Update only if the pipeline's public-facing features changed.
-
----
-
 ## Release Flow
 
 When invoked with the `release` argument:
@@ -262,9 +225,8 @@ When invoked with the `release` argument:
 5. Commit + TAG  git commit + git tag v{VERSION}
 6. PUSH          git push --tags -> release.yml auto-publish
 7. WEBSITE       Version + features -> {website-host}
-8. REMOTE        Update remote-control references
-9. COPILOT       Copilot CLI instructions + skills sync
-10. Report        Summary: version, touched repos, deploy status
+8. COPILOT       Copilot CLI instructions + skills sync
+9. Report        Summary: version, touched repos, deploy status
 ```
 
 ---
@@ -275,7 +237,7 @@ This runs on the Claude <-> Copilot axis — the two CLIs the pipeline supports
 
 | Claude Code | Copilot CLI |
 |-------------|-------------|
-| `~/.claude/commands/multi-agent/{cmd}.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
+| `~/.claude/commands/multi-agent/{cmd}/SKILL.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
 **36 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
@@ -287,7 +249,7 @@ local-autopilot, log, manual-test, prune-logs, purge, refactor, resume, review,
 scan, search, setup, stack, status, sync, test, update
 ```
 
-**NOT synced**: `refs/*`  -  lazy-load references, Claude Code specific
+**NOT synced**: `$HOME/.claude/multi-agent-refs/*`  -  lazy-load references, Claude Code specific
 
 **Claude -> Copilot**: add SKILL.md frontmatter (`name`, `description`, `user-invocable: true`, `argument-hint`)
 **Copilot -> Claude**: simplify the frontmatter (`description` + `allowed-tools`), add `$ARGUMENTS`

package/pipeline/lib/credential-store.sh

@@ -105,9 +105,11 @@ do_get() {
       val=$(secret-tool lookup service "$key" 2>/dev/null || true)
       ;;
     windows)
+      # Escape single quotes for PowerShell single-quoted strings ('' = literal ').
+      local key_esc="${key//\'/\'\'}"
       val=$(ps_run "
 \$ErrorActionPreference='SilentlyContinue'
-\$c = Get-StoredCredential -Target '$key'
+\$c = Get-StoredCredential -Target '$key_esc'
 if (\$c) { \$c.GetNetworkCredential().Password }
 " 2>/dev/null | tr -d '\r' || true)
       ;;
@@ -137,11 +139,13 @@ do_set() {
       printf '%s' "$val" | secret-tool store --label="$key" service "$key" >/dev/null
       ;;
     windows)
+      # Escape single quotes for PowerShell single-quoted strings ('' = literal ').
+      local key_esc="${key//\'/\'\'}" val_esc="${val//\'/\'\'}"
       # CredentialManager module: New-StoredCredential
       ps_run "
 \$ErrorActionPreference='Stop'
-\$pwd = ConvertTo-SecureString '$val' -AsPlainText -Force
-New-StoredCredential -Target '$key' -UserName '${USER:-${USERNAME:-claude}}' -SecurePassword \$pwd -Persist LocalMachine | Out-Null
+\$pwd = ConvertTo-SecureString '$val_esc' -AsPlainText -Force
+New-StoredCredential -Target '$key_esc' -UserName '${USER:-${USERNAME:-claude}}' -SecurePassword \$pwd -Persist LocalMachine | Out-Null
 " >/dev/null
       ;;
     *)
@@ -159,7 +163,7 @@ do_delete() {
   case "$PLATFORM" in
     macos)   security delete-generic-password -s "$key" >/dev/null 2>&1 || true ;;
     linux)   secret-tool clear service "$key" >/dev/null 2>&1 || true ;;
-    windows) ps_run "Remove-StoredCredential -Target '$key' -ErrorAction SilentlyContinue" >/dev/null 2>&1 || true ;;
+    windows) local key_esc="${key//\'/\'\'}"; ps_run "Remove-StoredCredential -Target '$key_esc' -ErrorAction SilentlyContinue" >/dev/null 2>&1 || true ;;
   esac
 }
 

package/pipeline/{commands/multi-agent → multi-agent-refs}/_account-picker.md

@@ -14,7 +14,7 @@ First step of every `multi-agent` flow **that touches a remote provider**.
 > repos, account-picker is bypassed and the state file's `accountId` is left
 > `null` with `tokens={}`. Phases 6/7 read these as "local-only" signals.
 
-> **Language**: Per `refs/rules.md` Language Application matrix  -  `AskUserQuestion.label` and `header` stay English (UI button + chip contract); `question` and `description` follow `outputLanguage`. Commit/PR/Jira payloads: subject + branch names + code identifiers stay English; body text follows `outputLanguage`.
+> **Language**: 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`. Commit/PR/Jira payloads: subject + branch names + code identifiers stay English; body text follows `outputLanguage`.
 
 ## Steps
 
@@ -28,7 +28,7 @@ First step of every `multi-agent` flow **that touches a remote provider**.
    - Bitbucket-based flow → `--providers bitbucket`
 
 3. **Picker UI**  -  show via AskUserQuestion (single-select):
-   - Breadcrumb (per `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).
+   - 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`

package/pipeline/{commands/multi-agent → multi-agent-refs}/_dev-context.md

@@ -6,7 +6,7 @@ description: "Internal  -  dev context (extra repos) picker for multi-agent."
 
 Selects extra repos the pipeline may touch beyond the primary repo(s)  -  typically submodules (e.g. SDKs vendored inside an app repo) or sibling libraries. Each candidate is enriched with a `canPush` flag so the picker can pre-select repos that the active account is allowed to edit, and surface read-only ones as advisory context the pipeline will not modify.
 
-> **Language**: Per `refs/rules.md` Language Application matrix  -  `AskUserQuestion.label` and `header` stay English (UI button + chip contract); `question` and `description` follow `outputLanguage`. Commit/PR/Jira/Wiki payloads: subject + branch names + code identifiers stay English; body text follows `outputLanguage`.
+> **Language**: 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`. Commit/PR/Jira/Wiki payloads: subject + branch names + code identifiers stay English; body text follows `outputLanguage`.
 
 ## Steps
 
@@ -34,7 +34,7 @@ Selects extra repos the pipeline may touch beyond the primary repo(s)  -  typica
    - `editable`  -  `canPush=true` → picker options, pre-selected
    - `readonly`  -  `canPush=false` → printed as an advisory note; not selectable
 
-3. **AskUserQuestion (multiSelect=true)**. Print the breadcrumb narrator line first (per `refs/picker-contract.md` Step narration): `<localized: "Step N/N: extra dev repos">`.
+3. **AskUserQuestion (multiSelect=true)**. Print the breadcrumb narrator line first (per `$HOME/.claude/multi-agent-refs/picker-contract.md` Step narration): `<localized: "Step N/N: extra dev repos">`.
    ```
    [N/N] Extra editable dev repos (multi):
      [x] <submodule-a>  (suggestion: from .gitmodules)

package/pipeline/{commands/multi-agent → multi-agent-refs}/_repo-picker.md

@@ -6,7 +6,7 @@ description: "Internal  -  multi-select repo picker for multi-agent."
 
 Used by `picker-issue`, `picker-jira`, `gh-num`, and `freetext` flows.
 
-> **Language**: Per `refs/rules.md` Language Application matrix  -  `AskUserQuestion.label` and `header` stay English (UI button + chip contract); `question` and `description` follow `outputLanguage`. Commit/PR/Jira/Wiki payloads: subject + branch names + code identifiers stay English; body text follows `outputLanguage`.
+> **Language**: 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`. Commit/PR/Jira/Wiki payloads: subject + branch names + code identifiers stay English; body text follows `outputLanguage`.
 
 ## Steps
 
@@ -30,7 +30,7 @@ Used by `picker-issue`, `picker-jira`, `gh-num`, and `freetext` flows.
    Local rows expose `localPath` (filesystem path) and a redacted `remoteUrl`
    (credentials stripped at cache time).
 
-2. **Show list** via AskUserQuestion (multiSelect=true). Print the breadcrumb narrator line first (per `refs/picker-contract.md` Step narration): `<localized: "Step 2/N: repo selection">`.
+2. **Show list** via AskUserQuestion (multiSelect=true). Print the breadcrumb narrator line first (per `$HOME/.claude/multi-agent-refs/picker-contract.md` Step narration): `<localized: "Step 2/N: repo selection">`.
    ```
    [2/N] Select repos (multi):
      [ ] <repo-a>      (github)

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/android-guide.md

@@ -1,6 +1,6 @@
 ## Android/Kotlin Component Generation Guide
 
-> **MUST: Figma MCP-first (BLOCKING).** If the task references any Figma frame (URL, node ID, or "from the design"), the Dev phase MUST call `mcp__claude_ai_Figma__get_design_context` for every frame BEFORE writing a single Composable line. Use the `CodeConnectSnippet` component name verbatim - no sound-alike substitutions. Authentication failure is not a skip path. Full rule, trigger conditions, and gate failure modes: `pipeline/rules/figma-pipeline.md` "MUST: Figma MCP-first (BLOCKING)". Phase wiring: `refs/phases/phase-3-dev.md` "MUST: Figma MCP-first (BLOCKING pre-step)".
+> **MUST: Figma MCP-first (BLOCKING).** If the task references any Figma frame (URL, node ID, or "from the design"), the Dev phase MUST call `mcp__claude_ai_Figma__get_design_context` for every frame BEFORE writing a single Composable line. Use the `CodeConnectSnippet` component name verbatim - no sound-alike substitutions. Authentication failure is not a skip path. Full rule, trigger conditions, and gate failure modes: `pipeline/rules/figma-pipeline.md` "MUST: Figma MCP-first (BLOCKING)". Phase wiring: `$HOME/.claude/multi-agent-refs/phases/phase-3-dev.md` "MUST: Figma MCP-first (BLOCKING pre-step)".
 
 When the task involves creating an Android UI component (Jetpack Compose), follow this architecture.
 

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/channels/jira.md

@@ -116,7 +116,7 @@ The dispatch summary line includes the comment URL with `?focusedCommentId=...`
 
 ## Wiki → Jira auto-link triad
 
-When the **Wiki** adapter writes pages on the same run AND `prefs.global.wikiToJiraComment === true`, the Wiki adapter also posts a humanizer-passed Jira comment summarizing wiki pages (component name + variant count + wiki URL). That secondary comment is independent of this adapter  -  both can coexist on the same issue. Full contract: `refs/issue-jira-triad.md`.
+When the **Wiki** adapter writes pages on the same run AND `prefs.global.wikiToJiraComment === true`, the Wiki adapter also posts a humanizer-passed Jira comment summarizing wiki pages (component name + variant count + wiki URL). That secondary comment is independent of this adapter  -  both can coexist on the same issue. Full contract: `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`.
 
 ## Hard rules (must not regress)
 

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

@@ -1,6 +1,6 @@
 # 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`.
+> 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 `$HOME/.claude/multi-agent-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`).
 
@@ -11,7 +11,7 @@ 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).
+Otherwise → **Case B** (preconditions missing)  -  show the menu from `$HOME/.claude/multi-agent-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.
 
@@ -34,17 +34,17 @@ The selected scope routes to a platform skill:
 
 | Platform | Skill | Notes |
 |---|---|---|
-| 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). |
+| iOS / SwiftUI | `ai-ios-engineering-toolkit: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 | `ai-android-engineering-toolkit:figma-component-wiki` | Reads Compose composables + previews, runs Paparazzi screenshots if available, otherwise generates from layout inspector. |
+| Generic | `ai-ios-engineering-toolkit:figma-component-wiki` (fallback) | Used when `state.platform` is unknown (fallback path  -  typically a flag). |
 
-Full per-skill contract: `refs/wiki-capture.md`.
+Full per-skill contract: `$HOME/.claude/multi-agent-refs/wiki-capture.md`.
 
 ## Wiki → Jira auto-link triad
 
 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: `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`.
 
 ## Wiki adapter modes (figma-config.wiki.mode)
 

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

@@ -0,0 +1,92 @@
+# 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 enabled `ai-<platform>-engineering-toolkit` **marketplace plugin's** component skill (`create-component`, falling back to `create-ui-component`) via the Skill tool. Implementation lives in the plugin; multi-agent's job is classification, dispatch, and state report. The pipeline no longer bundles its own `figma-to-component` orchestrator  -  component skills live in one place, the plugin marketplace.
+
+This doc is referenced from `$HOME/.claude/multi-agent-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.
+
+## Entry conditions
+
+Phase 3 checks, in order:
+
+1. `agent-state.json` has `taskType: "component"` (set by Phase 0 Step 7).
+2. `agent-state.json` has a non-null `figmaUrl`.
+
+Either missing → log the anomaly to `agent-log.md` ("component dispatch expected but state incomplete"), fall through to the standard TDD path. Never silently skip the Figma work.
+
+## Plugin skill resolution
+
+```
+project.platform  → component skill (enabled marketplace plugin, Claude Code)
+──────────────────────────────────────────────────────────────────────────────
+ios               → Skill: ai-ios-engineering-toolkit:create-component
+                            (fallback: ai-ios-engineering-toolkit:create-ui-component)
+android           → Skill: ai-android-engineering-toolkit:create-component
+                            (fallback: ai-android-engineering-toolkit:create-ui-component)
+web, multi-*      → HALT with clear error (no web target)
+```
+
+**Dual-name resolution.** The public (`multi-agent-plugins`) and a corporate/private marketplace named the same skill differently  -  `create-component` vs `create-ui-component`. Dispatch tries `create-component` first; if it is not available in the current repo, tries `create-ui-component`. (Same dual-name rule applies when `taskType` maps to evolve → `evolve-component`/`evolve-ui-component`, or fix → `fix-bug`.)
+
+If **neither** resolves, the platform's `ai-<platform>-engineering-toolkit` plugin is not enabled in this repo. **Halt with a user-visible error**: "component task requires the ai-<platform>-engineering-toolkit plugin enabled in this repo (`.claude/settings.local.json`)." Do not silently fall back to TDD  -  a component task ran through the bugfix path would produce wrong artefacts.
+
+## Dispatch call
+
+Emit `→ dispatching create-component <componentName>` via the progress contract, then invoke the resolved plugin skill via the **Skill tool** with:
+
+- `figmaUrl`  -  primary argument (the plugin skill's `<figma-url>`)
+- the component name + the analysis Section 6 (Bileşen Envanteri) row + Section 13.1 conventions as context (the plugin skill does not re-read the pipeline's analysis doc on its own  -  pass what it needs)
+- `mode`  -  `"dev"` vs `"full"` communicated so the plugin can elide tests/wiki on `--dev`
+
+Plugin skills are user-facing lifecycle skills; they do **not** accept an `agentState` path and do **not** write `agent-state.json`. State tracking therefore moves to the dispatch layer (next section).
+
+## Subphase contract (dispatch-layer owned)
+
+Because the plugin skill does not write pipeline state, **multi-agent's dispatch layer owns `state.phases["3"].subphases[]`**, not the skill. On dispatch, seed one coarse component-build subphase; on return, finalize it:
+
+```json
+{
+  "id": "3.component",
+  "name": "component-build (plugin: create-component)",
+  "status": "done",
+  "startedAt": "2026-04-16T18:12:02Z",
+  "endedAt":   "2026-04-16T18:13:47Z",
+  "buildStatus": "green",
+  "testStatus": "green"
+}
+```
+
+This is the accepted behavioral change from the old bundled orchestrator: subphase granularity is coarse (one component-build row) rather than the former 3.0-3.8 breakdown, because the plugin reports at its own granularity. If the plugin emits structured progress, the dispatch layer MAY map it to finer subphase rows, but coarse is the contract floor. Multi-agent's `phase-tracker` reads the array unchanged.
+
+## Multi-repo report
+
+When multi-repo mode is active (`state.projects.length > 1`), the dispatch layer passes `state.projects[]` to the plugin skill and sequences writes across the repo graph:
+
+- Tokens, accessibility metadata, testing identifiers, localisation keys → `repos.common`
+- 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 dispatch layer sequences the plugin invocation so token writes to `common` precede component reads in `components`. If the plugin skill is not repo-graph aware, dispatch runs it against `repos.components` and performs the `common` token/key writes itself around the call.
+
+## Failure + resume
+
+On failure (the plugin skill returns an unrecoverable build/test error, or the dispatch hits retry cap):
+
+1. The dispatch layer persists `{error, buildLog, testLog}` to `state.phases["3"].errors[]`.
+2. Multi-agent increments `state.phases["3"].retryCount`.
+3. Retry re-invokes the plugin skill (it is idempotent on an existing component; it reconciles rather than duplicating). There is no bundled `phase-<N>` resume anymore.
+4. Hard kill at `retryCount === 3` → surface the errors to the user, halt Phase 3. Do not loop indefinitely.
+
+## `--dev` mode behaviour
+
+When multi-agent is invoked with `--dev` (fast path: Init → Dev → Commit → Report), the dispatch layer passes `mode: "dev"` so the plugin skill can elide unit tests and wiki (structural + snapshot still required; wiki deferred to Phase 7). If the plugin does not honor a `mode` hint, dispatch simply skips the post-build wiki step itself.
+
+Phase 4 reviewer-skipping is **not** Phase 3's concern  -  Phase 4 decides based on `mode: "dev"` itself.
+
+## Cross-CLI behaviour (intentional divergence)
+
+Component dispatch is **no longer byte-identical across CLIs** and that is by design (see `cross-cli-contract.md` §1.1):
+
+- **Claude Code**: dispatches to the enabled `ai-<platform>-engineering-toolkit` marketplace plugin via the Skill tool (this doc).
+- **Copilot CLI**: has no plugin loader; it continues to use its standalone `~/.copilot/skills/figma-*` skill copies (frozen fallback). Copilot's resolution + progress lines follow those local skills.
+
+What still MUST match across CLIs: the `taskType === "component"` classification, the `state.phases["3"].subphases[]` shape the dispatch layer writes, and `--dev` elision semantics. Figma-skill *inventory* parity is no longer enforced. `smoke-cross-cli-behavior.sh` asserts only the classification + state-shape axis for components.

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/cross-cli-contract.md

@@ -28,65 +28,13 @@ Categories:
 
 > **Inventory drift is a contract violation.** Adding a slash command under `pipeline/commands/multi-agent/` without updating this list + its counterpart Copilot dir (`pipeline/skills/shared/core/multi-agent-<cmd>/`) is a merge blocker. `smoke-commands-skills-parity.sh` enforces command ↔ skill directory parity; `smoke-cross-cli-behavior.sh` enforces behavior parity. This doc is the authoritative command list  -  bump the count + table together.
 
-### 1.1 Figma component subphase skills
+### 1.1 Figma / component work (plugin-based on Claude Code; NOT parity-enforced)
 
-In addition to the 36 top-level multi-agent commands, the figma-to-component pipeline ships platform-specific skills that multi-agent dispatches from Phase 3 (see `refs/component-dispatch.md`). The structure is **platform-parallel iOS + Android with a shared common pool**:
+Component work is **no longer a bundled pipeline skill set**. Claude Code dispatches `taskType === "component"` to the enabled `ai-<platform>-engineering-toolkit` **marketplace plugin** (`create-component`, fallback `create-ui-component`) via the Skill tool  -  full contract in `$HOME/.claude/multi-agent-refs/component-dispatch.md`. The pipeline no longer ships `pipeline/skills/figma-ios|figma-android|figma-common`; the pipeline-unique component skills (iterate loops, performance harness, validate/review, commit, adapters, wiki) were absorbed into the `ai-ios-engineering-toolkit` plugin so component skills live in one place.
 
-| Location | Skill count | Purpose |
-|---|---|---|
-| `pipeline/skills/figma-ios/` | 5 | iOS-only Phase 3 sub-skills (SwiftUI-specific) |
-| `pipeline/skills/figma-android/` | 5 | Android-only Phase 3 sub-skills (Jetpack Compose-specific) |
-| `pipeline/skills/figma-common/` | 31 | Platform-agnostic helpers (iterate / commit / wiki setup / MCP auth / performance harness / cross-cutting integration adapters / etc.) |
-
-Both Claude Code and Copilot CLI MUST expose every skill with identical argument shape, identical progress-line emission, and identical state writes. Inventory divergence (skill exists on one side but not the other) is a contract violation and blocks merge.
-
-**iOS and Android parallel set** (same 5 skill names under each platform dir):
-
-| Skill | Scope | iOS path | Android path |
-|---|---|---|---|
-| `figma-to-component` | Orchestrator (3.0-3.8) | `pipeline/skills/figma-ios/figma-to-component/` | `pipeline/skills/figma-android/figma-to-component/` |
-| `figma-component-implement` | 3.4 code gen | `pipeline/skills/figma-ios/figma-component-implement/` | `pipeline/skills/figma-android/figma-component-implement/` |
-| `figma-component-test` | 3.5 tests | `pipeline/skills/figma-ios/figma-component-test/` | `pipeline/skills/figma-android/figma-component-test/` |
-| `figma-component-code-connect` | 3.6 mapping publish | `pipeline/skills/figma-ios/figma-component-code-connect/` | `pipeline/skills/figma-android/figma-component-code-connect/` |
-| `figma-component-wiki` | 3.7 wiki (4 adapters) | `pipeline/skills/figma-ios/figma-component-wiki/` | `pipeline/skills/figma-android/figma-component-wiki/` |
-
-**Common pool** (all 31 skills under `pipeline/skills/figma-common/`  -  platform-agnostic, dispatched regardless of iOS/Android):
+**Intentional cross-CLI divergence.** Copilot CLI has no marketplace-plugin loader, so it retains its own standalone `~/.copilot/skills/figma-*` copies as a frozen fallback. Component/figma dispatch is therefore **not** byte-identical across CLIs, and figma-skill *inventory* parity is **no longer enforced**  -  this is a deliberate exception to the parity rule, not drift.
 
-| Skill | Scope |
-|---|---|
-| `figma-component-start` | Issue → branches |
-| `figma-component-confluence-sync` | 7b confluence XHTML |
-| `figma-component-status-update` | Confluence dashboard refresh |
-| `figma-commit` | 14-item review + PR |
-| `figma-iteration-commit` | Iteration/develop commit |
-| `figma-issue` | Issue + Jira auto-create |
-| `figma-iterate` | Auto batch loop |
-| `figma-cli-iterate` | CLI iterate (all phases) |
-| `figma-cli-lean-iterate` | CLI iterate (skip test+wiki) |
-| `figma-cli-iterate-mend` | Re-implement discarded |
-| `figma-cli-skip` | Mark skipped |
-| `figma-fix` | Targeted bug fix |
-| `figma-mend` | Re-implement from scratch |
-| `figma-review` | Interactive review |
-| `figma-validate` | Pre-impl validation |
-| `figma-setup` | Env wizard |
-| `figma-remote-mcp-auth` | Figma MCP OAuth |
-| `figma-ui-patterns` | Pattern index |
-| `figma-utility` | Figma data fetch |
-| `figma-skip` | Skip + update Confluence |
-| `figma-form-integration` | Form protocol adapter |
-| `figma-price-integration` | Price protocol adapter |
-| `figma-navigation` | Navigation pattern adapter (native-first / `ui.navigationSystem`) |
-| `figma-overlays` | Overlay pattern adapter (native-first / `ui.overlaySystem`) |
-| `figma-bottom-sheets` | Bottom-sheet/detent adapter (native-first / `ui.sheetSystem`) |
-| `figma-evolve-component` | Reconcile drift + additive extend (human-gated) |
-| `performance-start` | Perf-tracked component start |
-| `performance-swiftui` | Perf-optimized pipeline |
-| `performance-tour` | Batch produce components |
-| `performance-review-next` | Interactive batch review |
-| `performance-iteration-commit-all` | Batch validate + push all |
-
-Total figma skill count: **41** (5 iOS + 5 Android + 31 Common).
+What still MUST match across CLIs for component tasks: the `taskType === "component"` classification, the `state.phases["3"].subphases[]` shape the dispatch layer writes, and `--dev` elision semantics. Resolution/routing is Claude-plugin vs Copilot-local-copy by design.
 
 ### 1.2 Store-compliance skills
 
@@ -99,24 +47,9 @@ Two parallel shared/core skills under `pipeline/skills/shared/core/` wrap extern
 
 Both skills are wired to 4 consumers: `/multi-agent:test "store-ready"` (primary), Phase 4 Security Auditor (`pipeline/agents/security-auditor.md`), `/multi-agent:review` + SKILL.md counterpart, `/multi-agent:channels` PR-body auto-augmentation. Contract enforced by `smoke-compliance-skills.sh` (46 assertions).
 
-### 1.2 Figma-skill routing from multi-agent
-
-Multi-agent Phase 3 resolves the orchestrator via `figmaConfig.project.platform`:
-
-- `"ios"` → `pipeline/skills/figma-ios/figma-to-component/SKILL.md`
-- `"android"` → `pipeline/skills/figma-android/figma-to-component/SKILL.md`
-- anything else → halt with a clear error
-
-Resolution logic MUST be byte-identical across CLIs. The full routing contract lives in `refs/component-dispatch.md`.
-
-### 1.3 Figma skill frontmatter MUST carry (platform-specific skills only)
-
-- `name` matching the directory name
-- `status: wip-v5` (or `stable`/`deprecated` once released)
-- `sourced-from: upstream/<orig>` or `sourced-from: derived-from/<peer-path>` for platform-specific peers
-- `platform: ios` or `platform: android` when the skill is platform-specific
+### 1.3 Figma-skill routing from multi-agent (superseded)
 
-Enforced by `smoke-figma-skill-import.sh` (iOS), `smoke-figma-android-parity.sh` (Android), `smoke-cross-cli-behavior.sh` (cross-platform inventory parity).
+Superseded by §1.1: Claude Code resolves component dispatch to the marketplace plugin (dual-name `create-component`/`create-ui-component`; full contract in `$HOME/.claude/multi-agent-refs/component-dispatch.md`); Copilot CLI uses its local `~/.copilot/skills/figma-*` copies. No shared filesystem-path routing table or figma-skill frontmatter/inventory parity remains under enforcement.
 
 ---
 
@@ -182,7 +115,7 @@ The top-level orchestrator has two deliberately different shapes on the two CLIs
 
 | Surface | File | Shape | Why |
 |---|---|---|---|
-| Claude Code (colon-form) | `pipeline/commands/multi-agent.md` | ~300 lines  -  thin dispatcher that routes to `refs/phases/phase-N-*.md` on demand | Claude Code supports lazy-loaded reference files (`@refs/phases/...`), so only the active phase's docs enter the context window. Saves tokens. |
+| Claude Code (colon-form) | `pipeline/commands/multi-agent.md` | ~300 lines  -  thin dispatcher that routes to `$HOME/.claude/multi-agent-refs/phases/phase-N-*.md` on demand | Claude Code supports lazy-loaded reference files (`@refs/phases/...`), so only the active phase's docs enter the context window. Saves tokens. |
 | Copilot CLI (dash-form) | `pipeline/skills/shared/core/multi-agent/SKILL.md` | ~830 lines  -  full inline orchestrator with all 8 phase specs embedded | Copilot CLI loads the whole SKILL.md into context once the skill is dispatched; it doesn't have an equivalent of Claude's ref-file loading pattern. Embedding keeps behavior identical without relying on a feature Copilot lacks. |
 
 **What must stay identical** (byte-level) across the two files:
@@ -293,7 +226,7 @@ Modifier flags are orthogonal and compose:
 
 ## 7. Platform Guards (macOS / Linux / WSL)
 
-Commands invoked via Copilot CLI may run on Linux or WSL. Claude Code currently macOS-only. Shell code in `pipeline/skills/figma-common/` command files must be portable.
+Commands invoked via Copilot CLI may run on Linux or WSL. Claude Code currently macOS-only. Shell code in `pipeline/skills/shared/core/` command files and in `pipeline/lib` / `pipeline/scripts` must be portable.
 
 For Keychain I/O the canonical path is **`~/.claude/lib/credential-store.sh`** (or `~/.copilot/lib/credential-store.sh` on Copilot installs). The shell driver detects platform internally and auto-delegates to `keychain.py` (Python helper, macOS / Linux) or PowerShell `CredentialManager` (Windows). Call sites stay platform-agnostic  -  no per-OS branching needed.
 
@@ -304,7 +237,7 @@ For Keychain I/O the canonical path is **`~/.claude/lib/credential-store.sh`** (
 | Clipboard read |  -  (still needs a per-platform branch  -  there is no helper) | `pbpaste` (macOS) · `wl-paste` (Wayland) · `xclip -selection clipboard -o` (X11) |
 | Clipboard clear |  -  | `pbcopy < /dev/null` (macOS) · `printf '' \| wl-copy` (Wayland) · `printf '' \| xclip -selection clipboard` (X11) |
 
-For clipboard ops, callers still gate with `if command -v pbpaste >/dev/null; then ...; elif command -v wl-paste ...; elif command -v xclip ...; fi`. A future `pipeline/lib/clipboard.sh` could absorb that pattern; until it exists, keep the inline guard in figma skill bash blocks.
+For clipboard ops, callers still gate with `if command -v pbpaste >/dev/null; then ...; elif command -v wl-paste ...; elif command -v xclip ...; fi`. A future `pipeline/lib/clipboard.sh` could absorb that pattern; until it exists, keep the inline guard in skill bash blocks.
 
 ---
 
@@ -316,7 +249,7 @@ This contract is validated by:
 - `smoke-commands-skills-parity.sh` (50 assertions)  -  enforces colon-form command ↔ dash-form skill directory parity
 - `smoke-compliance-skills.sh` (45 assertions)  -  enforces store-compliance skill catalog + 4 consumer wiring
 - `smoke-personal-data.sh`  -  extended in 0.5.5 to treat deprecated placeholders (`{github-username}`, `{your-website}`, `{website-repo}`) as leaks; adds `mmerterden` to public-handle blocklist for generic docs
-- `pre-push-check.sh`  -  runs both smoke tests before any push that touches `pipeline/skills/figma-common/` commands
+- `pre-push-check.sh`  -  runs the cross-CLI + personal-data smoke tests before any push that touches `pipeline/skills/shared/core/` commands
 - `sync.md` (Section 2 REPO step)  -  genericization lookup table MUST match Section 2 of this contract
 
 ---

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/features/verify-by-test.md

@@ -38,4 +38,4 @@ Adds one Sonnet call plus up to `maxFindings` single-test runs (and build-lock c
 
 ## Reference
 
-Wiring: `refs/phases/phase-4-review.md` Step 3.7. Schema: `pipeline/schemas/triage-output.schema.json` v3.2.0 (`$defs.verification`). Evidence gate: `pipeline/scripts/evidence-gate.mjs`. Prefs: `prefs.global.verifyByTest` in `pipeline/schemas/prefs.schema.json`.
+Wiring: `$HOME/.claude/multi-agent-refs/phases/phase-4-review.md` Step 3.7. Schema: `pipeline/schemas/triage-output.schema.json` v3.2.0 (`$defs.verification`). Evidence gate: `pipeline/scripts/evidence-gate.mjs`. Prefs: `prefs.global.verifyByTest` in `pipeline/schemas/prefs.schema.json`.

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/generate-issue.md

@@ -11,7 +11,7 @@ Consumed by `generate.md`. This ref is never invoked directly.
 - **Standard template is the baseline.** The description structure comes from the type's standard template (see [7/12]), not from a mined heading set. Mining informs summary prefix, labels, components, priority norm, sprint placement, and test-scenario style  -  never replaces the standard section skeleton.
 - **Auto-sizing.** A conditional section renders only when its trigger is present. No empty placeholder headings  -  if there is nothing to put in a conditional section, it does not appear.
 - **Issue content language follows `prefs.global.outputLanguage`.** Summary and description are written in the user's output language (intentional exception to the "external payloads stay English" default  -  the issue is authored FOR the user's team). Code identifiers, file paths, and URLs stay verbatim. AskUserQuestion `question`/`description` also follow `outputLanguage`; `label`/`header` stay English.
-- **UTF-8 verbatim POST path** (same as `refs/channels/jira.md`): description body goes to a file, `jq -n --rawfile` builds the payload, `curl --data-binary @file` ships it. Never round-trip through `unicode_escape`/`latin-1`, never hand-roll a re-encoding helper. Jira wiki markup (`h3.` headings, `[text|url]` links), real newlines, no HTML entities.
+- **UTF-8 verbatim POST path** (same as `$HOME/.claude/multi-agent-refs/channels/jira.md`): description body goes to a file, `jq -n --rawfile` builds the payload, `curl --data-binary @file` ships it. Never round-trip through `unicode_escape`/`latin-1`, never hand-roll a re-encoding helper. Jira wiki markup (`h3.` headings, `[text|url]` links), real newlines, no HTML entities.
 - **Humanizer pass** on the description body after composition, before the preview render.
 - **Read-only until approval.** Steps 1-9 perform only GET requests. The first write of any kind is the `POST /rest/api/2/issue` in step [10/12].
 
@@ -65,7 +65,7 @@ TOKEN=$(~/.claude/lib/credential-store.sh get "$ACCOUNT_JIRA_TOKEN_KEY")
 
 ### [2/12] Resolve project key
 
-Fallback chain (same as `refs/issue-jira-triad.md` Create path):
+Fallback chain (same as `$HOME/.claude/multi-agent-refs/issue-jira-triad.md` Create path):
 1. `figmaConfig.jira.projectKey` (per-project config, when running inside a configured repo)
 2. `prefs.global.defaultJiraKey`
 3. Fetch and ask:

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/issue-jira-triad.md

@@ -2,7 +2,7 @@
 
 > **TLDR**  -  When a GitHub issue triggers the pipeline and has no Jira ID, the `autoJiraFromGithubIssue` policy decides whether to auto-create a Jira task (and patch the GitHub issue body with the new Jira link). Phase 7 then posts a humanizer'd wiki-content summary back as a Jira comment, closing the loop. Autopilot treats `ask` as `always`.
 
-This doc is referenced from `refs/phases/phase-0-init.md` Step 1 (GitHub issue input) and `refs/phases/phase-7-report.md` Step 2 (component wiki). Keeps the phase docs tight and gives the triad contract a stable home.
+This doc is referenced from `$HOME/.claude/multi-agent-refs/phases/phase-0-init.md` Step 1 (GitHub issue input) and `$HOME/.claude/multi-agent-refs/phases/phase-7-report.md` Step 2 (component wiki). Keeps the phase docs tight and gives the triad contract a stable home.
 
 ## The triad at a glance
 

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/keychain.md

@@ -21,7 +21,7 @@ When a token resolves but the service rejects it (401 / 403), do not silently sk
 
 The question asks a *choice*; the replacement value still flows through the clipboard, never chat. `smoke-no-token-prompt.sh` greps for value-prompts (`enter token`, `paste token`, `API key:`) - decision labels like `Regenerate` / `Skip and continue` do not trip it.
 
-Expiry is also checked **proactively at init**: Phase 0 Step 0.7 (`refs/phases/phase-0-init.md`) probes every token the run will need with one cheap call each (cached via `global.serviceStatus`, TTL 300s) and runs this same decision at init instead of waiting for the first mid-run 401. The mid-run 401 path stays as the safety net.
+Expiry is also checked **proactively at init**: Phase 0 Step 0.7 (`$HOME/.claude/multi-agent-refs/phases/phase-0-init.md`) probes every token the run will need with one cheap call each (cached via `global.serviceStatus`, TTL 300s) and runs this same decision at init instead of waiting for the first mid-run 401. The mid-run 401 path stays as the safety net.
 
 #### Figma MCP token lifecycle (critical)
 

package/pipeline/{commands/multi-agent/refs → multi-agent-refs}/phases/log-format.md

@@ -75,7 +75,7 @@ Verdict: unverified (2 reviewers)
 
 ## Handoff - end of Phase {N} ({name}) - {ISO timestamp}
 
-(v10.8.0, appended chronologically by the phase-boundary checkpoint  -  one block per phase transition, the LATEST block is authoritative. Written by the orchestrator from state it already holds; no LLM call, ~15 lines max. `resume.md` Step 3 and post-`/compact` re-grounding read this block FIRST. Format spec: `refs/phases/operations.md`.)
+(v10.8.0, appended chronologically by the phase-boundary checkpoint  -  one block per phase transition, the LATEST block is authoritative. Written by the orchestrator from state it already holds; no LLM call, ~15 lines max. `resume.md` Step 3 and post-`/compact` re-grounding read this block FIRST. Format spec: `$HOME/.claude/multi-agent-refs/phases/operations.md`.)
 
 - Done: {up to 3 bullets of completed outcomes}
 - Remaining: {ordered list of remaining phases / sub-steps}