@mmerterden/multi-agent-pipeline 18.0.0 → 19.1.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "18.0.0",
-  "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.",
+  "version": "19.1.0",
+  "description": "6-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",
   "exports": {

package/pipeline/agents/dev-critic.md

@@ -1,14 +1,14 @@
 ---
 name: dev-critic
-description: "Phase 3.5 evaluator  -  runs after Dev's last edit, before Phase 4. Verifies build/test/checklist gates; returns pass | fix-list. Sonnet by default; Phase 3 orchestrator may override."
+description: "Phase 2.5 evaluator  -  runs after Dev's last edit, before Phase 4. Verifies build/test/checklist gates; returns pass | fix-list. Sonnet by default; Phase 3 orchestrator may override."
 model: sonnet
 preferredModel: sonnet
 modelRationale: "Critic tier  -  deterministic checklist + build/test verification needs reliable JSON output and tool-use, not deep reasoning. Sonnet hits the cost/quality sweet spot. Opus override only when the diff is large (>500 LOC) or touches security-critical paths; orchestrator decides via PHASE_MODEL_OVERRIDE."
 ---
 
-# Dev Critic Agent  -  Phase 3.5
+# Dev Critic Agent  -  Phase 2.5
 
-You are the in-loop critic for Phase 3 (Dev). The generator (Sonnet/Opus during Phase 3) has just finished its last edit. **You run BEFORE Phase 4**, on the same worktree, against deterministic criteria that already exist on disk. Your job: catch failures the generator would otherwise send into Phase 4 and waste 2-3 reviewer calls + Fable triage on.
+You are the in-loop critic for Phase 2 (Dev). The generator (Sonnet/Opus during Phase 2) has just finished its last edit. **You run BEFORE Phase 4**, on the same worktree, against deterministic criteria that already exist on disk. Your job: catch failures the generator would otherwise send into Phase 4 and waste 2-3 reviewer calls + Fable triage on.
 
 This is the **evaluator-optimizer pattern** from Anthropic's "Building Effective Agents"  -  the pattern is most effective "when we have clear evaluation criteria, and when iterative refinement provides measurable value." Phase 3 satisfies both: criteria are written in `rules/*.md`, refinement value is measured by Phase 4 fix-cycles avoided.
 
@@ -16,7 +16,7 @@ This is the **evaluator-optimizer pattern** from Anthropic's "Building Effective
 
 | Source | What it provides |
 |---|---|
-| Current worktree | Phase 3's final edit set |
+| Current worktree | Phase 2's final edit set |
 | `git diff origin/<base>...HEAD` | The diff under critique |
 | `rules/code-style.md` | Language/structure rules |
 | `rules/tdd.md` | Test-first contract |
@@ -119,14 +119,14 @@ Return ONLY a JSON object conforming to `pipeline/schemas/dev-critic-output.sche
 - **important**: Style/structure rule violation (missing accessibility id, force unwrap, magic-number-equivalent constant)
 - **suggestion**: Nice-to-have improvements (variable rename, comment clarity)
 
-Generator MUST fix all `blocking` items. `important` items SHOULD be fixed in round 1; if generator skips, they pass through to Phase 4 reviewers (who then have legitimate grounds to flag them, not theatre review).
+Generator MUST fix all `blocking` items. `important` items SHOULD be fixed in round 1; if generator skips, they pass through to Phase 3 reviewers (who then have legitimate grounds to flag them, not theatre review).
 
 `suggestion` items are **never** sent back for round 2  -  generator may apply them at its own judgement.
 
 ## What this agent does NOT do
 
 - Does NOT propose architectural changes (that's Phase 1/2's job)
-- Does NOT review for security depth (that's Phase 4 Reviewer 1 / security-auditor)
+- Does NOT review for security depth (that's Phase 3 Reviewer 1 / security-auditor)
 - Does NOT re-explore the codebase (use the existing diff and rules; no new exploration)
 - Does NOT post comments to the PR (this runs in-pipeline; only `post-pr-review.sh` posts)
 
@@ -140,7 +140,7 @@ LOG_METRIC_FORWARD_TO_TRACKER=1 pipeline/scripts/log-metric.sh "$TASK_ID" 3 \
   duration_ms=$D tokens_in=$TI tokens_out=$TO
 ```
 
-Phase 7 cost rollup includes critic calls as `phase 3.5` line items so cost summary shows the savings (or surplus) vs running Phase 4 directly.
+Phase 5 cost rollup includes critic calls as `phase 3.5` line items so cost summary shows the savings (or surplus) vs running Phase 4 directly.
 
 ## Rationale citation
 

package/pipeline/commands/figma-to-swiftui.md

@@ -1,5 +1,5 @@
 ---
-description: "Figma URL -> SwiftUI component generation (full 8-phase pipeline with SubPhases)"
+description: "Figma URL -> SwiftUI component generation (full 6-phase pipeline with SubPhases)"
 allowed-tools: Read, Write, Edit, Glob, Grep, Bash, Agent, WebFetch, TaskCreate, TaskUpdate
 ---
 

package/pipeline/commands/multi-agent/SKILL.md

@@ -80,7 +80,7 @@ Lib scripts (`~/.claude/lib/`):
 | `analysis ["<feature>"]` | Standalone feature-spec analizi: Figma / Swagger / Confluence / Jira / repo girdileri sabit 7-bölümlük şablona dökülür, humanizer'dan geçer, Local/Confluence/Jira hedef(ler)ine post edilir. Worktree veya commit yok. Dev'e zincirleme yok. |
 | `complaint-analysis ["<run-name>"] [--file <path>] [<jira-id\|confluence-url> ...]` | Müşteri şikayeti triyajı: şikayetler (serbest metin / csv-xlsx-txt-json dosya / Jira issue / Confluence URL) redakte edilerek alınır, trxId/conversationId ile Graylog kanıtı çekilir, seçili client + BFF repolarında salt-okunur eşleştirme yapılır; verdict: client/bff (kök neden + citation + mevcut mimariyi referans alan fix planı + hazır dev prompt'u) veya core (core ekibine yönlendirme önerisi) veya insufficient-evidence. Rapor + Stop; worktree, commit, dev zinciri yok. |
 | `build-optimize` | iOS-only Xcode build performance wrapper. Vendored `xcode-build-orchestrator`'a dispatch eder; benchmark + compilation / project / SPM analyzer'lar + recommend-first plan `.build-benchmark/optimization-plan.md`. Non-iOS stack'lerde fail-fast. |
-| `channels [PR-url\|#N\|Jira-url\|Jira-id] [--channels pr,jira,confluence,wiki] [--content normal,test,auto-diff,note] [--message "..."]` | Post task report to multi-select channels (PR description, Jira comment, Confluence page, Wiki pages) with multi-select content sources. Humanizer pass per-channel. Bitbucket PR updates use reviewer-preserving PUT. Phase 7 delegates to this command; also invocable post-hoc for fixes made outside the pipeline. No worktree. |
+| `channels [PR-url\|#N\|Jira-url\|Jira-id] [--channels pr,jira,confluence,wiki] [--content normal,test,auto-diff,note] [--message "..."]` | Post task report to multi-select channels (PR description, Jira comment, Confluence page, Wiki pages) with multi-select content sources. Humanizer pass per-channel. Bitbucket PR updates use reviewer-preserving PUT. Phase 5 delegates to this command; also invocable post-hoc for fixes made outside the pipeline. No worktree. |
 | `create-jira ["desc"] [figma-url] [swagger-url]` | Create a standards-compliant Jira issue: asks the type (**Task** / **Bug** / **Story**), mines the project's recent same-type issues for conventions (summary format, labels, priority, test-scenario style), detects the active sprint, drafts from a standard template with auto-sizing sections (Design Reference / API Contract / Screenshots appear only when their source is given), asks about unknown fields, then full draft preview + explicit approval before create. No worktree, no commits. |
 | `test` or `test [args]` | UI Bug Hunter  -  screenshot + tap + analyze on booted simulator via MCP (read `$HOME/.claude/commands/sim-test.md`). `/multi-agent:test` also resolves here via the `commands/multi-agent/test/SKILL.md` delegate. |
 | `test-dark-mode` · `test-accessibility` · `test-dynamic-type` · `test-screenshots [locale]` | Fixed-scenario aliases for the four parameterless / single-parameter `test` scenarios, so the tag autocompletes instead of having to be quoted. Each delegates to the same `sim-test.md` with its scenario pinned; behaviour is identical to the quoted form, which is not deprecated. |
@@ -130,7 +130,7 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 | Jetpack Compose task (Android) | `$HOME/.claude/multi-agent-refs/android-guide.md` |
 | Backend API task | `$HOME/.claude/multi-agent-refs/backend-guide.md` |
 | Web component task | `$HOME/.claude/multi-agent-refs/web-guide.md` |
-| Phase 1 or Phase 7 (knowledge) | `$HOME/.claude/multi-agent-refs/knowledge.md` |
+| Phase 1 or Phase 5 (knowledge) | `$HOME/.claude/multi-agent-refs/knowledge.md` |
 | Token lookup needed | `$HOME/.claude/multi-agent-refs/keychain.md` |
 | Audit tools (Phase 5/6) | `$HOME/.claude/multi-agent-refs/audit-guide.md` |
 | `test` | `$HOME/.claude/commands/sim-test.md` (colon-form `/multi-agent:test` uses the delegate at `commands/multi-agent/test/SKILL.md`) |
@@ -150,14 +150,14 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 - Multiple stacks -> load all relevant guides
 
 **Agent definitions** (used in Phase 1 and Phase 4):
-- `$HOME/.claude/agents/code-reviewer.md`  -  Phase 4 reviewer persona (`preferredModel: fable`; Phase 4 overrides Reviewer 3 to `sonnet`)
+- `$HOME/.claude/agents/code-reviewer.md`  -  Phase 3 reviewer persona (`preferredModel: fable`; Phase 4 overrides Reviewer 3 to `sonnet`)
 - `$HOME/.claude/agents/explorer.md`  -  Phase 1 codebase scan persona (`preferredModel: sonnet`  -  scan work, cost-efficient)
 - `$HOME/.claude/agents/ios-architect.md`  -  iOS architecture review (`preferredModel: fable`)
 - `$HOME/.claude/agents/android-architect.md`  -  Android architecture review (`preferredModel: fable`)
 - `$HOME/.claude/agents/backend-architect.md`  -  Backend/API architecture review (`preferredModel: fable`)
 - `$HOME/.claude/agents/security-auditor.md`  -  Security audit (`preferredModel: opus`)
 
-**Per-persona model routing:** Before each Agent dispatch, the orchestrator reads `preferredModel` from the persona file and exports `CLAUDE_CODE_SUBAGENT_MODEL` (Claude Code) / passes `--model` (Copilot CLI). Precedence: per-dispatch `PHASE_MODEL_OVERRIDE` > persona `preferredModel` > `fable` (falls back per `$HOME/.claude/multi-agent-refs/features/model-fallback.md`). Full contract: `skills/shared/core/multi-agent/SKILL.md#agent-dispatch--per-persona-model-routing-v610`.
+**Per-persona model routing:** Before each Agent dispatch, the orchestrator reads `preferredModel` from the persona file and exports `CLAUDE_CODE_SUBAGENT_MODEL` (Claude Code) / passes `--model` (Copilot CLI). Precedence: per-dispatch `PHASE_MODEL_OVERRIDE` > a matching `prefs.global.modelRouting` rule (v19.0.0+, consulted only when the phase named no model, and only inside the Anthropic ladder because subagent dispatch belongs to the host) > persona `preferredModel` > `fable` (falls back per `$HOME/.claude/multi-agent-refs/features/model-fallback.md`). Full contract: `skills/shared/core/multi-agent/SKILL.md#agent-dispatch--per-persona-model-routing-v610`.
 
 ---
 
@@ -229,7 +229,7 @@ Save to `prefs.projects[{project}].branches`.
 ### Step 2  -  Mode Selection
 ```
 Pipeline depth (same question Phase 0 Step 7.5 asks):
-  1. Full  (8 phases, Sonnet dev, parallel review + triage  -  CLI-aware reviewer set)
+  1. Full  (6 phases, Sonnet dev, parallel review + triage  -  CLI-aware reviewer set)
   2. Short (Init → Dev(Opus) → Review → Test → Commit → Report  -  no analysis/planning)
 Select [1/2]:
 ```
@@ -257,7 +257,7 @@ When called with `review`:
 1. Detect current branch and project from cwd (or ask)
 2. Get diff: `git diff HEAD` (unstaged + staged)
 3. If no diff, get diff against base branch: `git diff origin/{baseBranch}...HEAD`
-4. Launch Phase 4 review (parallel + Fable triage  -  3 reviewers on every host: Fable + Opus + Sonnet on Claude Code, GPT-5.4 + Opus + Sonnet on Copilot CLI) on the diff
+4. Launch Phase 3 review (parallel + Fable triage  -  3 reviewers on every host: Fable + Opus + Sonnet on Claude Code, GPT-5.4 + Opus + Sonnet on Copilot CLI) on the diff
 5. No worktree, no state file  -  lightweight one-shot review
 6. Print findings to terminal
 
@@ -281,7 +281,7 @@ Load `$HOME/.claude/multi-agent-refs/rules.md` for the full contract (Swift-spec
 
 ### TaskCreate ordering (strict)
 
-**All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied**  -  this binds the full interactive `/multi-agent` run (all 8 phases) exactly like every mode alias. The native widget renders tiles by creation order, not by phase number; out-of-order calls produce visually scrambled tile stacks. Register every tile in order, then flip status via TaskUpdate when a phase actually starts or short-circuits. Full contract: `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
+**All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied**  -  this binds the full interactive `/multi-agent` run (all 6 phases) exactly like every mode alias. The native widget renders tiles by creation order, not by phase number; out-of-order calls produce visually scrambled tile stacks. Register every tile in order, then flip status via TaskUpdate when a phase actually starts or short-circuits. Full contract: `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
 
 ---
 
@@ -294,8 +294,8 @@ Multi-Agent Tasks
 
 | ID | Project | Task | Branch | Phase | Status | Duration |
 |----|---------|------|--------|-------|--------|----------|
-| #1 | my-app | PROJ-12345 | feature/PROJ-12345-... | 3/7 Dev | in progress | 4m |
-| #2 | other-app | GH42 | feature/GH42-dark-mode | 6/7 Commit | complete | 12m |
+| #1 | my-app | PROJ-12345 | feature/PROJ-12345-... | 2/5 Dev | in progress | 4m |
+| #2 | other-app | GH42 | feature/GH42-dark-mode | 4/5 Commit | complete | 12m |
 
 Commands: kill #N | log #N | resume #N
 ```

package/pipeline/commands/multi-agent/analysis/SKILL.md

@@ -1,12 +1,12 @@
 ---
-description: "Standalone feature-spec analysis. Two profiles picked at intake: global (23-section development handoff, 8 of them in Lite mode) or corporate (IG/UC/FG requirements document with traceability matrices). Platform-agnostic concept layer with repo-driven convention extraction (Phase 1c) and per-platform Pass B render; stack selection is optional. Collects Figma / Swagger / Confluence / Jira / Standards (Confluence + Wiki + local file) / Firebase / repo inputs. Stops after emit - does not chain into a dev run. Use when a feature needs a written specification before any code."
-description-tr: "Bağımsız özellik-spesifikasyonu analizi. Girişte iki profil: global (23 bölümlük geliştirme dokümanı, Lite modda 8'i) veya kurumsal (izlenebilirlik matrisleriyle IG/UC/FG gereksinim dokümanı). Repo'dan konvansiyon çıkarımıyla (Faz 1c) platform-bağımsız kavram katmanı ve platform başına Pass B render; stack seçimi opsiyonel. Figma / Swagger / Confluence / Jira / Standartlar (Confluence + Wiki + yerel dosya) / Firebase / repo girdilerini toplar. Çıktıyı üretince durur - dev koşusuna zincirlenmez."
-argument-hint: "[\"<analysis-name>\"] [--lite | --full] [--no-cache] [--preview-conventions]"
+description: "Standalone feature-spec analysis. Two profiles picked at intake: global (23-section development handoff, evidence-trimmed) or corporate (IG/UC/FG requirements document with traceability matrices). Platform-agnostic concept layer with repo-driven convention extraction (Phase 1c) and per-platform Pass B render; stack selection is optional. Collects Figma / Swagger / Confluence / Jira / Standards (Confluence + Wiki + local file) / Firebase / repo inputs. Stops after emit - does not chain into a dev run. Use when a feature needs a written specification before any code."
+description-tr: "Bağımsız özellik-spesifikasyonu analizi. Girişte iki profil: global (23 bölümlük geliştirme dokümanı, kanıta göre budanır) veya kurumsal (izlenebilirlik matrisleriyle IG/UC/FG gereksinim dokümanı). Repo'dan konvansiyon çıkarımıyla (Faz 1c) platform-bağımsız kavram katmanı ve platform başına Pass B render; stack seçimi opsiyonel. Figma / Swagger / Confluence / Jira / Standartlar (Confluence + Wiki + yerel dosya) / Firebase / repo girdilerini toplar. Çıktıyı üretince durur - dev koşusuna zincirlenmez."
+argument-hint: "[\"<analysis-name>\"] [--no-cache] [--preview-conventions]"
 ---
 
 # multi-agent analysis - Feature Spec Analysis (v3)
 
-This command is **independent** from the orchestrator's Phase 1 analysis (which is a stack/findings detector inside `/multi-agent`). It produces a stakeholder-ready, platform-agnostic 23-section feature-spec document (or 7-section Lite mode) before any implementation starts. Each per-platform file is rendered by projecting concept-layer content onto repo-extracted conventions (Pass B).
+This command is **independent** from the orchestrator's Phase 1 analysis (which is a stack/findings detector inside `/multi-agent`). It produces a stakeholder-ready, platform-agnostic feature-spec document - up to 23 sections, trimmed to whatever the evidence supports - before any implementation starts. Each per-platform file is rendered by projecting concept-layer content onto repo-extracted conventions (Pass B).
 
 **Side-effect contract**: the command may write a local markdown file, post a Confluence page, or update a Jira description - but **never** creates branches, worktrees, commits, or PRs. It stops at the document.
 
@@ -28,20 +28,20 @@ Cite a decision as `Locked <n> (<short label>)` so the category is inferable.
 
 ## Profile
 
-Phase 0 Step 1b asks which analysis standard the document follows (Locked 32), and the answer selects the template. Both profiles read the same evidence: intake, fetching, repo evidence and convention extraction are shared, so the two cannot drift into two products.
+Phase 0 Step 1b asks which analysis standard the document follows (Locked 31), and the answer selects the template. Both profiles read the same evidence: intake, fetching, repo evidence and convention extraction are shared, so the two cannot drift into two products.
 
 | Profile | Template | Shape |
 |---|---|---|
 | `global` (default) | `analysis-template.md` | Development handoff, 23 sections. Business rules with Gherkin acceptance criteria, architecture plan, files to add, test plan. Zero-evidence sections drop (Locked 2). |
-| `corporate` | `analysis-template-corporate.md` | Requirements document. `IG -> UC -> FG` spine with three traceability matrices, current and target state with impact analysis, then Technical Analysis and Development Analysis. The Part A backbone always renders, carrying `N/A` or `EKLENECEK` (Locked 33). |
+| `corporate` | `analysis-template-corporate.md` | Requirements document. `IG -> UC -> FG` spine with three traceability matrices, current and target state with impact analysis, then Technical Analysis and Development Analysis. The Part A backbone always renders, carrying `N/A` or `EKLENECEK` (Locked 32). |
 
 One run emits one profile. A missing input never blocks either profile: the gap is written as `EKLENECEK` and raised as a Section 20 open question rather than halting the run.
 
-**Stack is optional** (Locked 35). When no platform is selected the run still completes: everything that does not need a target repository renders in full, and only the development layer plus the Pass B projection are skipped, with a Section 20 row recording why. The output is a single file at `~/Desktop/multiAgentAnalysis/<feature-name>/<feature>.md` instead of one per repo: without a repo there is no working tree for the usual `analysis/` path to be relative to, and the current working directory is never written to. The Phase 3.5 picker shows the resolved path and accepts an override.
+**Stack is optional** (Locked 34). When no platform is selected the run still completes: everything that does not need a target repository renders in full, and only the development layer plus the Pass B projection are skipped, with a Section 20 row recording why. The output is a single file at `~/Desktop/multiAgentAnalysis/<feature-name>/<feature>.md` instead of one per repo: without a repo there is no working tree for the usual `analysis/` path to be relative to, and the current working directory is never written to. The Phase 3.5 picker shows the resolved path and accepts an override.
 
 ## Template
 
-v3 template at `$HOME/.claude/multi-agent-refs/analysis-template.md`. Full mode renders up to 23 main sections + footer, minus any dropped by the omission table. The analysis doc is a development handoff, so low-signal sections are default-drop even in Full: **19 Alternatives** (render only for a real 2+-option architectural decision), **22 Glossary** (render only on request or >5 unfamiliar domain terms), and **18 Rollout** (compact checklist only, dropped when the pipeline's own commit/PR/rollout phase covers it). Lite mode renders 7 main sections (1 Summary, 2 Goals + Non-Goals, 4 User Stories, 9 API Contracts, 13 Architecture, 14 Files to Add, 21 References) plus optional 23 Changelog. Section omission rule (Locked 2): zero-evidence and default-drop sections omit entirely; numbering re-flows to stay sequential `1..N` over the rendered set.
+v3 template at `$HOME/.claude/multi-agent-refs/analysis-template.md`. Full mode renders up to 23 main sections + footer, minus any dropped by the omission table. The analysis doc is a development handoff, so low-signal sections are default-drop even in Full: **19 Alternatives** (render only for a real 2+-option architectural decision), **22 Glossary** (render only on request or >5 unfamiliar domain terms), and **18 Rollout** (compact checklist only, dropped when the pipeline's own commit/PR/rollout phase covers it). There is no second mode: Lite was removed in v19.0.0 because it picked a fixed list of sections while this rule picks them from evidence, and the two disagreed in both directions - a small feature with rich business rules lost Section 15, a feature with no API contract kept Section 9. Section omission rule (Locked 2): zero-evidence and default-drop sections omit entirely; numbering re-flows to stay sequential `1..N` over the rendered set.
 
 Numbering is plain Arabic numerals: `## 1. Geliştirme Özeti` / `## 1. Summary`, `## 2. Hedefler ve Karşı Hedefler` / `## 2. Goals and Non-Goals`. No special section characters; the section sign codepoint (U+00A7) is banned by `feedback_no-section-sign`.
 
@@ -59,11 +59,11 @@ Full contract: `$HOME/.claude/multi-agent-refs/analysis/evidence.md`. Fetches ev
 
 ### Phase 2, 2a, 2b - Two-pass synthesis
 
-Full contract: `$HOME/.claude/multi-agent-refs/analysis/synthesis.md`. Pass A builds the platform-agnostic concept layer; Phase 2a previews the resolved conventions for approval (Locked 26); Pass B projects each concept onto the selected platform with a footnote per filled cell (Locked 24).
+Full contract: `$HOME/.claude/multi-agent-refs/analysis/synthesis.md`. Pass A builds the platform-agnostic concept layer; Phase 2a previews the resolved conventions for approval (Locked 25); Pass B projects each concept onto the selected platform with a footnote per filled cell (Locked 24).
 
 ### Phases 3, 3.2, 3.3, 3.5, 4, 5 - Render, review, publish, report
 
-Full contract: `$HOME/.claude/multi-agent-refs/analysis/render.md`. Renders one markdown file per platform, runs the **required** `ai-common-toolkit:humanizer` pass, gates on `validate-analysis-doc.mjs` and on the `build-references.mjs --check` references coverage gate (Locked 34), asks for the output destination, dispatches to Local / Confluence / Jira (a Jira issue receives a comment unless the user explicitly asks for the description, which is never overwritten without a backup and a confirmation), then reports and stops. The humanizer pass and the validator are required in every mode; a document that skipped either is not shippable.
+Full contract: `$HOME/.claude/multi-agent-refs/analysis/render.md`. Renders one markdown file per platform, runs the **required** `ai-common-toolkit:humanizer` pass, gates on `validate-analysis-doc.mjs` and on the `build-references.mjs --check` references coverage gate (Locked 33), asks for the output destination, dispatches to Local / Confluence / Jira (a Jira issue receives a comment unless the user explicitly asks for the description, which is never overwritten without a backup and a confirmation), then reports and stops. The humanizer pass and the validator are required in every mode; a document that skipped either is not shippable.
 
 ### Resume contract
 
@@ -131,7 +131,7 @@ When `phase == "cancelled_at_pass_b_preview"`:
 - The minimum possible output (per per-platform file) is `1. Scope` + `7. Development Plan` (both always-present).
 - If Confluence or Jira POST returns 401 / 403 during Phase 4, surface the error and offer Local fallback (the local drafts in `/tmp/` are still on disk; copying them into the repo working tree is always available).
 - The `analysis/` directory is not in `.gitignore`; the user can `git add analysis/` manually. No auto-commit.
-- **Per-platform file naming**: `analysis/<feature>-<platform>.md`. The `<platform>` slug is lowercase, one of `ios | android | web | backend` for a repo-backed run, or `mobile | web` for the channels a repo-less run derives from its evidence (Locked 35). `web` is the pre-`web` spelling and is still read back for older state and documents. The `<feature>` slug preserves the user's feature name with whitespace replaced by `-` (e.g. `User Profile` -> `UserProfile` or `Item-Status` depending on input shape; the renderer trims and de-duplicates dashes).
+- **Per-platform file naming**: `analysis/<feature>-<platform>.md`. The `<platform>` slug is lowercase, one of `ios | android | web | backend` for a repo-backed run, or `mobile | web` for the channels a repo-less run derives from its evidence (Locked 34). `web` is the pre-`web` spelling and is still read back for older state and documents. The `<feature>` slug preserves the user's feature name with whitespace replaced by `-` (e.g. `User Profile` -> `UserProfile` or `Item-Status` depending on input shape; the renderer trims and de-duplicates dashes).
 - **Standards binding (the Standards question)**: When `evidence.standards[]` is non-empty, every decision in Section 13 (Architecture Plan, corporate Section 17) must cite the binding source in its 13.7 Standards-binding table. The renderer enforces this by failing render if any architectural decision has no `cite:` reference; the user is prompted to either tighten the source or add a Risk row acknowledging the missing citation.
 - **Firebase ingestion (the Firebase question)**: Console URLs are never fetched (auth-gated). Only `:names` and `:schema` inputs feed `evidence.firebase[]`. Section 11 Analytics (corporate Section 13) emits per-platform snippets but the events table itself is shared across all per-platform files (the rules / event vocabulary is one product invariant).
 - **Wiki access fallback chain**: Phase 1 `wiki` fetcher tries (a) `git clone .wiki.git`, (b) `gh api repos/.../contents/<file>.md`, (c) raw `WebFetch` of the page URL. Only after all three fail does the entry land in `fetchErrors[]`.
@@ -153,7 +153,7 @@ Two channels run in parallel at every phase boundary:
 ```bash
 # Phase 0, very first shell call (every CLI):
 bash $HOME/.claude/scripts/phase-tracker.sh init "$TASK_ID"
-for p in "0:Init" "1:Analysis" "2:Planning" "4:Review" "6:Commit" "7:Report"; do
+for p in "0:Init" "1:Plan" "3:Review" "4:Commit" "5:Report"; do
   bash $HOME/.claude/scripts/phase-tracker.sh add "${p%%:*}" "${p#*:}"
 done
 bash $HOME/.claude/scripts/phase-tracker.sh update 0 in_progress
@@ -173,7 +173,7 @@ In Claude Code the agent MUST also drive the native TaskList widget so the user
 
 ```text
 # Register one tile per phase, capture the taskId, persist it:
-for each phase in 0:Init, 1:Analysis, 2:Planning, 4:Review, 6:Commit, 7:Report:
+for each phase in 0:Init, 1:Plan, 3:Review, 4:Commit, 5:Report:
   TaskCreate({ subject: "Phase <N>: <Name>", activeForm: "<doing-form>" })
     -> returns taskId
   bash $HOME/.claude/scripts/phase-tracker.sh meta <N> tasklist_id "<taskId>"
@@ -190,11 +190,11 @@ TaskUpdate({ taskId: <saved>, status: "completed" })
 bash $HOME/.claude/scripts/phase-tracker.sh update <N> completed
 ```
 
-`analysis` mode does NOT TaskCreate phases 3/5  -  those are not part of the `analysis` phase set (`0:Init 1:Analysis 2:Planning 4:Review 6:Commit 7:Report`). Only register tiles for the active set.
+`analysis` mode does NOT TaskCreate phases 2  -  those are not part of the `analysis` phase set (`0:Init 1:Plan 3:Review 4:Commit 5:Report`). Only register tiles for the active set.
 
 #### TaskCreate ordering (strict)
 
-**All TaskCreate calls in a batch fire in strict phase-number order BEFORE any TaskUpdate is applied.** For `analysis` that means: Phase 0 → Phase 1 → Phase 2 → Phase 4 → Phase 6 → Phase 7. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks. Full ordering contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
+**All TaskCreate calls in a batch fire in strict phase-number order BEFORE any TaskUpdate is applied.** For `analysis` that means: Phase 0 → Phase 1 → Phase 3 → Phase 4 → Phase 5. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks. Full ordering contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
 
 ### Visual channel  -  Copilot CLI / plain shell
 

package/pipeline/commands/multi-agent/analysis-resolve/SKILL.md

@@ -19,7 +19,7 @@ Companion command to `/multi-agent:analysis`. Takes an `analysis/<feature>-<plat
 - **Locked 6 (no auto-commit).** The command rewrites the doc file(s) but never runs `git add` or `git commit`.
 - **Locked 7 (humanizer punctuation).** Every fragment this command writes into the doc uses ASCII punctuation only: no em-dash (U+2014), en-dash (U+2013), ellipsis (U+2026), curly quotes, or section sign. Diacritics are preserved verbatim (Turkish letters stay as-is; never ASCII-fold prose). Run the verification grep from `analysis.md` Phase 3 step 3 after the final save.
 - **Locked 24 (Pass B footnote).** When a resolution overrides a convention cell in Section 13 (or any per-platform projection), the cell's footnote is rewritten to `^[user-override: resolved via analysis-resolve <date>]`.
-- **Locked 30 (no MCP outside analysis phase).** This command makes NO Figma MCP calls, no `api.figma.com` requests, no `figma.com/design/...` fetches. A row that genuinely needs new design information gets only `Defer` plus a printed recommendation to re-run `/multi-agent:analysis` for that input. Repo reads and `~/.claude/lib/extract-conventions.sh` re-runs are allowed (they are local evidence, not design fetches).
+- **Locked 29 (no MCP outside analysis phase).** This command makes NO Figma MCP calls, no `api.figma.com` requests, no `figma.com/design/...` fetches. A row that genuinely needs new design information gets only `Defer` plus a printed recommendation to re-run `/multi-agent:analysis` for that input. Repo reads and `~/.claude/lib/extract-conventions.sh` re-runs are allowed (they are local evidence, not design fetches).
 
 ## Engine
 
@@ -61,6 +61,6 @@ Inherited decisions: `$HOME/.claude/multi-agent-refs/analysis/locked.md`.
 
 ## Notes
 
-- This command is downstream-safe: it edits only the analysis doc, so the Locked 30 contract (analysis doc as the sole design source for Phase 2+) is strengthened, not weakened - dev phases consume a doc with fewer open holes.
+- This command is downstream-safe: it edits only the analysis doc, so the Locked 29 contract (analysis doc as the sole design source for Phase 2+) is strengthened, not weakened - dev phases consume a doc with fewer open holes.
 - The resolver is idempotent over `Karar verildi / Decided` rows: re-running skips them.
 - When the session no longer holds `state.analysisSpec`, everything still works: evidence candidates fall back to what the doc itself cites, and repo candidates come from the Phase 1 subagent.

package/pipeline/commands/multi-agent/autopilot/SKILL.md

@@ -17,9 +17,9 @@ Run the task end-to-end with no confirmations.
 | Phase | Normal | Autopilot |
 |-----|--------|-----------|
 | Phase 2 (Plan Approval Gate) | Clarification (max 2 rounds) + approval loop  -  user confirms / cancels / sends free text | **Gate skipped**  -  log the plan, jump straight to Phase 3 (autopilot contract: zero interaction) |
-| Phase 5 (Test) | "Want to test?" → wait | Skip → Phase 6 |
-| Phase 6 (Commit) | "Commit?" → wait | Auto-commit + push |
-| Phase 6 (PR) | "Open PR?" → wait | Auto-create PR |
+| Phase 5 (Test) | "Want to test?" → wait | Skip → Phase 4 |
+| Phase 4 (Commit) | "Commit?" → wait | Auto-commit + push |
+| Phase 4 (PR) | "Open PR?" → wait | Auto-create PR |
 
 ## What is NEVER skipped
 
@@ -67,7 +67,7 @@ Two channels run in parallel at every phase boundary:
 ```bash
 # Phase 0, very first shell call (every CLI):
 bash $HOME/.claude/scripts/phase-tracker.sh init "$TASK_ID"
-for p in "0:Init" "1:Analysis" "2:Planning" "3:Dev" "4:Review" "6:Commit" "7:Report"; do
+for p in "0:Init" "1:Plan" "2:Dev" "3:Review" "4:Commit" "5:Report"; do
   bash $HOME/.claude/scripts/phase-tracker.sh add "${p%%:*}" "${p#*:}"
 done
 bash $HOME/.claude/scripts/phase-tracker.sh update 0 in_progress
@@ -87,7 +87,7 @@ In Claude Code the agent MUST also drive the native TaskList widget so the user
 
 ```text
 # Register one tile per phase, capture the taskId, persist it:
-for each phase in 0:Init, 1:Analysis, 2:Planning, 3:Dev, 4:Review, 6:Commit, 7:Report:
+for each phase in 0:Init, 1:Plan, 2:Dev, 3:Review, 4:Commit, 5:Report:
   TaskCreate({ subject: "Phase <N>: <Name>", activeForm: "<doing-form>" })
     -> returns taskId
   bash $HOME/.claude/scripts/phase-tracker.sh meta <N> tasklist_id "<taskId>"
@@ -104,11 +104,11 @@ TaskUpdate({ taskId: <saved>, status: "completed" })
 bash $HOME/.claude/scripts/phase-tracker.sh update <N> completed
 ```
 
-`autopilot` mode does NOT TaskCreate phases 5  -  those are not part of the `autopilot` phase set (`0:Init 1:Analysis 2:Planning 3:Dev 4:Review 6:Commit 7:Report`). Only register tiles for the active set.
+`autopilot` mode TaskCreates all 6 phases (no phase is skipped).
 
 #### TaskCreate ordering (strict)
 
-**All TaskCreate calls in a batch fire in strict phase-number order BEFORE any TaskUpdate is applied.** For `autopilot` that means: Phase 0 → Phase 1 → Phase 2 → Phase 3 → Phase 4 → Phase 6 → Phase 7. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks. Full ordering contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
+**All TaskCreate calls in a batch fire in strict phase-number order BEFORE any TaskUpdate is applied.** For `autopilot` that means: Phase 0 → Phase 1 → Phase 2 → Phase 3 → Phase 4 → Phase 5. The native widget renders by creation order, not by phase number  -  out-of-order calls produce visually scrambled tile stacks. Full ordering contract in `$HOME/.claude/multi-agent-refs/tracker-contract.md` section "TaskCreate ordering (strict)".
 
 ### Visual channel  -  Copilot CLI / plain shell
 

package/pipeline/commands/multi-agent/channels/SKILL.md

@@ -1,13 +1,13 @@
 ---
-description: "Multi-channel reporter  -  Jira/Confluence/Wiki/PR description/Board status. Multi-select channels + content, humanizer pass, reviewer-preserving Bitbucket PR PUT, GitHub Projects v2 board status move. Phase 7 delegates to this skill; users can invoke post-hoc by Jira ID / PR URL / branch."
-description-tr: "Çok kanallı raporlayıcı - Jira/Confluence/Wiki/PR açıklaması/Board durumu. Çoklu kanal + içerik seçimi, humanizer geçişi, reviewer'ı koruyan Bitbucket PR PUT, GitHub Projects v2 board durum taşıma. Faz 7 bu skill'e delege eder; Jira ID / PR URL / branch ile sonradan da çağrılabilir."
+description: "Multi-channel reporter  -  Jira/Confluence/Wiki/PR description/Board status. Multi-select channels + content, humanizer pass, reviewer-preserving Bitbucket PR PUT, GitHub Projects v2 board status move. Phase 5 delegates to this skill; users can invoke post-hoc by Jira ID / PR URL / branch."
+description-tr: "Çok kanallı raporlayıcı - Jira/Confluence/Wiki/PR açıklaması/Board durumu. Çoklu kanal + içerik seçimi, humanizer geçişi, reviewer'ı koruyan Bitbucket PR PUT, GitHub Projects v2 board durum taşıma. Faz 5 bu skill'e delege eder; Jira ID / PR URL / branch ile sonradan da çağrılabilir."
 argument-hint: '<Jira-id | PR-url | #N | Jira-url> [--channels pr,jira,confluence,wiki,board] [--content normal,technical,test,auto-diff,note] [--message "..."] [--message-file path] [--board-status <key>] [--dry-run] [--append] [--ready]'
 allowed-tools: Read, Write, Edit, Bash, Grep, WebFetch, AskUserQuestion
 ---
 
 # /multi-agent channels  -  Multi-Channel Reporter
 
-> **TLDR**  -  Single entry point for posting task reports to external channels. Supports Jira, Confluence, Wiki (component-only), and PR description updates. Multi-select channels × multi-select content sources. Phase 7 of the pipeline delegates to this command; users can also invoke it post-hoc by Jira ID / PR URL / branch.
+> **TLDR**  -  Single entry point for posting task reports to external channels. Supports Jira, Confluence, Wiki (component-only), and PR description updates. Multi-select channels × multi-select content sources. Phase 5 of the pipeline delegates to this command; users can also invoke it post-hoc by Jira ID / PR URL / branch.
 >
 > Replaces the old `enrich` command  -  all enrich capabilities (diff auto-summarize, manual mode, reviewer-preserving Bitbucket PR PUT) preserved and extended with two additional channels.
 
@@ -135,7 +135,7 @@ Then 3b renders:
 - "Wiki" unselectable unless `state.taskType === "component"` AND `figmaConfig.wiki.enabled === true`. If greyed, show reason: `"(no figma-config or taskType != component)"`.
 - "Board" unselectable unless `figmaConfig.board.enabled === true` AND `figmaConfig.board.provider === "github-projects-v2"` AND `figmaConfig.github.projectV2Id` set. If greyed, show reason: `"(no figma-config.board or projectV2Id missing)"`. Default target column: `inReview`.
 - "Normal analiz" + "Test senaryoları" unselectable if no pipeline log found. Reason: `"(no pipeline log for PROJ-12345)"`.
-- "Teknik analiz" unselectable if no Phase 2 planning log AND no PR diff available. Reason: `"(no technical source  -  need Phase 2 plan or PR diff)"`.
+- "Teknik analiz" unselectable if no Phase 1 planning log AND no PR diff available. Reason: `"(no technical source  -  need Phase 1 plan or PR diff)"`.
 - "Auto-diff" unselectable if no PR found. Reason: `"(no PR linked to this target)"`.
 - "Manuel not" always available.
 - "Cost özeti" unselectable if `phase-tracker.sh cost total` prints `-` (no priced token tallies; there is no `status` action) AND no `otel-spans.jsonl` exists for the task. Reason: `"(no tracker data  -  set MULTI_AGENT_OTEL_SPANS=1 or enable token tracking)"`.
@@ -152,7 +152,7 @@ Non-interactive in three cases  -  menu skipped entirely, flag values or prefs u
 | Mode | Behavior |
 |---|---|
 | `--channels X,Y` + `--content A,B` flags | Exact flag values, no menu. |
-| `autopilot` (Phase 7 delegate) | Reads `prefs.global.reportChannels` + `prefs.global.reportContent`  -  per Phase 7 autopilot-pause contract, Phase 7 STILL pauses before calling channels but pre-fills menu from prefs. Post-hoc `/channels` in autopilot mode uses prefs directly. |
+| `autopilot` (Phase 5 delegate) | Reads `prefs.global.reportChannels` + `prefs.global.reportContent`  -  per Phase 5 autopilot-pause contract, Phase 5 STILL pauses before calling channels but pre-fills menu from prefs. Post-hoc `/channels` in autopilot mode uses prefs directly. |
 | `--dry-run` | Runs menu, generates output, prints to stdout, DOES NOT post. |
 
 ### Step 5  -  Generator
@@ -178,7 +178,7 @@ lead reads before deciding how wide to test.
 | Content option | Generated section |
 |---|---|
 | Normal analiz | `### Analysis`  -  impact summary from Phase 1, risks from Phase 4 (pipeline-log source, high-level only) |
-| Teknik analiz | `### Technical Details`  -  Changes (what/why per file group), Architecture (structural decisions, pattern changes), Dependencies (new imports/frameworks/packages). Source: Phase 2 planning + Phase 3 dev log + `git diff --stat`. **PR and Confluence only** - never rendered into a Jira comment. |
+| Teknik analiz | `### Technical Details`  -  Changes (what/why per file group), Architecture (structural decisions, pattern changes), Dependencies (new imports/frameworks/packages). Source: Phase 1 planning + Phase 2 dev log + `git diff --stat`. **PR and Confluence only** - never rendered into a Jira comment. |
 | Test senaryoları | `### Test Scenarios`  -  precondition / steps / expected table (4-8 rows), user perspective |
 | Auto-diff | Old enrich Output Template verbatim  -  Root Cause / Solution / Changed Files / Test Scenarios |
 | Manuel not | `### Notes`  -  user-provided paragraph, or LLM-split into subsections if `--message` is plain text and long |
@@ -200,9 +200,9 @@ source, not that the section may be reordered or renamed.
 
 ### Technical Details               ← if "Teknik analiz" selected
 #### Changes
-{Per changed-file-group, what changed + why  -  from Phase 3 dev log}
+{Per changed-file-group, what changed + why  -  from Phase 2 dev log}
 #### Architecture
-{Structural decisions, pattern changes, new file layouts  -  from Phase 2 plan}
+{Structural decisions, pattern changes, new file layouts  -  from Phase 1 plan}
 #### Dependencies
 {New imports / frameworks / packages  -  from git diff --stat, or "None"}
 
@@ -353,7 +353,7 @@ Applying the Jira table to the PR body is the recurring failure of this step: it
 {body}
 ```
 
-Secondary artifacts ride along as one-line intents at the bottom of the preview: Wiki page list, wiki → Jira triad comment (when Wiki is selected and the triad is active per `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`), Board status move (`{from} → {to}`), GitHub issue comment + Progress-flag sync (Phase 7 Step 1.5  -  same gate, see `$HOME/.claude/multi-agent-refs/phases/phase-7-report.md`).
+Secondary artifacts ride along as one-line intents at the bottom of the preview: Wiki page list, wiki → Jira triad comment (when Wiki is selected and the triad is active per `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`), Board status move (`{from} → {to}`), GitHub issue comment + Progress-flag sync (Phase 5 Step 1.5  -  same gate, see `$HOME/.claude/multi-agent-refs/phases/phase-5-report.md`).
 
 **Then a single AskUserQuestion** (`question`/`label`/`description` in `outputLanguage`; `header` English):
 
@@ -489,18 +489,18 @@ Persist selections to `prefs.global.reportChannels` + `prefs.global.reportConten
 | Jira token missing/expired | Token Save Flow inline; skip on user-skip |
 | Wiki preconditions not met | Case B menu per `$HOME/.claude/multi-agent-refs/wiki-capture.md` |
 
-## Phase 7 delegation contract
+## Phase 5 delegation contract
 
-Phase 7 invokes this command internally instead of running its own inline Jira/Confluence/Wiki logic. Responsibilities split:
+Phase 5 invokes this command internally instead of running its own inline Jira/Confluence/Wiki logic. Responsibilities split:
 
 | Who | What |
 |---|---|
-| Phase 7 | Progress tracker (sub-steps 1-3), agent-log finalization (step 4), knowledge+memory capture (step 5), telemetry emission |
+| Phase 5 | Progress tracker (sub-steps 1-3), agent-log finalization (step 4), knowledge+memory capture (step 5), telemetry emission |
 | `channels` | All external delivery: PR description update, Jira comment, Confluence page, Wiki pages |
 
-Phase 7 passes a runtime state bundle: `{jiraId, prUrl, remoteType, taskType, figmaConfig, agentState, pipelineLogPath}`. `channels` reads these directly, skips target-resolution Step 1.
+Phase 5 passes a runtime state bundle: `{jiraId, prUrl, remoteType, taskType, figmaConfig, agentState, pipelineLogPath}`. `channels` reads these directly, skips target-resolution Step 1.
 
-**Autopilot contract:** Phase 7 ALWAYS pauses at the channels menu (breaks generic autopilot zero-interaction). 30-min timeout → session ends cleanly, task resumable via `/multi-agent:resume`. See `$HOME/.claude/multi-agent-refs/phases/modes.md` for full contract. The Step 6 body preview + approval gate follows the same split: interactive runs approve the composed bodies before dispatch; autopilot posts directly after the menu resolves.
+**Autopilot contract:** Phase 5 ALWAYS pauses at the channels menu (breaks generic autopilot zero-interaction). 30-min timeout → session ends cleanly, task resumable via `/multi-agent:resume`. See `$HOME/.claude/multi-agent-refs/phases/modes.md` for full contract. The Step 6 body preview + approval gate follows the same split: interactive runs approve the composed bodies before dispatch; autopilot posts directly after the menu resolves.
 
 ## Cross-CLI parity
 
@@ -515,7 +515,7 @@ Both installations read the same source file (`$HOME/.claude/commands/multi-agen
 
 Prompts MUST be byte-identical. `smoke-cross-cli-behavior.sh` asserts this  -  spacing, brackets, numbering, log-line format.
 
-Progress emission on Copilot (no native TaskCreate UI): `bash ~/.copilot/scripts/phase-tracker.sh sub 7 <N> "<step>" <status>`  -  same shape as Phase 7.
+Progress emission on Copilot (no native TaskCreate UI): `bash ~/.copilot/scripts/phase-tracker.sh sub 5 <N> "<step>" <status>`  -  same shape as Phase 5.
 
 ## Examples
 

package/pipeline/commands/multi-agent/diff-explain/SKILL.md

@@ -1,19 +1,19 @@
 ---
-description: "Map Phase 4 triage findings to branch diff lines. Read-only post-hoc command, used after review to answer 'which finding lines up with which code change'. Use when a review finding has to be traced to the exact lines that caused it."
-description-tr: "Faz 4 triyaj bulgularını branch diff satırlarına eşler. Review sonrası kullanılan salt-okunur komut: hangi bulgu hangi kod değişikliğine denk geliyor sorusunu cevaplar."
+description: "Map Phase 3 triage findings to branch diff lines. Read-only post-hoc command, used after review to answer 'which finding lines up with which code change'. Use when a review finding has to be traced to the exact lines that caused it."
+description-tr: "Faz 3 triyaj bulgularını branch diff satırlarına eşler. Review sonrası kullanılan salt-okunur komut: hangi bulgu hangi kod değişikliğine denk geliyor sorusunu cevaplar."
 argument-hint: "[#task-id | --triage <path> | --state <path>] [--branch <name>] [--base <name>]"
 ---
 
 # multi-agent diff-explain  -  Phase 4 Triage to Diff Bridge
 
-Maps the Phase 4 triage output (`accepted` / `deferred` / `rejected`) onto the branch's `git diff`. Every finding lands inline with the matching file / line hunk.
+Maps the Phase 3 triage output (`accepted` / `deferred` / `rejected`) onto the branch's `git diff`. Every finding lands inline with the matching file / line hunk.
 
 **This command has no side effects.** It runs `git diff` and prints markdown.
 
 ## When to use it
 
 - Between Phase 4 and Phase 5/6: answers "5 findings  -  which one belongs to which file?"
-- Phase 7 reporting: a "review summary with code context" block to embed in the Wiki / Confluence output.
+- Phase 5 reporting: a "review summary with code context" block to embed in the Wiki / Confluence output.
 - Post-hoc audit: for a closed PR, a "what did review flag, and how did the code change" diff.
 
 ## Steps
@@ -39,7 +39,7 @@ Maps the Phase 4 triage output (`accepted` / `deferred` / `rejected`) onto the b
 
 4. **Annotate the output** (optional):
    - Whether every blocking finding actually got touched (Phase 3 fix-coverage check)
-   - Whether every deferred finding is on the Phase 7 follow-up list
+   - Whether every deferred finding is on the Phase 5 follow-up list
 
 ## Output template
 
@@ -57,7 +57,7 @@ Maps the Phase 4 triage output (`accepted` / `deferred` / `rejected`) onto the b
 > Race condition: order total computed twice without lock
 **Fix:** Compute total once inside the existing transaction block
 ```diff
-@@ -98,5 +98,7 @@ ...
+ -98,5 +98,7  ...
    const total = sum(items);
 +  const total2 = sum(items);  // duplicate
    await chargeCard(total);

package/pipeline/commands/multi-agent/garbage-collect/SKILL.md

@@ -120,7 +120,7 @@ deletes nothing until you confirm.
    | `unattributed` | a worktree with no run state. **Never removed, whatever the flags.** `.worktrees/` is not exclusively ours, and nothing distinguishes a hand-made worktree from a pipeline one whose log was pruned. Report the list and its size; the user decides |
 
    Three rules hold with or without `--yes`, and they are why this is safe to
-   offer: a run waiting on you (open PR, Phase 6/7, `awaiting_input`) is never
+   offer: a run waiting on you (open PR, Phase 4/5, `awaiting_input`) is never
    touched; a path outside `<repo>/.worktrees/` is never removed, which matters
    because four state files on the measured machine record the REPO ROOT as
    their `worktreePath`; and uncommitted work is stashed rather than lost.

package/pipeline/commands/multi-agent/graph/SKILL.md

@@ -10,7 +10,7 @@ argument-hint: "[build | refresh | ask \"<question>\" | affected \"<symbol>\" |
 
 A code graph is a map of what this repo declares and what refers to what, built by
 regex over comment-stripped source. It exists so Phase 1 can narrow its Explore
-fan-out and Phase 7 can refresh `~/.claude/knowledge/<project>/` without an LLM
+fan-out and Phase 5 can refresh `~/.claude/knowledge/<project>/` without an LLM
 pass. It answers "where does this live" and "what depends on this". It does not
 answer "what calls this at runtime": call graphs and type resolution need a real
 parser, which would be an npm runtime dependency, and ADR-0004 forbids one.