@journeykit/canon 0.29.0 → 0.30.0

package/dist/skills/SKILL.src.md

@@ -219,7 +219,7 @@ before anything is written: an invalid element writes nothing and exits 2,
 ```text
 canon scenario new --input '[{"operands":["auth.login.01"],"title":"Logs in","case":"happy"},{"operands":["auth.login.02"],"title":"Wrong password","case":"failure"}]'
 canon evidence add --input '[{"scenarioId":"auth.login.01","class":"test-run","ref":"npm test","role":"implementer"},{"scenarioId":"auth.login.02","class":"test-run","ref":"npm test","role":"implementer"}]'
-canon finding add --input '[{"changeId":"add-login","round":1,"seq":1,"severity":"note","actorId":"reviewer-1","summary":"Token is logged"},{"changeId":"add-login","round":1,"seq":2,"severity":"blocker","actorId":"reviewer-1","summary":"No rate limit"}]'
+canon finding add --input '[{"changeId":"add-login","round":1,"seq":1,"severity":"note","actorId":"reviewer-1","summary":"Token is logged"},{"changeId":"add-login","round":1,"seq":2,"severity":"blocker","introducedUnknown":true,"actorId":"reviewer-1","summary":"No rate limit"}]'
 ```
 
 `--input` never carries `--commit` or `--plan-digest`, and the destructive
@@ -252,7 +252,7 @@ and `canon context` warn when the repo holds 0.27-era state and put
 2. `canon migrate --commit --plan-digest <digest>` with that digest applies it.
    It moves the layout, rewrites canon's own hooks and scripts, compacts the
    ledger, replaces an old full skill with the stub, and backs up every file it
-   rewrites under `.canon/migrate-backup/`. It refuses uncommitted changes
+   rewrites under `.canon/migrate-backup/` (local and git-ignored; `--revert` needs it). It refuses uncommitted changes
    under a path it moves.
 3. `canon skills install` refreshes the stub and the scripts; `canon skills check`
    confirms them.

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

@@ -205,9 +205,15 @@ Two refusals rather than a silent pass, both surfacing as
   `divergence`, or `subject` sent anywhere but `local`) refuses, because
   the gate reads one tier and would otherwise pass by seeing nothing.
 
-Malformed rows in those three kinds do NOT surface as
+Unparseable rows in those three kinds do NOT surface as
 `malformed-evidence`; they are kept off the evidence violation set on
-purpose, so enabling nothing changes no existing verdict.
+purpose, so enabling nothing changes no existing verdict. A row whose file
+name is not the one its body computes (a layout violation) is the
+exception once `spec_coverage` judges the corpus: the gate names it as
+`malformed-evidence`, because every read skips it and the corpus being
+judged would otherwise be missing it silently. Without the section the
+gate stays as it was; `canon query --kind <kind>` and `canon status`
+report such files.
 
 ### Accepted divergence and re-verification
 

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

@@ -182,7 +182,7 @@ In `canon report`'s own render order. Each panel names the view that
 computes it; nothing here is derived a second time.
 
 - **Trust matrix** (`mart_trust_matrix`) — Change/task coverage × green × who.
-  `covered` means at least one `evidence_record` exists for this `task_id`,
+  `covered` means at least one `evidence` record exists for this `task_id`,
   NOT that policy's REQUIRED evidence is present — that is `canon gate
   check`'s question, and this view deliberately does not answer it. `green`
   is the plain `verdict = 'faithful'` proxy over the latest attestation, not
@@ -258,7 +258,7 @@ computes it; nothing here is derived a second time.
 - **Review rounds** (`mart_review_rounds`) — one row per `(change_id, round)`
   over `Finding` records (`canon finding add`, then `canon finding close` to
   move a finding's disposition), folded to the latest version
-  of each `{change_id}__{round}__{seq}` finding first, so a finding raised
+  of each `(change_id, round, seq)` finding first, so a finding raised
   `open` and later closed is counted once and in one disposition bucket.
   A round that found
   nothing wrote no `Finding` and so has no row: the table

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

@@ -27,7 +27,7 @@ The order an agent follows to claim a subject done:
 
    ```bash
    canon finding add --change-id c-demo --round 1 --seq 1 \
-     --severity blocker --disposition open --actor-id reviewer-2 \
+     --severity blocker --introduced-unknown --disposition open --actor-id reviewer-2 \
      --summary "unbounded subprocess wait" --session-id review-session-1
    # ... fix, commit ...
    canon finding close c-demo --round 1 --seq 1 \
@@ -75,7 +75,7 @@ work collapsed into one identity.
 canon finding add --change-id <c> --round <n> --seq <n> \
   --severity blocker|should-fix|note --disposition open \
   --actor-id <who> --summary "<one line>" \
-  [--rev <rev>] [--resolution-rev <rev>] [--introduced-rev <rev>] [--file-ref path/to/file.rs:120-134] [--scenario-id <id>] [--session-id <id>]
+  [--rev <rev>] [--resolution-rev <rev>] [--introduced-rev <rev> | --introduced-unknown] [--file-ref path/to/file.rs:120-134] [--scenario-id <id>] [--session-id <id>]
 canon finding close <c> --round <n> --seq <n> \
   --disposition fixed --resolution-rev <rev> [--actor-id <id>] [--session-id <id>]   # or rejected / deferred / open
 canon finding close <c> --round <n> --seq <n> \
@@ -111,7 +111,8 @@ takes any git revision (`HEAD~1`, a branch, a tag, a full or short sha),
 resolved with `git rev-parse --verify <rev>^{commit}`; the record stores
 the full sha. `--rev` (the commit the round reviewed) defaults to `HEAD`,
 and so does `--resolution-rev` on a `fixed` close; `--introduced-rev` has
-no default and is only sourced, never guessed. A revision that names no
+no default and is only sourced, never guessed. A new `blocker` or `should-fix`
+needs it or `--introduced-unknown` (never both). A revision that names no
 commit is refused (exit `2`). A finding recorded against uncommitted code
 is allowed: the record carries the `codeTree` it saw and `worktreeDirty`.
 Outside git, or in a repository with no commit, the write is refused with

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

@@ -48,7 +48,7 @@ canon.yaml TierPolicy: `git` is a BACKEND name, not a rung — canon.yaml's
 ## Routing a record kind
 
 `routing:` is the only place a kind's rung is decided. Keys are the
-stable snake_case kind wire strings (`change`, `evidence_record`,
+stable snake_case kind wire strings (`change`, `evidence`,
 `strategy_item`, …) — the same string the record's own `kind` field
 serializes to. Values are `local`/`hot`/`cold`.
 
@@ -132,6 +132,23 @@ has no archive and keeps every version.
 **Done when:** after `canon ledger compact --commit --plan-digest <digest
 from the preview>`, a bare `canon ledger compact` previews no effect.
 
+## How a record is named
+
+Every store names a record the same way: `kind=<kind>/<key>_…_<digest8>.json`.
+One directory level (no `area=`), the kind's key components joined by `_`
+(a record with a `project_id` starts with it, `-` when absent; alternative
+keys carry a tag: `scenario`, `change`, `task`, `run`), and the first 8 hex
+digits of the content's SHA-256 last. Example:
+`kind=review/canon_scenario_gate.check.104_e7f52dd1.json`. A review's pin is
+in its body, not its name, so two reviews of one scenario share a key prefix
+and differ by digest. Free-text ids escape bytes outside `[a-z0-9.-]` as `+`
+and two hex digits. The same key with different content is refused in every
+store. Readers take the digest from the record body, never the name. Evidence
+is `evidence` everywhere (the 0.29 spelling `evidence_record` is gone). A
+0.29 repo warns on read and refuses writes until `canon migrate` (preview),
+then `canon migrate --commit --plan-digest <digest>`, moves it. Full rule:
+`docs/design/ledger-layout.md`.
+
 ## Where artifact bytes live (`artifact_store:`)
 
 ```yaml

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

@@ -216,7 +216,7 @@ The forms you reach for most (the story's ids; swap in yours):
 canon evidence add --all-scenarios --report junit:a.xml --report junit:b.xml --role implementer
 canon evidence add --scenario-id auth.login.01 --report junit:red.xml
 canon evidence add --scenario-id auth.login.01 --verdict divergent --class test-run --ref "upstream limit, tracked in issue 118" --artifact limit.log
-canon finding add --change-id add-login --round 1 --seq 1 --severity should-fix --actor-id unit-1 --summary "Token is logged"
+canon finding add --change-id add-login --round 1 --seq 1 --severity should-fix --introduced-unknown --actor-id unit-1 --summary "Token is logged"
 ```
 
 Batches are one `--input` document (the keys are option names in camelCase,

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

@@ -227,7 +227,7 @@ canon ledger compact
 ```
 ```text
 # Bring a repo from an earlier canon up to date
-canon migrate [--commit --plan-digest <DIGEST>] [--input]
+canon migrate [--commit --plan-digest <DIGEST>] [--revert] [--backup <DIR> (with --revert)] [--input]
 # a bare run previews and prints planDigest; `--commit --plan-digest <DIGEST>` with that digest acts
 ```
 ```bash
@@ -635,14 +635,15 @@ canon skills install
    (which do not count until then; the gate, `status` and `subject move`
    print one advisory naming it) and replaces an old full skill with the
    stub. It backs up every file it rewrites under
-   `.canon/migrate-backup/<timestamp>/`, is safe to run again (a second run
+   `.canon/migrate-backup/<timestamp>/` (local, git-ignored; `--revert` restores from it), is safe to run again (a second run
    finds nothing to move) and refuses uncommitted changes under a path it
    moves: commit first. In CI run it with full history (`fetch-depth: 0`).
 3. `canon skills install` refreshes the stub and the scripts for the selected
    harnesses; `canon skills check` reports a skill written by another canon
    version (exit 1, `SKILLS_DRIFT`), `canon skills doctor` explains it.
 
-Commit what it changes.
+Commit what it changes, except the backup: `.canon/migrate-backup/` is local and
+git-ignored, and `canon migrate --revert` needs it (keep it until you are sure).
 
 **Done when:** `canon migrate` reports nothing left to move, `canon skills
 check` exits 0, and `canon status` and `canon gate check` no longer warn

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

@@ -79,10 +79,10 @@ canon divergence resolve auth.login.01 --actor-id alice --role reviewer
 ```
 ```text
 # Record one code-review finding
-canon finding add --change-id <CHANGE_ID> --round <N> --seq <N> --severity <blocker|should-fix|note> --actor-id <ACTOR_ID> --summary <TEXT> [--disposition <open|fixed|rejected|deferred>] [--rev <REV>] [--resolution-rev <REV>] [--introduced-rev <REV>] [--file-ref <TEXT>] [--scenario-id <SCENARIO_ID>]* [--role <ROLE>] [--session-id <SESSION_ID>] [--promote | --no-promote] [--input]
+canon finding add --change-id <CHANGE_ID> --round <N> --seq <N> --severity <blocker|should-fix|note> --actor-id <ACTOR_ID> --summary <TEXT> [--disposition <open|fixed|rejected|deferred>] [--rev <REV>] [--resolution-rev <REV>] [--introduced-rev <REV>] [--introduced-unknown] [--review-id <REVIEW_ID>] [--file-ref <TEXT>] [--scenario-id <SCENARIO_ID>]* [--role <ROLE>] [--session-id <SESSION_ID>] [--promote | --no-promote] [--input]
 ```
 ```bash
-canon finding add --change-id add-login --round 1 --seq 2 --severity should-fix --actor-id alice --summary "Token is logged"
+canon finding add --change-id add-login --round 1 --seq 2 --severity should-fix --introduced-unknown --actor-id alice --summary "Token is logged"
 ```
 ```text
 # Move an already-committed finding's disposition
@@ -187,7 +187,7 @@ Several findings at once are one `--input` array (the keys are option names
 in camelCase):
 
 ```text
-canon finding add --input '[{"changeId":"add-login","round":1,"seq":3,"severity":"note","actorId":"reviewer-1","summary":"Token is logged"},{"changeId":"add-login","round":1,"seq":4,"severity":"should-fix","actorId":"reviewer-1","summary":"Error text leaks the user name"}]'
+canon finding add --input '[{"changeId":"add-login","round":1,"seq":3,"severity":"note","actorId":"reviewer-1","summary":"Token is logged"},{"changeId":"add-login","round":1,"seq":4,"severity":"should-fix","introducedUnknown":true,"actorId":"reviewer-1","summary":"Error text leaks the user name"}]'
 ```
 
 A review pins what you saw: the scenario's digest plus the verdict

package/man/canon-adapter-authorize.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-adapter-authorize 1  "authorize 0.29.0" 
+.TH canon-adapter-authorize 1  "authorize 0.30.0" 
 .SH NAME
 canon\-adapter\-authorize \- Authorize declared capabilities against repository policy (preflight only)
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-adapter-validate.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-adapter-validate 1  "validate 0.29.0" 
+.TH canon-adapter-validate 1  "validate 0.30.0" 
 .SH NAME
 canon\-adapter\-validate \- Read and validate one provider\-neutral response envelope
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-adapter.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-adapter 1  "adapter 0.29.0" 
+.TH canon-adapter 1  "adapter 0.30.0" 
 .SH NAME
 canon\-adapter \- Validate a provider\-neutral adapter response without executing a provider
 .SH SYNOPSIS
@@ -43,4 +43,4 @@ Examples:
   canon adapter validate \-\-response response.json
   canon adapter validate \-\-response response.json \-\-repo . \-\-json
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-artifacts-move.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-artifacts-move 1  "move 0.29.0" 
+.TH canon-artifacts-move 1  "move 0.30.0" 
 .SH NAME
 canon\-artifacts\-move \- Move the local artifact blobs to an object\-store tier, verify them, and remove the local copies
 .SH SYNOPSIS
@@ -60,4 +60,4 @@ The bare run previews: it lists every upload and removal and prints a planDigest
 
 Idempotent and resumable: a run stopped anywhere leaves a repo the gate still passes, and the next run finishes; a second run finds nothing to do. A blob whose bytes do not match its name is never moved. Moving back to local is refused; `\-\-tier local` on a local repo is a no\-op.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-artifacts-store.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-artifacts-store 1  "store 0.29.0" 
+.TH canon-artifacts-store 1  "store 0.30.0" 
 .SH NAME
 canon\-artifacts\-store \- Store the bound files of existing evidence records and current reviews in the artifact store (.canon/artifacts/sha256/)
 .SH SYNOPSIS
@@ -51,4 +51,4 @@ For records written before canon stored bound bytes (0.11\-0.13), and for any ev
 
 Exit 0 when the pass ran (the gate decides whether an unstored file matters), 2 when the ledger cannot be read or a write fails.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-artifacts-verify.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-artifacts-verify 1  "verify 0.29.0" 
+.TH canon-artifacts-verify 1  "verify 0.30.0" 
 .SH NAME
 canon\-artifacts\-verify \- Check that the artifact store holds every file the latest evidence and current reviews bind (\-\-full re\-hashes the stored bytes)
 .SH SYNOPSIS
@@ -45,4 +45,4 @@ Asks the store canon.yaml\*(Aqs `artifacts:` block selects (default: local, .can
 
 Exit 0 when every file is stored, 1 when one is missing or altered (data.problems names each), 2 when the store cannot be used or reached: an unreachable store is a refusal, never a pass.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-artifacts.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-artifacts 1  "artifacts 0.29.0" 
+.TH canon-artifacts 1  "artifacts 0.30.0" 
 .SH NAME
 canon\-artifacts \- Check or move the evidence artifact store (local, or an object\-store tier)
 .SH SYNOPSIS
@@ -42,4 +42,4 @@ Store the bound files of existing evidence records and current reviews in the ar
 canon\-artifacts\-move(1)
 Move the local artifact blobs to an object\-store tier, verify them, and remove the local copies
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-brief-approve.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-brief-approve 1  "approve 0.29.0" 
+.TH canon-brief-approve 1  "approve 0.30.0" 
 .SH NAME
 canon\-brief\-approve \- Record the human\*(Aqs approval of the brief, bound to its text; refused while `brief check` has blockers
 .SH SYNOPSIS
@@ -59,4 +59,4 @@ brief (the digest covers the brief without its `Approved:` lines) and records
 not approved (BRIEF_CHANGED_SINCE_APPROVAL) until a human answers again and this
 runs again. Run it only from the human\*(Aqs answer, with their words as \-\-note.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-brief-check.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-brief-check 1  "check 0.29.0" 
+.TH canon-brief-check 1  "check 0.30.0" 
 .SH NAME
 canon\-brief\-check \- Read the brief against the rules: blocker and advisory findings (exit 0 clean, 1 blockers, 2 refused)
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print version
 [\fICHANGE_ID\fR]
 The change to read (default: the repo\*(Aqs only live change)
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-brief-show.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-brief-show 1  "show 0.29.0" 
+.TH canon-brief-show 1  "show 0.30.0" 
 .SH NAME
 canon\-brief\-show \- Show where the change stands and the next one to three steps; never edits
 .SH SYNOPSIS
@@ -47,4 +47,4 @@ Examples:
 
 The operand names the change; without it the repo\*(Aqs only live change is read.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-brief.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-brief 1  "brief 0.29.0" 
+.TH canon-brief 1  "brief 0.30.0" 
 .SH NAME
 canon\-brief \- Check a change\*(Aqs brief (PRD format) and see the next steps; never edits
 .SH SYNOPSIS
@@ -60,4 +60,4 @@ Waive one rule in one section with
 A brief without markers (written before 0.19) checks as `brief.legacy`, an
 advisory. Without \-\-change\-id, the repo\*(Aqs only live change is checked.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-change-new.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-change-new 1  "new 0.29.0" 
+.TH canon-change-new 1  "new 0.30.0" 
 .SH NAME
 canon\-change\-new \- Write .canon/changes/<slug>/brief.md, import it, and adopt it into a subject
 .SH SYNOPSIS
@@ -63,4 +63,4 @@ Print version
 <\fICHANGE_ID\fR>
 The change\*(Aqs slug (its change_id)
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-change.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-change 1  "change 0.29.0" 
+.TH canon-change 1  "change 0.30.0" 
 .SH NAME
 canon\-change \- Write a plan change (.canon/changes/<slug>/brief.md) and adopt it into a subject
 .SH SYNOPSIS
@@ -39,4 +39,4 @@ Write .canon/changes/<slug>/brief.md, import it, and adopt it into a subject
 Examples:
   canon change new add\-login \-\-subject\-id auth \-\-title \*(AqAdd login\*(Aq
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-completion.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-completion 1  "completion 0.29.0" 
+.TH canon-completion 1  "completion 0.30.0" 
 .SH NAME
 canon\-completion \- Write the shell completion script for canon (bash, zsh or fish)
 .SH SYNOPSIS
@@ -57,4 +57,4 @@ Examples:
 
 The script is generated from the command tree, so it completes exactly what the parser accepts. It needs no repo and no network.
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-context-pack-add.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-context-pack-add 1  "add 0.29.0" 
+.TH canon-context-pack-add 1  "add 0.30.0" 
 .SH NAME
 canon\-context\-pack\-add \- Create an immutable context pack from a repository\-local JSON manifest
 .SH SYNOPSIS
@@ -44,4 +44,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-context-pack-show.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-context-pack-show 1  "show 0.29.0" 
+.TH canon-context-pack-show 1  "show 0.30.0" 
 .SH NAME
 canon\-context\-pack\-show \- Show a context pack after verifying its manifest and content objects
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print version
 <\fIPACK_ID\fR>
 Context pack id (sha256:<64 hex digits>)
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-context-pack-verify.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-context-pack-verify 1  "verify 0.29.0" 
+.TH canon-context-pack-verify 1  "verify 0.30.0" 
 .SH NAME
 canon\-context\-pack\-verify \- Verify a context pack\*(Aqs manifest and immutable content objects
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print version
 <\fIPACK_ID\fR>
 Context pack id (sha256:<64 hex digits>)
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-context-pack.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-context-pack 1  "context-pack 0.29.0" 
+.TH canon-context-pack 1  "context-pack 0.30.0" 
 .SH NAME
 canon\-context\-pack \- Create, inspect, and verify reproducible context packs
 .SH SYNOPSIS
@@ -47,4 +47,4 @@ Examples:
   canon context\-pack show sha256:<pack\-digest> \-\-repo . \-\-json
   canon context\-pack verify sha256:<pack\-digest>
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-context.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-context 1  "context 0.29.0" 
+.TH canon-context 1  "context 0.30.0" 
 .SH NAME
 canon\-context \- Show what you can author here: record kinds, fields, enums, policies
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-dashboard.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-dashboard 1  "dashboard 0.29.0" 
+.TH canon-dashboard 1  "dashboard 0.30.0" 
 .SH NAME
 canon\-dashboard \- Serve the local status dashboard
 .SH SYNOPSIS
@@ -47,4 +47,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-demo-init.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-demo-init 1  "init 0.29.0" 
+.TH canon-demo-init 1  "init 0.30.0" 
 .SH NAME
 canon\-demo\-init \- Scaffold the demo repo (gate starts RED)
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-demo-review.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-demo-review 1  "review 0.29.0" 
+.TH canon-demo-review 1  "review 0.30.0" 
 .SH NAME
 canon\-demo\-review \- Record the missing reviewer evidence (gate turns GREEN)
 .SH SYNOPSIS
@@ -41,4 +41,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-demo.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-demo 1  "demo 0.29.0" 
+.TH canon-demo 1  "demo 0.30.0" 
 .SH NAME
 canon\-demo \- Try the evidence loop end\-to\-end in a throwaway demo repo
 .SH SYNOPSIS
@@ -44,4 +44,4 @@ Examples:
   canon gate check   # RED
   canon demo review && canon gate check   # GREEN
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-dispatch-begin.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-dispatch-begin 1  "begin 0.29.0" 
+.TH canon-dispatch-begin 1  "begin 0.30.0" 
 .SH NAME
 canon\-dispatch\-begin \- Mint a Run manifest with retrieved guidance and context/policy lineage
 .SH SYNOPSIS
@@ -77,4 +77,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-dispatch-diff.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-dispatch-diff 1  "diff 0.29.0" 
+.TH canon-dispatch-diff 1  "diff 0.30.0" 
 .SH NAME
 canon\-dispatch\-diff \- Diff the declared plan DAG against the observed execution graph
 .SH SYNOPSIS
@@ -38,4 +38,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-dispatch-end.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-dispatch-end 1  "end 0.29.0" 
+.TH canon-dispatch-end 1  "end 0.30.0" 
 .SH NAME
 canon\-dispatch\-end \- Close a dispatched run with a terminal status and an ended_at
 .SH SYNOPSIS
@@ -57,4 +57,4 @@ Print version
 <\fIRUN_ID\fR>
 The RunId (ULID) minted by `canon dispatch begin`
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-dispatch.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-dispatch 1  "dispatch 0.29.0" 
+.TH canon-dispatch 1  "dispatch 0.30.0" 
 .SH NAME
 canon\-dispatch \- Begin an agent run with retrieved guidance recorded
 .SH SYNOPSIS
@@ -42,4 +42,4 @@ Close a dispatched run with a terminal status and an ended_at
 canon\-dispatch\-diff(1)
 Diff the declared plan DAG against the observed execution graph
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-divergence-accept.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-divergence-accept 1  "accept 0.29.0" 
+.TH canon-divergence-accept 1  "accept 0.30.0" 
 .SH NAME
 canon\-divergence\-accept \- Accept a divergent scenario as a tracked known gap (a reviewer step): its latest evidence must be divergent and not the accepting actor\*(Aqs or session\*(Aqs. The acceptance pins that evidence, so new evidence ends it, and lapses at \-\-expiry; until then the ship guard counts the cell as covered while `status` and `gate check` list it as `accepted\-divergence`
 .SH SYNOPSIS
@@ -65,4 +65,4 @@ Print version
 <\fISCENARIO_ID\fR>
 The accepted scenarios (`<area>.<surface>.<nn>`), one acceptance each, all or nothing
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-divergence-add.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-divergence-add 1  "add 0.29.0" 
+.TH canon-divergence-add 1  "add 0.30.0" 
 .SH NAME
 canon\-divergence\-add \- Add a divergence candidate, staged with no run_seq yet (commit it with `canon gate promote \-\-kind divergence`, or in the same run with \-\-promote / `write: { promote: auto }`)
 .SH SYNOPSIS
@@ -94,4 +94,4 @@ Print version
 <\fISCENARIO_ID\fR>
 The scenario (`<area>.<surface>.<nn>`)
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-divergence-defer.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-divergence-defer 1  "defer 0.29.0" 
+.TH canon-divergence-defer 1  "defer 0.30.0" 
 .SH NAME
 canon\-divergence\-defer \- Directly record a deferred divergence (requires \-\-reason/\-\-expiry)
 .SH SYNOPSIS
@@ -68,4 +68,4 @@ Print version
 <\fISCENARIO_ID\fR>
 The scenario (`<area>.<surface>.<nn>`)
 .SH VERSION
-v0.29.0
+v0.30.0

package/man/canon-divergence-list.1

@@ -1,6 +1,6 @@
 .ie \n(.g .ds Aq \(aq
 .el .ds Aq '
-.TH canon-divergence-list 1  "list 0.29.0" 
+.TH canon-divergence-list 1  "list 0.30.0" 
 .SH NAME
 canon\-divergence\-list \- List the current divergence burn\-down state
 .SH SYNOPSIS
@@ -53,4 +53,4 @@ Print help
 \fB\-V\fR, \fB\-\-version\fR
 Print version
 .SH VERSION
-v0.29.0
+v0.30.0