@mmerterden/multi-agent-pipeline 10.8.0 → 10.12.0

package/pipeline/commands/multi-agent/refs/tracker-contract.md

@@ -58,8 +58,9 @@ Phases by mode:
 | Mode | Phases |
 |---|---|
 | Full pipeline | 0,1,2,3,4,5,6,7 |
-| `--dev` | 0,3,6,7 |
-| `--autopilot`, `--dev autopilot` | same as dev, with confirmations skipped |
+| `--dev` | 0,3,5,6,7 |
+| `--dev autopilot`, `--dev local`, `--dev local autopilot` | 0,3,6,7 (Phase 5 interactive test gate dropped) |
+| `--autopilot` | same as full pipeline, with confirmations skipped |
 
 Register each phase:
 
@@ -118,9 +119,10 @@ Mode-specific phase sets:
 | Mode | TaskCreate set (in order) |
 |---|---|
 | Full pipeline (`/multi-agent`, `:autopilot`, `:local`, `:local-autopilot`) | 0 → 1 → 2 → 3 → 4 → 5 → 6 → 7 (all 8) |
-| `:dev`, `:dev-autopilot`, `:dev-local`, `:dev-local-autopilot` | 0 → 3 → 5 → 6 → 7 (5 phases  -  1/2/4 omitted entirely) |
+| `:dev` | 0 → 3 → 5 → 6 → 7 (5 phases  -  1/2/4 omitted entirely) |
+| `:dev-autopilot`, `:dev-local`, `:dev-local-autopilot` | 0 → 3 → 6 → 7 (4 phases  -  1/2/4/5 omitted entirely; the autopilot/local variants drop the interactive Phase 5 test gate) |
 
-Note: in `--dev` modes the omitted phases (1, 2, 4) **do not get TaskCreate calls at all**  -  they're not part of the mode's phase set. The "[SKIPPED]" pattern above only applies if a normally-included phase is conditionally skipped at runtime.
+Note: in `--dev` modes the omitted phases (1, 2, 4  -  plus 5 in the autopilot/local variants) **do not get TaskCreate calls at all**  -  they're not part of the mode's phase set. The "[SKIPPED]" pattern above only applies if a normally-included phase is conditionally skipped at runtime. The authoritative per-mode set is the `for p in ...` init block in each mode's own entry doc; this table mirrors those blocks.
 
 **Enforcement**: `smoke-tasklist-ordering.sh` scans every mode entry point doc (`commands/multi-agent.md`, `commands/multi-agent/{autopilot,local,local-autopilot,dev,dev-autopilot,dev-local,dev-local-autopilot}.md` + Copilot mirrors) for the explicit "in phase-number order" rule. Inventory drift fails the smoke.
 
@@ -172,23 +174,40 @@ TaskUpdate({taskId: <dev_task>, activeForm: "Editing TopBarView.swift"})
 TaskUpdate({taskId: <dev_task>, activeForm: "Running xcodebuild test"})
 ```
 
-**Other CLIs**  -  `meta Now` key plus a render call:
+**Other CLIs**  -  the dedicated `now` action (quiet: writes `meta.Now`, never renders; the card picks it up at the next boundary render/update):
 ```bash
-bash $HOME/.claude/scripts/phase-tracker.sh meta 3 Now "→ editing TopBarView.swift"
-bash $HOME/.claude/scripts/phase-tracker.sh render
+bash $HOME/.claude/scripts/phase-tracker.sh now 3 "editing TopBarView.swift"
 ```
 
-The `Now` meta key shows up in the bordered card as `Now: → editing TopBarView.swift`.
+The `Now` value shows up in the bordered card as `Now: editing TopBarView.swift` (truncated to 60 chars by the script).
+
+**Progress-line mirror (required).** Every `normal`-tier progress line from the progress contract's canonical "When to emit" set is ALSO mirrored to the active phase, so the tracker always answers "what is it doing right now":
+
+- Claude Code: `TaskUpdate({activeForm: "<line text, arrow prefix stripped>"})`
+- Other CLIs: `phase-tracker.sh now <N> "<line text, arrow prefix stripped>"`
+
+Throttling rules: mirror only canonical-set lines (`verbose`-tier internals are not mirrored); at most one mirror per emitted line; skip the mirror when the text is identical to the last mirrored value; the mirror itself never triggers a render. Text is truncated to 60 chars.
+
+### Delegated phases  -  mirror limitation + chunked dispatch (required)
+
+When a phase's work is delegated to a subagent (Phase 3 Dev on Opus in `--dev` modes, `figma-to-component` dispatch, Phase 1 explorers, Phase 4 reviewers), the visual channel freezes for the duration of the Agent call: the orchestrator is blocked while the call is in flight, so it cannot fire `TaskUpdate` / `now` / `tokens`, and a subagent cannot drive the parent session's TaskList (its own TaskCreate/TaskUpdate calls land on an invisible child list). The progress-line mirror above can therefore only fire while the orchestrator holds control. Rules:
+
+1. **Pre-dispatch marker.** Immediately before every Agent call, set the active-phase line to the delegation itself, so the frozen interval at least states what is running and on which model:
+   - Claude Code: `TaskUpdate({activeForm: "Dev subagent (opus): <task subject>"})`
+   - Other CLIs: `phase-tracker.sh now <N> "dev subagent (opus): <task subject>"`
+2. **Chunk long delegations.** A phase whose delegated work spans multiple tasks MUST NOT go out as one monolithic Agent call. Dispatch per task (the Phase 2 task graph, or in `--dev` mode the self-generated task list, is the natural chunk boundary) so the orchestrator regains control at each boundary and refreshes `activeForm`, `tokens`, and `now` between chunks. Single-task phases and inherently atomic dispatches (one reviewer, one explorer) are exempt.
+3. **Post-chunk accounting.** When each chunk returns, record its token estimate (`phase-tracker.sh tokens <N> <in> <out>`) before dispatching the next chunk  -  not accumulated once at phase end.
 
 ### 5. Token accounting  -  automatic (manual top-up optional)
 
 The native TaskList header automatically prints `↑Nk tokens · thought for Ns`  -  Claude Code uses session-level metrics. For per-phase token attribution:
 
 ```bash
-bash $HOME/.claude/scripts/phase-tracker.sh tokens <N> <input_count> <output_count>
+bash $HOME/.claude/scripts/phase-tracker.sh tokens <N> <input_count> <output_count> [cached_count]
+bash $HOME/.claude/scripts/phase-tracker.sh model  <N> <model_name>
 ```
 
-Token counts are additive  -  multiple calls accumulate. Stored per phase in the state file; surfaced in `:log` reports.
+Token counts are additive  -  multiple calls accumulate. `input_count` is FRESH input (cache-exclusive); the optional 4th arg is the prompt-cache-read count, priced at the discounted rate. `model` tags the phase so the card and the cost helper can price it. Stored per phase in the state file; surfaced in `:log` reports, on the bash card tile (`<elapsed> · <tok> tok · ~$<usd>`), and in the card footer (total USD + cached tokens).
 
 **MANDATORY: per-phase token narration on completion (v9.10.2).** The native
 TaskList widget cannot display per-phase tokens  -  it shows name, status, and
@@ -203,9 +222,22 @@ Phase <N> <name> tamamlandi - ~<in> giris / ~<out> cikis token (<model>, ~$<usd>
 Phase <N> <name> done - ~<in> in / ~<out> out tokens (<model>, ~$<usd>)
 ```
 
-USD comes from `cost-table.json` rates for the phase's model (same math as
-`render-agent-log-cost.sh`: floor to cents). Phases with zero recorded tokens
-print `(no LLM calls)` instead of fabricating numbers.
+USD comes from `phase-tracker.sh cost <N>` - the single pricing implementation
+(cost-table.json rates, cached tokens at the discounted rate, floored to
+cents; prints `-` when the model is unknown). Do not re-implement the math
+inline. Phases with zero recorded tokens print `(no LLM calls)` instead of
+fabricating numbers.
+
+**Completion tile suffix (Claude Code).** The native widget cannot show
+per-phase tokens, but subject edits after creation are safe (tile order is
+fixed at TaskCreate time). So on phase completion, in addition to the
+narration line, append the spend to the tile subject:
+
+```text
+TaskUpdate({taskId: <phase_task>, subject: "Phase 3: Dev · ~35k tok · ~$0.26"})
+```
+
+Skip the suffix when the phase recorded zero tokens (subject stays clean).
 
 **Honesty note:** on Claude Code the orchestrator does not receive its own
 usage metering, so per-phase counts are content-size estimates (chars/4 for
@@ -259,11 +291,22 @@ When `/multi-agent:resume <task_id>` is called:
 
 The `tasklist_id` meta from the previous session is replaced with the new IDs during resume.
 
+## Continuation runs (finish / manual-test)
+
+A pre-existing `tracker-state.json` for the task is never re-initialized. Rules for any command that continues an earlier run (`/multi-agent:finish`, `/multi-agent:manual-test`, resume):
+
+1. `init` runs ONLY when no state file exists for the task. Otherwise the existing file is kept - phase history (elapsed, tokens, model, meta) survives.
+2. The continuing command re-declares its phase set with `add` - `add` is idempotent, so existing phases keep their name, status, and token history; only genuinely new phases are appended. The card renders phases sorted by numeric id, so mixed sets stay in order.
+3. If Phase 5 was left `in_progress` with `Now: awaiting local test (user)`, the continuing command marks it `update 5 completed` + `meta 5 Result "local test done (user)"` before its own work starts (finish may re-open it with `update 5 in_progress` when its build+test gate runs; elapsed keeps the original `started_at`, which is acceptable).
+4. On Claude Code, rebuild the FULL TaskList from the state file (completed tiles included) in phase order before any `TaskUpdate`, refreshing every `tasklist_id` meta - exactly the Resume behaviour above.
+5. Print ONE line in `outputLanguage` summarizing the inherited history, e.g. `Continuing PROJ-12345: phases 0-3 finished earlier (12m, 38.4k tok, ~$0.74)` (USD via `cost total`), then `render`.
+
 ## Anti-patterns
 
 ❌ **TaskList only** → `:resume` will not work; no run history is preserved.
 ❌ **`phase-tracker.sh` only** in Claude Code → the user sees no widget, only bash stdout snapshots  -  the #1 source of "I see no phases" complaints.
 ❌ **Wiring `phase-tracker.sh render` to `statusLine` config** → it drops below the screen as a placeholder; the user complained, removed in v7.9.0.
+❌ **One monolithic subagent call for a whole multi-task phase** → the tile freezes for the entire phase (no `activeForm`, no `tokens`, no `now`)  -  the user sees a dead widget for 20+ minutes. Chunk per task; see "Delegated phases" above.
 
 ## Verification
 

package/pipeline/commands/multi-agent/resume.md

@@ -31,6 +31,10 @@ Resume a paused or failed task from the last successful phase.
      - Phase 3 code → already in the worktree
    - Recent `git log --oneline -10` in the worktree grounds what was actually committed vs. claimed.
 
-4. **Continue the pipeline**  -  start from the next phase (same pipeline as the main multi-agent command).
+4. **Rebuild the phase tiles**  -  load `tracker-state.json` for the task (never re-init it; `refs/tracker-contract.md` "Resume behaviour" + "Continuation runs"):
+   - Claude Code: `TaskCreate` every phase from the state file in phase order, then `TaskUpdate` each to its stored status, and replace every `tasklist_id` meta with the new IDs.
+   - Other CLIs: a single `bash $HOME/.claude/scripts/phase-tracker.sh render`.
 
-5. **Log**: `🔄 Resumed {JIRA-KEY}-{id} from Phase {N}`
+5. **Continue the pipeline**  -  start from the next phase (same pipeline as the main multi-agent command).
+
+6. **Log**: `🔄 Resumed {JIRA-KEY}-{id} from Phase {N}`

package/pipeline/commands/multi-agent/sync.md

@@ -58,7 +58,7 @@ Run every step automatically:
 Step 0: FIGMA_SYNC  SKIP (deprecated  -  feedback_figma_source_deprecated)
 Step 1: PLATFORM    Detect macOS / Linux / Windows (Git Bash / WSL); export PLATFORM env
 Step 1.5: DETECT    Compare timestamps, find stale targets
-Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 35 sub-command skills)
+Step 2: COPILOT     Claude Code -> Copilot CLI (instructions + 37 sub-command skills)
 Step 3: REPO        Claude Code -> pipeline repo (genericized, personal data scrub, bash -n on all sh)
 Step 3c: PLUGINS    pipeline shared/external -> multi-agent-plugins marketplace (rebuild knowledge/,
                      bump changed plugins' patch version, commit + push the plugins repo)
@@ -277,14 +277,14 @@ This runs on the Claude <-> Copilot axis — the two CLIs the pipeline supports
 |-------------|-------------|
 | `~/.claude/commands/multi-agent/{cmd}.md` | `~/.copilot/skills/multi-agent-{cmd}/SKILL.md` |
 
-**35 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
+**37 commands are synced** (canonical inventory  -  must match `cross-cli-contract.md` section 1; drift = contract violation):
 
 ```
 analysis, analysis-resolve, autopilot, build-optimize, channels, delete, dev,
 dev-autopilot, dev-local, dev-local-autopilot, diff-explain, finish, garbage-collect,
-help, issue, jira, kill, language, local, local-autopilot, log, manual-test,
-prune-logs, purge, refactor, resume, review, scan, search, setup, stack, status,
-sync, test, update
+generate-bug, generate-task, help, issue, jira, kill, language, local,
+local-autopilot, log, manual-test, prune-logs, purge, refactor, resume, review,
+scan, search, setup, stack, status, sync, test, update
 ```
 
 **NOT synced**: `refs/*`  -  lazy-load references, Claude Code specific

package/pipeline/commands/multi-agent.md

@@ -77,6 +77,8 @@ Lib scripts (`~/.claude/lib/`):
 | `analysis ["<feature>"]` | Standalone feature-spec analizi: Figma / Swagger / Confluence / Jira / repo girdileri sabit 7-bölümlük şablona dökülür, humanizer'dan geçer, Local/Confluence/Jira hedef(ler)ine post edilir. Worktree veya commit yok. Dev'e zincirleme yok. |
 | `build-optimize` | iOS-only Xcode build performance wrapper. Vendored `xcode-build-orchestrator`'a dispatch eder; benchmark + compilation / project / SPM analyzer'lar + recommend-first plan `.build-benchmark/optimization-plan.md`. Non-iOS stack'lerde fail-fast. |
 | `channels [PR-url\|#N\|Jira-url\|Jira-id] [--channels pr,jira,confluence,wiki] [--content normal,test,auto-diff,note] [--message "..."]` | Post task report to multi-select channels (PR description, Jira comment, Confluence page, Wiki pages) with multi-select content sources. Humanizer pass per-channel. Bitbucket PR updates use reviewer-preserving PUT. Phase 7 delegates to this command; also invocable post-hoc for fixes made outside the pipeline. No worktree. |
+| `generate-task ["desc"] [figma-url]` | Create a standards-compliant Jira **Task**: mines the project's recent Tasks for conventions (summary format, template, labels, priority), detects the active sprint, asks about unknown fields, then full draft preview + explicit approval before create. No worktree, no commits. |
+| `generate-bug ["desc"] [figma-url]` | Create a standards-compliant Jira **Bug**: same convention mining + active-sprint detection; free-text logs/devices map to Steps to Reproduce / Environment; full draft preview + explicit approval before create. No worktree, no commits. |
 | `test` or `test [args]` | UI Bug Hunter  -  screenshot + tap + analyze on booted simulator via MCP (read `$HOME/.claude/commands/sim-test.md`). `/multi-agent:test` also resolves here via the `commands/multi-agent/test.md` delegate. |
 | `manual-test [#id]` | Phase 5 standalone Manual Test  -  checks out the task branch, prints Xcode / SourceTree hints, waits for user verdict (`ok` / `fix: ...`). |
 | `stack [ios\|android\|backend\|mobile\|all]` | Swap skills for next conversation. No arg = show current stack. |
@@ -116,6 +118,8 @@ This command uses lazy loading for token efficiency. Read the relevant sub-file
 | `local-autopilot` | `$HOME/.claude/commands/multi-agent/local-autopilot.md` |
 | `dev-local` | `$HOME/.claude/commands/multi-agent/dev-local.md` |
 | `dev-local-autopilot` | `$HOME/.claude/commands/multi-agent/dev-local-autopilot.md` |
+| `generate-task` | `$HOME/.claude/commands/multi-agent/generate-task.md` (loads `refs/generate-issue.md`) |
+| `generate-bug` | `$HOME/.claude/commands/multi-agent/generate-bug.md` (loads `refs/generate-issue.md`) |
 | `stack` | `$HOME/.claude/commands/multi-agent/stack.md` |
 | `language` | Handled inline  -  set/show prompt language in preferences |
 | SwiftUI component task (iOS) | `$HOME/.claude/commands/multi-agent/refs/swiftui-guide.md` |

package/pipeline/lib/figma-mcp-refresh.sh

@@ -0,0 +1,79 @@
+#!/usr/bin/env bash
+# figma-mcp-refresh.sh  -  silent Figma MCP (figu_) token renewal via OAuth refresh grant.
+#
+# Used by the Phase 0 token pre-flight (refs/phases/phase-0-init.md Step 0.7) and the
+# expired-token decision (refs/keychain.md). Never prints token values  -  status lines only.
+#
+# Flow:
+#   1. Resolve the access-token Keychain name from prefs.global.keychainMapping.figma_mcp.
+#   2. Read the refresh token from "<name>_Refresh" (written by the user's generation script).
+#   3. Read client credentials from .figma-oauth.json next to prefs.global.tokenScripts.figma_mcp.
+#   4. POST grant_type=refresh_token to the Figma token endpoint.
+#   5. On success save the new access token (and rotated refresh token) back to the Keychain.
+#
+# Exit codes:
+#   0  renewed (access token replaced in Keychain)
+#   1  refresh grant rejected by Figma (refresh token dead  -  run the generation script)
+#   2  prerequisites missing (no mapping / no refresh entry / no oauth config)
+
+set -euo pipefail
+
+PREFS_FILE="${PREFS_FILE:-$HOME/.claude/multi-agent-preferences.json}"
+TOKEN_ENDPOINT="https://api.figma.com/v1/oauth/token"
+ACCOUNT="${USER:-$(whoami)}"
+
+say() { printf '%s\n' "$*"; }
+
+[ -f "$PREFS_FILE" ] || { say "figma-mcp-refresh: prefs file missing ($PREFS_FILE)"; exit 2; }
+
+KEY_NAME=$(jq -r '.global.keychainMapping.figma_mcp // empty' "$PREFS_FILE")
+[ -n "$KEY_NAME" ] || { say "figma-mcp-refresh: keychainMapping.figma_mcp not set"; exit 2; }
+
+REFRESH_KEY="${KEY_NAME}_Refresh"
+REFRESH_TOKEN=$(security find-generic-password -s "$REFRESH_KEY" -w 2>/dev/null || true)
+[ -n "$REFRESH_TOKEN" ] || { say "figma-mcp-refresh: no refresh token at '$REFRESH_KEY'"; exit 2; }
+
+SCRIPT_PATH=$(jq -r '.global.tokenScripts.figma_mcp // empty' "$PREFS_FILE")
+OAUTH_CONFIG=""
+if [ -n "$SCRIPT_PATH" ]; then
+  OAUTH_CONFIG="$(dirname "$SCRIPT_PATH")/.figma-oauth.json"
+fi
+[ -n "$OAUTH_CONFIG" ] && [ -f "$OAUTH_CONFIG" ] || { say "figma-mcp-refresh: .figma-oauth.json not found (tokenScripts.figma_mcp unset or sibling config missing)"; exit 2; }
+
+CLIENT_ID=$(jq -r '.client_id // empty' "$OAUTH_CONFIG")
+CLIENT_SECRET=$(jq -r '.client_secret // empty' "$OAUTH_CONFIG")
+[ -n "$CLIENT_ID" ] || { say "figma-mcp-refresh: client_id missing in .figma-oauth.json"; exit 2; }
+
+CURL_ARGS=(
+  --data-urlencode "grant_type=refresh_token"
+  --data-urlencode "refresh_token=${REFRESH_TOKEN}"
+  --data-urlencode "client_id=${CLIENT_ID}"
+)
+[ -n "$CLIENT_SECRET" ] && CURL_ARGS+=( --data-urlencode "client_secret=${CLIENT_SECRET}" )
+
+RESPONSE=$(curl -s --max-time 20 -X POST "$TOKEN_ENDPOINT" \
+  -H "Content-Type: application/x-www-form-urlencoded" \
+  "${CURL_ARGS[@]}")
+
+NEW_ACCESS=$(printf '%s' "$RESPONSE" | jq -r '.access_token // empty' 2>/dev/null || true)
+NEW_REFRESH=$(printf '%s' "$RESPONSE" | jq -r '.refresh_token // empty' 2>/dev/null || true)
+EXPIRES_IN=$(printf '%s' "$RESPONSE" | jq -r '.expires_in // "?"' 2>/dev/null || true)
+
+if [ -z "$NEW_ACCESS" ]; then
+  ERR=$(printf '%s' "$RESPONSE" | jq -r '.error // .message // "unknown"' 2>/dev/null || echo "unknown")
+  say "figma-mcp-refresh: refresh grant rejected ($ERR)  -  regenerate via tokenScripts.figma_mcp"
+  exit 1
+fi
+
+# Save new access token first, then the rotated refresh token  -  order matters so a
+# mid-write failure never leaves us with a lost refresh token AND a stale access token.
+security delete-generic-password -s "$KEY_NAME" -a "$ACCOUNT" >/dev/null 2>&1 || true
+security add-generic-password -s "$KEY_NAME" -a "$ACCOUNT" -w "$NEW_ACCESS" -T "" -U
+
+if [ -n "$NEW_REFRESH" ]; then
+  security delete-generic-password -s "$REFRESH_KEY" -a "$ACCOUNT" >/dev/null 2>&1 || true
+  security add-generic-password -s "$REFRESH_KEY" -a "$ACCOUNT" -w "$NEW_REFRESH" -T "" -U
+fi
+
+say "figma-mcp-refresh: renewed '$KEY_NAME' (expires_in=${EXPIRES_IN}s, refresh $( [ -n "$NEW_REFRESH" ] && echo rotated || echo unchanged ))"
+exit 0

package/pipeline/preferences-template.json

@@ -14,6 +14,7 @@
       "firebase": null,
       "jenkins": null
     },
+    "tokenScripts": {},
     "platformIdentityRouting": {},
     "recentProjects": [],
     "recentBranches": {},
@@ -153,4 +154,4 @@
       "overrides": {}
     }
   }
-}
+}

package/pipeline/schemas/prefs.schema.json

@@ -179,6 +179,17 @@
             }
           }
         },
+        "tokenScripts": {
+          "type": "object",
+          "additionalProperties": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "default": {},
+          "description": "Maps service ids to user-owned token generation scripts (absolute paths, personal - never synced). Used by the Phase 0 token pre-flight: figma_mcp silent renewal reads the .figma-oauth.json next to tokenScripts.figma_mcp; the 'Regenerate now (script)' option runs the script itself."
+        },
         "platformIdentityRouting": {
           "type": "object",
           "description": "v2.1.0+. Maps repo URL glob patterns to identity names. Used in Phase 0 to auto-select git identity + PAT based on repo origin. Prevents corporate identity leaking into personal repos and vice versa.",
@@ -701,6 +712,30 @@
           "default": false,
           "description": "v6.1.0+ \u2014 Phase 4 Step 2.5 rebuttal round. When reviewers disagree (mixed blocker/approved verdict), each reviewer is re-prompted with the others' opposing arguments for one additional round before triage. Lifts signal quality on ambiguous findings at ~1\u00d7 Step 2 token cost. Off by default \u2014 flip for security-critical or release-branch reviews."
         },
+        "updateCheck": {
+          "type": "object",
+          "additionalProperties": false,
+          "description": "v10.9+ - Phase 0 Step 0.6 advisory version check. Once per ttlHours window, a bounded (3s) registry read compares the installed version against dist-tags.latest. Newer version found: interactive modes ask 'Update now / Continue' (yes runs the /multi-agent:update flow, then the run continues); autopilot logs one line and never asks. Offline/failed checks are silent; the step never blocks the pipeline.",
+          "properties": {
+            "enabled": {
+              "type": "boolean",
+              "default": true,
+              "description": "Master switch. On by default - the cost is at most one 3s-bounded curl per ttlHours."
+            },
+            "ttlHours": {
+              "type": "integer",
+              "minimum": 1,
+              "maximum": 168,
+              "default": 24,
+              "description": "Cache window for the registry read."
+            },
+            "autoUpdate": {
+              "type": "boolean",
+              "default": false,
+              "description": "When true, skip the question and run the update flow automatically before the run starts (interactive AND autopilot). Off by default - self-modifying ~/.claude without asking is a surprise."
+            }
+          }
+        },
         "verifyByTest": {
           "type": "object",
           "additionalProperties": false,

package/pipeline/schemas/token-budget.json

@@ -3,15 +3,15 @@
   "$id": "https://github.com/mmerterden/multi-agent-pipeline/pipeline/schemas/token-budget.json",
   "description": "Per-phase token budget for lazy-loaded pipeline docs. Enforced by smoke-token-budget.sh.",
   "phases": {
-    "phase-0-init":      { "max_tokens": 11250, "warn_tokens": 9900 },
+    "phase-0-init":      { "max_tokens": 12400, "warn_tokens": 10900 },
     "phase-1-analysis":  { "max_tokens": 3750, "warn_tokens": 3300 },
     "phase-2-planning":  { "max_tokens": 6500, "warn_tokens": 5750 },
-    "phase-3-dev":       { "max_tokens": 7650, "warn_tokens": 6750 },
-    "phase-4-review":    { "max_tokens": 11100, "warn_tokens": 9750 },
-    "phase-5-test":      { "max_tokens": 2300, "warn_tokens": 2000 },
-    "phase-6-commit":    { "max_tokens": 5550, "warn_tokens": 4900 },
+    "phase-3-dev":       { "max_tokens": 7900, "warn_tokens": 6950 },
+    "phase-4-review":    { "max_tokens": 13250, "warn_tokens": 11650 },
+    "phase-5-test":      { "max_tokens": 2550, "warn_tokens": 2250 },
+    "phase-6-commit":    { "max_tokens": 6150, "warn_tokens": 5400 },
     "phase-7-report":    { "max_tokens": 5600, "warn_tokens": 4950 }
   },
-  "total_max_tokens": 46500,
-  "note": "Token estimate = ceil(chars / 4). Per-phase budget rule: warn = current+10% (rounded to nearest 50), max = current+25%. Gives ~6 edit cycles of headroom before warn trips  -  intentionally quiet under normal maintenance, loud when a phase grows unusually. Only the active phase is loaded (lazy). Recalibrated at v10.0.0 after the validator/consistency/simplifier/lesson gate contracts landed in phases 1-4 (prose already compressed; the residual growth is the gate contracts themselves)."
+  "total_max_tokens": 50000,
+  "note": "Token estimate = ceil(chars / 4). Per-phase budget rule: warn = current+10% (rounded to nearest 50), max = current+25%. Gives ~6 edit cycles of headroom before warn trips  -  intentionally quiet under normal maintenance, loud when a phase grows unusually. Only the active phase is loaded (lazy). Recalibrated at v10.0.0 after the validator/consistency/simplifier/lesson gate contracts landed in phases 1-4. Recalibrated again at v10.9.0 after the verify-by-test (Phase 4 Step 3.7), update-check (Phase 0 Step 0.6), immutable-test (Phase 3 GREEN) and redTests re-entry contracts landed  -  Step 3.7 prose was compressed to a pointer into refs/features/verify-by-test.md before the recalibration."
 }

package/pipeline/scripts/README.md

@@ -24,6 +24,7 @@ Validate contracts. Each emits `══ <name> smoke: N passed, M failed ══`
 - `smoke-phase4-triage.sh`  -  Phase 4 reviewer → triage flow
 - `smoke-verify-by-test.sh`  -  Phase 4 Step 3.7 verify-by-test contract (v10.8.0)
 - `smoke-handoff-contract.sh`  -  phase-boundary structured handoff + handoff-first resume (v10.8.0)
+- `smoke-update-check.sh`  -  Phase 0 Step 0.6 advisory update-check contract (v10.9.0)
 
 ### Schema + state
 - `smoke-schema-validation.sh`  -  all JSON schemas validate

package/pipeline/scripts/fixtures/install-layout.tsv

@@ -1,16 +1,16 @@
 .claude/CLAUDE.md	1
 .claude/agents	8
-.claude/commands	89
-.claude/lib	23
+.claude/commands	92
+.claude/lib	24
 .claude/multi-agent-preferences.json	1
 .claude/rules	12
 .claude/schemas	23
-.claude/scripts	169
+.claude/scripts	174
 .claude/settings.json	1
 .claude/skills	560
 .copilot/agents	8
 .copilot/copilot-instructions.md	1
-.copilot/lib	23
+.copilot/lib	24
 .copilot/schemas	23
-.copilot/scripts	169
-.copilot/skills	596
+.copilot/scripts	174
+.copilot/skills	598