@journeykit/canon 0.27.0 → 0.28.0

package/man/canon-artifacts-store.1

@@ -0,0 +1,54 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-artifacts-store 1  "store 0.28.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
+\fBcanon artifacts store\fR [\fB\-\-as\fR] [\fB\-\-max\-artifact\-mib\fR] [\fB\-\-dry\-run\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Store the bound files of existing evidence records and current reviews in the artifact store (.canon/artifacts/sha256/)
+.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\-\-max\-artifact\-mib\fR \fI<N>\fR [default: 25]
+Per\-file size limit for the artifact store, in MiB
+.TP
+\fB\-\-dry\-run\fR
+Validate fully and report what would be written, without writing anything
+.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 EXTRA
+For records written before canon stored bound bytes (0.11\-0.13), and for any evidence file, or file of a current review, whose stored blob was lost. Each attachment whose working\-tree file still hashes to the recorded digest is copied into .canon/artifacts/sha256/<hex> (or uploaded to the object store); everything else is listed as not stored, with why. A superseded review\*(Aqs files are not stored, as the gate does not check them. Commit the store with the ledger.
+
+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.28.0

package/man/canon-artifacts-verify.1

@@ -0,0 +1,48 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-artifacts-verify 1  "verify 0.28.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
+\fBcanon artifacts verify\fR [\fB\-\-as\fR] [\fB\-\-full\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Check that the artifact store holds every file the latest evidence and current reviews bind (\-\-full re\-hashes the stored 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\-\-full\fR
+Download every blob and re\-hash it, instead of trusting the store\*(Aqs size and digest metadata
+.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 EXTRA
+Asks the store canon.yaml\*(Aqs `artifacts:` block selects (default: local, .canon/artifacts/sha256) about each bound file, the way `canon gate check` does. For an object store that is one HEAD per distinct digest plus the size and sha256 metadata written at upload; \-\-full downloads each blob and re\-hashes it.
+
+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.28.0

package/man/canon-artifacts.1

@@ -0,0 +1,45 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-artifacts 1  "artifacts 0.28.0" 
+.SH NAME
+canon\-artifacts \- Check or move the evidence artifact store (local, or an object\-store tier)
+.SH SYNOPSIS
+\fBcanon artifacts\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Check or move the evidence artifact store (local, or an object\-store 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\-artifacts\-verify(1)
+Check that the artifact store holds every file the latest evidence and current reviews bind (\-\-full re\-hashes the stored bytes)
+.TP
+canon\-artifacts\-store(1)
+Store the bound files of existing evidence records and current reviews in the artifact store (.canon/artifacts/sha256/)
+.TP
+canon\-artifacts\-move(1)
+Move the local artifact blobs to an object\-store tier, verify them, and remove the local copies
+.SH VERSION
+v0.28.0

package/man/canon-brief-approve.1

@@ -0,0 +1,62 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-brief-approve 1  "approve 0.28.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
+\fBcanon brief 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] [\fICHANGE_ID\fR] 
+.SH DESCRIPTION
+Record the human\*(Aqs approval of the brief, bound to its text; refused while `brief check` has blockers
+.SH OPTIONS
+.TP
+\fB\-\-approver\fR \fI<NAME>\fR
+Who approved (the human, not the agent)
+.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
+The human\*(Aqs own words
+.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
+[\fICHANGE_ID\fR]
+The change to read (default: the repo\*(Aqs only live change)
+.SH EXTRA
+Examples:
+  canon brief approve add\-login \-\-approver Ana \-\-note \*(AqGo. Ship the failure flow too.\*(Aq
+
+Writes `Approved: <who> <when> — "<words>" (brief sha256:<digest>)` into the
+brief (the digest covers the brief without its `Approved:` lines) and records
+`canon policy approve` in the same call. Edit the brief afterwards and it reads as
+not approved (BRIEF_CHANGED_SINCE_APPROVAL) 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.28.0

package/man/canon-brief-check.1

@@ -0,0 +1,44 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-brief-check 1  "check 0.28.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
+\fBcanon brief check\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] [\fICHANGE_ID\fR] 
+.SH DESCRIPTION
+Read the brief against the rules: blocker and advisory findings (exit 0 clean, 1 blockers, 2 refused)
+.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
+[\fICHANGE_ID\fR]
+The change to read (default: the repo\*(Aqs only live change)
+.SH VERSION
+v0.28.0

package/man/canon-brief-show.1

@@ -0,0 +1,50 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-brief-show 1  "show 0.28.0" 
+.SH NAME
+canon\-brief\-show \- Show where the change stands and the next one to three steps; never edits
+.SH SYNOPSIS
+\fBcanon brief show\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] [\fICHANGE_ID\fR] 
+.SH DESCRIPTION
+Show where the change stands and the next one to three steps; 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\-\-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
+[\fICHANGE_ID\fR]
+The change to read (default: the repo\*(Aqs only live change)
+.SH EXTRA
+Examples:
+  canon brief show
+  canon brief show add\-login \-\-json
+
+The operand names the change; without it the repo\*(Aqs only live change is read.
+.SH VERSION
+v0.28.0

package/man/canon-brief.1

@@ -0,0 +1,63 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-brief 1  "brief 0.28.0" 
+.SH NAME
+canon\-brief \- Check a change\*(Aqs brief (PRD format) and see the next steps; never edits
+.SH SYNOPSIS
+\fBcanon brief\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Check a change\*(Aqs brief (PRD format) and see the next steps; 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\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH SUBCOMMANDS
+.TP
+canon\-brief\-show(1)
+Show where the change stands and the next one to three steps; never edits
+.TP
+canon\-brief\-check(1)
+Read the brief against the rules: blocker and advisory findings (exit 0 clean, 1 blockers, 2 refused)
+.TP
+canon\-brief\-approve(1)
+Record the human\*(Aqs approval of the brief, bound to its text; refused while `brief check` has blockers
+.SH EXTRA
+Examples:
+  canon brief show                     State and the next one to three steps
+  canon brief check                    Findings; exit 0 clean, 1 blockers, 2 refused
+  canon brief check add\-login \-\-json
+
+The brief is the PRD `canon change new` writes: sections are found by their
+`<!\-\- canon:section <key> role=… \-\->` marker, never by heading text. Blockers
+(structure) are a missing or out\-of\-order section, a duplicate flow id, step
+detail that does not match the flow ids, leftover placeholders, and, once the
+subject is building, a flow step with no scenario or no failure scenario.
+Advisories (prose) apply to normative sections, Intent and Questions, in the
+language each is written in (`language:` in canon.yaml overrides); only en and
+ko have rule lists.
+Waive one rule in one section with
+  <!\-\- canon:waive <rule\-id> <section\-key> "<reason>" \-\->
+A brief without markers (written before 0.19) checks as `brief.legacy`, an
+advisory. Without \-\-change\-id, the repo\*(Aqs only live change is checked.
+.SH VERSION
+v0.28.0

package/man/canon-change-new.1

@@ -0,0 +1,66 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-change-new 1  "new 0.28.0" 
+.SH NAME
+canon\-change\-new \- Write .canon/changes/<slug>/brief.md, import it, and adopt it into a subject
+.SH SYNOPSIS
+\fBcanon change new\fR [\fB\-\-as\fR] <\fB\-\-subject\-id\fR> [\fB\-\-change\-kind\fR] <\fB\-\-title\fR> [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fICHANGE_ID\fR> 
+.SH DESCRIPTION
+Write .canon/changes/<slug>/brief.md, import it, and adopt it into a subject
+.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\-\-subject\-id\fR \fI<SUBJECT_ID>\fR
+The existing subject to adopt the change under
+.TP
+\fB\-\-change\-kind\fR \fI<CHANGE_KIND>\fR [default: feature]
+`feature` (default): the PRD brief. `chore`: a short brief for work that changes how the subject is built or kept, never what it does
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+feature
+.IP \(bu 2
+chore
+.RE
+.TP
+\fB\-\-title\fR \fI<TEXT>\fR
+The change\*(Aqs title (also its brief\*(Aqs summary)
+.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
+<\fICHANGE_ID\fR>
+The change\*(Aqs slug (its change_id)
+.SH VERSION
+v0.28.0

package/man/canon-change.1

@@ -0,0 +1,42 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-change 1  "change 0.28.0" 
+.SH NAME
+canon\-change \- Write a plan change (.canon/changes/<slug>/brief.md) and adopt it into a subject
+.SH SYNOPSIS
+\fBcanon change\fR [\fB\-\-as\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIsubcommands\fR>
+.SH DESCRIPTION
+Write a plan change (.canon/changes/<slug>/brief.md) and adopt it into a subject
+.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\-change\-new(1)
+Write .canon/changes/<slug>/brief.md, import it, and adopt it into a subject
+.SH EXTRA
+Examples:
+  canon change new add\-login \-\-subject\-id auth \-\-title \*(AqAdd login\*(Aq
+.SH VERSION
+v0.28.0

package/man/canon-completion.1

@@ -0,0 +1,60 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-completion 1  "completion 0.28.0" 
+.SH NAME
+canon\-completion \- Write the shell completion script for canon (bash, zsh or fish)
+.SH SYNOPSIS
+\fBcanon completion\fR [\fB\-\-as\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fISHELL\fR> 
+.SH DESCRIPTION
+Write the shell completion script for canon (bash, zsh or fish)
+.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\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+<\fISHELL\fR>
+Shell to write the completion script for
+.br
+
+.br
+\fIPossible values:\fR
+.RS 14
+.IP \(bu 2
+bash
+.IP \(bu 2
+zsh
+.IP \(bu 2
+fish
+.RE
+.SH EXTRA
+Examples:
+  canon completion zsh > ~/.zfunc/_canon
+  canon completion bash > /etc/bash_completion.d/canon
+  canon completion fish > ~/.config/fish/completions/canon.fish
+
+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.28.0

package/man/canon-context-pack-add.1

@@ -0,0 +1,47 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-context-pack-add 1  "add 0.28.0" 
+.SH NAME
+canon\-context\-pack\-add \- Create an immutable context pack from a repository\-local JSON manifest
+.SH SYNOPSIS
+\fBcanon context\-pack add\fR [\fB\-\-as\fR] <\fB\-\-manifest\fR> [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-\-input\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] 
+.SH DESCRIPTION
+Create an immutable context pack 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 pack 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
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.SH VERSION
+v0.28.0

package/man/canon-context-pack-show.1

@@ -0,0 +1,44 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-context-pack-show 1  "show 0.28.0" 
+.SH NAME
+canon\-context\-pack\-show \- Show a context pack after verifying its manifest and content objects
+.SH SYNOPSIS
+\fBcanon context\-pack show\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIPACK_ID\fR> 
+.SH DESCRIPTION
+Show a context pack after verifying its manifest and content objects
+.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 pack manifest as JSON
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+<\fIPACK_ID\fR>
+Context pack id (sha256:<64 hex digits>)
+.SH VERSION
+v0.28.0

package/man/canon-context-pack-verify.1

@@ -0,0 +1,44 @@
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.TH canon-context-pack-verify 1  "verify 0.28.0" 
+.SH NAME
+canon\-context\-pack\-verify \- Verify a context pack\*(Aqs manifest and immutable content objects
+.SH SYNOPSIS
+\fBcanon context\-pack verify\fR [\fB\-\-as\fR] [\fB\-\-repo\fR] [\fB\-\-json\fR] [\fB\-h\fR|\fB\-\-help\fR] [\fB\-V\fR|\fB\-\-version\fR] <\fIPACK_ID\fR> 
+.SH DESCRIPTION
+Verify a context pack\*(Aqs manifest and immutable content objects
+.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 a JSON verification result
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print version
+.TP
+<\fIPACK_ID\fR>
+Context pack id (sha256:<64 hex digits>)
+.SH VERSION
+v0.28.0