@mmerterden/multi-agent-pipeline 16.2.1 → 16.2.2

package/CHANGELOG.md

@@ -16,6 +16,13 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [16.2.2] - 2026-08-24
+
+### Fixed
+
+- **The companion MCP server's old name survived in the docs.** 16.1.3 corrected one line in `docs/architecture.md` and called the rename done; `docs/ecosystem.md` still carried it 22 more times, including its section heading, its mermaid nodes and its boundary discussion. Fixing the instance is not fixing the class. `docs/internal/GENERICITY-REVIEW.md` keeps the old name on purpose: it is a dated pre-v10.7.0 snapshot, and editing a record to match today falsifies it.
+- `docs/ecosystem.md` advertised 80 tools against 83 served, and declared a `≥ v2.9.0` minimum where `cross-cli-contract.md` requires v3.0.0.
+
 ## [16.2.1] - 2026-08-24
 
 ### Fixed

package/docs/architecture.md

@@ -174,7 +174,7 @@ graph TD
     REPO["Pipeline Repo<br/>(npm package)"]
     WEB["Website"]
     PLUGREPO["multi-agent-plugins<br/>(5 stack plugins, own repo)"]
-    DTK["dev-toolkit-mcp<br/>(own repo, own release cadence)"]
+    DTK["multi-agent-toolkit-mcp<br/>(own repo, own release cadence)"]
 
     CC -->|copy + reformat| COP
     CC -->|transform via install.js --codex| COD
@@ -190,5 +190,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 → dev-toolkit MCP
+including the Phase 3 → plugin dispatch contract and the Phase 5 → multi-agent-toolkit MCP
 contract - lives in [`docs/ecosystem.md`](./ecosystem.md).

package/docs/ecosystem.md

@@ -7,11 +7,11 @@ separately, wired together at install time and at run time:
 |---|---|---|
 | **`multi-agent-pipeline`** (this repo) | Orchestration: the 8-phase flow, the 51 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 |
-| **`dev-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: 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 |
 
 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 → dev-toolkit, at Phase 5 / design-check / store-ready).
+protocol** (pipeline skills → multi-agent-toolkit, at Phase 5 / design-check / store-ready).
 Either can be swapped or removed without touching the other two's source.
 
 ```mermaid
@@ -32,7 +32,7 @@ graph LR
         ANAP["ai-analyst-toolkit"]
     end
 
-    subgraph DTK ["dev-toolkit-mcp (device/browser hands)"]
+    subgraph DTK ["multi-agent-toolkit-mcp (device/browser hands)"]
         direction TB
         DEV["Device Control (58)"]
         A11Y["Accessibility Audit (2)"]
@@ -71,7 +71,7 @@ graph TD
 
     REPO -->|"Step 3c: build-stack-plugins.mjs<br/>rebuilds knowledge/ from<br/>shared/external"| PLUGREPO["multi-agent-plugins repo<br/>(5 stack plugins)"]
 
-    DTK2["dev-toolkit-mcp repo<br/>(own codebase, own gates,<br/>NOT generated from Claude)"]
+    DTK2["multi-agent-toolkit-mcp repo<br/>(own codebase, own gates,<br/>NOT generated from Claude)"]
     SYNC3D["Step 3d: detect movement →<br/>gate → commit → publish"]
     CC -.->|"sync only SHIPS this,<br/>never authors it"| SYNC3D
     SYNC3D -.-> DTK2
@@ -85,13 +85,13 @@ graph TD
     style DTK2 fill:#dff,stroke:#333,stroke-dasharray: 5 5
 ```
 
-**Why `dev-toolkit-mcp` is drawn differently.** The other four targets are *derived*
-from the Claude Code source - sync writes their content. `dev-toolkit-mcp` is not:
+**Why `multi-agent-toolkit-mcp` is drawn differently.** The other four targets are *derived*
+from the Claude Code source - sync writes their content. `multi-agent-toolkit-mcp` is not:
 it's a separate codebase developed on its own schedule. Sync's Step 3d only
 *detects* whether it moved (dirty tree, unpushed commits, untagged version), runs
 **its own** gate suite, and ships it - commit, tag, `npm publish`. If the pipeline
 needs a tool that toolkit doesn't have yet, that's a two-repo change: add the tool
-in `dev-toolkit-mcp`, ship it, then bump the minimum version pin back in
+in `multi-agent-toolkit-mcp`, ship it, then bump the minimum version pin back in
 `cross-cli-contract.md` (see section 4).
 
 **Also not generated: the plugins' own authored skills.** `build-stack-plugins.mjs`
@@ -156,7 +156,7 @@ measurements behind this table):
 | **Pipeline commands** | 51 slash-command skills, native | 51 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 51 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 |
-| **dev-toolkit-mcp** | `claude mcp add dev-toolkit -- npx -y @mmerterden/dev-toolkit-mcp` | `copilot mcp add dev-toolkit -- npx -y @mmerterden/dev-toolkit-mcp` | `codex mcp add dev-toolkit -- npx -y @mmerterden/dev-toolkit-mcp` (skipped with a warning if `codex` isn't on `PATH`) |
+| **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`) |
 
 `smoke-cross-cli-behavior.sh` and `smoke-codex-install.sh` gate the axes that **do**
 have to match (phase labels, placeholder vocabulary, output schemas, command↔skill
@@ -182,7 +182,7 @@ graph TD
     P4 --> P5["Phase 5: 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"]
-    MCP --> DTKPROC["dev-toolkit-mcp process<br/>(npx @mmerterden/dev-toolkit-mcp)"]
+    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
 
     style DISPATCH fill:#dfd,stroke:#333
@@ -196,17 +196,17 @@ lifecycle (test → code → build → wiki) and reports back a coarse
 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) → dev-toolkit** is a long-lived MCP
+**Phase 5 (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 -
 e.g. `apple-archive-compliance` requires `ios_app_store_audit` from
-`dev-toolkit-mcp ≥ v2.9.0` - enforced in `cross-cli-contract.md` and checked by
-`/multi-agent:sync` Step 3d before any dev-toolkit release ships (a version bump
+`multi-agent-toolkit-mcp ≥ v3.0.0` - enforced in `cross-cli-contract.md` and checked by
+`/multi-agent:sync` Step 3d before any multi-agent-toolkit release ships (a version bump
 that drops or renames a tool a pipeline skill depends on is a **major** bump, by
 that step's own contract).
 
-### dev-toolkit-mcp's 80 tools, by category
+### multi-agent-toolkit-mcp's 83 tools, by category
 
 | Category | Tools | Primary pipeline consumers |
 |---|---|---|
@@ -228,10 +228,10 @@ that step's own contract).
   `create-component`) and dispatch still resolves correctly - the dual-name
   fallback lives in the pipeline, the implementation stays entirely in whichever
   plugin is enabled.
-- **Pipeline ↔ dev-toolkit boundary = MCP protocol, versioned contract.** The
+- **Pipeline ↔ multi-agent-toolkit boundary = MCP protocol, versioned contract.** The
   pipeline never shells out to `xcrun simctl` or `adb` directly; every device/browser
   action is a declared MCP tool call with a minimum-version pin. That's what lets
-  `dev-toolkit-mcp` ship on its own release cadence (its own gates, its own
+  `multi-agent-toolkit-mcp` ship on its own release cadence (its own gates, its own
   `npm publish`) without a pipeline release, as long as pinned tools keep their
   contract.
 - **Neither boundary is symmetric.** The pipeline depends on both other repos being

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "16.2.1",
+  "version": "16.2.2",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",