@journeykit/canon 0.36.0 → 0.37.0

package/dist/skills/SKILL.src.md

@@ -127,7 +127,11 @@ tree, or in a repo with no commits, a command that needs a commit refuses
 After a chore approval or a reopen, a scenario whose latest evidence was
 recorded on the current `codeTree` needs nothing new: a docs-only chore then
 needs its change-level review alone. What counts as code is `code.exclude` in
-`canon.yaml` (globs, default `docs/**` and `*.md`). When code did change,
+`canon.yaml` (globs, default `docs/**` and `*.md`). A chore approved over the
+code as it still is (the `(code tree <id>)` of its `Approved:` line is the
+current tree) asks for no evidence at all, whatever tree the evidence is on, and
+`status` says so; an approval with no recorded tree follows the rule above.
+When code did change,
 `canon status`, `meta.next` and the refusal hint lead with one batch over
 every report, for example
 `canon evidence add --all-scenarios --report junit:a.xml --report junit:b.xml --role implementer`
@@ -227,11 +231,18 @@ A role is guidance, not enforcement: `--role` on `evidence add` and
   gives the JSON Schema of each report in `schemas`, `Input` (the schema of one `--input`
   document) and `rejects` (what each validator refuses, in order); `#/schemas/<Name>` in
   the command document resolves there. The first line of every `--help` points at it.
+- An option of the same name takes the same value in every command that has it, and `canon schema` declares it once. An id
+  (`--project`, `--role`, `--domain`) is a kebab slug: lowercase letters and digits, single hyphens between them. A name
+  (`--actor`, `--approver`, `--relayed-via`) and a sentence (`--reason`, `--summary`, `--override-reason`) are one line of text:
+  the white space around it is trimmed (what is recorded, and what a signature is made of, is the trimmed text), and a value
+  that is empty once trimmed, or has a control character (a tab, an escape) or a line break inside it, is refused with the
+  command's own argument code. `--round` and `--limit` start at 1, and `--regime` is the four-part key `retrieve` and
+  `dispatch begin` both take. `finding close` takes `fixed`, `rejected` or `deferred`, never `open`.
 - Pass `--json` and read stdout as one document, nothing on stderr. Success is
   `{"ok":true,"data":…,"meta":…}`; failure is
   `{"ok":false,"error":{…},"meta":…}` (a check that fails keeps its report in
   `data`). `meta` carries `tool`, `toolVersion`, `contract` (`atip/1`),
-  `contractVersion` (`1.4`), `schemaVersion`,
+  `contractVersion` (`1.5`), `schemaVersion`,
   `command`, and when present `next`, `warnings` (`[{code, message}]`) and
   `page`; a repeated write that changed nothing reports `data.unchanged: true`.
   Absent members are omitted, never `null` or `[]` (a value you sent empty comes back as `received: ""`).

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

@@ -255,6 +255,17 @@ review of the chore itself (`canon review change <slug>`) before
 `--to shipped`; a changed verdict or case set stales that scenario's
 review as before (and a new `divergence accept`, where the gap remains).
 
+A chore's approval records the code tree of the work tree at that moment, as
+`(code tree <id>)` in its `Approved:` line (outside the brief digest; none
+outside git or with no commit). While that tree is the current code tree the
+chore changed no code since it was approved, so it asks for no evidence at
+all, whatever tree each scenario's latest evidence is on, and `status` says so
+on its line; its change-level review is still asked, and it must be a review of
+this code (the review records the code tree it saw): a brief edited after the
+approval needs a new review, and so does a review of other code, as when the
+same brief is approved again over code that came after the review. An approval
+with no recorded tree (written before 0.37) follows the rule above.
+
 ### Audit records (`canon evidence audit`)
 
 canon never generates or runs an audit. An external evaluator does, and

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

@@ -52,7 +52,11 @@ The production activation path is a signed, paired-evaluation workflow:
    `meta.next` names the human signing step. The `data` contains the evaluation digest, RFC3339 `approved_at`,
    subject `strategy:<strategy_id>`, namespace
    `canon-learning-approval-v1`, and `payload_hex`. `approval-payload` never
-   reads a private key and never sets `verified`.
+   reads a private key and never sets `verified`. `--approval-at` is an RFC 3339
+   date-time (`2026-10-02T12:00:00Z`; a date alone, white space around it and a
+   one-digit month are refused): canon never stamps it, so fix it once and give
+   the same value to the signature and to the record. The bytes hold the instant
+   as UTC to the nanosecond, so one instant written `Z` or `+09:00` is one payload.
 6. Decode `payload_hex` to the exact canonical JSON bytes. The signed object
    is:
 
@@ -190,7 +194,8 @@ canon strategy rollback <strategy_id> --reason "<reason>" --actor alice \
 
 `--signature-file` is an armored SSH detached signature over the
 `canon-learning-approval-v1` payload bound to
-`strategy:<id>:rollback:<sha256(reason)>`, actor, and `--approval-at`.
+`strategy:<id>:rollback:<sha256(reason)>`, actor, and `--approval-at` (the same
+RFC 3339 date-time that was signed; another instant fails the signature).
 `actor` MUST be listed in policy-pinned `approval.allowed_signers`; verification
 uses that file and `ssh-keygen -Y verify`. Successful rollback writes durable
 provenance, sets lifecycle `rolled_back`, and records the optional contradicting

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

@@ -155,7 +155,7 @@ text in the summary, not a field.
 
 | Disposition | Meaning |
 |---|---|
-| `open` | Raised and not yet dealt with. The default on `finding add`; `finding close --disposition open` reopens. |
+| `open` | Raised and not yet dealt with. The default on `finding add`; `finding close` refuses it (a defect that came back is a new finding). |
 | `fixed` | Fixed by a commit. Carries `--resolution-rev <rev>` (default `HEAD`) naming a commit this repo holds; only `fixed` may carry one. |
 | `rejected` | The reviewer's point was considered and declined. Needs `--reason`. |
 | `deferred` | Accepted, but postponed to later work. Needs `--reason`. |
@@ -164,8 +164,10 @@ text in the summary, not a field.
 
 Every reader takes the **latest version per natural key**
 `(change_id, round, seq)` — the same fold the report's finding panel
-uses. A blocker raised `open` and later closed `fixed` counts as fixed; a
-fixed finding reopened with `--disposition open` counts as open again.
+uses. A blocker raised `open` and later closed `fixed` counts as fixed.
+A finding is not reopened: `finding close` takes `fixed`, `rejected` or
+`deferred` and refuses `--disposition open`; a defect that came back is a new
+`finding add` (the next `--seq`).
 
 ## `canon review scenario`
 

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

@@ -192,7 +192,7 @@ section listing them and emits a matching stderr `WARN`.
 
 ## Retention, export, and access audit
 
-`canon purge --kind <kind> --before <RFC3339> [--commit --plan-digest <planDigest>] [--repo <dir>] [--json]`
+`canon purge --kind <kind> --before <RFC3339 date or date-time> [--commit --plan-digest <planDigest>] [--repo <dir>] [--json]`
 is the canonical data-lifecycle boundary: the bare run previews: it prints the removal set and
 its `planDigest` and deletes nothing; `--commit --plan-digest <planDigest>` deletes only if
 the plan recomputed now has the same digest (`PLAN_STALE`, exit 2, when the
@@ -220,7 +220,7 @@ human's review and `--commit --plan-digest`), and an export's page state (`total
 file and answers with `data: { output, kind, recordCount }`; `--dry-run`
 answers with what it would write and writes nothing.
 
-`canon export --kind <kind> [--before <RFC3339>] [--after <RFC3339>]
+`canon export --kind <kind> [--before <RFC3339 date or date-time>] [--after <RFC3339 date or date-time>]
 [--output <file>] [--json] [--limit <n> | --all] [--cursor <c>]` emits a versioned manifest containing source scope,
 counts, digests, and redacted metadata. It does not authorize backend access;
 credentials remain an operator prerequisite. New output files are mode

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

@@ -547,8 +547,9 @@ warn, and a command that writes and judges it is refused
   `reason`), one rule in one section, reason required; add `match` to waive
   only the findings whose matched text contains it. Listed in the output.
 - **`approve`** records the human's answer: it writes
-  `Approved: <who> <when> — "<words>" (brief sha256:<digest>)` into the
-  brief and records the policy approval in the same call. It refuses
+  `Approved: <who> <when> — "<words>" (code tree <id>) (brief sha256:<digest>)`
+  into the brief (the code tree, 0.37, is the work tree's as it is now and is
+  left out outside git or with no commit) and records the policy approval in the same call. It refuses
   (exit 2) while the check has structure blockers. Edit the brief
   afterwards and every reader says `BRIEF_APPROVAL_STALE` until a
   human answers again and `approve` runs again. Run it only from the
@@ -617,8 +618,8 @@ uses, so status and the gate cannot disagree about a gap:
   something after it, and sits outside HTML comments (`<!-- … -->`,
   multi-line included) and fenced code blocks (```` ``` ```` or `~~~`).
   `canon brief approve` writes it from the human's answer, as
-  `Approved: <who> <when> — "<the human's words>" (brief sha256:<digest>)`,
-  the digest covering the brief without its `Approved:` lines. A brief
+  `Approved: <who> <when> — "<the human's words>" (code tree <id>) (brief sha256:<digest>)`,
+  the digest covering the brief without its `Approved:` lines (the tree marker is outside it; a line without one is read as before). A brief
   edited after that reads `brief: not approved (<brief> changed after its
   approval (BRIEF_APPROVAL_STALE))` and names the re-approval
   command: the changed brief needs a new human answer. A line with no

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

@@ -342,7 +342,9 @@ canon evidence add --input '[{"scenario":"auth.login.01","class":"test-run","ref
    latest evidence was recorded on a different `codeTree` than the current
    code (`code.exclude` in `canon.yaml` decides what is not code; the default
    is `docs/**` and `*.md`). A docs-only chore needs its change-level review
-   alone. When code did change, the shipping refusal, `status` and
+   alone, and so does a chore whose approval recorded the code tree that is
+   still the current one (`(code tree <id>)` in its `Approved:` line; `status`
+   says so): it asks for no evidence at all. When code did change, the shipping refusal, `status` and
    `meta.next` lead with one command over every report, with the real paths
    (`--project <id>` is added only with several spec roots):
    `canon evidence add --all-scenarios --report junit:a.xml --report junit:b.xml --role implementer`.

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

@@ -87,7 +87,7 @@ canon finding add --change add-login --round 1 --seq 2 --severity should-fix --i
 ```
 ```text
 # Move an already-committed finding's disposition
-usage: canon finding close <CHANGE_ID> --round <N> --seq <N> --disposition <open|fixed|rejected|deferred> [--resolution-rev <REV>] [--reason <TEXT>] [--actor <ACTOR_ID>] [--role <ROLE>] [--session <SESSION_ID>] [--promote | --no-promote] [--input]
+usage: canon finding close <CHANGE_ID> --round <N> --seq <N> --disposition <fixed|rejected|deferred> [--resolution-rev <REV>] [--reason <TEXT>] [--actor <ACTOR_ID>] [--role <ROLE>] [--session <SESSION_ID>] [--promote | --no-promote] [--input]
 ```
 ```bash
 canon finding close add-login --round 1 --seq 1 --disposition rejected --reason "works as designed" --json

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.36.0" 
+.TH canon-adapter-authorize 1  "authorize 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-adapter-validate 1  "validate 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-adapter 1  "adapter 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-artifacts-move 1  "move 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-artifacts-store 1  "store 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-artifacts-verify 1  "verify 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-artifacts 1  "artifacts 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-brief-approve 1  "approve 0.37.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
@@ -66,10 +66,12 @@ Examples:
 Several ids take one name, one answer and one timestamp. Every id is checked
 first; one refused id refuses the call (the first refused id\*(Aqs code, with a
 detail for each) and nothing is
-written. Writes `Approved: <who> <when> — "<words>" (brief sha256:<digest>)` into the
-brief (the digest covers the brief without its `Approved:` lines) and records
+written. Writes `Approved: <who> <when> — "<words>" (code tree <id>) (brief sha256:<digest>)` into the
+brief (the digest covers the brief without its `Approved:` lines; the code tree is the work
+tree\*(Aqs as it is now, uncommitted code included, and is left out outside git or with no commit: a
+chore whose approval saw the code tree that is still the current one asks for no evidence) and records
 `canon policy approve` in the same call. Edit the brief afterwards and it reads as
 not approved (BRIEF_APPROVAL_STALE) 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.36.0
+v0.37.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.36.0" 
+.TH canon-brief-check 1  "check 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-brief-show 1  "show 0.37.0" 
 .SH NAME
 canon\-brief\-show \- Show where the change stands and the next one to three steps; never edits
 .SH SYNOPSIS
@@ -50,4 +50,4 @@ Examples:
 
 The operand names the change; without it the repo\*(Aqs only live change is read.
 .SH VERSION
-v0.36.0
+v0.37.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.36.0" 
+.TH canon-brief 1  "brief 0.37.0" 
 .SH NAME
 canon\-brief \- Check a change\*(Aqs brief (PRD format) and see the next steps; never edits
 .SH SYNOPSIS
@@ -61,4 +61,4 @@ gets one blocker, `brief.old\-format`: `canon migrate` rewrites it. A brief
 with fewer than two known headings (written before 0.19) checks as `brief.legacy`, an
 advisory. Without \-\-change, the repo\*(Aqs only live change is checked.
 .SH VERSION
-v0.36.0
+v0.37.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.36.0" 
+.TH canon-change-new 1  "new 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-change 1  "change 0.37.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 auth \-\-title \*(AqAdd login\*(Aq
 .SH VERSION
-v0.36.0
+v0.37.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.36.0" 
+.TH canon-completion 1  "completion 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-context-pack-add 1  "add 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-context-pack-show 1  "show 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-context-pack-verify 1  "verify 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-context-pack 1  "context-pack 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-context 1  "context 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-dashboard 1  "dashboard 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-demo-init 1  "init 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-demo-review 1  "review 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-demo 1  "demo 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-dispatch-begin 1  "begin 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-dispatch-diff 1  "diff 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-dispatch-end 1  "end 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-dispatch 1  "dispatch 0.37.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.36.0
+v0.37.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.36.0" 
+.TH canon-divergence-accept 1  "accept 0.37.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
@@ -36,7 +36,7 @@ Why the gap is accepted
 Where the gap is tracked: an issue URL or reference
 .TP
 \fB\-\-expiry\fR \fI<TIMESTAMP>\fR
-The date (YYYY\-MM\-DD, UTC) the acceptance stops holding; none means it holds until new evidence
+When the acceptance stops holding: an RFC 3339 date (`2030\-01\-01`, UTC midnight) or date\-time (`2030\-01\-01T10:00:00Z`); none means it holds until new evidence
 .TP
 \fB\-\-actor\fR \fI<ACTOR_ID>\fR
 The reviewer recording this (recorded as the divergence\*(Aqs reviewer and actor)
@@ -74,4 +74,4 @@ Print version
 <\fISCENARIO_ID\fR>
 The accepted scenarios (`<area>.<surface>.<nn>`), one acceptance each, all or nothing
 .SH VERSION
-v0.36.0
+v0.37.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.36.0" 
+.TH canon-divergence-add 1  "add 0.37.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
@@ -53,7 +53,7 @@ deferred
 Why the divergence is recorded; required with `\-\-state deferred`
 .TP
 \fB\-\-expiry\fR \fI<TIMESTAMP>\fR
-When a deferral lapses (RFC3339 or YYYY\-MM\-DD, UTC); required with `\-\-state deferred`
+When a deferral lapses: an RFC 3339 date (`2030\-01\-01`, UTC midnight) or date\-time (`2030\-01\-01T10:00:00Z`); required with `\-\-state deferred`
 .TP
 \fB\-\-round\fR \fI<N>\fR [default: 1]
 The review round this version belongs to (1\-based)
@@ -94,4 +94,4 @@ Print version
 <\fISCENARIO_ID\fR>
 The scenario (`<area>.<surface>.<nn>`)
 .SH VERSION
-v0.36.0
+v0.37.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.36.0" 
+.TH canon-divergence-defer 1  "defer 0.37.0" 
 .SH NAME
 canon\-divergence\-defer \- Directly record a deferred divergence (requires \-\-reason/\-\-expiry)
 .SH SYNOPSIS
@@ -45,7 +45,7 @@ The acting session (recorded as actor.session_id); optional
 Why the divergence is deferred
 .TP
 \fB\-\-expiry\fR \fI<TIMESTAMP>\fR
-When the deferral lapses (RFC3339 or YYYY\-MM\-DD, UTC)
+When the deferral lapses: an RFC 3339 date (`2030\-01\-01`, UTC midnight) or date\-time (`2030\-01\-01T10:00:00Z`)
 .TP
 \fB\-\-role\fR \fI<ROLE>\fR
 The role this record is attributed to (default: the role declared with \-\-as / CANON_ROLE)
@@ -68,4 +68,4 @@ Print version
 <\fISCENARIO_ID\fR>
 The scenario (`<area>.<surface>.<nn>`)
 .SH VERSION
-v0.36.0
+v0.37.0