@journeykit/canon 0.27.0 → 0.29.0

package/man/canon-scenario-new.1

@@ -0,0 +1,80 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-scenario-new 1  "new 0.29.0" 
+.SH NAME
+canon\-scenario\-new \- Append a tagged scenario stub to its .feature file (created if missing); many at once with `\-\-input`
+.SH SYNOPSIS
+\fBcanon scenario new\fR [\fB\-\-as\fR] <\fB\-\-title\fR> [\fB\-\-subject\-id\fR] [\fB\-\-lane\fR] [\fB\-\-case\fR] [\fB\-\-flow\fR] [\fB\-\-change\-id\fR] [\fB\-\-actor\-id\fR] [\fB\-\-session\-id\fR] [\fB\-\-feature\fR] [\fB\-\-project\-id\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISCENARIO_ID\fR> 
+.SH DESCRIPTION
+Append a tagged scenario stub to its .feature file (created if missing); many at once with `\-\-input`
+.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\-\-title\fR \fI<TEXT>\fR
+The Scenario: header label
+.TP
+\fB\-\-subject\-id\fR \fI<SUBJECT_ID>\fR
+Optional subject id tag to pin above the scenario
+.TP
+\fB\-\-lane\fR \fI<NAME>\fR
+Optional lane tag to classify the scenario
+.TP
+\fB\-\-case\fR \fI<NAME>\fR
+Optional case tag: which path of the behavior this scenario specifies (`happy`, `failure`, `edge` in the base vocabulary)
+.TP
+\fB\-\-flow\fR \fI<FLOW_ID>\fR
+The brief flow step this scenario covers (`F1`): writes `@flow:<change>.<F\-id>`. The change is \-\-change\-id, else the newest change of \-\-subject\-id, else the only live change
+.TP
+\fB\-\-change\-id\fR \fI<CHANGE_ID>\fR
+The change whose brief defines \-\-flow (default: \-\-subject\-id\*(Aqs newest adopted change)
+.TP
+\fB\-\-actor\-id\fR \fI<ACTOR_ID>\fR [default: canon\-scaffold]
+Agent id written into provenance (env: CANON_ACTOR)
+.RS
+May also be specified with the \fBCANON_ACTOR\fR environment variable. 
+.RE
+.TP
+\fB\-\-session\-id\fR \fI<SESSION_ID>\fR
+The acting session (recorded as actor.session_id); optional
+.TP
+\fB\-\-feature\fR \fI<FILE>\fR
+Target .feature file (default: derived from <tag>; must live under a specs.roots[] entry)
+.TP
+\fB\-\-project\-id\fR \fI<PROJECT_ID>\fR
+Which configured `specs.roots[]` entry to write under, by its id. Required only when the repo configures more than one
+.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
+.TP
+<\fISCENARIO_ID\fR>
+<area>.<surface>.<nn> scenario tag
+.SH VERSION
+v0.29.0

package/man/canon-scenario.1

@@ -0,0 +1,39 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-scenario 1  "scenario 0.29.0" 
+.SH NAME
+canon\-scenario \- Add a tagged scenario to a .feature spec file
+.SH SYNOPSIS
+\fBcanon scenario\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Add a tagged scenario to a .feature spec file
+.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\-scenario\-new(1)
+Append a tagged scenario stub to its .feature file (created if missing); many at once with `\-\-input`
+.SH VERSION
+v0.29.0

package/man/canon-schema.1

@@ -0,0 +1,63 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-schema 1  "schema 0.29.0" 
+.SH NAME
+canon\-schema \- Describe canon\*(Aqs own commands: list them, or show one command\*(Aqs arguments, options, effect and exit codes
+.SH SYNOPSIS
+\fBcanon schema\fR [\fB\-\-as\fR] [\fB\-\-json\fR] [\fB\-\-errors\fR] [\fB\-\-error\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] [\fIPATH\fR] 
+.SH DESCRIPTION
+Describe canon\*(Aqs own commands: list them, or show one command\*(Aqs arguments, options, effect and exit codes
+.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\-\-json\fR
+Output JSON instead of the human\-readable form
+.TP
+\fB\-\-errors\fR
+Print every error code any command can emit, with its meaning, instead of a command
+.TP
+\fB\-\-error\fR \fI<CODE>\fR
+Show one error code: its meaning, exit, retryable and fix (an unknown code exits 2)
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+[\fIPATH\fR]
+Command path, e.g. `evidence add` (omit to list every command)
+.SH EXTRA
+Examples:
+  canon schema
+  canon schema \-\-json
+  canon schema evidence add \-\-json
+  canon schema \-\-as reviewer \-\-json
+  canon schema \-\-errors \-\-json
+  canon schema \-\-error CONFIG_MISSING
+
+Generated from the command tree itself, so it never drifts from what the parser accepts.
+Touches no repo and no network: it works from any directory. An unknown path exits 2 and names the
+nearest matches.
+
+The bare listing is unfiltered: every command. `\-\-as <ROLE>` lists only that role\*(Aqs commands; the
+CANON_ROLE variable never filters or fails `schema` (an invalid value is a warning in meta.warnings).
+A command whose effect depends on its arguments carries `effectNote`.
+.SH VERSION
+v0.29.0

package/man/canon-selftest.1

@@ -0,0 +1,69 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-selftest 1  "selftest 0.29.0" 
+.SH NAME
+canon\-selftest \- Run canon\*(Aqs built\-in fixture self\-tests
+.SH SYNOPSIS
+\fBcanon selftest\fR [\fB\-\-as\fR] [\fB\-\-suite\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Run canon\*(Aqs built\-in fixture self\-tests
+.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\-\-suite\fR \fI<NAME>\fR
+Run only this suite (default: every suite)
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+trust\-spine\-gate
+.IP \(bu 2
+tiered\-storage
+.IP \(bu 2
+typed\-authoring\-vocabulary
+.IP \(bu 2
+policy\-expressions
+.IP \(bu 2
+format\-authority
+.IP \(bu 2
+session\-ingest
+.IP \(bu 2
+canon\-context
+.IP \(bu 2
+artifact\-ingest
+.IP \(bu 2
+spec\-ledger\-selftest
+.IP \(bu 2
+plugin\-overlays
+.IP \(bu 2
+plan\-import
+.RE
+.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-skills-check.1

@@ -0,0 +1,47 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-skills-check 1  "check 0.29.0" 
+.SH NAME
+canon\-skills\-check \- Check canonical projections without writing; exit 1 on drift, a legacy remnant, or a lock another canon version wrote
+.SH SYNOPSIS
+\fBcanon skills check\fR [\fB\-\-as\fR] [\fB\-\-skills\-source\fR] [\fB\-\-repo\fR] [\fB\-\-providers\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Check canonical projections without writing; exit 1 on drift, a legacy remnant, or a lock another canon version wrote
+.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\-\-skills\-source\fR \fI<DIR>\fR
+Source directory; defaults to CANON_SKILLS_SOURCE or canon/skills
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-providers\fR \fI<LIST>\fR
+Providers to inspect (`claude`, `codex`, `omp`, `pi`, or a comma\-separated list). Omitted: as for install
+.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-skills-doctor.1

@@ -0,0 +1,47 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-skills-doctor 1  "doctor 0.29.0" 
+.SH NAME
+canon\-skills\-doctor \- Print diagnostics for canonical projections, the install lock\*(Aqs canon version, legacy remnants, canon projections for a provider that is not selected, and other skills whose description claims build work; reports only, never edits
+.SH SYNOPSIS
+\fBcanon skills doctor\fR [\fB\-\-as\fR] [\fB\-\-skills\-source\fR] [\fB\-\-repo\fR] [\fB\-\-providers\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Print diagnostics for canonical projections, the install lock\*(Aqs canon version, legacy remnants, canon projections for a provider that is not selected, and other skills whose description claims build work; reports only, never edits
+.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\-\-skills\-source\fR \fI<DIR>\fR
+Source directory; defaults to CANON_SKILLS_SOURCE or canon/skills
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-providers\fR \fI<LIST>\fR
+Providers to inspect (`claude`, `codex`, `omp`, `pi`, or a comma\-separated list). Omitted: as for install
+.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-skills-install.1

@@ -0,0 +1,53 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-skills-install 1  "install 0.29.0" 
+.SH NAME
+canon\-skills\-install \- Install the canonical `canon` bundle or legacy developer skills
+.SH SYNOPSIS
+\fBcanon skills install\fR [\fB\-\-as\fR] [\fB\-\-skills\-source\fR] [\fB\-\-repo\fR] [\fB\-\-providers\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 canonical `canon` bundle or legacy developer skills
+.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\-\-skills\-source\fR \fI<DIR>\fR
+Developer override: read SKILL.src.md\*(Aqs frontmatter and scripts/ from this directory instead of the text built into the binary; defaults to CANON_SKILLS_SOURCE, else the built\-in text
+.TP
+\fB\-\-repo\fR \fI<DIR>\fR
+The repo to act on (default: the nearest ancestor directory holding a canon.yaml)
+.TP
+\fB\-\-providers\fR \fI<LIST>\fR
+Providers to project (`claude`, `codex`, `omp`, `pi`, a comma\-separated list, or `none`); also rewrites `skills.providers` in the target\*(Aqs canon.yaml. Omitted: canon.yaml `skills.providers`, else the install lock\*(Aqs providers, else the detected `.claude`, `.codex`, `.omp`, `.pi` directories; none detected installs nothing. Codex is projected to `.agents/skills/canon/`
+.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.29.0

package/man/canon-skills-show.1

@@ -0,0 +1,104 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-skills-show 1  "show 0.29.0" 
+.SH NAME
+canon\-skills\-show \- Print a guide built into this binary (markdown on stdout); the installed SKILL.md is a stub that points here
+.SH SYNOPSIS
+\fBcanon skills show\fR [\fB\-\-as\fR] [\fB\-\-full\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fINAME\fR> 
+.SH DESCRIPTION
+Print a guide built into this binary (markdown on stdout); the installed SKILL.md is a stub that points here
+.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\-\-full\fR
+With `canon`: append every reference after the core guide. Any other name is a complete guide already, so the flag changes nothing there
+.TP
+\fB\-\-json\fR
+Output JSON instead of the markdown
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+<\fINAME\fR>
+The guide to print: `canon` (the core guide) or a reference such as `role\-implementer`
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+canon
+.IP \(bu 2
+brief\-align
+.IP \(bu 2
+brief\-clarify
+.IP \(bu 2
+brief\-harden
+.IP \(bu 2
+brief\-polish
+.IP \(bu 2
+brief\-shape
+.IP \(bu 2
+canon\-artifact\-ingest
+.IP \(bu 2
+canon\-authoring
+.IP \(bu 2
+canon\-context
+.IP \(bu 2
+canon\-fmt
+.IP \(bu 2
+canon\-gate
+.IP \(bu 2
+canon\-inventory
+.IP \(bu 2
+canon\-learn
+.IP \(bu 2
+canon\-plan\-import
+.IP \(bu 2
+canon\-plugins
+.IP \(bu 2
+canon\-policy
+.IP \(bu 2
+canon\-report\-dashboard
+.IP \(bu 2
+canon\-retrieve
+.IP \(bu 2
+canon\-review
+.IP \(bu 2
+canon\-session\-ingest
+.IP \(bu 2
+canon\-storage
+.IP \(bu 2
+canon\-subject
+.IP \(bu 2
+canon\-vocab
+.IP \(bu 2
+role\-implementer
+.IP \(bu 2
+role\-orchestrator
+.IP \(bu 2
+role\-planner
+.IP \(bu 2
+role\-reviewer
+.RE
+.SH VERSION
+v0.29.0

package/man/canon-skills.1

@@ -0,0 +1,48 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-skills 1  "skills 0.29.0" 
+.SH NAME
+canon\-skills \- Install canon\*(Aqs agent guides into a repo
+.SH SYNOPSIS
+\fBcanon skills\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Install canon\*(Aqs agent guides into a repo
+.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\-skills\-install(1)
+Install the canonical `canon` bundle or legacy developer skills
+.TP
+canon\-skills\-check(1)
+Check canonical projections without writing; exit 1 on drift, a legacy remnant, or a lock another canon version wrote
+.TP
+canon\-skills\-doctor(1)
+Print diagnostics for canonical projections, the install lock\*(Aqs canon version, legacy remnants, canon projections for a provider that is not selected, and other skills whose description claims build work; reports only, never edits
+.TP
+canon\-skills\-show(1)
+Print a guide built into this binary (markdown on stdout); the installed SKILL.md is a stub that points here
+.SH VERSION
+v0.29.0

package/man/canon-status.1

@@ -0,0 +1,51 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-status 1  "status 0.29.0" 
+.SH NAME
+canon\-status \- Show where this repo stands: subjects by status, their gaps, and the next commands
+.SH SYNOPSIS
+\fBcanon status\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-fields\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Show where this repo stands: subjects by status, their gaps, and the next commands
+.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\-\-fields\fR \fI<FIELDS>\fR
+With \-\-json, keep only these top\-level report fields (comma\-separated); an unknown field is refused (camelCase and snake_case both match)
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH EXTRA
+Examples:
+  canon status
+  canon status \-\-json
+
+A read: exits 0 whatever it finds, and writes nothing. The counts come from the
+same joins `canon gate check` and `canon subject move` use.
+.SH VERSION
+v0.29.0

package/man/canon-strategy-approval-payload.1

@@ -0,0 +1,53 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-strategy-approval-payload 1  "approval-payload 0.29.0" 
+.SH NAME
+canon\-strategy\-approval\-payload \- The unsigned approval payload bytes an external signer signs (a read: identical arguments give identical bytes)
+.SH SYNOPSIS
+\fBcanon strategy approval\-payload\fR [\fB\-\-as\fR] <\fB\-\-evaluation\fR> <\fB\-\-approver\fR> <\fB\-\-approval\-at\fR> [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISTRATEGY_ID\fR> 
+.SH DESCRIPTION
+The unsigned approval payload bytes an external signer signs (a read: identical arguments give identical 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\-\-evaluation\fR \fI<FILE>\fR
+The paired evaluation bundle the approval is for
+.TP
+\fB\-\-approver\fR \fI<NAME>\fR
+Who approves (the human whose detached signature the payload is for)
+.TP
+\fB\-\-approval\-at\fR \fI<TIMESTAMP>\fR
+The approval time that is signed into the payload: RFC3339, or YYYY\-MM\-DD (UTC midnight)
+.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
+Envelope the payload as JSON instead of printing its bytes
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+<\fISTRATEGY_ID\fR>
+The StrategyId (ULID) whose approval payload to print
+.SH VERSION
+v0.29.0