@mmerterden/multi-agent-pipeline 17.6.0 → 19.0.0

package/docs/adr/0005-lazy-phase-docs.md

@@ -1,6 +1,6 @@
 # 5. Lazy-loaded phase docs with per-phase token budget
 
-**Status:** Accepted · 2025
+**Status:** Accepted · 2025 · amended by [ADR-0014](./0014-six-phase-consolidation.md)
 
 ## Context
 
@@ -36,6 +36,16 @@ Current budgets (v3.5.0):
 
 Total phase doc budget: 14,300 tokens across 8 phases, loaded incrementally.
 
+> **Amended by [ADR-0014](./0014-six-phase-consolidation.md) (v19.0.0).** There
+> are six phase docs now, not eight, and the numbers above are the v3.5.0 ones
+> rather than the current ceilings. They are left as written because an ADR
+> records what was decided, not what is true today. The mechanism this ADR
+> establishes is unchanged and still load-bearing: one document per phase,
+> loaded on entry, with a committed ceiling `smoke-token-budget.sh` enforces.
+> The live ceilings are in `pipeline/schemas/token-budget.json` and the phase
+> list itself in `pipeline/schemas/phases.json`, which is the duplication
+> ADR-0014 removed - restating either here would recreate it.
+
 ## Consequences
 
 Positive:

package/docs/adr/0008-installer-modularization-and-secret-leak-defense.md

@@ -1,6 +1,7 @@
 # 8. Installer modularization + secret-leak defense
 
 **Status:** Accepted · 2026-04-27 (v8.0.0)
+> **Phase numbers below are the eight-phase ones.** [ADR-0014](./0014-six-phase-consolidation.md) renumbered the contract in v19.0.0 (the producer/consumer phase docs it names were renumbered). The decision this ADR records is unchanged; only the labels moved, and they are left as written because an ADR records what was decided.
 
 > **Amended v10.7.0:** the `_adapters.mjs` module and its third-party adapter dispatch were removed when the pipeline narrowed to Claude Code + Copilot CLI (see ADR 0007). `install/` now ships **8** modules, not 9; the module list below records the v8.0.0 decision as it shipped at the time.
 

package/docs/adr/0010-own-code-graph.md

@@ -1,6 +1,7 @@
 # 10. Our own code graph, not a forked one
 
 **Status:** Accepted · 2026-08-28
+> **Phase numbers below are the eight-phase ones.** [ADR-0014](./0014-six-phase-consolidation.md) renumbered the contract in v19.0.0 (`phase-1-analysis.md` is now `phase-1-plan.md` and Phase 7 Report is now Phase 5). The decision this ADR records is unchanged; only the labels moved, and they are left as written because an ADR records what was decided.
 
 ## Context
 

package/docs/adr/0011-dormant-ci.md

@@ -1,6 +1,6 @@
 # 11. CI stays in the repository but dormant; the pre-push gate is primary
 
-**Status:** Accepted · 2026-08-31 · amended 2026-09-13
+**Status:** Accepted · 2026-08-31 · amended 2026-09-13 · amended 2026-09-17
 
 > **Amendment, 2026-09-13 (ADR-0012, macOS only).** Linux and Windows support
 > was removed. `package.json` now declares `os: ["darwin"]`, which npm enforces
@@ -91,6 +91,30 @@ gate already covers everything except the three items listed above.
 only macOS, disappears when the laptop is closed, and a self-hosted runner on a
 public repository executes code from any fork's pull request.
 
+> **Amendment, 2026-09-17.** Two of those three reasons have moved.
+>
+> "Covers only macOS" stopped being a cost when ADR-0012 removed the other
+> platforms: macOS is now the only target, so a macOS-only runner covers all of
+> it.
+>
+> The fork argument is weaker than it was but is NOT gone, and the difference is
+> worth stating precisely because the plan that revisited this got it wrong.
+> The repository is private, which is the important half. It is not
+> fork-free: measured on 2026-09-17 it has **one fork**, owned by another
+> account. GitHub requires approval before a fork's pull request runs a
+> workflow, so the exposure is gated - but the gate is a setting and an
+> approval given by reflex puts that code on the runner, with the runner's
+> keychain.
+>
+> "Disappears when the laptop is closed" is the reason this is still not the
+> default. It becomes a real option only on a machine that stays awake, which
+> is what `docs/server-readiness.md` describes and why that page is a
+> prerequisite rather than a companion.
+>
+> The decision is unchanged: CI stays dormant and the pre-push gate stays
+> primary. What changed is that a self-hosted runner is now a supported option
+> for someone who has read that page, rather than a rejected one.
+
 **Delete the workflows.** Honest but lossy. The files encode which steps matter
 and in what order, and the possible issue-triggered direction would have to
 rebuild them from nothing.

package/docs/adr/0014-six-phase-consolidation.md

@@ -0,0 +1,134 @@
+# 14. Six phases, because two of the eight were doing the same work twice
+
+**Status:** Accepted · 2026-09-18 · amends [ADR-0005](./0005-lazy-phase-docs.md)
+
+Three further ADRs carry the old numbers in their bodies and now carry a pointer
+back here instead of being rewritten: [ADR-0002](./0002-instruction-driven-flag.md)
+(Phase 6 commit truth table), [ADR-0008](./0008-installer-modularization-and-secret-leak-defense.md)
+(producer/consumer phase docs) and [ADR-0010](./0010-own-code-graph.md)
+(`phase-1-analysis.md`, Phase 7 refresh). [ADR-0007](./0007-multi-tool-adapter-framework.md)
+is Superseded and needs none.
+
+## Context
+
+The pipeline shipped an eight-phase contract (0 Init, 1 Analysis, 2 Planning,
+3 Dev, 4 Review, 5 Test, 6 Commit, 7 Report) from v1 until v18. Two seams in
+it were doing redundant work, and both were visible in the repo rather than
+inferred.
+
+**The build ran twice.** Phase 2 Dev built the project and tee'd the log
+(`phase-2-dev.md:177-182`, up to three attempts). Phase 3 Review opened by
+building it again (`phase-3-review.md:19-20`). Both logs fed the same evidence
+gate. Nothing consumed the difference between them - the second build existed
+because Review was written to be runnable standalone, not because the first
+build was untrusted.
+
+**Analysis and Planning were already one unit.** The depth picker never chose
+between them: `agent-state.schema.json` described `onlyDevelop` as "Short
+pipeline - phases 1 and 2 are skipped", and `features/skill-conformance.md`
+opened an entire section with "Dev-mode substitutes (Phases 1 and 2 never
+ran)". Two phase numbers, one decision, in every mode that had a choice.
+
+A third fact shaped the mapping rather than motivating it: the phase count
+appeared in 91 places across 40 files and **no gate held any of them**. The
+command count (56) was guarded in seven files, the jq count was guarded, the
+persona count was guarded. The phase count was not. A renumbering could have
+left the whole tree stale and the suite would have stayed green.
+
+## Decision
+
+Six phases. The mapping:
+
+| Was | Is | Name | What changed |
+|---|---|---|---|
+| 0 Init | **0** | Init | Nothing |
+| 1 Analysis + 2 Planning | **1** | Plan | One doc, one exit gate |
+| 3 Dev + 4 Review Stage 1 | **2** | Dev | Verify became Dev's exit gate; the build runs once |
+| 4 Review (Stage 2-3) + 5 Test | **3** | Review | The user test moved inside Review |
+| 6 Commit | **4** | Commit | Nothing |
+| 7 Report | **5** | Report | Nothing |
+
+Analysis folds into Plan rather than into Init because of the token budget,
+not preference. Init is 733 lines with a 13,400-token ceiling, already the
+largest doc; adding Analysis would have put it near 18,000 and
+`smoke-token-budget.sh` would have rejected it. Folded into Planning instead,
+the merged doc lands under Init's existing ceiling.
+
+Three supporting decisions came with it:
+
+**`pipeline/schemas/phases.json` is the contract.** The phase list previously
+existed as eight independent copies, none derived from another. It is now one
+file that `gen-mode-dispatch.mjs`, `runs-index.mjs`, `log-metric.sh` and the
+token budget read, and that `smoke-phase-contract.sh` holds every remaining
+copy to. Comparison thresholds that used to be literals (`phase >= 6` for
+"waiting on you", the Short-run boundary) are named fields in it.
+
+**`smoke-no-mcp-in-dev-phases.sh` keeps its `phase >= 2` threshold, and the
+gate now asserts that it is unchanged.** Figma MCP was reachable only in
+Analysis (1); Analysis is now inside Plan (1). The permitted set `{0, 1}` is
+identical either way. The threshold surviving a renumbering is a result of the
+mapping, not an oversight, and an edit that "corrects" it would widen MCP
+access - so the assertion is written as a gate rather than a comment.
+
+**`metrics.jsonl` gets a generation marker, not a rewrite.** The file is
+append-only and `phase: 3` means Dev in a pre-v19 row and Review in a post-v19
+one. Every line written from v19.0.0 on carries `phaseSchema: 2`; a line
+without the field is generation 1. `pipeline/lib/phase-schema.mjs` resolves
+both, and the two aggregators that compared phase numbers to literals
+(`token-budget-report.mjs`, `run-aggregator.mjs`) go through it. The file held
+four rows at the time of the change, so migrating history was not worth doing;
+adding the field was, because the next renumbering will not find four rows.
+
+## Consequences
+
+Positive:
+
+- One build per run instead of two. Phase 3 Review inherits `.build.log` and
+  `.test.log` from Phase 2 and runs the evidence gate against them.
+- The phase count is guarded. `smoke-phase-contract.sh` derives it from
+  `phases.json` and checks the generator's output, the token budget, the state
+  schema bounds, every shipped surface that states a count, the progress
+  fractions in sample output, and the named thresholds. It fails on a
+  deliberately wrong contract - verified both ways.
+- `state-2.1.0-to-2.2.0.mjs` is the first migration that rewrites phase
+  numbers, and it repairs four defects the live corpus already carried. The
+  62-file corpus went from 52 valid to 62.
+
+Negative:
+
+- Two source phases can collide onto one target key in `state.phases{}`. The
+  merge rule (furthest-along status, max `retryCount`, union of `files[]`,
+  earliest start, latest finish) is a judgement call, and `retryCount` takes
+  the max specifically because the schema caps it at 3 and a sum would emit an
+  invalid state.
+- Historical `agent-log.md` files keep their old phase names. They are dated
+  human documents and are correct as written; only new runs use new names.
+- Phase 3 Review is now the largest doc in the set. Stage 1 left it and the
+  user test entered it, and the net is growth. Its ceiling was re-measured
+  after the merge rather than summed from the old two, because
+  `smoke-token-budget.sh` rejects a ceiling more than 25% above the
+  measurement - summing would have shipped a stale ceiling by construction.
+
+## Alternatives Considered
+
+**Fold Analysis into Init.** Rejected on the token budget, as above. The
+semantic argument pointed the same way: `onlyDevelop` already treated Analysis
+and Planning as one unit, and never grouped Analysis with Init.
+
+**Keep six phases, hide the empty tiles in the tracker.** Rejected: this is
+cosmetic. The double build is a contract problem, not a display problem, and
+hiding tiles would leave it running while making it harder to see.
+
+**Fold Report into Commit.** Rejected. `ROADMAP.md` records the Phase 5
+approval requirement as a permanent design line: Jira, Confluence, wiki and PR
+bodies are externally visible, and content sent in the wrong tone leaks to the
+team. Merging Report into Commit would put that approval gate inside a phase
+that autopilot runs without interaction.
+
+**Drop the user test entirely.** Rejected. `phase-3-review.md` produces
+structured evidence that Phase 4 consumes; it is a real output, not a pause.
+It moved inside Review and kept its behaviour, including its waiting state.
+
+**Renumber without a contract file.** Rejected - this is what created the
+problem being fixed. Eight hand edits to eight independent copies is the
+mechanism by which the ninth copy gets missed.

package/docs/adr/README.md

@@ -14,7 +14,7 @@ Format: lightly adapted from [Michael Nygard's ADR template](https://cognitect.c
 | [0002](./0002-instruction-driven-flag.md) | instructionDriven flag as explicit pipeline fork  | Accepted |
 | [0003](./0003-unified-shared-skills.md) | Unified `skills/shared/` for Claude Code + Copilot | Accepted (amended v5.3.3) |
 | [0004](./0004-zero-dependency-philosophy.md) | Keep the package zero-runtime-deps                | Accepted |
-| [0005](./0005-lazy-phase-docs.md)      | Lazy-loaded phase docs with per-phase token budget | Accepted |
+| [0005](./0005-lazy-phase-docs.md)      | Lazy-loaded phase docs with per-phase token budget | Accepted (amended by 0014: eight phase docs became six) |
 | [0006](./0006-skills-core-external-split.md) | `shared/core/` vs `shared/external/` source org    | Accepted |
 | [0007](./0007-multi-tool-adapter-framework.md) | Multi-tool adapter framework + token-preserving uninstall | Superseded by v10.7.0 (adapters removed; Claude Code + Copilot CLI only) |
 | [0008](./0008-installer-modularization-and-secret-leak-defense.md) | Installer modularization + secret-leak defense | Accepted (amended v10.7.0: adapter module removed) |
@@ -23,6 +23,7 @@ Format: lightly adapted from [Michael Nygard's ADR template](https://cognitect.c
 | [0011](./0011-dormant-ci.md) | CI dormant in-repo; pre-push gate is primary | Accepted |
 | [0012](./0012-macos-only.md) | macOS only; Linux and Windows support removed | Accepted |
 | [0013](./0013-lsp-code-intelligence.md) | A language server for the answers regex cannot give | Accepted |
+| [0014](./0014-six-phase-consolidation.md) | Six phases, because two of the eight were doing the same work twice | Accepted |
 
 ## Writing a New ADR
 

package/docs/architecture.md

@@ -1,53 +1,49 @@
 # Architecture
 
-## 8-Phase Pipeline Flow (0-7)
+## 6-Phase Pipeline Flow (0-5)
 
 ```mermaid
 graph TD
     INPUT["🎯 Input<br/>(Issue # / Jira URL / free text)"]
     P0["Phase 0: Init<br/>Project detect, worktree, branch, identity"]
-    P1["Phase 1: Analysis<br/>Codebase scan (parallel Explore agents)"]
-    P2["Phase 2: Planning<br/>Task breakdown, architecture review"]
-    P3["Phase 3: Dev<br/>TDD: RED → GREEN → REFACTOR"]
-    P4["Phase 4: Review<br/>Parallel + Fable triage<br/>(3 reviewers per host: Claude Code Fable + Opus + Sonnet · Copilot GPT-5.4 + Opus + Sonnet)"]
-    P5["Phase 5: Test<br/>Optional manual testing"]
-    P6["Phase 6: Commit<br/>Git commit, PR creation"]
-    P7["Phase 7: Report<br/>Jira · Wiki+Figma · Confluence · Log · Knowledge"]
+    P1["Phase 1: Plan<br/>Codebase scan (parallel Explore agents),<br/>task breakdown, architecture review, Plan Approval Gate"]
+    P2["Phase 2: Dev<br/>TDD: RED → GREEN → REFACTOR<br/>Verify exit gate: build · lint · tests · secrets"]
+    P3["Phase 3: Review<br/>Parallel + Fable triage, then the optional user test<br/>(3 reviewers per host: Claude Code Fable + Opus + Sonnet · Copilot GPT-5.4 + Opus + Sonnet)"]
+    P4["Phase 4: Commit<br/>Git commit, PR creation"]
+    P5["Phase 5: Report<br/>Jira · Wiki+Figma · Confluence · Log · Knowledge"]
 
     INPUT --> P0
     P0 --> P1
     P1 --> P2
-    P2 --> P3
-    P3 --> P4
-    P4 -->|approved| P5
-    P4 -->|fix needed| P3
-    P5 --> P6
-    P6 --> P7
+    P2 -->|build + test logs| P3
+    P3 -->|approved| P4
+    P3 -->|fix needed| P2
+    P4 --> P5
 
     style INPUT fill:#f9f,stroke:#333
-    style P3 fill:#ffd,stroke:#333
-    style P4 fill:#dff,stroke:#333
-    style P7 fill:#a855f7,stroke:#333,color:#fff
+    style P2 fill:#ffd,stroke:#333
+    style P3 fill:#dff,stroke:#333
+    style P5 fill:#a855f7,stroke:#333,color:#fff
 ```
 
 ## Operating Modes
 
 ```mermaid
 graph LR
-    subgraph Normal ["Normal (Full 8-phase)"]
-        N0[Init] --> N1[Analysis] --> N2[Planning] --> N3[Dev] --> N4[Review] --> N5[Test] --> N6[Commit] --> N7[Report]
+    subgraph Normal ["Normal (Full 6-phase)"]
+        N0[Init] --> N1[Plan] --> N2[Dev] --> N3[Review] --> N4[Commit] --> N5[Report]
     end
 
     subgraph Dev ["Short depth (picker, Opus)"]
-        D0[Init] --> D3[Dev<br/>Opus] --> D4[Review] --> D5[Test] --> D6[Commit] --> D7[Report]
+        D0[Init] --> D2[Dev<br/>Opus] --> D3[Review] --> D4[Commit] --> D5[Report]
     end
 
     subgraph Autopilot ["Autopilot (skip confirmations)"]
-        A0[Init] --> A1[Analysis] --> A2[Planning] --> A3[Dev] --> A4[Review] --> A6[Commit] --> A7[Report]
+        A0[Init] --> A1[Plan] --> A2[Dev] --> A3[Review] --> A4[Commit] --> A5[Report]
     end
 ```
 
-## Review Architecture (Phase 4)
+## Review Architecture (Phase 3)
 
 ```mermaid
 graph TD
@@ -61,24 +57,24 @@ graph TD
     GPT --> TRIAGE
     SON --> TRIAGE
 
-    TRIAGE -->|PASS| P5["Phase 5: Test"]
-    TRIAGE -->|FIX_REQUIRED| P3["Phase 3: Dev (retry ≤3x)"]
+    TRIAGE -->|PASS| P4["Phase 4: Commit"]
+    TRIAGE -->|FIX_REQUIRED| P2["Phase 2: Dev (retry ≤3x)"]
 
     style TRIAGE fill:#ffd,stroke:#333
     style P3 fill:#fdd,stroke:#333
     style P5 fill:#dfd,stroke:#333
 ```
 
-## Figma SubPhase Integration (Phase 3)
+## Figma SubPhase Integration (Phase 2)
 
-When a task is classified `component`, Phase 3 dispatches to the marketplace component plugin (`ai-<platform>-toolkit`) via the Skill tool. Component skills are not bundled in this repo; the subphases below describe the flow the plugin skill runs internally:
+When a task is classified `component`, Phase 2 dispatches to the marketplace component plugin (`ai-<platform>-toolkit`) via the Skill tool. Component skills are not bundled in this repo; the subphases below describe the flow the plugin skill runs internally:
 
 ```mermaid
 graph TD
-    P3["Phase 3: Dev"]
+    P2["Phase 2: Dev"]
 
-    P3 -->|figmaConfigPath set| FIGMA
-    P3 -->|default| TDD["Standard TDD<br/>RED → GREEN → REFACTOR"]
+    P2 -->|figmaConfigPath set| FIGMA
+    P2 -->|default| TDD["Standard TDD<br/>RED → GREEN → REFACTOR"]
 
     subgraph FIGMA ["Figma Pipeline (17 SubPhases)"]
         direction TB
@@ -117,7 +113,7 @@ graph TB
     end
 
     subgraph "Pipeline Specs"
-        CMD[commands/<br/>56 command files]
+        CMD[commands/<br/>60 command files]
         AGT[agents/<br/>8 agent personas]
         RUL[rules/<br/>12 domain rules]
         PHS[multi-agent-refs/phases/<br/>phase specs + contracts]
@@ -147,15 +143,18 @@ User Input → Phase 0 (Init)
                 ↓
             agent-state.json (created)
                 ↓
-            Phase 1-2 (Analysis + Planning)
+            Phase 1 (Plan: analysis + breakdown + approval gate)
                 ↓
-            Phase 3 (Dev) ←──── retry loop (max 3x)
-                ↓                    ↑
-            Phase 4 (Review) ────────┘ (if fix needed)
+            Phase 2 (Dev) ←──────── retry loop (max 3x)
+                ↓                        ↑
+            Verify exit gate             │
+            build · lint · tests · secrets
+                ↓ .build.log + .test.log │
+            Phase 3 (Review + user test) ┘ (if fix needed)
                 ↓
-            Phase 5-6 (Test + Commit)
+            Phase 4 (Commit → push → PR)
                 ↓
-            Phase 7 REPORT (Jira → Wiki+Figma → Confluence → Log → Knowledge)
+            Phase 5 REPORT (Jira → Wiki+Figma → Confluence → Log → Knowledge)
                 ↓
             agent-log.md + agent-state.json (final)
 ```
@@ -170,7 +169,7 @@ revisions of this diagram - Codex CLI and the two independently-shipped repos
 graph TD
     CC["Claude Code<br/>(source of truth)"]
     COP["Copilot CLI<br/>(instructions + 56 skills)"]
-    COD["Codex CLI<br/>(1 router skill + 56 refs)"]
+    COD["Codex CLI<br/>(1 router skill + 60 refs)"]
     REPO["Pipeline Repo<br/>(npm package)"]
     WEB["Website"]
     PLUGREPO["multi-agent-plugins<br/>(5 stack plugins, own repo)"]
@@ -190,5 +189,5 @@ graph TD
 ```
 
 Full detail on how these three repos compose at install time and at run time -
-including the Phase 3 → plugin dispatch contract and the Phase 5 → multi-agent-toolkit MCP
+including the Phase 2 → plugin dispatch contract and the Phase 3 → multi-agent-toolkit MCP
 contract - lives in [`docs/ecosystem.md`](./ecosystem.md).

package/docs/best-practices.md

@@ -55,7 +55,7 @@ Applied in Phase 3:
 | Phase 1 → 2 | Analysis complete, no unanswered questions | Planning |
 | Phase 3 → 4 | Build passes, lint clean, tests green      | Review   |
 | Phase 4 → 6 | All blocking findings resolved             | Commit   |
-| Phase 6 → 7 | Push successful, PR created                | Report   |
+| Phase 4 → 7 | Push successful, PR created                | Report   |
 
 ## 6. 3-Iteration Hard Kill (original)
 

package/docs/ecosystem.md

@@ -5,20 +5,20 @@ separately, wired together at install time and at run time:
 
 | Repo | What it owns | Ships as |
 |---|---|---|
-| **`multi-agent-pipeline`** (this repo) | Orchestration: the 8-phase flow, the 56 slash commands, quality gates, review/triage, cross-CLI parity | npm package (`@mmerterden/multi-agent-pipeline`), installs itself onto Claude Code / Copilot CLI / Codex CLI |
+| **`multi-agent-pipeline`** (this repo) | Orchestration: the 6-phase flow, the 60 slash commands, quality gates, review/triage, cross-CLI parity | npm package (`@mmerterden/multi-agent-pipeline`), installs itself onto Claude Code / Copilot CLI / Codex CLI |
 | **`multi-agent-plugins`** | Stack knowledge: per-platform component/lifecycle skills (iOS, Android, Frontend, Backend) + shared knowledge | Claude Code marketplace, 5 independently-versioned plugins |
-| **`multi-agent-toolkit-mcp`** | The pipeline's hands on devices and browsers: 80 MCP tools across 6 categories (simulator/emulator control, accessibility audit, store compliance, web automation, Figma-vs-mock design audit, an agent-DSL batch runner) | npm package, registered as a standard stdio MCP server on every host |
+| **`multi-agent-toolkit-mcp`** | The pipeline's hands on devices and browsers: 99 MCP tools across 10 categories (simulator/emulator control, memory, crash diagnostics, accessibility audit, store compliance, web automation, Figma-vs-mock design audit, code intelligence, wallet passes, an agent-DSL batch runner) | npm package, registered as a standard stdio MCP server on every host |
 
 None of the three depends on the others at the code level. They compose through two
-narrow contracts: the **Skill tool** (pipeline → plugin, at Phase 3) and the **MCP
-protocol** (pipeline skills → multi-agent-toolkit, at Phase 5 / design-check / store-ready).
+narrow contracts: the **Skill tool** (pipeline → plugin, at Phase 2) and the **MCP
+protocol** (pipeline skills → multi-agent-toolkit, at Phase 3 / design-check / store-ready).
 Either can be swapped or removed without touching the other two's source.
 
 ```mermaid
 graph LR
     subgraph PIPE ["multi-agent-pipeline (orchestrator)"]
         direction TB
-        PHASES["8 phases · 56 commands"]
+        PHASES["6 phases · 60 commands"]
         GATES["deterministic gates + review triage"]
     end
 
@@ -34,17 +34,21 @@ graph LR
 
     subgraph DTK ["multi-agent-toolkit-mcp (device/browser hands)"]
         direction TB
-        DEV["Device Control (58)"]
-        A11Y["Accessibility Audit (2)"]
+        DEV["Device Control (59)"]
+        MEM["Memory (2)"]
+        CRASH["Crash Diagnostics (2)"]
+        A11Y["Accessibility Audit (3)"]
         STORE["Store Compliance (5)"]
         WEB["Web Automation (8)"]
         DESIGN["Design Audit (6)"]
-        AGENTDSL["Agent DSL (1)"]
+        CODE["Code Intelligence (8)"]
+        PASS["Wallet Passes (4)"]
+        AGENTDSL["Agent DSL (2)"]
     end
 
-    PHASES -->|"Phase 3: Skill tool<br/>taskType===component"| PLUG
-    PHASES -->|"Phase 5 / design-check /<br/>store-ready: MCP tool calls"| DTK
-    GATES -.->|"Phase 4 Security Auditor"| STORE
+    PHASES -->|"Phase 2: Skill tool<br/>taskType===component"| PLUG
+    PHASES -->|"Phase 3 / design-check /<br/>store-ready: MCP tool calls"| DTK
+    GATES -.->|"Phase 3 Security Auditor"| STORE
 
     style PIPE fill:#ffd,stroke:#333
     style PLUG fill:#dfd,stroke:#333
@@ -64,8 +68,8 @@ only those:
 graph TD
     CC["Claude Code<br/>~/.claude/commands/multi-agent/<br/>(source of truth)"]
 
-    CC -->|"Step 2: copy + reformat<br/>56 sub-command skills"| COP["Copilot CLI<br/>~/.copilot/skills/"]
-    CC -->|"Step 2b: transform<br/>(install.js --codex)"| COD["Codex CLI<br/>1 router skill + 56 refs<br/>+ 8 agent TOML"]
+    CC -->|"Step 2: copy + reformat<br/>60 sub-command skills"| COP["Copilot CLI<br/>~/.copilot/skills/"]
+    CC -->|"Step 2b: transform<br/>(install.js --codex)"| COD["Codex CLI<br/>1 router skill + 60 refs<br/>+ 8 agent TOML"]
     CC -->|"Step 3: genericize<br/>(strip personal data)"| REPO["multi-agent-pipeline repo<br/>pipeline/"]
     CC -->|"Step 4: version + feature sync"| WEB["Website<br/>projects.ts / i18n.tsx"]
 
@@ -131,7 +135,7 @@ graph TD
 
 A skill counted in more than one platform plugin (a cross-stack knowledge skill
 plus, say, an iOS-specific one) is why the plugins' skill counts sum to more than
-the 151-skill source: `ai-common` skills are vendored into every stack plugin's
+the 153-skill source: `ai-common` skills are vendored into every stack plugin's
 `knowledge/`, not deduplicated across them. Versioning is per-plugin and
 patch-only from this generator - a repo enabling only `ai-ios-toolkit`
 never pulls an Android-only change.
@@ -153,7 +157,7 @@ measurements behind this table):
 
 | | Claude Code | Copilot CLI | Codex CLI |
 |---|---|---|---|
-| **Pipeline commands** | 56 slash-command skills, native | 56 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 56 command specs as reference files - Codex silently truncates its skills block past a few dozen entries, so sub-commands are not peer skills here |
+| **Pipeline commands** | 60 slash-command skills, native | 56 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 60 command specs as reference files - Codex silently truncates its skills block past a few dozen entries, so sub-commands are not peer skills here |
 | **Stack plugins** | Marketplace plugin, loaded natively, resolved by `.claude/settings.json` enabled-list | Enabled plugin's authored skills copied flat into `~/.copilot/skills/`; `knowledge/` **not** re-copied (already delivered via `shared/external`) | Copied as reference files under `~/.codex/multi-agent-refs/skills/`, plugin-prefixed on name clash (e.g. `architecture` → `ai-ios-toolkit-architecture`) |
 | **Component dispatch (Phase 3)** | Marketplace plugin's `create-component`/`create-screen` skill via the Skill tool | No plugin loader - the enabled stack plugin's authored skills (incl. `create-component`) are copied flat into `~/.copilot/skills/` at install time (the old frozen `figma-*` copies are pruned, they were never a fallback) | Not part of the enforced parity axis; classification + state-shape must match, skill *inventory* does not |
 | **multi-agent-toolkit-mcp** | `claude mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` | `copilot mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` | `codex mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` (skipped with a warning if `codex` isn't on `PATH`) |
@@ -171,32 +175,31 @@ other:
 
 ```mermaid
 graph TD
-    START["Task running: Phase 3 (Dev)"]
+    START["Task running: Phase 2 (Dev)"]
     START -->|"taskType !== component"| TDD["Standard TDD loop<br/>(pipeline's own code)"]
     START -->|"taskType === component<br/>+ figmaUrl present"| VALIDATE["ai-ios-toolkit:figma-validate<br/>(registry, Code Connect, token compliance)"]
     VALIDATE -->|pass| DISPATCH["Skill tool →<br/>create-component / create-screen<br/>/ evolve-component (dual-name fallback)"]
-    VALIDATE -->|fail| HALT1["halt Phase 3, surface why"]
-    DISPATCH --> REPORT1["plugin returns build/test status →<br/>dispatch layer writes state.phases['3'].subphases[]"]
+    VALIDATE -->|fail| HALT1["halt Phase 2, surface why"]
+    DISPATCH --> REPORT1["plugin returns build/test status →<br/>dispatch layer writes state.phases['2'].subphases[]"]
 
-    REPORT1 --> P4["Phase 4: Review"]
-    P4 --> P5["Phase 5: Test"]
+    REPORT1 --> P3["Phase 3: Review + user test"]
 
-    P5 -->|"UI bug hunt / manual-test /<br/>design-check / store-ready"| MCP["MCP tool call over stdio<br/>e.g. ios_xcodebuild, design_visual_compare,<br/>ios_app_store_audit"]
+    P3 -->|"UI bug hunt / manual-test /<br/>design-check / store-ready"| MCP["MCP tool call over stdio<br/>e.g. ios_xcodebuild, design_visual_compare,<br/>ios_app_store_audit"]
     MCP --> DTKPROC["multi-agent-toolkit-mcp process<br/>(npx @mmerterden/multi-agent-toolkit-mcp)"]
-    DTKPROC -->|"result: screenshot / xcresult ID /<br/>18-rule audit verdict"| P5
+    DTKPROC -->|"result: screenshot / xcresult ID /<br/>18-rule audit verdict"| P3
 
     style DISPATCH fill:#dfd,stroke:#333
     style MCP fill:#dff,stroke:#333
     style HALT1 fill:#fdd,stroke:#333
 ```
 
-**Phase 3 → plugin** is a one-shot delegation: the plugin skill does its own
+**Phase 2 → plugin** is a one-shot delegation: the plugin skill does its own
 lifecycle (test → code → build → wiki) and reports back a coarse
 `component-build` result; the pipeline does not re-implement any of that logic, and
 a plugin failure counts against the pipeline's own retry cap (`retryCount === 3` →
 hard stop, per `component-dispatch.md`).
 
-**Phase 5 (and design-check / store-ready) → multi-agent-toolkit** is a long-lived MCP
+**Phase 3 (and design-check / store-ready) → multi-agent-toolkit** is a long-lived MCP
 session, not a one-shot call: the same stdio server process answers many tool
 calls across a phase (boot simulator once, then screenshot/tap/screenshot/tap...).
 Several pipeline skills pin a **minimum toolkit version** for a specific tool -
@@ -206,7 +209,13 @@ e.g. `apple-archive-compliance` requires `ios_app_store_audit` from
 that drops or renames a tool a pipeline skill depends on is a **major** bump, by
 that step's own contract).
 
-### multi-agent-toolkit-mcp's tools, by category (87 at the toolkit README's last count; the pipeline says "80+" elsewhere so the number does not go stale with every toolkit release)
+### multi-agent-toolkit-mcp's tools, by category
+
+99 tools in 10 categories, counted from the server's own `tools/list` response at
+toolkit 3.12.0 rather than from a README. The table stood at 87 across 8
+categories for several releases because Code Intelligence and Wallet Passes
+shipped without anyone adding their rows, and nothing here was checked against
+the server - which is why the count now names its source.
 
 | Category | Tools | Primary pipeline consumers |
 |---|---|---|
@@ -214,10 +223,12 @@ that step's own contract).
 | Memory | 2 (`ios_leaks`, `android_meminfo`) | none yet; available outside the pipeline |
 | Crash Diagnostics | 2 (`ios_list_crashes`, `android_list_crashes`) | `/multi-agent:test` full scenario (end-of-run crash sweep), outside-the-pipeline sessions |
 | Accessibility Audit | 3 (`ios_accessibility_audit`, `android_accessibility_audit`, `ios_accessibility_audit_deep`) | `/multi-agent:test` accessibility scenario, `test-accessibility` |
-| Store Compliance | 5 | `store-ready`, `testflight-validation`, `apple-archive-compliance` skill, Phase 4 Security Auditor |
+| Store Compliance | 5 | `store-ready`, `testflight-validation`, `apple-archive-compliance` skill, Phase 3 Security Auditor |
 | Web Automation | 8 | frontend-stack UI testing (via `test`) |
 | Design Audit | 6 | `design-check` (mock-mode vs Figma conformance) |
 | Autonomous Agent DSL | 2 (`agent_run_steps`, `agent_query_output`) | any skill that needs a scripted multi-step device flow in one round trip |
+| Code Intelligence | 8 (`code_definition`, `code_references`, `code_hover`, `code_diagnostics`, `code_document_symbols`, `code_workspace_symbols`, `code_index_status`, `code_server_reset`) | `/multi-agent:refactor`, Phase 3 reviewers needing a real symbol graph rather than grep |
+| Wallet Passes | 4 (`pass_build`, `pass_validate`, `pass_inspect`, `pass_certificates`) | pass-kit work outside the pipeline; no pipeline phase consumes them |
 
 ---
 

package/docs/engineering.md

@@ -26,7 +26,7 @@ Every loop in the pipeline has a deterministic exit condition and a hard iterati
 
 ## Context management
 
-- **Token-budgeted phase docs**: every phase document has a per-file and total token budget enforced by a smoke gate (`token-budget.json`). Growth is compressed first; budgets are recalibrated only when real contract text lands. This keeps the orchestrator's working context lean across an 8-phase run.
+- **Token-budgeted phase docs**: every phase document has a per-file and total token budget enforced by a smoke gate (`token-budget.json`). Growth is compressed first; budgets are recalibrated only when real contract text lands. This keeps the orchestrator's working context lean across a 6-phase run.
 - **Lazy loading**: only the active phase's document is in context; references load on demand.
 - **Structured handoff blocks**: at every phase boundary the orchestrator appends a Done / Remaining / Decisions / Open findings / Next block to the run log - written from state it already holds, no extra model call. Resume and post-compaction re-entry read the latest handoff plus the state file, never the conversation history.
 - **Proactive compaction**: past ~50% context usage the run compacts itself and re-grounds from durable artifacts instead of waiting for lossy auto-compaction.

package/docs/facts.json

@@ -0,0 +1,45 @@
+{
+  "$comment": "Generated by pipeline/scripts/gen-facts.mjs. Do not hand-edit: the site reads this, and a number edited here instead of at its source is the drift this file removes.",
+  "generatedAt": "2026-09-17",
+  "version": "19.0.0",
+  "phaseSchema": 2,
+  "phases": [
+    {
+      "id": 0,
+      "name": "Init"
+    },
+    {
+      "id": 1,
+      "name": "Plan"
+    },
+    {
+      "id": 2,
+      "name": "Dev"
+    },
+    {
+      "id": 3,
+      "name": "Review"
+    },
+    {
+      "id": 4,
+      "name": "Commit"
+    },
+    {
+      "id": 5,
+      "name": "Report"
+    }
+  ],
+  "phaseCount": 6,
+  "modes": {
+    "full": [0, 1, 2, 3, 4, 5],
+    "autopilot": [0, 1, 2, 3, 4, 5],
+    "local": [0, 1, 2, 3, 4, 5],
+    "local-autopilot": [0, 1, 2, 3, 4, 5],
+    "full-local": [0, 1, 2, 3, 4, 5],
+    "analysis": [0, 1, 3, 4, 5]
+  },
+  "commandCount": 60,
+  "skillCount": 153,
+  "toolCount": 99,
+  "toolkitVersion": "3.12.0"
+}