@azure-id/orc 1.9.0 → 1.9.1

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

@@ -56,7 +56,7 @@ is a pointer into nothing.
    knowledge never stops the run, never causes a fallback, never triggers a
    scan. Print ONE line each.
 4. **Code graph cache — never skipped** (`../_shared/code-graph.md` §0). Run
-   `orc graph status --if-enabled --heal --json`: it builds or updates the cache
+   `orc graph status --if-enabled --heal --json --brief`: it builds or updates the cache
    in the same call. Print its `line`; put its `trace` (`GRAPH-CONSULT …`) in the
    packet VERBATIM. Exit 3 = off → no other graph call this session. Every graph
    call carries `--if-enabled`, so the CLI reads the `code_graph` keys —
@@ -94,11 +94,11 @@ Print it on ONE line so nothing is skipped in secret:
 
 **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`, 5 at
+- 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`, then `ctx` on the files it ranks first. Asks what breaks
+  --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` before you call anything absent. Exit 3 →
+  <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.
@@ -155,7 +155,7 @@ Rules:
 
 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` (the OUTSIDE view — `references/look.md` §5), the wiki **paths**, the
+--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
@@ -187,12 +187,11 @@ say it once; never invent a build command — take it from `wiki-meta.json`'s
 exit=<n>` then `REPRO green :: <cmd> exit=0`. `repro: none` → say **not
 reproduced** with the reason (`references/defect.md`).
 
-**Affected tests first.** Run `orc graph changes --if-enabled --json`, keep the
-`symbols[]` whose `file` is in the return's `actual_files`, and run the test
-files their `tests[]` name BEFORE the suite — when the runner takes a file list.
-A runner that takes none → one line saying so. Then print the blast radius from
-the same answer, one line, and never a `risk` word without its `why`. Zero
-symbols in the graph → `blast radius   none indexed (<n> files not in the graph)`.
+**Affected tests first.** Run `orc graph changes --files=<actual_files> --if-enabled
+--json --brief`. Print its `tests_line`, run the files its `tests[]` names BEFORE
+the suite — a runner that takes no file list → one line saying so — and append
+` → <n> passed`. Then the suite. Then print its `blast_line` VERBATIM: the CLI
+attaches every `risk` word's `why`, so never restate it. Exit 3 → nothing.
 
 `tests reached  3 files (ROUTE 2 · call 1) → 12 passed` · then the suite · then
 `blast radius   3 symbols · callers 7 in 4 files · tests reach 2 · risk high: <symbol> (exported, fan-in 4, no test reaches it)`
@@ -210,13 +209,13 @@ Never offer commit while tests are red.
 
 **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:
-`orc graph update --notes-pending --files <actual_files> --if-enabled --json`
+`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` → print its `line` VERBATIM into chat and the entry. It is an estimate
+--json --brief` → print its `line` VERBATIM into chat and the entry. It is an estimate
 with a range; never restate it as a saving.
 
 Append entry N to `orc-quick/<slug>/quick-context.md`

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

@@ -70,7 +70,7 @@ It does not tell you what sits there or what depends on it.
 For each thread the user takes, run one call:
 
 ```bash
-orc graph ctx <the anchor file:line> --if-enabled --json
+orc graph ctx <the anchor file:line> --if-enabled --json --brief
 ```
 
 It names the symbol the comment sits in, its callers, and the tests that reach

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

@@ -20,9 +20,9 @@ way round.
 
 | The request | The call |
 |---|---|
-| names a file or a symbol | `orc graph ctx <targets> --if-enabled --json` — 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`, then `ctx` on the files it ranks first |
-| asks what breaks, or who uses something | `orc graph ctx <symbol> --depth 2 --if-enabled --json`, then `orc graph coverage <files> --if-enabled --json` |
+| 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` |
 
 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**,
@@ -52,7 +52,7 @@ candidate into your Q2 question. Never pick one in silence.
 
 "What breaks if I change this?" · "Who uses this?" · "Is it safe to change?"
 
-Run `orc graph coverage <the files in play> --if-enabled --json` FIRST. A file
+Run `orc graph coverage <the files in play> --if-enabled --json --brief` FIRST. A file
 whose coverage is `partial` is read in the source before you call anything
 absent in it.
 
@@ -75,7 +75,7 @@ sentence, word for word:
 ## 5. What you hand to an executor
 
 ```
-orc graph ctx <declared files> --for-slice --if-enabled --json
+orc graph ctx <declared files> --for-slice --if-enabled --json --brief
 ```
 
 ONE call, 10 files at most. Its `card` becomes the slice's `graph` block. This