@mmerterden/multi-agent-pipeline 20.20.0 → 20.22.0

package/pipeline/skills/.skill-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-10-11T20:10:05Z",
+  "generatedAt": "2026-10-12T21:38:23Z",
   "skillCount": 228,
   "entries": [
     {
@@ -165,7 +165,7 @@
     },
     {
       "path": "shared/core/multi-agent-review/SKILL.md",
-      "sha256": "2b6934d6086a467bdf145b326061ab4b83d5479bfb1a2fb36420ff8012a02e5d"
+      "sha256": "1a22618e6d3d9d07b267bd61fc591bb33726e1d7ef8567285401f61bc7be0ad5"
     },
     {
       "path": "shared/core/multi-agent-route-off/SKILL.md",
@@ -173,11 +173,11 @@
     },
     {
       "path": "shared/core/multi-agent-route-on/SKILL.md",
-      "sha256": "a807767460b09455087d48a7dd45036be788f67997475360acab29f2422f425b"
+      "sha256": "97c76d711454e6bc9edfd47344bbeab7f73cf72c116cca92cffacdcda7fe96b1"
     },
     {
       "path": "shared/core/multi-agent-route-status/SKILL.md",
-      "sha256": "b473b670b3f8535b295752eb5aed8b01cba8d1ed6763ae4d80d9cc2dbb1f7794"
+      "sha256": "869689dbf84edece67168a892a61b51459ff6c15cbf7dafe40c2b774f875b9f0"
     },
     {
       "path": "shared/core/multi-agent-routines/SKILL.md",
@@ -213,7 +213,7 @@
     },
     {
       "path": "shared/core/multi-agent-setup/SKILL.md",
-      "sha256": "427df811e5130da1ab6e23ff78202eb9134fb76bcd601924fba5668cbd630158"
+      "sha256": "79a4afa655df12221a25bc386a32e61c38016d2de660dd618b404ca8bb0b28d3"
     },
     {
       "path": "shared/core/multi-agent-stack/SKILL.md",
@@ -269,7 +269,7 @@
     },
     {
       "path": "shared/core/multi-agent/SKILL.md",
-      "sha256": "3dd44ccc00e41c09e59ad223900a391f80158bd3f69e45d67c684285bc42418d"
+      "sha256": "a39f712426638e7955db9171c950be720f11c861621884e628c81a0b6a49de5d"
     },
     {
       "path": "shared/external/accessibility-compliance-accessibility-audit/SKILL.md",

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

@@ -122,6 +122,8 @@ export CLAUDE_CODE_SUBAGENT_MODEL="$resolved_model"
 
 **Precedence:** per-dispatch `PHASE_MODEL_OVERRIDE` > `prefs.global.modelRouting` rule > persona `preferredModel` > global default (`opus`). Routing here is Anthropic-only: features/model-fallback.md "Routing at dispatch".
 
+**Simple text tasks (`delegate`):** before summarizing a log or document, extracting fields, labelling or drafting a translation or commit body in-session, ask `"$HOME/.claude/lib/model-dispatch.sh" delegate --default host`. `free` means call `llm_delegate`; `ESCALATE_TO_CLAUDE` or any other answer means do it in-session. Never for code, plans, reviews or triage. Task list and rules: `$HOME/.claude/multi-agent-refs/features/free-models.md`.
+
 **Observability:** emit `phase.agent.dispatch` OTel span with `{persona, resolved_model, override_source}` attributes when `MULTI_AGENT_OTEL_SPANS=1` (see `phase-tracker.sh`).
 
 ## Skill loading and injection

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

@@ -76,7 +76,11 @@ Skip Phase 0-3 and review a diff only. Input shapes: a PR (`#N`, `repo#N`, GitHu
    resolves whose `stack` is the other mobile platform and the diff touches a screen, a
    service, a request model or a localization file, compare the change against that repo
    on four axes: endpoints called, parameters sent, business rules around the call,
-   localization keys used. The counterpart is resolved automatically and in both
+   localization keys used. When the project belongs to a product
+   (`prefs.global.products`), the counterparts are the product's other repositories,
+   resolved with `product-context.mjs refs` and compared at their latest integration
+   branch through the toolkit's `repo_*` tools, pinned to a sha
+   (`features/product-context.md`). Otherwise the counterpart is resolved automatically and in both
    directions (ios ↔ android) from four sources in this order, first hit wins:
    `--with <path|owner/repo>` (a one-off override, remembered like any other resolution),
    then a remembered `prefs.projects[<slug>].counterpartRoots[]`, then the primary

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

@@ -2,7 +2,7 @@
 name: multi-agent-route-on
 description: "Enable policy-driven model routing: pick a strategy, a scope, and the rules that say which rung a call lands on. Use when asked to turn model routing on."
 user-invocable: true
-argument-hint: "[--strategy=manual|task-fit|cost-ceiling] [--scope=subagent,bulk-read,research]"
+argument-hint: "[--free [--allow-training] | --no-free] [--strategy=manual|task-fit|cost-ceiling] [--scope=subagent,bulk-read,delegate,research]"
 metadata:
   language: en
 ---
@@ -24,7 +24,8 @@ Routing ships **off**. This is the command that turns it on, and it writes to
 ```
 
 Ordered, first match wins. `when` matches on `persona`, `phase` (0..5) or
-`taskKind`; `prefer` lists rungs in descending preference.
+`taskKind`; `prefer` lists rungs in descending preference. `free` is a rung too,
+honoured only at `bulk-read` and `delegate` and only while `--free` is on.
 
 **Rung names are the contract; model ids are not.** `opus` is a rung here and a
 model id in `cost-table.json`, and the second can change without anyone editing
@@ -37,18 +38,41 @@ Set rules with:
 bash "$HOME/.claude/lib/route-state.sh" set-rules path/to/rules.json
 ```
 
+## Free models: `--free`
+
+```bash
+bash "$HOME/.claude/lib/route-state.sh" on --free
+```
+
+Layer 2. Simple text work the pipeline does itself - a large-file read, a log or
+document summary, field extraction, a label, a translation or commit-body draft -
+goes to the multi-agent-toolkit's verified free-model chain first. Every answer
+is checked against its source before it is used; when none passes, Claude does
+the task as before. Decisions, plans, code, reviews and triage never leave Claude.
+
+`--free` turns on `modelRouting.free`, adds `bulk-read` and `delegate` to the
+scope, and lists which providers are usable. With none, it says exactly which key
+to add: one free Groq key is enough. `--allow-training` also admits free tiers
+that may train on prompts; leave it off for corporate code and tickets.
+`--no-free` turns only the free chain off. Full contract, the task list for
+development and analysis, and unattended behaviour:
+`$HOME/.claude/multi-agent-refs/features/free-models.md`.
+
 ## Strategies
 
 | Strategy | What it does |
 |---|---|
 | `manual` | only the explicit rules apply, nothing is inferred. The default, because a router that guesses is a router nobody can predict |
-| `task-fit` | a rule may match on `taskKind`, and the cheapest rung clearing it is chosen |
-| `cost-ceiling` | rungs downgrade as the run approaches `budgetCeilingUsd` |
+| `task-fit` | the matched rule's rungs are tried cheapest first (cost-table prices, `free` first) |
+| `cost-ceiling` | the rule's order holds until the run reaches the warn threshold of `budgetCeilingUsd`, then the cheapest rung is tried first |
+
+`set-rules` checks every rule against the schema and the cost table and writes
+nothing if one fails: an unknown rung, a phase outside 0-5, an unknown key.
 
 ## Scope, and the value that is not in it
 
 `scope` names the call sites routing may act on: `subagent`, `bulk-read`,
-`research`. Every one of them is a call **this pipeline makes itself**.
+`delegate`, `research`. Every one of them is a call **this pipeline makes itself**.
 
 There is no `host-session` value, and that absence is enforced by that schema
 rather than written as advice. Routing a host session means rewriting the CLI's
@@ -61,8 +85,8 @@ Passing `--scope=host-session` is refused with that reason, not ignored.
 
 On Claude Code a subagent cannot be dispatched to a non-Anthropic model: subagent
 dispatch belongs to the host, not to us. So Phase 1, 2 and 3 personas stay inside
-the Anthropic ladder no matter what the rules say, and external providers apply
-only at `bulk-read` and `research`, where the pipeline makes the HTTP call.
+the Anthropic ladder no matter what the rules say, and the `free` rung applies
+only at `bulk-read` and `delegate`, where the pipeline makes the call itself.
 
 This is printed by `route-status` on every invocation instead of living in a doc,
 because the question it answers - "routing is on, why is the reviewer still on

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

@@ -28,13 +28,23 @@ A disabled router with rules is deliberately not reported as "off" alone: that
 reads as "unconfigured" and sends the user through `route-on`'s questions a
 second time.
 
+## Free models and what they saved
+
+With `route-on --free`, status also prints `free: true` with its data policy,
+where the free chain answers first (`bulk-read`, `delegate`), and the last seven
+days from the toolkit's usage log: tasks answered free and verified, answers
+served from cache, tasks handed back to Claude, and the input and output tokens
+kept off Claude with an estimated saving at haiku rates. The estimate is labelled
+as one: it prices the tokens at the rung the task would otherwise have used.
+
 ## The limit, printed every time
 
 On Claude Code a subagent cannot be sent to a non-Anthropic model. Subagent
 dispatch belongs to the host; the pipeline asks for a persona and the host
 decides what answers. So Phase 1, 2 and 3 personas stay inside the Anthropic
-ladder whatever the rules say, and an external provider is only reachable where
-the pipeline makes the HTTP call itself - `bulk-read.sh` and `research_ask`.
+ladder whatever the rules say, and a free model answers only where the pipeline
+makes the call itself - `bulk-read.sh` and the `delegate` call site - and only
+after the toolkit verified its answer against the source.
 
 This paragraph is output, not documentation, because the alternative is the
 question arriving later as "routing is on but the reviewer is still on Opus, is

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

@@ -24,6 +24,10 @@ node "$HOME/.copilot/scripts/doctor.mjs"
 
 Run it before the first question and again at the end. The first run makes setup targeted: never ask for a token that is already mapped and answering. The second run is how setup ends - "setup complete" is a claim, and the doctor's exit code is the evidence. Report both in `outputLanguage`; if the second run still shows a BLOCK, say so plainly rather than closing on the word "complete".
 
+## Sections
+
+`/multi-agent-setup hosts`: the Step 3.5 host prompt per mapped hosted service, then Token Save Flow Step 3.7 per mapped GitHub/Bitbucket token. `accounts`: Step 3.6. `jira-keys`: the Jira key mapping. Tokens are left alone.
+
 ## Setup (Credential Store + Git Identity Onboarding)
 
 Uses `~/.copilot/lib/credential-store.sh` to read/write secrets in the macOS Keychain (`security`, built in); the pipeline is macOS only (ADR-0012). Run `~/.copilot/lib/credential-store.sh doctor` first  -  it prints the platform and whether the backend is usable. The shell driver auto-delegates `get`/`set`/`delete` to the deterministic Python helper at `$HOME/.copilot/scripts/keychain.py` (Python 3 stdlib only, no external deps). The Python path writes both `-l` (label) and `-s` (service) attributes so items are findable regardless of how callers look them up. Set `KEYCHAIN_DELEGATE=0` to force the raw shell path.
@@ -189,11 +193,12 @@ The Step 2 discovery summary is never the end of setup. Immediately after showin
 10. `jenkins`
 11. App Store Connect block (Step 3b; only when the target repo is iOS)
 12. Google Play block (Step 3d; only when the target repo is Android)
+13. Free-model keys `llm-<id>` (only after `route-on --free`): `$HOME/.claude/multi-agent-refs/setup/free-models.md`
 
 Loop rules:
 
 - **One prompt per service.** Never collapse the list into a single "add missing tokens now?" yes/no, and never offer one multi-select covering all services: each service has its own source URL, key name, identity binding and host prompt, so each gets its own Token Save Flow pass.
-- **Each service pass asks, in order: token → author → host.** Step A/B collect the secret, Step C binds the git identity (author)  -  Bitbucket and GitHub included; every saved token gets an author  -  and Step 3.5 asks the host domain inline for hosted services (jira, confluence, bitbucket, fortify, graylog) - plus the Fortify project versions and the optional Graylog test instance. GitHub and Figma skip the host question (fixed domains); `bitbucket_user` skips author binding (username, not a PAT). Never end a service pass with the token saved but the author or a required host unasked.
+- **Each service pass asks, in order: token → author → host → read binding (GitHub, Bitbucket; Token Save Flow Step 3.7).** Step A/B collect the secret, Step C binds the git identity (author)  -  Bitbucket and GitHub included; every saved token gets an author  -  and Step 3.5 asks the host domain inline for hosted services (jira, confluence, bitbucket, fortify, graylog) - plus the Fortify project versions and the optional Graylog test instance. GitHub and Figma skip the host question (fixed domains); `bitbucket_user` skips author binding (username, not a PAT). Never end a service pass with the token saved but the author or a required host unasked.
 - **Skip is per-service.** A Skip answer leaves that service's `keychainMapping` at `null` and the loop continues with the next service. Skips never abort the loop.
 - **`figma` and `figma_mcp` are distinct credentials for distinct tiers  -  ask both.** Skipping the PAT does not imply skipping MCP, and vice versa. The `figma_mcp` pass opens with a Remote / Local mode question instead of a clipboard paste (see "Figma MCP Setup" below): Remote generates a `figu_` OAuth token for the current user, Local wires the PAT-based local server.
 - The loop ends only when every missing service has been asked exactly once; then continue to Step 4 (Verify all).
@@ -218,17 +223,15 @@ Runs inside Step 3, only when the target repo is Android. One entry, `google_pla
 
 ### Step 3.5  -  Host Prompt (embedded in Token Save Flow)
 
-Full procedure: `$HOME/.claude/multi-agent-refs/setup/token-save-flow.md`. Read it for the host question inside the Token Save Flow.
+Part of the Token Save Flow reference above.
 
 ### Step 3.6  -  Per-account host overrides (optional)
 
 **Runs only when** `~/.copilot/lib/account-resolver.sh` returns **more than one** account AND at least one account has Jira or Bitbucket tokens.
 
-Use case: one user with two identities (e.g. agency + client), each with its own Jira host; `prefs.global.hosts.jira` holds only one default.
-
-For each non-default account, ask once: "Account {label} has Jira/Bitbucket tokens but no host override yet. Use the global default ({hosts.jira}) or set a per-account host?" with options **1) Use global default** / **2) Set per-account host**. On `2`, prompt for `jiraHost` / `bitbucketHost` / `confluenceHost` (each optional) and save to `prefs.global.accounts[]`, e.g. `{ "id": "client-x", "jiraHost": "jira.client-x.example.com", "bitbucketHost": "bitbucket.client-x.example.com" }`.
+For each non-default account (two identities, each with its own Jira host), ask once: "Account {label} has Jira/Bitbucket tokens but no host override yet. Use the global default ({hosts.jira}) or set a per-account host?" with options **1) Use global default** / **2) Set per-account host**. On `2`, prompt for `jiraHost` / `bitbucketHost` / `confluenceHost` (each optional) and save to `prefs.global.accounts[]`, e.g. `{ "id": "client-x", "jiraHost": "jira.client-x.example.com", "bitbucketHost": "bitbucket.client-x.example.com" }`.
 
-`account-resolver.sh` reads this on every invocation; per-account override wins over `global.hosts.*`. Skip this step on autopilot  -  `accounts[]` stays empty until the user opts in via `/multi-agent-setup accounts`, which opens this editor without re-running token discovery.
+`account-resolver.sh` reads this on every invocation; per-account override wins over `global.hosts.*`. Skip this step on autopilot; `/multi-agent-setup accounts` opens it later.
 
 ---