@journeykit/canon 0.32.0 → 0.34.0

package/dist/skills/reference/role-orchestrator.md

@@ -18,7 +18,7 @@ in your ids. Use only the options on a line; never guess one. Ask `canon schema
 <command> --json` only for a leaf this block does not list, or after a `USAGE` refusal.
 
 <!-- canon:generated commands-orchestrator begin -->
-Every leaf takes `--as <ROLE>` and `--json`; `--repo <DIR>` too, except `completion`, `regime show`, `schema`, `selftest`, `skills show`. `--input <JSON|FILE|->` runs a leaf from one JSON document (an array is a batch) and is only on the lines ending `[--input]`. Its document keys are the option names in camelCase, singular even when the option repeats (the value is then an array), and `operands` holds the operands. `--fields <FIELDS>` is a comma list; camelCase and snake_case both match.
+Every leaf takes `--as <ROLE>` and `--json`; `--repo <DIR>` too, except `completion`, `regime show`, `schema`, `selftest`, `skills show`. `--input <JSON|FILE|->` runs a leaf from one JSON document (an array is a batch) and is only on the lines ending `[--input]`. Its document keys are the option names in camelCase, singular even when the option repeats (the value is then an array), and `operands` holds the operands. `--fields <FIELDS>` is a comma list of the paths `canon schema <COMMAND> --json` declares under `outputs[].fields.paths`; a path is the record's own key, spelled as the answer spells it.
 In a syntax line `<X>` is a value, `[x]` optional, `a | b` a choice, `(a | b)` exactly one is required, `[--x <V>]*` may repeat, `<X>+` is one or more, `[--a --b <V>]` go together. An option that is not on the line does not exist: it is refused (`USAGE`).
 
 ```text
@@ -26,14 +26,14 @@ In a syntax line `<X>` is a value, `[x]` optional, `a | b` a choice, `(a | b)` e
 canon adapter authorize --response <FILE>
 ```
 ```bash
-canon adapter authorize --response adapter-response.json --repo .
+canon adapter authorize --response adapter-response.json --repo . --json
 ```
 ```text
 # Read and validate one provider-neutral response envelope
 canon adapter validate --response <FILE>
 ```
 ```bash
-canon adapter validate --response adapter-response.json
+canon adapter validate --response adapter-response.json --json
 ```
 ```text
 # Move the local artifact blobs to an object-store tier, verify them, and remove the local copies
@@ -41,182 +41,182 @@ canon artifacts move --tier <TIER> [--commit --plan-digest <DIGEST>] [--input]
 # a bare run previews and prints planDigest; `--commit --plan-digest <DIGEST>` with that digest acts
 ```
 ```bash
-canon artifacts move --tier cold
+canon artifacts move --tier cold --json
 ```
 ```text
 # Store the bound files of existing evidence records and current reviews in the artifact store (.canon/artifacts/sha256/)
 canon artifacts store [--max-artifact-mib <N>] [--dry-run] [--input]
 ```
 ```bash
-canon artifacts store
+canon artifacts store --json
 ```
 ```text
 # Check that the artifact store holds every file the latest evidence and current reviews bind (--full re-hashes the stored bytes)
 canon artifacts verify [--full]
 ```
 ```bash
-canon artifacts verify
+canon artifacts verify --json
 ```
 ```text
 # Write the shell completion script for canon (bash, zsh or fish)
 canon completion <SHELL>
 ```
 ```bash
-canon completion zsh
+canon completion zsh --json
 ```
 ```text
 # Show what you can author here: record kinds, fields, enums, policies
 canon context [--fields <FIELDS>]
 ```
 ```bash
-canon context
+canon context --json
 ```
 ```text
 # Create an immutable context pack from a repository-local JSON manifest
 canon context-pack add --manifest <FILE> [--input]
 ```
 ```bash
-canon context-pack add --manifest .canon/context-manifest.json
+canon context-pack add --manifest .canon/context-manifest.json --json
 ```
 ```text
 # Show a context pack after verifying its manifest and content objects
 canon context-pack show <PACK_ID>
 ```
 ```bash
-canon context-pack show sha256:0000000000000000000000000000000000000000000000000000000000000000
+canon context-pack show sha256:0000000000000000000000000000000000000000000000000000000000000000 --json
 ```
 ```text
 # Verify a context pack's manifest and immutable content objects
 canon context-pack verify <PACK_ID>
 ```
 ```bash
-canon context-pack verify sha256:0000000000000000000000000000000000000000000000000000000000000000
+canon context-pack verify sha256:0000000000000000000000000000000000000000000000000000000000000000 --json
 ```
 ```text
 # Serve the local status dashboard
 canon dashboard [--snapshot <DIR>] [--port <N>] [--input]
 ```
 ```bash
-canon dashboard
+canon dashboard --json
 ```
 ```text
 # Scaffold the demo repo (gate starts RED)
 canon demo init [--input]
 ```
 ```bash
-canon demo init --repo canon-demo
+canon demo init --repo canon-demo --json
 ```
 ```text
 # Record the missing reviewer evidence (gate turns GREEN)
 canon demo review [--input]
 ```
 ```bash
-canon demo review
+canon demo review --json
 ```
 ```text
 # Mint a Run manifest with retrieved guidance and context/policy lineage
-canon dispatch begin --regime <KEY> [--role <ROLE>] [--actor <ACTOR_ID>] [--session <SESSION_ID>] [--provider <NAME>] [--model <NAME>] [--skill <ID>] [--skill-digest <DIGEST>] [--manifest <FILE>] [--prompt-bundle <NAME@VERSION>] [--task <TASK_ID>] [--parent-run <RUN_ID>] [--input]
+canon dispatch begin --regime <KEY> [--role <ROLE>] [--actor <ACTOR_ID>] [--session <SESSION_ID>] [--provider <NAME>] [--model <NAME>] [--skill <ID>] [--skill-digest <DIGEST> (with --skill)] [--manifest <FILE>] [--prompt-bundle <NAME@VERSION>] [--task <TASK_ID>] [--parent-run <RUN_ID>] [--input]
 ```
 ```bash
-canon dispatch begin --regime implementer/my-repo/api/abcdef012345 --role implementer
+canon dispatch begin --regime implementer/my-repo/api/abcdef012345 --role implementer --json
 ```
 ```text
 # Diff the declared plan DAG against the observed execution graph
 canon dispatch diff
 ```
 ```bash
-canon dispatch diff
+canon dispatch diff --json
 ```
 ```text
 # Close a dispatched run with a terminal status and an ended_at
 canon dispatch end <RUN_ID> --run-outcome <succeeded|failed> [--input]
 ```
 ```bash
-canon dispatch end 01ARZ3NDEKTSV4RRFFQ69G5FAV --run-outcome succeeded
+canon dispatch end 01ARZ3NDEKTSV4RRFFQ69G5FAV --run-outcome succeeded --json
 ```
 ```text
 # List the current divergence burn-down state
 canon divergence list [--as-of <TIMESTAMP>] [--limit <N> | --all] [--cursor <CURSOR>] [--fields <FIELDS>]
 ```
 ```bash
-canon divergence list --as-of 2030-01-01
+canon divergence list --as-of 2030-01-01 --json
 ```
 ```text
 # Emit exact bytes for external `ssh-keygen -Y sign -n canon-approval-v1`
 canon evidence approval-payload --approver <NAME> --approval-at <TIMESTAMP> [--task <TASK_ID>] [--project <PROJECT_ID>] [--scenario <SCENARIO_ID>] [--run <RUN_ID>] [--rev <REV>] [--surface-ref <PATH_OR_EFFECT>]*
 ```
 ```bash
-canon evidence approval-payload --scenario auth.login.01 --project root --approver alice --approval-at 2030-01-01T00:00:00Z
+canon evidence approval-payload --scenario auth.login.01 --project root --approver alice --approval-at 2030-01-01T00:00:00Z --json
 ```
 ```text
 # Export a redacted retention manifest without deleting records
 canon export --kind <change|task|scenario|session|run|event|handoff|review|divergence|trajectory|strategy_item|evidence|subject|finding> [--before <TIMESTAMP>] [--after <TIMESTAMP>] [--output <FILE>] [--include-sensitive] [--limit <N> | --all] [--cursor <CURSOR>] [--fields <FIELDS>] [--dry-run] [--input]
 ```
 ```bash
-canon export --kind evidence --output evidence.json
+canon export --kind evidence --output evidence.json --json
 ```
 ```text
 # List a change's committed findings at their latest version
 canon finding list --change <CHANGE_ID> [--open] [--limit <N> | --all] [--cursor <CURSOR>] [--fields <FIELDS>]
 ```
 ```bash
-canon finding list --change add-login
+canon finding list --change add-login --json
 ```
 ```text
 # Validate a spec/artifact corpus against canon's format
 canon format [<DIR>]
 ```
 ```bash
-canon format .canon/specs
+canon format .canon/specs --json
 ```
 ```text
 # Run the coverage/ledger/staleness/trust checks (0 clean, 1 red, 2 usage)
 canon gate check [--release]
 ```
 ```bash
-canon gate check
+canon gate check --json
 ```
 ```text
 # Install the gate hook into .claude/settings.json / .codex/hooks.json
 canon gate install-hooks [--event <NAME>] [--matcher <TEXT>] [--command <TEXT>] [--timeout <N>] [--dry-run] [--input]
 ```
 ```bash
-canon gate install-hooks
+canon gate install-hooks --json
 ```
 ```text
 # Import plans as Change/Task records
 canon ingest plans [--dialect <NAME> --plan-source <DIR>] [--dry-run] [--input]
 ```
 ```bash
-canon ingest plans
+canon ingest plans --json
 ```
 ```text
 # Import review/divergence/task/handoff records and derive verdicts
 canon ingest records [--watch] [--interval-secs <N>] [--dry-run] [--run <RUN_ID>] [--input]
 ```
 ```bash
-canon ingest records
+canon ingest records --json
 ```
 ```text
 # Import agent CLI session transcripts (omp/pi, Claude Code, Codex, Hermes)
 canon ingest sessions [--watch] [--interval-secs <N>] [--home <DIR>] [--full] [--all-workspaces] [--dry-run] [--input]
 ```
 ```bash
-canon ingest sessions
+canon ingest sessions --json
 ```
 ```text
 # Set up canon in a repo (canon.yaml, a starter policy, the AGENTS.md block, a plans home)
 canon init [--check] [--no-agents-md | --check] [--policy <light|standard|strict> | --check | --no-policy] [--providers <LIST> | --check] [--language <TAG> | --check] [--dry-run | --check] [--input]
 ```
 ```bash
-canon init
+canon init --json
 ```
 ```text
 # Validate each spec root, then materialize scenario index records
 canon inventory sync [--spec-root <DIR>] [--dry-run] [--input]
 ```
 ```bash
-canon inventory sync
+canon inventory sync --json
 ```
 ```text
 # Move superseded versions of every record out of the ledger into the archive
@@ -224,7 +224,7 @@ canon ledger compact [--commit --plan-digest <DIGEST>] [--input]
 # a bare run previews and prints planDigest; `--commit --plan-digest <DIGEST>` with that digest acts
 ```
 ```bash
-canon ledger compact
+canon ledger compact --json
 ```
 ```text
 # Bring a repo from an earlier canon up to date
@@ -232,35 +232,35 @@ canon migrate [--commit --plan-digest <DIGEST>] [--revert | --relayed-via <NAME>
 # a bare run previews and prints planDigest; `--commit --plan-digest <DIGEST>` with that digest acts
 ```
 ```bash
-canon migrate
+canon migrate --json
 ```
 ```text
 # Validate and write a plugin's overlay records
 canon plugin sync <PLUGIN_ID> [--spec-root <DIR>] [--dry-run] [--input]
 ```
 ```bash
-canon plugin sync my-plugin
+canon plugin sync my-plugin --json
 ```
 ```text
 # Show the policy's digest and its approval (who, when, which bytes)
 canon policy show
 ```
 ```bash
-canon policy show
+canon policy show --json
 ```
 ```text
 # Add a prompt bundle from a repository-local JSON manifest
 canon prompt add <NAME@VERSION> --manifest <FILE> [--input]
 ```
 ```bash
-canon prompt add reviewer@v1 --manifest .canon/prompt-manifest.json
+canon prompt add reviewer@v1 --manifest .canon/prompt-manifest.json --json
 ```
 ```text
 # Select a registered prompt bundle version
 canon prompt show <NAME@VERSION>
 ```
 ```bash
-canon prompt show reviewer@v1
+canon prompt show reviewer@v1 --json
 ```
 ```text
 # Remove allowlisted records older than a cutoff
@@ -268,161 +268,161 @@ canon purge --kind <session|run|event|trajectory> --before <TIMESTAMP> [--commit
 # a bare run previews and prints planDigest; `--commit --plan-digest <DIGEST>` with that digest acts
 ```
 ```bash
-canon purge --kind session --before 2020-01-01T00:00:00Z
+canon purge --kind session --before 2020-01-01T00:00:00Z --json
 ```
 ```text
 # Read stored records across every storage tier
 canon query --kind <change|task|scenario|session|run|event|handoff|review|divergence|trajectory|strategy_item|evidence|subject|finding> [--since <TIMESTAMP>] [--plugin <PLUGIN_ID> | --history] [--change <CHANGE_ID>] [--status <STATUS>] [--domain <NAME>] [--include-sensitive] [--limit <N> | --all] [--cursor <CURSOR>] [--fields <FIELDS>]
 ```
 ```bash
-canon query --kind evidence
+canon query --kind evidence --json
 ```
 ```text
 # Build a canonical regime key for hook scripts
 canon regime show --role-segment <NAME> --repo-name <NAME> --area <NAME> --hash <HASH>
 ```
 ```bash
-canon regime show --role-segment reviewer --repo-name my-repo --area api --hash abcdef012345
+canon regime show --role-segment reviewer --repo-name my-repo --area api --hash abcdef012345 --json
 ```
 ```text
 # Write the status report (.canon/REPORT.md)
 canon report build [--input]
 ```
 ```bash
-canon report build
+canon report build --json
 ```
 ```text
 # Byte-diff .canon/REPORT.md against a fresh build (0 fresh, 1 missing or drifted); writes nothing
 canon report check
 ```
 ```bash
-canon report check
+canon report check --json
 ```
 ```text
 # Export the panel marts to <DIR>/*.parquet plus manifest.json
 canon report snapshot <DIR> [--input]
 ```
 ```bash
-canon report snapshot snapshot-out
+canon report snapshot snapshot-out --json
 ```
 ```text
 # Fetch role-scoped strategy guidance
-canon retrieve --for-role <ROLE> [--regime <KEY>] [--domain <NAME>] [--subject <SUBJECT_ID>] [--limit <N>]
+canon retrieve --for-role <ROLE> (--regime <KEY> | --domain <NAME>) [--subject <SUBJECT_ID> (with --domain)] [--limit <N>]
 ```
 ```bash
-canon retrieve --for-role reviewer --domain dev --limit 20
+canon retrieve --for-role reviewer --domain dev --limit 20 --json
 ```
 ```text
 # Describe canon's own commands
-canon schema [<PATH>]* [--errors | --error <CODE>]
+canon schema [<PATH>]* [--errors | --error <CODE> | --warning <CODE> | --warnings]
 ```
 ```bash
-canon schema evidence add
+canon schema evidence add --json
 ```
 ```text
 # Search records, brief sections and scenario text, with each hit's neighbors in the record graph
 canon search <TEXT> [--kind <change|task|scenario|session|run|event|handoff|review|divergence|trajectory|strategy_item|evidence|subject|finding|brief>]* [--expand <N>] [--limit <N>]
 ```
 ```bash
-canon search timeout --kind finding
+canon search timeout --kind finding --json
 ```
 ```text
 # Run canon's built-in fixture self-tests
 canon selftest [--suite <trust-spine-gate|tiered-storage|typed-authoring-vocabulary|policy-expressions|format-authority|session-ingest|canon-context|artifact-ingest|spec-ledger-selftest|plugin-overlays|plan-import>]
 ```
 ```bash
-canon selftest --suite trust-spine-gate
+canon selftest --suite trust-spine-gate --json
 ```
 ```text
 # Check canonical projections without writing; exit 1 on drift, a legacy remnant, or a lock another canon version wrote
 canon skills check [--skills-source <DIR>] [--providers <LIST>]
 ```
 ```bash
-canon skills check
+canon skills check --json
 ```
 ```text
 # Print diagnostics for canonical projections, the install lock's 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
 canon skills doctor [--skills-source <DIR>] [--providers <LIST>]
 ```
 ```bash
-canon skills doctor
+canon skills doctor --json
 ```
 ```text
 # Install the canonical `canon` bundle or legacy developer skills
 canon skills install [--skills-source <DIR>] [--providers <LIST>] [--dry-run] [--input]
 ```
 ```bash
-canon skills install
+canon skills install --json
 ```
 ```text
 # Print a guide built into this binary (markdown on stdout); the installed SKILL.md is a stub that points here
 canon skills show <NAME> [--full]
 ```
 ```bash
-canon skills show canon --full
+canon skills show canon --full --json
 ```
 ```text
 # Show where this repo stands: subjects by status, their gaps, and the next commands
 canon status [--fields <FIELDS>]
 ```
 ```bash
-canon status
+canon status --json
 ```
 ```text
 # The unsigned approval payload bytes an external signer signs
 canon strategy approval-payload <STRATEGY_ID> --evaluation <FILE> --approver <NAME> --approval-at <TIMESTAMP>
 ```
 ```bash
-canon strategy approval-payload 01ARZ3NDEKTSV4RRFFQ69G5FAV --evaluation evaluation.json --approver alice --approval-at 2030-01-01T00:00:00Z
+canon strategy approval-payload 01ARZ3NDEKTSV4RRFFQ69G5FAV --evaluation evaluation.json --approver alice --approval-at 2030-01-01T00:00:00Z --json
 ```
 ```text
 # Promote a strategy after paired evaluation and signed approval
 canon strategy promote <STRATEGY_ID> [--evaluation <FILE> --approval <FILE>] [--signature-file <FILE> (with --approval)] [--dry-run] [--input]
 ```
 ```bash
-canon strategy promote 01ARZ3NDEKTSV4RRFFQ69G5FAV
+canon strategy promote 01ARZ3NDEKTSV4RRFFQ69G5FAV --json
 ```
 ```text
 # Disable an active strategy with durable rollback provenance
 canon strategy rollback <STRATEGY_ID> --reason <TEXT> --actor <ACTOR_ID> --signature-file <FILE> --approval-at <TIMESTAMP> [--contradicting-trajectory <ID>] [--input]
 ```
 ```bash
-canon strategy rollback 01ARZ3NDEKTSV4RRFFQ69G5FAV --reason "regressed in production" --actor alice --signature-file approval.sig --approval-at 2030-01-01T00:00:00Z
+canon strategy rollback 01ARZ3NDEKTSV4RRFFQ69G5FAV --reason "regressed in production" --actor alice --signature-file approval.sig --approval-at 2030-01-01T00:00:00Z --json
 ```
 ```text
 # Link an imported plan change to a subject (adopting it under another subject adds that subject; a change may belong to several)
 canon subject adopt <SUBJECT_ID> --change <CHANGE_ID> [--dry-run] [--input]
 ```
 ```bash
-canon subject adopt demo --change add-login
+canon subject adopt demo --change add-login --json
 ```
 ```text
 # 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)
 canon subject move <SUBJECT_ID> --to <proposed|specced|building|verifying|shipped|retired> [--override-reason <TEXT>] [--reason <TEXT>] [--actor <ACTOR_ID>] [--session <SESSION_ID>] [--input]
 ```
 ```bash
-canon subject move demo --to specced
+canon subject move demo --to specced --json
 ```
 ```text
 # Author a new subject at status `proposed`
 canon subject new <SUBJECT_ID> --domain <NAME> --title <TEXT> [--summary <TEXT>] [--owner-role <ROLE>] [--actor <ACTOR_ID>] [--session <SESSION_ID>] [--input]
 ```
 ```bash
-canon subject new payments --domain dev --title Payments
+canon subject new payments --domain dev --title Payments --json
 ```
 ```text
 # Show a subject (read-only)
 canon subject show <SUBJECT_ID>
 ```
 ```bash
-canon subject show demo
+canon subject show demo --json
 ```
 ```text
 # Take a change back out of a subject (the mirror of adopt; refused for a change whose brief is approved)
 canon subject unadopt <SUBJECT_ID> --change <CHANGE_ID> [--dry-run] [--input]
 ```
 ```bash
-canon subject unadopt demo --change add-login
+canon subject unadopt demo --change add-login --json
 ```
 ```text
 # Apply canon.yaml aging rules, moving old records to their destination tier
@@ -430,24 +430,24 @@ canon tier age [--commit --plan-digest <DIGEST>] [--input]
 # a bare run previews and prints planDigest; `--commit --plan-digest <DIGEST>` with that digest acts
 ```
 ```bash
-canon tier age
+canon tier age --json
 ```
 ```text
 # Follow a finding's review loop in time order: review, finding, fix, re-review, evidence
 canon trace <ID>
 ```
 ```bash
-canon trace add-login_1_1
+canon trace add-login_1_1 --json
 ```
 <!-- canon:generated commands-orchestrator end -->
 
 ## Read the state
 
 `canon status` lists the next steps, each with the `role` that takes it
-(`null` for the human), and `waitingOn` counts the steps held by each other
+(`null` for the human), and `data.waitingOn` counts the steps held by each other
 owner, `human` included. Call it once at the start and when resuming, not
 after a write: after `subject move --to` or a spawned role's write, the
-write's `meta.next` and `meta.waitingOn` are the status for what it touched.
+write's `meta.next` and `data.waitingOn` are the status for what it touched.
 
 ## Spawn each role
 
@@ -510,7 +510,7 @@ not sign off.
 
 ## Relay the human's answer
 
-When `status` or `meta.next` shows a step with `actor: human` (the brief's
+When `status` or `meta.next` shows a step with `x-canon.actor: human` (the brief's
 approval), stop everything for that scope and put the brief in front of the
 human in its language: `canon brief show <slug> --body` prints the brief and,
 last, its digest. Send the output to the human's own view, never retyped (omp:
@@ -563,7 +563,7 @@ holds the next command and the verified claims (`canon skills show canon-vocab`)
 After a timeout or a lost response, repeat the write only when its repeat is
 safe. `evidence add`, `review scenario`, `review change` and `finding add`
 are content-keyed: an identical repeat returns the existing record with
-`meta.unchanged: true` (a batch reports the element `unchanged`).
+`data.unchanged: true` (a batch reports the element `unchanged`).
 `finding close`, `subject adopt`, `inventory sync`, `ingest *`, `gate
 promote` and `task done` are replay-safe the same way. `subject new`,
 `change new`, `feature new`, `scenario new`, `subject move` and `dispatch
@@ -580,7 +580,7 @@ its preview, never from an old digest.
 | "The reviewer can be me under another label." | The reviewer is a separate process with its own real session id (#39). |
 | "Approve the brief; the human said they are busy." | An answer they did not give is not recorded. Show the brief, ask, and record only an explicit approval with `--relayed-via`. |
 | "Override the refusal to ship." | Fix the gap the refusal names; `--override-reason` waives only the `require_review` gaps and the brief gap, is recorded on the subject, and is for the human's call, not a shortcut. |
-| "Run the commit now, the preview looked fine earlier." | A bare run previews; `--commit --plan-digest` acts only on the plan you just previewed (`PLAN_CHANGED` otherwise). Preview again, then act. |
+| "Run the commit now, the preview looked fine earlier." | A bare run previews; `--commit --plan-digest` acts only on the plan you just previewed (`PLAN_STALE` otherwise). Preview again, then act. |
 | "I have corrected this agent before." | A correction repeated across runs belongs in a scenario, the policy or a gate, not more prose. Tell the human. |
 
 ## Move the subject
@@ -623,10 +623,10 @@ read the refusal in `error` of `canon subject move demo --to shipped --json`.
 move` and `canon migrate` delete or rewrite existing data. A bare run only
 previews: exit 0, nothing written, a report with `planDigest` and
 `effects[]`. Read the effects, then act with `--commit --plan-digest
-<planDigest>`; it refuses (`PLAN_CHANGED`, exit 2) when the plan recomputed
+<planDigest>`; it refuses (`PLAN_STALE`, exit 2) when the plan recomputed
 now differs from the one you previewed. A document passed with `--input`
 never carries `--commit` or `--plan-digest`, and these five leaves take one
-object only (`INPUT_BATCH_UNSUPPORTED`).
+object only (`INPUT_INVALID`).
 
 ```bash
 canon purge --kind session --before 2026-01-01
@@ -678,6 +678,6 @@ git-ignored, and `canon migrate --revert` needs it (keep it until you are sure).
 **Done when:** `canon migrate` reports nothing left to move, `canon skills
 check` exits 0, and `canon status` and `canon gate check` no longer warn
 about 0.27 state; read the first in `data` of `canon migrate --json`, the
-others in `meta.warnings`.
+others in `meta.warnings` (`[{code, message}]`).
 
 Reference: `canon skills show canon-subject`.