@journeykit/canon 0.24.0 → 0.24.1

package/dist/skills/reference/canon-gate.md

@@ -223,8 +223,11 @@ accepted divergences: 1 known gap(s) — not failing the gate:
 Re-verification is one rule with two triggers: a blocker whose latest
 disposition is `fixed`, and a chore change once approved, keep the subject
 from shipping until every one of its evidenced scenarios has evidence
-recorded after the close or the approval. The refusal names the scenarios
-and the batch command: `canon evidence add --project-id <root-id>
+recorded after the close or the approval. A blocker that names its
+scenarios (`finding add --scenario-id`) asks only those, and the refusal
+names them with the per-scenario command (`canon evidence add --project-id
+<root-id> --scenario-id <id> --report <format>:<path> …`). Otherwise the
+refusal names the scenarios and the batch command: `canon evidence add --project-id <root-id>
 --all-scenarios --report <format>:<path> --kind test-run --role
 implementer --ref "<test command>" …`. Reviews pin what the evidence says
 (its verdict and the identity of its checks), not which record it is, so

package/dist/skills/reference/canon-review.md

@@ -70,11 +70,17 @@ work collapsed into one identity.
 canon finding add --change-id <c> --round <n> --seq <n> \
   --severity blocker|should-fix|note --disposition open \
   --reviewer <who> --summary "<one line>" \
-  [--reviewed-sha <sha>] [--file-ref path/to/file.rs:120-134] [--actor-id <id>] [--session-id <id>]
+  [--reviewed-sha <sha>] [--file-ref path/to/file.rs:120-134] [--scenario-id <id> …] [--actor-id <id>] [--session-id <id>]
 canon finding close --change-id <c> --round <n> --seq <n> \
   --disposition fixed --resolution-sha <sha> [--session-id <id>]   # or rejected / deferred / open
 ```
 
+`--scenario-id` (repeatable, each a scenario the index knows; refused with
+`FINDING_UNKNOWN_SCENARIO` otherwise) names the scenarios the finding is
+about. After a `fixed` close, fresh evidence for those scenarios alone
+re-verifies the fix; a finding naming none asks every evidenced scenario of
+the subject, as before. `finding close` copies the list.
+
 Both stage a candidate. Under `write: { promote: auto }` (what
 `canon init` writes) the same run promotes it and the success line names
 the committed record (``wrote kind=finding/… — staged and promoted in this

package/dist/skills/reference/role-reviewer.md

@@ -12,7 +12,7 @@ a `specs.roots[]` entry in `canon.yaml` (`root` by default).
 ```bash
 canon brief check --change-id <slug> --as reviewer --json
 canon gate check --as reviewer --json                 # once, before review add
-canon finding add --change-id <slug> --round <n> --seq <n> --severity <blocker|should-fix|note> --reviewer <me> --actor-id <me> --session-id <session> --summary "<defect>" --as reviewer --json
+canon finding add --change-id <slug> --round <n> --seq <n> --severity <blocker|should-fix|note> --reviewer <me> --actor-id <me> --session-id <session> --summary "<defect>" --scenario-id <id> --scenario-id <id> --as reviewer --json   # one --scenario-id per scenario the defect is about
 canon finding list --change-id <slug> --open --as reviewer --json
 canon finding close --change-id <slug> --round <n> --seq <n> --disposition fixed --resolution-sha <sha> --as reviewer --json
 canon review add --project-id <root-id> --scenario-id <id> --scenario-id <id> --reviewer <me> --actor-id <me> --role reviewer --session-id <session> --pin <sha> --upstream-ref <ref> --as reviewer --json
@@ -97,8 +97,12 @@ ship guard and stays listed as `accepted-divergence` in `status` and
 - Sign off in one batch with `review add`, all or nothing. It writes
   directly; nothing to promote. canon stores and re-checks attached bytes
   and never compares images.
-- A blocker you close `fixed` stays blocking until the implementer records
-  the whole suite again (`evidence add --all-scenarios`); your pinned review
+- Pass `--scenario-id` for each scenario a finding is about. A blocker you
+  close `fixed` then stays blocking until the implementer records evidence
+  again for those scenarios alone (`evidence add --scenario-id <id> …`); the
+  close inherits the list. A blocker naming no scenario asks for the whole
+  suite again (`evidence add --all-scenarios`), which on a big suite is
+  a long e2e run for a one-scenario fix, so name them. Your pinned review
   stays current when the new evidence says the same, otherwise look again.
 - Fixes you ask for return as a re-review of the same change. When new
   evidence changes a verdict or the checks and so stales your review, look

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@journeykit/canon",
-  "version": "0.24.0",
+  "version": "0.24.1",
   "description": "canon — harness knowledge substrate. JS launcher: platform detection + native binary resolution.",
   "license": "MIT",
   "type": "module",
@@ -30,9 +30,9 @@
   },
   "dependencies": {},
   "optionalDependencies": {
-    "@journeykit/canon-core-darwin-arm64": "0.24.0",
-    "@journeykit/canon-core-linux-x64": "0.24.0",
-    "@journeykit/canon-core-win32-x64": "0.24.0"
+    "@journeykit/canon-core-darwin-arm64": "0.24.1",
+    "@journeykit/canon-core-linux-x64": "0.24.1",
+    "@journeykit/canon-core-win32-x64": "0.24.1"
   },
   "devDependencies": {
     "@types/node": "^20.0.0",