@mmerterden/multi-agent-pipeline 16.28.0 → 16.30.0

package/pipeline/skills/shared/core/multi-agent-sync/SKILL.md

@@ -30,9 +30,10 @@ When invoked, it synchronizes all targets in order. It detects what changed, upd
 Run all steps automatically:
 
 ```
+Step 0: DOCTOR      node $HOME/.claude/scripts/doctor.mjs  -  exit 2 or 4 STOPS the sync
 Step 1: DETECT      Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 51 sub-command skills)
-Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 51 specs as refs + 8 agent TOML)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 53 sub-command skills)
+Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 53 specs as refs + 8 agent TOML)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub)
 Step 3d: DEV-TOOLKIT Companion MCP server -> detect movement, ship gates, commit + publish
 Step 4: WEBSITE     Version + phase/model counts -> {website-host} (i18n + projects.ts)
@@ -40,6 +41,8 @@ Step 5: Commit      Commit + push all changed repos
 Step 6: Report      Summary: synced targets, changed files, deploy status, multi-agent-toolkit version
 ```
 
+**Step 0 is a gate, not a report.** Syncing a blocked install copies one fault onto five surfaces, and the copies are what people then debug. Exit 4 stops too: the layout did not resolve, so nothing was checked, and syncing from an unknown state is worse than not syncing.
+
 If nothing is stale -> report "All targets up to date" and stop.
 
 ## Special inputs
@@ -98,7 +101,7 @@ If nothing is stale -> report "All targets up to date" and stop.
 ## Codex Sync (Step 2b)
 
 This step does **not** hand-copy files. The Codex tree is a *transform* of the Claude
-tree, not a mirror: the 51 sub-command specs become reference files (Codex silently
+tree, not a mirror: the 53 sub-command specs become reference files (Codex silently
 truncates its skills block  -  see `cross-cli-contract.md` 2.6), every reference to a
 CLI-owned tree is retargeted (`agents/<persona>.md` becomes `.toml`, the dispatcher
 becomes the router skill), the 8 personas are regenerated as TOML with a model +
@@ -224,11 +227,11 @@ When invoked with the `release` argument:
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}/SKILL.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**51 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**53 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
-analysis, analysis-resolve, autopilot, build-optimize, channels,
-complaint-analysis, create-jira, design-check, diff-explain, feedback,
+analysis, analysis-jira, analysis-resolve, autopilot, build-optimize, channels,
+complaint-analysis, create-jira, design-check, doctor, diff-explain, feedback,
 forget, garbage-collect, graph, help, ios-coding-standard, issue, jira,
 kill, language, local, local-autopilot, log, manual-test, prune-logs,
 prune-prompts, purge, refactor, resume, resume-local, review,

package/pipeline/skills/shared/core/multi-agent-update/SKILL.md

@@ -6,6 +6,24 @@ user-invocable: true
 argument-hint: ""
 ---
 
+## After the install, check it
+
+```bash
+node "$HOME/.claude/scripts/doctor.mjs"
+```
+
+An update is the moment the layout changes, so it is the moment a layout check is
+worth most: a script that moved, a host tree that did not get the copy, a version
+stamp that disagrees with the package. Report the result in `outputLanguage`.
+Exit 2 means the update left the install in a state a run will fail from - say
+that, do not report "updated" and stop.
+
+# multi-agent update
+
+Update the pipeline in one command. The npm registry is the single update channel: the latest published release is downloaded and installed. Existing preferences are preserved; only skill / script / schema files are refreshed.
+
+A git clone of the pipeline repo is a maintainer workspace, kept in sync by `/multi-agent:sync` - it is never consulted here. A fix that only exists on `main` reaches users when a release is published, not before.
+
 # multi-agent-update  -  Pipeline Update
 
 Update the pipeline with a single command. Preferences are preserved; only skill/script/schema files are refreshed.