@journeykit/canon 0.27.0 → 0.29.0

package/man/canon-ledger-compact.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-ledger-compact 1  "compact 0.29.0" 
+.SH NAME
+canon\-ledger\-compact \- Move superseded versions of every record out of the ledger into the archive
+.SH SYNOPSIS
+\fBcanon ledger compact\fR [\fB\-\-as\fR] [\fB\-\-commit\fR] [\fB\-\-plan\-digest\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Move superseded versions of every record out of the ledger into the archive
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-commit\fR
+Act on the previewed plan; needs \-\-plan\-digest
+.TP
+\fB\-\-plan\-digest\fR \fI<DIGEST>\fR
+The `planDigest` the preview printed; the run acts only if the plan recomputed now has this digest
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-\-input\fR \fI<JSON|FILE|\->\fR
+The arguments as JSON: an object (one run) or an array / NDJSON file or `\-` (a batch); keys are the option names in camelCase, `operands` an array
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH VERSION
+v0.29.0

package/man/canon-ledger.1

@@ -0,0 +1,54 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-ledger 1  "ledger 0.29.0" 
+.SH NAME
+canon\-ledger \- Keep the ledger to the current version of each record
+.SH SYNOPSIS
+\fBcanon ledger\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Keep the ledger to the current version of each record
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH SUBCOMMANDS
+.TP
+canon\-ledger\-compact(1)
+Move superseded versions of every record out of the ledger into the archive
+.SH EXTRA
+Examples:
+  canon ledger compact
+  canon ledger compact \-\-commit \-\-plan\-digest <DIGEST>
+
+The bare run previews the move and prints its planDigest.
+
+Moves every superseded version of a record (an evidence record a newer one replaced, a
+scenario or finding rewritten since) from .canon/ledger to .canon/archive, once. The
+ledger then holds the current decision per key, and every default read (status, gate
+check, guards, query) reads only that; `canon query \-\-kind <kind> \-\-history` reads the
+archive too. Appending a new version moves the versions it supersedes on its own, so
+this is for a ledger written before 0.23, or after an interrupted move. Idempotent;
+`canon migrate` runs it. A record that carries a standing claim (a flagged overlay, a
+brief override, an approval at the current evidence) stays in the ledger.
+.SH VERSION
+v0.29.0

package/man/canon-migrate.1

@@ -0,0 +1,89 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-migrate 1  "migrate 0.29.0" 
+.SH NAME
+canon\-migrate \- Bring a repo from an earlier canon up to date: the 0.17 layout (specs, changes, approvals, skills, .gitignore), the 0.28 hooks, scripts and skill stub (backed up under .canon/migrate\-backup/), the 0.23 latest\-only ledger (superseded versions to .canon/archive) and 0.23 review pins
+.SH SYNOPSIS
+\fBcanon migrate\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-commit\fR] [\fB\-\-plan\-digest\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Bring a repo from an earlier canon up to date: the 0.17 layout (specs, changes, approvals, skills, .gitignore), the 0.28 hooks, scripts and skill stub (backed up under .canon/migrate\-backup/), the 0.23 latest\-only ledger (superseded versions to .canon/archive) and 0.23 review pins
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-commit\fR
+Act on the previewed plan; needs \-\-plan\-digest
+.TP
+\fB\-\-plan\-digest\fR \fI<DIGEST>\fR
+The `planDigest` the preview printed; the run acts only if the plan recomputed now has this digest
+.TP
+\fB\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-\-input\fR \fI<JSON|FILE|\->\fR
+The arguments as JSON: an object (one run) or an array / NDJSON file or `\-` (a batch); keys are the option names in camelCase, `operands` an array
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH EXTRA
+Examples:
+  canon migrate
+  canon migrate \-\-commit \-\-plan\-digest <DIGEST>
+
+The bare run prints the plan and its planDigest and writes nothing; \-\-commit \-\-plan\-digest applies exactly that plan. Idempotent:
+a second run finds nothing to move, and a run that stopped partway is finished
+by the next one.
+
+\- A spec root\*(Aqs features/kind=feature/ moves to <root>/kind=feature/ (git mv in a
+  git work tree). A root at the repo\-level `specs` moves to .canon/specs, and
+  canon.yaml records `former_roots: [specs]` so reviews pinned before the move
+  still find their scenarios.
+\- Changes `canon change new` wrote under openspec/changes move to
+  .canon/changes/<slug>/ (proposal.md \-> brief.md, tasks.md alongside); every
+  other change stays and is named. A change counts as canon\*(Aqs when its files are
+  still that command\*(Aqs scaffold and its first stored version was already adopted:
+  0.16 kept no durable provenance. A false positive keeps its content and ids and
+  is one `git mv` to undo; \-\-dry\-run shows exactly which changes move.
+  canon init\*(Aqs `{ dialect: openspec, root: . }` source goes once nothing unread is
+  left under it.
+\- An external proposal.md\*(Aqs Approved: line is copied into a canon pointer
+  brief, .canon/changes/<change>/brief.md, with a Source: line.
+\- skills.providers is written from the install lock; missing canon .gitignore
+  lines are added; the scenario index is rebuilt (full sync).
+\- 0.27 hooks, scripts and skill (0.28 D9): a hook command `canon gate task` (any removed
+  command spelling) becomes `canon task done`; a canon\-owned script that calls a removed
+  spelling is regenerated; a full skill projection is replaced by the stub that points to
+  `canon skills show canon`. Every file it rewrites is first copied under
+  .canon/migrate\-backup/<timestamp>/.
+\- Superseded ledger versions move to .canon/archive (`canon ledger compact`);
+  `canon query \-\-history` still reads them.
+\- Reviews written before 0.23 are re\-pinned to what their evidence says: a
+  review current under the old rule stays current, a stale one stays stale.
+
+Refuses (exit 2, nothing written) on uncommitted changes under a path it
+moves, on a destination that already exists, on a change directory that could
+stop halfway, and on a canon.yaml edit it cannot make with every other byte
+kept. canon.yaml is written atomically.
+.SH VERSION
+v0.29.0

package/man/canon-plugin-sync.1

@@ -0,0 +1,53 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-plugin-sync 1  "sync 0.29.0" 
+.SH NAME
+canon\-plugin\-sync \- Validate and write a plugin\*(Aqs overlay records
+.SH SYNOPSIS
+\fBcanon plugin sync\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-spec\-root\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIPLUGIN_ID\fR> 
+.SH DESCRIPTION
+Validate and write a plugin\*(Aqs overlay records
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-spec\-root\fR \fI<DIR>\fR
+Sync exactly one ad hoc root, overriding canon.yaml\*(Aqs specs.roots[]
+.TP
+\fB\-\-dry\-run\fR
+Validate fully and report what would be written, without writing anything
+.TP
+\fB\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-\-input\fR \fI<JSON|FILE|\->\fR
+The arguments as JSON: an object (one run) or an array / NDJSON file or `\-` (a batch); keys are the option names in camelCase, `operands` an array
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+<\fIPLUGIN_ID\fR>
+A .canon/plugins/<id>/plugin.yaml manifest id (e.g. porting)
+.SH VERSION
+v0.29.0

package/man/canon-plugin.1

@@ -0,0 +1,39 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-plugin 1  "plugin 0.29.0" 
+.SH NAME
+canon\-plugin \- Sync plugin overlay records onto the ledger
+.SH SYNOPSIS
+\fBcanon plugin\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Sync plugin overlay records onto the ledger
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH SUBCOMMANDS
+.TP
+canon\-plugin\-sync(1)
+Validate and write a plugin\*(Aqs overlay records
+.SH VERSION
+v0.29.0

package/man/canon-policy-approve.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-policy-approve 1  "approve 0.29.0" 
+.SH NAME
+canon\-policy\-approve \- Approve the current .canon/policy.yaml (written directly; nothing to promote)
+.SH SYNOPSIS
+\fBcanon policy approve\fR <\fB\-\-approver\fR> [\fB\-\-as\fR] [\fB\-\-note\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Approve the current .canon/policy.yaml (written directly; nothing to promote)
+.SH OPTIONS
+.TP
+\fB\-\-approver\fR \fI<NAME>\fR
+Who approved it (a human\*(Aqs name or id)
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-note\fR \fI<TEXT>\fR
+Why, or what was reviewed
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-\-input\fR \fI<JSON|FILE|\->\fR
+The arguments as JSON: an object (one run) or an array / NDJSON file or `\-` (a batch); keys are the option names in camelCase, `operands` an array
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH VERSION
+v0.29.0

package/man/canon-policy-show.1

@@ -0,0 +1,41 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-policy-show 1  "show 0.29.0" 
+.SH NAME
+canon\-policy\-show \- Show the policy\*(Aqs digest and its approval (who, when, which bytes)
+.SH SYNOPSIS
+\fBcanon policy show\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Show the policy\*(Aqs digest and its approval (who, when, which bytes)
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH VERSION
+v0.29.0

package/man/canon-policy.1

@@ -0,0 +1,52 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-policy 1  "policy 0.29.0" 
+.SH NAME
+canon\-policy \- Record who approved the gate\*(Aqs policy (.canon/policy.yaml) and which bytes
+.SH SYNOPSIS
+\fBcanon policy\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Record who approved the gate\*(Aqs policy (.canon/policy.yaml) and which bytes
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH SUBCOMMANDS
+.TP
+canon\-policy\-approve(1)
+Approve the current .canon/policy.yaml (written directly; nothing to promote)
+.TP
+canon\-policy\-show(1)
+Show the policy\*(Aqs digest and its approval (who, when, which bytes)
+.SH EXTRA
+Examples:
+  canon policy approve \-\-approver alice \-\-note \*(Aqreviewed the starter policy\*(Aq
+
+Writes .canon/policy.approval.json (commit it): the policy\*(Aqs sha256, who
+approved it, when, and the note. `canon gate check` and `canon status` print an
+advisory while the policy was never approved. A policy that changed since its
+approval (or whose approval cannot be read) fails closed: `gate check` exits 1
+and `subject move` refuses to ship or reopen; `\-\-override\-reason` does not
+waive it. `canon policy show` reads the approval back.
+.SH VERSION
+v0.29.0

package/man/canon-prompt-add.1

@@ -0,0 +1,47 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-prompt-add 1  "add 0.29.0" 
+.SH NAME
+canon\-prompt\-add \- Add a prompt bundle from a repository\-local JSON manifest
+.SH SYNOPSIS
+\fBcanon prompt add\fR [\fB\-\-as\fR] <\fB\-\-manifest\fR> [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] <\fINAME@VERSION\fR> 
+.SH DESCRIPTION
+Add a prompt bundle from a repository\-local JSON manifest
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-manifest\fR \fI<FILE>\fR
+Repository\-relative input manifest
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-json\fR
+Output the complete bundle manifest as JSON
+.TP
+\fB\-\-input\fR \fI<JSON|FILE|\->\fR
+The arguments as JSON: an object (one run) or an array / NDJSON file or `\-` (a batch); keys are the option names in camelCase, `operands` an array
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+<\fINAME@VERSION\fR>
+The bundle to register, `NAME@VERSION`
+.SH VERSION
+v0.29.0

package/man/canon-prompt-show.1

@@ -0,0 +1,41 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-prompt-show 1  "show 0.29.0" 
+.SH NAME
+canon\-prompt\-show \- Select a registered prompt bundle version
+.SH SYNOPSIS
+\fBcanon prompt show\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] <\fINAME@VERSION\fR> 
+.SH DESCRIPTION
+Select a registered prompt bundle version
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-json\fR
+Output the complete bundle manifest as JSON
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+<\fINAME@VERSION\fR>
+The bundle to show, `NAME@VERSION`
+.SH VERSION
+v0.29.0

package/man/canon-prompt.1

@@ -0,0 +1,43 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-prompt 1  "prompt 0.29.0" 
+.SH NAME
+canon\-prompt \- Register and select versioned prompt bundles
+.SH SYNOPSIS
+\fBcanon prompt\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Register and select versioned prompt bundles
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.SH SUBCOMMANDS
+.TP
+canon\-prompt\-add(1)
+Add a prompt bundle from a repository\-local JSON manifest
+.TP
+canon\-prompt\-show(1)
+Select a registered prompt bundle version
+.SH EXTRA
+Examples:
+  canon prompt add reviewer@v1 \-\-manifest .canon/reviewer.json
+  canon prompt show reviewer@v1 \-\-json
+.SH VERSION
+v0.29.0

package/man/canon-purge.1

@@ -0,0 +1,70 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-purge 1  "purge 0.29.0" 
+.SH NAME
+canon\-purge \- Remove allowlisted records older than a cutoff: the bare run previews the removal set and its planDigest, `\-\-commit \-\-plan\-digest <DIGEST>` deletes it
+.SH SYNOPSIS
+\fBcanon purge\fR [\fB\-\-as\fR] <\fB\-\-kind\fR> <\fB\-\-before\fR> [\fB\-\-commit\fR] [\fB\-\-plan\-digest\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Remove allowlisted records older than a cutoff: the bare run previews the removal set and its planDigest, `\-\-commit \-\-plan\-digest <DIGEST>` deletes it
+.SH OPTIONS
+.TP
+\fB\-\-as\fR \fI<ROLE>\fR
+The role you act as: planner, implementer, reviewer or orchestrator. Overrides `CANON_ROLE`. `schema` and `context` list only the role\*(Aqs commands, `status` keeps its steps, and `\-\-role` on `evidence add` / `evidence audit` / `review scenario` / `review change` defaults to it
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+planner
+.IP \(bu 2
+implementer
+.IP \(bu 2
+reviewer
+.IP \(bu 2
+orchestrator
+.RE
+.TP
+\fB\-\-kind\fR \fI<KIND>\fR
+The record kind to purge (session, run, event or trajectory)
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+session
+.IP \(bu 2
+run
+.IP \(bu 2
+event
+.IP \(bu 2
+trajectory
+.RE
+.TP
+\fB\-\-before\fR \fI<TIMESTAMP>\fR
+Remove records strictly before this time (RFC3339 or YYYY\-MM\-DD, UTC)
+.TP
+\fB\-\-commit\fR
+Act on the previewed plan; needs \-\-plan\-digest
+.TP
+\fB\-\-plan\-digest\fR \fI<DIGEST>\fR
+The `planDigest` the preview printed; the run acts only if the plan recomputed now has this digest
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-\-input\fR \fI<JSON|FILE|\->\fR
+The arguments as JSON: an object (one run) or an array / NDJSON file or `\-` (a batch); keys are the option names in camelCase, `operands` an array
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH VERSION
+v0.29.0