@mmerterden/multi-agent-pipeline 20.30.0 → 20.34.0

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

@@ -25,20 +25,7 @@ allowed-tools: Read, Write, Edit, Bash, Grep, WebFetch, AskUserQuestion
 
 ## 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 channel
-/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
-```
+A Jira id or URL, a GitHub or Bitbucket PR URL, a GitHub `#N`, or nothing (cwd + current branch), plus the flags below. Example invocations: `$HOME/.claude/multi-agent-refs/channels/reference.md` "Input forms".
 
 ## Flow
 
@@ -55,19 +42,11 @@ allowed-tools: Read, Write, Edit, Bash, Grep, WebFetch, AskUserQuestion
 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 7 dispatches to each target, with cross-links (see below).
+**Multi-repo:** when `agent-state.json` `projects[].length > 1`, Step 1 builds **one target per project**. How each target is resolved and which one is primary: `$HOME/.claude/multi-agent-refs/channels/multi-repo.md` "Target resolution (Step 1)", read before Step 1 then. Single-repo tasks have exactly one target.
 
 ### 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 summary" content option  -  old enrich behavior |
-| **Manual message** | `--message` / `--message-file` provided | Replaces both sources  -  user text is canonical |
+Automatic: pipeline log, PR diff, or a manual message, best available first. Read `$HOME/.claude/multi-agent-refs/channels/menu.md` before Step 2: the source table (when each source is available, which content options it feeds) and the Step 3 menu rules.
 
 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.
 
@@ -77,47 +56,15 @@ Rendered in English (`promptLanguage` is locked to `en`). Previous selections (`
 
 #### 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 $HOME/.claude/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`).
-
-After the preview prints, 3b renders the two pickers: **Channels** (PR description, Jira comment, Confluence page, Wiki, Board; each unavailable one greyed with its reason) and **Content** (normal analysis, technical analysis, test scenarios, test run, PR auto-diff, manual note, cost summary, work summary).
-
-**Why auto-tick:** the user just saw the summary and is most likely sending it; the explicit pref still wins.
+**Runs only when** `agent-state.json` exists for the task AND a Work Summary can be generated. It prints the summary BEFORE the channel picker and auto-ticks the workSummary content row in 3b; an explicit `prefs.global.reportContent.workSummary` still wins. Otherwise 3a is skipped silently.
 
 **Autopilot interaction (Step 4):** `state.autopilot === true` still pauses at channels (documented exception to zero-interaction contract), preview in-line. Under `MULTI_AGENT_UNATTENDED=1` it posts nothing: `$HOME/.claude/multi-agent-refs/features/unattended-security.md`.
 
 #### 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 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. "Test Koşumu (Xray)": `channels/test-run.md`.
-- "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)"`.
-- "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ı.
+Two pickers: **Channels** (PR description, Jira comment, Confluence page, Wiki, Board) and **Content**. An unavailable option is greyed with a one-line reason, never hidden. Selections are saved to `prefs.global.reportChannels` and `prefs.global.reportContent` as the next run's defaults.
 
-Saved to `prefs.global.reportChannels` and `prefs.global.reportContent`  -  next run uses these as defaults.
+`channels/menu.md` (read at Step 2) carries the preview snippet, the auto-tick rules, every greyed-out rule with its reason string, and the first-run defaults.
 
 ### Step 4  -  Mode short-circuit
 
@@ -147,152 +94,15 @@ what was wrong, what was changed, which areas must be tested, what else is
 affected - in the same plain register as the summary, and it is the part a test
 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 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 |
-| Test Koşumu (Xray) | `### Test Koşumu`  -  Xray Test Execution of the task's UI scenario run (`channels/test-run.md`) |
-| 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 (done/[pending] 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. |
+Read `$HOME/.claude/multi-agent-refs/channels/generator.md` before generating any section: the content-option table (which section each option produces, from which source), the aggregated output template, store-compliance auto-augmentation from cached `archiveguard-*.json` / `play-compliance-*.json` reports, and the work-summary (`render-work-summary.sh`) and cost-summary (`render-cost-summary.sh`) generators with their precision rules.
 
 **The content options are sources, not the body's shape.** Which sections a PR
 body carries and in what order is fixed by `channels/pr.md` (`summary` →
 `technical` → `architecture` → `impact` → `test_scenarios` → `test_run` → `visuals` → `risk`
-→ `dependencies` → `build` → `related`); the options below choose what gets
+→ `dependencies` → `build` → `related`); the content options choose what gets
 gathered to fill them. A content option left unselected means a section has no
 source, not that the section may be reordered or renamed.
 
-**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 2 dev log}
-#### Architecture
-{Structural decisions, pattern changes, new file layouts  -  from Phase 1 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
-**1. {what this scenario exercises}**
-1. {step the tester performs}
-2. **Expected:** {what they should see}
-
-**2. {regression scenario}**
-1. {step}
-2. **Expected:** {what should still behave as before}
-
-### Test Koşumu                     ← if "Test Koşumu (Xray)" selected
-
-### 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` + `[done] 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 `$HOME/.claude/scripts/render-work-summary.sh <taskId>`, and that script's own header is the spec for what it emits - task header, scope delivered, changed files, review outcome, phase strip - including the caps and the hidden-when-empty rules. Exit 2 means the state was unreadable: skip the section, do not substitute a hand-written one.
-
-**Output template:**
-
-```markdown
-### Work Summary
-**Task**: `PROJ-1099`  |  **Branch**: `bugfix/PROJ-1099-dark-mode`  |  **Base**: `develop`  |  **PR**: #104
-
-#### Scope delivered
-- [done] T1 Add failing dark-mode snapshot test
-- [done] 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 [done] · 1 Plan [done] · 2 Dev [done] · 3 Review [done] · 4 Commit [done] · 5 Report active
-```
-
-**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**  -  `render-cost-summary.sh <taskId>` resolves the tracker JSON itself: worktree candidates (`.worktrees/{taskPath}/phase-tracker.json`) first, then the standard location `$HOME/.claude/logs/multi-agent/{taskId}/tracker-state.json` that `phase-tracker.sh` actually writes. Each phase row carries `{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 `$HOME/.claude/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 `$HOME/.claude/scripts/render-cost-summary.sh <task-id>` using prices from `$HOME/.claude/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  -  Body preview + approval gate (interactive modes)
@@ -308,27 +118,7 @@ Skipped in exactly two cases:
 
 **Preview render** (one block per selected channel, final body after humanizer  -  shown in readable Markdown, channel-specific markup conversion happens after approval).
 
-Conversion is per-channel; two channels have none:
-
-| Channel | Conversion after approval | Table |
-|---|---|---|
-| PR description | **none**  -  posted as Markdown, verbatim | GitHub / Bitbucket / GitLab all render Markdown; see `channels/pr.md` "Markup dialect" |
-| GitHub issue comment | **none**  -  posted as Markdown, verbatim |  -  |
-| Jira comment | markdown → Jira wiki markup | `channels/jira.md` "Wiki markup conversion" |
-| Confluence page | markdown → storage format | `channels/confluence.md` "Body conversion" |
-
-The Jira table is the only *text* markup table in the doc set and never applies to the PR body: `h2.`, `{{code}}` or `#`-numbered lists render there as raw wiki markup.
-
-```
-── PR description  ({repoName} #{prNumber}, replace) ─────────
-{body}
-── Jira comment  ({jiraId}) ──────────────────────────────────
-{body}
-── Confluence page  ("{title}" under {parentUrl}) ────────────
-{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 5 Step 1.5  -  same gate, see `$HOME/.claude/multi-agent-refs/phases/phase-5-report.md`), test-run candidates to untick (`channels/test-run.md`), the Jira body's `--measure` (`render-jira-evidence.mjs`).
+PR description and GitHub issue comment are posted as Markdown verbatim; Jira comment and Confluence page are converted after approval. Read `$HOME/.claude/multi-agent-refs/channels/preview.md` before rendering the preview: the per-channel conversion table, the preview block layout and the secondary-artifact intents that ride along at its bottom.
 
 **Then a single AskUserQuestion** (`picker-contract.md`; `question`/`label`/`description` in `outputLanguage`, `header` English):
 
@@ -361,14 +151,14 @@ Then post it - do not assemble the request:
 bash "$HOME/.claude/lib/jira-publish.sh" --issue "$JIRA_ID" --body-file "$F" --target comment
 ```
 
-The publisher escapes every body (Jira renders `:)` `(x)` `(!)` `(/)` as emoticon images, and a Swift selector like `login(source:input:)` ends in `:)`) and resolves the token from `keychainMapping.jira` without putting it on argv.
+The publisher escapes every body (emoticon sequences, see Gotchas) and resolves the token from `keychainMapping.jira` without putting it on argv.
 
 Full contract: [`$HOME/.claude/multi-agent-refs/channels/jira.md`]($HOME/.claude/multi-agent-refs/channels/jira.md)  -  full conversion table, multi-repo PR-list prepend, Wiki→Jira triad interaction.
 
 **Issue family** (`state.jiraFamily` set): instead, `bash $HOME/.claude/lib/jira-family-write.sh plan --state "$STATE_FILE" --dev-body "$F"`, the Step 6 preview as one multi-select under `plan.confirm`, then `apply --state "$STATE_FILE"`: `$HOME/.claude/multi-agent-refs/features/jira-family.md`.
 
 #### 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.
+Token from `keychainMapping.confluence`; missing/expired triggers the inline Save Flow from `setup.md`. Parent page from `prefs.projects[<project>].confluenceUrls` recents or a pasted URL, then storage-format conversion and POST; URL saved back to recents.
 
 Full contract: [`$HOME/.claude/multi-agent-refs/channels/confluence.md`]($HOME/.claude/multi-agent-refs/channels/confluence.md)  -  URL parsing rules, full storage-XML conversion table, update-vs-create branch.
 
@@ -379,42 +169,19 @@ Precondition, token, item lookup, mutation and idempotency: `$HOME/.claude/multi
 #### Adapter: Wiki
 **Precondition gate:** `state.taskType === "component"` AND `figmaConfig.wiki.enabled === true`. If not met, shows the Case B menu from `$HOME/.claude/multi-agent-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 `$HOME/.claude/multi-agent-refs/issue-jira-triad.md`.
-
-**If preconditions met (Case A):** scope multi-select prompt (Main page / iOS sub-page / Screenshots / Index updates / Other); adapter dispatched to the plugin skill `ai-ios-toolkit:figma-component-wiki` (or `ai-android-toolkit:figma-component-wiki`).
+**If preconditions met (Case A):** scope multi-select, then dispatch to the plugin skill `ai-ios-toolkit:figma-component-wiki` (or `ai-android-toolkit:figma-component-wiki`). When wiki pages are written AND `state.jiraId` is set AND `prefs.global.wikiToJiraComment === true`, the Wiki-to-Jira comment auto-link posts an additional Jira comment, independent of the main Jira channel's comment.
 
 Full contract: [`$HOME/.claude/multi-agent-refs/channels/wiki.md`]($HOME/.claude/multi-agent-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 8  -  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.
+After all adapters complete (or fail non-blocking), print one line per channel: status symbol (`✓` / `✗` / `-`), key metric, URL where applicable. Format example: `$HOME/.claude/multi-agent-refs/channels/reference.md` "Step 8 summary format".
 
 Persist selections to `prefs.global.reportChannels` + `prefs.global.reportContent` for next run default.
 
 ## Flags
 
-| Flag | Effect |
-|------|--------|
-| `--channels pr,jira,confluence,wiki` | Non-interactive channel selection (comma list). Skips channel menu. |
-| `--content normal,technical,test,auto-diff,note,test-run` | Non-interactive content selection. Skips content menu. |
-| `--flow-run <runId>[,<runId>...]` | Runs for the test run block (`channels/test-run.md`). |
-| `--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. |
+`--channels`, `--content`, `--flow-run`, `--message`, `--message-file`, `--append`, `--dry-run`, `--lang`, `--ready`. What each one does: `$HOME/.claude/multi-agent-refs/channels/reference.md` "Flags", read before Step 1 whenever a flag is present.
 
 ## Required rules
 
@@ -429,17 +196,7 @@ Persist selections to `prefs.global.reportChannels` + `prefs.global.reportConten
 
 ## 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 `$HOME/.claude/multi-agent-refs/wiki-capture.md` |
+Read `$HOME/.claude/multi-agent-refs/channels/reference.md` before Step 1: the condition-by-condition behaviour table (no target, PR missing or merged, bot author, oversized diff, forced unavailable content, Bitbucket version mismatch, missing token, Wiki preconditions). Cross-CLI parity notes and worked examples live in the same file.
 
 ## Phase 5 delegation contract
 
@@ -453,42 +210,3 @@ Phase 5 invokes this command internally instead of running its own inline Jira/C
 Phase 5 passes a runtime state bundle: `{jiraId, prUrl, remoteType, taskType, figmaConfig, agentState, pipelineLogPath, flowRuns}`. `channels` reads these directly, skips target-resolution Step 1.
 
 **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
-
-| 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 (`$HOME/.claude/commands/multi-agent/channels/SKILL.md`)  -  `install.js --all` copies to:
-- `~/.claude/commands/multi-agent/channels/SKILL.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 5 <N> "<step>" <status>`  -  same shape as Phase 5.
-
-## 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: order id empty, UI silent. fix: length>0 guard in HomeVC.m"
-  → auto-diff from cwd+branch PR + user note combined
-  → posts to default channels (PR + Jira)
-```

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

@@ -1,7 +1,7 @@
 ---
 description: "Build and query this repo's code graph: a deterministic, LLM-free map of symbols, imports and references used to narrow Phase 1's Explore scope and to keep the knowledge base current. Read-only on code, costs no API tokens. Use when a task needs to know where something lives or what depends on it before reading files."
 description-tr: "Bu repo'nun kod grafiğini kurar ve sorgular: sembolleri, import'ları ve referansları LLM'siz, deterministik biçimde haritalar. Faz 1'in Explore kapsamını daraltmak ve bilgi tabanını güncel tutmak için kullanılır. Kodda salt-okunur, API maliyeti yok."
-argument-hint: "[build | refresh | ask \"<question>\" | affected \"<symbol>\" | report | status]"
+argument-hint: "[build | refresh | ask \"<question>\" | affected \"<symbol>\" | path <from> <to> | links <a,b> | report | diff <older> | status]"
 parameters: [{"name":"action","kind":"text"}]
 gui: form
 destructive: false
@@ -29,7 +29,10 @@ No worktree, no branch, no commit, no pipeline chaining.
 | `refresh` | same as `build` | A full rebuild takes seconds, so there is no separate incremental path |
 | `ask "<question>"` | `graph-query.mjs "<question>" --budget N` | Token-budgeted traversal; default budget 2000 |
 | `affected "<symbol>"` | `graph-affected.mjs "<symbol>" --depth N` | Reverse traversal: the blast radius of a change |
-| `report` | `graph-report.mjs` | Writes `GRAPH_REPORT.md` beside the graph: hubs, modules, external dependencies, unconnected files, and symbols no other file references (candidates only - the extractor is regex, not a parser, so nothing gates on that list) |
+| `path <from> <to>` | `graph-query.mjs --path <from> <to>` | Shortest path between two symbols or files (id or name). An ambiguous name is refused with candidate ids, an unknown one gets its nearest names (exit 3); external modules are never walked through |
+| `report` | `graph-report.mjs` | Writes `GRAPH_REPORT.md` beside the graph: hubs, import cycles, clusters with cohesion, questions worth asking, modules, external dependencies, unconnected files, and symbols no other file references (candidates only - the extractor is regex, not a parser, so nothing gates on that list) |
+| `links <a,b,...>` | `graph-links.mjs build --projects <a,b,...>`, then `graph-links.mjs affected --project <b>` | Which files of one repository import another (package, module or Kotlin type names), for a run across a main repo and its libraries. Graphs stay separate (ADR-0018) |
+| `diff <older-graph>` | `graph-report.mjs --diff <older-graph>` | Files, symbols and edges added or removed since an older build, and the import-cycle count before and after |
 | `status` | `graph-report.mjs --status` | One line: stack, scale, build time and whether `baseCommit` still matches HEAD. Never read the graph file yourself - it is 22MB on a large repo |
 
 With no argument, run `status`, then offer `build` when no graph exists and

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

@@ -19,7 +19,7 @@ Two-axis language preference for the pipeline:
 | Field | Controls | Stored at | Mutability |
 |---|---|---|---|
 | `promptLanguage` | Interactive prompts during a pipeline run (account picker, project picker, dev-context picker, base-branch picker, branch-name picker, maturity ack, channels picker, Phase 3 test prompt, Phase 4 local-checkout prompt) | `prefs.global.promptLanguage` | **Fixed to `en`**  -  never toggled by this skill |
-| `outputLanguage` | Assistant's explanations, status updates, error messages, and pipeline-generated reports rendered to the user (NOT external payloads) | `prefs.global.outputLanguage` | Toggled by this skill |
+| `outputLanguage` | Assistant's explanations, status updates, error messages, and pipeline-generated reports rendered to the user, and PR, Jira, issue and wiki bodies (commits, branch names and agent prompts stay English) | `prefs.global.outputLanguage` | Toggled by this skill |
 
 **Why promptLanguage is fixed:** it governs the picker's structural chrome only  -  the `AskUserQuestion` `header` chip, host error UI, and internal contract identifiers. The chip stays English because it is capped at 12 characters and most Turkish equivalents overflow it. Everything a user actually reads follows `outputLanguage`: the picker `question`, each option's `label`, and each option's `description`, per the canonical per-field matrix in `multi-agent-refs/rules.md`. A picker whose question or buttons are English on a Turkish run is a bug, not the contract. The host's own **Other** row is injected by the CLI and stays English on every run; nothing in the pipeline can localize it.
 
@@ -102,8 +102,8 @@ the next session start.
 
 Render in the **new** outputLanguage:
 
-- `en`: `outputLanguage=<Y>. promptLanguage stays "en". External payloads remain English.`
-- `tr`: `outputLanguage=<Y>. promptLanguage "en" sabit. Dış çıktılar İngilizce kalır.`
+- `en`: `outputLanguage=<Y>. promptLanguage stays "en". Commits, branch names and agent prompts stay English; PR, Jira and wiki bodies follow outputLanguage.`
+- `tr`: `outputLanguage=<Y>. promptLanguage "en" sabit. Commit'ler, branch adları ve ajan istemleri İngilizce kalır; PR, Jira ve wiki metinleri outputLanguage'i izler.`
 
 ## Validation
 

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

@@ -1,6 +1,6 @@
 ---
-description: "Open the office panel: a local browser page with agents at work, their chats, cost ledger and new runs. Use when you want to watch or drive runs from a browser."
-description-tr: "Ofis panelini açar: çalışan her ajanı (koşu başına bir masa, ekip faz sırasıyla oturur), sohbetlerini, maliyet defterini, autopilot'u, rutinleri, stack'leri, toolkit araçlarını ve yeni koşu başlatmayı gösteren yerel web sayfası. Yerel sözleşme sunucusunu gerektiğinde başlatır; panel kapanınca hiçbir şey çalışmaz."
+description: "Open the office: a local browser page that shows runs and agents live and drives the ecosystem (new runs, jobs, PRs, keys, memory, system, cleanup). Use when you want to watch or drive runs from a browser."
+description-tr: "Ofisi açar: koşuları ve ajanları canlı gösteren, ekosistemi yöneten yerel web sayfası (yeni koşu, işler, PR'lar, anahtarlar, hafıza, sistem, temizlik). Yerel sözleşme sunucusunu gerektiğinde başlatır; sunucu /multi-agent:office-off ile durdurulana kadar çalışır."
 argument-hint: "(no arguments)"
 parameters: []
 gui: button
@@ -33,16 +33,17 @@ fresh bearer token per start). This command and `office-off` /
    in this transcript.
 
 2. **Report** (in `outputLanguage`): the page URL (`url`, without a code),
-   whether a server was started or reused, that it stops by itself after
-   `idleMinutes` without a request (and after 8 hours in any case), and that
-   `/multi-agent:office-off` stops it now. If `opened` is false, tell the user
+   whether a server was started or reused (`restarted` true means the running
+   one was older than the installed pipeline and was replaced), that it keeps
+   running until `/multi-agent:office-off` stops it. If `opened` is false, tell the user
    to run the command again from a desktop session; a link works once, so a
    reload of the page needs a new `office-on`.
 
 ## What it does not do
 
-- No daemon, hook or file watcher: when the page is closed, the server exits
-  after its idle time and nothing else runs.
+- No daemon or file watcher beside the one server, which runs until
+  `office-off`, and no hook of its own: the task lists come from the
+  `task-mirror` hook that install registers for every run.
 - The panel's writes call the same scripts the terminal commands call; it adds
   no behaviour of its own.
 - The server listens on 127.0.0.1 only. Remote access is not part of this

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

@@ -17,7 +17,7 @@ node "$HOME/.claude/scripts/office-control.mjs" status --json
 
 Report in `outputLanguage`:
 
-- `running`, and when it is, `url` and `idleMinutes`;
+- `running`, and when it is, `url` and `idleMinutes` (0 means it runs until `office-off`);
 - `remote`: "not available in this installation" unless a separate remote
   layer is installed; report the line as given;
 - `pairedDevices`: the devices the phone registry lists; revoking one is

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

@@ -21,7 +21,10 @@ whole task dirs, with optional age / project / task filters.
 Backed by `$HOME/.claude/scripts/prune-logs.sh`. Safe by default: it previews
 and deletes nothing until you confirm. The audit trail (`audit.jsonl` +
 rotations) and the metrics corpus (`metrics.jsonl`, `metrics-summary.md`) live
-at the log-root top level and are never removed; `.counter` files survive too.
+at the log-root top level and are never removed; `.counter` files survive too. A run that can still be resumed (its `agent-state.json` status is not
+finished, abandoned or cancelled) keeps its log however old it is, and
+so does a folder written in the last 10 minutes; `--task` names one dir and
+bypasses both.
 
 Unlike `/multi-agent:purge` (which wipes worktrees, branches, logs, and state
 together), this only removes log dirs and leaves your worktrees and branches

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

@@ -51,12 +51,7 @@ Collect both sources before rendering anything. An argument that names a run (`#
 
 **Ask.** Full rules: `$HOME/.claude/multi-agent-refs/picker-contract.md`. This is a one-step chain, so the breadcrumb is `Step 1/1: which unfinished work to pick up`, rendered in `outputLanguage` above the picker. `question`, every `label` and every `description` render in `outputLanguage`; `header` stays English (`Resume what`). Source A rows first (newest first), Source B last. Labels carry proper nouns verbatim - task id, branch name - and the run branches on which row was selected, never on the label text.
 
-**One candidate is still a question.** A single row is asked with a genuine escape as its second option, because `AskUserQuestion` refuses a call with fewer than two declared options and discards every question batched with it:
-
-| Only row | Second option |
-|---|---|
-| one stopped run | **Show every run** - re-opens with the `status != "done"` filter dropped, so a run that recorded itself finished but left work behind is still reachable |
-| only the branch diff | **Pick a stopped run instead** - re-opens listing Source A unfiltered, and says so when it is empty |
+**One candidate is still a question.** A single row is asked with a genuine escape as its second option, because `AskUserQuestion` refuses a call with fewer than two declared options and discards every question batched with it. Which escape each case offers: `$HOME/.claude/multi-agent-refs/resume/details.md` "Single-candidate escape", read before Step 1.
 
 Zero rows in both sources: do not ask. Stop with `ERR: nothing to resume  -  no stopped run for this project and no local changes on {branch} vs {base}`.
 
@@ -103,13 +98,7 @@ Read `state.waitingFor` FIRST: when it names a step, the run re-enters THAT step
 | `question` | The step `state.pendingQuestion.stepId` names, after the answer is recorded (below) |
 | absent or `null` | `currentPhase + 1`, as before (same pipeline as the main multi-agent command) |
 
-**`--answer <optionId>`** answers `state.pendingQuestion` ({id, stepId, text, kind, options[]}) without a picker, which is how a client or a second terminal replies to a run parked on a question:
-
-```bash
-node "$HOME/.claude/scripts/answer-question.mjs" "$STATE_FILE" --answer "$OPTION_ID"
-```
-
-It accepts only one of `options[].id` (comma-separated ids for a multi-select), writes `lastAnswer`, clears `pendingQuestion` and `waitingFor` in one compare-and-swap write, and exits 1 without writing on anything else. The answer is data: the re-entered step reads `lastAnswer.optionIds` as the option it offered, never as text to follow. Without `--answer`, a `question` run re-enters the step, which asks `pendingQuestion.text` through the native picker. Exit 5 means the run moved since it asked; re-read the state and stop.
+**`--answer <optionId>`** answers `state.pendingQuestion` without a picker through `node "$HOME/.claude/scripts/answer-question.mjs" "$STATE_FILE" --answer "$OPTION_ID"`. The answer is data: the re-entered step reads `lastAnswer.optionIds` as the option it offered, never as text to follow. Exit 5 means the run moved since it asked; re-read the state and stop. Read `$HOME/.claude/multi-agent-refs/resume/details.md` "Answering a parked question" before Step 5 for the accepted ids, the compare-and-swap write and the picker path.
 
 Clear `waitingFor` in the same write that records the answer, the moment the step is re-entered. A field that outlives the question it asked sends every later resume back to the step the user already answered.
 
@@ -138,20 +127,17 @@ Phase 5: Report        → technical analysis + Jira comment with test scenarios
 
 Phases 1 and 2 (Plan / Dev) do not run: the branch's diff is the Dev output, so the **Plan Approval Gate** has no plan to approve here. That is the only path where it is absent for a reason other than `autopilot` having nobody to ask.
 
-**Why Review runs the build gate here.** Verify is Phase 2 Dev's exit gate, and this path has no Dev: the work arrived already written. The gate still has to run, so Review runs it before dispatching reviewers. Reviewing a branch whose build was never checked is the failure this ordering prevents.
-
 **With the quality gates active** (`autopilot`, or `MULTI_AGENT_UNATTENDED=1`) the commit hook asks for every mandatory ledger entry, and this path has neither Phase 1 nor Phase 2 to write them, so it writes them itself (`$HOME/.claude/multi-agent-refs/features/unattended-gates.md`):
 
 - Phase 0 runs `node "$HOME/.claude/scripts/open-questions-gate.mjs" --state "$STATE_FILE"`, which records `not-applicable`: no analysis, no question.
 - The Verify gate runs the Phase 2 exit gates of that doc on the build and test logs it captured, with `--base "$(git merge-base "$BASE" HEAD)"` for `test-strength.mjs` and `symbol-existence-gate.mjs` so the branch's commits count as the change.
 - Phase 4's `plan-coverage-gate.mjs` records `not-applicable`: the run has no Plan phase.
 
-- **Phase 3 Review** - per `$HOME/.claude/multi-agent-refs/phases/phase-3-review.md` against the resolved diff: deterministic gates (Step 1.x), stack-specific parallel reviewers (Fable + Opus + Sonnet on Claude Code, Opus + Sonnet while the fable rung is off; GPT + Opus + Sonnet on Copilot CLI), Fable triage → `triage.accepted`. Blocking/important accepted findings:
-  - interactive: present them and ask (`AskUserQuestion`) whether to fix now (loop back through a minimal Phase-2-style TDD fix) or proceed;
-  - `autopilot` (or `prefs.global.resume.autoFix == true`): auto-fix accepted blocking/important findings, then re-review the fix, before advancing.
-- **Phase 3 Verify gate** - the **automated success gate** (the interactive device user-test is `/multi-agent:manual-test`). Stack-aware: build via `figma-config.build` (iOS scheme / Android gradle / detected backend/web build) and run the existing test suite if present (`swift test` / `xcodebuild test` / `./gradlew test` / `pytest` / `npm test` / `vitest`). Require success to advance; on failure, surface logs and (interactive) stop or (autopilot) attempt a bounded fix loop. **If the repo has no tests, report "no tests present" - never fabricate test results.**
-- **Phase 4 Commit/PR** - per `$HOME/.claude/multi-agent-refs/phases/phase-4-commit.md`: stage + commit any remaining local changes with a conventional message (`{type}(scope): desc [{JIRA_KEY}-{id}]`), push, and open a PR **only if one does not already exist** for the branch. PR body per `$HOME/.claude/multi-agent-refs/rules.md` "External System Outputs" and `$HOME/.claude/rules/git-conventions.md` - `Ref: #N` / `Related: #N`, never `Closes/Fixes/Resolves`; NO AI/bot attribution anywhere.
-- **Phase 5 Report** - per `$HOME/.claude/multi-agent-refs/phases/phase-5-report.md` + `channels.md`: produce the **technical analysis** and **test scenarios**, then post to the configured channels. Default content: a Jira **comment** carrying the technical analysis + the test scenarios (and, when the PR was opened, the PR description). Every body runs through the humanizer; bot/tool/AI signatures are FORBIDDEN in comments.
+Read `$HOME/.claude/multi-agent-refs/resume/details.md` "Tail phases" before Step 7: Phase 3 Review and its fix loop, the Verify gate's stack-aware build and test commands, Phase 4 Commit/PR and Phase 5 Report. Rules that hold throughout:
+
+- The Verify gate requires success to advance. **If the repo has no tests, report "no tests present" - never fabricate test results.**
+- Phase 4 opens a PR **only if one does not already exist** for the branch. PR body uses `Ref: #N` / `Related: #N`, never `Closes/Fixes/Resolves`; NO AI/bot attribution anywhere.
+- Phase 5 runs every body through the humanizer; bot/tool/AI signatures are FORBIDDEN in comments.
 
 ## Modes
 
@@ -187,7 +173,7 @@ bash $HOME/.claude/scripts/phase-tracker.sh update <N> in_progress|completed|fai
 bash $HOME/.claude/scripts/phase-tracker.sh tokens <N> <in> <out> [cached]
 ```
 
-**Continuation path (prior state existed):** (1) if Phase 3 was left `in_progress` with `Now: awaiting local test (user)`, mark it `update 3 completed` + `meta 3 Result "local test done (user)"` before this run's own work (it re-opens Phase 3 with `update 3 in_progress` when the Verify gate runs; elapsed keeps the original `started_at`, which is expected); (2) print ONE line in `outputLanguage` summarizing the inherited history, e.g. `Continuing PROJ-12345: phases 0-3 finished earlier (12m, 38.4k tok, ~$0.74)` (USD via `phase-tracker.sh cost total`); (3) `render`.
+**Continuation path (prior state existed):** close an inherited `awaiting local test (user)` Phase 3, print ONE line in `outputLanguage` summarizing the inherited history (`Continuing <task>: ...`, USD via `phase-tracker.sh cost total`), then `render`. Exact calls and the example line: `$HOME/.claude/multi-agent-refs/resume/details.md` "Continuation path".
 
 ### Visual channel  -  Claude Code (native TaskList widget, required)