@journeykit/canon 0.8.0 → 0.9.0

package/dist/skills/reference/canon-report-dashboard.md

@@ -216,10 +216,12 @@ computes it; nothing here is derived a second time.
   Per-domain subject rollup: status × scenario coverage.
   One row per `subject` record, folded to its latest version, so a subject
   that walked proposed → shipped is still one row. `scenario_count` is how
-  many `scenario_ids` the subject links; `covered_scenarios` is how many of
-  those carry a latest NON-divergent evidence verdict (`faithful` or
-  `not_applicable`), the same last-wins fold the `verifying -> shipped` gate
-  uses. Read-only reporting; never a `canon gate` input. See `canon-subject`.
+  many scenarios the subject owns — those whose latest synced `Scenario`
+  generation carries `@subject:<id>` (run `canon inventory sync` after
+  tagging); `covered_scenarios` is how many of those carry a latest
+  NON-divergent evidence verdict (`faithful` or `not_applicable`), the same
+  join and last-wins fold the `verifying -> shipped` gate uses. Read-only
+  reporting; never a `canon gate` input. See `canon-subject`.
 
 - **Review rounds** (`mart_review_rounds`) — one row per `(change_id, round)`
   over `Finding` records (`canon finding add`, then `canon finding close` to

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

@@ -14,8 +14,17 @@ domain agent follows.
   A Subject is the product unit; its `.feature` files are its behavior
   specs. Never the same word.
 
-A Subject links, but does not contain, its work: `change_ids` (adopted
-plan units) and `scenario_ids` (behavior specs) are join links.
+A Subject links, but does not contain, its work. Two joins, each
+authored in one place:
+
+- **Changes**: `change_ids` on the Subject, appended by `canon subject
+  adopt`.
+- **Scenarios**: the `@subject:<id>` tag on each Gherkin scenario,
+  indexed onto `Scenario.subject_id` by `canon inventory sync`. The
+  Subject record carries no scenario list — the spec corpus is the only
+  source, and the Subjects report panel, `spec_coverage.scope`, and the
+  shipped gate all read it from there. To link a scenario, tag it and
+  re-sync; there is no subject-side command for it.
 
 ## The 4-step loop
 
@@ -52,8 +61,8 @@ canon subject new subject-domain-loop \
   `canon context` to see the set in force.
 - `--summary` is optional; `--owner-role` defaults to `implementer`;
   `--actor-id` defaults to `canon`. A freshly-authored Subject with no
-  `change_ids`/`scenario_ids` is a valid minimal record and starts at
-  status `proposed`. `--json` prints the written record.
+  adopted changes and no tagged scenarios is a valid minimal record and
+  starts at status `proposed`. `--json` prints the written record.
 
 ### 2. Retrieve subject-scoped strategy memory BEFORE working
 
@@ -120,12 +129,14 @@ blocking to subjects in named statuses, and `@subject:<id>` tagging is
 what brings a scenario into that scope. See `canon-gate`.
 
 **The `verifying → shipped` evidence gate:** shipping additionally
-requires that EVERY linked `scenario_ids` entry carries a latest,
-non-`Divergent` verdict in the ledger (the same last-wins rule `canon
-gate check` uses). If any linked scenario is uncovered or its latest
-verdict is `Divergent`, the transition prints the violating scenarios by
-failure class, exits 1, and the status stays `verifying`. `retired` is
-not gated.
+requires that the Subject OWNS at least one scenario (one whose latest
+synced generation carries `@subject:<id>`), and that EVERY owned
+scenario carries a latest, non-`Divergent` verdict in the ledger (the
+same last-wins rule `canon gate check` uses). A Subject with no tagged
+scenario is refused rather than shipped on an empty set; so is one whose
+`scenario` records route away from the gate's rung. Each refusal prints
+by failure class (`uncovered-cell`), exits 1, and the status stays
+`verifying`. `retired` is not gated.
 
 ## Adopt flow
 

package/package.json

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