@mmerterden/multi-agent-pipeline 15.2.0 → 15.3.0

package/CHANGELOG.md

@@ -16,6 +16,22 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [15.3.0] - 2026-08-15
+
+### Added
+
+- **`/multi-agent:setup` onboards the usage-dashboard token (opt-in, one-time).**
+  When a team runs the private dashboard and the admin issued this user a personal
+  ingest token, setup stores it in the OS credential store ONLY (never a file,
+  prefs value, git, or synced tree), maps `keychainMapping.usage_ingest`, and
+  turns logging on. After that single paste, `/multi-agent:update` keeps it active
+  and every run reports itself - no further steps. The token is write-only,
+  per-user (independently revocable), and read at runtime from the credential
+  store, transmitted only over TLS. Skipping the prompt leaves logging fully off.
+  True zero-touch is deliberately not offered: a machine that authenticates with
+  no prior onboarding would require an embeddable secret, which is the attack
+  vector - one-time onboarding is the security floor.
+
 ## [15.2.0] - 2026-08-15
 
 ### Added

package/package.json

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

@@ -206,6 +206,40 @@ Save the resolved mapping to preferences:
 
 `null` = not mapped (missing or skipped). Pipeline phases read this mapping to retrieve tokens dynamically  -  never hardcoded key names.
 
+### Step 2.7  -  Usage dashboard token (optional, opt-in)
+
+Only relevant when the team runs a private usage dashboard and the admin has issued this user a personal ingest token. This is the ONE-TIME onboarding that makes usage logging automatic afterwards: once the token is in the credential store, `/multi-agent:update` auto-enables `usageLog` and every run reports itself. Skipping it leaves logging fully off.
+
+Ask (in `outputLanguage`), and proceed only on an explicit yes:
+
+```
+Do you have a usage-dashboard ingest token from your admin?
+It turns on private run telemetry (who/what/when/tokens) for the team dashboard.
+[ Paste token / Skip ]
+```
+
+On paste, store the secret in the credential store ONLY - never in a file, prefs value, git, or any synced/published tree. Use the standard per-user key name so it is revocable independently and consistent across the user's machines:
+
+```bash
+~/.claude/lib/credential-store.sh set "${USER}_Usage_Ingest_Token" "<pasted-token>"
+```
+
+Then map it and enable logging (the token itself stays in the credential store; only the logical mapping + the on-switch land in prefs):
+
+```bash
+node -e '
+  const fs=require("fs"),os=require("os"),p=os.homedir()+"/.claude/multi-agent-preferences.json";
+  const j=JSON.parse(fs.readFileSync(p,"utf8"));
+  j.global=j.global||{}; j.global.keychainMapping=j.global.keychainMapping||{};
+  j.global.keychainMapping.usage_ingest=process.argv[1];
+  j.global.usageLog=Object.assign({enabled:true},j.global.usageLog||{},{enabled:true});
+  fs.writeFileSync(p,JSON.stringify(j,null,2)+"\n");
+' "${USER}_Usage_Ingest_Token"
+echo "  -> usage logging onboarded (token in credential store; logging on)"
+```
+
+Security notes to surface to the user: the token is **write-only** (it can only append activity metadata to the dashboard - no read access, no other scope), it is stored **only in the OS credential store**, and it is **per-user** so the admin can revoke this one token without affecting anyone else. `usage-report.mjs` reads it from the credential store at runtime via the `usage_ingest` mapping; it is never written to a file or transmitted except over TLS to the ingest endpoint.
+
 ### Auto-learned fields (no setup step needed)
 
 **Jira Project Key**: auto-learned from pipeline usage. User runs `/multi-agent ABC-123` → `ABC` is extracted and saved to `prefs.global.defaultJiraKey` (first ever) and `prefs.projects[{project}].jiraProjectKeys` (per-project). Multiple keys accumulate over time  -  most recent first, deduped. Phase 0 Step 1 (Parse Input) handles extraction.