@irythill/orq 0.4.0 → 0.6.0

package/dist/stats.js

@@ -6,7 +6,8 @@
 import { existsSync, readdirSync, readFileSync, statSync } from "node:fs";
 import { homedir } from "node:os";
 import { basename, join } from "node:path";
-const ROLE = /^(impl|fix\d*|review\d*|[a-z]+-review\d*)-?/;
+import { doneStatus } from "./process.js";
+const ROLE = /^(impl|fix\d*|review\d*|[a-z]+-review\d*|watchdog\d*)-?/;
 const read = (f) => { try {
     return readFileSync(f, "utf8");
 }
@@ -115,11 +116,12 @@ export function collectRuns(ws, days) {
             const name = basename(pre);
             const rm = ROLE.exec(name);
             const role = rm && rm[1].includes("review") ? "review"
-                : name.startsWith("fix") || txt.includes("-R ") || txt.includes(" resume ") || txt.includes("--resume") ? "fix"
-                    : name.startsWith("impl") ? "impl" : "other";
+                : rm && rm[1].startsWith("watchdog") ? "watchdog"
+                    : name.startsWith("fix") || txt.includes("-R ") || txt.includes(" resume ") || txt.includes("--resume") ? "fix"
+                        : name.startsWith("impl") ? "impl" : "other";
             const out = read(`${pre}.out.md`);
             const [neu, tot] = tokens(agent, log, read(`${pre}.id`).trim());
-            runs.push({ issue, name, agent, model, role, ok: read(done).includes("status=ok") && out.trim() !== "",
+            runs.push({ issue, name, agent, model, role, ok: doneStatus(read(done)) === "ok" && out.trim() !== "",
                 secs: Math.max(0, Math.floor((statSync(done).mtimeMs - rs.mtimeMs) / 1000)), new: neu, tot,
                 repo: name.includes("-") ? name.slice(name.indexOf("-") + 1) : "" });
         }

package/dist/testrun.js

@@ -2,14 +2,14 @@
 // memory cap (src/process.ts) and read its JSON report into "<file relative to the repo> :: <full test name>" lines.
 // The runner's own bin (node_modules/<runner>/package.json "bin") runs with this node, so Windows needs no shell;
 // without it, npx as before. Also the background job both share (launch on a TerminalHost, queue, .pid/.done, notify).
-import { spawn, spawnSync } from "node:child_process";
+import { spawnSync } from "node:child_process";
 import { createWriteStream, existsSync, lstatSync, readFileSync, realpathSync, rmdirSync, rmSync, symlinkSync, unlinkSync, writeFileSync } from "node:fs";
 import { dirname, isAbsolute, join, relative } from "node:path";
 import { fileURLToPath } from "node:url";
 import { writeAtomic } from "./fsutil.js";
 import { m } from "./i18n.js";
 import { acquire, release } from "./lock.js";
-import { stateDir } from "./paths.js";
+import { handoffFile, notify } from "./notice.js";
 import { killTree, parseSize, runCapped } from "./process.js";
 import { closeOwnTab, detectHost, launch } from "./terminal.js";
 export const JS_EXT = /\.(ts|tsx|js|jsx|mjs|cjs|mts|cts)$/;
@@ -197,28 +197,5 @@ export async function inJob(j, label, slots, body, done) {
     }
     return st === "ok" ? 0 : 1;
 }
-/** Where `orq handoff` records the pane that replaced a conductor's. */
-export const handoffFile = (pane) => join(stateDir(), "handoff", pane.replace(/\W/g, "_"));
-/** The conductor is a herdr pane: type the line into it (herdr-notify waits for it to leave a dialog). In the
- * background when the caller must not wait for that (an agent's end-of-turn hook holds its screen meanwhile). */
-export function notify(pane, line, background = false) {
-    const seen = new Set();
-    while (!seen.has(pane) && existsSync(handoffFile(pane))) {
-        seen.add(pane);
-        let next;
-        try {
-            next = readFileSync(handoffFile(pane), "utf8").trim();
-        }
-        catch {
-            break;
-        } // gone between the two calls
-        if (!next || next === pane)
-            break;
-        pane = next; // follow repeated handoffs to the current conductor
-    }
-    const local = join(dirname(CLI), "..", "setup", "herdr-notify"), cmd = existsSync(local) ? local : "herdr-notify";
-    if (background)
-        spawn(cmd, [pane, line], { detached: true, stdio: "ignore" }).on("error", () => { }).unref();
-    else
-        spawnSync(cmd, [pane, line], { stdio: "inherit" });
-}
+/** Tell the conductor's herdr pane (src/notice.ts): returns at once, delivery runs detached with retries and a log. */
+export { handoffFile, notify };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@irythill/orq",
-  "version": "0.4.0",
+  "version": "0.6.0",
   "description": "Orchestrate coding agents (Claude Code, Codex, OpenCode, Antigravity, Copilot) from one conductor.",
   "license": "MIT",
   "type": "module",

package/skills/issue/SKILL.md

@@ -1,36 +1,36 @@
 ---
 name: issue
-description: Runs a Plane issue end to end by orchestrating coding agents in herdr or any terminal (herdr-agent / orq agent + orq wait) — implementer and cross-vendor reviewer picked by orq pick, tests by herdr-verify / orq verify, comment and status in Plane. Use when the user says "/issue <ID>", "take issue X", "run ABC-123", or asks to check/create issues in the conductor's ecosystem.
+description: Runs a Plane issue end to end by orchestrating coding agents in herdr or any terminal (orq agent + orq wait) — implementer and cross-vendor reviewer picked by orq pick, tests by orq verify, comment and status in Plane. Use when the user says "/issue <ID>", "take issue X", "run ABC-123", or asks to check/create issues in the conductor's ecosystem.
 ---
 
-# /issue <ID> — conductor playbook (herdr or any terminal)
+# /issue <ID> — conductor playbook
 
 You are the **orchestrator**: you plan, dispatch, follow up and report. **Do not implement anything yourself** (it
 burns the conductor's model). Talk to the user in the user's language.
 
 **Ecosystem configuration:** the **workspace** `CLAUDE.md` (the folder named in your conductor instructions) defines
-the repositories and their groups (= herdr workspace, `-g`), **each repo's base branch**, verification commands,
+the repositories and their groups (= herdr workspace or just a label, `-g`), **each repo's base branch**, verification commands,
 Plane projects (identifier → project_id), default assignee, labels/modules and MCP limitations. Read it before you
 start. Below, `$WS` = workspace.
-**Inside herdr** (`HERDR_ENV=1`): children open in herdr tabs and their notices reach your pane — the flow below.
-**Outside herdr** (any terminal, tmux, any OS): the same flow with these swaps —
-- `herdr-agent ...` → `orq agent ...` (same flags; it is the same program). Children run in tmux windows inside tmux,
-  else in the background (their screen goes to a log; the answer is still `<prefix>.out.md`). `-T` needs tmux.
-- `herdr-claim` → `orq claim` (set `ORQ_CONDUCTOR_ID` to a fixed name per conductor), `herdr-deps` → `orq deps`.
-- **Completion signal:** no line arrives in your pane. After dispatching, run `orq wait <prefix>` **as a background
+**Terminal:** the flow is the same in herdr, tmux or a plain terminal, on any OS. Children open in herdr tabs inside
+herdr (`HERDR_ENV=1`), in tmux windows inside tmux, else in the background (their screen goes to a log; the answer is
+still `<prefix>.out.md`; `-T`, the agent's own screen, needs herdr or tmux). Set `ORQ_CONDUCTOR_ID` to a fixed name per
+conductor outside herdr.
+- **Completion signal:** in herdr, one line `[HERDR-AGENT DONE] <title> status=ok|fail ... answer: <file>` is typed into
+  your pane after each child. Anywhere else no line arrives: after dispatching, run `orq wait <prefix>` **as a background
   task** (Claude Code: Bash with `run_in_background`); its exit wakes you and its output is the line
-  `[ORQ AGENT DONE] <title> status=ok|fail ... answer: <file>` — treat it exactly like `[HERDR-AGENT DONE]`. Several
-  children in parallel: `orq wait --any <prefix1> <prefix2>` (one wake-up per finish; wait again for the rest).
-  No background tasks in your harness → run `orq wait` in the foreground; that is the one allowed blocking wait.
-- `herdr-verify` → `orq verify`, `herdr-baseline` → `orq baseline` (same flags). They run in a tmux window or in
-  the background like children, and you wait for them the same way: `orq wait $O/verify-<repo>`.
-- Peeking at a child: `<prefix>.log` (not `herdr pane read`).
+  `[ORQ AGENT DONE] <title> status=ok|fail ... answer: <file>`. Treat both lines the same. Several children in parallel:
+  `orq wait --any <prefix1> <prefix2>` (one wake-up per finish; wait again for the rest). No background tasks in your
+  harness → run `orq wait` in the foreground; that is the one allowed blocking wait.
+- `orq verify` and `orq baseline` run like children (herdr tab, tmux window or background) and you wait for them the same
+  way, e.g. `orq wait $O/verify-<repo>`.
+- Peeking at a child: `<prefix>.log` (in herdr also `herdr pane read $(cat <prefix>.pane) --source recent`).
 Issue artifacts (prompts, notes) live in `$WS/.orquestra/<ID>/`.
 
 ## 1. Read the issue
-- **First, claim it:** `herdr-claim -w $WS <ID>`. Exit 1 = another conductor owns it: **stop** and tell the user
+- **First, claim it:** `orq claim -w $WS <ID>`. Exit 1 = another conductor owns it: **stop** and tell the user
   (don't read it, don't dispatch anything). Taking it over (e.g. switching accounts) only with the user's OK:
-  `herdr-claim -w $WS -f <ID>`. Several conductors may share a workspace; `herdr-claim -w $WS -l` lists who has what,
+  `orq claim -w $WS -f <ID>`. Several conductors may share a workspace; `orq claim -w $WS -l` lists who has what,
   with each conductor's name (its herdr workspace label, e.g. "emp: orq-cms-dsgn"; outside herdr, `ORQ_CONDUCTOR_ID`).
 - **The user names another conductor** ("take over orq-cms-dsgn's work"): never guess a pane id. Run
   `orq claim -w $WS --from "<what they said>"` (any part of the name works). It lists that conductor's issues; exit 3 =
@@ -58,7 +58,7 @@ independent acceptance criteria.
 - Each batch is independently testable and reviewable; dispatch in order, one implementer per batch. Record the split in
   Plane (sub-issues or a checklist comment) before starting.
 - Scope too big mid-run (reviews hitting `policy.max_rounds`, repeated findings, the implementer asking to change
-  scope): stop, split the remainder, don't force more rounds.
+  scope): stop, split the remainder, don't force more rounds. `orq rounds <ID>` shows the alert; on warn/stop `orq rounds <ID> --diagnose` says why.
 
 ## 3. Pick agent and model: always `orq pick`, never by hand
 `orq pick` decides agent, model, effort and account (user config + delivery and token history + current quota +
@@ -71,19 +71,19 @@ orq pick opinion --impl-agent <agent that implemented>             # second opin
 ```
 More than one agent eligible for `review`/`opinion` (declared, not excluded or blocked, with a model for the role; quota is not considered) and neither `--impl-agent` nor `--impl-vendor` given → exit 2:
 always pass one of them (`--no-record`/`--explain` do not change this).
-The output goes straight into `herdr-agent` (`herdr-agent $(orq pick ...) -g ... -t ... -d ... -o ... -- prompt.md`).
+The output goes straight into `orq agent` (`orq agent $(orq pick ...) -g ... -t ... -d ... -o ... -- prompt.md`).
 - Exit 3 = no candidate (quota exhausted, no agent with that role): **stop and ask the user**.
 - Implementer failed review twice (step 6) → pick again without it: `orq pick impl --level <level> --exclude-agent <agent>`.
 - `--exclude-agent` never "sticks": every `orq pick` call decides again, with only that dispatch's exclusions.
 - The conductor's own model (e.g. Opus) as implementer: only with the user's OK, never through `orq pick`.
 - Want to understand a choice? `orq pick ... --explain --no-record` (score of each candidate; not counted in rotation).
 
-**Every child runs through `herdr-agent`** (agent from `orq pick`): headless (`claude -p` / `codex exec` /
-`opencode run` / `agy -p` / `copilot -p`) in a herdr tab (workspace = group `-g`, tab = title) with live output.
-When it finishes it writes `<prefix>.done` and sends ONE line `[HERDR-AGENT DONE] <title> status=ok|fail ...` to your
-pane; no MCP, and a **4 GB memory cap per agent** (own cgroup: if it blows up, only it dies). NEVER `herdr agent start`
+**Every child runs through `orq agent`** (agent from `orq pick`): headless (`claude -p` / `codex exec` /
+`opencode run` / `agy -p` / `copilot -p`) in a herdr tab (workspace = group `-g`, tab = title), a tmux window or the
+background, with a log. When it finishes it writes `<prefix>.done` and signals you (see the completion signal above:
+`[HERDR-AGENT DONE] <title> status=ok|fail ...` in herdr, `orq wait` elsewhere); no MCP, and a **4 GB memory cap per agent** (own cgroup: if it blows up, only it dies). NEVER `herdr agent start`
 for children (no memory cap, no answer file). **Screen mode (`-T`, or `HERDR_AGENT_TUI=1`; herdr or tmux):** the tab
-shows the agent's own TUI instead of the log; same cap, same files, same signal (end-of-turn hook). The screen stays
+or window shows the agent's own TUI instead of the log; same cap, same files, same signal (end-of-turn hook). The screen stays
 open after the turn (it holds memory until the tab closes); `-R` with the tab open types the follow-up into it. Use it
 when the user wants to watch. The repo must already be trusted in Codex/Claude (otherwise the TUI stops at the "trust this
 folder?" dialog — tell the user, don't approve it for them).
@@ -115,7 +115,7 @@ git -C $WT log -1 --format='%h %s'                    # check HEAD == origin/$BA
 on a modest disk that saturates I/O and memory and freezes the machine). The worktree uses a **link** to the main
 repo's `node_modules`:
 ```bash
-herdr-deps -r $R -b $BASE -w $WT     # link; stale deps → fast-forward + ONE install in $R (per-repo lock across conductors)
+orq deps -r $R -b $BASE -w $WT     # link; stale deps → fast-forward + ONE install in $R (per-repo lock across conductors)
 ```
 Exit 3 = stale deps and `$R` dirty or not on `$BASE` → **ask the user**. If another conductor is installing in the
 same repo, the command waits its turn (never install by hand).
@@ -124,36 +124,39 @@ tell me".
 **Dispatch** (no MCP; memory cap; writes in automatic mode — that is why implementation only happens in a worktree):
 ```bash
 orq pick impl --level <level> > $O/impl-<repo>.pick    # the fix rounds reuse it (step 6)
-herdr-agent $(cat $O/impl-<repo>.pick) -g <group> -t "<ID> impl <repo>" -d $WT -o $O/impl-<repo> -- $O/impl-<repo>.md
+orq agent $(cat $O/impl-<repo>.pick) -g <group> -t "<ID> impl <repo>" -d $WT -o $O/impl-<repo> -- $O/impl-<repo>.md
 ```
 - The Claude account (`-c`) already comes from `orq pick` (one under the limit whose pace stays within it, then the least used).
 - Full final answer in `$O/impl-<repo>.out.md`; log in `.log`; the agent's session id in `.id`.
 - Codex's sandbox has no network: `git fetch` is yours, beforehand (above). Push/PR: yours (step 7).
-- `herdr-agent` returns immediately (no need to background it); the child's pane is in `<prefix>.pane`
-  (`herdr pane read $(cat <prefix>.pane) --source recent` to peek).
-- **No baseline in the issue flow:** don't run `herdr-baseline` before dispatching (the base moves with every merge and
-  the full suite blocks every conductor's test queue). `herdr-verify` checks the base on demand (step 4b).
+- `orq agent` returns immediately (no need to background it); the child's pane is in `<prefix>.pane`
+  (to peek: `<prefix>.log`; in herdr, `herdr pane read $(cat <prefix>.pane) --source recent`).
+- **No baseline in the issue flow:** don't run `orq baseline` before dispatching (the base moves with every merge and
+  the full suite blocks every conductor's test queue). `orq verify` checks the base on demand (step 4b).
 - **Children start WITHOUT MCP** (Plane is yours; each MCP costs ~150–200 MB per session and `systemd-oomd` kills the
-  whole herdr server when memory runs out) — `herdr-agent` takes care of it.
+  whole herdr server when memory runs out) — `orq agent` takes care of it.
 - Every child prompt ends with: "Don't try to talk to the conductor or use herdr; finish with your complete final
   answer (that is what I read)."
 - **Verification in the child: lint and tsc only, one command at a time** (the cap is 4 GB per agent and jest/vitest
   blow it; tests are yours, step 4b): use the Verification column of the workspace `CLAUDE.md` and put in the prompt
   "verify sequentially, never in parallel or watch mode: (1) lint only the changed files (`git diff --name-only
   origin/<BASE>...HEAD`); (2) `NODE_OPTIONS=--max-old-space-size=2048 tsc --noEmit` for the project. Don't run tests".
-  Full suite only in CI (or a manual `herdr-baseline` if the user asks).
+  Full suite only in CI (or a manual `orq baseline` if the user asks).
 - An issue that changes an API contract: **API first**; consumers afterwards, with the new contract in the prompt.
+- **A red board line / `✗` pane title = a failure you may have missed.** If you see one (or the user says notices aren't
+  arriving), run `orq notice` (delivery log) and `<prefix>.done` for that issue, then handle the failure; running
+  `orq wait`, `orq verify` or `orq agent` for the issue acknowledges it.
 - **Never block waiting** (`herdr agent wait`, `pane wait-output`, `sleep`, `timeout`): completion arrives as a
-  `[HERDR-AGENT DONE]` line in your pane. Dispatch, report in one line and end your turn. "Done yet?" = `<prefix>.done`
+  `[HERDR-AGENT DONE]` line in your pane (herdr) or through the background `orq wait`. Dispatch, report in one line and end your turn. "Done yet?" = `<prefix>.done`
   exists (never `pgrep`).
-- Investigation only (no code): "READ ONLY" prompt, in the repo itself, no worktree. `herdr-agent -r` (Claude:
+- Investigation only (no code): "READ ONLY" prompt, in the repo itself, no worktree. `orq agent -r` (Claude:
   `--permission-mode plan`; the others: throwaway worktree, no editing).
 
 ## 4b. Tests (yours, not the child's)
 Child with `status=ok` → run the tests related to the diff, in their own tab, one at a time on the machine (queue):
-`herdr-verify -w $WS -r <repo> -d $WT -b <BASE> -o $O/verify-<repo> -g <group>` → `$O/verify-<repo>.txt` with
+`orq verify -w $WS -r <repo> -d $WT -b <BASE> -o $O/verify-<repo> -g <group>` → `$O/verify-<repo>.txt` with
 **new failures** and pre-existing ones: if any test fails, it runs the same test files on an updated
-`origin/<BASE>` (whatever fails there is pre-existing). You get `[HERDR-AGENT DONE] verify ... new=N`.
+`origin/<BASE>` (whatever fails there is pre-existing). You get the done line (`[HERDR-AGENT DONE]` / `[ORQ AGENT DONE]`) `verify ... new=N`.
 `new>0` → fix round with the list (step 6), no review. `new=0` → review.
 **Pre-existing failures get fixed too.** Any failure — tests listed as "already failing on origin/<BASE>", or a CI job
 (lint, biome, typecheck, shard, regression) failing on the PR or on the base — goes into a fix round on the issue's
@@ -162,12 +165,12 @@ something is red, new or old, and never widen a baseline or allowlist to silence
 outside the issue's domain: ask the user first (then it ships as its own PR, not as a note).
 **Mandatory order every round (impl and each fix): child `ok` → verify → review.** Never dispatch the review (or an
 "early" fix) while this round's verify is pending, even if it is queued behind another verify: wait for
-`[HERDR-AGENT DONE] ... verify ...` and end your turn until then.
+the `... verify ...` done line and end your turn until then.
 
 ## 5. Cross review (always another vendor)
 ```bash
 orq pick review --level <level> --impl-agent <who implemented> > $O/review-<repo>.pick   # round 2+ reuses it
-herdr-agent $(cat $O/review-<repo>.pick) -b $BASE \
+orq agent $(cat $O/review-<repo>.pick) -b $BASE \
   -g <group> -t "<ID> review <repo>" -d $WT -o $O/review-<repo> -r -i $O/impl-<repo>.md -i $O/impl-<repo>.out.md \
   -i $O/verify-<repo>.txt \
   -- $O/review-<repo>.md
@@ -178,12 +181,14 @@ are in the attached verify)". If the reviewer ends with `status=fail` and no ver
 `jetski: ... permission` line), that is not a rejection: run `orq pick review ... --exclude-agent <it>` and redo it.
 `--exclude-agent` applies **only to redoing that review** (save the new pick to `review-<repo>.pick`); the next
 round reuses whoever gave the verdict. An agent that failed twice in a row with no verdict →
-`orq block <agent> --days 1` and tell the user.
+`orq block <agent> --days 1` and tell the user. If it stopped on a quota limit, use `orq block <agent> --quota` (until
+the window resets; a fixed period outlives it and keeps the agent out of `orq pick` for nothing). If `orq pick` finds no
+candidate, its output is empty and `orq agent` refuses to start: stop and tell the user.
 **Review tools** (an agent whose `run` has no `{prompt}`/`{prompt_text}`/stdin, e.g. a CodeRabbit-like CLI with
 `ok_exit`/`filter` in the config): same command; it ignores the prompt and the attachments and reviews the branch
 against `{base}` itself. Read its answer like any other: `status=ok` with `rc≠0` is a verdict with findings, not a
 failure. Its high-severity items are the blockers, still under the step 6 rule (`file:line` + concrete failure).
-If the tool's answer opens with (or, when short, consists of) a statement that nothing was reviewed (e.g. Corvus's "Nada para revisar"), `agents.<name>.no_review` (a
+If the tool's answer opens with (or, when short, consists of) a statement that nothing was reviewed (e.g. Revtool's "Nothing to review"), `agents.<name>.no_review` (a
 regex) makes `orq agent` end that run `status=fail`: `orq pick`'s fallback and the conductor treat it as not run,
 same as an empty answer.
 **Second opinion** (`orq pick opinion`, read only, same attachments): only on **heavy** issues or when reviewer and
@@ -206,7 +211,7 @@ repo checklist.
 only restates a `## Decisions` choice, counts as a suggestion; when you downgrade one, say why in the Plane comment.
 No blockers left → APPROVED, even with suggestions.
 Blocking problems → write the list (blockers only) to `$O/fix-<n>.md` (always this name; reviews `$O/review-<repo>-<n>`, never `fix<n>-<repo>` or other variants — a later conductor counts rounds by these files) and continue the implementer's session (any agent):
-`herdr-agent $(orq pick fix --same $O/impl-<repo>.pick) -g <group> -t "<ID> fix<n> <repo>" -d $WT -o $O/impl-<repo> -R $(cat $O/impl-<repo>.id) -- $O/fix-<n>.md`.
+`orq agent $(orq pick fix --same $O/impl-<repo>.pick) -g <group> -t "<ID> fix<n> <repo>" -d $WT -o $O/impl-<repo> -R $(cat $O/impl-<repo>.id) -- $O/fix-<n>.md`.
 A fix is a continuation: same agent, model, account and session, effort one level up (`--same` reads the implementer's
 pick; never a new `orq pick`, never `-a` alone — without `-m` the session resumes on the CLI's default model, which
 loses the prompt cache and hands the work to a weaker model). `fix-<n>.md` = the numbered blockers + these rules: "fix only
@@ -214,7 +219,7 @@ these items, with the smallest diff that does it; don't refactor, rename or refo
 each blocker add or adjust a test that fails without the fix, when the code is testable (say so when it isn't); if an
 item is wrong or conflicts with a criterion, don't fix it: say why"; and it ends with "update the `## Decisions`
 section of your final answer for the whole branch". **Before dispatching the fix:** `git -C $WT rev-parse HEAD > $O/round-<n>.sha`.
-Then a new `herdr-verify` (4b) and the **round review** (step 5 with these changes):
+Then a new `orq verify` (4b) and the **round review** (step 5 with these changes):
 - Same reviewer as the round before: `$(cat $O/review-<repo>.pick)`. Only if it is over quota, blocked or fails with
   no verdict → a new `orq pick review` (saved to the same file).
 - Extra attachments: `git -C $WT diff $(cat $O/round-<n>.sha)..HEAD > $O/fix-<n>.diff` → `-i $O/fix-<n>.md -i $O/fix-<n>.diff`
@@ -223,7 +228,7 @@ Then a new `herdr-verify` (4b) and the **round review** (step 5 with these chang
   any regression it introduced, as `[blocker]`/`[suggestion]`. Outside the fix diff, report only a blocker you missed
   before that would break production, and say why it wasn't in the first review". Anything else is a suggestion. A review tool can't answer that: it reviews the whole
 branch again, so you do the matching — a finding is a blocker this round only if it is inside `fix-<n>.diff` or is a
-NOT RESOLVED item of `fix-<n>.md`; one you already decided on (fixed, rejected or downgraded) stays decided. **Maximum: `orq config get policy.max_rounds` rounds** — `orq agent -R` refuses the next one (exit 4) and counts per session, so a renamed prefix doesn't reset it; on exit 4 stop and tell the user, `-F` only with their OK; over it → `orq pick impl
+NOT RESOLVED item of `fix-<n>.md`; one you already decided on (fixed, rejected or downgraded) stays decided. **Maximum: `orq config get policy.max_rounds` rounds** — `orq agent -R` refuses the next one (exit 4) and counts per session, so a renamed prefix doesn't reset it; on exit 4 stop and tell the user. With their OK run `orq rounds <ID> --diagnose` (a cheap independent agent, advisory: read its `RECOMMENDATION` — continue / split / change-implementer / ask-user — and tell the user), then `-F` (refused without a diagnosis newer than the last fix/review; `-F -F` skips that, only if the user says so); over it → `orq pick impl
 --exclude-agent <it> > $O/impl-<repo>.pick` only with the user's OK, or stop and report. Non-blocking suggestions go into the comment; they
 don't become a round.
 
@@ -253,9 +258,9 @@ rules live) commits and writes the PR. Find and cite in the prompt, by path, wha
   Red → `gh run view <id> --log-failed | tail -40`: error from the diff → fix round; error already on the base → create
   a Plane issue (workspace standard) and tell the user. "Ready to merge" only with green checks or an explained failure
   + issue.
-- Move it to **In Review** (finished child tabs close by themselves; close any leftover with
+- Move it to **In Review** (finished child tabs close by themselves; in herdr, close any leftover with
   `herdr tab list | jq -r '.result.tabs[]|select(.label|startswith("<ID> "))|.tab_id' | xargs -rn1 herdr tab close`)
-  and **release the issue**: `herdr-claim -w $WS -r <ID>`. The worktree stays until the merge.
+  and **release the issue**: `orq claim -w $WS -r <ID>`. The worktree stays until the merge.
 - **After the merge** (when the user confirms): run `orq gc -w $WS` and show the list. If this issue's worktree is
   listed as removable, run `orq gc -w $WS --yes`; anything else → ask the user.
 - **Never** push, PR, merge or deploy unless the user asks. Report to the user in 3–5 lines.

package/templates/workspace.CLAUDE.md

@@ -5,18 +5,20 @@ rules — read the repo's own before touching it. This file only holds the map a
 
 ## Orchestration (read by the `/issue` skill)
 - **Workspace:** `{{WORKSPACE}}`
-- **Conductor (herdr):** opened with `herdr-conductor [account] [model] [-r <session-id>]` in a herdr pane, in this folder
-  (instructions in `.orquestra-conductor.md`); the **Group** in the table below is the herdr workspace (`-g`).
-  Tests from the Verification column (jest/vitest) **don't run in the child**: the conductor runs `herdr-verify` (`orq verify`
-  outside herdr; one at a time on the machine); the child does lint + `tsc` (`NODE_OPTIONS=--max-old-space-size=2048`).
-- **Agents:** chosen by `orq-pick` from each developer's `~/.config/orq/config.toml` — nothing about models here.
+- **Conductor:** opened with `orq conductor [account] [model] [-r <session-id>]` in this folder, in any terminal (inside a
+  herdr pane too; `herdr-conductor` still works there). Instructions in `.orquestra-conductor.md`; the **Group** in the
+  table below is the herdr workspace (`-g`) or just a label outside herdr.
+  Tests from the Verification column (jest/vitest) **don't run in the child**: the conductor runs `orq verify`
+  (one at a time on the machine); the child does lint + `tsc` (`NODE_OPTIONS=--max-old-space-size=2048`).
+- **Agents:** chosen by `orq pick` from each developer's `~/.config/orq/config.toml` — nothing about models here.
 
 ## Scope
 - Before dispatching, split big issues into sub-issues or sequential batches (one PR, one implementer each) when they touch
   several unrelated areas, change roughly >400 lines, mix refactor with behavior change, or have independent acceptance
   criteria. Each batch must be testable and reviewable on its own; record the split in Plane before starting.
 - Reviews hitting `policy.max_rounds`, repeated findings or the implementer asking to change scope mean it was too big:
-  stop and split the remainder instead of forcing more rounds.
+  stop and split the remainder instead of forcing more rounds. `orq rounds <ID> --diagnose` asks an independent agent why
+  (advisory); `orq agent -R -F` past `max_rounds` needs that diagnosis (`-F -F` skips it, only on the user's word).
 
 ## Repositories