@erclx/canon 5.62.0 → 5.64.0

package/claude/skills/context-fold/references/classify.md

@@ -1,87 +0,0 @@
----
-title: Classify the fold's diff baseline
-description: The classify diff invocation, the record fields to read, applying a finding, the one-line keep reason, the unreachable and missing-subcommand lines, and the report shape
----
-
-# Classify the fold's diff baseline
-
-Mechanics for the classify half of Step 4 of `context-fold`. The body owns the skip condition and the shared baseline, and this file owns the invocation, what the record carries, and what applying a finding does.
-
-## Invocation
-
-Call the verb rather than reimplementing its pattern or prompt in this skill:
-
-```bash
-canon context classify diff --base <base> --json
-```
-
-Never substitute a different verb for it, such as `canon docs <name>` (a documentation lookup, not a classification).
-
-Reuse the base the Diff baseline section already resolved for Steps 2 and 5 rather than resolving a second time. Never pick or configure a backend here. The project setting decides it, and this step reports `modelLayer` as the record returns it.
-
-## Reading the record
-
-Branch on the record's `decision` field, never on the exit code, which a shell function wrapping `canon` can flatten to zero.
-
-- `decision: 'refused'`: a bad range or a file the verb could not read. Report the record's `message` and continue. See "When the verb is absent or refused" below.
-- `decision: 'ok'`: the record carries `modelLayer` (`'off'`, `'ran'`, `'skipped-no-model'`, or `'skipped-unreachable'`) and `findings`.
-
-Each finding carries `file`, a `verdict` of `KEEP`, `REPLACE`, `HISTORY`, or `MOVE`, and `decidedBy` (`'regex'` or `'model'`) naming which layer's reading won. Take the `quote` and `reason` from whichever of the finding's `regex` or `model` fields `decidedBy` names. Skip every `KEEP` finding: nothing decided against that text.
-
-## Scope
-
-Answer every non-`KEEP` finding the verb returns, not only the files Step 3 wrote this run, since a branch carrying a prior session's commits has doc edits the fold is equally responsible for.
-
-The verb's own extraction already scopes to canonical doc types and reports nothing when the range carries none, so there is no narrower check to add here.
-
-## Applying a finding
-
-Locate the finding by its `quote` in the file's current content. The quote is often a narrow fragment rather than the whole clause it sits in, since the regex layer's own match is a short pattern hit, so the edit below targets the sentence or bullet the quote sits in rather than the literal substring alone.
-
-- **Found exactly once.** Apply the verdict under its heading below.
-- **Found more than once, or not found at all.** Report it as not located rather than guessing an occurrence or silently rewriting nothing. A model paraphrasing its quote is the usual cause.
-
-Run the classifier once per fold. Do not re-run it after applying a finding to check the edit, since a second pass over what this step wrote is the loop the verb's own reference already warns against.
-
-### REPLACE
-
-Rewrite the sentence or bullet carrying the quote in place with the fact that now stands, per Step 3's rewrite-in-place rule. State what is current and drop what the quote restated, in the one edit.
-
-### HISTORY
-
-Rewrite the sentence or bullet carrying the quote to drop the narration and keep any current fact the same clause states. The quote narrates how the fact arrived rather than stating the fact, which a canonical doc excludes regardless of what wrote it.
-
-A literal cut of the fragment alone would leave the rest of the clause grammatically stranded.
-
-### MOVE
-
-Do not cut. The verdict means correct content sits on the wrong surface, such as a rule written into a context entry that belongs in a path-scoped rule, and only the model layer returns it.
-
-Report the finding instead, naming the surface the `reason` names as where the content belongs, and leave the file unedited. Cutting would delete content a fold with no model configured would never have flagged at all.
-
-## Keeping a finding
-
-Keep a non-`KEEP` finding without applying it only when the quote is itself the alternative a nearby decision states and lost, or the file already carries the current fact elsewhere. State the reason in one line in the report. A keep costs one line, where an incorrect apply costs a rewrite of prose nobody asked to change.
-
-## When the verb is absent or refused
-
-The verb ships with the CLI and this skill ships with the plugin, so a target holding an older installed binary carries no `context classify` subcommand. Never read a missing subcommand as a clean pass, which would report a run that never checked anything as one that found nothing.
-
-| Case               | Report, then continue                                                                |
-| ------------------ | ------------------------------------------------------------------------------------ |
-| Subcommand missing | `⚠ Classify: canon context classify not available on the installed binary. Skipped.` |
-| Range refused      | `⚠ Classify: <message>`, naming the verb's own message                               |
-
-Neither case stops the fold. This step checks what the fold wrote, and a check that cannot run is not a reason to leave the fold's own output unshipped.
-
-## Report
-
-Print one line naming what ran, `✅ Classify: <n> findings, regex ran, model <modelLayer>`, then one line per non-`KEEP` finding:
-
-- `✏ Rewrote: <file>, "<quote>" (<reason>)`
-- `✂ Cut: <file>, "<quote>" (<reason>)`
-- `➡ Move needed: <file>, "<quote>" (<reason>)`, for a `MOVE` this step reported rather than cut
-- `⏭ Kept: <file>, "<quote>", <reason for keeping>`
-- `⚠ Not located: <file>, "<quote>" not found or found more than once`
-
-When every finding reads `KEEP`, output `✅ Classify: <n> findings, all KEEP` and nothing further.

package/governance/ledger/ui/copy.md

@@ -1,49 +0,0 @@
----
-title: UI copy rule ledger
-description: Sources for governance/rules/ui/copy.md, one row per bullet
----
-
-# UI copy rule ledger
-
-The field is content design, and the authority for researched interface copy is the GOV.UK Design System and its style guide.
-
-## Punctuation
-
-| Bullet                        | Source                                                                                                                                                                  | Read       |
-| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| No em dash or semicolon       | House choice: both read as generated copy in an interface, and a comma, a period, or a split sentence carries the same meaning in a shorter line                        | 2026-10-18 |
-| No trailing label punctuation | [Button](https://design-system.service.gov.uk/components/button/): every example label, such as "Start now", "Sign in", and "Continue", carries no trailing punctuation | 2026-10-18 |
-
-## Button copy
-
-| Bullet            | Source                                                                                                                                     | Read       |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
-| The action's verb | [Button](https://design-system.service.gov.uk/components/button/): "Write button text in sentence case, describing the action it performs" | 2026-10-18 |
-
-## Error messages
-
-| Bullet            | Source                                                                                                                                                                                                                                            | Read       |
-| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| Say how to fix it | [Error message](https://design-system.service.gov.uk/components/error-message/): "Describe what has happened and tell them how to fix it", and "'Enter your first name' is clearer, more direct and natural than 'First name must have an entry'" | 2026-10-18 |
-| Short and plain   | [Error message](https://design-system.service.gov.uk/components/error-message/): "The message must be in plain English, use positive language and get to the point", with no "technical jargon like 'form post error'"                            | 2026-10-18 |
-
-## Placeholder text
-
-| Bullet                         | Source                                                                                                                                                                                                                                           | Read       |
-| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
-| No placeholder, a hint instead | [Text input](https://design-system.service.gov.uk/components/text-input/): "Do not use placeholder text in place of a label, or for hints or examples", since "it vanishes when the user starts typing" and "not all screen readers read it out" | 2026-10-18 |
-
-## Declined
-
-Every bullet the rewrite removed or reshaped, grouped by why.
-
-### Contradicted by the source
-
-- Replaced "show format examples over instructions in placeholder text" with the hint text bullet, since GOV.UK says not to use a placeholder "for hints or examples".
-- Cut "reserve instructions for labels or helper text", which the new placeholder bullet now carries.
-
-### Merged or reworded
-
-- Merged the imperative verb and padded phrasing bullets. The `Save` over `Save changes` example went, since GOV.UK adds words "to better describe the action".
-- Merged "keep messages short and actionable" and "one sentence maximum" into the plain language bullet.
-- Reworded the error example to `Enter an email address`, the instruction form GOV.UK prefers over a description.

package/governance/ledger/ui/design-taste.md

@@ -1,19 +0,0 @@
----
-title: Design taste rule ledger
-description: Sources for governance/rules/ui/design-taste.md, one row per bullet
----
-
-# Design taste rule ledger
-
-The rule is a pointer to the `design-taste` skill, which carries its own sources, so both rows are house choices naming the bug the pointer prevents.
-
-## Authority
-
-| Bullet                     | Source                                                                                                                                                                     | Read       |
-| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| Load the skill             | House choice: a style edit made without the layer order or the coherence locks reaches for a model's defaults, and a second copy of them in the rule drifts from the skill | 2026-10-18 |
-| Report an unresolved skill | House choice: the rule ships with the CLI and the skill with the plugin, so a project holding governance alone would otherwise proceed silently without it                 | 2026-10-18 |
-
-## Declined
-
-The rewrite kept both bullets unchanged.

package/governance/ledger/ui/interface-casing.md

@@ -1,47 +0,0 @@
----
-title: Interface casing rule ledger
-description: Sources for governance/rules/ui/interface-casing.md, one row per bullet
----
-
-# Interface casing rule ledger
-
-The field is content design, and the authority is the GOV.UK style guide, which sets sentence case for every heading and title. The label count and the scope bullets are canon's own.
-
-## Sentence case
-
-| Bullet                   | Source                                                                                                                                                      | Read       |
-| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| Sentence case            | [A to Z of GOV.UK style](https://www.gov.uk/guidance/style-guide/a-to-z-of-gov-uk-style): "Always use sentence case, even in page titles and service names" | 2026-10-18 |
-| Proper nouns keep casing | [A to Z of GOV.UK style](https://www.gov.uk/guidance/style-guide/a-to-z-of-gov-uk-style): "The exceptions to this are proper nouns"                         | 2026-10-18 |
-
-## Uppercase labels
-
-| Bullet      | Source                                                                                                                                                       | Read       |
-| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
-| Label count | House choice: an uppercase eyebrow over every section is the template tell `design-taste` reaches past, and the count makes the cap checkable against a page | 2026-10-18 |
-
-## Where it applies
-
-| Bullet                 | Source                                                                                                           | Read       |
-| ---------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------- |
-| Copy outside the globs | House choice: a locale file holds the same rendered strings, so title case there ships with no rule firing on it | 2026-10-18 |
-
-## Overriding
-
-| Bullet              | Source                                                                                                                                        | Read       |
-| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| Depart where needed | House choice: an acronym or brand mark lowered to sentence case misnames it, the same reason GOV.UK keeps "proper nouns" as its one exception | 2026-10-18 |
-
-## Declined
-
-Every bullet the rewrite removed or reshaped, grouped by why.
-
-### Cut without a check
-
-- Cut "treat the count as a judgment, since a glob cannot check it", which tells a session nothing it can verify against a line.
-
-### Merged or reworded
-
-- Folded "treat title case on every heading as a template tell" into the sentence case bullet as its reason.
-- Shortened the uppercase label bullet under 200 characters, keeping the `ceil(sections / 3)` count and the delete remedy.
-- Reworded the scope bullet from a statement of what the rule covers to the directive a session can act on.

package/governance/ledger/ui/link-behavior.md

@@ -1,29 +0,0 @@
----
-title: Link behavior rule ledger
-description: Sources for governance/rules/ui/link-behavior.md, one row per bullet
----
-
-# Link behavior rule ledger
-
-The field is interaction design, and the authority is the Nielsen Norman Group's research on new windows and tabs.
-
-## Default target
-
-| Bullet                      | Source                                                                                                                                                                                                                                                                                           | Read       |
-| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
-| Same tab, new tab by task   | [Opening links in new browser windows and tabs](https://www.nngroup.com/articles/new-browser-windows-and-tabs/): "There is generally one good reason to open a page in a new window, and that is that the user will need to refer to that content in order to complete a task in another window" | 2026-10-18 |
-| No blanket external new tab | [Opening links in new browser windows and tabs](https://www.nngroup.com/articles/new-browser-windows-and-tabs/): "New windows or tabs prevent the use of the Back button" and "can cause disorientation"                                                                                         | 2026-10-18 |
-
-## mailto: links
-
-| Bullet             | Source                                                                                                                                       | Read       |
-| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| `mailto:` same tab | House choice: the link opens the mail client and leaves the page in place, so `target="_blank"` only adds an empty tab the person must close | 2026-10-18 |
-
-## Declined
-
-Every bullet the rewrite removed or reshaped, grouped by why.
-
-### Rewritten to what the source says
-
-- Reworded the new tab exception from "a destination that would discard in-progress work" to a page the person must consult while finishing a task, the one reason NN/g names.

package/governance/rules/ui/copy.md

@@ -1,28 +0,0 @@
----
-description: Enforce UI copy and text standards for rendered strings in components
-paths:
-  - '**/*.tsx'
-  - '**/*.jsx'
-  - '**/*.astro'
-  - '**/*.html'
----
-
-# UI copy standards
-
-## Punctuation
-
-- Write no em dash (`—`) or semicolon in rendered copy. Use a comma or a period, or restructure the sentence.
-- Add no trailing punctuation to a button label or a short action string.
-
-## Button copy
-
-- Label a button with the verb of the action it performs, such as `Save` or `Delete`, never with filler such as `Click to delete`.
-
-## Error messages
-
-- Tell the person how to fix the error, such as `Enter an email address` over `Email is invalid`.
-- Keep an error message to one short sentence in plain language, with no technical jargon or error codes.
-
-## Placeholder text
-
-- Never use placeholder text as a label, a hint, or an example. Put a format example such as `name@example.com` in hint text under the label.

package/governance/rules/ui/design-taste.md

@@ -1,18 +0,0 @@
----
-description: Route edits that decide how a surface looks to the design-taste skill for the layer ordering, the coherence locks, and the defaults a model reaches for
-paths:
-  - '**/*.tsx'
-  - '**/*.jsx'
-  - '**/*.astro'
-  - '**/*.html'
-  - '**/*.css'
-  - '**/*.scss'
-  - 'canon/DESIGN.md'
----
-
-# Design taste standards
-
-## Authority
-
-- Load the `canon:design-taste` skill for which design decision settles first, what must stay constant across a surface, and the defaults to reach past. It is the single source for all three.
-- Report it rather than proceeding silently when the skill does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.

package/governance/rules/ui/interface-casing.md

@@ -1,29 +0,0 @@
----
-description: Enforce casing for interface text in markup, MDX, and content modules, where copy lives in a content folder
-paths:
-  - '**/*.tsx'
-  - '**/*.jsx'
-  - '**/*.astro'
-  - '**/*.html'
-  - '**/*.mdx'
-  - '**/content/**/*.ts'
----
-
-# Interface casing standards
-
-## Sentence case
-
-- Use sentence case for rendered headings, labels, nav items, tab titles, and dialog titles, since title case on every heading reads as a template default.
-- Keep the original casing of a proper noun or product name, such as `GitHub`, `macOS`, or `TypeScript`.
-
-## Uppercase labels
-
-- Keep small uppercase labels above headings to `ceil(sections / 3)`, the first screen counting as one. Delete the extra labels, since position already names a section.
-
-## Where it applies
-
-- Apply the same casing to interface copy kept outside the globs, such as a locale file, which this rule never fires on.
-
-## Overriding
-
-- Depart from sentence case only where the case needs it, such as an acronym, a brand mark, or a set-in-caps identity the design chose on purpose.

package/governance/rules/ui/link-behavior.md

@@ -1,19 +0,0 @@
----
-description: Enforce the same-tab default for an outbound link and for a mail link
-paths:
-  - '**/*.tsx'
-  - '**/*.jsx'
-  - '**/*.astro'
-  - '**/*.html'
----
-
-# Link behavior standards
-
-## Default target
-
-- Open a link in the same tab. Reserve `target="_blank"` for a page the person must consult while finishing a task in the current one.
-- Never add `target="_blank"` as a default for every external link.
-
-## mailto: links
-
-- Open a `mailto:` link in the same tab. It hands off to the mail client rather than replacing the page, so a new tab leaves an empty tab behind.