@azure-id/orc 2.0.2 → 2.1.0

package/CHANGELOG.md

@@ -10,6 +10,407 @@ Format: `### v<version> — <title> _(<date>)_`.
 
 ---
 
+### v2.1.0 — the review counts, the score table moves up, and old logs can go _(2026-10-02)_
+
+**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`
+
+**Do not use `npm i -g -f`.** Full detail in v0.56.0 below.
+
+This release has eight parts. It moves the score table up to newer models, it
+makes Review quality count the reviews that really ran, and it adds a way to
+delete old logs.
+
+**1. Opus 4.x leaves the roles that do not write code**
+
+- The deep wiki scanner and the CLAUDE.md writer now use **Opus 5.5 low**. They
+  used Opus 4.8 high. An agent's model change is always a rename, so the files
+  change name:
+  - `orc-wiki-scanner-opus-4-8-high` → `orc-wiki-scanner-opus-5-low`
+  - `orc-claude-writer-opus-4-8-high` → `orc-claude-writer-opus-5-low`
+- The `opus5_only` twins of these two roles are **deleted**
+  (`orc-wiki-scanner-opus-5-med`, `orc-claude-writer-opus-5-med`). The defaults
+  are already Opus 5.5 low, so `opus5_only` has nothing to change. Under
+  `opus5_only`, a wiki scan and a CLAUDE.md write are now low effort, not medium
+  (cheaper).
+- The coding lanes and the `/orc` main-session baseline do not change. Opus 4.6
+  is used nowhere.
+
+**2. Sonnet 5 runs on `claude-sonnet-5-5`**
+
+- Every Sonnet 5 agent now has `model: claude-sonnet-5-5`. The agent names keep
+  `-sonnet-5-`, as Opus did in v1.9.2. A config that names `claude-sonnet-5` is
+  still valid.
+
+**3. A new score table with five bands**
+
+| Score | Agent | Model · effort |
+|---|---|---|
+| `[0,21)` | `orc-executor-sonnet-5-low` (new) | Sonnet 5 · low |
+| `[21,31)` | `orc-executor-sonnet-5-med` (new) | Sonnet 5 · medium |
+| `[31,41)` | `orc-executor-sonnet-5-high` | Sonnet 5 · high |
+| `[41,90)` | `orc-executor-opus-5-low` | Opus 5.5 · low |
+| `[90,100]` | `orc-executor-opus-5-med` | Opus 5.5 · medium |
+
+- The table had six bands. Seven executors now have no band
+  (`haiku-4-5`, `sonnet-4-6-med`, `sonnet-4-6-high`, `opus-4-7-med`,
+  `opus-4-7-high`, `opus-4-8-high`, `opus-5-high`). They still ship.
+  `rubric_bands_override`, `orc diy`'s `fixed_executor` and
+  `extra_fallback_agent` can still name them.
+- **The cost effect:**
+  - Scores 41–64 move from Sonnet (Sonnet 4.6 high $3/$15, Sonnet 5 high $2/$10)
+    to **Opus 5.5 low ($4/$20)**. This is the largest change.
+  - Scores 0–29 move from Haiku 4.5 ($1/$5) to Sonnet 5 low or medium ($2/$10).
+  - Scores 30–39 move from Sonnet 4.6 medium ($3/$15) to Sonnet 5 high ($2/$10).
+  - **Every band from 41 needs an Opus 5.5 main session.** Before, this was from
+    65. A lower main session runs these tasks on the session model, and the tier
+    line says so.
+  - Sandbox sample (14 scored tasks): the Opus share goes from 6 to 7 of 14, and
+    the Haiku share from 6 to 0. The sample is small. Measure your own project
+    with `orc stats`.
+- **`opus5_only` does not change** (`[0,90)` low · `[90,100]` medium). It now
+  differs from the default table only below score 41. The `opus5_only` text in
+  `orc config` showed an old three-band ladder; it now shows the real two bands.
+- A user route row in `orc diy` that spans two Claude bands now names both
+  agents.
+
+**4. The price table is correct** (`bin/pricing.json`, dated 2026-10-01)
+
+- `claude-sonnet-5-5` is added: $2 input · $2.50 cache write · $0.20 cache read
+  · $10 output per MTok.
+- `claude-sonnet-5` was $3/$15; it is now $2 / $2.50 / $0.20 / $10.
+- `claude-opus-5`, `claude-opus-4-8` and `claude-opus-4-7` are now
+  $5 / $6.25 / $0.50 / $25.
+- `claude-fable-5` is now $10 / $12.50 / $1 / $50.
+- `claude-sonnet-5-5` has a context window row, so `orc budget` shows its
+  context risk.
+
+**5. Review**
+
+- **The reviewer is `orc-reviewer-opus-5-low`** (renamed from
+  `orc-reviewer-opus-5-med`; low effort). In the live eval, low effort found
+  100% of the seeded defects that were still in the diff. **A script that names
+  the old file breaks.** `orc update` removes the old file.
+- **Review quality no longer says "0 so far" after real reviews.** It read only
+  `observations.jsonl`, and no lane wrote that file. Now a run with a
+  `FINDING-OUTCOME` line or a reviewer return in its trace counts as a review. A
+  clean review counts too. `orc gotcha quality --json` has two new fields:
+  `reviews_traced` and `reviews_observed`.
+- **An observation with `author: orc` must name its `run`.** Without it, `orc
+  gotcha observe` exits 2 and names `run`. A `ref` that starts with the run id
+  fills `run` for you.
+- **Your project's own review rule.** New command **`orc review policy`**. It
+  reads CLAUDE.md and AGENTS.md for a line that asks for a different review (for
+  example "All code review must go through /code-review"). When it finds one,
+  every coding lane that changed code asks: ORC review, that review, or skip.
+  The answer goes in a new trace line, `REVIEW-WHICH`. An external review is
+  counted as "Project reviews" and never in the ORC headline.
+- **Fixes the review can see.** An observation can now carry `introduced_by`
+  (`orc` · `ai` · `human` · `unknown`, from `git blame`), and a fix after a
+  review is recorded. The reviewer card shows a `fix` line for each changed file.
+  A review that missed a later fix is counted as a miss.
+- **New lane `/orc-fix`** with the commands **`orc fix classify`**, **`orc fix
+  record`** and **`orc fix list`**. Inside a paused run, `/orc-fix` only records:
+  one observation and one `FIX` line in the trace of that run. With no run open,
+  it fixes the way `/orc-quick` does, and it asks which agent to use. It refuses
+  while a dispatch is in flight.
+
+**6. The Behaviour tab**
+
+- The gate habit now proposes: one agent name written three ways now counts as
+  one answer.
+- `/orc-fast` reads its lane config first, so it records your answers.
+  `/orc-analyze` and `/orc-diy` do the same.
+- With `habits: off` you still see the Review quality and Gotchas tabs. Review
+  learning is always on.
+- The answer log shows the question, not only its id.
+- A run is dated from its file name. Rows say `orc-quick`, not `quick`. An empty
+  row is not shown.
+- At the end of a run, `orc trace write` names a question whose key you set in
+  your config when the lane wrote no answer for it.
+
+**7. Clear old logs**
+
+- New command **`orc clear logs`**. It shows the old traces and finished run
+  folders that it can delete, and why it keeps the rest. **`orc clear logs
+  --apply`** deletes them.
+- New key **`log_retention_days`**: 30 · 60 · 90 · 120 · 240 · 360 days
+  (default 90). The cutoff is never shorter than `aftermath_window_days`.
+- It never deletes your data, a waiting run, the active trace, a file younger
+  than 6 hours, or a trace with a habit answer that is younger than 180 days.
+- `orc stats` keeps the totals of a deleted run in `.claude/orc/logs-rollup.json`
+  and says "includes N pruned runs".
+- **The promise "log_dir is never deleted automatically" changes.** It is still
+  true by default. New key **`log_retention_auto`** (default `off`): `on` runs
+  the delete after a lane's last trace packet, at most once per 24 hours.
+- `orc ui` ▸ Maintenance has a **Clear old logs** row with a full preview.
+
+**8. The status line timer**
+
+- New key **`statusline_refresh`**: `off` · `1` · `2` · `3` · `5` · `10` seconds
+  (3 is new). It writes `statusLine.refreshInterval` in `settings.json`, the same
+  as `orc statusline refresh`, and `orc config list` reads it from there.
+- **The floor is 1 second.** Claude Code gives no timer below 1 second. A value
+  below 1 is refused, and the message names the nearest value. In `orc ui` ▸ CLI
+  Hook Interface, 0.2 · 0.5 · 0.7 are disabled.
+- With a timer, a pet moves one step for each redraw. `usage.json` is written
+  only when the numbers change.
+- `orc doctor` tells you when the value is below the floor, when a moving part
+  has no timer, and when the timer is on the sub-agent board.
+
+**Defects found in the live evals, and fixed**
+
+- **D1:** `/orc-fast` refused to record review observations. Every lane that
+  runs a review now records them.
+- **D2:** a free-text `FINDING` line (`FINDING 9 findings — P0×2 …`) was
+  accepted. The CLI now checks the count head (`FINDING p0= p1= p2= p3=`).
+- **D3:** a `REVIEW-WHICH` line was written with no project rule and no name.
+  The CLI now checks the format, and refuses it when `orc review policy` says
+  "orc".
+- **D4:** the question "which review" was asked with no project rule. It is now
+  refused by name.
+- **D5:** a `FINDING-OUTCOME` line used its own category names. The categories
+  are now checked against the closed set of the review return.
+- **D6:** an `/orc` run skipped review and verify for a small change. At the
+  end, `orc trace write` now names the skipped phase. `/orc` always runs both.
+- **D7:** an `/orc-quick` run wrote its trace lines by hand. No CLI check and no
+  end-of-run reminder ran, and the lane then said the findings were recorded.
+  The session hook now stops the turn once when a trace has more narration lines
+  than its `.jsonl` twin, and names `orc trace write` and `orc gotcha observe`.
+- **D8:** an `/orc` run ignored the end-of-run reminder to record its review
+  outcomes. The session hook now stops the turn once when a finished run had a
+  review with findings and no observation names the run.
+
+**Live evals.** Five rounds ran `/orc-mini`, `/orc-fast`, `/orc-quick` and `/orc`
+in a sandbox (17 sessions, about 43 USD). The reviewer at low effort found every
+seeded defect that was still in the diff, habit capture and the review count
+passed, and D1–D8 were each found live, fixed, and checked again in a later
+round. The `/orc-fix` eval (E-F1) is still to do. The result
+files are in `eval/results/2.1.0/` (maintainer copy, not in the package).
+
+**What you have to do**
+
+| You have … | What happens |
+|---|---|
+| any install | Run `orc update`. It removes the three renamed agent files and the two deleted twins. |
+| a compiled `orc diy` flow | The status line shows `STALE→recompile`, and `/orc-diy` refuses. Run `orc diy compile`. |
+| `rubric_bands_override`, `fixed_executor` or `extra_fallback_agent` with an old executor | It works. Those executors still ship. |
+| a main session on Opus 4.8 or Sonnet | Scores 41–64 now run on the session model (before, from 65). The tier line says so. |
+| a config or old traces that name `claude-sonnet-5` | They still work and still price. |
+| old traces that name the old reviewer | `orc stats` and `/orc-retro` still read them. |
+| a script that names `orc-reviewer-opus-5-med` | It breaks. Change it to `orc-reviewer-opus-5-low`. |
+| a script that observes with `author: orc` and no `run` | It exits 2 and names `run`. Add `run`. |
+| a 2.0.4 CLI on the same project | It reads the new observation fields. If it writes the same observation again, it drops `introduced_by` for that one row. |
+| Review quality in the panel | The review count goes up, because traces count now. Acceptance does not change. |
+| `refreshInterval` 1–60 in `settings.json` | `orc update` keeps it. |
+| habits off | `orc lane config --json --no-probes` is byte-identical. |
+
+New files `review-scope.jsonl` and `logs-rollup.json` are your data: they are not
+in the install manifest, they survive `orc update`, `--prune` and `doctor --fix`,
+and `orc clear logs` never deletes them.
+
+---
+
+### v2.0.4 — design the status line to the last cell _(2026-09-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`
+
+**Do not use `npm i -g -f`.** Full detail in v0.56.0 below.
+
+`orc ui` ▸ CLI Hook Interface can now change almost everything a terminal cell can
+show. Before, a bar drew only its cells: you could not put words before, after,
+above or below it, and a gradient used fixed colours. Every item below is a
+`orc statusline set` flag, and the part editor has a control for each one.
+
+**Words around any shape**
+
+- **A name on every shape.** `--label` now draws on a bar, a spark, an icon and a
+  motion mark too. `--label-pos before|after|above|below` says where it goes. A name
+  you already typed on a bar shows before it when you choose no position.
+- **Text before and after the shape.** `--prefix` and `--suffix` wrap a bar, for
+  example `[██░░]`.
+- **The number next to the bar.** `--value-pos before|after` draws the value of the
+  part beside its shape, with your number format.
+- **Captions.** `--caption "five-hour window"` puts a short text on a row above or
+  below the part, at the column of the part (`--caption-pos`, `--caption-align
+  left|center|right`, `--caption-color`, `--caption-case`). `{value}` and `{label}`
+  in the text are replaced.
+- **Small text.** A terminal has no font size, so `--case` (and `--caption-case`)
+  have three Unicode styles: `small` (ꜱᴍᴀʟʟ ᴄᴀᴘꜱ), `super` (ˢᵘᵖᵉʳ) and `sub` (numbers like ₆₁).
+
+**Bars in your own colours and characters**
+
+- `--fill-color` and `--empty-color` colour the filled and the empty cells.
+- `--ramp-colors "#22c55e,#eab308,#ef4444"` and `--ramp-stops "0,60,85"` give any
+  part your own colour range. On `gradient` with hex colours, each cell is blended
+  in true colour.
+- `--fill-char ■ --empty-char □` draw the bar with your own characters (one cell
+  each).
+- `--threshold` sets the mark on `split` and `marker`.
+
+**More control on every part**
+
+- `--brackets "⟦,⟧"`, `--pad-left`, `--pad-right`, `--align`, `--sign`, `--max-len`
+  and `--unknown dash|hide`.
+- `--bg` and any `#rrggbb` colour are in the editor now, and you can pick more than
+  one weight (bold and underline).
+- `--state-color "ok=green,critical=red"` and `--state-glyph "ok=✓"` per state.
+- `--param k=v` sets the settings of a part (the text of `text`, the clock format).
+
+**Lines**
+
+- `orc statusline line <n> --align right|center` and `--sep-color`. The panel also
+  takes your own separator text.
+
+**Six parts that drew nothing now work**
+
+- `text`, `divider`, `spacer`, `icon-static`, `fill` and `config` bound a value that
+  is always empty, and no command could set their text. They draw now. `fill`
+  pushes the parts after it to the right edge of the terminal.
+
+**Animated pets and weather**
+
+- **Eight pets that move** (group "Pets and motion"): `pet-cat` (a pixel cat drawn
+  in braille dots), `pet-mouse`, `pet-chase` (the cat chases the mouse),
+  `pet-cat-text` (ᓚᘏᗢ), `pet-pacman` (it eats the dots), `pet-fish`, `pet-bird` and
+  `pet-dog`. Each has three shapes: `run` (across the track), `bounce` (right and
+  back) and `idle` (stays and moves its legs), a track width of 6–40 cells, and a
+  `speed` setting.
+- **Weather:** `weather` (the temperature), `weather-icon` (☼ ◐ ☁ ☂ ❄ ϟ ≋) and
+  `weather-desc`. Set `location` (empty = found from your network address) and
+  `units` (`metric` or `us`). The hook never waits on the network: a small
+  background fetcher asks wttr.in at most every 30 minutes, and only while a weather
+  part is on your layout. `ORC_STATUSLINE_NO_NET=1` stops it.
+- **`orc statusline refresh <seconds|off>`** sets `refreshInterval` in the status
+  line setting. Claude Code redraws the status line only on events, or on this
+  timer (at least 1 second). So a pet moves about one step per second. The panel has
+  the same control, and tells you when a moving part has no timer.
+
+**The panel**
+
+- **Live preview of unsaved changes.** The panel replays your staged changes in a
+  temporary copy and draws the real result before you press Apply. A change that
+  the CLI refuses is named before Apply.
+- **The preview moves.** A layout with a pet or a motion mark plays 12 frames in the
+  panel (at most 20 seconds, never when your system asks for reduced motion).
+- A new `designer` preset shows the new powers.
+
+**Fixes**
+
+- **Text above or below a part showed at the start of the line.** Claude Code
+  removes the spaces at the start of every status line row, so a caption row, a
+  line prefix and a right-aligned line lost their indent. The first space of such a
+  row is now a braille blank (U+2800), which Claude Code keeps. The caption shows
+  above or below its own part.
+- **Spark showed nothing.** `burn-rate` and `tok-speed` never recorded a history,
+  the first sample came after 20 seconds, and an empty history drew `░░░░░░░░`.
+  Now every history is recorded, the first sample is taken at once, the spark adds
+  the current value as its last point, and an empty spark shows `—`. `spark-braille`
+  keeps its width, and `trend` with one point shows `—`.
+- **An unknown value on a bar drew an empty bar** (it read as 0%). It shows `—` now.
+- **A small value on a bar drew no cell** (6% on 10 cells). A value above 0 fills
+  at least one cell.
+- **`fill` could make a row wrap.** It leaves the last column free.
+- **Parts disappeared on a wide terminal.** When any line was wider than 72 cells,
+  the plan for a narrow terminal was used on every wider one too, and it could
+  remove a part from a line that fitted. Now a part is removed only when the
+  terminal is narrower than the widest line, and only from a line that does not fit.
+- Clearing a text field or a weight in the panel returned HTTP 400 ("missing
+  argument"). The clear now reaches the CLI.
+- A label, caption or separator with a control character (for example ESC) is
+  refused. Before, a layout could send terminal escape codes to your terminal.
+- `orc statusline set … --board subagent` read `subagent` as the part type.
+
+**What you have to do:** `orc update`. Layouts you already have compile to the same
+bytes.
+
+---
+
+### v2.0.3 — the status line you designed is the status line you see _(2026-09-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`
+
+**Do not use `npm i -g -f`.** Full detail in v0.56.0 below.
+
+A patch for `orc ui` ▸ CLI Hook Interface. You designed a status line, the panel said
+"Your lines are showing", and the terminal showed ORC's built-in lines. Some settings
+also did nothing when you applied them. Each fix is below.
+
+**Why your design fell back to the built-in lines**
+
+- **The hook compared version numbers, not the parts it can draw.** It refused a
+  compiled layout when the ORC version that compiled it was not the version of the
+  installed hooks. A CLI one patch newer than the hooks, or any upgrade, sent the bar
+  back to the built-in lines. Now `orc init` and `orc update` write `catalog_hash` into
+  `hooks/orc-version.json`, and the hook compares that hash with the lock. A different
+  version with the same parts renders your layout. An install with no hash keeps the
+  old version check.
+- **`orc update` recompiles your layout.** Before, nothing recompiled it after an
+  upgrade. Both boards are recompiled when their layout exists and validates. A layout
+  that does not validate is not touched, and the output says so.
+- **The panel tells you when your terminal does not show your layout.** `statusline
+  show --json` now carries `hook` (the installed hook, its version, whether it matches,
+  the recorded fallback and the fix). The status card shows "NOT IN YOUR TERMINAL" and
+  the command to copy (`orc update`, `orc update --global` or `orc statusline compile`).
+  `orc doctor` reports the same as `statusline-hook-skew`, with `fix_command`.
+- **A good render and a compile both clear the old fallback record**, so `orc doctor`
+  does not report a problem that is already gone.
+- **`statusline_custom: on  # a comment` now arms the layout** (and the same for
+  `subagent_line_custom`).
+- **A compiled op the hook does not know** falls back as `statusline-layout-skew`.
+
+**Settings that did nothing**
+
+- **You can clear a field.** An empty Name, Before, After or number sets the field back
+  to the shared value, and the colour and weight pickers have a "shared" option
+  (`--value-color inherit`). Before, the write said "ok" and changed nothing.
+- **A value that starts with `-` is kept** (for example a `-` prefix).
+- **Change part (swap) works** when the old shape does not fit the new part. The CLI
+  drops the old shape, name and width instead of refusing the swap.
+- **Your own colour and weight reach a bar.** A default colour ramp won over the value
+  colour you set, and the emphasis was lost with it.
+- **`mono` has no colour.** A default ramp no longer colours a `mono` bar.
+- **Apply stops at the first refused change.** The writes use positions, so a write
+  after a refusal changed the wrong part. The message names the refused change and how
+  many changes were not sent.
+- **A chip on the board shows the part as you saved it** (your name, colours and theme),
+  not the catalogue sample.
+
+**Parts that drew the wrong text**
+
+- `api-time` and `wall-time` showed milliseconds as minutes (`api 960000m`).
+- `clock` showed a raw number (`1767225600000`). It shows `HH:mm` now.
+- `pill` put the value inside the brackets (`⟪ORC2.0.2⟫`). It is `⟪ORC⟫2.0.2` now.
+- `effort` with `dots` drew nothing.
+- `lines-added` showed `+ +412`.
+- Four part descriptions still said the limit is five parts. It is six.
+
+**Also in `orc ui`**
+
+- The global-install banner could show twice, and it offered the wrong command
+  (`orc wiki sync`). It shows once and offers `orc update --global`.
+
+**What you have to do:** `orc update`. Your layout is recompiled for you.
+
+---
+
 ### v2.0.2 — the lanes record what you answered, and the reviewer always gets the card _(2026-09-28)_
 
 **Still on the unscoped `orc` package?** Do this once first - your `orc upgrade`

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-2.0.2-blue.svg?style=for-the-badge)
+![Version](https://img.shields.io/badge/version-2.1.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: v2.0.2** · diperbarui 28-09-2026 · [daftar perubahan lengkap](CHANGELOG.md)
+**Versi terbaru: v2.1.0** · diperbarui 02-10-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`
 
@@ -275,6 +275,7 @@ pemakaian 5 jam, pemakaian mingguan, dan beberapa hal lain.
 | **`/orc-mini`** | Satu agen Sonnet 5, satu pemeriksaan build + tes, lalu kirim. Melewati review penuh dan pengujian. Satu baris **pembacaan kompleksitas** berisi angka menawarkan lane penuh kalau perubahannya lebih luas dari satu area. Bisa pindah ke alur penuh di tengah jalan kalau diminta. | [lihat](templates/skills/orc-mini/examples/mini-run-mock.md) |
 | **`/orc-fast`** | Lane tercepat. Butuh wiki yang masih segar **dan** pola kode yang sudah tersimpan; kalau ada, ia melewati tahap analis dan perencana sepenuhnya. Kalau salah satu syarat tidak ada, ia mundur ke `/orc-mini` — obrolan tidak pernah berhenti. | [lihat](mock-run/orc-fast.md) |
 | **`/orc-quick`** | Minta apa saja: perbaikan kecil, pertanyaan, mencari bug, menaikkan versi dependensi, komentar PR. Lihat → tanya sekali → kerjakan. **Selalu bertanya agen mana yang mau dipakai**, dan tidak ada pengaturan yang bisa mengubah itu. Satu **defect direproduksi merah dulu sebelum diperbaiki**. | [lihat](mock-run/orc-quick.md) |
+| **`/orc-fix`** | Memperbaiki satu hal setelah review: isu Sonar, CI merah, atau bug yang ditemukan orang. Di dalam run yang sedang dijeda, ia hanya **mencatat** perbaikannya (satu observasi dan satu baris `FIX` di jejak run itu), jadi review yang melewatkannya ikut terhitung. Kalau tidak ada run yang terbuka, ia memperbaiki seperti `/orc-quick` dan bertanya agen mana yang dipakai. | [lihat](mock-run/orc-fix.md) |
 | **`/orc-diy`** | Lane racikan Anda sendiri, disusun di terminal dengan `orc diy` lalu dikompilasi. Kalau belum disetel atau sudah basi, ia menolak jalan dan menawarkan `/orc` biasa. | [lihat](mock-run/orc-diy.md) |
 
 ### Memikirkan apa yang mau dibuat
@@ -665,9 +666,19 @@ dipublikasikan mengubahnya jadi angka. Risiko yang dikutip memaksa nilai minimal
 model terkunci** — jadi apa yang benar-benar berjalan bisa diperiksa, bukan
 sekadar diminta lewat kalimat.
 
+Tabel bawaan (sejak v2.1.0):
+
+| Nilai | Agen | Model · effort |
+|---|---|---|
+| `[0,21)` | `orc-executor-sonnet-5-low` | Sonnet 5 · low |
+| `[21,31)` | `orc-executor-sonnet-5-med` | Sonnet 5 · medium |
+| `[31,41)` | `orc-executor-sonnet-5-high` | Sonnet 5 · high |
+| `[41,90)` | `orc-executor-opus-5-low` | Opus 5.5 · low |
+| `[90,100]` | `orc-executor-opus-5-med` | Opus 5.5 · medium |
+
 > **Aturan yang paling sering membuat orang bingung:** model sebuah subagen tidak
-> akan pernah lebih tinggi daripada model sesi utama Anda. Jalankan sesi Anda di
-> Opus 5.
+> akan pernah lebih tinggi daripada model sesi utama Anda. Setiap pita mulai nilai
+> 41 butuh sesi utama Opus 5.5.
 
 **Penjelasan lengkap — pita nilainya, `opus5_only`, dan penjaga tingkat yang
 dipasang `orc init`: [guides/model-selection.md](guides/model-selection.md).**
@@ -699,13 +710,13 @@ yang sama.
 
 ```
 templates/
-├── skills/       31 folder skill, 38 berkas SKILL.md (satu lane boleh membawa
+├── skills/       34 folder skill, 41 berkas SKILL.md (satu lane boleh membawa
 │                 sub-skill) — lane di atas, plus yang tidak punya perintah
 │                 sendiri: context-combiner, orc-advisor, orc-judge,
 │                 orc-analyze-mini, dan _shared/ (kesepakatan lintas lane)
-├── commands/     29 perintah garis miring
+├── commands/     33 perintah garis miring
 ├── hooks/        penjaga effort (PreToolUse) · peringatan statusline · catatan jejak
-└── agents/       48 subagen dengan model terkunci + MODEL-MAPPING.md
+└── agents/       50 subagen dengan model terkunci + MODEL-MAPPING.md
 bin/cli.js        pemasang, penyunting pengaturan, penyusun alur, pembaca status
                   pekerjaan, dan separuh pasti dari setiap lane. Setiap pembacaan
                   bisa menjawab --json
@@ -786,25 +797,43 @@ 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.
 
-### v2.0.2 - lane mencatat jawaban Anda, dan reviewer selalu mendapat kartunya _(28-09-2026)_
-
-**Patch dari eval langsung.** Habits sekarang benar-benar bekerja di run langsung, dan
-reviewer selalu mendapat kartunya:
-
-- **Jawaban Anda dicatat dengan benar.** `orc trace write` memeriksa setiap jawaban saat
-  masuk dan mengembalikan jawaban yang salah bersama id yang benar. Di akhir run, ia
-  menyebut pertanyaan yang belum dicatat.
-- **Reviewer selalu mendapat kartu gotcha.** Sebuah hook memberikannya ke setiap
-  reviewer, verifier dan judge.
-- **Run yang tidak menulis trace dihentikan sekali** dan diberi tahu cara memperbaikinya.
-- **`/orc-quick` selalu mengambil snapshot undo.**
-- **Kartu aturan ringkas menyala secara default untuk `/orc-mini` dan `/orc-fast`** (eval E4 lulus).
-
-**Yang harus Anda lakukan:** `orc update`.
+### v2.1.0 - review terhitung, tabel nilai naik, dan log lama bisa dihapus _(02-10-2026)_
+
+- **Tabel nilai baru dengan lima pita.** Nilai 0–40 ke Sonnet 5 (low, medium,
+  high). Nilai 41–89 ke Opus 5.5 low, dan 90–100 ke Opus 5.5 medium. Haiku tidak
+  lagi ada di tabel. **Setiap pita mulai nilai 41 butuh sesi utama Opus 5.5.**
+- **Sonnet 5 berjalan di `claude-sonnet-5-5`.** Tabel harga kembali benar.
+- **Reviewer sekarang `orc-reviewer-opus-5-low`.** Di eval langsung, effort low
+  menemukan setiap cacat yang sengaja ditanam dan masih ada di diff.
+- **Pemindai wiki dan penulis CLAUDE.md memakai Opus 5.5 low** (dulu Opus 4.8).
+- **Review quality tidak lagi menulis "0 so far" setelah review sungguhan.** Ia
+  menghitung review dari jejak. Review yang bersih juga dihitung.
+- **Aturan review milik proyek Anda.** Kalau CLAUDE.md atau AGENTS.md meminta
+  review lain (misalnya `/code-review`), lane bertanya "review ORC, review itu,
+  atau lewati". `orc review policy` menunjukkan apa yang ORC temukan.
+- **Lane baru `/orc-fix`.** Ia mencatat perbaikan setelah review (Sonar, CI merah,
+  bug) dan siapa yang memasukkan bug itu. Kartu reviewer menampilkannya, dan panel
+  menampilkan "Fixes after review".
+- **`orc clear logs`** menampilkan jejak dan folder run yang lama. `--apply`
+  menghapusnya. Tidak ada yang dihapus otomatis kecuali Anda menyetel
+  `log_retention_auto: on`.
+- **Timer status line:** 1, 2, 3, 5 atau 10 detik. Di bawah 1 detik ditolak, karena
+  Claude Code tidak mendukungnya.
+- **Perbaikan tab Behaviour:** dengan `habits: off` Anda tetap melihat Review quality
+  dan Gotchas, `/orc-fast` mencatat jawaban Anda, dan log jawaban menampilkan
+  pertanyaannya.
+
+**Yang harus Anda lakukan:** `orc update`. Kalau Anda punya alur `orc diy` yang
+sudah dikompilasi, jalankan `orc diy compile`. Kalau ada skrip yang menyebut
+`orc-reviewer-opus-5-med`, ganti menjadi `orc-reviewer-opus-5-low`. Biayanya
+berubah: baca CHANGELOG.
 
 <details>
-<summary><strong>Rilis sebelumnya</strong> — 124 rilis, hanya judulnya. Teks lengkapnya (dalam bahasa Inggris) ada di <a href="CHANGELOG.md">CHANGELOG.md</a>.</summary>
+<summary><strong>Rilis sebelumnya</strong> — 127 rilis, hanya judulnya. Teks lengkapnya (dalam bahasa Inggris) ada di <a href="CHANGELOG.md">CHANGELOG.md</a>.</summary>
 
+- **v2.0.4** — design the status line to the last cell · _2026-09-30_
+- **v2.0.3** — the status line you designed is the status line you see · _2026-09-30_
+- **v2.0.2** — the lanes record what you answered, and the reviewer always gets the card · _2026-09-28_
 - **v2.0.1** — the trace keeps the gate name, and the lanes find the habits rule · _2026-09-27_
 - **v2.0.0** — the coding lanes remember what you fixed and how you work · _2026-09-27_
 - **v1.9.2** — the code graph gets its own tab, and Opus 5 becomes Opus 5.5 · _2026-09-23_