@mmerterden/multi-agent-pipeline 13.5.1 → 14.0.0

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

@@ -177,7 +177,7 @@ vercel deploy --token=vcp_...
 vercel deploy --token "$VERCEL_TOKEN"
 ```
 
-The wrapper at `pipeline/lib/vercel-deploy.sh` (installed to `~/.claude/lib/`, `~/.copilot/lib/` and `~/.codex/lib/` with the rest of the shell libraries) refuses any `--token=` argv input, runs the CLI with `VERCEL_TOKEN` env, and pipes every stdout/stderr line through a redact filter that scrubs `vcp_...`, `Bearer ...`, and JSON-body token shapes. Regression gate: `smoke-vercel-deploy-redact.sh` (12 assertions).
+The wrapper at `$HOME/.claude/lib/vercel-deploy.sh` (installed to `~/.claude/lib/`, `~/.copilot/lib/` and `~/.codex/lib/` with the rest of the shell libraries) refuses any `--token=` argv input, runs the CLI with `VERCEL_TOKEN` env, and pipes every stdout/stderr line through a redact filter that scrubs `vcp_...`, `Bearer ...`, and JSON-body token shapes. Regression gate: `smoke-vercel-deploy-redact.sh` (12 assertions).
 
 Same rule applies to any future provider wrapper (e.g. `cloudflare-deploy.sh`, `npm-publish.sh`)  -  never pass tokens via argv when the underlying CLI may echo argv on failure.
 
@@ -196,19 +196,21 @@ When any task references a Figma frame (URL, node ID, or free-text "from the des
 
 | Tier | Source | When chosen | Code Connect available |
 |---|---|---|---|
-| 1 | Figma MCP server (`mcp__claude_ai_Figma__get_design_context`, `get_screenshot`, `get_metadata`); MCP token resolves through `prefs.global.keychainMapping.figma_mcp` (for MCP server config bootstrap) | MCP auth succeeds (after one re-auth retry; on continued failure the user is asked: recreate the MCP token or continue with the PAT  -  never a silent fallthrough) | yes (`CodeConnectSnippet` blocks) |
-| 2 | Figma REST API (`GET /v1/files/{fileKey}/nodes`, `GET /v1/images/{fileKey}`) with Personal Access Token resolved via `~/.claude/lib/credential-store.sh get <logical-key>` where `<logical-key>` = `prefs.global.keychainMapping.figma_pat` | Tier 1 unreachable AND PAT is mapped; on a 401/403 the user is asked the Expired-token decision (regenerate / different token / skip) before moving to Tier 3 | no, fall back to repo `*.figma.swift` / `*.figma.kt` mappings keyed by `fileKey` + `nodeId` |
+| 1 | Figma MCP server (`mcp__claude_ai_Figma__get_design_context`, `get_screenshot`, `get_metadata`); MCP token resolves through `prefs.global.keychainMapping.figma_mcp` (for MCP server config bootstrap) | The host serves the `mcp__claude_ai_Figma__*` tools AND MCP auth succeeds (after one re-auth retry; on continued auth failure the user is asked: recreate the MCP token or continue with the PAT  -  never a silent fallthrough) | yes (`CodeConnectSnippet` blocks) |
+| 2 | Figma REST API (`GET /v1/files/{fileKey}/nodes`, `GET /v1/images/{fileKey}`) with Personal Access Token resolved via `~/.claude/lib/credential-store.sh get <logical-key>` where `<logical-key>` = `prefs.global.keychainMapping.figma` | Tier 1 unreachable AND PAT is mapped; on a 401/403 the user is asked the Expired-token decision (regenerate / different token / skip) before moving to Tier 3 | no, fall back to repo `*.figma.swift` / `*.figma.kt` mappings keyed by `fileKey` + `nodeId` |
 | 3 | User-attached screenshot in chat or task attachment | Tiers 1 + 2 both unreachable AND user has provided a screenshot | no  -  record an Open Question, pick the closest existing primitive WITH user confirmation, set Phase 4 reviewer flag to `review_blocking` |
 
+**Tier 1 availability is per host, and "unavailable" is not "auth failed".** Tools absent (the normal case on Copilot CLI and Codex CLI, where the installer registers only `dev-toolkit`) means Tier 2 is the expected entry point: record `figmaAccess.tier1Unavailable = "host"`, skip the re-auth retry, and never raise the MCP-token question. Tools present but failing auth is `"auth"`, where the retry does apply. Probe mechanics: `phases/phase-0-init.md`.
+
 **Halt condition.** If all three tiers fail, halt the run and ask the user how to proceed. Never substitute primitives, never guess from Confluence prose, never derive layout from a text description.
 
-**Synced-file rule.** The literal Keychain service name for the Figma PAT is NEVER embedded in any synced file under `~/.claude/commands/` or `~/.copilot/skills/`. The mapping resolves at runtime through `prefs.global.keychainMapping.figma_pat`. See the Synced Command Hygiene rule below.
+**Synced-file rule.** The literal Keychain service name for the Figma PAT is NEVER embedded in any synced file under `~/.claude/commands/` or `~/.copilot/skills/`. The mapping resolves at runtime through `prefs.global.keychainMapping.figma`. See the Synced Command Hygiene rule below.
 
 Full chain definition, REST endpoints, URL parsing, Code Connect snippet rules, and the pre-UI checklist live in `rules/figma-pipeline.md` "MUST: Figma access - 3-tier fallback chain (BLOCKING, pipeline-wide)". Do not duplicate that text here; the canonical copy is the rule file.
 
 ### Figma Access by Phase (pipeline-wide BLOCKING, v9.0.0)
 
-Per Locked decision 30 of `/multi-agent:analysis` and the parallel rule in `pipeline/rules/figma-pipeline.md`, Figma MCP / REST is allowed only in the analysis phase. Phase 2 through Phase 7 in every orchestrator mode (including `--dev`, `--local`, `--autopilot` combinations) consume the analysis document + repo Code Connect mappings.
+Per Locked decision 30 of `/multi-agent:analysis` and the parallel rule in `$HOME/.claude/rules/figma-pipeline.md`, Figma MCP / REST is allowed only in the analysis phase. Phase 2 through Phase 7 in every orchestrator mode (including `--dev`, `--local`, `--autopilot` combinations) consume the analysis document + repo Code Connect mappings.
 
 | Phase | MCP | REST | Sole design source |
 |---|---|---|---|

package/pipeline/multi-agent-refs/swiftui-guide.md

@@ -1,6 +1,6 @@
 ## SwiftUI Component Generation Guide (Generic)
 
-> **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 UI 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)".
+> **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 UI 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: `$HOME/.claude/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 a SwiftUI component (any project), follow this architecture.
 These practices come from the battle-tested Figma-to-SwiftUI pipeline  -  apply them in every iOS project.

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

@@ -74,8 +74,8 @@ Phases by mode:
 | Mode | Phases |
 |---|---|
 | Full pipeline | 0,1,2,3,4,5,6,7 |
-| `--dev` | 0,3,5,6,7 |
-| `--dev autopilot`, `--dev local`, `--dev local autopilot` | 0,3,6,7 (Phase 5 interactive test gate dropped) |
+| `--dev` | 0,3,4,5,6,7 |
+| `--dev autopilot`, `--dev local`, `--dev local autopilot` | 0,3,4,6,7 (Phase 5 interactive test gate dropped) |
 | `--autopilot` | same as full pipeline, with confirmations skipped |
 
 Register each phase:
@@ -112,22 +112,23 @@ Why: an agent reasoning "this is a `--dev` task, so phases 1/2/4 will be skipped
 The correct sequence is **always**:
 
 ```text
-# Step A  -  register every phase tile in the active mode's set, in phase-number order
+# Step A  -  register every phase tile in the ACTIVE MODE'S SET, in phase-number
+# order. A phase outside the mode's set gets no TaskCreate at all  -  the example
+# below is the full pipeline, whose set happens to be all eight.
 TaskCreate(Phase 0)  → taskId₀
-TaskCreate(Phase 1)  → taskId₁     # even if Phase 1 will be skipped in this mode
+TaskCreate(Phase 1)  → taskId₁
 TaskCreate(Phase 2)  → taskId₂
 TaskCreate(Phase 3)  → taskId₃
-TaskCreate(Phase 4)  → taskId₄     # even if Phase 4 will be skipped in this mode
+TaskCreate(Phase 4)  → taskId₄
 TaskCreate(Phase 5)  → taskId₅
 TaskCreate(Phase 6)  → taskId₆
 TaskCreate(Phase 7)  → taskId₇
 
 # Step B  -  only AFTER every tile is created, apply status updates
 TaskUpdate(taskId₀, status="in_progress")              # Phase 0 starts
-# `--dev` mode immediately also fires:
-TaskUpdate(taskId₁, status="completed", activeForm="[SKIPPED]")
-TaskUpdate(taskId₂, status="completed", activeForm="[SKIPPED]")
-TaskUpdate(taskId₄, status="completed", activeForm="[SKIPPED]")
+# A phase that IS in the set but short-circuits at runtime flips here, e.g. a
+# full-pipeline run whose Phase 5 test gate is suppressed by autopilot:
+TaskUpdate(taskId₅, status="completed", activeForm="[SKIPPED]")
 ```
 
 Mode-specific phase sets:
@@ -135,10 +136,10 @@ Mode-specific phase sets:
 | Mode | TaskCreate set (in order) |
 |---|---|
 | Full pipeline (`/multi-agent`, `:autopilot`, `:local`, `:local-autopilot`) | 0 → 1 → 2 → 3 → 4 → 5 → 6 → 7 (all 8) |
-| `:dev` | 0 → 3 → 5 → 6 → 7 (5 phases  -  1/2/4 omitted entirely) |
-| `:dev-autopilot`, `:dev-local`, `:dev-local-autopilot` | 0 → 3 → 6 → 7 (4 phases  -  1/2/4/5 omitted entirely; the autopilot/local variants drop the interactive Phase 5 test gate) |
+| `:dev` | 0 → 3 → 4 → 5 → 6 → 7 (6 phases  -  1/2 omitted entirely) |
+| `:dev-autopilot`, `:dev-local`, `:dev-local-autopilot` | 0 → 3 → 4 → 6 → 7 (5 phases  -  1/2/5 omitted entirely; the autopilot/local variants drop the interactive Phase 5 test gate) |
 
-Note: in `--dev` modes the omitted phases (1, 2, 4  -  plus 5 in the autopilot/local variants) **do not get TaskCreate calls at all**  -  they're not part of the mode's phase set. The "[SKIPPED]" pattern above only applies if a normally-included phase is conditionally skipped at runtime. The authoritative per-mode set is the `for p in ...` init block in each mode's own entry doc; this table mirrors those blocks.
+Note: in `--dev` modes the omitted phases (1, 2  -  plus 5 in the autopilot/local variants) **do not get TaskCreate calls at all**  -  they're not part of the mode's phase set. Phase 4 is in every mode's set as of v14.0.0, so it is always registered. The "[SKIPPED]" pattern above only applies if a phase that IS in the set is conditionally skipped at runtime. The authoritative per-mode set is the `for p in ...` init block in each mode's own entry doc, generated by `gen-mode-dispatch.mjs`; this table mirrors those blocks.
 
 **Enforcement**: `smoke-tasklist-ordering.sh` scans every mode entry point doc (`commands/multi-agent.md`, `commands/multi-agent/{autopilot,local,local-autopilot,dev,dev-autopilot,dev-local,dev-local-autopilot}.md` + Copilot mirrors) for the explicit "in phase-number order" rule. Inventory drift fails the smoke.
 
@@ -309,7 +310,7 @@ The `tasklist_id` meta from the previous session is replaced with the new IDs du
 
 ## Continuation runs (finish / manual-test)
 
-A pre-existing `tracker-state.json` for the task is never re-initialized. Rules for any command that continues an earlier run (`/multi-agent:finish`, `/multi-agent:manual-test`, resume):
+A pre-existing `tracker-state.json` for the task is never re-initialized. Rules for any command that continues an earlier run (`/multi-agent:ship`, `/multi-agent:manual-test`, resume):
 
 1. `init` runs ONLY when no state file exists for the task. Otherwise the existing file is kept - phase history (elapsed, tokens, model, meta) survives.
 2. The continuing command re-declares its phase set with `add` - `add` is idempotent, so existing phases keep their name, status, and token history; only genuinely new phases are appended. The card renders phases sorted by numeric id, so mixed sets stay in order.
@@ -332,5 +333,5 @@ A pre-existing `tracker-state.json` for the task is never re-initialized. Rules
 
 - `$HOME/.claude/multi-agent-refs/phases.md` section "Visual Phase Tracker" (canonical spec)
 - `$HOME/.claude/multi-agent-refs/progress-contract.md` (one-line stdout format, runs alongside the tracker)
-- `pipeline/scripts/phase-tracker.sh` (state file CRUD)
-- `pipeline/scripts/run-aggregator.mjs` (post-hoc cost summary)
+- `$HOME/.claude/scripts/phase-tracker.sh` (state file CRUD)
+- `$HOME/.claude/scripts/run-aggregator.mjs` (post-hoc cost summary)

package/pipeline/preferences-template.json

@@ -1,5 +1,5 @@
 {
-  "schemaVersion": "2.1.0",
+  "schemaVersion": "2.5.0",
   "global": {
     "identities": [],
     "keychainMapping": {
@@ -73,6 +73,12 @@
       "enabled": true,
       "mcpServerName": "dev-toolkit",
       "registry": "github-packages"
+    },
+    "skillConformance": {
+      "blockOnCoverageGap": false
+    },
+    "ship": {
+      "autoFix": false
     }
   },
   "projects": {},

package/pipeline/rules/figma-pipeline.md

@@ -25,7 +25,7 @@ The MCP token itself resolves through `prefs.global.keychainMapping.figma_mcp` (
 
 #### Tier 2 - Figma Personal Access Token via REST API (fallback)
 
-Token retrieval goes through `~/.claude/lib/credential-store.sh get <logical-key>` where `<logical-key>` is read from `prefs.global.keychainMapping.figma_pat` (or whichever per-user logical name the mapping resolves to). The literal Keychain service name is NEVER embedded in any synced file under `~/.claude/commands/` or `~/.copilot/skills/`; see the Synced Command Hygiene rule.
+Token retrieval goes through `~/.claude/lib/credential-store.sh get <logical-key>` where `<logical-key>` is read from `prefs.global.keychainMapping.figma` (or whichever per-user logical name the mapping resolves to). The literal Keychain service name is NEVER embedded in any synced file under `~/.claude/commands/` or `~/.copilot/skills/`; see the Synced Command Hygiene rule.
 
 Endpoints:
 - Design context (frame metadata + structure):
@@ -33,7 +33,7 @@ Endpoints:
 - Screenshot render:
   `GET https://api.figma.com/v1/images/{fileKey}?ids={nodeId}&format=png&scale=2` with the same header. The response is a signed URL valid for 30 days; download it locally before the URL expires.
 
-If the REST call returns 401 / 403 (the PAT is expired or revoked), do NOT silently fall through to Tier 3  -  run the Expired-token decision (`refs/keychain.md` Rule 1) for `figma_pat`: **Regenerate** / **Use a different token** / **Skip and continue**. Only on the explicit "Skip and continue" choice (or when no `figma_pat` is mapped) does the chain move to Tier 3.
+If the REST call returns 401 / 403 (the PAT is expired or revoked), do NOT silently fall through to Tier 3  -  run the Expired-token decision (`refs/keychain.md` Rule 1) for `figma`: **Regenerate** / **Use a different token** / **Skip and continue**. Only on the explicit "Skip and continue" choice (or when no `figma` is mapped) does the chain move to Tier 3.
 
 Tier 2 does NOT return a Code Connect snippet (the REST API has no equivalent). When operating on Tier 2, the canonical-component decision falls back to the repo's `*.figma.swift` / `*.figma.kt` mappings (search by `fileKey` + `nodeId`); if none match, record an Open Question for the design team and pick the closest existing primitive WITH user confirmation.