@mmerterden/multi-agent-pipeline 17.0.0 → 17.1.0

package/CHANGELOG.md

@@ -14,6 +14,38 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ---
 
+## [17.1.0] - 2026-09-14
+
+Continuous mode, and three things that were computed correctly and shown to
+nobody: the plan's own steps, a web repo's UI tests, and the queue's status when
+one field arrived as a number.
+
+### Added
+
+- **Continuous mode.** `/multi-agent:autopilot-on` picks the repos ONE machine watches; labelled GitHub issues and assigned + labelled Jira items then run in a worktree and stop at an open PR. `:autopilot-status` is the single producer the terminal, the menu bar indicator and the session hook all render, `:autopilot-off` removes the schedule and keeps the selection. Nothing is on by default: installing writes no state and schedules nothing, and `smoke-autopilot-default-off.sh` fails the build if that changes.
+
+  The ordering is deterministic with no model call - explicit rank, repo grouping, priority, then OLDEST first, which is the opposite of the `jira` picker on purpose: a human wants what just landed, an unattended queue must not starve what has been waiting. Two preconditions are checked before any item is taken: a rolling 24-hour spend total, and a per-source credential gate, so a dead Jira token stops Jira items without stopping GitHub ones.
+
+  A menu bar indicator draws the same `status.json` in the top right when `swiftc` is present. ActivityKit is `@available(macOS, unavailable)` - there is no Live Activity on a Mac - so this is an `NSStatusItem`, built from source on demand rather than shipped as a binary that would need signing.
+
+- **UI tests on web.** `run-ui-tests.sh` rejected every platform but `ios|android`, so a repo with a full Playwright suite reported "no UI test target" and the PR body said UI tests had not run - a statement true of the runner and false of the repo. Detection keys on the browser-driving import (`@playwright/test`, `cy.visit(`), not on a directory called `e2e`: the same distinction that keeps 475 iOS snapshot tests from being counted as UI tests.
+
+### Changed
+
+- **The Jira comment and the PR body stopped being the same document.** Jira now carries Geliştirme Özeti, Test Senaryoları, Etki Analizi and Bağlantılar with the PR link on line 1 and no identifiers, file paths or diff hunks anywhere in it. The PR keeps all of that and gains Teknik Açıklama, Etki Analizi and Build - the build command, its result and the base sha it ran against. Given/When/Then is gone from the scenarios: it reads as translated English to the person running them, who wants a titled list they can follow with the app open.
+
+### Fixed
+
+- **The menu bar indicator read "autopilot kapalı" with items in flight.** `phase` was declared `String?` while the producer passes the queue's own value through `jq` untouched, so a numeric phase made Swift's `Decodable` throw - and the throw did not lose one field, it failed the whole document. A silent blank is the worst failure a status indicator has, because it is indistinguishable from good news.
+
+- **`ma_ap_boottime` returned the microseconds.** `.*sec = ` is greedy and walks past `sec` into `usec`, so the helper produced a six-digit number that looked plausible and never equalled the same fact read anywhere else. It surfaced as a live runner being declared dead.
+
+- **Three phase documents said "MCP forbidden" without qualifying it**, while the gate that enforces it has always matched `figma` and nothing else. The prose therefore banned the screenshot, xcodebuild and UI-test tools that Phase 3 itself calls, which is one way a run reaches Phase 7 with no evidence.
+
+- **`channels/jira.md` told Phase 7 to upload evidence Phase 6 had already uploaded**, so re-rendering a comment attached every file a second time.
+
+---
+
 ## [17.0.0] - 2026-09-14
 
 Five things in this release were not working, and four of them looked like they

package/README.md

@@ -89,7 +89,7 @@ Depth, autopilot and `--local` are the only knobs on the run itself; everything
 
 ## Commands
 
-`/multi-agent` plus 53 sub-commands. `/multi-agent:help` renders the same catalog in your terminal, in your `outputLanguage`.
+`/multi-agent` plus 56 sub-commands. `/multi-agent:help` renders the same catalog in your terminal, in your `outputLanguage`.
 
 ### Pipeline entries
 
@@ -195,6 +195,51 @@ Eight are installed alongside the commands and dispatched by the phases: `explor
 
 Two compliance skills install on every host and back the store gates: `apple-archive-compliance` (18-rule Apple review scan with ITMS code mapping) and `google-play-compliance` (21-rule Play policy catalog with Console error codes). Everything else stack-shaped - SwiftUI, Compose, backend, frontend - comes from the marketplace plugins described below.
 
+## Continuous mode
+
+Everything above starts when you start it. Continuous mode is the same pipeline
+picking work up on its own, on ONE machine you choose, from repos you choose.
+
+| Command | What it does |
+| --- | --- |
+| `/multi-agent:autopilot-on` | Pick the repos this machine watches. Labelled GitHub issues and assigned + labelled Jira items then run in a worktree and stop at an open PR. Re-run to change the list |
+| `/multi-agent:autopilot-status` | What is running and at which phase, what is queued, what is waiting for an answer, the PRs of the last day, and the rolling spend |
+| `/multi-agent:autopilot-off` | Remove the schedule. Work already running finishes; the repo selection is kept |
+
+**Nothing is on by default and nothing is added implicitly.** Installing the
+package writes no state and schedules nothing; `smoke-autopilot-default-off.sh`
+fails the build if that ever changes. A label is a filter, not a gate - anyone
+who can open an issue in a repo you have push on could add one - so the gate is
+the picker, and it is per machine.
+
+The biggest win is not parallelism. Measured here, the median run is 44 minutes,
+but an item that finishes at 14:00 waits until you sit down again: overnight that
+is 16 hours against 40 minutes. Continuous mode removes the waiting, not the work.
+
+**What it will not do.** It does not merge - the runner stops at an open PR and
+the decision stays yours. It does not touch an attended run: per-repo concurrency
+is always 1, so the queue steps around a repo you are working in rather than
+competing for `.git/index.lock`. There is no cap on PRs; the bounds are
+`costCeilingUsd` over a rolling 24 hours and what the machine can hold.
+
+**A menu bar indicator**, when `swiftc` is present, draws the same `status.json`
+in the top right and refreshes on its own: one row per item with its id, Full or
+Short, the phase as a fraction, the elapsed time and the stack. A row disappears
+the moment the item finishes and reappears under Reports with its PR. It only
+draws - it cannot start, stop or change a run. ActivityKit is unavailable on
+macOS, so this is an `NSStatusItem`, built from source on demand rather than
+shipped as a binary that would need signing.
+
+**It survives a restart with no command to run.** launchd loads the job at
+**login**, not at boot, and that is correct rather than a limitation: the login
+keychain is what unlocks the tokens, so a tick that fired before login could not
+reach Jira or GitHub anyway. There is no `autopilot-resume` - a command you have
+to remember is a queue that silently stops when you forget it. `doctor` reports
+the real failure instead: configured, but launchd holds no job.
+
+Sleep is held **only on AC**. A queue that flattens a laptop off the charger is a
+bug; on battery the assertion is released and work resumes when you plug in.
+
 ## Stacks
 
 Stack skills ship as versioned plugins in the [`mmerterden/multi-agent-plugins`](https://github.com/mmerterden/multi-agent-plugins) marketplace. Select a stack per-repo:
@@ -207,13 +252,13 @@ This enables the matching plugin (+ the shared `ai-common` plugin) in the repo's
 
 ## Tool support
 
-The pipeline runs natively on **Claude Code**, **Copilot CLI** and **Codex CLI** - all three install from the same `pipeline/` source and get the same 53 commands.
+The pipeline runs natively on **Claude Code**, **Copilot CLI** and **Codex CLI** - all three install from the same `pipeline/` source and get the same 56 commands.
 
 | Tool        | Flag                 | What it installs                                                                                       |
 | ----------- | -------------------- | ------------------------------------------------------------------------------------------------------ |
 | Claude Code | `--claude` (default) | slash commands + skills + agents + three `PreToolUse` hooks (secret scan, agent-guard, read-size gate) |
-| Copilot CLI | `--copilot`          | instructions + 53 sub-command skills + scripts                                                         |
-| Codex CLI   | `--codex`            | one router skill + 53 specs as refs + 8 agent TOML + `AGENTS.md` block + `codex mcp add`               |
+| Copilot CLI | `--copilot`          | instructions + 56 sub-command skills + scripts                                                         |
+| Codex CLI   | `--codex`            | one router skill + 56 specs as refs + 8 agent TOML + `AGENTS.md` block + `codex mcp add`               |
 
 Filter skills by stack with `--platform=ios\|android\|all`.
 

package/README.tr.md

@@ -89,7 +89,7 @@ Koşunun kendisinde ayarlanabilen tek şey derinlik, autopilot ve `--local`; ger
 
 ## Komutlar
 
-`/multi-agent` ve 51 alt komut. `/multi-agent:help` aynı katalogu terminalde, `outputLanguage` ayarına göre gösterir.
+`/multi-agent` ve 56 alt komut. `/multi-agent:help` aynı katalogu terminalde, `outputLanguage` ayarına göre gösterir.
 
 ### Pipeline girişleri
 
@@ -195,6 +195,52 @@ Komutlarla birlikte sekiz agent kurulur ve fazlar bunları çağırır: `explore
 
 İki uyumluluk skill'i her host'a kurulur ve store kapılarını besler: `apple-archive-compliance` (ITMS kod eşlemeli 18 kurallı Apple review taraması) ve `google-play-compliance` (Console hata kodlu 21 kurallı Play politika kataloğu). Stack'e bağlı geri kalan her şey - SwiftUI, Compose, backend, frontend - aşağıda anlatılan marketplace plugin'lerinden gelir.
 
+## Sürekli mod
+
+Yukarıdaki her şey sen başlattığında başlar. Sürekli mod, aynı pipeline'ın
+**senin seçtiğin tek makinede**, **senin seçtiğin repolardan** işi kendi başına
+alması.
+
+| Komut | Ne yapar |
+| --- | --- |
+| `/multi-agent:autopilot-on` | Bu makinenin izleyeceği repoları seçersin. Etiketli GitHub issue'ları ve sana atanmış + etiketli Jira maddeleri worktree'de koşar, açık PR'da durur. Listeyi değiştirmek için tekrar çalıştır |
+| `/multi-agent:autopilot-status` | Ne koşuyor hangi fazda, sırada ne var, ne cevap bekliyor, son bir günün PR'ları ve yuvarlanan harcama |
+| `/multi-agent:autopilot-off` | Zamanlamayı kaldırır. Koşan iş biter; repo seçimi saklanır |
+
+**Varsayılan olarak hiçbir şey açık değil ve hiçbir repo kendiliğinden eklenmez.**
+Paketi kurmak ne durum yazar ne zamanlama kurar; bu bir gün değişirse
+`smoke-autopilot-default-off.sh` derlemeyi düşürür. Etiket bir filtredir, kapı
+değil - push yetkin olan bir repoda issue açabilen herkes etiket ekleyebilir -
+o yüzden kapı picker'dır ve makine başınadır.
+
+En büyük kazanç paralellik değil. Ölçüm: medyan koşu 44 dakika, ama 14:00'te
+biten bir madde sen masaya oturana kadar bekler; gece boyunca bu 40 dakikaya
+karşı **16 saat**. Sürekli mod işi değil, beklemeyi kaldırıyor.
+
+**Yapmayacakları.** Merge etmez - koşucu açık PR'da durur, karar sende kalır.
+Senin elle koşturduğun bir işe dokunmaz: repo başına eşzamanlılık her zaman 1,
+yani kuyruk senin çalıştığın repoyu `.git/index.lock` için yarışmak yerine atlar.
+PR sayısına tavan yok; sınırlar 24 saatlik yuvarlanan `costCeilingUsd` ve
+makinenin kapasitesi.
+
+**`swiftc` varsa menü çubuğu göstergesi** aynı `status.json`'ı sağ üstte çizer ve
+kendi kendine tazelenir: madde başına tek satır - id, Full ya da Short, kesir
+olarak faz, geçen süre, stack. Madde biter bitmez satır kaybolur ve PR'ıyla
+Raporlar altında görünür. Yalnızca **çizer**; bir koşuyu başlatamaz, durduramaz,
+değiştiremez. ActivityKit macOS'ta yok, o yüzden bu bir `NSStatusItem` ve
+imzalanması gerekecek bir ikili olarak değil, yerinde kaynaktan derleniyor.
+
+**Yeniden başlatmadan sonra çalıştırman gereken komut yok.** launchd işi
+**girişte** yükler, boot'ta değil - ve bu bir eksiklik değil doğrusu: token'ları
+açan şey login keychain'in açılması, giriş öncesi ateşlenen bir tick zaten ne
+Jira'ya ne GitHub'a bağlanabilirdi. `autopilot-resume` diye bir komut yok -
+hatırlanması gereken komut, unutulduğunda sessizce duran kuyruk demektir.
+Bunun yerine `doctor` gerçek arızayı söyler: kurulu, ama launchd'de iş yok.
+
+Uyku **yalnızca prizdeyken** engellenir. Prizde olmayan bir laptop'u boşaltan
+kuyruk hatadır; bataryada assertion bırakılır ve prize takınca kaldığı yerden
+devam eder.
+
 ## Stack'ler
 
 Stack skill'leri [`mmerterden/multi-agent-plugins`](https://github.com/mmerterden/multi-agent-plugins) marketplace'inde versiyonlu plugin'ler olarak gönderilir. Repo başına bir stack seç:
@@ -207,13 +253,13 @@ Bu, ilgili plugin'i (+ ortak `ai-common` plugin'ini) repo'nun `.claude/settings.
 
 ## Araç desteği
 
-Pipeline **Claude Code**, **Copilot CLI** ve **Codex CLI** üzerinde native çalışır - üçü de aynı `pipeline/` kaynağından kurulur ve aynı 53 komutu alır.
+Pipeline **Claude Code**, **Copilot CLI** ve **Codex CLI** üzerinde native çalışır - üçü de aynı `pipeline/` kaynağından kurulur ve aynı 56 komutu alır.
 
 | Araç        | Bayrak                  | Ne kurar                                                                                                         |
 | ----------- | ----------------------- | ---------------------------------------------------------------------------------------------------------------- |
 | Claude Code | `--claude` (varsayılan) | slash komutları + skill'ler + agent'lar + üç `PreToolUse` hook'u (secret scan, agent-guard, okuma-boyutu geçidi) |
-| Copilot CLI | `--copilot`             | talimatlar + 53 alt-komut skill'i + script'ler                                                                   |
-| Codex CLI   | `--codex`               | bir router skill + ref olarak 53 spec + 8 agent TOML + `AGENTS.md` bloğu + `codex mcp add`                       |
+| Copilot CLI | `--copilot`             | talimatlar + 56 alt-komut skill'i + script'ler                                                                   |
+| Codex CLI   | `--codex`               | bir router skill + ref olarak 56 spec + 8 agent TOML + `AGENTS.md` bloğu + `codex mcp add`                       |
 
 Skill'leri stack'e göre filtrele: `--platform=ios\|android\|all`.
 

package/docs/architecture.md

@@ -117,7 +117,7 @@ graph TB
     end
 
     subgraph "Pipeline Specs"
-        CMD[commands/<br/>53 command files]
+        CMD[commands/<br/>56 command files]
         AGT[agents/<br/>8 agent personas]
         RUL[rules/<br/>12 domain rules]
         PHS[multi-agent-refs/phases/<br/>phase specs + contracts]
@@ -169,8 +169,8 @@ revisions of this diagram - Codex CLI and the two independently-shipped repos
 ```mermaid
 graph TD
     CC["Claude Code<br/>(source of truth)"]
-    COP["Copilot CLI<br/>(instructions + 53 skills)"]
-    COD["Codex CLI<br/>(1 router skill + 53 refs)"]
+    COP["Copilot CLI<br/>(instructions + 56 skills)"]
+    COD["Codex CLI<br/>(1 router skill + 56 refs)"]
     REPO["Pipeline Repo<br/>(npm package)"]
     WEB["Website"]
     PLUGREPO["multi-agent-plugins<br/>(5 stack plugins, own repo)"]

package/docs/ecosystem.md

@@ -5,7 +5,7 @@ separately, wired together at install time and at run time:
 
 | Repo | What it owns | Ships as |
 |---|---|---|
-| **`multi-agent-pipeline`** (this repo) | Orchestration: the 8-phase flow, the 53 slash commands, quality gates, review/triage, cross-CLI parity | npm package (`@mmerterden/multi-agent-pipeline`), installs itself onto Claude Code / Copilot CLI / Codex CLI |
+| **`multi-agent-pipeline`** (this repo) | Orchestration: the 8-phase flow, the 56 slash commands, quality gates, review/triage, cross-CLI parity | npm package (`@mmerterden/multi-agent-pipeline`), installs itself onto Claude Code / Copilot CLI / Codex CLI |
 | **`multi-agent-plugins`** | Stack knowledge: per-platform component/lifecycle skills (iOS, Android, Frontend, Backend) + shared knowledge | Claude Code marketplace, 5 independently-versioned plugins |
 | **`multi-agent-toolkit-mcp`** | The pipeline's hands on devices and browsers: 80 MCP tools across 6 categories (simulator/emulator control, accessibility audit, store compliance, web automation, Figma-vs-mock design audit, an agent-DSL batch runner) | npm package, registered as a standard stdio MCP server on every host |
 
@@ -18,7 +18,7 @@ Either can be swapped or removed without touching the other two's source.
 graph LR
     subgraph PIPE ["multi-agent-pipeline (orchestrator)"]
         direction TB
-        PHASES["8 phases · 53 commands"]
+        PHASES["8 phases · 56 commands"]
         GATES["deterministic gates + review triage"]
     end
 
@@ -64,8 +64,8 @@ only those:
 graph TD
     CC["Claude Code<br/>~/.claude/commands/multi-agent/<br/>(source of truth)"]
 
-    CC -->|"Step 2: copy + reformat<br/>53 sub-command skills"| COP["Copilot CLI<br/>~/.copilot/skills/"]
-    CC -->|"Step 2b: transform<br/>(install.js --codex)"| COD["Codex CLI<br/>1 router skill + 53 refs<br/>+ 8 agent TOML"]
+    CC -->|"Step 2: copy + reformat<br/>56 sub-command skills"| COP["Copilot CLI<br/>~/.copilot/skills/"]
+    CC -->|"Step 2b: transform<br/>(install.js --codex)"| COD["Codex CLI<br/>1 router skill + 56 refs<br/>+ 8 agent TOML"]
     CC -->|"Step 3: genericize<br/>(strip personal data)"| REPO["multi-agent-pipeline repo<br/>pipeline/"]
     CC -->|"Step 4: version + feature sync"| WEB["Website<br/>projects.ts / i18n.tsx"]
 
@@ -153,7 +153,7 @@ measurements behind this table):
 
 | | Claude Code | Copilot CLI | Codex CLI |
 |---|---|---|---|
-| **Pipeline commands** | 53 slash-command skills, native | 53 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 53 command specs as reference files - Codex silently truncates its skills block past a few dozen entries, so sub-commands are not peer skills here |
+| **Pipeline commands** | 56 slash-command skills, native | 56 skills, `multi-agent-{cmd}` naming, copied in | 1 router skill (`multi-agent`) + 56 command specs as reference files - Codex silently truncates its skills block past a few dozen entries, so sub-commands are not peer skills here |
 | **Stack plugins** | Marketplace plugin, loaded natively, resolved by `.claude/settings.json` enabled-list | Enabled plugin's authored skills copied flat into `~/.copilot/skills/`; `knowledge/` **not** re-copied (already delivered via `shared/external`) | Copied as reference files under `~/.codex/multi-agent-refs/skills/`, plugin-prefixed on name clash (e.g. `architecture` → `ai-ios-toolkit-architecture`) |
 | **Component dispatch (Phase 3)** | Marketplace plugin's `create-component`/`create-screen` skill via the Skill tool | No plugin loader - the enabled stack plugin's authored skills (incl. `create-component`) are copied flat into `~/.copilot/skills/` at install time (the old frozen `figma-*` copies are pruned, they were never a fallback) | Not part of the enforced parity axis; classification + state-shape must match, skill *inventory* does not |
 | **multi-agent-toolkit-mcp** | `claude mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` | `copilot mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` | `codex mcp add multi-agent-toolkit -- npx -y @mmerterden/multi-agent-toolkit-mcp` (skipped with a warning if `codex` isn't on `PATH`) |

package/install/templates/multi-agent-autopilot.plist.template

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+  multi-agent autopilot  -  the schedule for continuous mode.
+
+  Rendered and installed ONLY by /multi-agent:autopilot-on, after an explicit
+  confirmation that names this file's path. A clean install writes nothing here;
+  smoke-autopilot-default-off.sh fails if it ever does.
+
+  A user agent, not a daemon, and that is the correct choice rather than a
+  limitation: it loads at LOGIN. Before login the keychain is locked, so a tick
+  that fired at boot could not read a single token - it would take items it could
+  not work on and burn them. Automatic login means nothing to do after a restart.
+
+  StartInterval does NOT wake a sleeping Mac; it fires on the next wake. The mode
+  therefore holds its own sleep assertion while on AC and releases it on battery,
+  so an overnight queue keeps moving without flattening a laptop off the charger.
+
+  {{PLACEHOLDERS}} are substituted by autopilot-on: NODE, TICK, LABEL, ROOT,
+  INTERVAL.
+-->
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>{{LABEL}}</string>
+
+  <key>ProgramArguments</key>
+  <array>
+    <string>{{NODE}}</string>
+    <string>{{TICK}}</string>
+  </array>
+
+  <!-- Load at login and run one tick immediately, so turning the mode on does
+       something visible rather than waiting out the first interval. -->
+  <key>RunAtLoad</key>
+  <true/>
+
+  <key>StartInterval</key>
+  <integer>{{INTERVAL}}</integer>
+
+  <!-- One tick at a time. Overlapping ticks would each claim the queue head;
+       the runner's own pid+sessionId check is the real mutual exclusion, and
+       this keeps the common case from ever reaching it. -->
+  <key>AbandonProcessGroup</key>
+  <false/>
+
+  <key>ProcessType</key>
+  <string>Background</string>
+
+  <!-- Nice to the interactive session. The point of this mode is work that
+       happens while you do something else, so it must never be what makes the
+       machine feel slow. -->
+  <key>LowPriorityIO</key>
+  <true/>
+  <key>Nice</key>
+  <integer>5</integer>
+
+  <!-- Both streams go to the runner's own log, inside the 0700 state directory.
+       Not /tmp: a tick's output names tickets, repos and branches, and on a
+       shared machine that is somebody's roadmap. Every file the runner writes
+       is scanned for credentials before it is kept. -->
+  <key>StandardOutPath</key>
+  <string>{{ROOT}}/runner.log</string>
+  <key>StandardErrorPath</key>
+  <string>{{ROOT}}/runner.log</string>
+
+  <key>EnvironmentVariables</key>
+  <dict>
+    <key>PATH</key>
+    <string>/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin:/usr/sbin:/sbin</string>
+    <!-- No token is set here, deliberately. launchd plists are world-readable
+         and get backed up; credentials are read from the keychain at tick time
+         through credential-store.sh, which streams them over stdin so they never
+         reach argv either. -->
+  </dict>
+
+  <key>WorkingDirectory</key>
+  <string>{{ROOT}}</string>
+</dict>
+</plist>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "17.0.0",
+  "version": "17.1.0",
   "description": "8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase cost ledger, persistent learnings memory, wiki generation, commit automation. Token-preserving uninstall.",
   "type": "module",
   "main": "index.js",

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

@@ -0,0 +1,64 @@
+---
+description: "Turn off continuous mode on this machine: the schedule is removed, work already running finishes, the repo selection is kept. Use when the machine should stop picking work up."
+description-tr: "Bu makinede sürekli modu kapatır: zamanlama kaldırılır, koşan iş biter, repo seçimi saklanır."
+argument-hint: "[--now]  -  --now also stops the item currently running"
+---
+
+# multi-agent autopilot-off  -  stop picking work up
+
+Removes the schedule. **Work already in flight finishes** unless you pass
+`--now`: an item stopped mid-development leaves a worktree and a half-written
+branch, which is the exact state this release spent its time cleaning up.
+
+## Steps
+
+### 1. Say what is in flight before stopping anything
+
+```bash
+bash "$HOME/.claude/scripts/autopilot-status.sh" --short
+```
+
+When something is running, name it and how long it has been going. "Stopped"
+means something different when an item is 2 minutes from a PR than when the queue
+is idle, and the user is the one who knows which.
+
+### 2. Remove the schedule
+
+```bash
+L="com.multi-agent.autopilot"
+launchctl bootout "gui/$(id -u)/$L" 2>/dev/null || launchctl unload "$HOME/Library/LaunchAgents/$L.plist" 2>/dev/null
+rm -f "$HOME/Library/LaunchAgents/$L.plist"
+```
+
+The plist is removed rather than left disabled, because its presence is the
+definition of on: a disabled-but-present job is a third state nobody can read
+from the outside.
+
+### 3. Release the sleep assertion and the indicator
+
+```bash
+pkill -f 'caffeinate -i -w' 2>/dev/null || true       # only the one this mode holds
+pkill -f "$HOME/.claude/autopilot/bin/menubar" 2>/dev/null || true
+```
+
+### 4. `--now` only: end the in-flight item deliberately
+
+Without `--now` nothing here runs. With it, the child session is stopped and the
+run is marked `abandoned`, its worktree is removed **unless it holds uncommitted
+work**, in which case the work is stashed to `autopilot/abandoned/<task-id>` and
+the worktree is kept. Same contract as `gc-abandoned.sh`; losing a day of edits
+is worse than 750 MB.
+
+### 5. Keep the selection
+
+`~/.claude/autopilot/config.json`, `queue.json` and `attempted.jsonl` all stay.
+Turning the mode back on must not re-ask which repos, and the attempt history is
+what stops an item that already failed twice from being retried forever.
+
+To forget the selection as well: `rm -rf ~/.claude/autopilot`. Say that rather
+than doing it - "off" and "forget everything" are different requests.
+
+### 6. Report
+
+State that it is off, what was left running or finishing, and that the repo
+selection is kept. If an item was stashed, name the branch.

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

@@ -0,0 +1,173 @@
+---
+description: "Turn on continuous mode on THIS machine: pick the repos it watches; labelled GitHub issues and assigned+labelled Jira items then run in a worktree and stop at an open PR. Use when the machine should pick work up unattended."
+description-tr: "Bu makinede sürekli modu açar: izlenecek repoları seçersin, etiketli GitHub issue'ları ve sana atanmış + etiketli Jira maddeleri worktree'de geliştirilip PR'da durur. Repo listesini değiştirmek için aynı komutu tekrar çalıştır."
+argument-hint: "(no arguments  -  opens the repo picker)"
+---
+
+# multi-agent autopilot-on  -  continuous mode, on this machine
+
+Turns on the mode that picks work up without being asked. **No repo is included
+by default and none is ever added implicitly** - you choose, here, every time.
+
+Why a picker rather than a label alone: measured on one machine, 66 repos grant
+push and a good half belong to other people. A label is a filter; anyone who can
+open an issue in a repo you happen to have push on could add one. The gate is
+this selection, and it is per machine.
+
+## Steps
+
+### 1. Prerequisites, stated before anything is written
+
+```bash
+gh auth status >/dev/null 2>&1 || echo "BLOCKED: gh is not authenticated - run 'gh auth login'"
+command -v jq >/dev/null 2>&1 || echo "BLOCKED: jq is required"
+node "$HOME/.claude/scripts/doctor.mjs" >/dev/null 2>&1; [ "$?" -ge 2 ] && echo "BLOCKED: doctor reports a blocking problem - fix it first"
+```
+
+Any BLOCKED line stops here and is reported. Arming unattended work on an install
+that `doctor` calls broken produces a queue of failures, one per item.
+
+### 2. The repo list, both halves of it
+
+```bash
+bash "$HOME/.claude/lib/autopilot-activation.sh" list
+```
+
+Two states come back and **both are shown**:
+
+- `eligible` - push rights and a checkout on this machine
+- `unavailable` - push rights, no local checkout, listed WITH that reason
+
+Never hide the second list. Dropping 51 of 66 rows silently looks exactly like a
+permissions problem, and the user goes hunting for a token fault that does not
+exist.
+
+### 3. Pick, with the current selection already checked
+
+Read `~/.claude/autopilot/config.json` if it exists, then one `AskUserQuestion`
+(`multiSelect: true`) over the **eligible** rows:
+
+- `question` (in `outputLanguage`): which repos this machine should pick work up from
+- `header`: "Repos" (English, UI contract)
+- `options`: one per eligible repo, currently-selected ones marked "(seçili)" / "(selected)"
+
+**This is how repos are added and removed.** Checking a new one adds it;
+unchecking an existing one removes it. There is no `add-repo` / `remove-repo`
+command, because two entry points to one list is two lists.
+
+Unavailable repos are printed above the question as a plain list with their
+reason, not offered as options.
+
+### 4. Sources and label, per selected repo
+
+One `AskUserQuestion` per newly added repo (already-configured ones keep their
+answers - re-running must not re-ask what was already settled):
+
+- Sources: `GitHub issues` / `Jira` / both
+- Label: default **`agent-queue`** on both sides, editable
+
+The same name works on both sides and both mechanisms already exist:
+
+| Source | Query | Extra condition |
+|---|---|---|
+| GitHub | `gh issue list --repo <r> --label <label> --state open` | none - the label is the whole gate |
+| Jira | `assignee = currentUser() AND labels = "<label>" AND resolution = EMPTY AND status not in (Done, Closed, Cancelled)` | **assigned to you**, so a label somebody else adds is not enough |
+
+Two Jira caveats worth saying out loud when Jira is selected: labels are one
+global namespace across the whole instance and anyone can write them, so on a
+shared instance prefer a qualified name (`agent-queue-<team>`); and the Labels
+field has to be on the edit screen for the issue types in play. An instance where
+neither holds is a `jiraJql` config change - a saved filter, a component - not a
+redesign.
+
+Run the query before saving it, and show the count:
+
+```bash
+bash "$HOME/.claude/scripts/jira-search.sh" --jql "$JQL" --max 5 | jq '.total, [.issues[].key]'
+```
+
+A JQL that returns nothing is not an error and is usually correct on day one
+(nothing is labelled yet), but a JQL that errors is a config that will be silent
+forever - the Labels field missing from an edit screen looks exactly like an
+empty queue from the outside. Saying "0 items, query valid" and "query rejected"
+differently here is the difference between a two-minute fix and a week of
+wondering why nothing happens.
+
+### 5. Write the config
+
+Validate against `schemas/autopilot-config.schema.json`, then write
+`~/.claude/autopilot/config.json` (0600, in a 0700 directory) via
+`ma_ap_write` in `lib/autopilot-state.sh`. Defaults that are not asked:
+`slots: 1`, `scanIntervalSeconds: 120`, `maxAttempts: 2`,
+`askOnLowMaturity: true`, `costCeilingUsd: 25`, `depthRouter: "off"`.
+
+### 6. Build the menu bar indicator (best effort)
+
+```bash
+SRC="$HOME/.claude/scripts/autopilot-menubar.swift"
+OUT="$HOME/.claude/autopilot/bin/menubar"
+if command -v swiftc >/dev/null 2>&1; then
+  swiftc -O "$SRC" -o "$OUT" 2>/dev/null && chmod 700 "$OUT"
+fi
+```
+
+Built from source on demand, never shipped as a binary: the package contains only
+text today, and a compiled artifact in it would need signing and notarization to
+be distributable. No `swiftc` means no indicator and nothing else changes - say
+so in one line rather than failing. `autopilot-status` works either way.
+
+### 7. Confirm the schedule, naming the file
+
+Render `templates/multi-agent-autopilot.plist.template` by substituting its five
+placeholders, then show the resolved **path** and interval and `AskUserQuestion`:
+
+```bash
+TPL="$HOME/.claude/templates/multi-agent-autopilot.plist.template"
+DEST="$HOME/Library/LaunchAgents/com.multi-agent.autopilot.plist"
+INTERVAL=$(bash "$HOME/.claude/scripts/autopilot-status.sh" --json | jq -r '.scanIntervalSeconds // 120')
+sed -e "s|{{NODE}}|$(command -v node)|g" \
+    -e "s|{{TICK}}|$HOME/.claude/scripts/autopilot-runner.mjs|g" \
+    -e "s|{{LABEL}}|com.multi-agent.autopilot|g" \
+    -e "s|{{ROOT}}|$HOME/.claude/autopilot|g" \
+    -e "s|{{INTERVAL}}|$INTERVAL|g" \
+    "$TPL" > "$DEST"
+```
+
+`command -v node` rather than the bare word: launchd does not read a login
+shell, so its `PATH` is the short one in the plist's own `EnvironmentVariables`,
+and a Homebrew or nvm node that is not on that path would make every tick fail
+with a message nobody is watching for.
+
+- `question`: install the schedule at `~/Library/LaunchAgents/com.multi-agent.autopilot.plist` and start picking work up?
+- options: `{ label: "Start" }` / `{ label: "Configure only", description: "Save the repo selection, do not schedule anything yet" }`
+
+"Configure only" is a real answer and the safe default to offer first: the queue
+can be watched with `autopilot-status` for a while before anything runs.
+
+On **Start**:
+
+```bash
+launchctl bootstrap "gui/$(id -u)" "$HOME/Library/LaunchAgents/com.multi-agent.autopilot.plist" 2>/dev/null \
+  || launchctl load "$HOME/Library/LaunchAgents/com.multi-agent.autopilot.plist"
+```
+
+### 8. Report what is now true
+
+Say all five, because each one is something a user has asked about after the
+fact: which repos and which labels; that it survives a restart with no command to
+run (launchd loads at **login** - not boot, and that is correct, because the login
+keychain is what unlocks the tokens, so a run before login could not reach Jira or
+GitHub anyway); that the machine will be kept awake **only on AC**; the slot count
+and the ceiling this machine would allow (`ma_ap_slot_ceiling`); and that
+`/multi-agent:autopilot-off` is the only way to stop it.
+
+## What this does not do
+
+- **No cap on PRs.** As many items as carry the label become as many PRs. The
+  bounds are `costCeilingUsd` over a rolling 24 hours and what the machine can
+  hold - never a daily count.
+- **Does not merge.** The runner stops at an open PR; the merge decision stays
+  yours.
+- **Does not touch an attended run.** Both are worktrees and per-repo concurrency
+  is 1, so the queue skips a repo you are working in rather than competing for
+  `.git/index.lock`.