@mmerterden/multi-agent-pipeline 16.7.0 → 16.8.0

package/CHANGELOG.md

@@ -26,6 +26,26 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 - **`smoke-website-deploy-identity.sh` (20 assertions).** It runs the script against throwaway repos with real remotes rather than grepping the doc: the happy path lands and pushes, an exported `GIT_AUTHOR_EMAIL` halts with the commit still local, an unchanged tree makes no empty commit, a matching config is preserved while a wrong name is corrected, and missing or non-repository arguments exit 2. Wiring is asserted separately, since a correct script nothing calls is its own failure mode.
 
+## [16.8.0] - 2026-08-25
+
+Usage reporting answers the question it was built for, and stops carrying what it never should have.
+
+### Changed
+
+- **`usageLog.enabled` now defaults to `true`.** Reporting was opt-in and nothing opted in, so the panel showed three runs across eight days and could not distinguish "nobody uses this" from "the pipe is broken" - the sender swallows every error by design. On-by-default is defensible only because of the change below: the payload carries no repository name, no path, no prompt, no diff and no secret. `usageLog.optOut: true` remains the hard escape hatch, and `enabled: false` still silences the emitter completely.
+- **The event carries the command that ran.** `commandOf()` returned `state.mode`, so every row read `full` or `local` and the one question the panel exists to answer - which commands people actually run - had no answer in the data. It now sends the invoked command; `mode` continues to ship separately.
+
+### Fixed
+
+- **The repository name is no longer sent.** `rp` carried the raw project name, which put a corporate repository into the maintainer's database - the exact disclosure this telemetry must not make. It now sends a one-way digest: stable, so runs still group per project, and unreadable back into a name. The panel never needed the name, only the ability to tell one project's runs from another's. The row already stored was redacted in place.
+
+## [16.7.1] - 2026-08-25
+
+### Fixed
+
+- **The two commands 16.7.0 added were not listed anywhere a user looks.** `/multi-agent:review-analysis` and `/multi-agent:feedback` shipped without an entry in `/multi-agent:help` (either language), in either README, or in the Copilot and Codex help variant - so the release published two commands nobody could discover. Every gate was green through seven rounds and none of them caught it, because no gate asks whether a new command was documented; a command a user cannot find is close to a command that does not exist.
+- Making room for those entries took `help/SKILL.md` past its grandfathered token ceiling (8586 against 8500). The ceiling is governed by a list that only ratchets down, so raising it was not available - and should not have been. The new lines were cut first, and the rest came from the `store-ready` entry, which spent four lines per language on detail that belongs in its own command doc. A help listing is one line per command. Space for the new commands was taken back from an entry that had more than its share rather than borrowed from the budget.
+
 ## [16.7.0] - 2026-08-25
 
 Two commands: one that reviews the document instead of the diff, one that lets a user say something went wrong.

package/README.md

@@ -77,7 +77,7 @@ The discipline behind all of this - bounded loops, evidence gates, token-budgete
 | Audit | `/multi-agent:design-check` | Mock-mode vs Figma conformance, local-only |
 | Audit | `/multi-agent:testflight-validation` | Pre-submission gates for a TestFlight build: static archive audit → Apple's `altool --validate-app` → Review-Guidelines check. Validates only, never uploads |
 
-Helpers: `setup`, `status`, `resume #N`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `create-jira`, `save`, `routines`, `forget`. 53 commands in all  -  full list: `/multi-agent:help`.
+Helpers: `setup`, `status`, `resume #N`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `review-analysis`, `feedback`, `create-jira`, `save`, `routines`, `forget`. 53 commands in all  -  full list: `/multi-agent:help`.
 
 ## Stacks
 

package/README.tr.md

@@ -76,7 +76,7 @@ Bunun arkasındaki disiplin - sınırlı loop'lar, kanıt kapıları, token-büt
 | Audit | `/multi-agent:design-check` | Mock-mode vs Figma uygunluğu, yalnızca lokal |
 | Audit | `/multi-agent:testflight-validation` | TestFlight build için pre-submission kapıları: statik archive denetimi → Apple'ın `altool --validate-app`'i → Review-Guidelines kontrolü. Yalnızca doğrular, asla yüklemez |
 
-Yardımcılar: `setup`, `status`, `resume #N`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `create-jira`, `save`, `routines`, `forget`. Toplam 53 komut - tam liste: `/multi-agent:help`.
+Yardımcılar: `setup`, `status`, `resume #N`, `kill #N`, `garbage-collect`, `prune-logs`, `purge`, `review`, `test`, `channels`, `stack`, `update`, `sync`, `refactor`, `jira`, `issue`, `analysis`, `review-analysis`, `feedback`, `create-jira`, `save`, `routines`, `forget`. Toplam 53 komut - tam liste: `/multi-agent:help`.
 
 ## Stack'ler
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-pipeline",
-  "version": "16.7.0",
+  "version": "16.8.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/help/SKILL.md

@@ -116,11 +116,13 @@ Status & Resume:
 Post-Hoc & Side-Channel:
 
   /multi-agent:channels       Post multi-channel report (Jira / Confluence / Wiki / PR description)
+  /multi-agent:feedback "msg"  Tell the maintainer something broke; only your text is sent
   /multi-agent:review         Parallel review of a PR or branch diff; no URL -> pick open GitHub/Bitbucket PRs
   /multi-agent:review-jira    Grade a Jira issue's pipeline-readiness -> comment the gaps on it
   /multi-agent:review-issue   Grade a GitHub issue's pipeline-readiness -> comment the gaps on it
   /multi-agent:analysis ["analysis-name"]  Feature-spec analysis (Figma + Swagger + Confluence + repos) → per-platform v3 doc (23-section Full / 7-section Lite)
   /multi-agent:analysis-resolve [doc]      Resolve Section 20 open questions of an analysis doc, one at a time with source-labeled candidates
+  /multi-agent:review-analysis [doc]  Review a written analysis; findings cite the rule they break
   /multi-agent:complaint-analysis ["run-name"] [--file path]  Customer-complaint triage: Graylog evidence per trx/conv id + read-only repo correlation → client/bff root cause + fix plan + dev prompt, or core routing recommendation
   /multi-agent:build-optimize iOS-only Xcode build perf wrapper → benchmark + analyze + recommend-first .build-benchmark/optimization-plan.md
   /multi-agent:create-jira ["desc"] [figma-url] [swagger-url]  Create a Jira Task/Bug/Story matching team conventions (asks type + mining + active sprint + auto-sizing sections + preview & approval)
@@ -128,10 +130,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:search         Cross-task log search with smart ranking; --semantic queries triage corpus
   /multi-agent:scan           Skill security scan against tiered pattern catalog
   /multi-agent:refactor       Best practices + bug hunt + upstream drift + toolkit MCP research -> one plan, approval, dev + sync
-  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep]  Pre-submission store readiness,
-                              iOS + Android, local-only. Three symmetric gates per platform: static package audit,
-                              the store's own validator, policy review vs repo source. Plus the running-app sweep.
-                              A skipped gate is never counted as a pass. Validates only, never uploads.
+  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep]  Pre-submission store readiness, iOS + Android, local-only: three symmetric gates per platform plus the running-app sweep. A skipped gate is never a pass. Validates only, never uploads.
   /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  iOS-pinned alias of :store-ready, kept because it is
                               the name you reach for when the target is TestFlight. Same three gates, one implementation.
   /multi-agent:ios-coding-standard [module]  Audit an iOS module against the 99-rule coding-standard registry -> remediation
@@ -391,11 +390,13 @@ Status & Resume:
 Post-Hoc & Side-Channel:
 
   /multi-agent:channels       Multi-channel rapor gönder (Jira / Confluence / Wiki / PR description)
+  /multi-agent:feedback "mesaj"  Bakımcıya bir şeyin bozulduğunu bildir; yalnızca yazdığın metin gider
   /multi-agent:review         PR veya branch diff'ini paralel review et; URL yoksa -> açık GitHub/Bitbucket PR'larını seçtir
   /multi-agent:review-jira    Jira maddesinin pipeline'a hazırlığını değerlendir -> eksikleri yorum olarak ekle
   /multi-agent:review-issue   GitHub issue'nun pipeline'a hazırlığını değerlendir -> eksikleri yorum olarak ekle
   /multi-agent:analysis ["analysis-name"]  Feature-spec analizi (Figma + Swagger + Confluence + repolar) → platform başına v3 doküman (23 bölüm Full / 7 bölüm Lite)
   /multi-agent:analysis-resolve [doc]      Analiz dokümanının Bölüm 20 açık sorularını kaynak etiketli adaylarla teker teker çözer
+  /multi-agent:review-analysis [doc]  Yazılmış analizi review eder; bulgular ihlal edilen kuralı gösterir
   /multi-agent:complaint-analysis ["run-adı"] [--file yol]  Müşteri şikayeti triyajı: trx/conv id ile Graylog kanıtı + salt-okunur repo eşleştirme → client/bff kök neden + fix planı + dev prompt'u, veya core'a yönlendirme önerisi
   /multi-agent:build-optimize iOS-only Xcode build performance wrapper → benchmark + analiz + recommend-first .build-benchmark/optimization-plan.md
   /multi-agent:create-jira ["açıklama"] [figma-url] [swagger-url]  Takım standartlarına uygun Jira Task/Bug/Story oluştur (tip sorar + convention mining + aktif sprint + auto-sizing bölümler + önizleme & onay)
@@ -403,10 +404,7 @@ Post-Hoc & Side-Channel:
   /multi-agent:search         Task log'larında akıllı arama; --semantic triage corpus'unu sorgular
   /multi-agent:scan           Skill güvenlik taraması (tiered pattern catalog)
   /multi-agent:refactor       Uyarlanmış best-practice + bug avı + upstream-drift + multi-agent-toolkit MCP araştırması -> tek plan, onay, dev + sync
-  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep]  Yükleme öncesi store hazırlığı,
-                              iOS + Android, yalnızca lokal. Platform başına 3 simetrik kapı: statik paket denetimi,
-                              store'un kendi doğrulayıcısı, kaynağa karşı politika incelemesi. Artı çalışan-app sweep'i.
-                              Atlanan kapı asla pass sayılmaz. Sadece doğrular, asla yüklemez.
+  /multi-agent:store-ready [repo] [--archive=|--ipa=|--aab=|--apk=] [--skip-sweep]  Yükleme öncesi store hazırlığı, iOS + Android, yalnızca lokal: platform başına 3 simetrik kapı artı çalışan-app sweep'i. Atlanan kapı asla pass sayılmaz. Sadece doğrular, asla yüklemez.
   /multi-agent:testflight-validation [repo] [--ipa=|--archive=]  :store-ready'nin iOS'a sabitlenmiş alias'ı; hedef
                               TestFlight olduğunda akla gelen isim olduğu için korunuyor. Aynı 3 kapı, tek implementasyon.
   /multi-agent:ios-coding-standard [modül]  Bir iOS modülünü 99 kurallık kodlama-standardı registry'sine göre denetler -> düzeltme

package/pipeline/schemas/prefs.schema.json

@@ -1061,8 +1061,8 @@
           "properties": {
             "enabled": {
               "type": "boolean",
-              "default": false,
-              "description": "Master switch. When false the emitter exits silently and nothing leaves the machine."
+              "default": true,
+              "description": "Master switch, on by default. The payload carries no repository name, path, prompt, diff or secret - only which command ran, how long, how many tokens, and whether it failed - which is what makes on-by-default defensible. Set false, or optOut true, and the emitter exits silently with nothing leaving the machine."
             },
             "optOut": {
               "type": "boolean",

package/pipeline/scripts/usage-report.mjs

@@ -26,6 +26,7 @@ import { homedir, platform } from "os";
 import { dirname, join } from "path";
 import { fileURLToPath, pathToFileURL } from "url";
 import { execFileSync } from "child_process";
+import { createHash } from "crypto";
 import { costUsd } from "./_cost.mjs";
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
@@ -272,13 +273,28 @@ function inputType(state) {
   return "free-text";
 }
 
+// The command that was actually invoked (`/multi-agent:analysis`, `:review`,
+// ...). This used to return `state.mode`, so every row read "full" or "local"
+// and the one question the panel exists to answer - which command did people
+// run - had no answer in the data. `mode` still ships separately as `m`.
 function commandOf(state) {
+  const c = state.command;
+  if (typeof c === "string" && c.trim()) return c.trim().slice(0, 60);
   if (state.mode) return state.mode;
   if (state.onlyDevelop) return "dev";
   if (state.localMode) return "local";
   return "full";
 }
 
+// A repository name is the user's, not ours. It put a corporate project into
+// the maintainer's database, which is the disclosure this telemetry must not
+// make - and the panel never needed the name, only the ability to tell one
+// project's runs from another's. A digest does that and cannot be read back.
+function projectDigest(name) {
+  if (typeof name !== "string" || !name.trim()) return null;
+  return `p${createHash("sha256").update(name.trim()).digest("hex").slice(0, 8)}`;
+}
+
 function resolveTracker(state) {
   const id = state.taskId || state.shortId;
   if (id == null) return null;
@@ -490,7 +506,7 @@ function buildEvent(state) {
     lo: Boolean(state.localMode),
     dev: Boolean(state.onlyDevelop),
     in: inputType(state),
-    rp: state.project || null,
+    rp: projectDigest(state.project),
     ph: typeof state.currentPhase === "number" ? state.currentPhase : null,
     st: state.status || null,
     hr: state.haltReason || null,

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

@@ -106,6 +106,8 @@ Utility Commands (dash form on Copilot, colon form on Claude Code):
   /multi-agent:review         Review a PR or branch diff; no URL -> pick open GitHub/Bitbucket PRs
   /multi-agent:review-jira    Grade a Jira issue's pipeline-readiness -> comment the gaps
   /multi-agent:review-issue   Grade a GitHub issue's pipeline-readiness -> comment the gaps
+  /multi-agent:review-analysis [doc | page | KEY]  Review a written analysis: gates first, then parallel model review; findings cite the rule
+  /multi-agent:feedback "msg" Tell the maintainer something broke; only your text is sent, shown before it goes
   /multi-agent:create-jira ["desc"] [figma-url] [swagger-url]  Create a Jira Task/Bug/Story matching team conventions (asks type + preview + approval)
   /multi-agent:sync           Sync ecosystem (Claude + Copilot + website)
   /multi-agent:setup          Keychain tokens + Git identity + language onboarding