@journeykit/canon 0.26.0 → 0.28.0

package/man/canon-format.1

@@ -0,0 +1,49 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-format 1  "format 0.28.0" 
+.SH NAME
+canon\-format \- Validate a spec/artifact corpus against canon\*(Aqs format
+.SH SYNOPSIS
+\fBcanon format\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] [\fIDIR\fR] 
+.SH DESCRIPTION
+Validate a spec/artifact corpus against canon\*(Aqs format
+.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
+.TP
+[\fIDIR\fR]
+Corpus directory, e.g. a consumer repo\*(Aqs spec/ directory (default: every configured specs.roots[] entry). A relative path resolves under \-\-repo when given, else the current directory
+.SH EXTRA
+Examples:
+  canon format                  Every configured spec root
+  canon format spec
+  canon format spec \-\-repo ~/work/myrepo
+.SH VERSION
+v0.28.0

package/man/canon-gate-check.1

@@ -0,0 +1,44 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-gate-check 1  "check 0.28.0" 
+.SH NAME
+canon\-gate\-check \- Run the coverage/ledger/staleness/trust checks (0 clean, 1 red, 2 usage)
+.SH SYNOPSIS
+\fBcanon gate check\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-release\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Run the coverage/ledger/staleness/trust checks (0 clean, 1 red, 2 usage)
+.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\-\-release\fR
+Additionally engage the release\-scoped trust check
+.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.28.0

package/man/canon-gate-install-hooks.1

@@ -0,0 +1,59 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-gate-install-hooks 1  "install-hooks 0.28.0" 
+.SH NAME
+canon\-gate\-install\-hooks \- Install the gate hook into .claude/settings.json / .codex/hooks.json
+.SH SYNOPSIS
+\fBcanon gate install\-hooks\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-event\fR] [\fB\-\-matcher\fR] [\fB\-\-command\fR] [\fB\-\-timeout\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Install the gate hook into .claude/settings.json / .codex/hooks.json
+.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\-\-event\fR \fI<NAME>\fR [default: PreToolUse]
+The hook event name (e.g. PreToolUse, Stop)
+.TP
+\fB\-\-matcher\fR \fI<TEXT>\fR
+Omitted for a matcher\-less event
+.TP
+\fB\-\-command\fR \fI<TEXT>\fR [default: canon task done]
+The command the hook runs
+.TP
+\fB\-\-timeout\fR \fI<N>\fR [default: 30]
+Hook timeout in seconds
+.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
+.SH VERSION
+v0.28.0

package/man/canon-gate-promote.1

@@ -0,0 +1,62 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-gate-promote 1  "promote 0.28.0" 
+.SH NAME
+canon\-gate\-promote \- Promote staged records (evidence, findings, divergences) to the committed ledger
+.SH SYNOPSIS
+\fBcanon gate promote\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-kind\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Promote staged records (evidence, findings, divergences) to the committed 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\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-kind\fR \fI<KIND>\fR
+Promote only this kind of staged record (default: every kind)
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+evidence
+.IP \(bu 2
+finding
+.IP \(bu 2
+divergence
+.RE
+.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
+.SH VERSION
+v0.28.0

package/man/canon-gate.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-gate 1  "gate 0.28.0" 
+.SH NAME
+canon\-gate \- Run evidence gates, promote staged records, install hooks
+.SH SYNOPSIS
+\fBcanon gate\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Run evidence gates, promote staged records, install hooks
+.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\-gate\-check(1)
+Run the coverage/ledger/staleness/trust checks (0 clean, 1 red, 2 usage)
+.TP
+canon\-gate\-promote(1)
+Promote staged records (evidence, findings, divergences) to the committed ledger
+.TP
+canon\-gate\-install\-hooks(1)
+Install the gate hook into .claude/settings.json / .codex/hooks.json
+.SH EXTRA
+Examples:
+  canon gate check
+  canon task done my\-change#3
+  canon gate install\-hooks
+.SH VERSION
+v0.28.0

package/man/canon-ingest-plans.1

@@ -0,0 +1,53 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-ingest-plans 1  "plans 0.28.0" 
+.SH NAME
+canon\-ingest\-plans \- Import plans as Change/Task records: canon\*(Aqs own .canon/changes, then the configured external sources (openspec, superpowers)
+.SH SYNOPSIS
+\fBcanon ingest plans\fR [\fB\-\-as\fR] [\fB\-\-dialect\fR] [\fB\-\-plan\-source\fR] [\fB\-\-repo\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Import plans as Change/Task records: canon\*(Aqs own .canon/changes, then the configured external sources (openspec, superpowers)
+.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\-\-dialect\fR \fI<NAME>\fR
+One\-shot override: import this dialect\*(Aqs \-\-plan\-source root (requires \-\-plan\-source)
+.TP
+\fB\-\-plan\-source\fR \fI<DIR>\fR
+One\-shot override\*(Aqs source root (paired with \-\-dialect)
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.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
+.SH VERSION
+v0.28.0

package/man/canon-ingest-records.1

@@ -0,0 +1,56 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-ingest-records 1  "records 0.28.0" 
+.SH NAME
+canon\-ingest\-records \- Import review/divergence/task/handoff records and derive verdicts
+.SH SYNOPSIS
+\fBcanon ingest records\fR [\fB\-\-as\fR] [\fB\-\-watch\fR] [\fB\-\-interval\-secs\fR] [\fB\-\-repo\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-run\-id\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Import review/divergence/task/handoff records and derive verdicts
+.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\-\-watch\fR
+Keep polling instead of exiting after one pass
+.TP
+\fB\-\-interval\-secs\fR \fI<N>\fR [default: 30]
+Seconds between polls
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.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\-\-run\-id\fR \fI<RUN_ID>\fR
+Attribute this pass\*(Aqs trajectories to a dispatched run (a RunId minted by `canon dispatch begin`)
+.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.28.0

package/man/canon-ingest-sessions.1

@@ -0,0 +1,62 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-ingest-sessions 1  "sessions 0.28.0" 
+.SH NAME
+canon\-ingest\-sessions \- Import agent CLI session transcripts (omp/pi, Claude Code, Codex, Hermes)
+.SH SYNOPSIS
+\fBcanon ingest sessions\fR [\fB\-\-as\fR] [\fB\-\-watch\fR] [\fB\-\-interval\-secs\fR] [\fB\-\-home\fR] [\fB\-\-repo\fR] [\fB\-\-full\fR] [\fB\-\-all\-workspaces\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Import agent CLI session transcripts (omp/pi, Claude Code, Codex, Hermes)
+.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\-\-watch\fR
+Keep polling instead of exiting after one pass
+.TP
+\fB\-\-interval\-secs\fR \fI<N>\fR [default: 30]
+Seconds between polls
+.TP
+\fB\-\-home\fR \fI<DIR>\fR
+The scan root\*(Aqs home directory (defaults to $HOME)
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-full\fR
+Ignore watermark cursors and re\-parse every in\-scope file
+.TP
+\fB\-\-all\-workspaces\fR
+Scan every workspace on this machine, not just this project
+.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
+.SH VERSION
+v0.28.0

package/man/canon-ingest.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-ingest 1  "ingest 0.28.0" 
+.SH NAME
+canon\-ingest \- Import agent sessions, records, and plans into canon\*(Aqs store
+.SH SYNOPSIS
+\fBcanon ingest\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Import agent sessions, records, and plans into canon\*(Aqs store
+.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\-ingest\-sessions(1)
+Import agent CLI session transcripts (omp/pi, Claude Code, Codex, Hermes)
+.TP
+canon\-ingest\-records(1)
+Import review/divergence/task/handoff records and derive verdicts
+.TP
+canon\-ingest\-plans(1)
+Import plans as Change/Task records: canon\*(Aqs own .canon/changes, then the configured external sources (openspec, superpowers)
+.SH EXTRA
+Examples:
+  canon ingest sessions \-\-watch
+  canon ingest records
+  canon ingest plans
+.SH VERSION
+v0.28.0

package/man/canon-init.1

@@ -0,0 +1,98 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-init 1  "init 0.28.0" 
+.SH NAME
+canon\-init \- Set up canon in a repo (canon.yaml, a starter policy, the AGENTS.md block, a plans home)
+.SH SYNOPSIS
+\fBcanon init\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-check\fR] [\fB\-\-no\-agents\-md\fR] [\fB\-\-policy\fR] [\fB\-\-no\-policy\fR] [\fB\-\-providers\fR] [\fB\-\-language\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Set up canon in a repo (canon.yaml, a starter policy, the AGENTS.md block, a plans home)
+.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 [default: .]
+Directory to set up (used as\-is)
+.TP
+\fB\-\-check\fR
+Validate an existing canon.yaml instead of writing one
+.TP
+\fB\-\-no\-agents\-md\fR
+Do not write or refresh the canon block in AGENTS.md
+.TP
+\fB\-\-policy\fR \fI<LEVEL>\fR [default: strict]
+Level of the starter .canon/policy.yaml [default: strict]
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+light: Evidence on every scenario
+.IP \(bu 2
+standard: Light, plus a `@case:failure` scenario per feature surface
+.IP \(bu 2
+strict: Standard, plus independent review
+.RE
+.TP
+\fB\-\-no\-policy\fR
+Do not write the starter .canon/policy.yaml
+.TP
+\fB\-\-providers\fR \fI<LIST>\fR
+Harnesses to install the canon skill for, without asking (`claude`, `codex`, `omp`, `pi`, comma\-separated; `none` for none)
+.TP
+\fB\-\-language\fR \fI<TAG>\fR
+Language the briefs are written in (`en`, `ko`, or any tag: `en` headings, structure rules only); recorded as `language:` in canon.yaml
+.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 (see a summary with \*(Aq\-h\*(Aq)
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH EXTRA
+Examples:
+  canon init
+  canon init \-\-policy light
+  canon init \-\-providers claude,codex
+  canon init \-\-no\-agents\-md \-\-no\-policy
+  canon init \-\-check
+
+Policy levels (\-\-policy, default strict): light requires evidence on every
+scenario; standard adds a `@case:failure` scenario per feature surface; strict
+adds independent review. The level is the first line of .canon/policy.yaml and
+`canon status` shows it.
+
+Harnesses (\-\-providers): on a terminal, init asks which harnesses get the canon
+skill, with the detected ones (.claude, .codex, .omp, .pi directories) checked.
+Without a terminal or \-\-providers it takes the detected ones; with none detected
+it installs nothing and says how to choose. The answer is recorded as
+`skills: { providers: [...] }` in canon.yaml (`\-\-providers none` records `[]`).
+
+Rerunning in a repo that has canon.yaml leaves canon.yaml and .canon/policy.yaml
+alone and only refreshes the canon block in AGENTS.md.
+.SH VERSION
+v0.28.0

package/man/canon-inventory-sync.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-inventory-sync 1  "sync 0.28.0" 
+.SH NAME
+canon\-inventory\-sync \- Validate each spec root, then materialize scenario index records
+.SH SYNOPSIS
+\fBcanon inventory 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] 
+.SH DESCRIPTION
+Validate each spec root, then materialize scenario index 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
+.SH VERSION
+v0.28.0

package/man/canon-inventory.1

@@ -0,0 +1,39 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-inventory 1  "inventory 0.28.0" 
+.SH NAME
+canon\-inventory \- Index a validated .feature corpus into the scenario ledger
+.SH SYNOPSIS
+\fBcanon inventory\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Index a validated .feature corpus into the scenario 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\-inventory\-sync(1)
+Validate each spec root, then materialize scenario index records
+.SH VERSION
+v0.28.0