canon-operatorlisted

# Canon operator Front door to the toolkit. Orient first, then run the simplest operation that satisfies the intent or hand off to the owning skill. Never bypass `canon` to edit managed files by hand. ## Orient Run these from the target project root, in parallel, before acting: - `canon docs list`: the index of toolkit reference docs - `canon docs agents`: the CLI command catalog and invocation contract - `canon docs target-projects`: the scaffold, add-a-domain, and sync lifecycle Load a domain doc with `canon docs <topic>` only when the intent touches that domain. Read the live catalog for any domain you act on with `canon <domain> list --json`. Never hardcode stack, rule, snippet, or standards names. ## Diagnose Run `canon sync --check . --json` before routing. It reports what a target is behind on across every surface, so the intent comes from the project state rather than from the user having to know it already. Skip only when the user named a single operation to run. Read seven fields off the report and carry each to `## Route`: - `unmigrated`: a domain sitting at the root layout with nothing under `.claude/`. The most urgent finding, because that domain reports no drift of its own while being entirely behind - `superseded`: a file a newer seed folder replaced. No command moves it, since the content is the project's own, so this routes to the skill that proposes the split rather than ending at the report - `seeds`: entries are `matching`, `stale`, `drifted`, or