@azure-id/orc 2.1.0 → 2.2.0

package/templates/skills/orc-pr-driver/references/orc-run-split.md

@@ -1,99 +1,108 @@
-# Reference — splitting an already-built worktree (entry mode `orc-run`)
-
-Loaded at Phase D1/D2 when the change ALREADY exists — the normal case when
-ORC's ship phase hands the stack over. The code is written; the job is to
-distribute it across layer branches **without losing a byte and without hunk
-surgery**.
-
-## Invariants
-
-- **File-granular only.** Every changed path belongs to exactly ONE layer. A file
-  whose content seems to belong in two layers is an UNCERTAIN → ask; the default
-  option offered is "the whole file lands in the LOWEST layer that needs it".
-- **The snapshot exists before any branch switch.** The user's work is never held
-  only by the worktree once branch surgery starts.
-- **Nothing is lost:** after the last layer, the union of the layers' files must
-  equal the snapshot's changed-file set, exactly. That equality is a GATE.
-
-## Step 1 — snapshot the change
-
-```bash
-git status --short > /tmp/orc-stack-surface.txt   # the authoritative surface list
-git checkout -b orc-stack-snapshot/<slug>         # keeps the worktree as-is
-git add -A                                        # tracked + untracked
-git commit -m "<TICKET> snapshot: pre-stack state (temporary, not for review)"
-SNAPSHOT=$(git rev-parse HEAD)
-```
-
-Then **verify the snapshot is complete** before going further:
-
-```bash
-git diff --name-status <trunk>..$SNAPSHOT          # must cover every path in the surface list
-```
-
-Any path in `git status --short` that is missing from that diff → **STOP**. Do not
-proceed with a partial snapshot.
-
-Note the excluded-but-listed paths (generated code, lockfiles, vendored trees —
-`../../_shared/stack-plan.md`): they are still real files that must land in some
-layer, they just do not count toward a budget.
-
-## Step 2 — start the stack from the trunk
-
-```bash
-git checkout <trunk> && git pull --ff-only
-gh stack init -b <trunk>
-```
-
-The worktree now shows trunk state. The change is safe in `$SNAPSHOT`.
-
-## Step 3 — materialize each layer, bottom-up
-
-Per layer, from the plan's explicit file list:
-
-```bash
-gh stack add -m "<TICKET> <layer title>" <layer-branch>
-
-# additions + modifications for THIS layer only
-git checkout $SNAPSHOT -- <file> <file> ...
-
-# deletions this layer owns (checkout cannot delete)
-git rm <deleted-file> ...
-
-git status --short          # sanity: nothing from another layer
-```
-
-Then run the full green-gate ladder (`green-gate.md`) and commit through the
-repo's hooks. Never `--no-verify`.
-
-**A moved/renamed file** is one unit: its delete and its add land in the SAME
-layer, always.
-
-## Step 4 — completeness gate (before `gh stack submit`)
-
-```bash
-git diff --name-only <trunk>..<top layer branch> | sort > /tmp/stacked.txt
-git diff --name-only <trunk>..$SNAPSHOT          | sort > /tmp/snapshot.txt
-diff /tmp/stacked.txt /tmp/snapshot.txt          # MUST be empty
-```
-
-Non-empty → a file was dropped or duplicated. Fix it before submitting: an
-unreviewed missing file is exactly the failure stacking is supposed to prevent.
-
-## Step 5 — the snapshot branch stays
-
-Keep `orc-stack-snapshot/<slug>` until the last layer merges — it is the undo
-button, and it is also how you re-cut a seam without re-deriving the change. It
-is **never pushed** and never becomes a PR. Delete it (after asking) when the
-stack is fully merged.
-
-## When the change is already committed on a feature branch
-
-Same procedure with `$SNAPSHOT` = that branch's tip; skip the `add`/`commit`.
-Leave the original branch untouched — it is the snapshot.
-
-## What this reference does NOT do
-
-- No hunk splitting, no interactive `git add -p`, no manual patch editing.
-- No retrofitting an already-open PR into a stack (`gh stack link`) — out of
-  scope; ship it as one regular PR instead.
+# Reference — splitting an already-built worktree (entry mode `orc-run`)
+
+Loaded at Phase D1/D2 when the change ALREADY exists — the normal case when
+ORC's ship phase hands the stack over. The code is written; the job is to
+distribute it across layer branches **without losing a byte and without hunk
+surgery**.
+
+## Invariants
+
+- **File-granular only.** Every changed path belongs to exactly ONE layer. A file
+  whose content seems to belong in two layers is an UNCERTAIN → ask; the default
+  option offered is "the whole file lands in the LOWEST layer that needs it".
+- **The snapshot exists before any branch switch.** The user's work is never held
+  only by the worktree once branch surgery starts.
+- **Nothing is lost:** after the last layer, the union of the layers' files must
+  equal the snapshot's changed-file set, exactly. That equality is a GATE.
+
+## Step 1 — snapshot the change
+
+```bash
+git status --short > /tmp/orc-stack-surface.txt   # the authoritative surface list
+git checkout -b orc-stack-snapshot/<slug>         # keeps the worktree as-is
+git add -A                                        # tracked + untracked
+git commit -m "<TICKET> snapshot: pre-stack state (temporary, not for review)"
+SNAPSHOT=$(git rev-parse HEAD)
+```
+
+Then **verify the snapshot is complete** before going further:
+
+```bash
+git diff --name-status <trunk>..$SNAPSHOT          # must cover every path in the surface list
+```
+
+Any path in `git status --short` that is missing from that diff → **STOP**. Do not
+proceed with a partial snapshot.
+
+Note the excluded-but-listed paths (generated code, lockfiles, vendored trees —
+`../../_shared/stack-plan.md`): they are still real files that must land in some
+layer, they just do not count toward a budget.
+
+## Step 2 — start the stack from the trunk
+
+```bash
+git checkout <trunk>
+git merge-base --is-ancestor <trunk> $SNAPSHOT   # exit 1 → STOP (below)
+gh stack init -b <trunk>
+```
+
+The worktree now shows trunk state. The change is safe in `$SNAPSHOT`.
+
+**Do not pull here.** The stack starts from the trunk commit the change was cut
+from, so `git checkout $SNAPSHOT -- <file>` reproduces exactly the change and
+Step 4 compares like with like. The trunk is not an ancestor of `$SNAPSHOT`
+(it moved after the change was cut) → **STOP** and ask: rebase the snapshot
+first (`git rebase <trunk> orc-stack-snapshot/<slug>`), or stop. A remote trunk
+that moved ahead is `gh stack sync` after submit (`conflict-playbook.md`, "the
+trunk moved") — never a pull in the middle of a split.
+
+## Step 3 — materialize each layer, bottom-up
+
+Per layer, from the plan's explicit file list:
+
+```bash
+gh stack add -m "<TICKET> <layer title>" <layer-branch>
+
+# additions + modifications for THIS layer only
+git checkout $SNAPSHOT -- <file> <file> ...
+
+# deletions this layer owns (checkout cannot delete)
+git rm <deleted-file> ...
+
+git status --short          # sanity: nothing from another layer
+```
+
+Then run the full green-gate ladder (`green-gate.md`) and commit through the
+repo's hooks. Never `--no-verify`.
+
+**A moved/renamed file** is one unit: its delete and its add land in the SAME
+layer, always.
+
+## Step 4 — completeness gate (before `gh stack submit`)
+
+```bash
+git diff --name-only <trunk>..<top layer branch> | sort > /tmp/stacked.txt
+git diff --name-only <trunk>..$SNAPSHOT          | sort > /tmp/snapshot.txt
+diff /tmp/stacked.txt /tmp/snapshot.txt          # MUST be empty
+```
+
+Non-empty → a file was dropped or duplicated. Fix it before submitting: an
+unreviewed missing file is exactly the failure stacking is supposed to prevent.
+
+## Step 5 — the snapshot branch stays
+
+Keep `orc-stack-snapshot/<slug>` until the last layer merges — it is the undo
+button, and it is also how you re-cut a seam without re-deriving the change. It
+is **never pushed** and never becomes a PR. Delete it (after asking) when the
+stack is fully merged.
+
+## When the change is already committed on a feature branch
+
+Same procedure with `$SNAPSHOT` = that branch's tip; skip the `add`/`commit`.
+Leave the original branch untouched — it is the snapshot.
+
+## What this reference does NOT do
+
+- No hunk splitting, no interactive `git add -p`, no manual patch editing.
+- No retrofitting an already-open PR into a stack (`gh stack link`) — out of
+  scope; ship it as one regular PR instead.

package/templates/skills/orc-pr-setup/SKILL.md

@@ -186,8 +186,8 @@ in the SAME step. A phase that ends with `zero new trace lines is a protocol vio
 
 ## Lane contract (`../_shared/lane-contract.md` — read it ONLY when a call exits ≠ 0)
 
-- **Calls:** `orc lane calls orc-pr-setup --json` names every call and its exit codes.
-  **An exit code is an ANSWER where it says so, not a failure.** Make no other call.
+- **Calls:** `orc lane calls orc-pr-setup --json` names shared calls and exit codes.
+  **An exit code is an ANSWER where it says so, not a failure.** Own calls are here; make no other.
 - **Config:** `orc lane config orc-pr-setup --json`. Obey `effective`. Never merge
   `.claude/orc.config.yaml` yourself (`../_shared/config-precedence.md`). Nothing
   here is contested, gated or a stop: no preflight line, no gate to honour.

package/templates/skills/orc-quick/README.md

@@ -113,22 +113,21 @@ Now the **one** user turn — questions and the agent choice together:
      Z  delete now — breaks clients still sending `a`
 
 Which executor?
-  1. orc-executor-sonnet-4-6-med    3 files, mechanical
+  1. orc-executor-sonnet-5-med    3 files, mechanical
   2. orc-executor-opus-5-low        thinks harder, ~3× cost
 ```
 
 > **You:** `1: Y, 2: Y, executor 1`
 
 ```
-dispatching orc-executor-sonnet-4-6-med…
-✅ returned · 3 files · expect=sonnet-4-6/medium actual=sonnet-4-6/medium
+dispatching orc-executor-sonnet-5-med…
+✅ returned · 3 files · expect=sonnet-5-5/medium actual=sonnet-5-5/medium
 
 build          npm run build → GREEN
 tests reached  1 file (call 1) → 4 passed
 suite          41 passed
 blast radius   2 symbols · callers 3 in 2 files · tests reach 2 · risk none
-graph          gen 43 · 2 files updated
-graph gain     paid 1.2K tokens · avoided an estimated 3–9K · measured: not yet (N=1)
+graph pack     2 files · 3 ranges quoted
 
 (test-update not offered — the executor already fixed the spec)
 
@@ -204,7 +203,7 @@ this needs more reading than I should do myself, so it wants a dispatch.
 
 Entry 2 is a context dig. Which agent should look?
 
-  1. orc-recon-sonnet-4-6-med     finding things, not deciding      → suggested
+  1. orc-recon-sonnet-5-med     finding things, not deciding      → suggested
   2. orc-recon-opus-5-low         a wide or subtle question
   3. other — name a model (effort follows your session; not traced by the hook)
 
@@ -271,7 +270,7 @@ of you:
 ```
 kind: defect — the fix will be shown red first.
 
-dispatching orc-executor-sonnet-4-6-med…
+dispatching orc-executor-sonnet-5-med…
 ✅ returned · 2 files
 
 repro red     npm test -- tests/orders.search.test.js   exit 1
@@ -349,12 +348,12 @@ There is **no smoke gate** in this lane. Two simple rules instead.
 build   tsc → ❌ RED (14 errors)
 starting repair — rounds 1–2 reuse this executor.
 
-repair 1/3 · orc-executor-sonnet-4-6-med    RED (6 errors)
-repair 2/3 · orc-executor-sonnet-4-6-med    RED (4 errors)
+repair 1/3 · orc-executor-sonnet-5-med    RED (6 errors)
+repair 2/3 · orc-executor-sonnet-5-med    RED (4 errors)
 
 2 rounds in, still red. The rest is type-level, not mechanical.
 Round 3 — which executor?
-  1. orc-executor-sonnet-4-6-med    current
+  1. orc-executor-sonnet-5-med    current
 → 2. orc-executor-opus-5-low        stronger
 ```
 
@@ -366,8 +365,8 @@ After 3 rounds it stops and shows you **how the errors moved**:
 ```
 3 rounds, still red.
   left    2 errors, middleware/validate.ts:31
-  tried   r1 sonnet-4-6-med  14 → 6
-          r2 sonnet-4-6-med   6 → 4
+  tried   r1 sonnet-5-med  14 → 6
+          r2 sonnet-5-med   6 → 4
           r3 opus-5-low       4 → 2
 
   1. 3 more rounds

package/templates/skills/orc-quick/SKILL.md

@@ -12,7 +12,7 @@ description: >
 
 The quick lane. You ask for something. It looks, asks you **one** set of
 questions, dispatches one agent, and writes down what happened. **Three steps
-per request, one user turn. Fewer than any other lane. Do not add steps.**
+per request, one user turn. Do not add steps.**
 
 **You never implement — you spawn.** You read only to FIND the right files. To
 UNDERSTAND something, you dispatch an agent.
@@ -21,7 +21,7 @@ UNDERSTAND something, you dispatch an agent.
 decide if it only READS or also WRITES → pick what to dispatch → **ask the
 user** → dispatch → check the return → write the doc entry. No request is "not
 supported"; a request can only be **too big**, and then you OFFER `/orc-mini`.
-**What this lane is NOT** — no teaching doc, no repo scan, no spec, no plan, no
+**What this lane is NOT** — no repo scan, no spec, no plan, no
 waves, no scoring, no acceptance pass (`README.md` §2).
 
 ---
@@ -34,10 +34,9 @@ without the manifest (`../_shared/lane-contract.md` §Phases).
 
 ## Q0 — Preflight (ONE time per session, silent, nothing can stop the run)
 
-1. **Config.** Read `log_dir` only. Read no other key. **One exception, and it
+1. **Config.** Read `log_dir` only. **One exception, and it
    is a PROBE, not a key read:** `probes["extra-slot"]` in the `orc lane config`
-   answer (`resolved`: extra or claude) answers the master gate, the position and the
-   routing in one, so the code-writing menu can offer line 3. Do not call
+   answer (`resolved`: extra or claude) answers the gate and the routing, so the code-writing menu can offer line 3. Do not call
    `orc extra resolve --slot quick-executor`. **A gate that is never probed is a
    gate that is always off.** Keep the answer for this session; it is an OPTION
    on a menu, never a default (`references/dispatch-gate.md`). **`habits{}` in
@@ -61,7 +60,7 @@ without the manifest (`../_shared/lane-contract.md` §Phases).
 4. **Code graph cache — never skipped** (`../_shared/code-graph.md` §0). Print
    `probes["graph-status"].line`; run
    `orc graph status --if-enabled --heal --json --brief` only when `heal_needed` is true. Put the `trace` (`GRAPH-CONSULT …`) in
-   the packet VERBATIM. Exit 3 = off → no other graph call this session. Every graph
+   the packet VERBATIM. Exit 3 (`off` or `semi`) → no other graph call this session. Every graph
    call carries `--if-enabled`, so the CLI reads the `code_graph` keys —
    this lane still reads `log_dir` and nothing else.
 5. **`gh` probe — only when the request names a PR** (`pr <n>`, `PR <n>`, a
@@ -96,16 +95,15 @@ Print it on ONE line:
 
 **The dig — graph first** (`references/look.md`). Ask the graph BEFORE any
 Grep; Grep only for what the graph does not know.
-- Names a file or symbol → `orc graph ctx <targets> --if-enabled --json --brief`, 5 at
-  most. Names none → `orc graph map --focus "<3–6 words>" --budget 800
-  --if-enabled --json --brief`, then `ctx` on the files it ranks first. Asks what breaks
-  or who uses something → `ctx <symbol> --depth 2` and `orc graph coverage
-  <files> --if-enabled --json --brief` before you call anything absent. Exit 3 →
-  Grep/Glob. Exit 4 → Grep the name, carry EVERY candidate into your question.
-  Copy each `line` into chat, each `trace` into the running record. A `map`
-  answer is ONE call; a card never replaces reading the range it names.
+- Names a symbol → ONE `orc graph ctx <symbol> --anchors --focus=<words> --if-enabled
+  --json --brief`: callers, tests (also via a caller), coverage — no Grep of that name,
+  `coverage` only on `partial`; `anchors_card` = the slice's `graph_anchors` (no
+  `--for-slice`), declared = target file + its caller files. Files → `ctx <files>` (≤ 5).
+  None → `orc graph map --focus=<3–6 words> --budget 800 …`, then ONE `ctx` (≤ 5), not
+  `cat`/`grep`. Exit 3 → Grep/Glob. Exit 4 → Grep the name, carry EVERY candidate.
+  `line` → chat, `trace` → the record. A card never replaces reading its range.
 - Wiki exists → pick 1–3 pages from `wiki/INDEX.md` and keep their **PATHS**
-  only. Never paste wiki text into a slice. Emit
+  only. With `graph_anchors` in the slice, list at most ONE wiki page path (the one about the feature's intent), not 1–3. Never paste wiki text into a slice. Emit
   `WIKI-CONSULT <tier> :: docs=<paths>`.
 - Pattern cached → keep it for the slice.
 - Always put this line in every slice, word for word:
@@ -157,12 +155,14 @@ Rules:
 
 ### 3.1 Dispatch and check the return
 
-Put in the slice: the change sketch, the Q2 answers, 2–3 acceptance bullets, the
-`graph` block from `orc graph ctx <declared files> --for-slice --if-enabled
---json --brief` (the OUTSIDE view — `references/look.md` §5), the wiki **paths**, the
-cached pattern (whole text), the `house_rules` card
-(`../_shared/phases/house-rules.md`, whole text), the `rules_card` under it
-(`orc rules slice --lane orc-quick --json` → `text`, whole text), PR comments
+Put in the slice: the change sketch, Q2 answers, 2–3 acceptance bullets, the
+`graph_anchors` (WHOLE `card` VERBATIM, `read all:` + code) from ONE `orc graph ctx --for-slice <declared files>
+--focus=<3–8 words: request, doc, copy-from name> [--refs=<copy-FROM files,
+found first>] --anchors --if-enabled --json --brief`
+(print `line`; exit 3/4 or one file, no outside change → none — `references/look.md`
+§5), the wiki **paths**, the cached pattern, the `house_rules` card
+(`../_shared/phases/house-rules.md`), the `rules_card` under it
+(`orc rules slice --lane orc-quick --json` → `text`) — all three whole text, PR comments
 with their `file:line`, and a short-return rule. A `kind: defect` entry also
 carries `repro` — the EXECUTOR writes it red, then fixes it green, never you
 (`references/defect.md`). An **ad-hoc** dispatch is also told to report its own
@@ -170,7 +170,7 @@ carries `repro` — the EXECUTOR writes it red, then fixes it green, never you
 
 Check the return with `../_shared/return-validation.md` §1–§3 + each injected
 field's §: honest `unmet[]`, `pattern_version` + `invariants_checked`,
-`graph_used` (absent on a slice that carried a card = malformed), `repro` when
+`graph_used` (absent on a slice that carried `graph_anchors` = malformed), `repro` when
 the slice asked for it, and `actual_model` / `actual_effort` → emit `VERIFY`, which names
 `graph_used=<n> targets gen <n>` and `repro red→green` beside the model match,
 and show ⛔ DOWNGRADE if they differ. Also compare `git status --short`
@@ -209,16 +209,13 @@ Never offer commit while tests are red.
 
 ### 3.3 Write the doc — ALWAYS, and BEFORE any offer
 
-**After a request that WROTE code** (never after a read-only one), so the next
-request and the next session start from a current cache, in this order:
+**After a request that WROTE code** (never after a read-only one), and ONLY
+when `probes["graph-status"].update_step` is `lane`:
 `orc graph update --notes-pending --files <actual_files> --if-enabled --json --brief`
 — ONE call that answers both (print its `line`, copy its `trace`). Exit 0 on
-`notes` → dispatch `orc-graph-noter-sonnet-4-6-med` in the SAME tool block as
-this doc write. It is ORC bookkeeping, like the trace writer — not a Q2 gate
-dispatch (`references/dispatch-gate.md` rule 8). Exit 3 or 5 → nothing. Then,
-after the entry is appended, `orc graph gain --run <this run> --if-enabled
---json --brief` → print its `line` VERBATIM into chat and the entry. It is an estimate
-with a range; never restate it as a saving.
+`notes` → dispatch `orc-graph-noter-haiku-5-high` in the SAME tool block as
+this doc write — bookkeeping, not a Q2 gate dispatch (`references/dispatch-gate.md` rule 8). Exit 3 or 5 → nothing.
+`hook`, `preflight` or `none` → no update call. No lane runs the gain meter.
 
 Append entry N to `orc-quick/<slug>/quick-context.md`
 (`references/context-doc.md`, only `## Entry shape` or `## A read-only entry`).
@@ -270,8 +267,8 @@ every event is a protocol violation. Pipe each packet to
 
 ## Lane contract (`../_shared/lane-contract.md` — read it ONLY when a call exits ≠ 0)
 
-- **Calls:** `orc lane calls orc-quick --json` names every call and its exit codes.
-  **An exit code is an ANSWER where it says so, not a failure.** Make no other call.
+- **Calls:** `orc lane calls orc-quick --json` names shared calls and exit codes.
+  **An exit code is an ANSWER where it says so, not a failure.** Own calls are here; make no other.
 - **Config:** `orc lane config orc-quick --json`. Obey `effective`, print every line
   in `announce[]` VERBATIM at preflight, and honour `stops[]` before wave 1.
   Never merge `.claude/orc.config.yaml` yourself (`../_shared/config-precedence.md`).

package/templates/skills/orc-quick/references/context-doc.md

@@ -75,8 +75,8 @@ Use as many of these as apply. Leave out what does not fit.
 **dispatches**
 | # | kind | agent / model | expect | actual | result |
 |---|---|---|---|---|---|
-| 1 | recon | `orc-recon-sonnet-4-6-med` | sonnet-4-6/medium | sonnet-4-6/medium ✅ | what it found |
-| 2 | executor | `orc-executor-sonnet-4-6-med` | sonnet-4-6/medium | sonnet-4-6/medium ✅ | 3 files |
+| 1 | recon | `orc-recon-sonnet-5-med` | sonnet-5-5/medium | sonnet-5-5/medium ✅ | what it found |
+| 2 | executor | `orc-executor-sonnet-5-med` | sonnet-5-5/medium | sonnet-5-5/medium ✅ | 3 files |
 
 Only an **other** dispatch keeps the `*(ad-hoc, untraced-by-hook)*` mark. A
 dispatch of either pinned recon agent is a normal row with the agent's name.
@@ -86,7 +86,7 @@ dispatch of either pinned recon agent is a normal row with the agent's name.
 **repro** red → green · `npm test -- tests/orders.search.test.js` (before: exit 1 · after: exit 0)
 **blast radius** 3 symbols · callers 7 in 4 files · tests reach 2 · risk high: searchByItemPrefix (exported, fan-in 4, no test reaches it)
 **tests** reached 12 passed · suite 41 passed
-**graph** gen 42 · cards 2 · <the `orc graph gain` line, word for word>
+**graph** gen 42 · <the pack `line`, word for word>
 
 **how it was resolved** a short, plain explanation of the fix and WHY this way.
 Say what you did not do, and why. This is the most useful part later.
@@ -118,8 +118,8 @@ Leave out the ones that do not apply:
   the entry tidy: an unreproduced fix is the thing the reader most needs to know.
 - **`blast radius`** — a `risk` word NEVER appears without its `why`. Nothing in
   the graph → `none indexed (<n> files not in the graph)`.
-- **`graph`** — the gain line is an estimate with a range. Copy it; never turn
-  it into a saving.
+- **`graph`** — the pack `line`, as the CLI printed it. Copy it; never
+  change it.
 
 ## A read-only entry
 

package/templates/skills/orc-quick/references/dispatch-gate.md

@@ -10,8 +10,8 @@ what is about to be spent, before it is spent.
 
 | Kind | Offer | Traced by the hook | Downgrade check |
 |------|-------|--------------------|-----------------|
-| Writes code | `orc-executor-sonnet-4-6-med` · `orc-executor-opus-5-low` · **a third option when a `quick-executor` position is held** | yes | yes (a foreign return has no `actual_model` — §2b) |
-| Read only (recon) | `orc-recon-sonnet-4-6-med` · `orc-recon-opus-5-low` · **other — name a model** | yes · yes · no | yes |
+| Writes code | `orc-executor-sonnet-5-med` · `orc-executor-opus-5-low` · **a third option when a `quick-executor` position is held** | yes | yes (a foreign return has no `actual_model` — §2b) |
+| Read only (recon) | `orc-recon-sonnet-5-med` · `orc-recon-opus-5-low` · **other — name a model** | yes · yes · no | yes |
 | Review | `orc-reviewer-opus-5-low` · or ad-hoc | yes / no | yes |
 | Build repair, round 1–2 | *reused — not asked* | yes | yes |
 | Build repair, round 3 | asked again | yes | yes |
@@ -28,7 +28,7 @@ each outcome with `orc gotcha observe` (one per finding, with `run`) and the
 ```
 Which executor for entry 2 — "add retry header"?
 
-  1. orc-executor-sonnet-4-6-med    cheap, fits a 3-file change
+  1. orc-executor-sonnet-5-med    cheap, fits a 3-file change
   2. orc-executor-opus-5-low        thinks harder, about 3× the cost   → suggested: callers 9 in 5 files
 
 Your choice — nothing runs until you answer.
@@ -49,7 +49,7 @@ Show a third line ONLY when all three are true:
 ```
 Which executor for entry 2 — "add retry header"?
 
-  1. orc-executor-sonnet-4-6-med    cheap, fits a 3-file change
+  1. orc-executor-sonnet-5-med    cheap, fits a 3-file change
   2. orc-executor-opus-5-low        thinks harder, about 3× the cost
   3. deepseek/deepseek-chat         via profile `ds` — sends this slice to a third party
 ```
@@ -89,7 +89,7 @@ else.
 ```
 Entry 3 is a context dig. Which agent should look?
 
-  1. orc-recon-sonnet-4-6-med     finding things, not deciding      → suggested
+  1. orc-recon-sonnet-5-med     finding things, not deciding      → suggested
   2. orc-recon-opus-5-low         a wide or subtle question
   3. other — name a model (effort follows your session; not traced by the hook)
 
@@ -133,12 +133,12 @@ count (`../../_shared/habits.md`), never from a feeling. Suggest
 | confident callers of the files to change ≥ 8 (from the dig, or from `orc graph changes`) | the change is felt in more places than a cheap pass checks |
 | a risk class is visible: auth · money · migration · security · concurrency · data-integrity | the same six classes the full lane's planner floors to 70 |
 | more than 3 files will really change | the cheap executor's sweet spot is a 1–3 file change |
-| **otherwise** → `orc-executor-sonnet-4-6-med` | the boring choice for a mechanical edit |
+| **otherwise** → `orc-executor-sonnet-5-med` | the boring choice for a mechanical edit |
 
 **Always print the reason beside the marker.** A marker with no reason is a
 default wearing a recommendation's clothes, and rule 1 forbids it.
 
-For recon, the suggestion is simpler: `orc-recon-sonnet-4-6-med` finds things;
+For recon, the suggestion is simpler: `orc-recon-sonnet-5-med` finds things;
 `orc-recon-opus-5-low` is for a wide or a subtle question.
 
 ## Rules
@@ -181,7 +181,7 @@ For recon, the suggestion is simpler: `orc-recon-sonnet-4-6-med` finds things;
    no step and no question to this lane.
 
 8. **ORC bookkeeping is not a dispatch you gate.** The trace writer and
-   `orc-graph-noter-sonnet-4-6-med` (the code graph's notes,
+   `orc-graph-noter-haiku-5-high` (the code graph's notes,
    `../../_shared/code-graph.md` §6) are fixed, never offered on this menu and
    never asked. They run no user task and change no code, and asking about them
    would add a user turn to a lane whose promise is one turn per request.
@@ -200,8 +200,8 @@ bad day worse, so:
 ```
 3 rounds, still red.
   left    2 errors, middleware/validate.ts:31
-  tried   r1 sonnet-4-6-med  14 → 6
-          r2 sonnet-4-6-med   6 → 4
+  tried   r1 sonnet-5-med  14 → 6
+          r2 sonnet-5-med   6 → 4
           r3 opus-5-low       4 → 2
 
   1. 3 more rounds

package/templates/skills/orc-quick/references/gh-mode.md

@@ -88,7 +88,8 @@ it — a test that arrives through a URL included. Print one line per thread:
 [1] dana · export.js:34 → streamRows (callers 2 · tests 1)
 ```
 
-That card goes into the thread's slice. Exit 3 (the graph is off) or exit 4 (not
+Use that card to choose the thread's declared files. The slice gets the pack
+(`SKILL.md` Q3.1), not this card. Exit 3 (the graph is off) or exit 4 (not
 found) → skip the line and work from the anchor alone.
 
 ## One gate per thread

package/templates/skills/orc-quick/references/look.md

@@ -22,13 +22,17 @@ way round.
 
 | The request | The call |
 |---|---|
-| names a file or a symbol | `orc graph ctx <targets> --if-enabled --json --brief` — 5 targets at most |
-| names none ("where is the retry logic?") | `orc graph map --focus "<3–6 words from the request>" --budget 800 --if-enabled --json --brief`, then `ctx` on the files it ranks first |
-| asks what breaks, or who uses something | `orc graph ctx <symbol> --depth 2 --if-enabled --json --brief`, then `orc graph coverage <files> --if-enabled --json --brief` |
+| names a symbol | ONE `orc graph ctx <symbol> --anchors --focus=<words> --if-enabled --json --brief` — the card gives the callers, the tests (also via a caller) and the coverage verdict: do not Grep that name, do not run `coverage` unless the card says `partial` |
+| names a file | `orc graph ctx <targets> --if-enabled --json --brief` — 5 targets at most |
+| names none ("where is the retry logic?") | `orc graph map --focus=<3–6 words from the request> --budget 300 --if-enabled --json --brief`, then `ctx` on the files it ranks first |
+| asks what breaks, or who uses a FILE | `orc graph ctx <files> --if-enabled --json --brief`, then `orc graph coverage <files> --if-enabled --json --brief` |
 
 Exit 3 = the graph is off → Grep and Glob, as before, and make no other graph
 call this session. Exit 1 = no index → the same. **A `map` answer is ONE call**,
-not one per file it lists.
+not one per file it lists. After `map`, get facts about the files it names with
+ONE `orc graph ctx <files…> --if-enabled --json --brief` (≤ 5) — not `cat`/`grep`
+of those files. Read source only for a fact the card cannot give (a literal
+string, a template line).
 
 Copy each answer's `line` into chat. Copy each answer's `trace` into the running
 record, word for word.
@@ -38,9 +42,10 @@ record, word for word.
 **A card does not replace reading the range it names.** It tells you where to
 look. It never tells you what the code does.
 
-**No card in the slice for a change inside one file the user named**, when no
-signature changes and nothing new is exported (`../../_shared/code-graph.md`
-§7). The executor reads that file whole anyway, so the card would be paid twice.
+**The slice gets the pack path, never a card.** A dispatch that writes code
+gets ONE pack (§5). **No pack when the change stays inside ONE file the user
+named and nothing outside it changes** (no signature change, no new export):
+the executor reads that file anyway, and a pack there is pure cost.
 
 **`--source [N]` is for a range you will NOT edit.** A caller's body, a
 neighbour, a test. A file the executor is going to change is read in full by the
@@ -76,14 +81,31 @@ sentence, word for word:
 
 ## 5. What you hand to an executor
 
+**A request that names a symbol:** the look call `ctx <symbol> --anchors` (§2)
+already returned the anchors. Its `anchors_card` goes into the slice as
+`graph_anchors` — no second `--for-slice` call for that dispatch. Declared files
+= the target file + the caller files the card lists.
+
+**A request that names files, or nothing (map first):**
+
 ```
-orc graph ctx <declared files> --for-slice --if-enabled --json --brief
+orc graph ctx --for-slice <file1> <file2> … (space- or comma-separated) --focus=<the dig words> [--refs=<copy-from files>] --anchors --if-enabled --json --brief
 ```
 
-ONE call, 10 files at most. Its `card` becomes the slice's `graph` block. This
-is the **outside view** — who imports these files, who calls into them from
-elsewhere, which tests reach them, where they are mounted. It is the half the
-executor cannot see by reading the files it was given.
+ONE call, 10 files at most. No file is written; it answers ONE `line` (print it)
+and a `card`. Paste the `card` into the slice VERBATIM as `graph_anchors`, with its `read all: …` line and its code block — never shorten it. With `graph_anchors` in the slice, list at most ONE wiki page path (the one about the feature's intent), not 1–3. The card:
+up to 12 `path:a-b` ranges the dig found — the members of the declared files and
+of the `--refs` files that best match the focus words — and ONE `read all:` command
+the executor runs first. `--refs` = every file the request or its
+requirement document says to copy behaviour or style FROM, plus the precedent
+the dig found (max 5) — never the files you will edit. You have none → leave it out; the CLI picks them.
+
+`--focus=` takes 3–8 words from the request AND from the requirement document it names — always
+the words the document uses to name a file to copy behaviour or style from (e.g. `swap,modal,selection`).
+Before the anchors call, locate every copy-from file the document names with ONE
+`orc graph map --focus=<its words> --budget 300 --if-enabled --json --brief` (or `orc graph ctx <Name>
+--if-enabled --json --brief` when the name is exact), and pass it in `--refs=`.
+Exit 3 or 4 → none. One named file, nothing outside it changes → none (§3).
 
 Its `trace` gets `entry=<n>`.
 

package/templates/skills/orc-retro/SKILL.md

@@ -236,11 +236,11 @@ documented defaults, out loud. Priorities and families:
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-retro --json` names every
-CLI call this lane makes, each with its exit-code contract, its cost, when to run
+SHARED CLI call this lane makes, each with its exit-code contract, its cost, when to run
 it, and what an EMPTY answer means. Never invent a spelling, never re-word an
 exit code, and never re-derive a state word — the CLI's state words are the only
 state words, and **an exit code is an ANSWER wherever that contract says so, not
-a failure**. A call the answer does not name is a call this lane does not make.
+a failure**. A call that neither it nor this skill names is a call this lane does not make.
 Exit ≠ 0 from the catalogue itself → say the CLI is unavailable and name the
 command you are about to run, out loud, before running it.