@journeykit/canon 0.26.0 → 0.28.0

package/man/canon-strategy-promote.1

@@ -0,0 +1,59 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-strategy-promote 1  "promote 0.28.0" 
+.SH NAME
+canon\-strategy\-promote \- Promote a strategy after paired evaluation and signed approval
+.SH SYNOPSIS
+\fBcanon strategy promote\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-evaluation\fR] [\fB\-\-approval\fR] [\fB\-\-signature\-file\fR] [\fB\-\-dry\-run\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISTRATEGY_ID\fR> 
+.SH DESCRIPTION
+Promote a strategy after paired evaluation and signed approval
+.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\-\-evaluation\fR \fI<FILE>\fR
+Evaluation bundle produced by the honest promotion adapter
+.TP
+\fB\-\-approval\fR \fI<FILE>\fR
+Approval JSON containing the detached SSH signature
+.TP
+\fB\-\-signature\-file\fR \fI<FILE>\fR
+Detached signature file to attach to the approval JSON
+.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
+<\fISTRATEGY_ID\fR>
+The StrategyId (ULID) to promote
+.SH VERSION
+v0.28.0

package/man/canon-strategy-rollback.1

@@ -0,0 +1,62 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-strategy-rollback 1  "rollback 0.28.0" 
+.SH NAME
+canon\-strategy\-rollback \- Disable an active strategy with durable rollback provenance
+.SH SYNOPSIS
+\fBcanon strategy rollback\fR [\fB\-\-as\fR] <\fB\-\-reason\fR> <\fB\-\-actor\-id\fR> <\fB\-\-signature\-file\fR> <\fB\-\-approval\-at\fR> [\fB\-\-contradicting\-trajectory\-id\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISTRATEGY_ID\fR> 
+.SH DESCRIPTION
+Disable an active strategy with durable rollback provenance
+.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\-\-reason\fR \fI<TEXT>\fR
+Why the strategy is rolled back (signed: `strategy:<id>:rollback:<sha256(reason)>`)
+.TP
+\fB\-\-actor\-id\fR \fI<ACTOR_ID>\fR
+The approver; must be a policy\-pinned approver
+.TP
+\fB\-\-signature\-file\fR \fI<FILE>\fR
+Detached signature file over the rollback payload
+.TP
+\fB\-\-approval\-at\fR \fI<TIMESTAMP>\fR
+When the approver signed: RFC3339, or YYYY\-MM\-DD (UTC midnight)
+.TP
+\fB\-\-contradicting\-trajectory\-id\fR \fI<ID>\fR
+A trajectory that contradicts the strategy (must exist in the trajectory store)
+.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
+<\fISTRATEGY_ID\fR>
+The StrategyId (ULID) to roll back
+.SH VERSION
+v0.28.0

package/man/canon-strategy.1

@@ -0,0 +1,45 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-strategy 1  "strategy 0.28.0" 
+.SH NAME
+canon\-strategy \- Promote a proven strategy into the git\-tracked tier
+.SH SYNOPSIS
+\fBcanon strategy\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Promote a proven strategy into the git\-tracked tier
+.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\-strategy\-promote(1)
+Promote a strategy after paired evaluation and signed approval
+.TP
+canon\-strategy\-approval\-payload(1)
+The unsigned approval payload bytes an external signer signs (a read: identical arguments give identical bytes)
+.TP
+canon\-strategy\-rollback(1)
+Disable an active strategy with durable rollback provenance
+.SH VERSION
+v0.28.0

package/man/canon-subject-adopt.1

@@ -0,0 +1,53 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-subject-adopt 1  "adopt 0.28.0" 
+.SH NAME
+canon\-subject\-adopt \- Link an imported plan change to a subject (adopting it under another subject adds that subject; a change may belong to several)
+.SH SYNOPSIS
+\fBcanon subject adopt\fR [\fB\-\-as\fR] <\fB\-\-change\-id\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] <\fISUBJECT_ID\fR> 
+.SH DESCRIPTION
+Link an imported plan change to a subject (adopting it under another subject adds that subject; a change may belong to several)
+.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\-\-change\-id\fR \fI<CHANGE_ID>\fR
+The imported Change\*(Aqs id
+.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
+.TP
+<\fISUBJECT_ID\fR>
+The subject to adopt the change under
+.SH VERSION
+v0.28.0

package/man/canon-subject-move.1

@@ -0,0 +1,80 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-subject-move 1  "move 0.28.0" 
+.SH NAME
+canon\-subject\-move \- Move a subject to another lifecycle state (shipping is evidence\-gated; with spec_coverage.require_review, entering its scope is review\-gated; shipped → verifying reopens with \-\-reason)
+.SH SYNOPSIS
+\fBcanon subject move\fR [\fB\-\-as\fR] <\fB\-\-to\fR> [\fB\-\-override\-reason\fR] [\fB\-\-reason\fR] [\fB\-\-actor\-id\fR] [\fB\-\-session\-id\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISUBJECT_ID\fR> 
+.SH DESCRIPTION
+Move a subject to another lifecycle state (shipping is evidence\-gated; with spec_coverage.require_review, entering its scope is review\-gated; shipped → verifying reopens with \-\-reason)
+.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\-\-to\fR \fI<STATE>\fR
+The state to move the subject to (proposed/specced/building/verifying/shipped/retired)
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+proposed
+.IP \(bu 2
+specced
+.IP \(bu 2
+building
+.IP \(bu 2
+verifying
+.IP \(bu 2
+shipped
+.IP \(bu 2
+retired
+.RE
+.TP
+\fB\-\-override\-reason\fR \fI<TEXT>\fR
+Move anyway when only the require_review checks (unreviewed\-promotion, open\-blocker) refuse; the reason is recorded on the subject and `canon gate check` lists the gaps as advisories
+.TP
+\fB\-\-reason\fR \fI<TEXT>\fR
+Why the subject moves (required for shipped → verifying, optional on every other transition); recorded on the subject with the actor
+.TP
+\fB\-\-actor\-id\fR \fI<ACTOR_ID>\fR [default: canon]
+The invoking actor\*(Aqs id, recorded with an \-\-override\-reason waiver or a \-\-reason
+.TP
+\fB\-\-session\-id\fR \fI<SESSION_ID>\fR
+The acting session (recorded as actor.session_id); optional
+.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
+<\fISUBJECT_ID\fR>
+The subject to move
+.SH VERSION
+v0.28.0

package/man/canon-subject-new.1

@@ -0,0 +1,65 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-subject-new 1  "new 0.28.0" 
+.SH NAME
+canon\-subject\-new \- Author a new subject at status `proposed`
+.SH SYNOPSIS
+\fBcanon subject new\fR [\fB\-\-as\fR] <\fB\-\-domain\fR> <\fB\-\-title\fR> [\fB\-\-summary\fR] [\fB\-\-owner\-role\fR] [\fB\-\-actor\-id\fR] [\fB\-\-session\-id\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISUBJECT_ID\fR> 
+.SH DESCRIPTION
+Author a new subject at status `proposed`
+.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\-\-domain\fR \fI<NAME>\fR
+The subject\*(Aqs domain (kebab slug)
+.TP
+\fB\-\-title\fR \fI<TEXT>\fR
+The subject\*(Aqs title
+.TP
+\fB\-\-summary\fR \fI<TEXT>\fR
+The subject\*(Aqs summary (optional)
+.TP
+\fB\-\-owner\-role\fR \fI<ROLE>\fR [default: implementer]
+The accountable owning role (default: implementer)
+.TP
+\fB\-\-actor\-id\fR \fI<ACTOR_ID>\fR [default: canon]
+The invoking actor\*(Aqs id
+.TP
+\fB\-\-session\-id\fR \fI<SESSION_ID>\fR
+The acting session (recorded as actor.session_id); optional
+.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
+<\fISUBJECT_ID\fR>
+The subject\*(Aqs kebab\-slug id
+.SH VERSION
+v0.28.0

package/man/canon-subject-show.1

@@ -0,0 +1,44 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-subject-show 1  "show 0.28.0" 
+.SH NAME
+canon\-subject\-show \- Show a subject (read\-only)
+.SH SYNOPSIS
+\fBcanon subject show\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISUBJECT_ID\fR> 
+.SH DESCRIPTION
+Show a subject (read\-only)
+.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
+<\fISUBJECT_ID\fR>
+The subject to show
+.SH VERSION
+v0.28.0

package/man/canon-subject-unadopt.1

@@ -0,0 +1,63 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-subject-unadopt 1  "unadopt 0.28.0" 
+.SH NAME
+canon\-subject\-unadopt \- Take a change back out of a subject (the mirror of adopt; refused for a change whose brief is approved)
+.SH SYNOPSIS
+\fBcanon subject unadopt\fR [\fB\-\-as\fR] <\fB\-\-change\-id\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] <\fISUBJECT_ID\fR> 
+.SH DESCRIPTION
+Take a change back out of a subject (the mirror of adopt; refused for a change whose brief is approved)
+.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\-\-change\-id\fR \fI<CHANGE_ID>\fR
+The change to take out of the subject
+.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
+.TP
+<\fISUBJECT_ID\fR>
+The subject to take the change out of
+.SH EXTRA
+Examples:
+  canon subject unadopt demo \-\-change\-id add\-login
+
+Removes the link on both sides (the subject\*(Aqs change list and the change\*(Aqs
+subject list). The change and its brief stay and can be adopted elsewhere, for
+example by a proposed holding subject. Refused (SUBJECT_UNADOPT_REFUSED) for a
+change whose brief carries an `Approved:` line: it is the subject\*(Aqs approved
+scope, and for a change a scenario the subject owns is tagged
+`@flow:<change>.*` for (remove or retag it first). A pair that is not linked writes nothing and exits 0.
+.SH VERSION
+v0.28.0

package/man/canon-subject.1

@@ -0,0 +1,51 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-subject 1  "subject 0.28.0" 
+.SH NAME
+canon\-subject \- Create and manage subjects (durable product units)
+.SH SYNOPSIS
+\fBcanon subject\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Create and manage subjects (durable product units)
+.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\-subject\-new(1)
+Author a new subject at status `proposed`
+.TP
+canon\-subject\-adopt(1)
+Link an imported plan change to a subject (adopting it under another subject adds that subject; a change may belong to several)
+.TP
+canon\-subject\-unadopt(1)
+Take a change back out of a subject (the mirror of adopt; refused for a change whose brief is approved)
+.TP
+canon\-subject\-show(1)
+Show a subject (read\-only)
+.TP
+canon\-subject\-move(1)
+Move a subject to another lifecycle state (shipping is evidence\-gated; with spec_coverage.require_review, entering its scope is review\-gated; shipped → verifying reopens with \-\-reason)
+.SH VERSION
+v0.28.0

package/man/canon-task-done.1

@@ -0,0 +1,47 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-task-done 1  "done 0.28.0" 
+.SH NAME
+canon\-task\-done \- Flip one task checkbox, gated on real evidence (fails closed)
+.SH SYNOPSIS
+\fBcanon task done\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fITASK_ID\fR> 
+.SH DESCRIPTION
+Flip one task checkbox, gated on real evidence (fails closed)
+.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\-\-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
+<\fITASK_ID\fR>
+The task id (<change_id>#<n>)
+.SH VERSION
+v0.28.0

package/man/canon-task.1

@@ -0,0 +1,42 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-task 1  "task 0.28.0" 
+.SH NAME
+canon\-task \- Flip a plan task\*(Aqs checkbox once committed evidence supports it
+.SH SYNOPSIS
+\fBcanon task\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Flip a plan task\*(Aqs checkbox once committed evidence supports 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\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH SUBCOMMANDS
+.TP
+canon\-task\-done(1)
+Flip one task checkbox, gated on real evidence (fails closed)
+.SH EXTRA
+Examples:
+  canon task done my\-change#3
+.SH VERSION
+v0.28.0

package/man/canon-tier-age.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-tier-age 1  "age 0.28.0" 
+.SH NAME
+canon\-tier\-age \- Apply canon.yaml aging rules, moving old records to their destination tier
+.SH SYNOPSIS
+\fBcanon tier age\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
+Apply canon.yaml aging rules, moving old records to their destination tier
+.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.28.0