@mmerterden/multi-agent-pipeline 19.1.3 → 19.1.4

package/CHANGELOG.md

@@ -14,6 +14,55 @@ Internal file-layout changes that don't affect the slash-command surface are sti
 
 ---
 
+## [19.1.4] - 2026-09-21
+
+### Added
+
+- **`smoke-gui-json-contract.sh` - the JSON a non-model consumer decodes stays
+  put.** `runs-index.mjs` and `update-check.sh` already had their output pinned;
+  `doctor.mjs --json` and `autopilot-status.sh --json` did not, and a renamed key
+  there breaks every consumer at once while the pipeline's own callers, which
+  read the human output, notice nothing. The gate drives both scripts and reads
+  their real stdout: `checks[]` with `{id, severity, step, problem, detail}` and
+  unique ids, `exit` an integer, severities from the documented set, the queue
+  triple as lists, the counters as numbers and `on` as a boolean. Adding a key
+  is deliberately not a failure - a decoder ignores what it does not know.
+- **`smoke-no-confessional-prose.sh`** - shipped comments and docs describe the
+  code, not the project's own history. A reason a rule exists still ships; a
+  past-defect narration belongs in this file. Four allow-list entries are
+  anchored to the lines that carry them, so a stale exemption fails the gate.
+- **A deterministic test for write-state's mid-write refusal.** The refusal
+  needs another writer to take the lock between acquiring it and renaming, which
+  on an idle machine is too narrow to hit and under load is a coin flip.
+  `WRITE_STATE_TEST_DELAY_MS` opens that window on purpose; the gate then asserts
+  both halves - exit 4, and nothing of that writer in the file.
+
+### Fixed
+
+- **The concurrent-writer gate counted an honest exit 4 as an unexpected code.**
+  A writer whose lock is taken mid-write refuses and writes nothing, which is the
+  same class of outcome as an exit-2 lock timeout. It is now counted with its
+  invariant attached - a refusal that wrote nothing must leave nothing behind -
+  and both refusal counts are reported so a rising one stays visible.
+- **`bulk-read.sh` claimed routing could send it outside the Anthropic ladder.**
+  It delegates to the `claude` CLI, which speaks that ladder and nothing else, so
+  the dispatcher's refusal of an external rung is the correct behaviour and the
+  comment was the wrong half. Both READMEs now state the limit: no call site
+  sends a model request itself, and a delegated read must not put a file's full
+  text outside the account that owns it.
+
+### Changed
+
+- **Both READMEs gained a "which model answers" section**, listing
+  `/multi-agent:{route-on,route-off,route-status,model}` with the two lines that
+  matter: `scope` has no `host-session` value and that is a schema gate, and an
+  external rung is refused at dispatch.
+- Confessional history removed from 57 shipped comments and doc paragraphs
+  across 40 files; each reason the rule exists was kept and rewritten with the
+  code as its subject.
+
+---
+
 ## [19.1.3] - 2026-09-21
 
 ### Fixed
@@ -101,6 +150,7 @@ them.
   is refused for a subagent, because subagent dispatch belongs to the host - the
   script says so on stderr instead of substituting an Anthropic rung and leaving
   the user believing a rule worked that never could.
+
 - `cost-table.json` rungs declare a `provider`. Without it every rung looks
   alike and the subagent limit above cannot be checked at all.
 - `smoke-model-dispatch.sh` (18 assertions). Half of them drive the router; the
@@ -495,7 +545,7 @@ gate cannot be loaded.
   and producing no effect.
 
   **Interactive runs ask at the step instead of ending at it**: open the item and
-  fix it, continue without it (recording in `state.maturity.accepted[]` *which*
+  fix it, continue without it (recording in `state.maturity.accepted[]` _which_
   gap was waved through, which is what separates an informed continue from a
   skipped check), or abort. `askInteractively: false` restores the old halt.
 
@@ -519,7 +569,7 @@ gate cannot be loaded.
 
   **The rule that shapes the rest: an edit is a reason to look again, never proof
   the gap closed.** A reply reading "will do later" moves the timestamp and fixes
-  nothing, so a changed item is re-fetched and re-scored and the *check* decides.
+  nothing, so a changed item is re-fetched and re-scored and the _check_ decides.
   Only a genuinely DIFFERENT gap set earns a second comment - otherwise an
   unattended queue turns an item into a wall of identical bot text. "Cannot tell
   whether it moved" resolves to re-check, never to wait, because folding unknown
@@ -886,6 +936,7 @@ were the same shape: a chain fixed on one side and left broken on the other.
   than attaching nothing because a present artefact does not get re-checked.
   `fit` gained `webm`, which had been falling through to the pass-through arm and
   reaching the uploader at full size.
+
 - **Continuous mode's node half still named one host.** 17.2.0 fixed the shell
   side and closed the class. `autopilot-runner.mjs` was still resolving its three
   siblings from `~/.claude/scripts`, and `autopilot-intake.mjs` looked for
@@ -1233,7 +1284,6 @@ The flow video existed as a contract with no recorder, no UI test ever ran, and
 
 - **`install/templates/` now reaches the user tree.** It shipped in the tarball and was never copied, so `setup` told people to merge `install/templates/claude-hooks.json` - a path that exists only in a checkout. From an install the instruction named a file the reader did not have, and nothing said so. The doctor's `hook-coverage` check would have been a permanent `SKIP` for the same reason.
 
-
 ### Fixed
 
 - **The widget came back empty of everything except the phase name.** The native tile renders exactly one string, its subject, so whatever a reader wants from the card has to travel in that subject. It carried `Phase 1 Analysis` and nothing else, while the tracker already held the model, the elapsed time, the tokens and the cost for that phase and the fallback card printed all four. `phase-tracker.sh subjects [id]` now renders the same values in the one shape the host accepts, `tiles` builds its `TaskCreate` calls from it, and every boundary hint re-reads it so the numbers advance instead of freezing at creation time. A phase with nothing to report is still just its name - no empty separators.
@@ -1286,7 +1336,6 @@ The flow video existed as a contract with no recorder, no UI test ever ran, and
 
 - **`council-view.mjs`** renders what each reviewer found and what triage did with it. Everything it needs was already on the state and nothing displayed it; `run-metrics.mjs` reduced it to a ratio and the rows behind the ratio were invisible. De-anonymization is safe here because it runs after triage has ruled, and the gate pins that the map reaches no prompt. `/multi-agent:log` renders it; exit 2 means the run never reached Phase 4.
 
-
 - **A validator summary that says which checks ran.** `validate-analysis-doc.mjs --report` prints every check by name with a verdict each: `ok`, a finding count, or `skipped: <reason>`. The gap it closes is specific - the traceability matrix only runs in the corporate profile, so on a global document it never executed and the output was byte-identical to "ran, found nothing". Attribution is positional and reconciles by construction, so a check added without its mark misnames a finding but can never lose one; the gate asserts the printed set equals the set the file defines. Default output is unchanged for gate callers.
 
 - **Provenance in the reports a human reads.** `evidence_digest` and `base_commit` were already in the document front-matter, on the side only a machine reads. The analysis Phase 5 report, the `review-analysis` verdict and `--report` now carry them too: a timestamp cannot separate two reports made the same day, and the first question anyone asks of an older verdict is which version of the document it judged.
@@ -1312,6 +1361,7 @@ The flow video existed as a contract with no recorder, no UI test ever ran, and
   The contract, its reasoning and the check table live in `analysis/redesign.md`, which `analysis/SKILL.md` does not name and which therefore loads only on a redesign run.
 
 - `ANALYSIS_CEILING` 155000 -> 158500, the largest single raise it has taken. What could not be moved out is the argument: the section skeletons belong in `analysis-template.md`, where every other conditional section (15.6, 16.2) is already defined; Locked 37 belongs in `analysis/locked.md`, because a decision recorded only where it is implemented is not locked; and the intake question belongs in `analysis/intake.md`, because the option is chosen before anything knows the run is a redesign. 5.9 kB stayed outside the count. Everything was compressed twice before the number was picked.
+
 ### Fixed
 
 - `learn-from-transcripts.mjs` called `process.exit(0)` on the line after writing its `--json` result, so a large mining result was cut at the 64 KB pipe buffer - the exact defect the gate added in 16.27.0 exists to prevent, in the file that motivated it. The gate caught it; the two sites it named are now a `main()` with a return.
@@ -1368,12 +1418,11 @@ The flow video existed as a contract with no recorder, no UI test ever ran, and
 
 - **Setup merged one hook event and dropped the rest.** The instruction said to deep-merge `hooks.PreToolUse`, so the capture hooks would never have installed - the fix would have shipped inert.
 
-
 ## [16.26.0] - 2026-09-09
 
 ### Fixed
 
-- **The credential store mangled every multi-line secret, and the failure surfaced three layers away.** `security` picks its output format from the *content* of the value: anything it deems non-printable - a newline included - comes back as bare hex with no marker, and the reader took that at face value. A Firebase service-account JSON went in and `7b0a2020...` came out, which is neither JSON nor base64, so the Crashlytics fetcher reported a token-exchange error for a credential that was stored perfectly. The write side had the mirror defect: `security -i` is line-oriented, so a newline inside `-w` terminated the command mid-value and the item was never written at all.
+- **The credential store mangled every multi-line secret, and the failure surfaced three layers away.** `security` picks its output format from the _content_ of the value: anything it deems non-printable - a newline included - comes back as bare hex with no marker, and the reader took that at face value. A Firebase service-account JSON went in and `7b0a2020...` came out, which is neither JSON nor base64, so the Crashlytics fetcher reported a token-exchange error for a credential that was stored perfectly. The write side had the mirror defect: `security -i` is line-oriented, so a newline inside `-w` terminated the command mid-value and the item was never written at all.
 
   `keychain.py` now reads with `-g` and decodes on the explicit `0x` marker rather than guessing from shape, and writes with `-X <hex>` so no value can be cut at a newline. Lookup also walks all four attribute conventions (`-a`+`-l`, `-a`+`-s`, `-l`, `-s`) instead of one.
 
@@ -1397,7 +1446,7 @@ The flow video existed as a contract with no recorder, no UI test ever ran, and
 
 - **`firebase-app-discovery.sh` - the repo already knew the appIds.** Every Crashlytics call needs the opaque `1:<n>:ios:<hex>`, and a console URL carries only the bundle id, so the fetcher spent a Management API round trip resolving it on every run. `GoogleService-Info*.plist` and `google-services.json` name both ids; the script reads every match (a repo with several targets has several plists, and they do not all point at one project), skips build outputs, and emits entries shaped for `prefs.global.firebase.accounts[].apps[]`. The fetcher prefers that when present and falls through to the API when absent, so an install that never ran discovery behaves exactly as before.
 
-- **An encoding-regression gate.** `smoke-keychain.sh` stored a short ASCII word, which is exactly the value class that never reproduced the bug. It now round-trips a multi-line service-account JSON (and asserts it still *parses*, not merely compares equal), a hex-looking string, embedded quotes and backslashes, non-ASCII, and leading/trailing spaces.
+- **An encoding-regression gate.** `smoke-keychain.sh` stored a short ASCII word, which is exactly the value class that never reproduced the bug. It now round-trips a multi-line service-account JSON (and asserts it still _parses_, not merely compares equal), a hex-looking string, embedded quotes and backslashes, non-ASCII, and leading/trailing spaces.
 
 - **A gate for the shipped-but-dead script.** `firebase-app-discovery.sh` was written, installed onto every machine by all three hosts, and invoked by nothing: its only mention sat inside a comment in another script. That is the declared-but-inert defect in its purest form - the docs describe a capability, the install carries the code, and nothing connects them. `smoke-consumer-smoke-surface.sh` now checks every shipped script for an actual invoker, and is deliberately picky about what counts: comment lines, JSON schema descriptions, CHANGELOG and ROADMAP entries all name a script without ever running it, and each of those, left in the corpus, made the check pass on the broken state while it was being built.
 

package/README.md

@@ -43,12 +43,12 @@ package. Check first, then pick the row that matches:
 node -v; npm -v; command -v node npm npx
 ```
 
-| What you see | What to do |
-|---|---|
-| nothing at all | Install Node >= 20.11: `brew install node`, or the LTS installer from nodejs.org |
-| `node` works, `npx` does not | `npm i -g @mmerterden/multi-agent-pipeline` then `multi-agent-pipeline install --claude` |
-| nvm is installed but the shell does not see it | `source ~/.nvm/nvm.sh && nvm use --lts`, or just open a new terminal |
-| npm is ancient (< 5.2, which predates npx) | `npm i -g npm@latest`, or use the global-install row above |
+| What you see                                   | What to do                                                                               |
+| ---------------------------------------------- | ---------------------------------------------------------------------------------------- |
+| nothing at all                                 | Install Node >= 20.11: `brew install node`, or the LTS installer from nodejs.org         |
+| `node` works, `npx` does not                   | `npm i -g @mmerterden/multi-agent-pipeline` then `multi-agent-pipeline install --claude` |
+| nvm is installed but the shell does not see it | `source ~/.nvm/nvm.sh && nvm use --lts`, or just open a new terminal                     |
+| npm is ancient (< 5.2, which predates npx)     | `npm i -g npm@latest`, or use the global-install row above                               |
 
 And the path that needs neither `npx` nor a global install - clone and run the
 installer directly:
@@ -116,9 +116,10 @@ The other half of the change is that the count is finally guarded.
 `smoke-phase-contract.sh` derives it from `pipeline/schemas/phases.json` and
 holds every other copy to it: the generator's output, the token budget, the
 state-schema bounds, the progress fractions in sample output, and the named
-thresholds that used to be literals scattered across scripts. The phase count
-appeared in 91 places across 40 files with nothing checking any of them, while
-the command count, the jq count and the persona count all had gates.
+thresholds, none of which is a literal in a script any more. A phase count is
+otherwise the kind of number that spreads across dozens of files with nothing
+checking any of them, the way the command count, the jq count and the persona
+count are each held by a gate.
 
 Reasoning, mapping and rejected alternatives:
 [ADR-0014](./docs/adr/0014-six-phase-consolidation.md).
@@ -175,6 +176,7 @@ The discipline behind all of this - bounded loops, evidence gates, token-budgete
 | 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     |
 
 Depth, autopilot and `--local` are the only knobs on the run itself; everything else is its own command. The full catalog is below.
+
 ### Pipeline depth: Full or Short
 
 Depth is the one question the run asks about its own shape. `/multi-agent` and `/multi-agent:local` ask it at Phase 0 Step 7.5 - after the issue is fetched and the task type is known, because that is what the recommendation is drawn from.
@@ -186,7 +188,6 @@ Short is right when you already know the fix and the file: a one-line guard, a c
 
 The widget follows the answer rather than predicting it: Phase 0 is the only tile drawn before you choose, and a Short run never draws an Analysis tile at all. Both autopilot entries skip the question and always run Full. `agent-state.json` records which one ran as `onlyDevelop`.
 
-
 ## Commands
 
 `/multi-agent` plus 56 sub-commands. `/multi-agent:help` renders the same catalog in your terminal, in your `outputLanguage`.
@@ -300,11 +301,37 @@ Two compliance skills install on every host and back the store gates: `apple-arc
 Everything above starts when you start it. Continuous mode is the same pipeline
 picking work up on its own, on ONE machine you choose, from repos you choose.
 
-| Command | What it does |
-| --- | --- |
-| `/multi-agent:autopilot-on` | Pick the repos this machine watches. Labelled GitHub issues and assigned + labelled Jira items then run in a worktree and stop at an open PR. Re-run to change the list |
-| `/multi-agent:autopilot-status` | What is running and at which phase, what is queued, what is waiting for an answer, the PRs of the last day, and the rolling spend |
-| `/multi-agent:autopilot-off` | Remove the schedule. Work already running finishes; the repo selection is kept |
+| Command                         | What it does                                                                                                                                                            |
+| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `/multi-agent:autopilot-on`     | Pick the repos this machine watches. Labelled GitHub issues and assigned + labelled Jira items then run in a worktree and stop at an open PR. Re-run to change the list |
+| `/multi-agent:autopilot-status` | What is running and at which phase, what is queued, what is waiting for an answer, the PRs of the last day, and the rolling spend                                       |
+| `/multi-agent:autopilot-off`    | Remove the schedule. Work already running finishes; the repo selection is kept                                                                                          |
+
+## Which model answers
+
+The ladder is `fable -> opus -> sonnet -> haiku`, and a run walks it on failure.
+Routing lets a policy pick the rung instead, per call site, and is off until you
+turn it on.
+
+| Command                     | What it does                                                                                                                                        |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `/multi-agent:route-on`     | Pick a strategy, a scope and the rules that say which rung a call lands on. Validated against `route-config.schema.json` before anything is written |
+| `/multi-agent:route-off`    | Disarm it. The rules are KEPT, so turning it back on does not re-ask for the same configuration                                                     |
+| `/multi-agent:route-status` | Whether it is armed, which rule applies where, which rung the last dispatches took, and what this run has cost                                      |
+| `/multi-agent:model`        | Turn the top rung on or off, and move the cost ledger's pricing with it in the same step                                                            |
+
+**The scope cannot be the whole session.** `scope` accepts `subagent`,
+`bulk-read` and `research`; there is no `host-session` value and that is a schema
+gate, not a convention. Owning the host's base URL would send every call you make
+through a third layer, including work that has nothing to do with this pipeline.
+
+**The honest limit, which `route-status` prints rather than hides.** A rung on a
+non-Anthropic provider is refused at dispatch. No call site sends a model
+request itself: the one that routes, `bulk-read.sh`, delegates to the `claude`
+CLI, which speaks that ladder and nothing else. Sending a read to a third-party
+provider would also put the file's full text outside the account that owns it,
+so it is a decision a user makes rather than a default. Routing chooses inside
+the ladder.
 
 **Nothing is on by default and nothing is added implicitly.** Installing the
 package writes no state and schedules nothing; `smoke-autopilot-default-off.sh`

package/README.tr.md

@@ -43,12 +43,12 @@ bak, sonra sana uyan satırı uygula:
 node -v; npm -v; command -v node npm npx
 ```
 
-| Gördüğün | Yapılacak |
-|---|---|
-| hiçbiri yok | Node >= 20.11 kur: `brew install node` ya da nodejs.org'dan LTS installer |
-| `node` çalışıyor, `npx` çalışmıyor | `npm i -g @mmerterden/multi-agent-pipeline` sonra `multi-agent-pipeline install --claude` |
-| nvm kurulu ama kabuk görmüyor | `source ~/.nvm/nvm.sh && nvm use --lts`, ya da yeni bir terminal aç |
-| npm çok eski (< 5.2, npx'ten önceki sürümler) | `npm i -g npm@latest`, ya da üstteki global kurulum satırı |
+| Gördüğün                                      | Yapılacak                                                                                 |
+| --------------------------------------------- | ----------------------------------------------------------------------------------------- |
+| hiçbiri yok                                   | Node >= 20.11 kur: `brew install node` ya da nodejs.org'dan LTS installer                 |
+| `node` çalışıyor, `npx` çalışmıyor            | `npm i -g @mmerterden/multi-agent-pipeline` sonra `multi-agent-pipeline install --claude` |
+| nvm kurulu ama kabuk görmüyor                 | `source ~/.nvm/nvm.sh && nvm use --lts`, ya da yeni bir terminal aç                       |
+| npm çok eski (< 5.2, npx'ten önceki sürümler) | `npm i -g npm@latest`, ya da üstteki global kurulum satırı                                |
 
 Ne `npx` ne de global kurulum isteyen yol - klonla ve installer'ı doğrudan çalıştır:
 
@@ -156,6 +156,7 @@ Bunun arkasındaki disiplin - sınırlı loop'lar, kanıt kapıları, token-büt
 | 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 |
 
 Koşunun kendisinde ayarlanabilen tek şey derinlik, autopilot ve `--local`; geri kalan her şey kendi komutu. Tam katalog aşağıda.
+
 ### Pipeline derinliği: Tam mı Kısa mı
 
 Derinlik, koşunun kendi şekli hakkında sorduğu tek soru. `/multi-agent` ve `/multi-agent:local` bunu Faz 0 Adım 7.5'te sorar - issue çekildikten ve görev tipi belirlendikten sonra, çünkü öneri onlardan çıkıyor.
@@ -167,7 +168,6 @@ Kısa'yı düzeltmeyi ve dosyayı zaten biliyorsan seç: tek satırlık bir guar
 
 Widget cevabı tahmin etmek yerine takip eder: sen seçmeden önce yalnızca Faz 0 karosu çizilir, Kısa koşu Analiz karosunu hiç çizmez. İki autopilot girişi de bu soruyu sormaz, her zaman Tam koşar. Hangisinin koştuğunu `agent-state.json` `onlyDevelop` alanında tutar.
 
-
 ## Komutlar
 
 `/multi-agent` ve 56 alt komut. `/multi-agent:help` aynı katalogu terminalde, `outputLanguage` ayarına göre gösterir.
@@ -282,11 +282,37 @@ Yukarıdaki her şey sen başlattığında başlar. Sürekli mod, aynı pipeline
 **senin seçtiğin tek makinede**, **senin seçtiğin repolardan** işi kendi başına
 alması.
 
-| Komut | Ne yapar |
-| --- | --- |
-| `/multi-agent:autopilot-on` | Bu makinenin izleyeceği repoları seçersin. Etiketli GitHub issue'ları ve sana atanmış + etiketli Jira maddeleri worktree'de koşar, açık PR'da durur. Listeyi değiştirmek için tekrar çalıştır |
-| `/multi-agent:autopilot-status` | Ne koşuyor hangi fazda, sırada ne var, ne cevap bekliyor, son bir günün PR'ları ve yuvarlanan harcama |
-| `/multi-agent:autopilot-off` | Zamanlamayı kaldırır. Koşan iş biter; repo seçimi saklanır |
+| Komut                           | Ne yapar                                                                                                                                                                                      |
+| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `/multi-agent:autopilot-on`     | Bu makinenin izleyeceği repoları seçersin. Etiketli GitHub issue'ları ve sana atanmış + etiketli Jira maddeleri worktree'de koşar, açık PR'da durur. Listeyi değiştirmek için tekrar çalıştır |
+| `/multi-agent:autopilot-status` | Ne koşuyor hangi fazda, sırada ne var, ne cevap bekliyor, son bir günün PR'ları ve yuvarlanan harcama                                                                                         |
+| `/multi-agent:autopilot-off`    | Zamanlamayı kaldırır. Koşan iş biter; repo seçimi saklanır                                                                                                                                    |
+
+## Hangi model cevaplıyor
+
+Merdiven `fable -> opus -> sonnet -> haiku`; koşu başarısızlıkta merdiveni iner.
+Yönlendirme basamağı çağrı yeri başına bir politikaya seçtirir ve sen açana
+kadar kapalıdır.
+
+| Komut                       | Ne yapar                                                                                                                                                        |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `/multi-agent:route-on`     | Strateji, kapsam ve hangi çağrının hangi basamağa düşeceğini söyleyen kuralları sorar. Hiçbir şey yazılmadan önce `route-config.schema.json`'a karşı doğrulanır |
+| `/multi-agent:route-off`    | Kapatır. Kurallar SAKLANIR, tekrar açıldığında aynı yapılandırma yeniden sorulmaz                                                                               |
+| `/multi-agent:route-status` | Açık mı, hangi kural nerede geçerli, son çağrılar hangi basamağa gitti, bu koşu ne tuttu                                                                        |
+| `/multi-agent:model`        | Üst basamağı açıp kapatır ve maliyet defterinin fiyatlamasını aynı adımda onunla taşır                                                                          |
+
+**Kapsam oturumun tamamı olamaz.** `scope` yalnız `subagent`, `bulk-read` ve
+`research` kabul eder; `host-session` diye bir değer yoktur ve bu bir teamül
+değil, şema kapısıdır. Host'un base URL'ini sahiplenmek, bu pipeline'la ilgisi
+olmayan işler dahil yaptığın her çağrıyı üçüncü bir katmandan geçirirdi.
+
+**Dürüst sınır, ve `route-status` bunu gizlemek yerine yazar.** Anthropic
+dışı bir sağlayıcıdaki basamak dağıtımda reddedilir. Hiçbir çağrı yeri model
+isteğini kendisi atmıyor: yönlendirilen tek yer olan `bulk-read.sh` işi `claude`
+CLI'ına devrediyor, o da yalnız bu merdiveni konuşuyor. Bir okumayı üçüncü bir
+sağlayıcıya göndermek ayrıca dosyanın tam metnini onu sahiplenen hesabın dışına
+çıkarırdı; bu yüzden varsayılan değil, kullanıcının verdiği bir karardır.
+Yönlendirme merdivenin içinde seçim yapar.
 
 **Varsayılan olarak hiçbir şey açık değil ve hiçbir repo kendiliğinden eklenmez.**
 Paketi kurmak ne durum yazar ne zamanlama kurar; bu bir gün değişirse

package/docs/ecosystem.md

@@ -212,10 +212,9 @@ that step's own contract).
 ### multi-agent-toolkit-mcp's tools, by category
 
 115 tools in 13 categories, counted from the server's own `tools/list` response
-at toolkit 3.13.0 rather than from a README. The table stood at 87 across 8
-categories for several releases because Code Intelligence and Wallet Passes
-shipped without anyone adding their rows, and nothing here was checked against
-the server - which is why the count now names its source.
+at toolkit 3.13.1 rather than from a README. Three families are defined in
+modules the main file only spreads in, so a count taken from the source reads
+low; the response is the only place the whole surface appears at once.
 
 The families can be narrowed per host: `MCP_TOOLKIT_CAPS` serves only the named
 ones, and unset serves all 115. A frontend repo that sets `web,code,context`

package/docs/facts.json

@@ -1,7 +1,7 @@
 {
   "$comment": "Generated by pipeline/scripts/gen-facts.mjs. Do not hand-edit: the site reads this, and a number edited here instead of at its source is the drift this file removes.",
   "generatedAt": "2026-09-21",
-  "version": "19.1.3",
+  "version": "19.1.4",
   "phaseSchema": 2,
   "phases": [
     {
@@ -56,6 +56,6 @@
     "research": 2,
     "media": 1
   },
-  "pluginSkillCount": 238,
-  "toolkitVersion": "3.13.0"
+  "pluginSkillCount": 239,
+  "toolkitVersion": "3.13.1"
 }

package/install/_common.mjs

@@ -485,11 +485,11 @@ export function pruneOrphanSkillFiles(skillsDir) {
  *
  * `.skills-index.json` is what `match-skills.mjs` reads when
  * `prefs.global.dynamicSkillLoading` is on; `skills-index.md` is the human-readable
- * twin. Both used to be copied ONLY under `--index-only`, while the preferences
- * schema stated that a full install always ships the index. It did not, so turning
- * the pref on after a normal install produced `cannot read index` and a silent
- * fall back to eager loading. One helper, called from every target, so the two
- * install modes cannot disagree about it again.
+ * twin. Both ship on a full install, not only under `--index-only`: the
+ * preferences schema states that a full install always carries the index, and an
+ * install that skips it makes turning the pref on afterwards produce `cannot read
+ * index` and a silent fall back to eager loading. One helper, called from every
+ * target, so the two install modes cannot disagree about it.
  *
  * @param {string} pipelineSrc - the repo's `pipeline/` directory
  * @param {string} skillsDest - the host's skills directory

package/install/_mcp-register.mjs

@@ -152,7 +152,7 @@ function saysAlreadyExists(text) {
  * automatically a failure, and a zero exit is not automatically a fresh write - which
  * is why the "already exists" test runs on both paths. Reporting an existing server as
  * "skipped MCP registration (Command failed)" would send the user to fix something that
- * is already correct, and that is exactly what the first version of this did.
+ * is already correct.
  *
  * An existing entry under the same name is removed and re-added so its spec follows
  * the installed version (the entry is installer-owned; the reason is at the remove

package/install/_plugin-skills.mjs

@@ -4,9 +4,8 @@
  * Claude Code loads `{owner}/multi-agent-plugins` natively, so it gets all of a
  * stack plugin's skills. The other two hosts do not:
  *
- * - **Copilot CLI** has no plugin loader at all. The contract used to say it kept
- *   standalone `figma-*` copies as a "frozen fallback", but `install/copilot.mjs`
- *   pruned exactly those directories, so in practice Copilot had **zero**
+ * - **Copilot CLI** has no plugin loader at all. `install/copilot.mjs` prunes the
+ *   standalone `figma-*` directories, so Copilot carries **zero**
  *   plugin-authored skills - `create-screen`, `figma-validate`, `figma-review`,
  *   `component`, `state` and `navigation` were all absent. A component task on
  *   Copilot therefore had nothing to dispatch to.
@@ -221,7 +220,7 @@ export function installAuthoredPluginSkills(opts) {
               .map((e) => ({ name: e.name, from: join(groupDir, e.name) }));
 
       for (const { name, from } of entries) {
-        // A plugin skill whose name a PIPELINE skill already owns used to be dropped.
+        // A plugin skill whose name a PIPELINE skill already owns is KEPT.
         // That is not a duplicate: the pipeline's `architecture` is a generic ADR
         // framework while the iOS plugin's is that stack's structural rules, and the
         // same holds for `backlog`. Claude Code reaches both because its loader

package/install/copilot.mjs

@@ -86,11 +86,11 @@ export function installCopilot(ctx) {
 /**
  * `$HOME/.claude/...` rewrites applied to skill files copied into the Copilot tree.
  *
- * Copilot's skills used to be copied byte-for-byte, so a Copilot-only install
- * shipped 15 references to `~/.claude/scripts` and `~/.claude/lib` - trees that
- * install never creates. Every one of those was a dangling path: the skill told the
- * agent to run a script at a location that does not exist on that machine. Codex has
- * had this rewrite since its installer was written; Copilot simply never got it.
+ * Copied byte-for-byte, a Copilot-only install would carry every `~/.claude/scripts`
+ * and `~/.claude/lib` reference in the skill text - trees that install never creates
+ * on that host. Each one is a dangling path: the skill tells the agent to run a
+ * script at a location that does not exist on that machine. Codex's installer
+ * applies the same rewrite for the same reason.
  *
  * Only the trees Copilot actually OWNS are rewritten:
  *