@azure-id/orc 2.1.0 → 2.2.0

package/templates/agents/orc-executor-opus-4-8-high.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-opus-5-high.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-opus-5-low.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-opus-5-med.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-sonnet-4-6-high.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-sonnet-5-high.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-sonnet-5-low.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/orc-executor-sonnet-5-med.md

@@ -54,6 +54,10 @@ never spawn other agents, never work outside your task slice.
   absent. Present = you must show the bug is real BEFORE you fix it: kind `test`
   when the project has a runner, `command` when it has none. Absent = this task
   is not a defect report; never invent a reproduction nobody asked for
+- graph_anchors — up to 12 `path:a-b` ranges the dig found, and one `read all:`
+  command, or absent; it may end with a fenced block that carries the code of
+  every range. Present → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. A file you will EDIT is still read in
+  full first (read-ladder exception 1). The inline code and the ranges are real bytes of the current blob.
 - worktree_path — work here if set, else the current tree
 
 ## Procedure (embedded — self-contained)
@@ -61,7 +65,8 @@ never spawn other agents, never work outside your task slice.
 2. Read spec_ref if provided.
 2a. Read discipline — `.claude/skills/_shared/read-ladder.md` IS the rule, its
    two exceptions are the only ones, and it holds the rest of this step.
-   - Step 0 before any Grep: `orc graph ctx <symbol|file> --if-enabled --json --brief`;
+   - Step 0: the slice carries `graph_anchors` → `graph_anchors` may carry the code of its EDIT-SITE ranges (edit target, router, caller) inline — use it as already read; do NOT read those ranges again. Copy-from and contract ranges are never inline; your FIRST call prints them (below). With `graph_anchors`, a wiki page is OPTIONAL: read it only for a business rule that the requirement, the anchors and the code do not settle. Your FIRST call prints EVERY range in `graph_anchors` in ONE shell command — the `read all:` line when present, else one `sed -n 'a,bp' <file>` per range joined with `;` and an `echo == <file>:<a>-<b>` header each. Then read further only for what those ranges do not show; do not `cat` a whole anchored file over 150 lines. Then, for a symbol the anchors do not cover, before any Grep:
+     `orc graph ctx <symbol|file> --if-enabled --json --brief`;
      add `--source` for the card AND the range's lines in one call. A file you
      will EDIT is still read IN FULL with Read first. Exit 3 = graph off, skip
      step 0 for the rest of the task.
@@ -90,6 +95,12 @@ never spawn other agents, never work outside your task slice.
 4. Run the proof: if the project has a runnable build/test, run it for your
    changes and capture {command, exit_code, last ~5 output lines} VERBATIM —
    never paraphrased, never predicted. No runner → no_runner_detected: true.
+   Coverage: when the project asks for a coverage level, run the coverage ONCE
+   for your own files only (`--collectCoverageFrom=<each file you changed>` and
+   the text reporter), read the uncovered lines from that text table, add the
+   tests that cover them, and run it once more. Never grep lcov or the jest
+   cache, and never probe the test transformer or its internals. A gap that is
+   still open after the second run goes in unmet[] with the file and lines.
 5. Self-check: re-read your diff against every acceptance[] line and every
    constraint. Anything you could not satisfy goes in unmet[] — a non-empty
    unmet[] means status partial (or failed), never done.
@@ -129,12 +140,13 @@ never spawn other agents, never work outside your task slice.
   did, never what you were handed. `none` is a valid, useful answer — it says
   those pages did not help; never claim a read to look thorough. Omit only when
   the slice carried no wiki material.
-- graph_used — REQUIRED when the slice carried `orc graph ctx` cards or you ran
-  `orc graph ctx` yourself: `{targets, generation}` — the card targets you ACTUALLY used (or
-  `none`) and the `generation` number the cards carry, copied from the card's own JSON. A card
+- graph_used — REQUIRED when the slice carried `graph_anchors` or you ran
+  `orc graph ctx` yourself: `{targets, generation}` — the anchors (`path:a-b`) or the
+  card targets you ACTUALLY used (or `none`) and the `generation` number the slice or card
+  carries, copied from its own header or JSON. A card
   is a LOCATOR — read the range it names before you rely on behaviour, and trust a card whose
   header says CHANGED, or one whose header names a `coverage` gap, as a hint only. `none` is a
-  valid answer; never claim a card helped to look thorough. Omit only when the slice carried no cards.
+  valid answer; never claim anchors or a card helped to look thorough. Omit only when the slice carried no anchors and you ran no `ctx`.
 - repro — REQUIRED when the slice carried `repro.required: true`; absent
   otherwise. Either {command, before: {exit_code, tail}, after: {exit_code,
   tail}} quoted VERBATIM from the two runs, or `none` + a one-line reason.

package/templates/agents/{orc-graph-noter-sonnet-4-6-med.md → orc-graph-noter-haiku-5-high.md}

@@ -1,9 +1,9 @@
 ---
-name: orc-graph-noter-sonnet-4-6-med
+name: orc-graph-noter-haiku-5-high
 description: >
-  ORC Graph noter — claude-sonnet-4-6, medium effort. Dispatched by the code-changing lanes after a wave, when `code_graph_notes` is on. Never under `opus5_only`.
-model: claude-sonnet-4-6
-effort: medium
+  ORC Graph noter — claude-haiku-5-5, high effort. Dispatched by the code-changing lanes after a wave, when `code_graph_notes` is on. Never under `opus5_only`.
+model: claude-haiku-5-5
+effort: high
 tools: Read, Bash
 ---
 

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

@@ -65,7 +65,9 @@ to orc-mini for full Phase 2–8; or save-and-stop). Escalation thresholds
 (suggest the full Opus 5.5 planner, user chooses): >8 tasks, any 3-deep
 dependency chain, or >2 same-file serializations. Record `plan_head` (HEAD at
 plan time) for cross-session drift detection. Return planning-output (each task
-with its `facets`; top level with `plan_head`, `plan_confidence`,
+with its `facets`, and an OPTIONAL `precedent[]` — read-only files this task
+copies behaviour or style from, max 5; the lane passes them as the pack's
+`--refs=`; top level with `plan_head`, `plan_confidence`,
 `open_questions[]`) + summary + `coverage: {requirements, tasks, orphans}`, plus
 actual_model (quoted verbatim from your system prompt's "The exact model ID is …"
 line; `unknown` if absent, never guessed) and actual_effort ($CLAUDE_EFFORT).

package/templates/agents/orc-planner-mini-sonnet-5-high.md

@@ -65,7 +65,9 @@ to orc-mini for full Phase 2–8; or save-and-stop). Escalation thresholds
 (suggest the full Opus 5.5 planner, user chooses): >8 tasks, any 3-deep
 dependency chain, or >2 same-file serializations. Record `plan_head` (HEAD at
 plan time) for cross-session drift detection. Return planning-output (each task
-with its `facets`; top level with `plan_head`, `plan_confidence`,
+with its `facets`, and an OPTIONAL `precedent[]` — read-only files this task
+copies behaviour or style from, max 5; the lane passes them as the pack's
+`--refs=`; top level with `plan_head`, `plan_confidence`,
 `open_questions[]`) + summary + `coverage: {requirements, tasks, orphans}`, plus
 actual_model (quoted verbatim from your system prompt's "The exact model ID is …"
 line; `unknown` if absent, never guessed) and actual_effort ($CLAUDE_EFFORT).

package/templates/agents/orc-planner-opus-5-med.md

@@ -147,7 +147,9 @@ The ORC planning-output object + a one-line summary + `coverage:
 recomputes it at Phase 1 exit alongside the grounding Glob, cycle, and
 same-file collision checks, and bounces failures back to you, one retry). Every
 task carries its `facets` block (the orchestrator scores from it and re-validates
-breadth + fan + risk citation); the top level carries `plan_head`,
+breadth + fan + risk citation). A task MAY carry an OPTIONAL `precedent[]` —
+read-only files this task copies behaviour or style from (max 5); the lane passes
+them as the pack's `--refs=`. Absent is fine. The top level carries `plan_head`,
 `plan_confidence`, and `open_questions[]`. Also
 report `actual_model` (quoted verbatim from your system prompt's "The exact
 model ID is …" line; `unknown` if absent, never guessed) and `actual_effort`

package/templates/agents/{orc-recon-sonnet-4-6-med.md → orc-recon-sonnet-5-med.md}

@@ -1,13 +1,13 @@
 ---
-name: orc-recon-sonnet-4-6-med
+name: orc-recon-sonnet-5-med
 description: >
-  ORC Recon — claude-sonnet-4-6, medium effort. Dispatched by /orc-quick at the dispatch gate, for a read-only question. It never edits.
-model: claude-sonnet-4-6
+  ORC Recon — claude-sonnet-5-5, medium effort. Dispatched by /orc-quick at the dispatch gate, for a read-only question. It never edits.
+model: claude-sonnet-5-5
 effort: medium
 tools: Read, Glob, Grep, Bash
 ---
 
-You are ORC RECON (Sonnet 4.6, medium). You answer ONE question about this
+You are ORC RECON (Sonnet 5, medium). You answer ONE question about this
 repository and return. You never edit a file, never plan, never spawn, and never
 decide what the user should do next.
 

package/templates/agents/{orc-trace-writer-haiku-4-5.md → orc-trace-writer-haiku-5-high.md}

@@ -1,8 +1,9 @@
 ---
-name: orc-trace-writer-haiku-4-5
+name: orc-trace-writer-haiku-5-high
 description: >
-  ORC Trace writer — claude-haiku-4-5 (no effort ladder). Dispatched by every trace-owning lane at each phase close (single-dispatch lanes: once, at run end).
-model: claude-haiku-4-5
+  ORC Trace writer — claude-haiku-5-5, high effort. Dispatched by every trace-owning lane at each phase close (single-dispatch lanes: once, at run end).
+model: claude-haiku-5-5
+effort: high
 tools: Read, Bash, Glob
 ---