@mmerterden/multi-agent-pipeline 17.0.0 → 17.3.0

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

@@ -0,0 +1,64 @@
+---
+name: multi-agent-autopilot-status
+language: en
+description: "Show what continuous mode is doing here: what runs at which phase, what is queued, what waits for an answer, what PRs it opened today. Use when asked whether autopilot is on."
+user-invocable: true
+argument-hint: "[--subjects]  -  --subjects prints one widget line per in-flight item"
+---
+
+
+# multi-agent autopilot-status  -  what is it doing
+
+```bash
+bash "$HOME/.claude/scripts/autopilot-status.sh" ${ARGUMENTS}
+```
+
+That script is the **only** producer. The menu bar indicator, this command and
+the session-start hook all render the same `status.json` it writes, because the
+moment each computes its own answer they start disagreeing - which is the failure
+this whole area was built around: a run reading `in_progress` while its PR was
+already open.
+
+## What the output means
+
+| Line | Meaning |
+|---|---|
+| `KAPALI` with repos selected | the selection is kept, launchd holds no job. `autopilot-on` starts it again without re-asking |
+| `kurulu değil` | never configured on this machine; nothing has been written |
+| `Koşuyor` | in flight now. Phase and elapsed come from the run's own state, not from a guess |
+| `Cevap bekliyor` | the item was not mature enough, the open questions were posted as a comment, and it resumes on its own once answered |
+| `config açık ama launchd'de iş yok` | the failure a `resume` command would have hidden: an OS update dropped the plist, or it was booted out. Re-run `autopilot-on` |
+
+An empty queue is reported with the reason - no item carries the label yet - and
+not as an error. That is the most common "why is nothing happening", and it is
+not a fault.
+
+## The menu bar indicator
+
+When `swiftc` was available at `autopilot-on` time, `~/.claude/autopilot/bin/menubar`
+shows the same thing in the top right, refreshing on its own: one row per item
+with its id, whether it is running Full or Short, the phase as a fraction, the
+elapsed time and the stack, then the queue, then what is waiting, then the PRs of
+the last day - each one clickable.
+
+The indicator only **draws**. It cannot start, stop or change a run: control
+stays here, where it is confirmed. It disappears from the list the moment an item
+finishes, and the item reappears under `Raporlar` with its PR.
+
+No `swiftc` means no indicator and nothing else changes.
+
+## `--subjects`
+
+One line per in-flight item, shaped for the native task widget, with the numbers
+travelling **inside** the subject string because the widget takes exactly one
+string per row:
+
+```
+PROJ-1234 · Full · Faz 3/8 Dev · ios
+PROJ-1199 · cevap bekliyor
+```
+
+Honest limit, worth saying rather than discovering: that widget belongs to the
+session that calls `TaskUpdate`, and it refreshes when that session takes a turn -
+when you type, or when a hook fires. It is a view, not a live counter. The menu
+bar indicator is the one that updates on its own.

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

@@ -105,22 +105,69 @@ GitHub uses `gh pr edit --body-file`  -  reviewers independent, no risk.
 
 ### Jira comment (wiki markup)
 
+Four sections in this fixed order, the PR link on line 1. Jira is read by the
+person who filed the ticket and by whoever tests it, so the comment carries the
+development summary, the scenarios to run and the impact - never class names,
+never file paths, never a diff walk. The technical view lives in the PR, one
+click away through that first line.
+
 ```
 PR: {prUrl}
 
-*Root cause:* {single paragraph summary}
+h2. Geliştirme Özeti
+
+{2-5 sentences: what changed, where the user meets it, and the size of the
+effect when it is measurable}
+
+h2. Test Senaryoları
+
+*1. {what this scenario exercises}*
+# {step the tester performs, in the app's own words}
+# {step}
+# *Beklenen:* {what they should see}
+
+*2. {regression scenario}*
+# {step}
+# *Beklenen:* {what should still behave as before}
+
+h2. Etki Analizi
+
+*1 - Problemin Tanımı*
+{what was wrong and since when}
+
+*2 - Yapılan Geliştirme*
+{what the change does, and why the behaviour around it is unchanged}
 
-*Solution:*
-- {{file.ext → func}}  -  {one line}
+*3 - Etkilenen Fonksiyonlar*
+{the screens and flows that must be tested}
 
-*Changed files:* file.ext (+N/-M), other.ext (+N/-M)
+*4 - Diğer Sistemlere Etkisi*
+{none, or which service, contract or channel}
 
-*Test scenarios:*
-# Scenario 1
-# Scenario 2
+h2. Bağlantılar
+
+* Crashlytics / Confluence / Figma: {url}
+```
+
+Reproduction scenarios first, then regressions for whatever the change could
+have disturbed. Full contract: `channels/jira.md`.
+
+`{{file.ext → func}}`, `*Root cause:*` and `*Changed files:*` used to be this
+template. They are gone deliberately: that shape put a hash-table mutation
+walk in front of a tester, and `{{file → func}}` is exactly where a Swift
+selector like `hash(into:)` ends up - whose trailing `:)` Jira renders as a
+smiley.
+
+**Post through the publisher, never a hand-rolled `curl`:**
+
+```bash
+bash "$HOME/.claude/lib/jira-publish.sh" --issue "$JIRA_ID" --body-file "$F" --target comment
 ```
 
-First line: PR URL (one-click jump). Run the converted body through `node "$HOME/.claude/scripts/jira-wiki-escape.mjs"` before POST  -  Jira turns `:)` `(x)` `(!)` `(/)` into emoticon images, including inside `{{monospace}}`. POST `/rest/api/2/issue/{id}/comment` with heredoc + `jq --rawfile` + `curl --data-binary @file` from the escaped file. Real newlines, no HTML entities.
+It escapes every body unconditionally before sending and keeps the token off
+argv. Jira turns `:)` `(x)` `(!)` `(/)` into emoticon images, including inside
+`{{monospace}}`; an escape that has to be remembered is one that is eventually
+forgotten, and that is how the selector above shipped.
 
 ### Confluence page
 
@@ -165,9 +212,13 @@ First line: PR URL (one-click jump). Run the converted body through `node "$HOME
 | `path/to/File.ext` | +N / -M |
 
 ### Test Scenarios                  ← if "Test senaryoları" OR "Auto-diff"
-| # | Precondition | Steps | Expected | Status |
-|---|--------------|-------|----------|--------|
-| 1 | ...          | ...   | ...      | To Test|
+**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}
 
 ### Notes                           ← if "Manuel not" selected
 {user message}

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

@@ -32,8 +32,8 @@ Run all steps automatically:
 ```
 Step 0: DOCTOR      node $HOME/.claude/scripts/doctor.mjs  -  exit 2 or 4 STOPS the sync
 Step 1: DETECT      Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 53 sub-command skills)
-Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 53 specs as refs + 8 agent TOML)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 56 sub-command skills)
+Step 2b: CODEX      Claude Code -> Codex CLI (1 router skill + 56 specs as refs + 8 agent TOML)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub)
 Step 3d: DEV-TOOLKIT Companion MCP server -> detect movement, ship gates, commit + publish
 Step 4: WEBSITE     Version + phase/model counts -> {website-host} (i18n + projects.ts)
@@ -101,7 +101,7 @@ If nothing is stale -> report "All targets up to date" and stop.
 ## Codex Sync (Step 2b)
 
 This step does **not** hand-copy files. The Codex tree is a *transform* of the Claude
-tree, not a mirror: the 53 sub-command specs become reference files (Codex silently
+tree, not a mirror: the 56 sub-command specs become reference files (Codex silently
 truncates its skills block  -  see `cross-cli-contract.md` 2.6), every reference to a
 CLI-owned tree is retargeted (`agents/<persona>.md` becomes `.toml`, the dispatcher
 becomes the router skill), the 8 personas are regenerated as TOML with a model +
@@ -228,13 +228,14 @@ When invoked with the `release` argument:
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}/SKILL.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**53 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**56 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
-analysis, analysis-jira, analysis-resolve, autopilot, build-optimize, channels,
-complaint-analysis, create-jira, design-check, doctor, diff-explain, feedback,
-forget, garbage-collect, graph, help, ios-coding-standard, issue, jira,
-kill, language, local, local-autopilot, log, manual-test, prune-logs,
+analysis, analysis-jira, analysis-resolve, autopilot, autopilot-off,
+autopilot-on, autopilot-status, build-optimize, channels, complaint-analysis,
+create-jira, design-check, diff-explain, doctor, feedback, forget,
+garbage-collect, graph, help, ios-coding-standard, issue, jira, kill,
+language, local, local-autopilot, log, manual-test, prune-logs,
 prune-prompts, purge, refactor, resume, resume-local, review,
 review-analysis, review-issue, review-jira, routines, save, scan, search,
 setup, stack, status, steer, store-ready, sync, test, test-accessibility,