@mmerterden/multi-agent-pipeline 15.7.0 → 15.8.0

package/CHANGELOG.md

@@ -16,6 +16,11 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ## [Unreleased]
 
+## [15.8.0] - 2026-08-19
+
+### Added
+- **Operational reporting self-registers on update**: when no ingest token is onboarded, `/multi-agent:update` requests a per-machine write-only token from the reporting endpoint's `/register` route, stores it only in the OS credential store, and enables `usageLog`. Registration failing (offline, endpoint down, ingest disabled) leaves reporting off with a one-line notice - never an error. Hard opt-out via `usageLog.optOut: true` blocks both the registration and the auto-enable; setup Step 2.7 (admin-issued token) still takes precedence. The emitter's payload is unchanged: coarse run metadata only, never prompts, code, diffs, or paths.
+
 ## [15.7.0] - 2026-08-19
 
 ### Added

package/package.json

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

@@ -208,7 +208,7 @@ Save the resolved mapping to preferences:
 
 ### Step 2.7  -  Operational reporting token (optional, opt-in)
 
-Only relevant when the team runs the optional operational reporting integration and the admin has issued this user a token. This is the ONE-TIME onboarding that configures it afterwards: once the token is in the credential store, `/multi-agent:update` auto-configures `usageLog`. Skipping it leaves the integration fully off.
+Only relevant when the admin has issued this user a token. Since v15.8.0, `/multi-agent:update` self-registers a per-machine token automatically when none is onboarded (opt-out: `usageLog.optOut=true`), so Skip here is never a dead end; an admin-issued token pasted now simply takes precedence.
 
 Ask (in `outputLanguage`), and proceed only on an explicit yes:
 

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

@@ -77,28 +77,51 @@ A git clone of the pipeline repo is a maintainer workspace, kept in sync by `/mu
    fi
    ```
 
-5b. **Auto-configure operational reporting when a token is already onboarded.** The
-   integration is opt-in and off by default. This step turns it ON only when a
-   token can be resolved - it NEVER fabricates a secret or ships one, so a machine
-   that was never given the token stays inert. Resolution order: env
-   `MULTI_AGENT_USAGE_TOKEN`, then `usageLog.token`, then the Keychain item named by
-   `keychainMapping.usage_ingest`. Endpoint is left to the emitter's default.
+5b. **Auto-configure operational reporting.** Off means silent: the emitter still
+   no-ops unless `enabled` is true AND a token resolves. This step never SHIPS a
+   secret; when no token is onboarded it REQUESTS a per-machine write-only token
+   from the reporting endpoint's `/register` route (self-registration, v15.8.0+),
+   stores it only in the credential store, and flips `usageLog.enabled` on. It
+   reports coarse run metadata only - never prompts, code, diffs, or paths.
+   Resolution order: env `MULTI_AGENT_USAGE_TOKEN`, then `usageLog.token`, then
+   the Keychain item named by `keychainMapping.usage_ingest`, then
+   self-registration. Registration failing (offline, endpoint down, admin turned
+   ingest off) leaves reporting off with one status line - never an error.
+   **Opt-out is `usageLog.optOut: true`**: it blocks both the auto-enable and the
+   self-registration permanently; print the opt-out hint on first auto-enable.
    ```bash
    PREFS="$HOME/.claude/multi-agent-preferences.json"
    if [ -f "$PREFS" ] && command -v jq >/dev/null 2>&1; then
      ENABLED=$(jq -r '.global.usageLog.enabled // false' "$PREFS" 2>/dev/null)
-     if [ "$ENABLED" != "true" ]; then
+     OPTOUT=$(jq -r '.global.usageLog.optOut // false' "$PREFS" 2>/dev/null)
+     if [ "$ENABLED" != "true" ] && [ "$OPTOUT" != "true" ]; then
        TOK="${MULTI_AGENT_USAGE_TOKEN:-}"
        [ -z "$TOK" ] && TOK=$(jq -r '.global.usageLog.token // empty' "$PREFS" 2>/dev/null)
        if [ -z "$TOK" ]; then
          KNAME=$(jq -r '.global.keychainMapping.usage_ingest // empty' "$PREFS" 2>/dev/null)
          [ -n "$KNAME" ] && TOK=$(bash "$HOME/.claude/lib/credential-store.sh" get "$KNAME" 2>/dev/null)
        fi
+       if [ -z "$TOK" ]; then
+         EP=$(jq -r '.global.usageLog.endpoint // "https://mmerterden.vercel.app/api/usage/ingest"' "$PREFS" 2>/dev/null)
+         REG_EP="${EP%/ingest}/register"
+         RUSER=$(jq -r '.global.identities[0].username // .global.identities[0].name // empty' "$PREFS" 2>/dev/null)
+         [ -z "$RUSER" ] && RUSER="$USER"
+         RESP=$(curl -sS -m 10 -X POST -H "Content-Type: application/json" \
+           --data "{\"u\":\"$RUSER\",\"c\":\"$(hostname -s 2>/dev/null || echo unknown)\"}" \
+           "$REG_EP" 2>/dev/null)
+         TOK=$(printf '%s' "$RESP" | jq -r '.token // empty' 2>/dev/null)
+         if [ -n "$TOK" ]; then
+           printf '%s' "$TOK" | bash "$HOME/.claude/lib/credential-store.sh" set "${USER}_Usage_Ingest_Token" "$(cat)"
+           node -e 'const fs=require("fs"),p=process.argv[1];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[2];fs.writeFileSync(p,JSON.stringify(j,null,2)+"\n");' "$PREFS" "${USER}_Usage_Ingest_Token"
+           echo "  -> operational reporting: registered this machine (write-only token in credential store)"
+           echo "     opt out any time: set global.usageLog.optOut=true in multi-agent-preferences.json"
+         fi
+       fi
        if [ -n "$TOK" ]; then
          node -e 'const fs=require("fs"),p=process.argv[1];const j=JSON.parse(fs.readFileSync(p,"utf8"));j.global=j.global||{};j.global.usageLog=j.global.usageLog||{};j.global.usageLog.enabled=true;fs.writeFileSync(p,JSON.stringify(j,null,2)+"\n");' "$PREFS"
-         echo "  -> operational reporting configured (token found)"
+         echo "  -> operational reporting configured"
        else
-         echo "  -> operational reporting left off (no token onboarded)"
+         echo "  -> operational reporting left off (no token; registration unreachable or disabled)"
        fi
      fi
    fi

package/pipeline/schemas/prefs.schema.json

@@ -1122,13 +1122,18 @@
         "usageLog": {
           "type": "object",
           "additionalProperties": false,
-          "description": "Optional, opt-in per-run operational reporting via pipeline/scripts/usage-report.mjs. Emits coarse run metadata only (never prompts, code, diffs, or absolute paths). Off by default; the emitter no-ops unless enabled is true AND a token resolves (from token below or env MULTI_AGENT_USAGE_TOKEN), so it is inert for anyone who has not configured it.",
+          "description": "Optional, opt-in per-run operational reporting via pipeline/scripts/usage-report.mjs. Emits coarse run metadata only (never prompts, code, diffs, or absolute paths). The emitter no-ops unless enabled is true AND a token resolves (from token below or env MULTI_AGENT_USAGE_TOKEN). Since v15.8.0 /multi-agent:update self-registers a per-machine write-only token and enables this automatically; optOut=true blocks that permanently.",
           "properties": {
             "enabled": {
               "type": "boolean",
               "default": false,
               "description": "Master switch. When false the emitter exits silently and nothing leaves the machine."
             },
+            "optOut": {
+              "type": "boolean",
+              "default": false,
+              "description": "Hard opt-out. When true, /multi-agent:update neither self-registers a token nor auto-enables reporting; enabled stays false until the user clears this."
+            },
             "endpoint": {
               "type": "string",
               "description": "Ingest URL that receives the run record. The token is sent in the X-Usage-Token header."