@erclx/canon 5.20.0 → 5.22.0

package/docs/agents/slides.md

@@ -0,0 +1,164 @@
+---
+title: Slides
+description: What a folder of HTML slides declares for the whole deck in deck.json, the faces it embeds, what each slide declares on its own body, transitions and entrances, the master built from the project's tokens, speaker notes, charts, and what each refusal reports
+---
+
+# Slides
+
+`canon slides render --source <folder>` turns a folder of `.html` slides into an editable PowerPoint deck. Each slide describes its own shapes. What belongs to the whole deck, being the bands, the numbers, and the mark, sits in one file beside them, and the master that carries it takes the project's own colors and face.
+
+```bash
+canon slides render --source slides/q3-review
+```
+
+## The deck file
+
+`deck.json` beside the slides is optional. Without it the deck gets its defaults.
+
+| Field          | Default                        | What it sets                                      |
+| -------------- | ------------------------------ | ------------------------------------------------- |
+| `title`        | the folder name                | the file's title and the default footer text      |
+| `header`       | off                            | a band at the top, with `left`, `center`, `right` |
+| `footer`       | on, with the title on the left | a band at the bottom, with the same three slots   |
+| `slideNumbers` | `true`                         | the number at the right of the footer             |
+| `mark`         | none                           | an image path, relative to the folder, top right  |
+| `fonts`        | none                           | faces to embed in the file, described below       |
+
+```json
+{
+  "title": "Q3 review",
+  "header": { "left": "Acme" },
+  "footer": { "center": "Internal" },
+  "mark": "assets/mark.png",
+  "fonts": [
+    { "family": "Inter", "path": "fonts/Inter-Regular.ttf" },
+    { "family": "Inter", "weight": 700, "path": "fonts/Inter-Bold.ttf" }
+  ]
+}
+```
+
+A band takes `show` and the three slots. A declared band merges over its default, so `"footer": { "center": "Internal" }` keeps the title on the left. Declaring any slot turns a band on unless it also says `"show": false`. Set a slot to `""` to empty it.
+
+Slide numbers belong to the footer and hold its right slot. They show only where the footer does, and `footer.right` needs `slideNumbers` set to `false`.
+
+Prefer a raster mark. An SVG mark lands as a vector, and its fallback for a viewer that cannot draw SVG comes out broken.
+
+### Embedded faces
+
+Each entry in `fonts` names one TrueType or OpenType file inside the deck folder, and the deck carries it so it renders in its own face on a machine without the font installed.
+
+- `family` is required and should match the family the slides set, since that is the name PowerPoint looks the face up by.
+- `weight` defaults to `400`. PowerPoint holds four faces a family, so `600` and above fills the bold slot and anything lighter fills regular.
+- `style` is `normal` or `italic`, defaulting to `normal`.
+- `path` is relative to the folder and has to stay inside it.
+
+A face is refused, and the deck still written without it, when its license forbids embedding or allows a bitmap only, when it is a variable font, when it is a `woff` or `woff2` file, or when a second face lands in a slot one already fills. Supply static instances, one per weight, in place of a variable face. For `woff2`, supply the TrueType or OpenType file it was compressed from, which most font downloads ship beside it.
+
+## What each slide declares
+
+A slide sets its own place in the deck through attributes on `<body>`.
+
+| Attribute                               | Effect                                        |
+| --------------------------------------- | --------------------------------------------- |
+| `data-section="Results"`                | opens a section the slides after it stay in   |
+| `data-hidden`                           | hides the slide in the show                   |
+| `data-header="off"`                     | drops the header on this slide                |
+| `data-footer="off"`                     | drops the footer and its number on this slide |
+| `data-footer-left`, `-center`, `-right` | replaces that footer slot on this slide alone |
+| `data-header-left`, `-center`, `-right` | replaces that header slot on this slide alone |
+
+Once any slide opens a section, slides ahead of the first one sit in a section named after the deck, since PowerPoint wants every slide in one. A title the deck returns to after another section opens a new section numbered `Intro (2)`, so each section stays one run of slides.
+
+A slide dropping one band keeps the other from the master. A slide replacing a slot draws its band as its own text, so editing that band once in PowerPoint's master view reaches every slide except the ones that replaced it.
+
+## Motion
+
+A slide declares how it arrives on `<body>`, and an element declares how it comes in on its own tag.
+
+| Attribute                  | Takes                           | Effect                                 |
+| -------------------------- | ------------------------------- | -------------------------------------- |
+| `data-transition`          | `fade`, `push`, `wipe`, `cover` | the transition into this slide         |
+| `data-transition-duration` | `500`, `500ms`, or `0.5s`       | rounded to 0.5, 0.75, or 1 second      |
+| `data-enter`               | `fade`, `fly`, `wipe`, `zoom`   | an entrance played on a click          |
+| `data-enter-order`         | a number                        | the click it plays on, lowest first    |
+| `data-enter-duration`      | `500`, `500ms`, or `0.5s`       | the entrance length, 500 ms by default |
+
+```html
+<body data-transition="fade">
+  <h1>Results</h1>
+  <div class="card" data-enter="fly" data-enter-order="1">…</div>
+  <div class="card" data-enter="fly" data-enter-order="2">…</div>
+</body>
+```
+
+Each entrance is its own click. Entrances without an order play after the ordered ones, in page order. An entrance brings in every shape drawn from its element and the elements inside it together, so a card's box and its text arrive on one click, and an element drawn as a picture brings in that picture. An element inside it with its own `data-enter` waits for its own click. Fly comes in from the bottom and wipe from the left.
+
+A transition length rounds to the nearest of the three speeds PowerPoint's file format names, since a length in milliseconds needs an extension the deck does not write.
+
+## The master
+
+The master takes its colors from the `<html>` element of the first slide as Chromium laid it out with the project's token stylesheet injected, so a theme switched on one slide's `<body>`, such as a dark cover, stays on that slide:
+
+- `--color-background`: the slide ground
+- `--color-text`: the header text
+- `--color-muted`: the footer text
+- `--color-accent`: the slide number
+- the `<body>` font family, first name with a ` Variable` suffix dropped: the theme face
+
+A role the project declares no token for falls back to the slide body's own color and prints one `✗` line naming it. It never falls back to the toolkit's palette.
+
+A slide whose `<body>` background differs from the master's keeps its own. A slide whose `<body>` computes a `--color-text` apart from the master's prints one `✗` line naming it, since its bands keep the master's colors and may not read against its ground.
+
+## Speaker notes
+
+`<aside class="notes">` becomes the slide's notes and is never drawn. Each paragraph or list item becomes its own line, and markup is dropped.
+
+## Charts
+
+A `<figure data-chart="...">` holding a `<table>` becomes a native, editable chart placed where the figure was laid out. The table stays the page's accessible source and is not drawn as well.
+
+```html
+<figure data-chart="bar" data-labels>
+  <figcaption>Revenue by region</figcaption>
+  <table>
+    <tr>
+      <th>Region</th>
+      <th>Q1</th>
+      <th>Q2</th>
+    </tr>
+    <tr>
+      <td>North</td>
+      <td>12</td>
+      <td>16</td>
+    </tr>
+    <tr>
+      <td>South</td>
+      <td></td>
+      <td>11</td>
+    </tr>
+  </table>
+</figure>
+```
+
+- `data-chart` takes `bar`, `line`, `area`, `pie`, or `doughnut`.
+- The header row names the series and the first column names the categories.
+- An empty cell is a gap, not a zero. A comma is a thousands separator only where it groups in threes, as in `12,345.5`, so a comma-decimal `3,5` refuses rather than reading as 35.
+- `data-labels` shows each value. A `<figcaption>` becomes the chart title.
+- Series take the accent first, then every other declared `--color-*` role in sheet order except the background and surface, repeating past the last.
+
+## Refusals
+
+| Case                                   | Report                                         | Exit |
+| -------------------------------------- | ---------------------------------------------- | ---- |
+| `deck.json` field malformed or unknown | `✗` naming the file and the field              | 1    |
+| `mark` path missing                    | `✗` naming the resolved path                   | 1    |
+| `fonts` path missing or outside folder | `✗` naming the field and the path              | 1    |
+| face not embeddable                    | `✗` naming the path and the reason             | 0    |
+| unknown transition or entrance name    | `✗` naming the slide, the element, the effect  | 0    |
+| entrance on an element that draws none | `✗` naming the slide and the element           | 0    |
+| chart cell not a number                | `✗` naming the slide, the figure, and the cell | 0    |
+| `data-chart` outside the five types    | `✗` naming the value                           | 0    |
+| token role not declared                | `✗` naming the role                            | 0    |
+| slide body sets its own `--color-text` | `✗` naming the slides                          | 0    |
+
+A refused chart, effect, or face is left out and the rest of the deck is written.

package/docs/agents/tasks-validate.md

@@ -61,7 +61,7 @@ The blocker check re-takes a measurement the board records once and never repeat
 }
 ```
 
-A closed outcome is not the fact the dependency half needs. The ship chain marks outcomes as its first step and opens the pull request several steps later, so a check reading the checkbox reports the row settled while the branch is still in review. A live task therefore settles the row only once it closed every outcome and carries a `Pull request:` line the trunk holds. One that names no pull request, and one whose number no trunk ref could answer for, land in the untested array below rather than being settled or left silent.
+A closed outcome is not the fact the dependency half needs. The ship chain marks outcomes as its first step and opens the pull request several steps later, so a check reading the checkbox reports the row settled while the branch is still in review. A live task therefore settles the row only once it closed every outcome and carries a `Pull request:` line the trunk holds. One that carries a `Pending branch:` line, one that names no pull request, and one whose number no trunk ref could answer for, land in the untested array below rather than being settled or left silent.
 
 The trunk is read as the clone already holds it, `origin/main` first and local `main` behind it, and no run fetches. A validate runs several times a sweep and a fetch per run is a cost this command does not carry, so a clone behind its remote under-reports rather than claiming work landed.
 

package/docs/agents/tasks.md

@@ -64,7 +64,7 @@ Run from a branch other than `main` or `master`, the verb also drops that branch
 
 Exit codes: `0` recorded, `1` refused. The `reason` field carries `no-board`, `no-match`, or `ambiguous`. `git-pr` skips silently on those three, because each is a case where a guessed write would archive the wrong task once the branch merges.
 
-A malformed argument refuses as `bad-input` instead, which sits outside that set on purpose. `git-pr` derives the number by slicing whatever `gh pr create` printed, so a non-numeric value is reachable, and folding it into the swallowed set would lose the number with nothing reporting it.
+A malformed argument refuses as `bad-input` instead, which sits outside that set on purpose. `git-pr` derives the number by slicing the address the create call returned, so a non-numeric value is reachable, and folding it into the swallowed set would lose the number with nothing reporting it.
 
 ## Outcome
 
@@ -84,7 +84,7 @@ canon tasks outcome --plan worktree-scratch-routing --close 2 --json
 
 An outcome already closed comes back under `alreadyClosed` rather than refusing, so a rerun against the same positions changes nothing. A position past the end of the list refuses as `out-of-range`, since a caller counting wrong should hear about it rather than mark a neighbor.
 
-A close that ticks at least one box from a branch other than `main` or `master` names that branch on a `Pending branch:` line, read from `git branch --show-current` in the working directory. The line holds the task against `canon tasks archive --pull-request` until `canon tasks pull-request` records that branch's own number. A detached HEAD, a trunk checkout, or a failed git read writes no line and refuses nothing. The `pending` field lists the branches on the line after the write.
+A close that ticks at least one box from a branch other than `main` or `master` names that branch on a `Pending branch:` line, read from `git branch --show-current` in the working directory. The line holds the task against `canon tasks archive --pull-request` until `canon tasks pull-request` records that branch's own number. A detached HEAD, a trunk checkout, or a failed git read writes no line and refuses nothing. The line is also skipped when `gh pr list --head <branch> --state all` lists a number already on the task's `Pull request:` line, since that branch has recorded itself and a marker would outlive it, as in a review-address pass. A failed, offline, or unreadable `gh` lookup counts as no listing and writes the line. The `pending` field lists the branches on the line after the write.
 
 Positions skip fenced blocks. A checkbox inside a sample a task displays is not an outcome the task claims, and counting one would shift every position after it. `canon tasks archive` reads the list through the same walker, so the two verbs cannot disagree about which checkboxes are outcomes.
 

package/docs/target/migrations.md

@@ -60,9 +60,11 @@ The first line reports the plan and the second applies it, relocating each rule
 
 ## Rename the skill citations, once
 
-Twenty-five plugin skills dropped their `claude-` prefix for two-word names, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. A project that installed governance or tooling before that release holds files naming the old ones, and the plugin answers to none of them. A later release renamed `docs-fold` to `context-fold`, since the skill folds a session into the context entries and the task board rather than into `docs/`, and the same sweep carries a project across that rename too. <!-- canon-keep-retired -->
+Twenty-five plugin skills dropped their `claude-` prefix for two-word names, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. A project that installed governance or tooling before that release holds files naming the old ones, and the plugin answers to none of them. A later release renamed `docs-fold` to `context-fold`, since the skill folds a session into the context entries and the task board rather than into `docs/`, and the same sweep carries a project across that rename too. The pointer that answered under the old name no longer ships, so a citation the sweep has not reached names nothing. <!-- canon-keep-retired -->
 
-Two of those files run rather than sit there. `.husky/post-merge` runs the `canon hooks post-merge` verb, so a stale copy of the hook calls a binary that may lack it, and `.claude/hooks/pr-create-log.sh` hands a session a message naming a skill, so a stale copy tells someone to invoke something that no longer exists. A rule under `.claude/rules/canon/core/` names skills too, though a rule is read rather than run.
+The same sweep carries the merge of the five per-kind document drafters into `draft-doc`, so a citation of any one of them lands on `canon:draft-doc`.
+
+Two of those files run rather than sit there. `.husky/post-merge` runs the `canon hooks post-merge` verb, so a stale copy of the hook calls a binary that may lack it, and `.claude/hooks/pr-create-log.sh` hands a session a message naming a skill, so a stale copy tells someone to invoke something that no longer exists. A copy older than `git-pr`'s move to REST also matches only `gh pr create`, so it stays silent on every pull request `git-pr` opens. A rule under `.claude/rules/canon/core/` names skills too, though a rule is read rather than run.
 
 Resync what the toolkit owns, then sweep what the project wrote:
 

package/docs/target/sync.md

@@ -28,7 +28,7 @@ Each domain holds its own toolkit commit, so syncing governance today does not m
 
 A project that has never synced under a toolkit new enough to write a stamp falls back to the toolkit's own git history. Installed content matching any version that history published proves the file untouched, so it reports `stale` naming the commit it came from, and content matching no published version stays `drifted`. That fallback needs the toolkit as a git checkout. Installed from the registry it ships source without history, and the report says attribution was unavailable rather than reading every file as a local edit.
 
-Further causes sit outside the per-domain scan, each naming something that walk cannot see. A seed the project edited is reported under `seeds` and reconciled with `canon:seed-sync`, since no sync command touches a seed. A file a newer seed folder replaced is reported under `superseded`, such as `.claude/TASKS.md` against the `.canon/tasks/` that now ships, and nothing moves it because the content is the project's own. A domain sitting at the root layout with nothing under `.claude/` is reported under `unmigrated`, and no command moves it either. The project moves the content itself.
+Further causes sit outside the per-domain scan, each naming something that walk cannot see. A seed the project edited is reported under `seeds` and reconciled with `canon:seed-sync`, since no sync command touches a seed. A file a newer seed folder replaced is reported under `superseded`, such as `.claude/TASKS.md` against the `.canon/tasks/` that now ships, and nothing moves it because the content is the project's own. A domain sitting at the root layout with nothing under `.claude/` is reported under `unmigrated`, and no command moves it either. The project moves the content itself. A surface still at its `.claude/` spelling with nothing under `canon/`, such as `.claude/REQUIREMENTS.md`, is reported under `unmovedSurfaces`, since rules glob the `canon/` spelling alone, and `canon migrate surface-roots` moves it. <!-- canon-keep-surface-root -->
 
 `unmigrated` currently names no domain, since standards and snippets are the two the toolkit ever installed at the project root, standards closed its install channel, and snippets retired outright. A target still holding a root `standards/` folder from an older toolkit is carrying its own authoring surface now, not an unfinished install, and nothing proposes moving it. A leftover `.claude/snippets/` reports under `reverse` below instead.
 

package/docs/workflow/ai-workflow.md

@@ -97,7 +97,7 @@ Review findings split by origin before severity is read. One the branch inherite
 
 Review is skipped when the diff is prose that only informs: every changed file matches `*.md` or `*.txt`, and none sits under a behavior path. Behavior paths cover skills and rules in both the authoring and the installed spelling, so the list matches whether a repository authors those surfaces or consumed them from the toolkit. Standards, `internal/`, and `tooling/` carry the authoring spelling alone, since none of the three reaches a session through a `.claude/` copy, and root `CLAUDE.md` is named as a file because a path prefix reaches nothing sitting in no folder.
 
-Markdown under one states what an agent does, so a branch touching it reaches review while `docs/` and `wiki/` still skip and stay gated by `docs-sync`, `standards-audit`, and pre-push hooks.
+Markdown under one states what an agent does, so a branch touching it reaches review while `docs/` and `wiki/` still skip and stay gated by `docs-sync`, `canon markdown audit`, and pre-push hooks.
 
 An empty changed-file list stops the chain rather than counting as prose-only. The filename test passes vacuously on an empty set, which routed a branch past review instead of through it.
 

package/docs/workflow/skill-map.md

@@ -61,7 +61,6 @@ This page is the corpus the coverage claim is measured against: every name `cano
 | Skill                    | When to use                                                                             |
 | ------------------------ | --------------------------------------------------------------------------------------- |
 | `canon:review-branch`    | On the local branch diff, before anything is pushed                                     |
-| `canon:standards-audit`  | When changed markdown has to answer to the authoring standards                          |
 | `canon:document-health`  | When the documents themselves have to answer for length, placement, and staleness       |
 | `canon:markdown-propose` | When a markdown claim needs rewriting and the change should wait for an answer per file |
 | `canon:ux-audit`         | To read UI source for missing states, edge cases, and inconsistencies                   |
@@ -70,18 +69,17 @@ This page is the corpus the coverage claim is measured against: every name `cano
 
 ## Ship it
 
-| Skill                  | When to use                                                                                       |
-| ---------------------- | ------------------------------------------------------------------------------------------------- |
-| `canon:git-ship`       | To run the whole post-feature chain from the verify gate through open PR                          |
-| `canon:memory-capture` | First skill in that chain, to route what the session learned to the surface owning it             |
-| `canon:context-fold`   | When decisions diverged from the plan, or a shipped task needs its outcomes marked                |
-| `canon:docs-fold`      | Never on purpose. A pointer at the old name that names `context-fold` <!-- canon-keep-retired --> |
-| `canon:docs-sync`      | When a change since main left `README.md` or `docs/` stale                                        |
-| `canon:git-stage`      | When the staged set spans several concerns and wants one commit each                              |
-| `canon:git-commit`     | When the staged set is one concern, or was staged hunk by hand                                    |
-| `canon:git-branch`     | When a branch name needs generating or renaming to conventional form                              |
-| `canon:git-pr`         | When a pull request needs a title and body written from the diff                                  |
-| `canon:memory-review`  | When the pen has grown, to propose where each entry belongs                                       |
+| Skill                  | When to use                                                                           |
+| ---------------------- | ------------------------------------------------------------------------------------- |
+| `canon:git-ship`       | To run the whole post-feature chain from the verify gate through open PR              |
+| `canon:memory-capture` | First skill in that chain, to route what the session learned to the surface owning it |
+| `canon:context-fold`   | When decisions diverged from the plan, or a shipped task needs its outcomes marked    |
+| `canon:docs-sync`      | When a change since main left `README.md` or `docs/` stale                            |
+| `canon:git-stage`      | When the staged set spans several concerns and wants one commit each                  |
+| `canon:git-commit`     | When the staged set is one concern, or was staged hunk by hand                        |
+| `canon:git-branch`     | When a branch name needs generating or renaming to conventional form                  |
+| `canon:git-pr`         | When a pull request needs a title and body written from the diff                      |
+| `canon:memory-review`  | When the pen has grown, to propose where each entry belongs                           |
 
 ## After the pull request opens
 
@@ -120,24 +118,20 @@ This page is the corpus the coverage claim is measured against: every name `cano
 
 ## Generate an artifact on demand
 
-| Skill                     | When to use                                                                                                       |
-| ------------------------- | ----------------------------------------------------------------------------------------------------------------- |
-| `canon:create-rule`       | For a project-specific governance rule the toolkit does not ship                                                  |
-| `canon:create-skill`      | For a new `SKILL.md`                                                                                              |
-| `canon:create-standard`   | For a new authoring convention                                                                                    |
-| `canon:draft-docs`        | For a brand-new `docs/*.md` page, drafted against `standards/docs.md`                                             |
-| `canon:draft-ready`       | For finished files a worker should copy, written as a ready folder with its overview, thin plan, and task         |
-| `canon:draft-context`     | For a brand-new `canon/context/<domain>.md` entry, drafted against `standards/context.md`                         |
-| `canon:draft-wireframes`  | For a brand-new `canon/wireframes/<surface>.md` file, drafted against `standards/wireframes.md`                   |
-| `canon:draft-wiki`        | For a brand-new wiki reference page on a subject owned outside the project, drafted against `standards/wiki.md`   |
-| `canon:draft-figure`      | For a hand-drawn figure inside an existing doc, drafted against `standards/figures.md` in Mermaid or freehand SVG |
-| `canon:draft-readme`      | For a project's `README.md`, drafted against `standards/readme.md`                                                |
-| `canon:bash-cli-script`   | For a small non-interactive shell wrapper, stopping at 100 lines in favor of TypeScript on Bun                    |
-| `canon:ci-workflow`       | For a GitHub Actions workflow file                                                                                |
-| `canon:draft-slides`      | For a deck, drafted as `.claude/SLIDES.md` and rendered to PowerPoint                                             |
-| `canon:draft-screencast`  | For a recording script with beats and defaults already seeded                                                     |
-| `canon:record-screencast` | For recording a screencast draft, then composing the take into a finished mp4 when the draft asks for a wrap      |
-| `canon:draft-identity`    | For a project's logo mark and its social card, drafted through `draft-and-pick`'s pick loop                       |
+| Skill                     | When to use                                                                                                                                    |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `canon:create-rule`       | For a project-specific governance rule the toolkit does not ship                                                                               |
+| `canon:create-skill`      | For a new `SKILL.md`                                                                                                                           |
+| `canon:create-standard`   | For a new authoring convention                                                                                                                 |
+| `canon:draft-doc`         | For a brand-new `docs/` page, context entry, wireframe surface, wiki reference page, or `README.md`, drafted against the standard for its kind |
+| `canon:draft-ready`       | For finished files a worker should copy, written as a ready folder with its overview, thin plan, and task                                      |
+| `canon:draft-figure`      | For a hand-drawn figure inside an existing doc, drafted against `standards/figures.md` in Mermaid or freehand SVG                              |
+| `canon:bash-cli-script`   | For a small non-interactive shell wrapper, stopping at 100 lines in favor of TypeScript on Bun                                                 |
+| `canon:ci-workflow`       | For a GitHub Actions workflow file                                                                                                             |
+| `canon:draft-slides`      | For a deck, drafted as `.claude/SLIDES.md` and rendered to PowerPoint                                                                          |
+| `canon:draft-screencast`  | For a recording script with beats and defaults already seeded                                                                                  |
+| `canon:record-screencast` | For recording a screencast draft, then composing the take into a finished mp4 when the draft asks for a wrap                                   |
+| `canon:draft-identity`    | For a project's logo mark and its social card, drafted through `draft-and-pick`'s pick loop                                                    |
 
 ## Answer a question at any point
 

package/governance/rules/canon/604-scratch.md

@@ -7,4 +7,3 @@ description: Write temporary files to the scratch folder structure
 ## Temporary files
 
 - Write temporary files to `.canon/tmp/<slug>/<file>.md` at the current worktree's root, a nested folder with a kebab-slug tied to the topic rather than a flat `<slug>-<file>.md`. The slug must not take one of the five reserved names `runs`, `hooks`, `handoff`, `pr`, and `render`. A skill that resolves a write at the main root instead states so in its own body.
-- Write to `.claude/.tmp/<slug>/` instead in a project that carries no `.canon/` root, and `canon migrate records` moves it to the first spelling. <!-- canon-keep-record-root -->

package/governance/rules/claude/575-hooks.md

@@ -1,8 +1,7 @@
 ---
-description: State the hook stdin guard and the silencing rule for .claude/hooks scripts and their seeded copies
+description: State the hook stdin guard and the silencing rule for .claude/hooks scripts
 paths:
   - '.claude/hooks/**/*.sh'
-  - 'tooling/claude/seeds/.claude/hooks/**/*.sh'
 ---
 
 # Hook standards

package/governance/rules/claude/576-settings.md

@@ -1,8 +1,7 @@
 ---
-description: State the autoContinueAtUsageLimit inversion and the autoCompactWindow cap for .claude/settings.json and its seeded copy
+description: State the autoContinueAtUsageLimit inversion and the autoCompactWindow cap for .claude/settings.json
 paths:
   - '.claude/settings.json'
-  - 'tooling/claude/seeds/.claude/settings.json'
 ---
 
 # Settings standards

package/governance/rules/lib/330-testing-py.md

@@ -1,7 +1,7 @@
 ---
 description: Enforce pytest fixtures, parametrize, and async patterns for Python tests
 paths:
-  - 'tests/**/*.py'
+  - '**/tests/**/*.py'
   - '**/test_*.py'
   - '**/*_test.py'
 ---

package/governance/rules/lib/336-testing-php.md

@@ -1,7 +1,7 @@
 ---
 description: Enforce PHPUnit test classes, attributes, and strict assertions for PHP tests
 paths:
-  - 'tests/**/*.php'
+  - '**/tests/**/*.php'
   - '**/*Test.php'
 ---
 

package/governance/rules/standards/architecture.md

@@ -3,7 +3,6 @@
 description: Shape and content rules for canon/ARCHITECTURE.md
 paths:
   - 'canon/ARCHITECTURE.md'
-  - '.claude/ARCHITECTURE.md'
 ---
 
 # Architecture standards

package/governance/rules/standards/context.md

@@ -3,7 +3,6 @@
 description: Shape and content rules for canon/context/<domain>.md entries
 paths:
   - 'canon/context/**'
-  - '.claude/context/**'
 ---
 
 # Context entry standards

package/governance/rules/standards/design.md

@@ -3,7 +3,6 @@
 description: Shape and content rules for canon/DESIGN.md
 paths:
   - 'canon/DESIGN.md'
-  - '.claude/DESIGN.md'
 ---
 
 # Design standards

package/governance/rules/standards/diagrams.md

@@ -3,7 +3,6 @@
 description: Shape and content rules for .canon/diagrams/<kind>.md files
 paths:
   - '.canon/diagrams/**'
-  - '.claude/DIAGRAMS.md'
 ---
 
 # Diagram standards
@@ -13,5 +12,3 @@ paths:
 - Follow the diagrams standard for shape and content rules for .canon/diagrams/<kind>.md files. It is the single source. Read it with `canon standards diagrams`.
 - Layout, budgets, accessibility, labels, and render verification inside the fence are a separate topic. The mermaid standard routes them.
 - A diagram entry carries structure and flow, not implementation. Read the standard before adding or revising a kind.
-- Write a new diagram to `.canon/diagrams/<kind>.md`, never to `.claude/DIAGRAMS.md`
-- Convert a `.claude/DIAGRAMS.md` left by an older install into per-kind entries before editing it

package/governance/rules/standards/requirements.md

@@ -3,7 +3,6 @@
 description: Shape and content rules for canon/REQUIREMENTS.md
 paths:
   - 'canon/REQUIREMENTS.md'
-  - '.claude/REQUIREMENTS.md'
 ---
 
 # Requirements standards

package/governance/rules/standards/wireframes.md

@@ -3,7 +3,6 @@
 description: Shape and content rules for canon/wireframes/<surface>.md files
 paths:
   - 'canon/wireframes/**'
-  - '.claude/wireframes/**'
 ---
 
 # Wireframe standards

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/canon",
   "type": "module",
-  "version": "5.20.0",
+  "version": "5.22.0",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
   "license": "MIT",
   "bin": {

package/scripts/manage-sandbox.sh

@@ -190,10 +190,10 @@ provision_sandbox() {
   (cd "$SANDBOX" && configure_sandbox_git_credentials)
 }
 
-# Runs the real installer rather than copying the source tree. The two copies
-# these replaced each reimplemented an installer's selection rules, so a change
-# to what install produces left the sandbox provisioning the old shape and no
-# scenario could observe the difference.
+# Runs the real installer rather than copying the source tree. The copies these
+# replaced, for gov rules and for seeds, each reimplemented an installer's
+# selection rules, so a change to what install produces left the sandbox
+# provisioning the old shape and no scenario could observe the difference.
 run_sandbox_install() {
   local label="$1"
   shift
@@ -223,10 +223,9 @@ inject_gov_rules() {
 }
 
 inject_seeds() {
-  local seeds_source="$PROJECT_ROOT/tooling/claude/seeds"
-  if [ -d "$seeds_source" ]; then
-    cp -r "$seeds_source/." "$SANDBOX/"
-  fi
+  [ ! -d "$PROJECT_ROOT/tooling/claude/seeds" ] && return
+
+  run_sandbox_install "seeds" claude init "$SANDBOX"
 }
 
 commit_environment_setup() {

package/src/claude/cases/authoring.ts

@@ -31,7 +31,7 @@ export const AUTHORING_CASES: readonly SkillCase[] = [
   {
     prompt:
       'Write a brand-new docs page for the capture command, nothing under docs/ covers it yet.',
-    expect: 'draft-docs',
+    expect: 'draft-doc',
   },
   {
     prompt:
@@ -40,22 +40,22 @@ export const AUTHORING_CASES: readonly SkillCase[] = [
   },
   {
     prompt: 'This project has no README.md at all, write one from scratch.',
-    expect: 'draft-readme',
+    expect: 'draft-doc',
   },
   {
     prompt:
       'Write a context entry for the payments domain, there is no canon/context page for it yet.',
-    expect: 'draft-context',
+    expect: 'draft-doc',
   },
   {
     prompt:
       'Draft a wireframe for the settings panel, nothing under canon/wireframes covers that surface yet.',
-    expect: 'draft-wireframes',
+    expect: 'draft-doc',
   },
   {
     prompt:
       'Write a wiki reference page for Claude Code output styles, no page covers that subject yet.',
-    expect: 'draft-wiki',
+    expect: 'draft-doc',
   },
   {
     prompt: 'Say what that dense answer actually means in plain terms.',

package/src/claude/cases/workflow.ts

@@ -38,12 +38,6 @@ export const WORKFLOW_CASES: readonly SkillCase[] = [
       'Fold what we decided this session into the context entries and mark off what shipped on the task board.',
     expect: 'context-fold',
   },
-  {
-    prompt:
-      'I typed the old fold skill name and it says it was renamed, where did it go?',
-    // The pointer answers under its old name on purpose. canon-keep-retired
-    expect: 'docs-fold',
-  },
   {
     prompt:
       'Sketch out a plan for adding this new capability before we touch any code.',
@@ -143,16 +137,10 @@ export const WORKFLOW_CASES: readonly SkillCase[] = [
     prompt: 'Turn this topic into a slide deck I can render.',
     expect: 'draft-slides',
   },
-  {
-    prompt:
-      'Check whether the markdown I changed violates any authoring standards.',
-    expect: 'standards-audit',
-  },
-  // Rot across documents nobody changed is what separates this from
-  // `standards-audit`, which is diff-scoped and reports a stated rule broken on
-  // a given line. It is also not `target-check`, which asks whether a document
-  // exists and holds its sections rather than whether it still describes the
-  // tree.
+  // Rot across documents nobody changed is what this reads, rather than a
+  // stated rule broken on a given line. It is also not `target-check`, which
+  // asks whether a document exists and holds its sections rather than whether
+  // it still describes the tree.
   {
     prompt:
       'Which of our docs have gone stale, grown too long, or ended up in the wrong file?',
@@ -230,10 +218,6 @@ export const WORKFLOW_CASES: readonly SkillCase[] = [
       "Go through what's still unanswered in the intake folder and decide.",
     expect: 'plan-intake-answer',
   },
-  {
-    prompt: 'Check this markdown against the house style rules.',
-    expect: 'standards-audit',
-  },
   {
     prompt: 'Find the rough, unfinished-feeling spots in this interface.',
     expect: 'ux-audit',

package/src/commands/slides.ts

@@ -119,9 +119,11 @@ export function register(program: Command): void {
 
 /**
  * The converter loads on demand, so no other command resolves pptxgenjs,
- * jszip, or the token module at startup. A fallback or a refused link reports
- * one line each and keeps the exit at 0, as an unrecognized layout does on the
- * markdown path, since the deck is written either way.
+ * jszip, or the token module at startup. A fallback, a refused link, chart, or
+ * effect, or a token the master fell back on reports one line each and keeps
+ * the exit at 0, as an unrecognized layout does on the markdown path, since the
+ * deck is written either way. A malformed `deck.json` refuses before any slide is laid
+ * out and exits 1.
  */
 async function renderHtmlFolder(
   sourceDir: string,
@@ -156,6 +158,24 @@ async function renderHtmlFolder(
       `${GREY}│${NC} ${RED}✗${NC} slide ${slide} ${selector} link "${href}" left out: ${reason}\n`,
     )
   }
+  for (const { slide, selector, message } of result.refusedCharts) {
+    process.stderr.write(
+      `${GREY}│${NC} ${RED}✗${NC} slide ${slide} ${selector} chart left out: ${message}\n`,
+    )
+  }
+  for (const { slide, message } of result.refusedMotion) {
+    process.stderr.write(
+      `${GREY}│${NC} ${RED}✗${NC} slide ${slide} motion left out: ${message}\n`,
+    )
+  }
+  for (const { path, message } of result.refusedFonts) {
+    process.stderr.write(
+      `${GREY}│${NC} ${RED}✗${NC} font ${path} not embedded: ${message}\n`,
+    )
+  }
+  for (const notice of result.notices) {
+    process.stderr.write(`${GREY}│${NC} ${RED}✗${NC} ${notice}\n`)
+  }
   if (result.mirrorPath) {
     process.stderr.write(
       `${GREY}│${NC} ${GREEN}✓${NC} mirrored to ${result.mirrorPath}\n`,

package/src/commands/sync.ts

@@ -168,6 +168,16 @@ function renderCheck(report: CheckReport): void {
     logInfo('Move the content yourself. No sync command touches these.')
   }
 
+  if (report.unmovedSurfaces.length > 0) {
+    logStep('Surfaces at the old .claude/ root')
+    for (const entry of report.unmovedSurfaces) {
+      logWarn(`${entry.rel} (moves to ${entry.movesTo})`)
+    }
+    logInfo(
+      'Rules glob the canon/ spelling only. Run `canon migrate surface-roots` to move these.',
+    )
+  }
+
   renderSeeds(report)
 
   if (report.superseded.length > 0) {