@azure-id/orc 1.9.0 → 1.9.2

package/mock-run/orc-ultra.md

@@ -1,103 +1,103 @@
-# Mock run — `/orc-ultra`
-
-> The same pipeline as `/orc`, plus an advisor at the start and three judges
-> along the way. It costs the most. Use it when a mistake is expensive.
-
----
-
-## 1. What it does
-
-`/orc-ultra` adds four things to a normal `/orc` run:
-
-| Extra | When | What it is for |
-|---|---|---|
-| **Advisor** | before the analyst | Writes a brief: real risks, other ways to do it, a **security section**, and a **rubric** — the list of things a correct answer must get right here |
-| **Judge (analysis)** | after the analyst | Scores the analysis against that rubric |
-| **Judge (plan)** | after the planner | Same, for the plan |
-| **Judge (implementation)** | after verify | Did we build what was asked, at the quality asked |
-
-It also forces on: deep analysis, code patterns, test authoring, the security
-pass, and a floor on executor models. You do not configure any of that — the
-lane sets it for this run only and never writes it to your settings.
-
----
-
-## 2. The run
-
-Rina is changing how refunds are calculated. Money code.
-
-```
-> /orc-ultra rewrite the refund amount calculation to support partial refunds
-```
-
-### Phase U0 — Advisor (runs once, before anything else)
-
-```
-Dispatching orc-advisor-opus-5-xhigh …
-returned as: claude-opus-5 / xhigh          ✓
-
-ADVISORY BRIEF — partial refunds
-
-Risks in this domain
-  · Rounding. A cent lost per refund is a real bug, not a rounding style.
-  · Double refunds. Retry + no idempotency key = money out twice.
-  · Currency. api/payments/ stores minor units; web/ formats major units.
-
-Security section (always written)
-  · The refund endpoint must re-check ownership. Today it checks the session
-    only — api/refunds/create.ts:31.
-
-RUBRIC — what a correct answer must get right here
-  R1  amounts are integers in minor units end to end
-  R2  a partial refund can never exceed the remaining refundable amount
-  R3  the operation is idempotent per refund request id
-  R4  every branch has a test with a real number in it
-
-OPEN QUESTIONS  (answer together, one round)
-  Q1  Can one order have several partial refunds?      default: yes
-  Q2  Rounding on a split refund — who gets the cent?  default: the last refund
-
-> Q1 yes.  Q2 the customer gets the cent, not us.
-```
-
-### Then the normal pipeline, with gates
-
-```
-Analyst (deep, 3 scouts) → done
-  Judge (gate=analysis): APPROVE with 1 note
-    R2 is not evidenced anywhere in the analysis. Cited section added.
-
-Planner → 6 tasks
-  Judge (gate=plan): REVISE
-    "T3 changes the refund total but has no test task. R4 fails."
-    → planner re-ran once → TDD task added → APPROVE
-
-Build → review → verify → PASSED
-  Judge (gate=implementation): APPROVE
-    R1 ✓ minor units, checked at refunds/calc.ts:18 and web/format.ts:9
-    R2 ✓ test "cannot refund more than remaining" — a real number, 1250
-    R3 ✓ idempotency key on the request row
-    R4 ✓ 9 new tests, all with numbers
-```
-
----
-
-## 3. What to notice
-
-- **The judge can send work back, but only twice.** A REVISE loop is capped at
-  2 rounds. After that it must APPROVE, ESCALATE to you, or stop. It can never
-  argue with itself forever.
-- **A judge never fixes anything.** It reads and it votes. The author fixes.
-- **A judge never re-opens an earlier gate.** The plan judge does not re-argue
-  the analysis.
-- **The rubric came before the work.** That is the trick — the standard is
-  written by someone who has not seen the answer yet.
-- **`ultra_mode` is not a setting.** It exists only inside this command. `/orc`
-  and `/orc-mini` never turn it on.
-
----
-
-## 4. Related
-
-- The normal pipeline: [`/orc`](orc.md)
-- What it will cost first: [`/orc-budget`](orc-budget.md)
+# Mock run — `/orc-ultra`
+
+> The same pipeline as `/orc`, plus an advisor at the start and three judges
+> along the way. It costs the most. Use it when a mistake is expensive.
+
+---
+
+## 1. What it does
+
+`/orc-ultra` adds four things to a normal `/orc` run:
+
+| Extra | When | What it is for |
+|---|---|---|
+| **Advisor** | before the analyst | Writes a brief: real risks, other ways to do it, a **security section**, and a **rubric** — the list of things a correct answer must get right here |
+| **Judge (analysis)** | after the analyst | Scores the analysis against that rubric |
+| **Judge (plan)** | after the planner | Same, for the plan |
+| **Judge (implementation)** | after verify | Did we build what was asked, at the quality asked |
+
+It also forces on: deep analysis, code patterns, test authoring, the security
+pass, and a floor on executor models. You do not configure any of that — the
+lane sets it for this run only and never writes it to your settings.
+
+---
+
+## 2. The run
+
+Rina is changing how refunds are calculated. Money code.
+
+```
+> /orc-ultra rewrite the refund amount calculation to support partial refunds
+```
+
+### Phase U0 — Advisor (runs once, before anything else)
+
+```
+Dispatching orc-advisor-opus-5-xhigh …
+returned as: claude-opus-5-5 / xhigh          ✓
+
+ADVISORY BRIEF — partial refunds
+
+Risks in this domain
+  · Rounding. A cent lost per refund is a real bug, not a rounding style.
+  · Double refunds. Retry + no idempotency key = money out twice.
+  · Currency. api/payments/ stores minor units; web/ formats major units.
+
+Security section (always written)
+  · The refund endpoint must re-check ownership. Today it checks the session
+    only — api/refunds/create.ts:31.
+
+RUBRIC — what a correct answer must get right here
+  R1  amounts are integers in minor units end to end
+  R2  a partial refund can never exceed the remaining refundable amount
+  R3  the operation is idempotent per refund request id
+  R4  every branch has a test with a real number in it
+
+OPEN QUESTIONS  (answer together, one round)
+  Q1  Can one order have several partial refunds?      default: yes
+  Q2  Rounding on a split refund — who gets the cent?  default: the last refund
+
+> Q1 yes.  Q2 the customer gets the cent, not us.
+```
+
+### Then the normal pipeline, with gates
+
+```
+Analyst (deep, 3 scouts) → done
+  Judge (gate=analysis): APPROVE with 1 note
+    R2 is not evidenced anywhere in the analysis. Cited section added.
+
+Planner → 6 tasks
+  Judge (gate=plan): REVISE
+    "T3 changes the refund total but has no test task. R4 fails."
+    → planner re-ran once → TDD task added → APPROVE
+
+Build → review → verify → PASSED
+  Judge (gate=implementation): APPROVE
+    R1 ✓ minor units, checked at refunds/calc.ts:18 and web/format.ts:9
+    R2 ✓ test "cannot refund more than remaining" — a real number, 1250
+    R3 ✓ idempotency key on the request row
+    R4 ✓ 9 new tests, all with numbers
+```
+
+---
+
+## 3. What to notice
+
+- **The judge can send work back, but only twice.** A REVISE loop is capped at
+  2 rounds. After that it must APPROVE, ESCALATE to you, or stop. It can never
+  argue with itself forever.
+- **A judge never fixes anything.** It reads and it votes. The author fixes.
+- **A judge never re-opens an earlier gate.** The plan judge does not re-argue
+  the analysis.
+- **The rubric came before the work.** That is the trick — the standard is
+  written by someone who has not seen the answer yet.
+- **`ultra_mode` is not a setting.** It exists only inside this command. `/orc`
+  and `/orc-mini` never turn it on.
+
+---
+
+## 4. Related
+
+- The normal pipeline: [`/orc`](orc.md)
+- What it will cost first: [`/orc-budget`](orc-budget.md)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@azure-id/orc",
-  "version": "1.9.0",
+  "version": "1.9.2",
   "description": "ORC — an orchestrator skill constellation for Claude Code: intake, planning, scored parallel subagents, code-pattern matching, review, verify, ship, plus a project knowledge-base wiki.",
   "bin": {
     "orc": "bin/cli.js"

package/templates/agents/MODEL-MAPPING.md

@@ -11,8 +11,8 @@ model is pinned in frontmatter, not requested in prose. No agent is multi-role.
 | [30,40)  | orc-executor-sonnet-4-6-med  | claude-sonnet-4-6 | medium |
 | [40,55)  | orc-executor-sonnet-4-6-high | claude-sonnet-4-6 | high |
 | [55,65)  | orc-executor-sonnet-5-high   | claude-sonnet-5   | high |
-| [65,90)  | orc-executor-opus-5-low      | claude-opus-5     | low |
-| [90,100] | orc-executor-opus-5-med      | claude-opus-5     | medium |
+| [65,90)  | orc-executor-opus-5-low      | claude-opus-5-5     | low |
+| [90,100] | orc-executor-opus-5-med      | claude-opus-5-5     | medium |
 
 Score→executor mapping lives in config.md (one canonical 6-band table;
 `rubric_bands` is granularity only, not a preset selector).
@@ -29,45 +29,45 @@ model change, and an agent's model change is always a RENAME.
 
 | Agent | Model | Effort | Role |
 |-------|-------|--------|------|
-| orc-system-analyst-opus-5-high | claude-opus-5 | high | doc analysis |
-| orc-planner-opus-5-med | claude-opus-5 | medium | planning |
-| orc-reviewer-opus-5-med | claude-opus-5 | medium | review |
-| orc-verifier-opus-5-med | claude-opus-5 | medium | verify (+ /orc-verify) |
-| orc-test-author-opus-5-med | claude-opus-5 | medium | test authoring (opt-in Phase 6.5; writes tests, never runs) |
+| orc-system-analyst-opus-5-high | claude-opus-5-5 | high | doc analysis |
+| orc-planner-opus-5-med | claude-opus-5-5 | medium | planning |
+| orc-reviewer-opus-5-med | claude-opus-5-5 | medium | review |
+| orc-verifier-opus-5-med | claude-opus-5-5 | medium | verify (+ /orc-verify) |
+| orc-test-author-opus-5-med | claude-opus-5-5 | medium | test authoring (opt-in Phase 6.5; writes tests, never runs) |
 | orc-analyze-mini-sonnet-5-high | claude-sonnet-5 | high | mini analysis |
 | orc-planner-mini-sonnet-5-high | claude-sonnet-5 | high | mini planning |
 | orc-scout-sonnet-4-6-high | claude-sonnet-4-6 | high | deep-analysis code scout (read-only) |
 | orc-recon-sonnet-4-6-med | claude-sonnet-4-6 | medium | answer ONE repository question with file:line evidence (/orc-quick read-only entries; never edits, never plans) |
-| orc-recon-opus-5-low | claude-opus-5 | low | the same contract for a WIDE or SUBTLE question — a blast radius across areas, a defect with no obvious anchor |
-| orc-context-combiner-opus-5-high | claude-opus-5 | high | combine 2+ related analyses (full lane) |
+| orc-recon-opus-5-low | claude-opus-5-5 | low | the same contract for a WIDE or SUBTLE question — a blast radius across areas, a defect with no obvious anchor |
+| orc-context-combiner-opus-5-high | claude-opus-5-5 | high | combine 2+ related analyses (full lane) |
 | orc-pattern-codifier-sonnet-5-high | claude-sonnet-5 | high | reconcile per-language playbook vs. project files → cached code-pattern (opt-in) |
 | orc-retro-sonnet-5-high | claude-sonnet-5 | high | mine behavior traces → calibration report (/orc-retro; read-only) |
 | orc-wiki-scanner-opus-4-8-high | claude-opus-4-8 | high | scan ONE wiki coverage area → evidence-anchored doc body + crosslink tags (/orc-wiki only; read-only against the project). The DEEP half of the v0.46.0 tier ladder: first scan · STRUCTURAL · wide delta · a new exported symbol |
 | orc-wiki-scanner-sonnet-5-high | claude-sonnet-5 | high | the LIGHT half of the same ladder — an existing doc whose covered files moved by a small, no-new-surface delta. IDENTICAL return contract; it escalates with `needs_context` rather than under-delivering. Never used for a first scan |
-| orc-executor-opus-5-med | claude-opus-5 | medium | the `[90,100]` band in BOTH tables |
-| orc-executor-opus-5-low | claude-opus-5 | low | the default table's `[65,90)`, `opus5_only`'s `[0,90)`, and the forced mini/fast executor |
-| orc-advisor-opus-5-xhigh | claude-opus-5 | xhigh | ultra Phase U0 advisory brief + rubric + clarification questions (read-only; /orc-ultra only) |
-| orc-judge-opus-5-xhigh | claude-opus-5 | xhigh | ultra judgment gates — analysis / plan / implementation (read-only; /orc-ultra only) |
-| orc-learn-writer-opus-5-low | claude-opus-5 | low | deepen ONE feature → learning-docs/<slug>/ (/orc-learn only; git-ignored output) |
+| orc-executor-opus-5-med | claude-opus-5-5 | medium | the `[90,100]` band in BOTH tables |
+| orc-executor-opus-5-low | claude-opus-5-5 | low | the default table's `[65,90)`, `opus5_only`'s `[0,90)`, and the forced mini/fast executor |
+| orc-advisor-opus-5-xhigh | claude-opus-5-5 | xhigh | ultra Phase U0 advisory brief + rubric + clarification questions (read-only; /orc-ultra only) |
+| orc-judge-opus-5-xhigh | claude-opus-5-5 | xhigh | ultra judgment gates — analysis / plan / implementation (read-only; /orc-ultra only) |
+| orc-learn-writer-opus-5-low | claude-opus-5-5 | low | deepen ONE feature → learning-docs/<slug>/ (/orc-learn only; git-ignored output) |
 | orc-claude-writer-opus-4-8-high | claude-opus-4-8 | high | scan repo → write/refresh the local CLAUDE.md (/orc-claude only; zero questions) |
-| orc-challenge-judge-opus-5-high | claude-opus-5 | high | grade ONE finished artifact against a FROZEN goal + template (/orc-challenge only; read-only). It reports findings and can never declare a pass — `orc challenge record` computes that |
-| orc-challenge-advisor-opus-5-med | claude-opus-5 | medium | turn a FAILED verdict into a remediation strategy — root-cause groups, an order with reasons, the decisions that are not defects (/orc-challenge only; read-only, no prose, no diffs) |
-| orc-challenge-reader-opus-5-low | claude-opus-5 | low | the COLD READ: answer questions from ONE artifact with `Read` and nothing else (/orc-challenge only). LOW ON PURPOSE — a harder-thinking reader reasons around the gaps D4 exists to find, so a stronger configuration is a worse instrument |
-| orc-challenge-contrarian-opus-5-high | claude-opus-5 | high | THE COUNCIL (v0.49.1): start from "this has a fatal flaw" and go find it — load-bearing claim, then unhappy path, then second-order (/orc-challenge only; read-only). HIGH IS THE INSTRUMENT: a shallow contrarian returns the three surface complaints the free lint already caught |
-| orc-challenge-outsider-opus-5-low | claude-opus-5 | low | THE COUNCIL: what does this page assume you already know? The TIGHTEST slice in the lane — the artifact and this protocol, `Read` only, no goal, no audience, no template (/orc-challenge only). LOW IS A MEASUREMENT, NOT A COST CHOICE: a harder-thinking outsider reasons its way around an unexplained acronym and reports the document is fine. NOTHING MAY UPGRADE IT |
-| orc-challenge-executor-opus-5-med | claude-opus-5 | medium | THE COUNCIL: can this be started on Monday, and where is the first step? Returns D6/D2 findings plus the literal `monday_morning` list — or the point at which writing it becomes impossible (/orc-challenge only; read-only, `Bash` to CHECK a prerequisite, never to change anything). Not an ORC build executor — it writes nothing |
-| orc-challenge-principles-opus-5-high | claude-opus-5 | high | THE COUNCIL: the ONLY role allowed to say the frozen goal is wrong. Returns `premise` objects — no severity, never in findings[], never near the pass gate — and its report NEVER reaches the judge (/orc-challenge only; read-only). HIGH because rebuilding a problem statement from the ground up is the deepest reasoning in the lane |
-| orc-challenge-expansionist-opus-5-med | claude-opus-5 | medium | THE COUNCIL: the only lens not looking for a defect — what is being undervalued? Returns `opportunity` objects with a first step and a route, never a severity (/orc-challenge only; read-only). MEDIUM because it is pattern work against a concrete artifact, the same class as the advisor |
-| orc-doc-writer-opus-5-med | claude-opus-5 | medium | write ONE part file of a long document from a slice of sections (/orc-doc only). It writes to `.work/<id>.md` and NEVER opens document.md — that is what makes parallel writing safe here |
-| orc-doc-checker-opus-5-low | claude-opus-5 | low | read ONE LINE RANGE of a document and report anchored findings (/orc-doc only; read-only). LOW ON PURPOSE — the same reasoning that pins the challenge cold reader: a harder-thinking checker reasons its way past a gap a real reader would trip on |
-| orc-test-designer-opus-5-high | claude-opus-5 | high | fill the GAPS the free case matrix could not derive, and author the front-end journey SCRIPT (/orc-test only). HIGH IS THE INSTRUMENT: a shallow designer returns the three obvious cases the deterministic expansion already covered, which is the one output that costs money and adds nothing |
-| orc-test-interpreter-opus-5-low | claude-opus-5 | low | read ONLY a run’s evidence files and say whether what is in them is a finding (/orc-test only; SEALED slice, `Read` and nothing else). LOW IS A MEASUREMENT CHOICE, NOT A COST ONE, and nothing may ever upgrade it: a harder-thinking interpreter reasons its way to why a leaked stack trace is probably fine in staging |
+| orc-challenge-judge-opus-5-high | claude-opus-5-5 | high | grade ONE finished artifact against a FROZEN goal + template (/orc-challenge only; read-only). It reports findings and can never declare a pass — `orc challenge record` computes that |
+| orc-challenge-advisor-opus-5-med | claude-opus-5-5 | medium | turn a FAILED verdict into a remediation strategy — root-cause groups, an order with reasons, the decisions that are not defects (/orc-challenge only; read-only, no prose, no diffs) |
+| orc-challenge-reader-opus-5-low | claude-opus-5-5 | low | the COLD READ: answer questions from ONE artifact with `Read` and nothing else (/orc-challenge only). LOW ON PURPOSE — a harder-thinking reader reasons around the gaps D4 exists to find, so a stronger configuration is a worse instrument |
+| orc-challenge-contrarian-opus-5-high | claude-opus-5-5 | high | THE COUNCIL (v0.49.1): start from "this has a fatal flaw" and go find it — load-bearing claim, then unhappy path, then second-order (/orc-challenge only; read-only). HIGH IS THE INSTRUMENT: a shallow contrarian returns the three surface complaints the free lint already caught |
+| orc-challenge-outsider-opus-5-low | claude-opus-5-5 | low | THE COUNCIL: what does this page assume you already know? The TIGHTEST slice in the lane — the artifact and this protocol, `Read` only, no goal, no audience, no template (/orc-challenge only). LOW IS A MEASUREMENT, NOT A COST CHOICE: a harder-thinking outsider reasons its way around an unexplained acronym and reports the document is fine. NOTHING MAY UPGRADE IT |
+| orc-challenge-executor-opus-5-med | claude-opus-5-5 | medium | THE COUNCIL: can this be started on Monday, and where is the first step? Returns D6/D2 findings plus the literal `monday_morning` list — or the point at which writing it becomes impossible (/orc-challenge only; read-only, `Bash` to CHECK a prerequisite, never to change anything). Not an ORC build executor — it writes nothing |
+| orc-challenge-principles-opus-5-high | claude-opus-5-5 | high | THE COUNCIL: the ONLY role allowed to say the frozen goal is wrong. Returns `premise` objects — no severity, never in findings[], never near the pass gate — and its report NEVER reaches the judge (/orc-challenge only; read-only). HIGH because rebuilding a problem statement from the ground up is the deepest reasoning in the lane |
+| orc-challenge-expansionist-opus-5-med | claude-opus-5-5 | medium | THE COUNCIL: the only lens not looking for a defect — what is being undervalued? Returns `opportunity` objects with a first step and a route, never a severity (/orc-challenge only; read-only). MEDIUM because it is pattern work against a concrete artifact, the same class as the advisor |
+| orc-doc-writer-opus-5-med | claude-opus-5-5 | medium | write ONE part file of a long document from a slice of sections (/orc-doc only). It writes to `.work/<id>.md` and NEVER opens document.md — that is what makes parallel writing safe here |
+| orc-doc-checker-opus-5-low | claude-opus-5-5 | low | read ONE LINE RANGE of a document and report anchored findings (/orc-doc only; read-only). LOW ON PURPOSE — the same reasoning that pins the challenge cold reader: a harder-thinking checker reasons its way past a gap a real reader would trip on |
+| orc-test-designer-opus-5-high | claude-opus-5-5 | high | fill the GAPS the free case matrix could not derive, and author the front-end journey SCRIPT (/orc-test only). HIGH IS THE INSTRUMENT: a shallow designer returns the three obvious cases the deterministic expansion already covered, which is the one output that costs money and adds nothing |
+| orc-test-interpreter-opus-5-low | claude-opus-5-5 | low | read ONLY a run’s evidence files and say whether what is in them is a finding (/orc-test only; SEALED slice, `Read` and nothing else). LOW IS A MEASUREMENT CHOICE, NOT A COST ONE, and nothing may ever upgrade it: a harder-thinking interpreter reasons its way to why a leaked stack trace is probably fine in staging |
 | orc-trace-writer-haiku-4-5 | claude-haiku-4-5 | — (no ladder) | append one phase block of behavior-trace narration from an orchestrator packet (every trace-owning lane; append-only, never reads source) |
 | orc-graph-noter-sonnet-4-6-med | claude-sonnet-4-6 | medium | write ONE sentence per changed function for the local code graph (`orc graph` Layer 2). Reads line RANGES only, pipes its notes to `orc graph notes apply -` (the CLI validates and stores), returns ONE line. Dispatched by code-changing lanes only when `code_graph_notes` is on and a batch reaches its minimum |
 
 ## Opus-5-only mode agents (hard-gated; dispatched only when `opus5_only: true`)
 
-`opus5_only` FORCES every dispatched role onto `claude-opus-5`, with effort as
+`opus5_only` FORCES every dispatched role onto `claude-opus-5-5`, with effort as
 the only cost dial. Each agent below replaces its default with the same slice
 and the same return contract. Effort is PINNED per role — no CLI rewrites
 these. Full mapping + precedence:
@@ -75,24 +75,24 @@ these. Full mapping + precedence:
 
 | Agent | Model | Effort | Replaces |
 |-------|-------|--------|----------|
-| orc-executor-opus-5-low | claude-opus-5 | low | the `[0,90)` band · orc-mini's and orc-fast's fixed executor |
-| orc-executor-opus-5-med | claude-opus-5 | medium | the `[90,100]` band |
-| orc-analyze-mini-opus-5-med | claude-opus-5 | medium | orc-analyze-mini-sonnet-5-high |
-| orc-planner-mini-opus-5-med | claude-opus-5 | medium | orc-planner-mini-sonnet-5-high |
-| orc-scout-opus-5-low | claude-opus-5 | low | orc-scout-sonnet-4-6-high |
-| orc-pattern-codifier-opus-5-med | claude-opus-5 | medium | orc-pattern-codifier-sonnet-5-high |
-| orc-wiki-scanner-opus-5-med | claude-opus-5 | medium | orc-wiki-scanner-opus-4-8-high |
-| orc-claude-writer-opus-5-med | claude-opus-5 | medium | orc-claude-writer-opus-4-8-high |
-| orc-retro-opus-5-med | claude-opus-5 | medium | orc-retro-sonnet-5-high |
-
-The nine roles already on `claude-opus-5` — analyst, planner, reviewer,
+| orc-executor-opus-5-low | claude-opus-5-5 | low | the `[0,90)` band · orc-mini's and orc-fast's fixed executor |
+| orc-executor-opus-5-med | claude-opus-5-5 | medium | the `[90,100]` band |
+| orc-analyze-mini-opus-5-med | claude-opus-5-5 | medium | orc-analyze-mini-sonnet-5-high |
+| orc-planner-mini-opus-5-med | claude-opus-5-5 | medium | orc-planner-mini-sonnet-5-high |
+| orc-scout-opus-5-low | claude-opus-5-5 | low | orc-scout-sonnet-4-6-high |
+| orc-pattern-codifier-opus-5-med | claude-opus-5-5 | medium | orc-pattern-codifier-sonnet-5-high |
+| orc-wiki-scanner-opus-5-med | claude-opus-5-5 | medium | orc-wiki-scanner-opus-4-8-high |
+| orc-claude-writer-opus-5-med | claude-opus-5-5 | medium | orc-claude-writer-opus-4-8-high |
+| orc-retro-opus-5-med | claude-opus-5-5 | medium | orc-retro-sonnet-5-high |
+
+The nine roles already on `claude-opus-5-5` — analyst, planner, reviewer,
 verifier, test-author, combiner, learn-writer, advisor, judge — dispatch
 unchanged under this mode. **Never forced:** `orc-trace-writer-haiku-4-5` (it
 transcribes a packet, no reasoning) and orc-diy (its table is compile-owned).
-**Not dispatched at all:** `orc-graph-noter-sonnet-4-6-med` has NO Opus 5
+**Not dispatched at all:** `orc-graph-noter-sonnet-4-6-med` has NO Opus 5.5
 variant. Under this mode a lane skips graph notes and prints
 `graph notes: skipped (opus5_only)` — a one-sentence summary does not justify an
-Opus 5 dispatch, and the graph's structure layer costs no model at all.
+Opus 5.5 dispatch, and the graph's structure layer costs no model at all.
 
 Mini execution reuses orc-executor-sonnet-5-high. Fast-lane (orc-fast)
 execution reuses orc-executor-sonnet-4-6-high — no dedicated agent. Under
@@ -141,11 +141,11 @@ The orchestrator (main session) is NOT an agent file.
 Model IDs use the Platform/API dateless format (confirmed at
 platform.claude.com/docs/en/about-claude/models/model-ids-and-versions):
 claude-haiku-4-5, claude-sonnet-4-6, claude-sonnet-5, claude-opus-4-7,
-claude-opus-4-8 and claude-opus-5 (the top executor band + the core fixed
+claude-opus-4-8 and claude-opus-5-5 (the top executor band + the core fixed
 roles).
 
 1. **Run `/agents`** to confirm Claude Code accepts these full IDs in agent
-   frontmatter — in particular `claude-haiku-4-5` and `claude-opus-5`. If it
+   frontmatter — in particular `claude-haiku-4-5` and `claude-opus-5-5`. If it
    wants short aliases (opus/sonnet/haiku) or dated IDs, adjust
    each `model:` field. The full IDs are valid at the API level but Claude Code
    may normalize differently.
@@ -160,7 +160,7 @@ and it silently falls back to the main model. **Run your main Claude Code
 session on Opus** or every opus-* agent downgrades to Sonnet. As of v0.34.0 the
 [90,100] executor band AND every core fixed role (analyst, planner, reviewer,
 verifier, test author, combiner, learn writer, ultra advisor/judge) are pinned
-to **claude-opus-5** — on an Opus 4.8 session they all land on Opus 4.8. Verify by
+to **claude-opus-5-5** — on an Opus 4.8 session they all land on Opus 4.8. Verify by
 expanding a subagent's tool-call in the transcript to see the model it ran.
 
 ## How dispatch works

package/templates/agents/orc-advisor-opus-5-xhigh.md

@@ -1,56 +1,56 @@
----
-name: orc-advisor-opus-5-xhigh
-description: >
-  ORC Advisor — claude-opus-5, xhigh effort. Ultra lane only. Single-role:
-  pre-analysis advisory. Turns the user's request + read-only repo access into
-  an advisory brief: domain risks, architectural pitfalls, alternatives, a
-  mandatory security-risk section, and a request-specific RUBRIC of what a
-  correct analysis, plan, and implementation must each get right — plus
-  open_questions[] (every ambiguity, each with a proposed default). Dispatched
-  once by the orchestrator at ultra Phase U0, before the analyst.
-model: claude-opus-5
-effort: xhigh
-tools: Read, Glob, Grep, Bash
----
-
-You are the ORC Advisor (Opus 5, xhigh). Your only job is producing the
-advisory brief that sharpens every downstream role on an ultra run. You do NOT
-analyze the document, plan tasks, implement, or judge. You are READ-ONLY on the
-project: you never edit code, and you never spawn subagents.
-
-## What you produce (the advisory brief)
-
-Write `advisory-brief.md` into the run-folder path the orchestrator gives you.
-Ground every claim in the actual codebase (Read/Glob/Grep) — never the request
-text alone. Sections, all mandatory:
-
-1. **Domain risks & architectural pitfalls** — specific to THIS request and
-   THIS codebase, each with a `file:line — "verbatim snippet"` anchor where the
-   code is the source, or an explicit `ASSUMPTION` tag where it is not.
-2. **Alternatives considered** — options + trade-offs + a one-line
-   recommendation each. Rejected options say why.
-3. **Security risks (mandatory, never empty-by-default)** — attack surface of
-   the request, data/trust boundaries touched, request-specific pitfalls. If
-   you judge the request has NO security surface, say so explicitly with the
-   reasoning — silence is not an option.
-4. **Rubric** — three checklists the judges will score against: what a correct
-   ANALYSIS must get right, what a correct PLAN must get right, what a faithful
-   IMPLEMENTATION must get right. Concrete and request-specific — a rubric line
-   that could apply to any project is a bad line.
-5. **Open questions** — every ambiguity in the request, each as
-   `{question, proposed_default, why_it_matters}`. The orchestrator relays
-   these to the user in ONE batch; unanswered ones fall back to your default
-   and enter the assumption ledger as UNCONFIRMED.
-6. **Assumptions** — seed entries for the run's assumption ledger:
-   `assumption → confirmed-by-code-evidence (anchor) | UNCONFIRMED`.
-
-## Return
-brief_path, open_questions[] (mirrored from the brief so the orchestrator can
-relay without re-parsing), assumptions[] (the seed ledger entries),
-actual_model (quoted verbatim from your system prompt's "The exact model ID
-is …" line; `unknown` if absent, never guessed), actual_effort
-($CLAUDE_EFFORT via Bash).
-
-The orchestrator injects your brief verbatim into the analyst, planner, judge,
-and executor slices. You run ONCE per ultra run; you are never re-dispatched
-for revisions (the judges own quality from here).
+---
+name: orc-advisor-opus-5-xhigh
+description: >
+  ORC Advisor — claude-opus-5-5, xhigh effort. Ultra lane only. Single-role:
+  pre-analysis advisory. Turns the user's request + read-only repo access into
+  an advisory brief: domain risks, architectural pitfalls, alternatives, a
+  mandatory security-risk section, and a request-specific RUBRIC of what a
+  correct analysis, plan, and implementation must each get right — plus
+  open_questions[] (every ambiguity, each with a proposed default). Dispatched
+  once by the orchestrator at ultra Phase U0, before the analyst.
+model: claude-opus-5-5
+effort: xhigh
+tools: Read, Glob, Grep, Bash
+---
+
+You are the ORC Advisor (Opus 5.5, xhigh). Your only job is producing the
+advisory brief that sharpens every downstream role on an ultra run. You do NOT
+analyze the document, plan tasks, implement, or judge. You are READ-ONLY on the
+project: you never edit code, and you never spawn subagents.
+
+## What you produce (the advisory brief)
+
+Write `advisory-brief.md` into the run-folder path the orchestrator gives you.
+Ground every claim in the actual codebase (Read/Glob/Grep) — never the request
+text alone. Sections, all mandatory:
+
+1. **Domain risks & architectural pitfalls** — specific to THIS request and
+   THIS codebase, each with a `file:line — "verbatim snippet"` anchor where the
+   code is the source, or an explicit `ASSUMPTION` tag where it is not.
+2. **Alternatives considered** — options + trade-offs + a one-line
+   recommendation each. Rejected options say why.
+3. **Security risks (mandatory, never empty-by-default)** — attack surface of
+   the request, data/trust boundaries touched, request-specific pitfalls. If
+   you judge the request has NO security surface, say so explicitly with the
+   reasoning — silence is not an option.
+4. **Rubric** — three checklists the judges will score against: what a correct
+   ANALYSIS must get right, what a correct PLAN must get right, what a faithful
+   IMPLEMENTATION must get right. Concrete and request-specific — a rubric line
+   that could apply to any project is a bad line.
+5. **Open questions** — every ambiguity in the request, each as
+   `{question, proposed_default, why_it_matters}`. The orchestrator relays
+   these to the user in ONE batch; unanswered ones fall back to your default
+   and enter the assumption ledger as UNCONFIRMED.
+6. **Assumptions** — seed entries for the run's assumption ledger:
+   `assumption → confirmed-by-code-evidence (anchor) | UNCONFIRMED`.
+
+## Return
+brief_path, open_questions[] (mirrored from the brief so the orchestrator can
+relay without re-parsing), assumptions[] (the seed ledger entries),
+actual_model (quoted verbatim from your system prompt's "The exact model ID
+is …" line; `unknown` if absent, never guessed), actual_effort
+($CLAUDE_EFFORT via Bash).
+
+The orchestrator injects your brief verbatim into the analyst, planner, judge,
+and executor slices. You run ONCE per ultra run; you are never re-dispatched
+for revisions (the judges own quality from here).

package/templates/agents/orc-analyze-mini-opus-5-med.md

@@ -1,60 +1,60 @@
----
-name: orc-analyze-mini-opus-5-med
-description: >
-  ORC mini System Analyst — Opus-5-only mode variant. claude-opus-5, medium
-  effort. Fast-lane requirement analysis for ORC-MINI. Same artifacts/contract as
-  orc-analyze-mini-sonnet-5-high, trimmed depth. Doc-optional + evidence-or-mark
-  + recommended-option questions, but always single-pass — NO deep mode, NO
-  scouts. Dispatched INSTEAD of orc-analyze-mini-sonnet-5-high when
-  `opus5_only: true`.
-model: claude-opus-5
-effort: medium
-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch
----
-
-You are the ORC mini System Analyst (Opus 5, medium). Same job as the full
-analyst, shallower and always single-pass. Detect+confirm mode (prose / audit /
-requirement — the last has NO doc, the user's request is the source of truth).
-Bound to scope: the deliverable stays X (Y/Z never become tasks), but when an
-in-scope item clearly DEPENDS on an adjacent scope, gather that touchpoint as
-anchored, non-actionable context (self-read, touchpoint-bounded, NO scouts) —
-each item anchored to the requirement it serves + labeled "do not build";
-unanchored context is dropped.
-
-**Coverage floor (same as the full analyst — trimmed depth never means a lower
-floor):** you MUST verify (a) every row that emits a `files[]` entry and
-(b) every `status: exists|conflict` claim. Peripheral references may stay
-tagged instead of exhaustively traced.
-
-**Evidence-or-mark, quote-anchored:** every code claim or interpretation
-carries `file:line — "verbatim snippet"` (a ref with no quote auto-downgrades
-to UNVERIFIED), OR gets an `ASSUMPTION`/`UNVERIFIED` tag and becomes a
-question — never a silent guess. **Absence claims** (missing/buildable) carry
-`searched:` — the concrete globs/greps run. The orchestrator spot-checks your
-evidence on return and bounces misses.
-
-**Challenges are recommended-option sets** (2–3 choices, one flagged
-recommended + reason), TRIAGED: blocking (scope changes, code-vs-doc conflicts,
-anything changing files[] or a status) one at a time; everything else demoted
-to ONE batched advisory round — recorded in the report, never silently dropped.
-
-You do NOT run deep mode or scouts. **Escalation thresholds** (recommend the
-full Opus 5 analyst `/orc-analyze` and let the user choose): source doc > ~10
-pages, OR > 12 in-scope requirements, OR > 3 conflict rows, OR audit mode with
-> 5 stale-premise rows.
-
-Write report.md (mode template) + derived requirement-spec.md into
-orc/analyzer/{name}/ — spec derived only AFTER the user confirms the report,
-stamped with `git_head` (git rev-parse HEAD) + `dirty` — including the Evidence
-column, the Assumptions & Open Questions section, and the **Additional context
-(do not build)** section when any survived. **Return the STRUCTURED fields
-FIRST, prose last** — an analyst return has been observed arriving TRUNCATED, so
-leading with the fields costs prose instead of the verdicts (and an early
-actual_model is what lets the trace hook attach `model=` to the RETURN line):
-mode + scope, then actual_model (quoted verbatim from your system prompt's "The
-exact model ID is …" line; `unknown` if absent, never guessed) + actual_effort
-($CLAUDE_EFFORT), then handoff_ready (a CHECKLIST — true only when: all blocking
-challenges resolved, zero open UNVERIFIED on in-scope items, every requirement
-has status + evidence-or-resolution, spec derived after confirmation,
-scope_closed: true written) + report_path + spec_path, then everything else.
-Never build or spawn.
+---
+name: orc-analyze-mini-opus-5-med
+description: >
+  ORC mini System Analyst — Opus-5-only mode variant. claude-opus-5-5, medium
+  effort. Fast-lane requirement analysis for ORC-MINI. Same artifacts/contract as
+  orc-analyze-mini-sonnet-5-high, trimmed depth. Doc-optional + evidence-or-mark
+  + recommended-option questions, but always single-pass — NO deep mode, NO
+  scouts. Dispatched INSTEAD of orc-analyze-mini-sonnet-5-high when
+  `opus5_only: true`.
+model: claude-opus-5-5
+effort: medium
+tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch
+---
+
+You are the ORC mini System Analyst (Opus 5.5, medium). Same job as the full
+analyst, shallower and always single-pass. Detect+confirm mode (prose / audit /
+requirement — the last has NO doc, the user's request is the source of truth).
+Bound to scope: the deliverable stays X (Y/Z never become tasks), but when an
+in-scope item clearly DEPENDS on an adjacent scope, gather that touchpoint as
+anchored, non-actionable context (self-read, touchpoint-bounded, NO scouts) —
+each item anchored to the requirement it serves + labeled "do not build";
+unanchored context is dropped.
+
+**Coverage floor (same as the full analyst — trimmed depth never means a lower
+floor):** you MUST verify (a) every row that emits a `files[]` entry and
+(b) every `status: exists|conflict` claim. Peripheral references may stay
+tagged instead of exhaustively traced.
+
+**Evidence-or-mark, quote-anchored:** every code claim or interpretation
+carries `file:line — "verbatim snippet"` (a ref with no quote auto-downgrades
+to UNVERIFIED), OR gets an `ASSUMPTION`/`UNVERIFIED` tag and becomes a
+question — never a silent guess. **Absence claims** (missing/buildable) carry
+`searched:` — the concrete globs/greps run. The orchestrator spot-checks your
+evidence on return and bounces misses.
+
+**Challenges are recommended-option sets** (2–3 choices, one flagged
+recommended + reason), TRIAGED: blocking (scope changes, code-vs-doc conflicts,
+anything changing files[] or a status) one at a time; everything else demoted
+to ONE batched advisory round — recorded in the report, never silently dropped.
+
+You do NOT run deep mode or scouts. **Escalation thresholds** (recommend the
+full Opus 5.5 analyst `/orc-analyze` and let the user choose): source doc > ~10
+pages, OR > 12 in-scope requirements, OR > 3 conflict rows, OR audit mode with
+> 5 stale-premise rows.
+
+Write report.md (mode template) + derived requirement-spec.md into
+orc/analyzer/{name}/ — spec derived only AFTER the user confirms the report,
+stamped with `git_head` (git rev-parse HEAD) + `dirty` — including the Evidence
+column, the Assumptions & Open Questions section, and the **Additional context
+(do not build)** section when any survived. **Return the STRUCTURED fields
+FIRST, prose last** — an analyst return has been observed arriving TRUNCATED, so
+leading with the fields costs prose instead of the verdicts (and an early
+actual_model is what lets the trace hook attach `model=` to the RETURN line):
+mode + scope, then actual_model (quoted verbatim from your system prompt's "The
+exact model ID is …" line; `unknown` if absent, never guessed) + actual_effort
+($CLAUDE_EFFORT), then handoff_ready (a CHECKLIST — true only when: all blocking
+challenges resolved, zero open UNVERIFIED on in-scope items, every requirement
+has status + evidence-or-resolution, spec derived after confirmation,
+scope_closed: true written) + report_path + spec_path, then everything else.
+Never build or spawn.