@azure-id/orc 1.6.0 → 1.7.1

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

@@ -202,7 +202,8 @@ Rules:
 
 Put in the slice: the change sketch, the Q2 answers, 2–3 acceptance bullets,
 the wiki **paths**, the cached pattern (whole text), the `house_rules` card
-(`../_shared/phases/house-rules.md`, whole text), PR comments with their
+(`../_shared/phases/house-rules.md`, whole text), the `rules_card` under it
+(`orc rules slice --lane orc-quick --json` → `text`, whole text), PR comments with their
 `file:line`, and a short-return rule (fields only, no long prose).
 
 For an **ad-hoc** dispatch, also tell the agent to report its own
@@ -328,6 +329,13 @@ orc-quick has no config key of its own and ignores every dispatch-forcing key
 which is why five of them come back INERT with a reason. Say that at the gate;
 see "Nothing can override this lane" above.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-quick --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-quick --json` names every

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

@@ -243,6 +243,13 @@ a failure**. A call the answer does not name 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.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-retro --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

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

@@ -182,6 +182,13 @@ a failure**. A call the answer does not name 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.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-route --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

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

@@ -227,6 +227,13 @@ Tier **Iterative** — one packet per completed cycle. Narration is DISPATCHED,
 never remembered: build the PHASE PACKET and dispatch
 `orc-trace-writer-haiku-4-5`. Canonical: `../_shared/phases/trace.md`.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-test --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

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

@@ -99,6 +99,13 @@ a failure**. A call the answer does not name 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.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-verify --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Waiting mid-run (`/orc-wait`)
 
 Canonical: `../_shared/wait.md`. **`a lane that waits without a hand-back` has broken this contract.**

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

@@ -143,6 +143,14 @@ v0.41.0 has been recording and never reading. **Usage lives in its own file
 100% doc-header-derived and `orc wiki sync` is its only writer. Render what the
 CLI returns; never compute an order, a tier or an estimate here.
 
+**One doc at a time (v1.7.0).** `/orc-wiki update <doc-or-topic>` is the targeted
+refresh under the name people type; `/orc-wiki add "<topic>"` adds ONE new doc to
+a wiki that already exists, without re-planning any other area. A topic is
+resolved with `orc wiki resolve` (free) before anything is scanned — AMBIGUOUS is
+a question, never a guess — a new row is RESERVED with `orc wiki add`, and the
+run ends with `orc wiki refs`, the derived-reference sweep. Flow: A0–A7 in
+references/partial-refresh.md.
+
 ## Refresh & staleness (references/staleness.md — THE canonical freshness reference)
 
 Freshness is computed on read, never stored: measure `scan_commit` (from
@@ -163,6 +171,13 @@ the CLI is unavailable and fall back to `../_shared/config-precedence.md`'s
 documented defaults, out loud. Priorities and families:
 `../_shared/config-precedence.md`.
 
+## Rules — the anti-slop card (`../_shared/phases/rules.md`)
+
+`orc rules slice --lane orc-wiki --json` is the ONLY assembler; never build
+the card here. It rides under the house rules and above the task —
+**house rules > your project's rules > ORC's own packs** — and its `line` prints
+VERBATIM at preflight. Returns gain `rules_applied[]`, `rules_conflicts[]` (a gap,
+never a silent choice) and `rules_overridden[]`.
 ## Calls
 
 **ONE catalogue, and it is not you:** `orc lane calls orc-wiki --json` names every

package/templates/skills/orc-wiki/references/partial-refresh.md

@@ -52,12 +52,20 @@ in this skill** — one engine, the same rule the wiki tier itself lives under
 ## Targeted refresh
 
 ```
+/orc-wiki update <doc>                   the same thing, under the name people type
+/orc-wiki update "<topic>"               resolved to a doc first — see below
 /orc-wiki refresh <doc>
 /orc-wiki refresh --only api/refunds/**
 /orc-wiki refresh --top 2
 /orc-wiki refresh --all-touched          (today's delta behaviour)
 ```
 
+`update` is an ENTRY, not a second mechanism. A filename goes straight into
+R0–R5 below. A topic goes through `orc wiki resolve "<topic>" --json` first
+(free, no scan): **exit 0** names the doc · **exit 2** is AMBIGUOUS, so ask which
+one rather than scanning a guess · **exit 1** means nothing covers it, and the
+request is really an ADD.
+
 It **skips Phase 0 branch detection and Phase 1 area planning entirely** — the doc
 exists, so its coverage area is already in its own header. That skip is the whole
 saving in wall-clock terms.
@@ -77,6 +85,66 @@ task refresh simply never reaches it.
 **Crosslink rules are unchanged:** tags publish per scan-task, no refresh path
 bulk-deletes `wiki/crosslink/`, and the dead-tag sweep still runs per point.
 
+## Add ONE topic — `/orc-wiki add "<topic>"`   (v1.7.0)
+
+The other half of "one doc at a time". Targeted refresh answers *this doc has
+moved*; this answers *this topic is not in the wiki at all* — and until v1.7.0 a
+new coverage area only appeared as a by-product of the coverage-gap sweep during
+a delta refresh, so "add the remittance feature" had no path that did not
+re-plan every area in the repo.
+
+Like a targeted refresh it **skips Phase 0 branch detection and Phase 1 area
+planning**. Unlike one, it ends with the **reference sweep**: adding a doc moves
+more derived surfaces than changing one does.
+
+```
+A0  resolve     orc wiki resolve "<topic>" --json                       free
+                exit 0 MATCH      → this is really an UPDATE. Say so, route there.
+                exit 2 AMBIGUOUS  → ask which doc. NEVER scan a guess.
+                exit 1 NEW        → continue.
+                exit 3            → no wiki, or unregistered. Fix that first.
+A1  scope       the resolver returns `suggested_covers` from PATH NAMES ONLY.
+                Show them as a proposal and let the user correct them. ONE turn.
+                A wrong glob is a doc that documents the wrong area forever.
+A2  confirm     slug · title · covers · the resolved TIER · the token + $ estimate.
+                ONE turn. NOTHING spawns before the user says yes.
+A3  reserve     orc wiki add <slug> --title "<t>" --covers "<glob>"      free
+                Writes a STUB with `status: reserved` — a target for the scan,
+                not a document. It is reported as outstanding until a scan
+                replaces the body, so a half-finished add can never look done.
+A4  scan        ONE scan-task, at the tier the ladder resolved
+A5  write       doc body + crosslink tags (the per-scan-task rule, unchanged).
+                Replace `status: reserved` with a real `scanned_at`,
+                `scanned_commit` and `covered_files` set.
+A6  references  orc wiki refs                                            free
+A7  integrity   the existing self-check, scoped to the new doc
+```
+
+### A6 — the reference sweep, and why it is its own step
+
+After ONE doc is written, these surfaces are derived from the doc SET and are
+now behind it. Before v1.7.0 they were repaired from memory, one at a time, and
+the ones nobody remembered stayed wrong — which is likeliest on a SMALL run,
+because the run feels too small to need a sweep.
+
+| Surface | What goes wrong | Repaired by |
+|---|---|---|
+| `wiki-meta.json` + `wiki/INDEX.md` | the new doc is not registered | `orc wiki refs` does it (free) |
+| a reserved row | the reservation never got its scan | reported, with the update command |
+| `wiki/orc-orientation.md` | its reading order predates the new doc | reported — free to regenerate |
+| `wiki/orc-architecture-overview.md` | it names neither the file nor the area | reported — free, and OPTIONAL |
+| the `CLAUDE.md` pointer block | its doc COUNT is now measurably wrong | reported |
+| `wiki/crosslink/**` | a tag anchored to a file that is gone | reported, offered per tag, never bulk-deleted |
+
+`orc wiki refs` **repairs only the registration**, because `orc wiki sync` is
+free and already the single writer of those two files. Everything else is
+REPORTED with its command. A sweep that silently regenerated prose would be
+spending money nobody asked it to spend, which is the same rule the free-repair
+ladder above is built on.
+
+`orc wiki refs --check` reports and repairs nothing. Exit **0** clean · **1**
+work pending or registration repaired · **2** cannot compute.
+
 ## The scan tier ladder (`wiki_scan_tier`, default `ladder`)
 
 Every scan-task used to dispatch the most expensive scanner in the payload whether

package/templates/skills/orc-wiki/references/phases/phase-0.md

@@ -48,6 +48,20 @@ Then detect state and branch:
 - **Wiki checkpoint exists (mid-scan)** → RESUME. Re-anchor from
   state-of-play + checkpoint; show "X of Y areas done, ~Z remaining"; light
   cost note; continue where it stopped.
+- **`/orc-wiki update <doc-or-topic>` (explicit)** → **TARGETED REFRESH**, the
+  same branch as `refresh <doc>` below and the same flow. It exists because
+  `update some-doc.md` is what a user actually types. A FILENAME routes straight
+  to the refresh; a TOPIC ("the remittance feature") goes through
+  `orc wiki resolve "<topic>" --json` first (free): exit 0 names the doc and you
+  refresh it, exit 2 is AMBIGUOUS and you ask which one, exit 1 means nothing
+  covers it and this is really an ADD.
+- **`/orc-wiki add "<topic>"` (explicit)** → **ADD ONE TOPIC**
+  (references/partial-refresh.md, the A0–A7 flow). One new doc in a wiki that
+  already exists, without re-planning a single other area. It skips branch
+  detection and area planning like a targeted refresh does, and it ends with the
+  **reference sweep** (`orc wiki refs`) rather than a bare `orc wiki sync` —
+  adding a doc moves more derived surfaces than changing one does. Never start
+  it without the ONE confirmation turn at A2.
 - **`/orc-wiki refresh <doc> | --only <glob> | --top N | --all-touched`
   (explicit)** → **TARGETED REFRESH** (references/partial-refresh.md). Skips
   branch detection AND area planning — the doc exists, so its coverage area is
@@ -66,6 +80,6 @@ Then detect state and branch:
   re-publishes crosslink tags in the same pass (hard rule 11), preserves the
   folder (rule 12), and ends by regenerating the orientation doc + atlas
   (derived, cheap). A LEGACY wiki with unpublished tags is a backfill, not a
-  refresh — route to CROSSLINK-ONLY.
+  refresh — route to CROSSLINK-ONLY.
 
 <!-- /orc:layer -->