@mmerterden/multi-agent-pipeline 8.6.0

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

@@ -0,0 +1,116 @@
+---
+description: "Launch any task in autopilot mode: skips every confirmation, runs end-to-end autonomously."
+argument-hint: '"task" — issue URL, Jira ID, free-text, or #id (for resume)'
+---
+
+# multi-agent autopilot — Autonomous Pipeline
+
+**Input**: $ARGUMENTS
+
+> **Language (read FIRST)**: Before any status output, read `prefs.global.outputLanguage` and render every conversational line in it. `AskUserQuestion` and external payloads stay English. Full contract: `refs/rules.md` "Language Application".
+
+Run the task end-to-end with no confirmations.
+
+## What changes
+
+| 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 |
+
+## What is NEVER skipped
+
+- 🔴 **Review-blocking finding** → auto fix + rebuild (max 3 retries)
+- 💥 **Build failure** → auto fix + rebuild (max 3 retries, then pause)
+- ⚠️ **Kill / Purge** → always asks for confirmation (destructive)
+
+## Usage
+
+```
+# GitHub Issue
+/multi-agent:autopilot https://github.com/.../issues/316
+
+# Jira ID
+/multi-agent:autopilot {JIRA-KEY}-12345
+
+# Free text
+/multi-agent:autopilot LoginView dark mode fix
+
+# Resume a stopped task in autopilot
+/multi-agent:autopilot resume #3
+```
+
+## Steps
+
+1. **Parse input** — standard multi-agent input formats
+2. **Set the autopilot flag** — write `"autopilot": true` to `agent-state.json`
+3. **Launch the multi-agent pipeline** — every confirmation is skipped
+4. **On error** — after 3 failed retries, pause and ask the user
+## Required: Phase Tracker Contract
+
+**The phase tracker is mandatory** — the agent cannot skip it. Full spec: [`refs/tracker-contract.md`](./refs/tracker-contract.md).
+
+> **Autopilot mode:** user confirmations are skipped. The tracker is still mandatory — autopilot agent calls cannot skip it; skipping breaks `smoke-tracker-contract.sh`.
+
+Two channels run in parallel at every phase boundary:
+
+1. **State channel** (every CLI, identical): `phase-tracker.sh` writes to `tracker-state.json`. Drives `:resume`, `:log`, `:status`.
+2. **Visual channel** (CLI-specific): native widget on Claude Code, ANSI render on every other CLI. Without it the user sees no phase progress.
+
+```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" "5:Test" "6:Commit" "7:Report"; do
+  bash $HOME/.claude/scripts/phase-tracker.sh add "${p%%:*}" "${p#*:}"
+done
+bash $HOME/.claude/scripts/phase-tracker.sh update 0 in_progress
+
+# Every phase boundary (every CLI):
+bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress|completed|failed|skipped
+
+# After every LLM call (every CLI):
+bash $HOME/.claude/scripts/phase-tracker.sh tokens <N> <in> <out>
+```
+
+### Visual channel — Claude Code (native TaskList widget, required)
+
+In Claude Code the agent MUST also drive the native TaskList widget so the user sees a sticky phase tile stack — this is the only progress signal Claude Code surfaces. Skipping these calls is the #1 source of "I don't see any phases" complaints.
+
+**TaskCreate ordering (strict)**: All TaskCreate calls fire in strict phase-number order BEFORE any TaskUpdate is applied. The native widget renders by creation order, not by phase number — out-of-order calls produce visually scrambled tile stacks (e.g. `1 ✓ · 2 ✓ · 4 ✓ · 0 ▶ · 3 ☐`) even when the underlying state is correct. Pre-marking phases as completed/skipped before Phase 0 starts is FORBIDDEN — register the tile in order, then flip status via TaskUpdate when the phase actually short-circuits. Full contract in `refs/tracker-contract.md` § "TaskCreate ordering (strict)".
+
+```text
+# Phase 0 startup — register one tile per phase (0..N), capture the taskId, persist it:
+for each phase in 0:Init, 1:Analysis, 2:Planning, 3:Dev, 4:Review, 5:Test, 6:Commit, 7:Report:
+  TaskCreate({ subject: "Phase <N>: <Name>", activeForm: "<doing-form>" })
+    -> returns taskId
+  bash $HOME/.claude/scripts/phase-tracker.sh meta <N> tasklist_id "<taskId>"
+
+# Phase entry — flip the tile to in_progress alongside the state update:
+TaskUpdate({ taskId: <saved>, status: "in_progress" })
+bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress
+
+# Active sub-step inside a phase — update activeForm so the spinner header reflects what's happening now:
+TaskUpdate({ taskId: <saved>, activeForm: "Editing TopBarView.swift" })
+
+# Phase exit — flip to completed/failed/skipped on both channels:
+TaskUpdate({ taskId: <saved>, status: "completed" })
+bash $HOME/.claude/scripts/phase-tracker.sh update <N> completed
+```
+
+`autopilot` mode TaskCreates all 8 phases (no phase is skipped).
+
+#### TaskCreate ordering (strict)
+
+**All TaskCreate calls 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 → 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 `refs/tracker-contract.md` § "TaskCreate ordering (strict)".
+
+### Visual channel — Copilot CLI / Cursor / Windsurf / plain shell
+
+These CLIs have no TaskList widget. After every state change the agent calls render, which prints a bordered ANSI card as the last tool result so the user sees an updated phase table:
+
+```bash
+bash $HOME/.claude/scripts/phase-tracker.sh render
+```
+
+Do NOT call TaskCreate on these CLIs — the tool does not exist and the call fails.

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

@@ -0,0 +1,465 @@
+---
+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."
+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.
+>
+> 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.
+
+**Claude Code invocation:** `/multi-agent:channels <target>`
+**Copilot CLI invocation:** `multi-agent-channels <target>` (top-level command, dash-separated per Copilot no-namespace convention)
+
+## Input
+
+```
+/multi-agent:channels                                         # cwd + current branch
+/multi-agent:channels PROJ-12345                            # Jira ID
+/multi-agent:channels #42                                     # GitHub issue/PR number
+/multi-agent:channels https://github.com/<org>/<repo>/pull/N
+/multi-agent:channels https://<bitbucket-host>/projects/.../pull-requests/N
+/multi-agent:channels https://<jira-host>/browse/PROJ-12345
+
+/multi-agent:channels PROJ-12345 --channels jira,confluence # non-interactive kanal
+/multi-agent:channels PROJ-12345 --content auto-diff        # non-interactive content
+/multi-agent:channels PROJ-12345 --message "root: ..."      # manual source
+/multi-agent:channels PROJ-12345 --message-file notes.md    # manual, long
+/multi-agent:channels PROJ-12345 --dry-run                  # preview, no POST
+```
+
+Target resolution is identical to the pre-existing enrich flow — any of the 6 forms above works.
+
+## Flow
+
+`resolve target → fetch context → menu (or flags) → generator → humanizer → dispatch → summary`. Channels: Jira comment, Confluence page, Wiki pages, PR description, Board status (GitHub Projects v2).
+
+### Step 1 — Target resolution
+
+1. Parse argument → classify as: Jira-id, Jira-url, PR-url (GitHub or Bitbucket), GitHub-issue-number, empty (cwd+branch).
+2. Resolve linked entities:
+   - Jira ID → linked PR via dev-status API (`/rest/dev-status/latest/issue/detail`)
+   - PR URL → Jira ID extracted from branch name / title / body using `{JIRA_KEY}-XXXXX` pattern
+   - GitHub `#N` → resolved against the repo in cwd
+   - Empty → read git branch, extract Jira ID, find linked PR
+3. Detect remote type: `github` (gh CLI) or `bitbucket` (REST).
+4. Store in runtime state: `{jiraId, targets: [{prUrl, prNumber, remoteType, repoPath, baseBranch, headBranch, repoName, isPrimary}]}`.
+
+**Multi-repo:** when `agent-state.json` `projects[].length > 1`, Step 1 builds **one target per project**. Each project's PR is resolved via `pr` field in its projects[] entry; if missing, the Jira/Issue link query returns multiple PRs (one per repo) — all are added to `targets[]`. The project at `projects[0]` (or whose name matches `state.project`) is marked `isPrimary: true`; others are `isPrimary: false`.
+
+For single-repo tasks, `targets` has exactly one entry. The rest of the flow is target-aware: Step 5 generates one body, Step 6 dispatches to each target, with cross-links (see below).
+
+### Step 2 — Context source detection
+
+Automatic. The generator picks the best-available source:
+
+| Source | Available when | Used for |
+|---|---|---|
+| **Pipeline log** | `$HOME/.claude/logs/multi-agent/<project>/<task-id>/agent-log.md` exists AND matches `jiraId` | "Normal analiz" + "Test senaryoları" content options — uses Phase 1/2/4 output verbatim |
+| **PR diff** | PR exists, diff fetchable (`gh pr diff` or Bitbucket `/diff?contextLines=5`) | "Auto-diff özet" content option — old enrich behavior |
+| **Manual message** | `--message` / `--message-file` provided | Replaces both sources — user text is canonical |
+
+If both pipeline log and PR diff exist, the menu offers both. If only one, the unavailable options are greyed out with a one-line reason.
+
+### Step 3 — Multi-select menu (normal mode)
+
+Rendered in English (`promptLanguage` is locked to `en`). Previous selections (`prefs.global.reportChannels`, `prefs.global.reportContent`) are pre-ticked.
+
+#### Step 3a — Work Summary preview (summary-first flow)
+
+**Runs only when** (a) `agent-state.json` exists for the task AND (b) a Work Summary can be generated (same availability rule as the "Yapılan iş özeti" content row). Purpose: give the user an instant "what did this ship?" answer BEFORE they pick channels. They see the outcome first, then decide where to route it — instead of the reverse.
+
+```bash
+preview=$(bash pipeline/scripts/render-work-summary.sh "$TASK_ID" 2>/dev/null || true)
+[ -n "$preview" ] && {
+  printf '%s\n\n' "$preview"
+  # Auto-tick workSummary content row when preview was shown.
+  # Users can still untick it in 3b if they don't want to re-send the same
+  # block to remote channels (useful when preview was enough for a look).
+  content_defaults.workSummary=true
+}
+```
+
+When the preview renders:
+- **workSummary** row in 3b is **auto-ticked** (user can still uncheck).
+- Previous `prefs.global.reportContent.workSummary` value is respected — if the user had explicitly unticked in a prior run, the auto-tick is **suppressed** and the ticked state matches the pref.
+
+When the preview does NOT render (no state, or pref explicitly off at global level with no override):
+- Skip 3a silently, go straight to the channels picker. The workSummary row in 3b stays at its pref default (`false`).
+
+**Visual flow (TR, pref on + state available):**
+
+```
+📋 Yapılan iş özeti — PROJ-12345
+──────────────────────────────────────────────────────────
+{rendered Work Summary block — header + scope + diffstat + review + phases}
+──────────────────────────────────────────────────────────
+
+✅ İş özetini gördün. Şimdi nereye rapor gönderelim?
+```
+
+Then 3b renders:
+
+```
+┌─ Kanallar ────────────────────────────────────────────
+│ Nereye rapor gönderilsin?
+│   [x] PR description      (replace / append)
+│   [x] Jira comment        (jiraId: PROJ-12345)
+│   [ ] Confluence page
+│   [ ] Wiki                (taskType=component + wiki.enabled gerekli)
+│   [ ] Board               (figmaConfig.board.enabled + projectV2Id gerekli)
+└───────────────────────────────────────────────────────
+
+┌─ İçerik ──────────────────────────────────────────────
+│ Ne eklensin?
+│   [x] Normal analiz       (Phase 1+2+4'ten — high-level impact + risks)
+│   [ ] Teknik analiz       (Changes · Architecture · Dependencies — PR body'deki Technical Details özeti)
+│   [x] Test senaryoları    (Phase 1+2+4'ten)
+│   [ ] PR diff'ten auto-gen (PR varsa diff'i summarize eder)
+│   [ ] Manuel not          (--message / --message-file)
+│   [ ] Cost özeti          (per-phase token + est. USD — tracker data gerekli)
+│   [x] Yapılan iş özeti     (executive summary — yukarıda gösterilen block)
+└───────────────────────────────────────────────────────
+```
+
+**Why auto-tick:** the user JUST saw the summary and is likely sending it somewhere — otherwise they would have stopped before running `/multi-agent:channels`. Auto-tick matches the 80% case; the 20% case (preview was enough, no remote post needed) is a single keystroke to uncheck.
+
+**Autopilot interaction (Step 4):** when `state.autopilot === true`, autopilot still pauses at channels (documented exception to zero-interaction contract). The Work Summary preview renders in-line before the menu, same as normal mode.
+
+#### Step 3b — Channel + content picker
+
+**Greyed-out rules:**
+- "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)"`.
+- "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 status <id>` returns no token tallies AND no `otel-spans.jsonl` exists for the task. Reason: `"(no tracker data — set MULTI_AGENT_OTEL_SPANS=1 or enable token tracking)"`.
+- "Yapılan iş özeti" unselectable if no `agent-state.json` exists for the task (post-hoc call with `--branch` + `--base-branch` flags restores partial availability). Reason: `"(no agent-state.json for {taskId})"`. **Auto-ticked** when Step 3a preview was shown — user can still uncheck before confirming the menu.
+
+**Defaults (first run):** PR + Jira ticked, Confluence + Wiki unticked. Content: auto-diff if pipeline log missing; otherwise normal-analiz + test-senaryoları.
+
+Saved to `prefs.global.reportChannels` and `prefs.global.reportContent` — next run uses these as defaults.
+
+### Step 4 — Mode short-circuit
+
+Non-interactive in three cases — menu skipped entirely, flag values or prefs used directly:
+
+| 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. |
+| `--dry-run` | Runs menu, generates output, prints to stdout, DOES NOT post. |
+
+### Step 5 — Generator
+
+For each selected **content** source, produce one section body. Each section runs through the `humanizer` skill separately (Jira / Confluence / PR tones differ).
+
+| 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`. Same shape as PR body's Technical Details — gives Jira/Confluence readers the code-reviewer view without making them click into the PR. |
+| 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 |
+| Cost özeti | `### Cost Summary` — per-phase token tally + est. USD table. Source: `phase-tracker.sh` phase status + optional OTel spans. See "Cost summary generation" below. |
+| Yapılan iş özeti | `### Work Summary` — executive one-screen summary: task + branch + base + PR, scope delivered (✅/⏳ per Phase 2 task), changed files with +/- counts (capped at 20 rows), review outcome (accepted/deferred/rejected + approved), phase tick strip. Source: `agent-state.json` + `phase-tracker.json` + `git diff --numstat base...HEAD`. See "Work summary generation" below. |
+
+**Output template (aggregated across selected content options):**
+
+```markdown
+### Analysis                        ← if "Normal analiz" selected
+{impact summary, risks — from pipeline log, high-level}
+
+### Technical Details               ← if "Teknik analiz" selected
+#### Changes
+{Per changed-file-group, what changed + why — from Phase 3 dev log}
+#### Architecture
+{Structural decisions, pattern changes, new file layouts — from Phase 2 plan}
+#### Dependencies
+{New imports / frameworks / packages — from git diff --stat, or "None"}
+
+### Root Cause                      ← if "Auto-diff" selected
+{single paragraph — from diff}
+
+- `path/to/File.ext → funcName`: {why it broke}
+
+### Solution                        ← if "Auto-diff" selected
+- `path/to/File.ext:LINE-LINE` — {change, one line}
+
+### Changed Files                   ← if "Auto-diff" selected
+| File | +/- |
+|------|-----|
+| `path/to/File.ext` | +N / -M |
+
+### Test Scenarios                  ← if "Test senaryoları" OR "Auto-diff" selected
+| # | Precondition | Steps | Expected | Status |
+|---|--------------|-------|----------|--------|
+| 1 | ...          | ...   | ...      | To Test|
+
+### Notes                           ← if "Manuel not" selected
+{user message}
+
+### Work Summary                    ← if "Yapılan iş özeti" selected
+{executive scope + files + review + phases block — see "Work summary generation" below}
+
+### Cost Summary                    ← if "Cost özeti" selected
+{per-phase token + USD table — see "Cost summary generation" below}
+
+### Store compliance                ← auto-appended if cached compliance report exists
+{summary line — see below}
+
+Ref: {jiraId}
+```
+
+**Store compliance auto-augmentation:**
+
+After the content-selected sections are generated, check for a recent compliance report cached from `/multi-agent:test "store-ready"`:
+
+```bash
+# Cache locations (newest wins; expire after 6h to avoid stale cross-branch reports)
+find /tmp -maxdepth 1 -name 'archiveguard-*.json' -o -name 'play-compliance-*.json' \
+  -newermt "-6 hours" -print 2>/dev/null | head -1
+```
+
+If a cached report exists AND any of the selected channels is PR / Jira / Confluence, append an auto-summary section:
+
+| Blocker count | Appended line |
+|---|---|
+| `errors > 0` | `### Store compliance` + `⚠️ {N} blocker(s), {M} warning(s) — run /multi-agent:test "store-ready" for the full report.` — per-blocker: `- \`{ruleID}\` — {Apple ITMS / Play ref}: {message}` (capped at 5 rows, rest collapsed to `+N more`) |
+| `errors == 0, warnings > 0` | `### Store compliance` + `✅ No blockers. {M} warning(s) — see /multi-agent:test "store-ready" for detail.` |
+| `errors == 0, warnings == 0` | Skip section entirely — don't pollute PR body |
+
+The section references `ruleID` + policy ref from the compliance skill catalogs (`apple-archive-compliance` / `google-play-compliance`) verbatim. No translation — global identifiers stay as-is.
+
+If no cached report exists, skip silently — this is augmentation, not a gate.
+
+**Work summary generation:**
+
+Emitted only when `reportContent.workSummary === true` and at least one of (`agent-state.json`, `--branch` flag) is available. The shell adapter is `pipeline/scripts/render-work-summary.sh <taskId>`:
+
+1. **Task header** — `taskId`, `branch`, `baseBranch`, `prNumber` from `agent-state.json` (or explicit flags for post-hoc invocation).
+2. **Scope delivered** — Phase 2 `planTodos[]` / `tasks[]` rendered as `✅` (status=done) or `⏳` (anything else) rows. Task id + title shown; `(deferred — rationale)` appended if the task's `status` is `"deferred"`.
+3. **Changed files** — `git -C $WORKTREE diff --numstat $baseBranch...HEAD`. Shows `` `path` (+add / -del) `` per row, capped at 20 with a `_... +N more files not shown_` footer when exceeded. Total adds/dels + file count in section header.
+4. **Review outcome** — from `reviewConsensus` (pre-v6.1) or `phases["4"].triage`: `{accepted} accepted · {deferred} deferred · {rejected} rejected · approved={bool}`. Hidden entirely when all three buckets are empty (normal for `--dev` / `dev-autopilot` runs that skip Phase 4).
+5. **Phase tick strip** — single line from `phase-tracker.json`: `0 Init ✅ · 1 Analysis ✅ · 2 Planning ✅ · 3 Dev ✅ · 4 Review ✅ · 5 Test ⏭ · 6 Commit ✅ · 7 Report ▶`. Marks: `✅` completed · `▶` in_progress · `❌` failed · `⏭` skipped · `·` pending.
+
+**Output template:**
+
+```markdown
+### Work Summary
+**Task**: `PROJ-1099`  |  **Branch**: `bugfix/PROJ-1099-dark-mode`  |  **Base**: `develop`  |  **PR**: #104
+
+#### Scope delivered
+- ✅ T1 Add failing dark-mode snapshot test
+- ✅ T2 Replace Color.white with design token
+
+#### Changed files (3 files · +48 / -12)
+- `Sources/Auth/LoginView.swift` (+24 / -8)
+- `Sources/Auth/LoginViewTests.swift` (+22 / -4)
+- `Sources/DesignSystem/Color+Tokens.swift` (+2 / -0)
+
+#### Review outcome
+- 1 accepted · 0 deferred · 0 rejected · approved=true
+
+#### Phases
+- 0 Init ✅ · 1 Analysis ✅ · 2 Planning ✅ · 3 Dev ✅ · 4 Review ✅ · 5 Test ⏭ · 6 Commit ✅ · 7 Report ▶
+```
+
+**Post-hoc invocation** (task already finished, agent-state.json may be archived): pass `--branch` + `--base-branch` explicitly — the script still emits task header + changed-files + phases sections (scope + review outcome are state-dependent and will be absent if state is gone).
+
+**Cost summary generation:**
+
+Emitted only when `reportContent.costSummary === true` and tracker data is available. Source of truth is `phase-tracker.sh`:
+
+1. **Token tallies per phase** — read `.worktrees/{taskPath}/phase-tracker.json` (written by `phase-tracker.sh update` / `tokens` actions). If present, each phase row has `{tokens_in, tokens_out}`.
+2. **Fallback to OTel spans** — if tracker JSON has no token columns but `otel-spans.jsonl` exists (set `MULTI_AGENT_OTEL_SPANS=1` beforehand), aggregate `phase.tokens` spans by phase ID.
+3. **USD estimate** — uses a static price table in `pipeline/scripts/cost-table.json` (model → $/Mtok_in, $/Mtok_out). Missing model → show `—` for USD, never block.
+
+**Output template:**
+
+```markdown
+### Cost Summary
+| Phase | Model | Tokens in | Tokens out | Est. USD |
+|-------|-------|-----------|------------|----------|
+| 1. Analysis | opus   | 12,480 | 3,210 | $0.42 |
+| 2. Planning | opus   | 18,904 | 5,120 | $0.66 |
+| 3. Dev      | sonnet | 42,310 | 9,880 | $0.27 |
+| 4. Review   | opus   | 21,050 | 4,720 | $0.66 |
+| **Total**   |        | **94,744** | **22,930** | **$2.04** |
+```
+
+Generated by `pipeline/scripts/render-cost-summary.sh <task-id>` using prices from `pipeline/scripts/cost-table.json`. The channels adapter shells out to this renderer — doc table is illustrative only, runtime is authoritative.
+
+**Precision rules:** tokens as thousand-separated integers. USD rounded to 2 dp (`printf '$%.2f'`). Rows with zero tokens dropped. If total USD is `—` (no price for any model), replace the total row USD cell with `—` and add a one-line footnote: `*USD unavailable — add model to cost-table.json*`.
+
+**Target length rule:** full body fits one screen on a typical laptop (< 80 lines). Auto-diff summary capped at 5 lines per section. No framework-theory paragraphs, no numbered "why this approach" lists.
+
+### Step 6 — Channel dispatch
+
+For each selected **channel**, call the corresponding adapter. Adapters run **in parallel** — one failure does not block others.
+
+**Multi-repo dispatch:** When `state.projects[].length > 1`, the dispatcher delegates per-channel rendering to `~/.claude/lib/channels-multi-repo.sh`:
+
+| Channel | Behavior | Adapter call |
+|---------|----------|--------------|
+| **PR description** | Posted to **every** target's PR. Primary's body lists extras as `Related: <url>`; each extra's body lists primary as `Part of: <url>`. | `channels-multi-repo.sh render-pr <state> <body> <repoName>` per target |
+| **Jira comment** | Posted **once** (Jira ticket is shared by all repos). Body prepended with bulleted `* PR:` list — primary first, extras after. | `channels-multi-repo.sh render-jira <state> <body>` once |
+| **Confluence page** | Posted **once** to the primary's component slug. `## Related PRs` heading block prepended. | `channels-multi-repo.sh render-conf <state> <body>` once |
+| **Wiki** | Posted **once** to the primary repo's wiki, since wiki scope is `figma-config.wikiRepo` (single repo). | No adapter — body unchanged |
+| **Board** | Posted **once** — board status is keyed off the GitHub Issue, not per-PR. Primary repo's issue is the target. | No adapter — single mutation |
+
+**Target enumeration:** `channels-multi-repo.sh targets <state>` returns a JSON array `[{repoName, prUrl, prNumber, isPrimary, crossLinks}]` for the dispatch loop. Single-repo tasks return one entry with empty `crossLinks` — every render-* call falls through to the body unchanged, so the loop is uniform across single-repo and multi-repo paths.
+
+**Logging hint:** `channels-multi-repo.sh summary <state>` produces a one-line autopilot log entry (`1 primary (foo) + 2 extras: <url> <url>` or `single-repo task`).
+
+#### Adapter: PR description
+Aggregated Markdown from Step 5 → PR description. GitHub uses `gh pr edit --body-file`; Bitbucket uses a **reviewer-preserving (required)** `PUT /pull-requests/{id}` payload (must re-send `reviewers`, `fromRef`, `toRef`, `draft`, `version` — omitting any one resets that field server-side). Default is **replace**; `--append` opt-in. Multi-repo cross-links handled by `channels-multi-repo.sh render-pr`.
+
+Full contract: [`refs/channels/pr.md`](refs/channels/pr.md) — Bitbucket payload assembly snippet, version-mismatch retry, `--ready` promotion, multi-repo cross-link block.
+
+#### Adapter: Jira comment
+Body converted to Jira wiki markup (`### ...` → `*...*`, `- [ ] ...` → `# ...`, `` `x` `` → `{{x}}`, tables to `||h||h|| |c|c|`); first line is the PR URL. POST `/rest/api/2/issue/{id}/comment` via heredoc + `jq --rawfile` + `curl --data-binary @file`. Token resolved from `keychainMapping.jira`.
+
+Full contract: [`refs/channels/jira.md`](refs/channels/jira.md) — full conversion table, multi-repo PR-list prepend, Wiki→Jira triad interaction.
+
+#### Adapter: Confluence page
+Token from `keychainMapping.confluence`; missing/expired triggers the inline Save Flow from `setup.md`. Parent page picked from `prefs.projects[<project>].confluenceUrls` recents (LRU, max 5) or paste new URL. Auto-suggest title `"{jiraId} — {taskTitle}"`. Body converted to Confluence storage format (`<h3>`, `<table>`, `<ac:structured-macro>` code blocks). POST `/rest/api/content`; URL saved back to recents.
+
+Full contract: [`refs/channels/confluence.md`](refs/channels/confluence.md) — URL parsing rules, full storage-XML conversion table, update-vs-create branch.
+
+#### Adapter: Board (GitHub Projects v2 status move)
+
+**Precondition gate:** `figmaConfig.board.enabled === true` AND `figmaConfig.board.provider === "github-projects-v2"` AND `figmaConfig.github.projectV2Id` non-empty. If not met, the channel is greyed in the menu (Step 3b rule) and the adapter is skipped silently in flag-mode dispatch.
+
+**Default target column:** `inReview` — read from `figmaConfig.github.fieldOptions.status.inReview` (the option ID, e.g. `bdb0d8ef`). Other column targets (e.g. `done`, `bugfix`) overridable via flag `--board-status <key>` where `<key>` matches a key under `fieldOptions.status`.
+
+**Token:** `prefs.global.keychainMapping.github_projects` (preferred — must include `project,read:project` scopes). Fallback chain: `keychainMapping.github` → standard key `${USER}_Github_Access_Token`. Resolve via `~/.claude/lib/credential-store.sh get <key>` (cross-platform — delegates to macOS Keychain / Linux libsecret / Windows Credential Manager). Token must NOT be passed on the CLI — export as `GH_TOKEN` env var only (per memory rule on token leakage).
+
+**Item lookup:** the issue's project item ID is fetched via GraphQL `repository.issue(number).projectItems(first:5)` filtered to `project.id === figmaConfig.github.projectV2Id`. If the issue is not yet in the project, dispatch silently no-ops with reason `"issue not on board"` in the summary.
+
+**Mutation:** GraphQL `updateProjectV2ItemFieldValue(input: { projectId, itemId, fieldId: figmaConfig.github.projectV2Fields.status, value: { singleSelectOptionId: <target> } })`. Verify by re-querying `fieldValueByName(name: "Status")` on the same item; assert `name === target column label` from `figmaConfig.board.columns`.
+
+**Multi-repo:** runs **once** (board status is keyed off the GitHub Issue, not per-PR). When `state.projects[].length > 1`, the primary repo's issue is the target; extras' PRs do not trigger additional moves.
+
+**Idempotency:** if the issue is already on the target column, the mutation is a no-op and the adapter reports `"already in <column>"` in the summary.
+
+Full contract: [`refs/channels/board.md`](refs/channels/board.md) — token scope upgrade flow (`gh auth refresh -s project,read:project`), field-ID auto-discovery for repos missing `projectV2Fields.status` in figma-config, error-recovery (token expired vs scope insufficient).
+
+#### Adapter: Wiki
+**Precondition gate:** `state.taskType === "component"` AND `figmaConfig.wiki.enabled === true`. If not met, shows the Case B menu from `refs/wiki-capture.md` (setup / skip / disable / manual-note).
+
+**Wiki → Jira comment auto-link** (triad contract, preserved from v5.6): when the Wiki adapter writes pages AND `state.jiraId` is set AND `prefs.global.wikiToJiraComment === true`, also post a humanizer-passed summary of the wiki pages (component name + variant count + wiki URL) as an additional Jira comment on the same issue. Independent of the main Jira channel's comment — both can coexist. Full contract in `refs/issue-jira-triad.md`.
+
+**If preconditions met (Case A):** scope multi-select prompt (Ana sayfa / iOS sub-page / Screenshots / Index updates / Diğer); adapter dispatched to `pipeline/skills/figma-ios/figma-component-wiki` (or `figma-android/`).
+
+Full contract: [`refs/channels/wiki.md`](refs/channels/wiki.md) — all four `figma-config.wiki.mode` adapters (submodule / in-repo / github-wiki / separate-repo), full Case A scope menu, screenshot quadrant gate.
+
+### Step 7 — Summary
+
+After all adapters complete (or fail non-blocking):
+
+```
+channels dispatch complete
+  PR description  ✓   version 3→4, reviewers 23 preserved
+  Jira comment    ✓   posted → <jira-url>?focusedCommentId=2484780
+  Confluence      –   skipped: user declined
+  Wiki            ✓   3 files via github-wiki adapter
+  Board           ✓   In Develop → In Review (project #4)
+```
+
+Each line: status symbol (`✓` / `✗` / `–`), key metric, URL where applicable.
+
+Persist selections to `prefs.global.reportChannels` + `prefs.global.reportContent` for next run default.
+
+## Flags
+
+| Flag | Effect |
+|------|--------|
+| `--channels pr,jira,confluence,wiki` | Non-interactive kanal selection (comma list). Skips kanal menu. |
+| `--content normal,technical,test,auto-diff,note` | Non-interactive content selection. Skips content menu. |
+| `--message "..."` | Manual mode — use user text as source, no diff read. Forces `content=note`. |
+| `--message-file path` | Manual mode, long message from file. |
+| `--append` | PR description: append instead of replace. |
+| `--dry-run` | Generate, print to stdout, do not POST. |
+| `--lang=tr\|en\|both` | Output language override (default: `en`; `promptLanguage` is locked to `en`). |
+| `--ready` | If PR draft, promote to READY after channels dispatch. |
+
+## Required rules
+
+- **Bitbucket reviewer preservation** — every PR PUT MUST carry current `reviewers`, `fromRef`, `toRef`, `draft`. Omitting any resets that field server-side.
+- **Default is replace, not append** for PR description. `--append` opt-in.
+- **Real newlines + no HTML entities** in ALL bodies (Jira, Confluence, PR): heredoc + `jq --rawfile` + `curl --data-binary @file`. Never embed `\n` literally — Jira/Bitbucket save verbatim.
+- **Humanizer per-channel** — each channel body runs humanizer independently. Tones differ (Jira informal, Confluence formal, PR technical).
+- **No markers** — channels does a full replace each run; no `<!-- channels:start -->` bookmarks.
+- **Every body item references a symbol/file/line** from diff or pipeline log. No generic "tested the feature" sentences.
+- **Adapter failures are non-blocking** — one channel failing does not abort others. Final summary shows per-adapter status.
+
+## Error handling
+
+| Condition | Behavior |
+|-----------|----------|
+| No target resolvable | Error, exit 1 |
+| PR not found + Jira selected | Proceed Jira-only, log reason |
+| PR merged/closed | Warn, confirm continue |
+| Author bot / dependabot | Skip entire run |
+| Diff > 2 MB | Ask: skip / top-20-files / cancel |
+| No pipeline log + "Normal analiz" selected | Greyed out at menu; if forced via `--content`, error |
+| Bitbucket PR version mismatch | Refetch once, retry; fail on second mismatch |
+| Jira token missing/expired | Token Save Flow inline; skip on user-skip |
+| Wiki preconditions not met | Case B menu per `refs/wiki-capture.md` |
+
+## Phase 7 delegation contract
+
+Phase 7 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 |
+| `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.
+
+**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 `refs/phases/modes.md` for full contract.
+
+## Cross-CLI parity
+
+| CLI | Command name | Invocation |
+|---|---|---|
+| Claude Code | `/multi-agent:channels` | Slash namespace (colon) |
+| Copilot CLI | `multi-agent-channels` | Top-level command (dash-separated, no namespace support) |
+
+Both installations read the same source file (`pipeline/commands/multi-agent/channels.md`) — `install.js --all` copies to:
+- `~/.claude/commands/multi-agent/channels.md`
+- `~/.copilot/commands/multi-agent-channels.md`
+
+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.
+
+## Examples
+
+```
+/multi-agent:channels
+  → resolves from cwd+branch → PROJ-12345 + PR #3433
+  → menu: PR ✓ Jira ✓ / Normal analiz ✓ Test senaryoları ✓
+  → PR description replaced (v3→4, 23 reviewers preserved)
+  → Jira comment posted (id 2484780)
+  → Confluence –  Wiki –
+
+/multi-agent:channels PROJ-12345 --channels confluence --content note --message-file notes.md
+  → non-interactive: only Confluence, content from notes.md
+  → asks: parent page URL (or recent [1] / [2])
+  → page created → https://<host>/pages/12345
+
+/multi-agent:channels https://<bitbucket>/.../pull-requests/42 --dry-run
+  → resolves → PROJ-67890
+  → prints Jira + PR body preview to stdout, no POST
+
+/multi-agent:channels --message "root: PNR empty, UI silent. fix: length>0 guard in HomeVC.m"
+  → auto-diff from cwd+branch PR + user note combined
+  → posts to default kanals (PR + Jira)
+```

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

@@ -0,0 +1,66 @@
+---
+description: "Uninstall the pipeline from every CLI (Claude / Copilot / Cursor / Windsurf / Cline). Keychain access tokens are left untouched. Asks for double confirmation."
+argument-hint: "[--dry-run] [--claude] [--copilot] [--cursor] [--windsurf] [--cline] [--target=<path>]"
+---
+
+# multi-agent delete — Token-Preserving Uninstall
+
+Uninstalls the pipeline itself from the system. **This is different from `:purge`:**
+
+| Command | What it removes |
+|---|---|
+| `:purge` | Active tasks' worktrees / branches / logs / state (development data) |
+| `:delete` | The pipeline itself: skills, commands, agents, scripts, rules — from every CLI |
+
+## Never deleted
+
+- **Keychain / Credential Manager / libsecret** personal access tokens (GitHub, Jira, Bitbucket, Confluence, Telegram, Vercel, Firebase, etc.)
+- `~/.claude/CLAUDE.md` (user customisations)
+- `~/.claude/multi-agent-preferences.json` (user settings)
+- User content OUTSIDE the `<!-- multi-agent-pipeline:begin/end -->` markers (`.windsurfrules`, `copilot-instructions.md`)
+
+## Steps
+
+1. **Determine scope** — parse `$ARGUMENTS`:
+   - No target flag: every installed target (default)
+   - `--claude / --copilot / --cursor / --windsurf / --cline`: selective
+   - `--target=<path>`: adapter target (default: cwd)
+   - `--dry-run`: report only, delete nothing
+
+2. **Show a preview** (run the script with `--dry-run`):
+   ```bash
+   node "$HOME/.claude/scripts/uninstall.mjs" --dry-run --yes <flags>
+   ```
+   Show the output raw to the user.
+
+3. **First confirmation**:
+   > "The above will be deleted. Tokens will NOT be touched. Continue? (y/N)"
+   - `n` → cancel, exit.
+
+4. **Second confirmation** (paranoia gate, same pattern as `:purge`):
+   > "Irreversible. Type 'delete' to confirm:"
+   - Anything other than `delete` → cancel.
+
+5. **Delete** — run the real script with `--yes`:
+   ```bash
+   node "$HOME/.claude/scripts/uninstall.mjs" --yes <flags>
+   ```
+
+6. **Confirm**:
+   ```
+   ✓ multi-agent-pipeline removed.
+   ℹ Personal access tokens preserved in Keychain.
+   ```
+   Remind the user how to inspect the tokens (cross-platform — same command on every backend):
+   - `~/.claude/lib/credential-store.sh get "<service>"`
+
+7. **Reinstall** (if the user wants to):
+   ```bash
+   npx @mmerterden/multi-agent-pipeline install
+   ```
+
+## Notes
+
+- This command does NOT remove the *installed copy* of the npm package. It only removes the distributed files. `npm uninstall -g @mmerterden/multi-agent-pipeline` is a separate step.
+- `--dry-run` is always safe — zero side effects.
+- The adapter target (Cursor / Windsurf / Cline) is the cwd. For another repo, pass `--target=<path>`.