@azure-id/orc 0.56.1 → 1.0.0

package/README-id.md

@@ -7,13 +7,13 @@
 *Terima permintaan → pahami → rencanakan → beri nilai → kerjakan paralel → periksa → uji → kirim.*
 
 ![npm](https://img.shields.io/npm/v/%40azure-id%2Forc?style=for-the-badge&color=cb3837&logo=npm)
-![Version](https://img.shields.io/badge/version-0.56.0-blue.svg?style=for-the-badge)
+![Version](https://img.shields.io/badge/version-1.0.0-blue.svg?style=for-the-badge)
 ![License](https://img.shields.io/badge/license-MIT-green.svg?style=for-the-badge)
 ![Node](https://img.shields.io/badge/node-%3E%3D18-brightgreen.svg?style=for-the-badge)
 ![Claude Code](https://img.shields.io/badge/Claude_Code-Skills-purple.svg?style=for-the-badge)
 ![Dependencies](https://img.shields.io/badge/dependencies-zero-lightgrey.svg?style=for-the-badge)
 
-**Versi terbaru: v0.56.1** · diperbarui 28-08-2026 · [daftar perubahan lengkap](CHANGELOG.md)
+**Versi terbaru: v1.0.0** · diperbarui 30-08-2026 · [daftar perubahan lengkap](CHANGELOG.md)
 
 **Ada di npm: [`@azure-id/orc`](https://www.npmjs.com/package/@azure-id/orc)** — `npm i -g @azure-id/orc`
 
@@ -619,113 +619,55 @@ Bacalah sebagai catatan putaran itu, bukan sebagai audit terkini:
 **Riwayat lengkap: [CHANGELOG.md](CHANGELOG.md)** — atau `orc changelog`, yang
 hanya mencetak yang lebih baru dari versi yang Anda punya.
 
-### v0.56.1 - pekerja yang hidup tapi tidak mengerjakan apa pun _(28-08-2026)_
+### v1.0.0 - konfigurasi, fase, dan panggilan berhenti jadi prosa _(30-08-2026)_
 
-**Masih memakai paket `orc` yang tanpa awalan?** Lakukan ini sekali dulu -
+**Masih memakai paket `orc` yang tanpa awalan?** Lakukan ini sekali dulu —
 `orc upgrade` Anda adalah versi sebelum v0.56.0 dan tidak bisa memasang dirinya
-sendiri:
-
-- **Langkah 1 - lepaskan perintahnya dari paket lama:** `npm uninstall -g orc`
-- **Langkah 2 - pasang paket yang sekarang:** `npm i -g @azure-id/orc`
-- **Langkah 3 - terapkan lagi ke proyek Anda:** `orc update`
-
-**Jangan pakai `npm i -g -f`.** Rinciannya ada di v0.56.0 di bawah.
-
-**Pengiriman ke opencode yang diam di tengah jalan dulu menghabiskan seluruh
-batas waktu lima belas menit lalu melapor `timeout`.** Kata itu bercerita
-tentang kesabaran ORC, dan terbaca sebagai batas waktu yang perlu dinaikkan.
-Padahal yang tertinggal adalah sebuah POSISI yang perlu dilanjutkan seseorang.
-
-- **`extra_stall_s` (bawaan 180, `0` mematikannya)** menghentikan pekerja luar
-  yang tidak menghasilkan apa pun selama itu. Direset oleh kemajuan yang
-  terlihat - aliran keluaran pekerja, keluaran kesalahannya, atau berkas yang
-  dideklarasikan berubah di disk - jadi ia tidak pernah memotong pekerja yang
-  sekadar lambat. Hanya untuk mesin `cli`.
-- **`stalled` adalah jenis kegagalannya sendiri dan boleh diulang**, jadi
-  `orc extra reconcile` membaca posisinya dan `extra_resume` melanjutkan dari
-  apa yang sudah ada di disk, bukan mengulang dari nol. Itulah cara ORC sendiri
-  mengetik `continue`. Sengaja tidak ada dorongan lewat stdin: `opencode run`
-  bukan sesi percakapan, jadi ketikan yang tak dibaca siapa pun hanyalah
-  perbaikan palsu.
-- **Setiap balasan mesin `cli` membawa `timeline`** - bita pertama, kemajuan
-  terakhir, jeda diam terpanjang, dan kedua batas waktunya - baik saat berhasil
-  maupun gagal.
-- **`orc extra health <profil> [--model <id>]`** menjawab "apakah model ini suka
-  diam", lewat pengawas yang SAMA dengan yang dipakai pengiriman sungguhan.
-  Model yang terdaftar belum tentu jalan, dan model yang jalan belum tentu
-  selesai.
-- **`extra_fallback_agent` (bawaan `band`)** menentukan siapa yang mengambil
-  alih tugasnya. `ask` berhenti dan menyodorkan pilihannya kepada Anda; nama
-  agen apa pun yang terpasang bisa dikunci. Saat `ask`, lane-nya tidak memilih
-  sendiri. Ia mengubah siapa, bukan skor, daftar berkas, atau syarat
-  penerimaannya. Tidak berlaku di `/orc-quick`.
-
-### v0.56.0 - satu penggantian nama memindahkan perintahnya, dan tak seorang pun bisa meraih perbaikannya _(27-08-2026)_
-
-**Paketnya pindah dari `orc` tanpa awalan ke `@azure-id/orc`, dan semua jalur
-pemutakhiran di lapangan mati bersamaan.** Kedua nama itu mendaftarkan perintah
-`orc` yang sama, dan npm tidak mau menautkannya untuk paket baru selama paket
-lama masih memilikinya - jadi tarball, spesifikasi `github:`, dan registry
-semuanya gagal dengan `EEXIST` yang sama pada berkas perintahnya. Itu bentrokan
-BERKAS, bukan masalah sumber, dan itulah sebabnya berganti sumber tidak pernah
-menolong.
-
-- **`orc upgrade` mengusir paket lama SEBELUM mencoba sumber mana pun.**
-  Diumumkan, tidak pernah diam-diam. Pengenalannya lewat KEPEMILIKAN - paket
-  yang tidak mendaftarkan perintah `orc` tidak pernah disentuh.
-- **Registry npm dicoba lebih dulu**, lalu tarball, lalu spesifikasi `github:`.
-- **`--force` tetap ada untuk satu kasus yang cocok saja** - berkas perintah
-  yatim yang tidak dimiliki paket mana pun.
-- **`orc doctor` melaporkan `legacy-global-package` dengan namanya.** Sengaja
-  tidak bisa diperbaiki `--fix`: jangkauan `--fix` hanya `.claude/` proyek ini.
-
-### v0.55.1 — ORC sudah ada di npm _(27-08-2026)_
-
-**ORC diterbitkan dengan nama [`@azure-id/orc`](https://www.npmjs.com/package/@azure-id/orc).**
-Pemasangan lewat GitHub tetap jalan, dan isi paketnya tidak berubah sama sekali —
-ini hanya soal cara memasangnya sekarang punya nama.
-
-- **`npm i -g @azure-id/orc`** untuk memasang, dan
-  **`npm i -g @azure-id/orc@latest`** untuk memperbarui. `orc upgrade` sudah
-  melakukan keduanya sejak dulu dan tetap begitu.
-- **Pemasangan dari GitHub sekarang jadi cadangan**, bukan cara utama — tetap ada
-  di bagian "Cara mulai", dilipat, untuk fork atau kalau Anda mengunci sebuah
-  branch.
-
-### v0.51.0 — alat yang sudah Anda punya, dan koneksi yang membuktikan dirinya _(22-08-2026)_
-
-**Koneksi `orc extra`.** Dua alat coding yang bisa diberi pekerjaan oleh ORC
-adalah **program di komputer Anda sendiri**, bukan situs — jadi sekarang keduanya
-jadi penyedia kelas satu, punya kotak hubungkan masing-masing, dan daftar model
-yang dibangun dari apa yang benar-benar bisa dijangkau akun Anda.
-
-- **Program bisa saja belum terpasang, dan panelnya mengatakan itu lebih dulu** —
-  empat keadaan, dihitung setiap kali, tidak pernah diingat. Alat yang belum
-  terpasang tidak diberi tombol yang tidak mungkin berhasil, dan `orc extra add`
-  menolak sambil menyebutkan perintah pemasangannya.
-- **ORC membuka terminal Anda sendiri dan menjalankan pemasangannya di sana.**
-  Bukan pekerjaan tersembunyi di latar — di dalamnya, permintaan hak
-  administrator, kegagalan izin, unduhan 80 MB, dan tunggu empat puluh detik
-  semuanya terlihat sama: *tidak terjadi apa-apa*. Perintahnya tampil sebelum
-  tombolnya, jendelanya milik Anda, dan **ORC tidak pernah meminta hak
-  administrator**. Tidak ada terminal yang bisa dibuka? Anda tetap dapat
-  perintahnya untuk disalin.
-- **Uji koneksi sekarang bertingkat**: programnya ada · cukup baru · sudah masuk
-  akun · model apa yang bisa dijangkau akun ini · dan, hanya kalau Anda minta,
-  **apakah pesan sungguhan benar-benar dijawab** — lengkap dengan waktu tempuh,
-  jawabannya, dan empat jenis hitungan token yang tidak pernah dicampur.
-- **Model yang terdaftar bukan berarti model yang bekerja.**
-  `orc extra models <nama> --test <id>` adalah satu-satunya cara membedakannya.
-- **Kedua alat lokal itu tidak memberi tahu model mana yang menjawab**, jadi ORC
-  menuliskan kalimat itu, bukan membiarkan kolom kosong.
-- **`extra_enabled` tidak bisa dinyalakan sebelum ada yang menjawab** — dulu ia
-  akan terbaca NYALA padahal artinya MATI.
-
-Sebelumnya: **v0.50.0 — pekerjaan yang berjalan di tempat lain** (`orc extra`),
-**v0.49.1 — dewan penilai, dan `--json` yang berhenti membuang isinya**,
-**v0.49.0 — dokumen itu folder, dan berkasnya hasil rakitan** (`/orc-doc`), dan
-**v0.48.1 — satu berkas untuk satu hal, dan dokumen yang bisa diselesaikan**.
-[Baca semuanya di daftar perubahan](CHANGELOG.md).
+sendiri. Rincian lengkapnya ada di blok PERHATIAN di bagian atas berkas ini.
+
+- **Langkah 1 — lepaskan perintahnya dari paket lama:** `npm uninstall -g orc`
+- **Langkah 2 — pasang paket yang sekarang:** `npm i -g @azure-id/orc`
+- **Langkah 3 — terapkan lagi ke proyek Anda:** `orc update`
+
+**Tidak ada pengaturan yang berubah artinya, dan tidak ada perintah yang diganti
+namanya.** Tiga hal benar-benar mengubah perilaku; sisanya adalah ORC yang
+akhirnya membaca muatannya sendiri dengan cara yang selama ini ia ajarkan kepada
+Anda untuk membaca kode Anda.
+
+- **Tabel skor ke model berakhir di `opus-5-low [65,90)` · `opus-5-med
+  [90,100]`.** Dua dari enam pita kini ingin sesi utama Opus 5, dari sebelumnya
+  satu dari delapan.
+- **Pekerja luar yang macet dua kali dalam satu run akan menepi** untuk sisa run
+  itu. Dua jam, tidak pernah digabung; ia tidak menulis pengukuran baru dan tidak
+  pernah menulis konfigurasi Anda; sebuah promote adalah tanda batas, bukan
+  membisukan, dan perlu alasan.
+- **`orc diy init` kini berbawaan `opus-5-high`.** Bawaan yang lama diam-diam
+  meruntuhkan sepertiga atas tangga Anda ke satu agen sebelum Anda memilih
+  apa pun.
+
+Bagian strukturalnya - **konfigurasi, fase, dan panggilan berhenti jadi prosa**:
+
+- **`orc lane config <lane>`** menjawab konfigurasi sebuah lane sudah menjadi
+  apa, dengan setiap bayangan sudah dikalimatkan. Sebuah lane tidak pernah lagi
+  menggabungkan berkas konfigurasi sendiri, dan **peringkat di bawah peringkat
+  yang sudah menjawab tidak dibaca sama sekali**.
+- **`orc lane phases <lane>`** dan **`orc lane calls --all`** melakukan hal yang
+  sama untuk pustaka fase bersama dan katalog panggilan CLI - masing-masing satu
+  salinan kanonis, dari sebelumnya 14-59 pengulangan per panggilan.
+- **`orc ui` menampilkan semuanya**: tangga peringkat yang menunjukkan
+  pengaturan mana yang MENJAWAB, lane mana yang membaca tiap kunci, panel Lane
+  baru, dan baris penurunan di Extra ▸ Recovery beserta tombol Promote.
+  `orc doctor` mendapat `lane-keys-drifted`.
+
+**Ini tidak membuat muatannya lebih kecil** - 208 berkas menjadi 291, 26.507
+baris menjadi 33.204. Sebagian besar gelombang terukur sebagai kebenaran, bukan
+penghapusan duplikasi. Yang berubah adalah kini ada satu tempat untuk memperbaiki
+masing-masing hal ini, dan ada lint yang gagal saat sebuah salinan tumbuh
+kembali. Dua penghapusan yang direncanakan **diukur lalu ditolak**, dan flake
+yang membuat empat gelombang gagal akhirnya didiagnosis - dengan catatan jujur
+bahwa tiga run hijau adalah gerbangnya, bukan buktinya.
+
+**Entri lengkap: [CHANGELOG.md](CHANGELOG.md).**
 
 ---
 

package/README.md

@@ -7,14 +7,14 @@
 *Intake → analyze → plan → score → parallel subagents → review → verify → ship.*
 
 ![npm](https://img.shields.io/npm/v/%40azure-id%2Forc?style=for-the-badge&color=cb3837&logo=npm)
-![Version](https://img.shields.io/badge/version-0.56.0-blue.svg?style=for-the-badge)
+![Version](https://img.shields.io/badge/version-1.0.0-blue.svg?style=for-the-badge)
 ![License](https://img.shields.io/badge/license-MIT-green.svg?style=for-the-badge)
 ![Node](https://img.shields.io/badge/node-%3E%3D18-brightgreen.svg?style=for-the-badge)
 ![Claude Code](https://img.shields.io/badge/Claude_Code-Skills-purple.svg?style=for-the-badge)
 ![Dependencies](https://img.shields.io/badge/dependencies-zero-lightgrey.svg?style=for-the-badge)
 ![GitHub stars](https://img.shields.io/github/stars/azure-id/orc?style=for-the-badge&color=yellow)
 
-**Latest: v0.56.1** · updated 2026-08-28 · [full changelog](CHANGELOG.md)
+**Latest: v1.0.0** · updated 2026-08-30 · [full changelog](CHANGELOG.md)
 
 **On npm: [`@azure-id/orc`](https://www.npmjs.com/package/@azure-id/orc)** — `npm i -g @azure-id/orc`
 
@@ -574,137 +574,49 @@ a current audit: [EVAL-REPORT.md](EVAL-REPORT.md).
 **Full history: [CHANGELOG.md](CHANGELOG.md)** — or `orc changelog`, which prints
 only what is newer than the version you have.
 
-### v0.56.1 - a worker that is alive and doing nothing _(2026-08-28)_
-
-**Still on the unscoped `orc` package?** Do this once before anything else -
-your `orc upgrade` is the pre-v0.56.0 one and it cannot install itself:
-
-- **Step 1 - release the command from the old package:** `npm uninstall -g orc`
-- **Step 2 - install the current package:** `npm i -g @azure-id/orc`
-- **Step 3 - re-apply it to your project:** `orc update`
-
-**Do not use `npm i -g -f`.** Full detail in v0.56.0 below.
-
-**An opencode dispatch that goes quiet mid-task used to burn the whole
-fifteen-minute wall clock and then report `timeout`.** That word is a statement
-about ORC's patience and reads as a budget somebody should raise. It was a
-POSITION somebody should resume from.
-
-- **`extra_stall_s` (default 180, `0` disables)** stops a foreign worker that
-  has produced NOTHING for that long. Reset by observable progress - the
-  worker's stream, its stderr, or a declared file that changed on disk - so it
-  never fires on a worker that is merely slow. Engine `cli` only.
-- **`stalled` is its own failure class and it is RETRYABLE**, so
-  `orc extra reconcile` reads the position and `extra_resume` continues from
-  what is on disk instead of starting over. That is ORC's spelling of typing
-  `continue`. There is deliberately no stdin nudge: `opencode run` is not an
-  interactive session, so a keystroke nobody reads would be a fake fix.
-- **Every engine-`cli` return carries a `timeline`** - first byte, last
-  progress, longest quiet gap, both budgets - on success as well as failure.
-- **`orc extra health <profile> [--model <id>]`** answers "does this model
-  stall", through the SAME watchdog a dispatch uses. A listed model is not a
-  working model, and a working model is not a model that finishes.
-- **`extra_fallback_agent` (default `band`)** decides who picks the task up.
-  `ask` STOPS and puts the menu to you; any installed agent name pins one. Under
-  `ask` the lane does not choose. It changes WHO, never the score, the declared
-  files or the acceptance criteria. INERT in `/orc-quick`.
-
-### v0.56.0 - a rename moved the command, and nobody could reach the fix _(2026-08-27)_
-
-**READ THIS FIRST IF YOUR `orc upgrade` IS FAILING.** On a version before
-v0.56.0, this release cannot install itself - your `orc upgrade` is the OLD one.
-Run these three lines once, by hand:
-
-- **Step 1 - release the command from the old package:** `npm uninstall -g orc`
-- **Step 2 - install the current package:** `npm i -g @azure-id/orc`
-- **Step 3 - re-apply it to your project:** `orc update` (add `--global` to also
-  refresh `~/.claude`)
-
-Then `orc version` should print 0.56.0 or newer. Your `.claude/` and your
-`orc.config.yaml` are untouched. **Do not use `npm i -g -f`.**
-
-**The package moved from the unscoped `orc` to `@azure-id/orc`, and every
-upgrade path in the field died at once.** Both names declare the same `orc` bin,
-and npm will not link it for the new package while the old one owns it - so the
-tarball, the `github:` spec and the registry all failed with the same `EEXIST`
-on the command file. It is a FILE conflict, not a source problem, which is why
-changing sources never helped and `npm i -g -f` was the only thing that worked.
-
-- **`orc upgrade` evicts the legacy package BEFORE trying any source**, because
-  the collision fails every source identically. Announced, never silent.
-  Detection is by OWNERSHIP - a package that does not declare the `orc` bin is
-  never touched.
-- **The npm registry is tried first**, then the tarball, then the `github:` spec.
-  `freshCliPath()` now resolves the SCOPED directory, so step 2 stops re-applying
-  the templates step 1 just superseded.
-- **`--force` is kept for the one case it fits** - an orphaned command file no
-  package owns - and never for an unrelated `EEXIST`.
-- **`orc doctor` reports `legacy-global-package` by name.** Not `--fix`-able on
-  purpose: `--fix` is scoped to this project's `.claude/`.
-- **A CAUTION at the top of this README** carries the one-time manual fix, since
-  anyone still on the old package does not have this code yet.
-
-### v0.55.2 - a gate that is never probed is a gate that is always off _(2026-08-27)_
-
-**`/orc-quick` and `/orc-fast` documented the foreign-worker option and then
-never went and looked for it.** Both carried the whole `orc extra` slot contract
-but neither preflight ever ran the probe that answers whether a position is
-held, so an armed `extra_enabled` plus a slot row still offered only the shipped
-Claude executors.
-
-- **orc-quick Q0 gains one PROBE** - `orc extra resolve --slot quick-executor
-  --json`, the single exception to "read no other key" - so the menu can render
-  line 3. Still an option: never a default, never sticky.
-- **orc-fast F0 gains gate `d`** - `orc extra resolve --slot fast-executor
-  --json` - and prints the P0 `extra:` line where the prose always said it
-  would, naming the agent it displaces.
-- **`/orc-doc` was never affected**: `orc doc next` resolves its targets in the
-  CLI, which is the shape the other two now borrow.
-
-### v0.55.1 — ORC is on npm _(2026-08-27)_
-
-**ORC is published as [`@azure-id/orc`](https://www.npmjs.com/package/@azure-id/orc).**
-The GitHub tarball still works and nothing about the payload changed — this is
-the install path getting a name.
-
-- **`npm i -g @azure-id/orc`** is the install, and
-  **`npm i -g @azure-id/orc@latest`** is the update. `orc upgrade` already did
-  both steps for you and continues to; `--from @azure-id/orc` names npm
-  explicitly.
-- **The GitHub tarball is now the fallback**, not the headline — it is kept in
-  the Quick start behind a fold for forks and for anyone pinning a branch.
-
-### v0.55.0 — a score is what a band needs, and four lanes do not have one _(2026-08-26)_
-
-**`/orc-quick`, `/orc-fast`, `/orc-doc` and `/orc-wiki` pin an agent to a
-position instead of scoring a task. `orc extra` routed them by reading that
-agent's score band — arithmetic on a number nobody chose. It was wrong twice and
-dead once.**
-
-- **`orc extra role` holds six POSITIONS** — `quick-executor` · `fast-executor` ·
-  `doc-writer` · `doc-checker` · `wiki-scanner-deep` · `wiki-scanner-light`. One
-  connection and one model each, and a row's presence is the arming. All six are
-  always listed: an unrouted one keeps its slot and reads as the Claude agent it
-  falls back to.
-- **`orc extra resolve --slot` never touches a band**, and the Claude answer it
-  carries is a pinned NAME rather than an interval. Nine hold-backs, each named.
-- **Precedence, one sentence:** extra decides *whether* a Claude agent runs at
-  all; `opus5_only` and the score tables only decide *which* one runs where extra
-  did not take it. Under a taken position `opus5_only` is not consulted — and it
-  stays fully live for every position with no row.
-- **The bridge accepts a slot** (`band` becomes `slot:<slot>`, so cost reporting
-  splits per position for free) with **zero new engines, zero new dispatch paths
-  and zero new agents**. A doc checker now resolves its OWN position, `/orc-wiki`
-  can route at all, and `/orc-quick` gets a THIRD OPTION on its menu — never a
-  default, never sticky, re-asked after a failure.
-- **A second ladder in `orc ui ▸ Extra ▸ Routing`**, and **zero config keys
-  added**.
-
-Before that: **v0.54.0 — a failed dispatch is a POSITION, not a blank page**,
-**v0.53.4 — the reload that dropped its own token**, **v0.53.3 — the key it never
-sent**, **v0.53.2 — the cost that was paid and never written down**, and
-**v0.53.1 — "up to date" now names what it checked**.
-[Read them in the changelog](CHANGELOG.md).
+### v1.0.0 - config, phases and calls stop being prose _(2026-08-30)_
+
+**Still on the unscoped `orc` package?** Do this once first — your `orc upgrade`
+is the pre-v0.56.0 one and cannot install itself. Full detail in the CAUTION at
+the top of this file.
+
+- **Step 1 — release the command from the old package:** `npm uninstall -g orc`
+- **Step 2 — install the current package:** `npm i -g @azure-id/orc`
+- **Step 3 — re-apply it to your project:** `orc update`
+
+**Nothing you configure changes meaning, and no command you run is renamed.**
+Three things actually change behaviour; everything else is ORC finally reading
+its own payload the way it has been telling you to read yours.
+
+- **The score to model table ends `opus-5-low [65,90)` · `opus-5-med [90,100]`.**
+  Two bands in six now want an Opus 5 main session where one in eight did.
+- **A foreign worker that stalls twice in one run steps aside** for the rest of
+  that run. Two clocks, never merged; it writes no new measurement and never
+  writes your config; a promote is a watermark, not a mute, and needs a reason.
+- **`orc diy init` defaults to `opus-5-high`.** The old default silently
+  collapsed the top third of your ladder onto one agent before you chose
+  anything.
+
+The structural half - **config, phases and calls stop being prose**:
+
+- **`orc lane config <lane>`** answers what a lane's config resolved to, with
+  every shadow already worded. A lane never merges the config file itself again,
+  and **a rank below a resolved rank is not read at all**.
+- **`orc lane phases <lane>`** and **`orc lane calls --all`** do the same for the
+  shared phase library and the CLI call catalogue - one canonical copy each,
+  where there were 14-59 restatements per call.
+- **`orc ui` renders all of it**: a rank ladder showing which setting ANSWERED,
+  the lanes that read each key, a Lanes panel, and Extra ▸ Recovery's demotion
+  row with Promote. `orc doctor` gains `lane-keys-drifted`.
+
+**It did not make the payload smaller** - 208 files became 291, 26,507 lines
+became 33,204. Most waves measured as correctness, not deduplication. What
+changed is that there is now one place to fix each of these, and a lint that
+fails when a copy grows back. Two planned deletions were **measured and
+refused**, and the test suite's four-wave flake was diagnosed - with the honest
+caveat that three green runs are the gate and not proof.
+
+**Full entry: [CHANGELOG.md](CHANGELOG.md).**
 
 ---
 

package/bin/build-agents.js

@@ -22,24 +22,31 @@ const TEMPLATE = path.join(ROOT, "agents-src", "executor.template.md");
 const OUT_DIR = path.join(ROOT, "templates", "agents");
 
 // Score→model bands mirror templates/agents/MODEL-MAPPING.md and the single
-// 8-band score→model table in skills/orc/config.md (documented drift — change
+// score→model table in skills/orc/config.md (documented drift — change
 // together). `effort: null` = a model with NO effort ladder (haiku): the
 // generator omits the `effort:` frontmatter line entirely.
+//
+// v1.0.0 W4 — the table is SIX bands, not eight, and the `opus5_only` ladder is
+// TWO, not three. Four of these agents are named by NO default row:
+// names them, and they ship anyway (D14). They stay reachable through
+// `rubric_bands_override`, `orc diy` `fixed_executor` and `extra_fallback_agent`,
+// and deleting a generated file that no row happens to name today would be a
+// rename-shaped migration for what is only a table change. Their `band` string
+// says so rather than naming a range that no longer exists — a band label that
+// lies is worse than one that admits it is unreachable by default.
 const VARIANTS = [
-  { name: "orc-executor-opus-5-high",    model: "claude-opus-5",    effort: "high",   band: "highest-complexity [90,100]" },
-  { name: "orc-executor-opus-4-8-high",  model: "claude-opus-4-8",  effort: "high",   band: "very-high-complexity [80,90)" },
-  { name: "orc-executor-opus-4-7-high",  model: "claude-opus-4-7",  effort: "high",   band: "high-complexity [70,80)" },
-  { name: "orc-executor-opus-4-7-med",   model: "claude-opus-4-7",  effort: "medium", band: "upper-mid-complexity [65,70)" },
+  { name: "orc-executor-opus-5-med",     model: "claude-opus-5",     effort: "medium", band: "highest-complexity [90,100]" },
+  { name: "orc-executor-opus-5-low",     model: "claude-opus-5",     effort: "low",    band: "upper-complexity [65,90)" },
   { name: "orc-executor-sonnet-5-high",  model: "claude-sonnet-5",  effort: "high",   band: "mid-complexity [55,65)" },
   { name: "orc-executor-sonnet-4-6-high", model: "claude-sonnet-4-6", effort: "high",  band: "low-mid-complexity [40,55)" },
   { name: "orc-executor-sonnet-4-6-med", model: "claude-sonnet-4-6", effort: "medium", band: "low-complexity [30,40)" },
   { name: "orc-executor-haiku-4-5",      model: "claude-haiku-4-5",  effort: null,     band: "lowest-complexity [0,30)" },
-  // v0.35.0, widened v0.36.0 — the `opus5_only` ladder ONLY (default off). Same model,
-  // effort as the cost dial: [0,40) low · [40,80) medium · [80,100] high (the
-  // existing opus-5-high covers the top band in BOTH tables). These two are
-  // never dispatched by the default 8-band table.
-  { name: "orc-executor-opus-5-med",     model: "claude-opus-5",     effort: "medium", band: "opus5-only mid [40,80)" },
-  { name: "orc-executor-opus-5-low",     model: "claude-opus-5",     effort: "low",    band: "opus5-only low [0,40)" },
+  // NAMED BY NO BAND since v1.0.0 W4 (D14) — kept on disk, dispatched only when a
+  // user names one explicitly.
+  { name: "orc-executor-opus-5-high",    model: "claude-opus-5",    effort: "high",   band: "no default band — reachable via rubric_bands_override, orc diy fixed_executor, or extra_fallback_agent" },
+  { name: "orc-executor-opus-4-8-high",  model: "claude-opus-4-8",  effort: "high",   band: "no default band — reachable via rubric_bands_override, orc diy fixed_executor, or extra_fallback_agent" },
+  { name: "orc-executor-opus-4-7-high",  model: "claude-opus-4-7",  effort: "high",   band: "no default band — reachable via rubric_bands_override, orc diy fixed_executor, or extra_fallback_agent" },
+  { name: "orc-executor-opus-4-7-med",   model: "claude-opus-4-7",  effort: "medium", band: "no default band — reachable via rubric_bands_override, orc diy fixed_executor, or extra_fallback_agent" },
 ];
 
 function render(template, v) {