@mmerterden/multi-agent-pipeline 19.1.3 → 20.0.0

package/pipeline/scripts/smoke-schema-validation.sh

@@ -26,11 +26,10 @@ LIVE_PREFS="$HOME/.claude/multi-agent-preferences.json"
 
 # The migration target, derived the way migrate-prefs.mjs derives it: the last
 # entry of the schema's schemaVersion enum, read from the schema that sits
-# beside the migrator being checked. It used to be grepped as a
-# `TARGET_VERSION = "x.y.z"` literal out of the migrator, and when that literal
-# was replaced by the schema read - precisely because a literal had drifted a
-# minor behind - the grep started matching nothing and both checks that depend
-# on it reported "no reference point". A gate that reads the source of truth
+# beside the migrator being checked. Not grepped as a `TARGET_VERSION = "x.y.z"`
+# literal out of the migrator: a literal drifts, and the moment it is replaced by
+# a schema read the grep matches nothing and both checks that depend on it report
+# "no reference point". A gate that reads the source of truth
 # cannot go stale against it; a gate that reads a transcription of it can.
 migration_target() {
   local schema="$1/../schemas/prefs.schema.json"
@@ -213,15 +212,13 @@ if [ -f "$LIVE_PREFS" ]; then
 
   # The target is read from migrate-prefs.mjs, never hardcoded here.
   #
-  # This block used to say `if [ "$LVER" = "2.1.0" ]; then pass "already v2.1.0"`
-  # with everything else falling through to `fail "unknown schemaVersion"`. The
-  # migration target had since moved to 2.4.0, which inverted the gate: a prefs
-  # file left behind at 2.1.0 reported PASS as "already current", while a file
-  # correctly migrated to 2.4.0 hit the else arm and FAILED as "unknown". The
-  # gate was rejecting the only fully-migrated state it exists to encourage.
+  # A hardcoded version here inverts the gate the moment the migration target
+  # moves: the stale version passes as "already current" and the correctly
+  # migrated one falls through to "unknown schemaVersion", so the gate rejects
+  # the only fully-migrated state it exists to encourage.
   #
   # Reading the target and the accepted set from the same schema enum the
-  # migrator reads means this can never disagree with it again.
+  # migrator reads means this cannot disagree with it.
   MIGRATOR="$SMOKE_DIR/migrate-prefs.mjs"
   TARGET=$(migration_target "$(dirname "$MIGRATOR")")
   KNOWN=$(node -e "

package/pipeline/scripts/usage-report.mjs

@@ -277,7 +277,6 @@ function commandOf(state) {
   const c = state.command;
   if (typeof c === "string" && c.trim()) return c.trim().slice(0, 60);
   if (state.mode) return state.mode;
-  if (state.onlyDevelop) return "dev";
   if (state.localMode) return "local";
   return "full";
 }
@@ -501,7 +500,6 @@ function buildEvent(state) {
     m: state.mode || null,
     ap: Boolean(state.autopilot),
     lo: Boolean(state.localMode),
-    dev: Boolean(state.onlyDevelop),
     in: inputType(state),
     rp: projectDigest(state.project),
     ph: typeof state.currentPhase === "number" ? state.currentPhase : null,
@@ -612,11 +610,11 @@ if (invokedDirectly) {
   // Exit 0 stays: usage telemetry must never be the reason a run fails, and a
   // non-zero exit here would propagate into whatever called it.
   //
-  // But the silence goes. `catch(() => process.exit(0))` reported success for
-  // every failure, so a telemetry path that had been broken for weeks looked
-  // exactly like one that worked - there was no surface on which anyone could
-  // notice. One line on stderr costs nothing and is the difference between a
-  // degraded feature and an invisible one.
+  // But the silence goes. A bare `catch(() => process.exit(0))` reports success
+  // for every failure, so a broken telemetry path looks exactly like one that
+  // works and there is no surface on which to notice it. One line on stderr
+  // costs nothing and is the difference between a degraded feature and an
+  // invisible one.
   main().catch((err) => {
     process.stderr.write(`usage-report: not sent  -  ${err?.message ?? err}\n`);
     process.exit(0);

package/pipeline/scripts/validate-analysis-doc.mjs

@@ -935,10 +935,10 @@ function main() {
 
   mark("placeholder-bodies", profile === "global" ? undefined : "corporate profile");
 
-  // 4b. Locked 2's numbering half, which was ungated until v19.0.0.
+  // 4b. Locked 2's numbering half.
   //
-  // It is NOT "numbering re-flows 1..N". That is what the rule used to say and
-  // it could not hold: Locked 30 threads ids across the document by section
+  // It is NOT "numbering re-flows 1..N", which could not hold: Locked 30
+  // threads ids across the document by section
   // NUMBER ("Section 15.1 scenario", "Section 4.4", "Section 3/5 layout cells"),
   // so a re-flowed document sends every one of those references to the wrong
   // section. No emitted document ever re-flowed. The rule was the wrong half.

package/pipeline/scripts/worktree-finalize.sh

@@ -116,13 +116,13 @@ fi
 
 # --- preconditions ---------------------------------------------------------
 
-# `--local` mode has no worktree: worktreePath equals the project root. Removing
+# A local workspace has no worktree: worktreePath equals the project root. Removing
 # it would delete the user's checkout.
 rp_wt="$(cd "$WORKTREE" 2>/dev/null && pwd -P || echo "")"
 rp_pr="$(cd "$PROJECT_ROOT" 2>/dev/null && pwd -P || echo "")"
 [ -n "$rp_wt" ] || skip "worktree path does not exist: $WORKTREE"
 [ -n "$rp_pr" ] || skip "project root does not exist: $PROJECT_ROOT"
-[ "$rp_wt" != "$rp_pr" ] || skip "worktree equals project root (--local mode)  -  nothing to remove"
+[ "$rp_wt" != "$rp_pr" ] || skip "worktree equals project root (local workspace)  -  nothing to remove"
 
 # Refuse if the caller is standing inside the tree being removed. A shell left on
 # a deleted inode is worse than a leftover directory, and Phase 4 legitimately

package/pipeline/scripts/write-state.mjs

@@ -40,6 +40,9 @@
  *   WRITE_STATE_LOCK_ABANDON_MS  ceiling past which even a lock that probes as
  *                                alive is reclaimed, covering PID reuse
  *                                (default: 10x STALE_MS)
+ *   WRITE_STATE_TEST_DELAY_MS    test seam: pause between acquiring the lock
+ *                                and the write, so the exit-4 refusal can be
+ *                                driven on purpose (default 0, off)
  * A dead holder (PID no longer alive) is reclaimed immediately regardless of
  * age. A live holder keeps its lock: liveness outranks age. See
  * lockIdentityIfStale() for why that order is load-bearing.
@@ -109,11 +112,11 @@ async function acquireLock(
   const staleMs = Number(process.env.WRITE_STATE_LOCK_STALE_MS) || 30_000;
   const deadline = Date.now() + timeoutMs;
   // The lock file must never be observable without its owning PID inside it.
-  // It used to be created with openSync(wx) and filled on the next line, so
-  // between those two calls it existed and was empty. A writer arriving in
-  // that window read an unparseable PID, concluded the lock was stale, and
-  // deleted a live one - after which two writers held it and one write was
-  // lost. Under CPU load that reproduced 3 times in 15 runs.
+  // Created with openSync(wx) and filled on the next line, it exists and is
+  // empty between those two calls. A writer arriving in that window reads an
+  // unparseable PID, concludes the lock is stale, and deletes a live one -
+  // after which two writers hold it and one write is lost. The window is only
+  // wide enough to hit under CPU load, which is where it matters.
   //
   // Writing the PID into a private temp file and hard-linking it into place
   // closes the window: link() fails with EEXIST if the lock is held, and the
@@ -141,8 +144,8 @@ async function acquireLock(
       // deleting it, the holder can release and a THIRD writer can acquire a
       // fresh one - and an unlink by path deletes that live lock, after which
       // two writers hold it and one update is lost. Same failure the PID window
-      // above once caused, at a different point in the loop; it survived because
-      // it only reproduces under load, where the gap is wide enough to lose.
+      // above describes, at a different point in the loop, and it only reproduces
+      // under load, where the gap is wide enough to lose.
       //
       // The inode is the identity: a newly acquired lock is a different file
       // even at the same path. Delete only if the file we judged is still the
@@ -176,10 +179,10 @@ async function acquireLock(
  * A lock is stale when its owning PID is no longer alive. Age alone is not
  * staleness.
  *
- * The order here is the whole point. Age used to be checked first and returned
- * "stale" on its own, so a holder that was demonstrably ALIVE lost its lock the
- * moment the file passed 30 seconds - and the next writer then deleted a live
- * lock and overwrote the update behind it. Liveness is direct evidence;
+ * The order here is the whole point. Checking age first and returning "stale" on
+ * its own costs a holder that is demonstrably ALIVE its lock the moment the file
+ * passes 30 seconds - and the next writer then deletes a live lock and overwrites
+ * the update behind it. Liveness is direct evidence;
  * a timestamp is a guess about it, and a guess must not overrule the evidence.
  *
  * Age survives for the one case liveness cannot answer: PID reuse. A dead
@@ -330,6 +333,14 @@ async function main() {
   try {
     heldLockIno = await acquireLock(path);
     heldLockFor = path;
+    // Test seam. The refusal below is the one path that cannot be reached on
+    // demand: it needs another writer to take the lock inside the window
+    // between acquiring it and renaming, which on an idle machine is too
+    // narrow to hit and on a loaded one is a coin flip. A gate that can only
+    // observe this path by accident is not holding it. Unset in every real
+    // run; the whole seam is one sleep.
+    const testDelayMs = Number(process.env.WRITE_STATE_TEST_DELAY_MS) || 0;
+    if (testDelayMs > 0) await new Promise((r) => setTimeout(r, testDelayMs));
   } catch (err) {
     if (err.code === "LOCK_TIMEOUT") {
       console.error(err.message);

package/pipeline/skills/.skill-manifest.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-09-21T06:17:16Z",
-  "skillCount": 216,
+  "generatedAt": "2026-09-21T11:25:15Z",
+  "skillCount": 213,
   "entries": [
     {
       "path": "shared/core/apple-archive-compliance/SKILL.md",
@@ -33,7 +33,7 @@
     },
     {
       "path": "shared/core/multi-agent-autopilot-status/SKILL.md",
-      "sha256": "065958fb3ff608d7d0ea36b3eef4614da442742dc69b00799cf1658848cee786"
+      "sha256": "f706d3fe4a0db86691d525f4bc008c095fddffbf69026fc553b780b2389eac6e"
     },
     {
       "path": "shared/core/multi-agent-autopilot/SKILL.md",
@@ -45,7 +45,7 @@
     },
     {
       "path": "shared/core/multi-agent-channels/SKILL.md",
-      "sha256": "414eead38b461c8aa95f6af3175366be905338233e6872313f5d4f59a02351af"
+      "sha256": "e4f59e784d77018326e719632ef371e50e9fb9af61318a7d5bf713c386c0fd3f"
     },
     {
       "path": "shared/core/multi-agent-complaint-analysis/SKILL.md",
@@ -85,11 +85,11 @@
     },
     {
       "path": "shared/core/multi-agent-help/SKILL.md",
-      "sha256": "6ebe7d4de1a1ff815f572abb5d5db5d5af9ea507b3047ec60597a54455176da5"
+      "sha256": "4d6181bd8d612f758db5b60df1b18668cf39a5fa3b5174c19b063491d240c054"
     },
     {
       "path": "shared/core/multi-agent-ios-coding-standard/SKILL.md",
-      "sha256": "15a8d583cb7c772d5223c66c158062f25fdff4c41c6d353b7b70590a441dea38"
+      "sha256": "a424507424e883be63886da79b294314e03c73129c658b4ad3d080315f60e325"
     },
     {
       "path": "shared/core/multi-agent-issue/SKILL.md",
@@ -107,14 +107,6 @@
       "path": "shared/core/multi-agent-language/SKILL.md",
       "sha256": "63e746bc63ec9963c54e852e6ca5cdb30afd9309a02ee3fdb35965eb931d0300"
     },
-    {
-      "path": "shared/core/multi-agent-local-autopilot/SKILL.md",
-      "sha256": "5e367258e57fa710d16a1ad6363d5974b89aa99fb0ac791d1ce0070c81191f6b"
-    },
-    {
-      "path": "shared/core/multi-agent-local/SKILL.md",
-      "sha256": "0a5f20782de81ac3376088579ff6fbc3a6f3781cb285860aae796408aa57e6aa"
-    },
     {
       "path": "shared/core/multi-agent-log/SKILL.md",
       "sha256": "34bb9841af478abfd4a052d13b821ab4ccd9b5ba29154e9a06029312955b45a4"
@@ -143,13 +135,9 @@
       "path": "shared/core/multi-agent-refactor/SKILL.md",
       "sha256": "56eb2be076a6840ddfbf57b8e82c8b4bcf76209553d41a06cc71e56dc894364e"
     },
-    {
-      "path": "shared/core/multi-agent-resume-local/SKILL.md",
-      "sha256": "9f5089c748a8f0ae5983a3f392879a86017a33c883a87607169e32705c68c5e9"
-    },
     {
       "path": "shared/core/multi-agent-resume/SKILL.md",
-      "sha256": "6701424edde0a19b55a7de62bb5ba5f9dbaef7d9fb9ea2bce632374863145774"
+      "sha256": "57b97c497d34d10afdd030f44b74628a0d9f054431fec424dab7114cba775cf7"
     },
     {
       "path": "shared/core/multi-agent-review-analysis/SKILL.md",
@@ -217,7 +205,7 @@
     },
     {
       "path": "shared/core/multi-agent-sync/SKILL.md",
-      "sha256": "3d3331d34f9610ea02b96ee27c8029734f3a3447d2857fc0dca92d5b43d0f8e2"
+      "sha256": "34aea52bbbe86018011edc1c96a986d1ee2aba8bdb82b19212714bac80bea076"
     },
     {
       "path": "shared/core/multi-agent-test-accessibility/SKILL.md",
@@ -253,7 +241,7 @@
     },
     {
       "path": "shared/core/multi-agent/SKILL.md",
-      "sha256": "9ab7af2ffb01f8eb0fae624ae40ea9ff2f6d69ad61544bd266b1b97f60eb4a0f"
+      "sha256": "ca1286f3f17d76b75547320ec9b39af575a88828da14b4ed4ffe79932c7406a3"
     },
     {
       "path": "shared/external/accessibility-compliance-accessibility-audit/SKILL.md",

package/pipeline/skills/.skills-index.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "1.0.0",
-  "skillCount": 216,
+  "skillCount": 213,
   "entries": [
     {
       "name": "accessibility-compliance-accessibility-audit",
@@ -180,7 +180,7 @@
     },
     {
       "name": "apple-archive-compliance",
-      "description": "Apple App Store Review compliance  -  wraps the multi-agent-toolkit-mcp `ios_app_store_audit` tool (18-rule deep scan) with ITMS error code mapping + EN/TR humanizer templates. Consumed by: /multi-agent:test 'store-ready' (primary dispatch), Phase 4 Security Auditor (catalog cross-ref on Info.plist ",
+      "description": "Apple App Store Review compliance  -  wraps the multi-agent-toolkit-mcp `ios_app_store_audit` tool (18-rule deep scan) with ITMS error code mapping + EN/TR humanizer templates. Consumed by: /multi-agent:test 'store-ready' (primary dispatch), Phase 3 Security Auditor (catalog cross-ref on Info.plist ",
       "platform": null,
       "group": "core",
       "plugin": null,
@@ -587,7 +587,7 @@
     },
     {
       "name": "google-play-compliance",
-      "description": "Google Play Store publication compliance  -  bundletool + aapt2 + apksigner orchestration + 21-rule policy catalog with Play Console error codes + humanizer templates. Consumed by: /multi-agent:test 'store-ready' (primary dispatch), Phase 4 Security Auditor (catalog cross-ref on AndroidManifest / bu",
+      "description": "Google Play Store publication compliance  -  bundletool + aapt2 + apksigner orchestration + 21-rule policy catalog with Play Console error codes + humanizer templates. Consumed by: /multi-agent:test 'store-ready' (primary dispatch), Phase 3 Security Auditor (catalog cross-ref on AndroidManifest / bu",
       "platform": null,
       "group": "core",
       "plugin": null,
@@ -1159,7 +1159,7 @@
     },
     {
       "name": "multi-agent-ios-coding-standard",
-      "description": "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent or :local. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions.",
+      "description": "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions.",
       "platform": null,
       "group": "core",
       "plugin": null,
@@ -1212,28 +1212,6 @@
       "triggerPaths": [],
       "relativePath": "shared/core/multi-agent-language/SKILL.md"
     },
-    {
-      "name": "multi-agent-local",
-      "description": "Full pipeline in local mode  -  no worktree, runs directly on the current branch. Use when the full pipeline should run on the current branch without creating a worktree.",
-      "platform": null,
-      "group": "core",
-      "plugin": null,
-      "invokeAs": "multi-agent-local",
-      "triggerKeywords": [],
-      "triggerPaths": [],
-      "relativePath": "shared/core/multi-agent-local/SKILL.md"
-    },
-    {
-      "name": "multi-agent-local-autopilot",
-      "description": "Full pipeline + local + autopilot  -  no worktree, no confirmations, all 6 phases run end-to-end on the current branch. Use when the full pipeline should run on the current branch with no worktree and no prompts.",
-      "platform": null,
-      "group": "core",
-      "plugin": null,
-      "invokeAs": "multi-agent-local-autopilot",
-      "triggerKeywords": [],
-      "triggerPaths": [],
-      "relativePath": "shared/core/multi-agent-local-autopilot/SKILL.md"
-    },
     {
       "name": "multi-agent-log",
       "description": "Show the agent-log.md for the given task. With no ID, shows the most recent task. Use when asked what a task did, or to read its log.",
@@ -1247,7 +1225,7 @@
     },
     {
       "name": "multi-agent-manual-test",
-      "description": "Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 5 standalone (the UI Bug Hunter lives at multi-agent-test). Use when a finished change needs trying by hand on a device or simulator.",
+      "description": "Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 3 user-test step, standalone (the UI Bug Hunter lives at multi-agent-test). Use when a finished change needs trying by hand on a device or simulator.",
       "platform": null,
       "group": "core",
       "plugin": null,
@@ -1313,7 +1291,7 @@
     },
     {
       "name": "multi-agent-resume",
-      "description": "Resume a stopped or failed task from the phase where it left off. Use when a task stopped or failed and should carry on from where it left off.",
+      "description": "Pick up unfinished work: a pipeline run that stopped mid-phase, or work already written on the current branch that never went through the pipeline. Use when a task stopped or failed, or when hand-written local work needs review, build, PR and reporting.",
       "platform": null,
       "group": "core",
       "plugin": null,
@@ -1322,17 +1300,6 @@
       "triggerPaths": [],
       "relativePath": "shared/core/multi-agent-resume/SKILL.md"
     },
-    {
-      "name": "multi-agent-resume-local",
-      "description": "Continue already-done LOCAL work through the pipeline tail: Review (with its build gate) → Commit/PR → Report (technical analysis + Jira test-scenario comment). No dev phase. Use when local work is already done and only review, build, commit and reporting remain.",
-      "platform": null,
-      "group": "core",
-      "plugin": null,
-      "invokeAs": "multi-agent-resume-local",
-      "triggerKeywords": [],
-      "triggerPaths": [],
-      "relativePath": "shared/core/multi-agent-resume-local/SKILL.md"
-    },
     {
       "name": "multi-agent-review",
       "description": "Run parallel review on a branch diff or a Pull Request: 3 models on Claude Code (Fable + Opus + Sonnet), 3 models on Copilot CLI (GPT + Opus + Sonnet). On PR input, posts per-finding inline comments + approve/needs-work. With no input (interactive), lists open GitHub + Bitbucket PRs to multi-select.",

package/pipeline/skills/shared/README.md

@@ -2,11 +2,11 @@
 
 Single source of truth for skills delivered to both Claude Code (`~/.claude/skills/`) and Copilot CLI (`~/.copilot/skills/`) by the installer.
 
-**Total:** 216 skills (63 core + 153 external). Auto-generated by `scripts/gen-skills-index.mjs`  -  do not edit by hand.
+**Total:** 213 skills (60 core + 153 external). Auto-generated by `scripts/gen-skills-index.mjs`  -  do not edit by hand.
 
 ## Directory layout
 
-- **`core/`**  -  63 `multi-agent*` orchestration skills that are pipeline-critical. Edits here are core-code changes.
+- **`core/`**  -  60 `multi-agent*` orchestration skills that are pipeline-critical. Edits here are core-code changes.
 - **`external/`**  -  153 iOS / Android / generic skills imported from the upstream skill library. Mirrors of third-party guidance.
 - Install destinations (ADR-0009): Claude Code gets NO local copy of `external/` - it loads those skills from the `multi-agent-plugins` marketplace, namespaced (`ai-<stack>-toolkit:<name>`); only the two compliance catalogs from `core/` land in `~/.claude/skills/`. Copilot CLI and Codex CLI receive a flat copy filtered to the enabled stacks. `external/` remains the single authoring source that `build-stack-plugins.mjs` publishes from.
 
@@ -14,7 +14,7 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 
 ## Categories
 
-- [Pipeline Orchestration](#pipeline-orchestration)  -  63
+- [Pipeline Orchestration](#pipeline-orchestration)  -  60
 - [iOS / Apple Ecosystem](#ios-apple-ecosystem)  -  90
 - [Android / Kotlin](#android-kotlin)  -  13
 - [Web](#web)  -  10
@@ -52,17 +52,14 @@ Source layout is logical grouping only  -  skill discovery at runtime is unchang
 | [`multi-agent-jira`](./core/multi-agent-jira/) | `core` | List open Jira issues, pick one, and launch the multi-agent pipeline. Use when a Jira issue should be picked up and started without knowing  |
 | [`multi-agent-kill`](./core/multi-agent-kill/) | `core` | Stop the given task, then remove its worktree and branch. Asks for confirmation. Use when a running or stuck task should be stopped and its  |
 | [`multi-agent-language`](./core/multi-agent-language/) | `core` | Toggle outputLanguage (assistant explanations, picker questions, PR/Jira/Confluence bodies). promptLanguage is fixed to English; commit mess |
-| [`multi-agent-local`](./core/multi-agent-local/) | `core` | Full pipeline in local mode  -  no worktree, runs directly on the current branch. Use when the full pipeline should run on the current branc |
-| [`multi-agent-local-autopilot`](./core/multi-agent-local-autopilot/) | `core` | Full pipeline + local + autopilot  -  no worktree, no confirmations, all 6 phases run end-to-end on the current branch. Use when the full pi |
 | [`multi-agent-log`](./core/multi-agent-log/) | `core` | Show the agent-log.md for the given task. With no ID, shows the most recent task. Use when asked what a task did, or to read its log. |
-| [`multi-agent-manual-test`](./core/multi-agent-manual-test/) | `core` | Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 5 standalone (the UI Bug Hunter lives at multi-agent-te |
+| [`multi-agent-manual-test`](./core/multi-agent-manual-test/) | `core` | Switch to the active task's branch and prepare it for manual testing in Xcode. Phase 3 user-test step, standalone (the UI Bug Hunter lives a |
 | [`multi-agent-model`](./core/multi-agent-model/) | `core` | Turn the top model rung on or off and keep the cost ledger's pricing in step with it. Use when asked to enable or disable Fable, or which mo |
 | [`multi-agent-prune-logs`](./core/multi-agent-prune-logs/) | `core` | Delete per-task project logs under ~/.claude/logs/multi-agent (filter by age/project/task). Audit trail + metrics are preserved. Dry-run fir |
 | [`multi-agent-prune-prompts`](./core/multi-agent-prune-prompts/) | `core` | Zero-base prompt review: measure the always-on instruction footprint, classify every rule block, propose keep/trial-removal/delete; applies  |
 | [`multi-agent-purge`](./core/multi-agent-purge/) | `core` | ⚠️ Wipes every worktree, branch, log, and state file. Irreversible; asks for double confirmation. Use when every worktree, branch, log and s |
 | [`multi-agent-refactor`](./core/multi-agent-refactor/) | `core` | Analyse the project: extract adapted best-practices, hunt real bugs + improvement areas, check upstream drift of derived skills, research th |
-| [`multi-agent-resume`](./core/multi-agent-resume/) | `core` | Resume a stopped or failed task from the phase where it left off. Use when a task stopped or failed and should carry on from where it left o |
-| [`multi-agent-resume-local`](./core/multi-agent-resume-local/) | `core` | Continue already-done LOCAL work through the pipeline tail: Review (with its build gate) → Commit/PR → Report (technical analysis + Jira tes |
+| [`multi-agent-resume`](./core/multi-agent-resume/) | `core` | Pick up unfinished work: a pipeline run that stopped mid-phase, or work already written on the current branch that never went through the pi |
 | [`multi-agent-review`](./core/multi-agent-review/) | `core` | Run parallel review on a branch diff or a Pull Request: 3 models on Claude Code (Fable + Opus + Sonnet), 3 models on Copilot CLI (GPT + Opus |
 | [`multi-agent-review-analysis`](./core/multi-agent-review-analysis/) | `core` | Review a written analysis document instead of a diff: resolve it from a path, a Confluence page or a Jira issue, run the deterministic gates |
 | [`multi-agent-review-issue`](./core/multi-agent-review-issue/) | `core` | Assess whether a GitHub issue is ready for multi-agent development: fetch it, grade scope / acceptance criteria / repro / design / API / sta |

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

@@ -311,25 +311,22 @@ Every user-facing phase title  -  TaskCreate cards, `phase-banner.sh` headers, a
 
 All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied (Claude Code path; Copilot CLI does not have a TaskList widget so this rule is Claude-only). The native widget renders by creation order, not by phase-number metadata  -  out-of-order calls produce visually scrambled tile stacks (e.g. `1 ✓ · 2 ✓ · 4 ✓ · 0 ▶ · 3 ☐`) even when the underlying state file is correct. Pre-marking phases as completed/skipped before Phase 0 starts is FORBIDDEN: register the tile in order with default `pending` status, then flip via TaskUpdate when the phase actually short-circuits. Mode-specific phase sets:
 
-- `multi-agent`: 0 → 1 → 2 → 3 → 4 → 5 → 6 → 7
-- `multi-agent-local`, `multi-agent-autopilot`, `multi-agent-local-autopilot`: 0 → 1 → 2 → 3 → 4 → 5 (the interactive Phase 5 gate needs a worktree checkout and an attended run)
-- `multi-agent-analysis`: 0 → 1 → 2 → 4 → 6 → 7 (no code, so no Dev and no Test)
+- `multi-agent`, `multi-agent-autopilot`: 0 → 1 → 2 → 3 → 4 → 5 (the user-test gate inside Phase 3 needs a worktree checkout and an attended run; the phase set is the same either way)
+- `multi-agent-analysis`: 0 → 1 → 3 → 4 → 5 (no code is written, so Dev is not in the set)
 
-Depth decides WHICH of the command's set is registered. The tracker boots at Step -1, long before the depth question can be asked, so it registers Phase 0 alone and the remaining tiles are created at Step 7.5 once the answer is known - a Short run never draws an Analysis or Planning tile.
+Every mode registers its whole set at Step -1: the set is a property of the command, so nothing is deferred.
 
 Full contract: `refs/tracker-contract.md` section "TaskCreate ordering (strict)".
 
 ### Phase 0: Init
 
-> **Contract (strict)**  -  Phase 0 has **8 sequential interactive steps** plus the
-> Step 7.5 depth question (`/multi-agent` and `:local` only; the autopilot entries
-> skip it and always run Full), defined in
+> **Contract (strict)**  -  Phase 0 has **8 sequential interactive steps**, defined in
 > `refs/phases/phase-0-init.md`. Read it before every Phase 0 run and execute all of
 > them. Do **NOT** short-circuit: even when the input is a Jira ID plus a branch, the
 > prefs load, the multi-repo offer, the branch picker and the branch-name confirm are
-> required UX checkpoints. A run once took a Jira ID and implemented straight onto the
-> local checkout with neither the project nor the branch picker ever shown, and nothing
-> failed, so nothing caught it. The walkthrough below covers input parsing and worktree
+> required UX checkpoints. Skipping them lets a Jira ID land straight on the local
+> checkout with neither the project nor the branch picker ever shown, and nothing
+> fails, so nothing catches it. The walkthrough below covers input parsing and worktree
 > creation only; it is not the contract.
 >
 > **Exit gate (BLOCKING).** Prose alone did not stop that run. Before marking Phase 0
@@ -434,7 +431,7 @@ Two halves, one phase, one approval gate (Phases 1 and 2 until 19.0.0).
 2. Launch **ios-architect** agent for architecture review (if structural changes)
 3. Determine development approach per todo (new file, modify, refactor)
 4. Log: `🧠 Phase 1: Plan  -  {N} todos created`
-5. **Plan Approval Gate** (Full + interactive only  -  a Short run has no plan, autopilot may not ask). Full flow in `refs/phases/phase-1-plan.md` Step 5:
+5. **Plan Approval Gate** (interactive only  -  autopilot may not ask). Full flow in `refs/phases/phase-1-plan.md` Step 5:
    - **5a  -  Clarification** (conditional, max 2 rounds): if the Jira/issue description is ambiguous (vague acceptance, UI task without Figma, API task without endpoint contract, `ambiguityScore >= 2`, parent-story scope drift), ask structured questions before rendering the plan. User answers → plan regenerated. If it is still unclear after the 2nd round, render the plan with a "best-effort" banner.
    - **5b  -  Approval loop**: render plan → user: `onayla`/`iptal`/free-text. A free-text edit request → the planning model (Fable) revises the plan → show it again. No iteration cap; user controls exit via `onayla` or `iptal`.
    - Persist `clarificationRounds`, `clarificationQuestions`, `clarificationAnswers`, `planIterations`, `planApprovedAt`, `planEditRequests` to `state.phases["1"]`.
@@ -708,5 +705,5 @@ When `multi-agent status` is called, show:
 ## Help Display
 
 Rendered by the `multi-agent-help` skill (`/multi-agent:help`), which owns
-the full text in both languages. It used to be duplicated here in English
-only, on a path this skill takes for exactly one input.
+the full text in both languages. Duplicating it here would mean English only,
+on a path this skill takes for exactly one input.

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

@@ -37,7 +37,7 @@ not a fault.
 
 When `swiftc` was available at `autopilot-on` time, `~/.claude/autopilot/bin/menubar`
 shows the same thing in the top right, refreshing on its own: one row per item
-with its id, whether it is running Full or Short, the phase as a fraction, the
+with its id, the phase as a fraction, the
 elapsed time and the stack, then the queue, then what is waiting, then the PRs of
 the last day - each one clickable.
 

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

@@ -152,11 +152,10 @@ h2. Bağlantılar
 Reproduction scenarios first, then regressions for whatever the change could
 have disturbed. Full contract: `channels/jira.md`.
 
-`{{file.ext → func}}`, `*Root cause:*` and `*Changed files:*` used to be this
-template. They are gone deliberately: that shape put a hash-table mutation
-walk in front of a tester, and `{{file → func}}` is exactly where a Swift
-selector like `hash(into:)` ends up - whose trailing `:)` Jira renders as a
-smiley.
+`{{file.ext → func}}`, `*Root cause:*` and `*Changed files:*` are deliberately
+NOT this template. That shape puts a hash-table mutation walk in front of a
+tester, and `{{file → func}}` is exactly where a Swift selector like
+`hash(into:)` ends up - whose trailing `:)` Jira renders as a smiley.
 
 **Post through the publisher, never a hand-rolled `curl`:**
 

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

@@ -38,8 +38,8 @@ Render **exactly one** of the two blocks below  -  the one matching `LANG`. Do n
   multi-agent "#316"                              -> GitHub Issue #
   multi-agent "bug/feature description"           -> Free-text
 
-(Copilot CLI uses the dash form: multi-agent-local, multi-agent-channels, etc.
- Claude Code uses colon form: /multi-agent:local, /multi-agent:channels, etc.)
+(Copilot CLI uses the dash form: multi-agent-channels, etc.
+ Claude Code uses colon form: /multi-agent:channels, etc.)
 
 ------------------------------------------------------------
 
@@ -52,7 +52,7 @@ How It Works (Phase 0  -  Interactive Flow):
   5. BRANCH NAME bugfix/{jiraId} or feature/{jiraId} -> confirm
   6. GIT ID      Select identity from preferences (multiple supported)
   7. INSTRUCTION Auto-detect if .instructions/ exists (figma etc.)
-  8. WORKSPACE   Create worktree (default) or local branch (--local)
+  8. WORKSPACE   Ask where the branch lives: worktree (default) or project root
 
 ------------------------------------------------------------
 
@@ -76,17 +76,15 @@ Pipeline (after Phase 0):
 
 Modes:
 
-  Depth is asked at Phase 0 Step 7.5, not passed as a flag:
-    Full   Plan -> Dev(Sonnet) -> Review -> Commit -> Report
-    Short  Dev(Opus, self-contained) -> Review -> Commit -> Report
-  Recommended from taskType. Review is never skipped either way.
+  One pipeline. Every mode runs its whole phase set:
+    Plan -> Dev(Sonnet) -> Review -> Commit -> Report
+  What a run costs follows the evidence the task carries.
 
-  --local              No worktree  -  works directly on local branch
-  autopilot            Skip all confirmations, including the depth question, so
-                       it always runs Full (EXCEPT Phase 5 channels menu)
+  autopilot            Skip all confirmations and resolve the workspace to a
+                       worktree (EXCEPT Phase 5 channels menu)
 
 Dedicated dash commands (Copilot):
-  multi-agent-local, multi-agent-autopilot, multi-agent-local-autopilot
+  multi-agent-autopilot
 
 ------------------------------------------------------------
 
@@ -212,8 +210,8 @@ Logs: $HOME/.copilot/logs/multi-agent/{project}/{task-id}/  (Copilot)
   multi-agent "#316"                              -> GitHub Issue #
   multi-agent "bug/özellik açıklaması"            -> Serbest metin
 
-(Copilot CLI dash form kullanır: multi-agent-local, multi-agent-channels vb.
- Claude Code colon form kullanır: /multi-agent:local, /multi-agent:channels vb.)
+(Copilot CLI dash form kullanır: multi-agent-channels vb.
+ Claude Code colon form kullanır: /multi-agent:channels vb.)
 
 ------------------------------------------------------------
 
@@ -226,7 +224,7 @@ Nasıl Çalışır (Phase 0  -  İnteraktif Akış):
   5. BRANCH NAME bugfix/{jiraId} veya feature/{jiraId} -> onayla
   6. GIT ID      Kimlik seç (prefs'ten; birden fazla desteklenir)
   7. INSTRUCTION .instructions/ varsa otomatik algıla
-  8. WORKSPACE   Worktree yarat (default) ya da local branch (--local)
+  8. WORKSPACE   Branch nerede yaşayacak: worktree (default) ya da proje kökü
 
 ------------------------------------------------------------
 
@@ -255,12 +253,11 @@ Modlar:
     Kısa   Dev(Opus, kendi kendine yeten) -> Review -> Commit -> Report
   taskType'a göre önerilir. Review iki durumda da atlanmaz.
 
-  --local              Worktree yok  -  doğrudan local branch'te çalışır
   autopilot            Derinlik sorusu dahil tüm onayları atlar, bu yüzden her
                        zaman Tam koşar (İSTİSNA: Phase 5 channels menüsü)
 
 Dedicated dash komutlar (Copilot):
-  multi-agent-local, multi-agent-autopilot, multi-agent-local-autopilot
+  multi-agent-autopilot
 
 ------------------------------------------------------------
 

package/pipeline/skills/shared/core/multi-agent-ios-coding-standard/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: multi-agent-ios-coding-standard
 language: en
-description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent or :local. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
+description: "Audit an iOS module against the shared coding-standard registry (99 stable-ID rules), produce a remediation plan, then hand off to /multi-agent. Use for a standards pass on a module, or when a review needs rule IDs rather than opinions."
 user-invocable: true
 argument-hint: "[module name or path]"
 ---
@@ -237,10 +237,9 @@ Show a concise version of the plan to the user too.
 
 | Option | What it does |
 |---|---|
-| `/multi-agent:local` | No worktree; branches from the main development branch, fixes on the current checkout |
 | `/multi-agent` | Opens a worktree; fixes on a fresh branch + PR |
 
-Both ask Full or Short at Phase 0 Step 7.5; a standards sweep is usually already scoped, so Short is the common answer.
+Both run the whole pipeline; a standards sweep is usually already scoped, so Phase 1 has little to say and its document is short.
 
 Invoke the chosen command with the plan file as the task input, branching off the repo's main
 development branch (e.g. `chore/<module>-coding-standard`). The dev pipeline applies the fixes,