@azure-id/orc 2.1.0 → 2.2.0

package/templates/skills/orc-diy/references/blocks/wiki.md

@@ -1,26 +1,26 @@
-## Wiki gate
-
-<!-- diy:when wiki_gate=off -->
-Skip the wiki freshness check entirely for this flow. If a project wiki
-exists, executors may still receive wiki page pointers, but freshness is
-never computed and never surfaced.
-<!-- /diy:when -->
-<!-- diy:when wiki_gate=notice -->
-Compute the wiki freshness tier exactly as the full lane does (follow the
-read-side procedure in `.claude/skills/orc-wiki/references/staleness.md`).
-Fresh → use silently; aging → one-line notice, continue; stale → warn the
-user that wiki hints may be outdated, continue. Never block on it.
-<!-- /diy:when -->
-<!-- diy:when wiki_gate=hard -->
-Compute the wiki freshness tier exactly as the full lane does (follow the
-read-side procedure in `.claude/skills/orc-wiki/references/staleness.md`).
-Fresh or aging → proceed. Stale or missing → STOP and ask the user: refresh
-the wiki first (recommended), or continue anyway with hints demoted. Respect
-the precedence rule from that reference in every consumer slice.
-<!-- /diy:when -->
-
-<!-- diy:when post_ship_wiki_ask=on -->
-After a successful ship on a big run, offer the post-ship wiki refresh ask
-exactly as the full lane defines it in the orc skill (guarded on a non-empty
-wiki; judged by final task/file counts at ship time).
-<!-- /diy:when -->
+## Wiki gate
+
+<!-- diy:when wiki_gate=off -->
+Skip the wiki freshness check entirely for this flow. If a project wiki
+exists, executors may still receive wiki page pointers, but freshness is
+never computed and never surfaced.
+<!-- /diy:when -->
+<!-- diy:when wiki_gate=notice -->
+Read the wiki freshness tier from `orc wiki status --json` (`state`, then
+`tier`) — the CLI is its only executor; never compute it yourself.
+Fresh → use silently; aging → one-line notice, continue; stale → warn the
+user that wiki hints may be outdated, continue. Never block on it.
+<!-- /diy:when -->
+<!-- diy:when wiki_gate=hard -->
+Read the wiki freshness tier from `orc wiki status --json` (`state`, then
+`tier`) — the CLI is its only executor; never compute it yourself.
+Fresh or aging → proceed. Stale or missing → STOP and ask the user: refresh
+the wiki first (recommended), or continue anyway with hints demoted. Respect
+the precedence rule from that reference in every consumer slice.
+<!-- /diy:when -->
+
+<!-- diy:when post_ship_wiki_ask=on -->
+After a successful ship on a big run, offer the post-ship wiki refresh ask
+exactly as the full lane defines it in the orc skill (guarded on a non-empty
+wiki; judged by final task/file counts at ship time).
+<!-- /diy:when -->

package/templates/skills/orc-diy/references/flow-schema.md

@@ -27,7 +27,7 @@ selector.
 | `mock_example` | `ask` / `on` / `off` | Post-verify mocked example + drift recovery (`mock-examples/<slug>/`, never committed) |
 | `tdd` | `on` / `off` | TDD-anchored planning: plan-time `tdd_spec` (scoped by `disposition`), paired TDD tasks for the red proof, TDD gate in the verify slot |
 | `gotchas` | `on` / `off` | Repair memory: inject scope-matching gotchas into slices, record one when a repair loop goes red → green (`_shared/gotchas.md`) |
-| `code_graph` | `on` (default) / `off` | Code-graph cache steps: `orc graph status --heal` at preflight, `orc graph ctx` cards in slices, `orc graph map` then `orc graph impact` + `orc graph cochange` at planning, `orc graph changes` at review, `orc graph coverage` on demand, `orc graph update` after every wave and at ship, one `orc graph notes` batch per wave when notes are on. `on` compiles them in and the global `code_graph` key decides at run time (every call carries `--if-enabled`); `off` removes them (`_shared/code-graph.md`) |
+| `code_graph` | `on` (default) / `off` | The four graph touchpoints: consult at preflight (print the probe line; `orc graph status --heal` only when `heal_needed`), orient at planning (`orc graph map --focus=` once, then `orc graph impact` + `orc graph cochange`), ONE `orc graph ctx --for-slice … --anchors` per writing slice (`graph_anchors`, inline), `orc graph changes --files=` once at review; `orc graph update --notes-pending` only when `update_step` is `lane`; no gain step. `on` compiles them in and the global `code_graph` key decides at run time (every call carries `--if-enabled`); `off` removes them (`_shared/code-graph.md`) |
 | `wiki_gate` | `notice` / `off` / `hard` | Wiki freshness handling at preflight |
 | `post_ship_wiki_ask` | `on` / `off` | Post-ship wiki refresh offer on big runs |
 | `summary` | `full` / `off` / `short` | Summary depth |
@@ -44,7 +44,7 @@ selector.
 Hard errors (config not written):
 - `scoring: off` without a `fixed_executor`.
 - `fixed_executor` or any agent choice above `session_tier` (tier order:
-  haiku-4-5 < sonnet-4-6 < sonnet-5 < opus-4-7 < opus-4-8 < opus-5 < fable-5 —
+  haiku-5 < sonnet-4-6 < sonnet-5 < opus-4-7 < opus-4-8 < opus-5 < fable-5 —
   subagents cannot exceed the main session; effort medium < high < xhigh < max).
   A tier below `opus-5-high` clips the `[90,100]` band to the highest agent it
   allows, at compile time.

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

@@ -13,7 +13,7 @@ explaining anything twice.
 
 That is why a 900-line TSD does not end a session. Nothing that holds context
 ever holds the document: each writer owns exactly ONE file, each checker reads
-ONE bounded part, and the orchestrator holds a map.
+only the bounded part files of its slice, and the orchestrator holds a map.
 
 And since v0.49.0 there is a second sentence:
 
@@ -159,7 +159,7 @@ orc doc parts my-prd                       # what is written, and what is not
 orc doc compile my-prd [--partial]         # sections/ -> document.md. FREE
 orc doc lint my-prd                        # the free check (0 clean / 1 findings)
 orc doc map my-prd                         # fresh line numbers, never stored
-orc doc plan my-prd --role check --json    # one bounded part file per checker
+orc doc plan my-prd --role check --json    # bounded part files per checker slice
 orc doc split my-prd --section 04-design --by-heading   # store a big section in parts
 orc doc split my-prd                       # recover sections/ from document.md
 orc doc status my-prd                      # 0 nothing to do / 1 something to do / 2 unknown