@erclx/canon 5.20.0 → 5.21.0

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "canon",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
-  "version": "5.20.0",
+  "version": "5.21.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/auto-ship/references/verb-absent.md

@@ -29,7 +29,7 @@ Behavior paths carry two spellings, the one a surface authors at and the one it
 
 Markdown under one of them states what an agent does, so a change there is a behavior change wearing a prose extension. Everything outside them is informational, which keeps `docs/`, `README.md`, and `CHANGELOG.md` skipping without naming them. One behavior file sends the whole branch to review, since documentation shipped beside a behavior change does not cancel it.
 
-Informational prose is already gated by `docs-sync`, `standards-audit`, and pre-push hooks. Running a code-style review on it burns tokens with no signal.
+Informational prose is already gated by `docs-sync`, `canon markdown audit`, and pre-push hooks. Running a code-style review on it burns tokens with no signal.
 
 The list covers this toolkit's authoring layout and the layout it installs, which is not every layout. A project keeping executable prose where neither spelling reaches adds the path, and until it does every branch touching it skips review silently.
 

package/claude/skills/docs-sync/REQUIREMENT.md

@@ -38,4 +38,4 @@ The quiet one is the baseline. A diff resolved against a bare local ref equals H
 - The context entries, requirements, architecture, wireframes, and task board: `context-fold`, which runs immediately before this skill in the ship chain and resolves the same baseline. The split is by audience, so a file's location decides which skill owns it rather than its subject.
 - `CLAUDE.md` and the installed seed docs: `seed-sync`, which reconciles them per section against the toolkit source
 - Changelog entries, which release tooling generates from commit messages
-- Whether the prose conforms to its standards. `standards-audit` reports violations and fixes none, and this skill writes prose it does not audit.
+- Whether the prose conforms to its standards. `canon markdown audit` reports violations and fixes none, and this skill writes prose it does not audit.

package/claude/skills/document-health/REQUIREMENT.md

@@ -40,7 +40,7 @@ The third is silence on an unread axis. Both measured verbs resolve their folder
 ## Out of scope
 
 - Whether a document exists or holds its required sections, which is the structural question `target-check` answers across six domains
-- Conformance of changed markdown to the authoring standards declaring jurisdiction over its paths, which is `standards-audit`. That skill is diff-scoped and standard-declared, taking a changed file and reporting which stated rule it breaks with a line number. This one is corpus-scoped and reads rot in documents nobody changed, which is the case a diff-scoped audit never reaches. The two sit beside each other rather than one absorbing the other.
+- Banned tokens and structural checkpoints in markdown, which `canon markdown audit` measures from package data. This skill reads rot a ban set cannot state.
 - Rewriting a stale claim once this run has named it, which is `markdown-propose`
 - Running the toolkit's own checks as one gating set over its own corpus, which is `canon audits run`. That set gates a push and this reports to a reader.
 - Repairing anything an axis names. Each routes to the command or skill that owns it.

package/claude/skills/draft-ready/REQUIREMENT.md

@@ -13,6 +13,7 @@ Without this skill, a session holding finished files that hands them to a worker
 - Lists a destination in the overview that the plan's `**Files to touch:**` omits, or the reverse. The omitted path is invisible to `plan-reach`, so a second track writes the same file and neither side finds out.
 - Picks the next ordinal by reading only the live folder, and reuses a number an archived folder already spent, which the pull request that shipped it cites by name.
 - Picks a phase label by scanning the live board alone, which is the scan that let two sessions hand out one label within minutes of each other.
+- Reads the label bare, which reserves nothing and returns one a live claim already holds until that claim's task file lands.
 - Leaves the plan's `**Constraints:**` without a line naming the folder as the verbatim source, so the worker reads the files as inspiration and writes its own version.
 - Leaves a note, an alternate, or a draft passage in the folder beside the real files, so the worker guesses which one is the source.
 - Writes into the main worktree root from a linked worktree with `Edit` or `Write`, which the isolation guard refuses, and takes the refusal's redirect into a second gitignored copy no later session reads.
@@ -22,7 +23,7 @@ Without this skill, a session holding finished files that hands them to a worker
 
 - Refuse before writing when the operator has named no finished file, since a folder assembled from a description is a plan with extra steps.
 - Read the ordinal from the live folder and its archive together, so a spent number is never reused.
-- Take the phase label from `canon tasks next-label` rather than from a scan of its own.
+- Take the phase label from `canon tasks next-label --claim` rather than from a scan of its own or a bare read, and stop on a binary that predates the flag rather than falling back.
 - Derive the overview's `destinations` and the plan's `**Files to touch:**` from one list, and compare the two before reporting, so neither can name a path the other lacks.
 - Write the plan's `**Constraints:**` line naming the folder as the verbatim source.
 - Copy each finished file whole to its destination path inside the folder, and carry nothing else into it.

package/claude/skills/draft-ready/SKILL.md

@@ -31,13 +31,15 @@ Read these in parallel before writing:
 
 Read `<main-root>/.canon/ready/` and `<main-root>/.canon/ready/archive/` together and take the highest `<nn>` across both, plus one. A folder set with no entry takes `01`. Keep this skill-local. No verb allocates a ready ordinal, and two writers running at once can claim one number, so re-read the folder immediately before Step 3 writes.
 
-Take the label from the verb rather than from a scan:
+Claim the label through the verb rather than reading it bare or scanning for it:
 
 ```bash
-canon tasks next-label --json
+canon tasks next-label --claim --json
 ```
 
-Branch on the record's `label` rather than on the exit code. Report the verb as unavailable and stop when the installed binary carries no `next-label` subcommand, since a label picked by hand is the collision the verb exists to prevent.
+The claim reserves the label under `.canon/ordinal-locks/`, so a second session allocating at the same moment gets the next one. A bare read reserves nothing and can return a label a live claim already holds.
+
+Branch on the record's `reason` rather than on the exit code, taking `label` from a record that carries one. `label-contended` means re-run the claim. Report the verb as unavailable and stop when the installed binary carries no `next-label` subcommand, or when an unknown `--claim` prints no record, since that binary predates the flag. Never fall back to a bare read or a label picked by hand, which reopens the collision the claim exists to prevent.
 
 ## Step 3: write the overview
 
@@ -67,7 +69,7 @@ Run the match check in `${CLAUDE_SKILL_DIR}/references/assembly.md` before going
 
 ## Step 6: write the task
 
-Write `<main-root>/.canon/tasks/<label>-<slug>.md` by heredoc, from the label Step 2 read. Its frontmatter, H1, and `## Outcomes` follow `${CLAUDE_SKILL_DIR}/../../standards/tasks.md`. Write a `Ready:` line beside the `Plan:` line pointing at the folder, then point the task at the plan through the verb:
+Write `<main-root>/.canon/tasks/<label>-<slug>.md` by heredoc, from the label Step 2 claimed, without calling the verb again, since a second call would claim a different label. Its frontmatter, H1, and `## Outcomes` follow `${CLAUDE_SKILL_DIR}/../../standards/tasks.md`. Write a `Ready:` line beside the `Plan:` line pointing at the folder, then point the task at the plan through the verb:
 
 ```bash
 canon tasks plan-link <task-stem> .canon/plans/feature-<slug>.md --json

package/claude/skills/markdown-propose/REQUIREMENT.md

@@ -7,9 +7,9 @@ description: Why a markdown rewrite is proposed per file and answered before any
 
 ## Gap
 
-Rewriting a passage in a governing document today means editing it live or arguing in chat, and three surfaces sit near this moment without covering it. `standards-audit` maps changed markdown to the standards claiming it and reports violations, ending on its own description: `Do NOT fix violations. Reporting only.` `canon markdown audit` measures bans and structural checkpoints from package data.
+Rewriting a passage in a governing document today means editing it live or arguing in chat, and two surfaces sit near this moment without covering it. `canon markdown audit` measures bans and structural checkpoints from package data.
 
-`review-branch` reports findings on a diff someone already wrote. None of the three drafts a replacement, carries an answer slot, or waits.
+`review-branch` reports findings on a diff someone already wrote. Neither drafts a replacement, carries an answer slot, or waits.
 
 A review delivered in chat gets applied from memory across files nobody reopened, and nothing records which changes the operator approved. A change nobody agreed to either lands unreviewed, because the session acting on a chat review cannot tell an approved line from an inferred one, or never gets written down at all, because a finding with no draft behind it hands the rewrite back to whoever reads it next.
 
@@ -41,7 +41,7 @@ A second failure compounds the first. A claim copied across several files is cor
 
 ## Out of scope
 
-- Reporting a violation with no drafted replacement, which `standards-audit` and `canon markdown audit` already own
+- Reporting a violation with no drafted replacement, which `canon markdown audit` already owns
 - Reviewing a diff someone already wrote, which `review-branch` owns
 - Filing a raw brain dump as findings, which `plan-intake` owns
 - Reviewing `.canon/memory/` and proposing promote-or-retire actions per entry, which `memory-review` owns on a different subject with a different answer contract

package/claude/skills/markdown-propose/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: markdown-propose
-description: Reviews a named markdown surface against a named concern, drafts a per-file proposal under `.canon/proposals/<nn>-<slug>/` carrying a diff and a reason for each change, and stops without editing a source file. Takes the concern and the surface as inputs, such as a claim stated stronger than the record, a fact gone stale, two files disagreeing, or a passage duplicated without derivation. A later invocation applies what the operator answered. Use when asked to "propose a change to CLAUDE.md", "draft a rewrite of this standard", "propose fixes to this doc", "draft alternatives for this passage", or "apply the answered proposals". Do NOT use to report without drafting a replacement (`standards-audit` or `canon markdown audit`), to review a diff already made (`review-branch`), or to file a raw brain dump as findings (`plan-intake`).
+description: Reviews a named markdown surface against a named concern, drafts a per-file proposal under `.canon/proposals/<nn>-<slug>/` carrying a diff and a reason for each change, and stops without editing a source file. Takes the concern and the surface as inputs, such as a claim stated stronger than the record, a fact gone stale, two files disagreeing, or a passage duplicated without derivation. A later invocation applies what the operator answered. Use when asked to "propose a change to CLAUDE.md", "draft a rewrite of this standard", "propose fixes to this doc", "draft alternatives for this passage", or "apply the answered proposals". Do NOT use to report without drafting a replacement (`canon markdown audit`), to review a diff already made (`review-branch`), or to file a raw brain dump as findings (`plan-intake`).
 ---
 
 # Markdown propose

package/docs/agents/commands.md

@@ -130,6 +130,7 @@ Subcommands no other page describes:
 - `design regen` rewrites this repository's `canon/DESIGN.md` from `src/design/tokens.ts` and `src/design/base.css` from `src/design/neutral.ts`. `design css` emits the tokens and components as CSS on stdout, with `--no-components` for properties alone, and `design render` declares each vendored face the typography table names under `--embed-fonts`.
 - `slides render` renders a `.claude/SLIDES.md` source into a PowerPoint deck and reports any unrecognized layout name on stderr, and `slides list --json` emits the layout catalog.
 - `slides render --source <folder>` lays out each `.html` file in filename order in Chromium at 1280 by 720 and rebuilds it as editable shapes. Each element drawn as a picture prints one `✗` line on stderr naming the slide, the selector, and the properties that forced it. A link left out, being a `#slide-N` past the deck's end or any target that is neither that nor an absolute URL, prints one too, and the exit stays 0.
+- A deck folder's `deck.json`, its per-slide `<body>` attributes, speaker notes, and charts are described in `slides.md`.
 - `canvas`, with its verbs, content format, and write routes, is described in `canvas.md`.
 - `labels scan` fails a pull request or a posted review whose title, body, or review comment carries a phase label, a label a code span quotes, a gitignored record path, a session link, a title word no dictionary holds, or a title breaking `standards/pr.md`'s format, casing, or length rule (`--event`, `--body-file`, `--json`).
 - `repo metadata propose` compares a description, homepage, and topic set computed from the README and `package.json` against what the remote carries, writing nothing, and `repo metadata apply` writes an explicitly supplied set through `gh repo edit` (`--description`, `--homepage`, `--topics`).

package/docs/agents/index.md

@@ -55,6 +55,7 @@ CLI catalog and invocation rules for agents, split by command domain. Start with
 - [Sessions](sessions.md): Resolving live peer sessions to the worktree and branch each holds, reading which row is the caller, the liveness confidence field, what each session surface can see, and where moving a session to another machine is described
 - [Skill audit](skills-audit.md): Measuring both skill corpora against the skill standards, the checks it reads, the requirement gate that is the only failing one, and the drift verb that names bodies rewritten since a ref
 - [Citation reach](skills-reach.md): Reporting the skill bodies that cite a path no target project receives, which corpus the verb reads, the ownership key that decides what counts, the one-word qualifier that marks a citation as decided, and why the verb reports instead of gating
+- [Slides](slides.md): What a folder of HTML slides declares for the whole deck in deck.json, what each slide declares on its own body, the master built from the project's tokens, speaker notes, charts, and what each refusal reports
 - [Standard success criteria](standards-audit.md): Reading the corpus against the success-criterion gate, the two headings it accepts, why the check scopes to arrival rather than the whole corpus, and the exit codes it sets
 - [State-scoped risk](state-scoped-risk.md): Reading committed state rather than an arriving change, the shipped-tree corpus the secret scan reads, what it keys on and how a deliberate value is exempted, the advisory check and its network failure mode, and why one gates while the other reports
 - [Superseded values](superseded.md): Reading where the tree still asserts a value a changed convention no longer produces, why the sweep keys on the value rather than the file, the family stem behind a templated citation, the exemption marker, the blind spots it cannot reach, and why it reports rather than gates

package/docs/agents/markdown-audit.md

@@ -87,7 +87,7 @@ A hit the closed set could not separate from correct prose was the case with no
 
 ### Where the rules are enforced
 
-Five surfaces apply the ban set and four of them go through this verb. `.claude/hooks/standards-audit.sh` runs it against a single file after each markdown edit, the seed copy a project installs does the same, the `Markdown bans` stage in `canon gate run` runs it across the whole corpus before this repository's own push, and the same-named stage in the one verify runner every stack shares, `scripts/verify.ts`, runs it across a scaffolded project's tracked markdown before its own push. Each hook parsed its own copy of the word bans in awk before that, which left a British spelling passing at edit time and failing the push with nothing in between explaining the difference.
+Four surfaces apply the ban set and all four go through this verb. `.claude/hooks/standards-audit.sh` runs it against a single file after each markdown edit, the seed copy a project installs does the same, the `Markdown bans` stage in `canon gate run` runs it across the whole corpus before this repository's own push, and the same-named stage in the one verify runner every stack shares, `scripts/verify.ts`, runs it across a scaffolded project's tracked markdown before its own push. Each hook parsed its own copy of the word bans in awk before that, which left a British spelling passing at edit time and failing the push with nothing in between explaining the difference.
 
 The seed copy moved onto the verb when the sets became data, since its awk had nothing left to parse. It resolves one runner where the toolkit copy resolves two, looking for no checkout source, and a machine carrying no `canon` gets a report naming the binary to install rather than a silent pass. The Seed independence stage of `bun run check` scopes its walk to markdown and leaves the seed hooks outside it, which its own comment records as deliberate.
 
@@ -95,8 +95,6 @@ The target push stage reads the same exit codes `canon gate run`'s own stage rea
 
 The target push stage excludes `CHANGELOG.md`, unlike every other surface here. A changelog a generator builds from commit subjects carries prose nobody wrote against the ban set, where this repository's own passes only because `release-please` builds it from subjects sessions already wrote to the rule. The stage passes an explicit file list rather than the bare invocation the other surfaces use, so a corpus with no file left once the changelog is set aside reads as a pass rather than falling back to the whole tree.
 
-The fifth surface reads the standards directly and is not a consolidation left half done. `claude/skills/standards-audit/SKILL.md` greps the banned tokens agent-side, which is a session reading prose rather than a process it can shell out to, and it ships to every target. It is the likeliest place for the next drift, since nothing compares it against the verb.
-
 The hook prefers a checkout's own `src/cli.ts` over a globally installed binary, so it and the push stage read one build. A published binary lags a branch by whatever has not been released, which would put a ban kind added on the branch into the push and not into the edit. It reads its findings out of the `--json` record rather than off the exit code, so an older binary still reports where the fallback applies. It reads `bans.emptySets` out of the same record, so a set the verb shipped empty reaches the author as a check narrowed to what it could measure rather than as a clean pass.
 
 That field replaced `bans.missingStandards`, which answered a standard resolving under none of three roots. The set ships with the package now, so the state it named cannot occur and the narrowed check has one cause left, a defect in the build. The hook keeps reading a field either way, since a reader cannot tell a narrowed check from a clean one without it.

package/docs/agents/slides.md

@@ -0,0 +1,120 @@
+---
+title: Slides
+description: What a folder of HTML slides declares for the whole deck in deck.json, what each slide declares on its own body, 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  |
+
+```json
+{
+  "title": "Q3 review",
+  "header": { "left": "Acme" },
+  "footer": { "center": "Internal" },
+  "mark": "assets/mark.png"
+}
+```
+
+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.
+
+## 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.
+
+## 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    |
+| 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 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

@@ -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,7 +60,7 @@ 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.
 

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
 

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/package.json

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

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 or chart,
+ * 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,14 @@ 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 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/tasks.ts

@@ -65,6 +65,7 @@ const EXIT_FINDINGS = 2
 
 /** Matches `trunk.ts`'s bound on a git subprocess this verb also shells out to. */
 const GIT_TIMEOUT_MS = 10_000
+const GH_TIMEOUT_MS = 10_000
 
 const TRUNK_BRANCHES: readonly string[] = ['main', 'master']
 
@@ -522,7 +523,9 @@ export function register(program: Command): void {
         'Run from a branch other than main or master, a close that ticks a new',
         'box names that branch on a Pending branch: line, which holds the task',
         'against a merge-time archive until canon tasks pull-request records',
-        "the branch's own number.",
+        "the branch's own number. The marker is skipped once gh lists a pull",
+        "request for the branch whose number is already on the task's Pull",
+        'request: line, and a failed gh lookup writes it.',
         '',
         'Examples:',
         '  canon tasks outcome v28.1-trigger-escalation --close 1 --close 3',
@@ -728,6 +731,45 @@ async function workingBranch(): Promise<string | undefined> {
   return branch
 }
 
+/**
+ * The pull request numbers whose head is `branch`, open or not. A failed run,
+ * an unreadable answer, or no `gh` at all returns an empty list, which writes
+ * the marker, the direction that holds a task open rather than archiving it.
+ */
+async function branchPullNumbers(
+  branch: string | undefined,
+): Promise<readonly number[]> {
+  if (branch === undefined) return []
+
+  const result = await execa(
+    'gh',
+    ['pr', 'list', '--head', branch, '--state', 'all', '--json', 'number'],
+    {
+      cwd: process.cwd(),
+      reject: false,
+      timeout: GH_TIMEOUT_MS,
+      env: gitEnv(),
+      extendEnv: false,
+    },
+  )
+  if (result.exitCode !== 0) return []
+
+  try {
+    const rows: unknown = JSON.parse(result.stdout)
+    if (!Array.isArray(rows)) return []
+
+    return rows
+      .map((row: unknown) =>
+        typeof row === 'object' && row !== null && 'number' in row
+          ? row.number
+          : undefined,
+      )
+      .filter((number): number is number => Number.isInteger(number))
+  } catch {
+    return []
+  }
+}
+
 async function runPlanLink(
   task: string,
   plan: string,
@@ -789,11 +831,13 @@ async function runOutcome(
   }
 
   const root = opts.root ?? (await mainWorktreeRoot())
+  const branch = await workingBranch()
   const outcome = await closeOutcomes(
     root,
     selector,
     raw.map(Number),
-    await workingBranch(),
+    branch,
+    await branchPullNumbers(branch),
   )
 
   return reportOutcome(outcome, emitJson, root)

package/src/migrate/skill-names.ts

@@ -110,11 +110,6 @@ export const SKILL_NAME_MAP: Readonly<Record<string, string>> = {
  * what shipped or what a session ran under whatever name was current then, so
  * rewriting one makes it testify to a release or a run that never happened.
  *
- * The pointer left at `docs-fold` is excluded because it exists to answer under
- * the old name, so a later run would move it onto the skill it points at. The
- * exclusion is only safe once the real body has moved, since excluding the path
- * ahead of the first sweep leaves that body behind.
- *
  * The record archives need no entry here. They are gitignored, so the tracked
  * listing every sweep reads never reaches them.
  */
@@ -127,7 +122,5 @@ export const SKILL_NAME_RULES: RenameRules = defineRenameRules({
     'CHANGELOG.md',
     'src/migrate/skill-names.ts',
     'src/migrate/skill-names.test.ts',
-    'claude/skills/docs-fold/SKILL.md',
-    'claude/skills/docs-fold/REQUIREMENT.md',
   ],
 })