@erclx/canon 5.22.0 → 5.24.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.22.0",
+  "version": "5.24.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/canon-operator/REQUIREMENT.md

@@ -27,6 +27,7 @@ The last failure is a section no route reaches. `## Route` maps an intent or a d
 - Run the CLI non-interactively and report the command run, what changed, and the full path of anything written
 - Read the overwrite contract from the body before any install or sync, and name each surface it lists as overwritten before running one
 - Read the reverse walk beside the forward sections, so a folder the toolkit stopped shipping reaches the user
+- Read `unmovedSurfaces` from the report itself, since the drift status ignores it by design, and name `canon migrate surface-roots` without running either form
 - Name an unmigrated domain's root and install path for the user to move themselves, since no skill covers the move
 - Route a measurement intent to the audit offers from the route table itself, rather than leaving the section reachable only by reading past the table
 - Rank a lifecycle row against the audit offers where the route table itself states it, so a session acting on the lifecycle row reads the ranking without opening the section being ranked

package/claude/skills/canon-operator/SKILL.md

@@ -22,10 +22,11 @@ Load a domain doc with `canon docs <topic>` only when the intent touches that do
 
 Run `canon sync --check . --json` before routing. It reports what a target is behind on across every surface, so the intent comes from the project state rather than from the user having to know it already. Skip only when the user named a single operation to run.
 
-Read seven fields off the report and carry each to `## Route`:
+Read eight fields off the report and carry each to `## Route`:
 
 - `unmigrated`: a domain sitting at the root layout with nothing under `.claude/`. The most urgent finding, because that domain reports no drift of its own while being entirely behind
 - `superseded`: a file a newer seed folder replaced. No command moves it, since the content is the project's own, so this routes to `canon:target-check` for the full per-domain reading rather than ending at the report
+- `unmovedSurfaces`: a surface held only at its `.claude/` spelling, each entry carrying `rel` and `movesTo`. Every other field reads clean for such a target, and the report's drift status ignores it by design, so read the array itself rather than an exit status
 - `seeds`: entries are `matching`, `stale`, `drifted`, or `missing`. Anything but `matching` needs the seed handoff
 - `domains[].entries`: per-file `stale`, `customized`, `stranded`, and `orphaned` as before, plus `retired` for a rule the toolkit no longer ships, which the next sync deletes
 - `reverse`: what the target holds that no live catalog claims. `unclaimed` lists folders at roots the toolkit stopped shipping, each with an `attribution` of `dropped`, `unattributed`, or `project`. Act on the first two and leave `project` alone, which history proved the project owns
@@ -34,6 +35,8 @@ Read seven fields off the report and carry each to `## Route`:
 
 State what the report found in one line per finding before acting on any of it.
 
+An `unmovedSurfaces` key the report does not carry at all is likewise a CLI predating the field rather than a target with nothing to move. Say the section was unread and name the installed CLI version as the cause.
+
 A `reverse` key the report does not carry at all is a CLI predating the field rather than a target with nothing unclaimed. Say the walk did not run and name the CLI version as the cause. Reading the absent key as an empty answer reports a clean target to a project nobody has looked at, and answering it from a filesystem walk of your own is worse, since that reaches a verdict the attribution the field carries is the only thing entitled to make.
 
 ## Route
@@ -44,6 +47,7 @@ The two can name different rows, and a reply answers both rather than picking on
 
 - A domain in `unmigrated`: name it, the root path, and the install path. No command moves it, so the user runs the relocation themselves
 - Anything in `superseded`: name which files and what replaced them, then hand off to `canon:target-check`, which reports and never moves or deletes the file
+- Anything in `unmovedSurfaces`: name `canon migrate surface-roots`, which only reports its plan until `--write` is passed, with each entry's `rel` and `movesTo`, and run neither form, since the move rewrites tracked paths
 - A folder in `unclaimed`: name it and the attribution it carries. No command moves it and the content may be the project's own, so the decision is the user's
 
 - First-time scaffold of a fresh project: hand off to `target-setup`

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

@@ -19,6 +19,7 @@ The same procedure ran as five skills, one per kind, each restating the read, th
 - Check the catalog by exact name and by title and description, since a subject can be covered under a name the request does not guess
 - Confirm the resolved path, the kind's detections, and the full content with the user before writing, since placement and detection are judgment calls with no diff to preview them against
 - Regenerate the catalog of the folder the document landed in, where the kind keeps one, so the next run's collision check sees it
+- Draft a README from the template for every detected project type and combine them, never the closest one, since a project that is a CLI and a plugin owes its reader both
 - Carry each kind's own musts in its reference: the root check for context and wireframes, tier detection and the two modes for wireframes, both placement tests and a fetched source for the wiki, and project detection and rendered-value badges for the readme
 
 ## Must not

package/claude/skills/draft-doc/references/readme/agent-facing.md

@@ -0,0 +1,59 @@
+![<Project name> logo](<committed logo path>)
+
+# <Project name>
+
+[![<build status>](<badge image URL>)](<run history URL>)
+[![<license>](<badge image URL>)](<license URL>)
+
+<One-line claim taken from the repository description.>
+
+<Two or three sentences expanding the claim: the conventions or tooling an agent working here picks up, and what a session gains from them.>
+
+## Installation
+
+### Requirements
+
+- <Agent tool and minimum version>
+- <Runtime the listing command needs>
+
+### Set up
+
+```bash
+<clone command>
+<setup command, when a session needs one>
+```
+
+## Usage
+
+### What an agent loads first
+
+`<file an agent reads at session start>` carries <what that file holds>. It points at <the files it imports or links>.
+
+### List what the project exposes
+
+```bash
+<command that lists skills, rules, or commands>
+```
+
+### Where things live
+
+| Path       | Holds        |
+| ---------- | ------------ |
+| `<folder>` | <What it is> |
+
+## Documentation
+
+<Link to the full conventions reference.>
+
+## Support
+
+- <Where to open an issue>
+- <Where to ask a question>
+
+## Contributing
+
+See the [contributing guidelines](<CONTRIBUTING.md path>).
+
+## License
+
+[<License name>](<LICENSE path>)

package/claude/skills/draft-doc/references/readme/application.md

@@ -0,0 +1,66 @@
+![<Project name> logo](<committed logo path>)
+
+# <Project name>
+
+[![<build status>](<badge image URL>)](<run history URL>)
+[![<license>](<badge image URL>)](<license URL>)
+
+<One-line claim taken from the manifest or repository description.>
+
+[<Live site name>](<live URL>)
+
+![<What the screenshot depicts>](<committed image path>)
+
+<Two or three sentences expanding the claim: who the product is for, then what they do with it.>
+
+## Features
+
+- <Benefit the user gets>
+- <Benefit the user gets>
+
+## Installation
+
+### Requirements
+
+- <Runtime and version>
+- <Service the app depends on>
+
+### Set up
+
+```bash
+<clone command>
+<dependency install command>
+```
+
+## Usage
+
+### Run locally
+
+```bash
+<dev server command>
+```
+
+<Address the app serves on.>
+
+### Configuration
+
+| Variable | Purpose            | Default     |
+| -------- | ------------------ | ----------- |
+| `<NAME>` | <What it controls> | `<default>` |
+
+### Deploy
+
+<Where the app deploys and the command or workflow that does it.>
+
+## Support
+
+- <Where to open an issue>
+- <Where to ask a question>
+
+## Contributing
+
+See the [contributing guidelines](<CONTRIBUTING.md path>).
+
+## License
+
+[<License name>](<LICENSE path>)

package/claude/skills/draft-doc/references/readme/cli.md

@@ -0,0 +1,64 @@
+![<Project name> logo](<committed logo path>)
+
+# <Project name>
+
+[![<package version>](<badge image URL>)](<registry page URL>)
+[![<build status>](<badge image URL>)](<run history URL>)
+[![<license>](<badge image URL>)](<license URL>)
+
+<One-line claim taken from the manifest description.>
+
+<Two or three sentences expanding the claim: the task a reader repeats by hand, then what the command does about it.>
+
+## Features
+
+- <Benefit the reader gets>
+- <Benefit the reader gets>
+
+## Installation
+
+```bash
+<global install or one-shot run command>
+```
+
+<Runtime or platform requirement, when one exists.>
+
+## Usage
+
+### Run a command
+
+```bash
+<command> <argument>
+```
+
+### Flags
+
+```bash
+<command> --<flag> <value>
+<command> --<flag>
+```
+
+| Flag       | Effect         |
+| ---------- | -------------- |
+| `--<flag>` | <What it does> |
+
+### Exit codes
+
+<What each non-zero exit means, when a script depends on it.>
+
+## Documentation
+
+<Link to the full command reference.>
+
+## Support
+
+- <Where to open an issue>
+- <Where to ask a question>
+
+## Contributing
+
+See the [contributing guidelines](<CONTRIBUTING.md path>).
+
+## License
+
+[<License name>](<LICENSE path>)

package/claude/skills/draft-doc/references/readme/library.md

@@ -0,0 +1,57 @@
+![<Project name> logo](<committed logo path>)
+
+# <Project name>
+
+[![<package version>](<badge image URL>)](<registry page URL>)
+[![<build status>](<badge image URL>)](<run history URL>)
+[![<license>](<badge image URL>)](<license URL>)
+
+<One-line claim taken from the manifest description.>
+
+[<Live site name>](<live URL>)
+
+![<What the screenshot depicts>](<committed image path>)
+
+<Two or three sentences expanding the claim: the problem a reader recognizes, then what the library does about it.>
+
+## Features
+
+- <Benefit the reader gets>
+- <Benefit the reader gets>
+
+## Installation
+
+```bash
+<install command for the package manager the project uses>
+```
+
+## Usage
+
+### Quickstart
+
+```<language>
+<Import and one call that shows the core behavior>
+```
+
+### <Second common task>
+
+```<language>
+<Snippet for the task>
+```
+
+## Documentation
+
+<Link to the full API reference.>
+
+## Support
+
+- <Where to open an issue>
+- <Where to ask a question>
+
+## Contributing
+
+See the [contributing guidelines](<CONTRIBUTING.md path>).
+
+## License
+
+[<License name>](<LICENSE path>)

package/claude/skills/draft-doc/references/readme/plugin.md

@@ -0,0 +1,66 @@
+![<Project name> logo](<committed logo path>)
+
+# <Project name>
+
+[![<build status>](<badge image URL>)](<run history URL>)
+[![<license>](<badge image URL>)](<license URL>)
+
+<One-line claim taken from the plugin manifest description.>
+
+<Two or three sentences expanding the claim: the work a session repeats, then what the plugin adds to it.>
+
+## Features
+
+- <Skill, command, or hook and what it gives the user>
+- <Skill, command, or hook and what it gives the user>
+
+## Installation
+
+### <First channel name>
+
+```bash
+<install command for this channel>
+```
+
+### <Second channel name>
+
+```bash
+<install command for this channel>
+```
+
+### Update
+
+```bash
+<update command>
+```
+
+## Usage
+
+### Invoke a skill
+
+```text
+/<plugin name>:<skill name> <argument>
+```
+
+### What the plugin adds
+
+| Name     | Kind                      | Purpose        |
+| -------- | ------------------------- | -------------- |
+| `<name>` | <skill, command, or hook> | <What it does> |
+
+### Configuration
+
+<Setting the plugin reads and where the user sets it, when one exists.>
+
+## Support
+
+- <Where to open an issue>
+- <Where to ask a question>
+
+## Contributing
+
+See the [contributing guidelines](<CONTRIBUTING.md path>).
+
+## License
+
+[<License name>](<LICENSE path>)

package/claude/skills/draft-doc/references/readme.md

@@ -24,16 +24,44 @@ The target path is the placement. A README keeps no catalog, so there is no coll
 
 ## Detect
 
-- Read the project's manifest (`package.json`, `pyproject.toml`, `Cargo.toml`, or equivalent) for a `bin` field or CLI entry point, an installable package name, and its declared dependencies.
-- Check for a `claude/skills/` or `.claude/skills/` folder, a `plugin.json`, or a marketplace manifest, each naming an agent-facing or marketplace-distributed surface.
-- Note every type that applies rather than stopping at the first match, since a project is often several at once and the draft covers each one.
+Read the project's manifest (`package.json`, `pyproject.toml`, `Cargo.toml`, or equivalent) and the tree, then test each type on its own signal. Note every type that matches rather than stopping at the first, since a project is often several at once.
+
+- Library: an installable package name, counted only when no application, CLI, or plugin signal matches, since a named package is also what a site, a CLI, or a plugin carries. An agent-facing match leaves it in place, so a library with a `CLAUDE.md` still gets its quickstart.
+- CLI: a `bin` field, a `[project.scripts]` table in `pyproject.toml`, a `[[bin]]` table in `Cargo.toml`, or a CLI entry point.
+- Application: a site framework dependency, a site config file, or an app entry point.
+- Agent-facing: a `.claude/skills/` folder, or a file an agent loads such as `CLAUDE.md`.
+- Plugin: a `plugin.json` or a marketplace manifest.
+
+A match on no type falls back to the standard's generic template. Say so in the preview, and never force the nearest type.
+
 - Check for a page. A dependency on a site framework or a site config file in the manifest or the tree marks a project as having one. Read a live URL separately, from a `homepage` field or a deploy config, since a project can have a page and no known URL.
 - A monorepo can carry a page in one package and a CLI in another, so both signals may fire. Report each rather than picking one.
 - Look for the mark and the screenshot among images the project already commits: scan the existing README for image references, then the asset and public folders.
 
+## Pick
+
+Read the template for each detected type from `readme/`, beside this file:
+
+- `readme/library.md`
+- `readme/cli.md`
+- `readme/application.md`
+- `readme/agent-facing.md`
+- `readme/plugin.md`
+
+Each is a whole page of slots and structure, so fill it from the manifest and the tree rather than from memory. The standard still owns voice and content, and a template carries no rule of its own.
+
+A project matching one type drafts from that template. A project matching several combines them:
+
+- Keep one H1, one header block, and one description.
+- Order the sections as the standard orders them.
+- Add each extra type's usage or install subsection under the shared `## Installation` or `## Usage` H2, never as a second H2 of the same name.
+- Drop a template section the page already carries rather than repeating it.
+
+Between agent-facing and plugin alone, a repository with no plugin manifest takes only the agent-facing template, and a plugin that is not agent-facing in its own repository takes only the plugin template. A CLI or an application that also matches agent-facing keeps its own template beside it.
+
 ## Draft
 
-- Draft the H1, a 2-3 sentence description in plain text, then the required sections, then whichever optional sections and per-type content Detect found. A README takes no frontmatter.
+- Start from the picked or combined template. Draft the H1, a 2-3 sentence description in plain text, then the required sections, then whichever optional sections and per-type content Detect found. A README takes no frontmatter.
 - Open the page with the standard's header block, filling each slot from what Detect found: mark, title, badges, a one-line claim from the manifest description, the live link, then the product screenshot.
 - Fill the screenshot slot only with an image the project already commits, referenced with alt text naming what it depicts. This kind cannot capture one. Omit the slot when no such image exists and say so in the preview. Never write a placeholder path or invent a mark.
 - Omit the link and the screenshot for a project with no page, and the mark for a project with none, without a note in the drafted page. A project with a page and no known URL gets the screenshot slot, and the Confirm step asks for the link.
@@ -48,6 +76,7 @@ Add these lines, then confirm them with the path:
 
 - `**Target:** <root | nested>`
 - `**Detected:** <project types>`
+- `**Templates:** <each template read, or the generic fallback>`
 - `**Header:** <each slot as filled (source) or skipped (reason)>`
 - `**Badges:** <candidates and what backs each one, or none>`
 

package/claude/skills/target-check/SKILL.md

@@ -26,7 +26,7 @@ CANON_NON_INTERACTIVE=1 canon sync --check . --json
 CANON_NON_INTERACTIVE=1 canon context audit --json
 ```
 
-The first answers five domains from one read, being `skew`, `domains`, `seeds`, `tooling`, and the layout fields `unmigrated`, `superseded`, and `reverse`. The second deepens a domain that first read only counts.
+The first answers five domains from one read, being `skew`, `domains`, `seeds`, `tooling`, and the layout fields `unmigrated`, `superseded`, `unmovedSurfaces`, and `reverse`. The second deepens a domain that first read only counts.
 
 Then run `CANON_NON_INTERACTIVE=1 canon records validate <kind> --json` once per record folder the target carries, taking `<kind>` from what is present under the record root rather than from a list held here.
 
@@ -76,14 +76,14 @@ Lead with the table, then one detail block per domain that is not current:
 ```markdown
 Target check: `<path>`, against canon `<version>`.
 
-| Domain           | State                     | Evidence                          |
-| ---------------- | ------------------------- | --------------------------------- |
-| Toolkit version  | current / behind / unread | `skew.installed` against `latest` |
-| `canon/` folder  | current / behind / unread | what the layout fields named      |
-| Governance rules | current / behind / unread | the per-state counts              |
-| Tooling          | current / behind / unread | what a sync would change          |
-| Seeds            | current / behind / unread | the per-state counts              |
-| Claude harness   | unchecked                 | no verb reads it                  |
+| Domain           | State                     | Evidence                                       |
+| ---------------- | ------------------------- | ---------------------------------------------- |
+| Toolkit version  | current / behind / unread | `skew.installed` against `latest`              |
+| `canon/` folder  | current / behind / unread | the layout fields, including `unmovedSurfaces` |
+| Governance rules | current / behind / unread | the per-state counts                           |
+| Tooling          | current / behind / unread | what a sync would change                       |
+| Seeds            | current / behind / unread | the per-state counts                           |
+| Claude harness   | unchecked                 | no verb reads it                               |
 
 No overall verdict. The harness row is unchecked rather than passing.
 ```

package/claude/skills/target-check/references/domains.md

@@ -21,19 +21,25 @@ This domain is first because it conditions the other five. A target a release be
 
 ## 2. The `canon/` folder
 
-Read three fields off the same report, then two verbs:
+Read four fields off the same report, then two verbs:
 
 - `unmigrated`: a domain still at the root layout with nothing under `.claude/`. The most urgent finding, because such a domain reports no drift of its own while being entirely behind.
 - `superseded`: a file a newer seed folder replaced. No command moves it, since the content is the project's own.
+- `unmovedSurfaces`: a surface held only at its `.claude/` spelling, each entry carrying `rel` and `movesTo`. Every other field reads clean for such a target, and the report's drift status ignores it by design, so read the array itself rather than an exit status.
 - `reverse`: `unclaimed` names folders at roots the toolkit stopped shipping, each with an `attribution` of `dropped`, `unattributed`, or `project`.
 - `canon context audit --json`: required sections, entry length, citations, and index drift across the context folder.
 - `canon records validate <kind> --json`, once per record folder the target carries.
 
-- Current: `unmigrated` and `superseded` both empty, `reverse.unclaimed` carrying nothing outside `project` attribution, and both verbs finding nothing.
-- Behind: any of those carrying an entry. Name the entry and its attribution.
-- Unread: `historyUnavailable` set on `reverse`, a `reverse` key the report does not carry at all, or either verb refusing. A missing `reverse` key is a binary predating the field rather than a target with nothing unclaimed.
+- Current: `unmigrated`, `superseded`, and `unmovedSurfaces` all empty, `reverse.unclaimed` carrying nothing outside `project` attribution, and both verbs finding nothing.
+- Behind: any of those carrying an entry. Name the entry and its attribution, and for `unmovedSurfaces` each `rel` with its `movesTo`.
+- Unread: `historyUnavailable` set on `reverse`, a `reverse` or `unmovedSurfaces` key the report does not carry at all, or either verb refusing. A missing key is a binary predating the field rather than a target with nothing to report, so name the installed version beside it.
 
-Routes by finding. `unmigrated` routes to a relocation the user runs, since no command moves it. `superseded` routes to a split the user makes, since no command moves the content and no skill proposes it. An `unclaimed` folder carrying `project` attribution routes nowhere, since history proved the project owns it.
+Routes by finding.
+
+- `unmovedSurfaces` routes to `canon migrate surface-roots`, which only reports its plan until `--write` is passed. Name the verb with each entry's `rel` and `movesTo`, and run neither form.
+- `unmigrated` routes to a relocation the user runs, since no command moves it.
+- `superseded` routes to a split the user makes, since no command moves the content and no skill proposes it.
+- An `unclaimed` folder carrying `project` attribution routes nowhere, since history proved the project owns it.
 
 ## 3. Governance rules
 

package/docs/agents/architecture-record.md

@@ -19,7 +19,7 @@ What the derivation costs where it does apply is that the ceiling rises when a d
 
 The decision word check counts each decision's prose against the cap the record states in a clause of the form `at most 150 words a decision`. The count runs below the `###` heading with fenced lines dropped, so neither the heading nor a template block inside a decision counts, and the report and the gate read the same number. The JSON record carries the clause as `architecture.wordCap`, and the audit catalog counts the decisions past it as `recordOverWords`, absent where the record states no clause.
 
-The risk bullet check counts every list item under `## Risks / open questions`, nested ones included, against a clause of the form `at most 6 risk bullets`, since a nested bullet is weight the reader pays for like any other. Both clauses can share the entry cap's sentence, and each gates only a record stating it, for the reason the cap does. A record stating a risk cap and carrying no Risks section is reported as absent rather than passed as zero bullets. The JSON record carries the clause as `architecture.riskCap` and the count as `architecture.risksBullets`, and the audit catalog counts a section past its cap as `recordOverRisks`, absent where the record states no clause.
+The risk bullet check counts every list item under `## Risks / open questions`, nested ones included, against a clause of the form `at most 6 risk bullets`, since a nested bullet is weight the reader pays for like any other. Both clauses can share the entry cap's sentence, and each gates only a record stating it, for the reason the cap does. The record `canon claude init` seeds into a new project states all three caps in that one sentence, so a new project gates on them from its first decision, and a project that installed earlier keeps whatever its own record states. A record stating a risk cap and carrying no Risks section is reported as absent rather than passed as zero bullets. The JSON record carries the clause as `architecture.riskCap` and the count as `architecture.risksBullets`, and the audit catalog counts a section past its cap as `recordOverRisks`, absent where the record states no clause.
 
 The coverage report classifies each decision as carrying a countable claim, a structural invariant, or neither, then reports each testable entry against whether it names a check that exists. A countable claim carries a figure a run could recompute, and an invariant quantifies over a named tree closely enough that a walk could falsify it. A check is a `scripts/**.sh` path the entry spells that is on disk, or a `canon` invocation matching a registered audit, so coverage reads the entry rather than the tree and a claim some check happens to cover without the entry saying so reads as unchecked.
 
@@ -33,4 +33,4 @@ The `## Risks / open questions` section is weighed the same way, reported apart
 
 ## The requirements record
 
-The audit reads `canon/REQUIREMENTS.md` under its own step and counts every word below the frontmatter against the cap the record states in a clause of the form `This record holds at most 600 words.` The cap is the record's own, so a record stating none is measured and never gated, and a project with no record is reported as out of scope. The JSON record carries the reading as `requirements`, null where the project carries no record and absent under `--citations-only`, and the audit catalog counts a record past its cap as `requirementsOverWords`.
+The audit reads `canon/REQUIREMENTS.md` under its own step and counts every word below the frontmatter against the cap the record states in a clause of the form `This record holds at most 600 words.` The cap is the record's own, so a record stating none is measured and never gated, and a project with no record is reported as out of scope. The seeded record states the 600-word cap. The JSON record carries the reading as `requirements`, null where the project carries no record and absent under `--citations-only`, and the audit catalog counts a record past its cap as `requirementsOverWords`.

package/docs/agents/canvas.md

@@ -11,6 +11,10 @@ description: The canvas server, its content format, and the verbs that list, arr
 
 `canvas serve` serves the canvas on `127.0.0.1`, walks ports like `canon serve`, refuses a `Host` other than loopback on its own port, and runs until interrupted. Each frame gets the project's token stylesheet injected, being this toolkit's tokens in its own checkout, else `.claude/design/base.css` plus anything under `.claude/design/project/`, else none with a notice. An open canvas reloads a frame whose file changes.
 
+The toolkit's own tokens arrive with the font faces they name embedded, so a frame renders in them on a machine that never installed them. An installed base owns its fonts and gets no faces added.
+
+Before it binds a port, `canvas serve` checks that `preact` and `@preact/signals` resolve from the package the CLI runs from, never from the served project. When either is missing it refuses with reason `missing-client-deps` and names `bun install` in the detail, rather than serving a shell that loads as a blank page.
+
 The write routes the shell posts to also refuse a request carrying an `Origin` other than the server's own, and a body that is not JSON.
 
 ## List and add
@@ -37,7 +41,7 @@ A pick is refused as `address-mismatch` when the browser builds elements the fil
 
 The operator edits the same set from the inspector, which posts to the same writer with the hash the frame was served with. An edit made against a version of the file Claude has since rewritten is refused as `stale-address` and the shell reloads the frame, so nothing lands on a shifted element. A color picked from the project's tokens is written as `var(--<name>)`. Both writers take the frame file's lock, and an edit that keeps the selected element where it was keeps the selection fresh.
 
-Inline style beats a class, so an operator's edit masks a class change Claude makes later. Read a frame's inline styles before restyling it, and remove one the change should replace. A property outside the set, or a value carrying `;`, `{`, `}`, `<`, `>`, or a line break, is refused as `invalid-edit`.
+Inline style beats a class, so an operator's edit masks a class change Claude makes later. Read a frame's inline styles before restyling it, and remove one the change should replace. The inspector marks a color or background set inline with the word `raw` when its value names no `var()` and is not `currentColor` or a CSS-wide keyword, since that value stays fixed when the theme changes. A property outside the set, or a value carrying `;`, `{`, `}`, `<`, `>`, or a line break, is refused as `invalid-edit`.
 
 The Theme tab in the shell lists what the token stylesheet defines, grouped as color, spacing, radius, font family, font size, and other. The page record at `/api/pages` carries the same list as `tokens.groups`.
 

package/docs/agents/index.md

@@ -62,7 +62,7 @@ CLI catalog and invocation rules for agents, split by command domain. Start with
 - [Targets](targets.md): The projects this toolkit installed into, the record the install writes against the sweep that backs it, what bounds each answer, and the cross-target pull request read
 - [Tasks archive](tasks-archive.md): Archiving a shipped task by stem or pull request, declining one decided against, the refusal reasons each carries, and how the plan and ready folder move with the task
 - [Tasks plans](tasks-plans.md): The five verbs that read or write a task's plan, being where it sits and who cites it, whether it waits on the operator, the branch it derives, what a branch reached against what it declared, and writing its Plan line
-- [Tasks validate](tasks-validate.md): Validating the board against the tree, the seven checks, the untested, claims, and unplaced arrays, the exit codes, and the refusal reasons
+- [Tasks validate](tasks-validate.md): Validating the board against the tree, the seven checks, the untested, claims, wide, and unplaced arrays, the exit codes, and the refusal reasons
 - [Tasks](tasks.md): Claiming the next phase label, recording a pull request number and closing an outcome, listing each task's readiness, and where archiving, the plan verbs, and board validation are described
 - [Teach authoring](teach-authoring.md): Resolving what the next lesson needs before it is written, rendering a lesson body's blocks to HTML, and rewriting the root listing, a contents page, and each lesson's chrome and quiz stepper from its marker regions
 - [Teach](teach.md): Listing learning workspaces with what their records schedule next, opening one with its required files, recording sources and glossary terms, viewing one with its chrome refreshed, where the lesson authoring verbs are described, the refusal reasons, and why every write here runs through a verb

package/docs/agents/tasks-validate.md

@@ -1,6 +1,6 @@
 ---
 title: Tasks validate
-description: Validating the board against the tree, the seven checks, the untested, claims, and unplaced arrays, the exit codes, and the refusal reasons
+description: Validating the board against the tree, the seven checks, the untested, claims, wide, and unplaced arrays, the exit codes, and the refusal reasons
 ---
 
 # Tasks validate
@@ -103,7 +103,9 @@ That claim collides with every row a later session writes under the folder, and
 
 The scan reaches `## Run now` and stops, where the collision check stops. A cell in another group describes work nobody has planned, written as a sentence and rewritten once a plan exists, so a claim read off one reports on prose rather than on a file set. A parked folder claim surfaces when its row is promoted, which is when the cell becomes something a dispatcher can act on.
 
-A task file neither surface names lands in a fourth array, on the same reasoning:
+A code span in any cell that the preview cannot break lands in a fourth array, `wide`, with the same `group`, `subject`, and `message` fields. The scan measures a span's longest whitespace-free run and flags one past 60 characters, or a brace-glob at any width. A 57-character span fit the pane and a 78-character one did not, so the limit is a heuristic and the array moves no exit code. A link target is skipped, since only its label renders, and the scan reaches every group, since the overflow it exists for sat under `## Up next`.
+
+A task file neither surface names lands in a fifth array, on the same reasoning:
 
 ```json
 {

package/docs/agents/tasks.md

@@ -118,6 +118,6 @@ canon tasks list --json | jq -r '.tasks[] | select(.readiness == "backlog") | .s
 
 ## Validate
 
-`canon tasks validate` reports what each row of `priority.md` and each line of `backlog.md` claims against what the tree holds. Its seven checks, the three arrays that move no exit code, and the refusals are in `tasks-validate.md`.
+`canon tasks validate` reports what each row of `priority.md` and each line of `backlog.md` claims against what the tree holds. Its seven checks, the four arrays that move no exit code, and the refusals are in `tasks-validate.md`.
 
 For the board format, see `standards/board.md`. For the `Pull request:` line and the archive rules, see `standards/tasks.md`.

package/docs/target/projects.md

@@ -71,7 +71,7 @@ Keep the `## Scripts` table in `canon/context/development.md` current as scripts
 
 Scaffold installs tooling and seeds. It does not fill the planning docs or the design system. Complete those before the first feature session:
 
-1. Fill `canon/REQUIREMENTS.md` and `canon/ARCHITECTURE.md`. The seed provides the files, the scope and decisions are yours to write.
+1. Fill `canon/REQUIREMENTS.md` and `canon/ARCHITECTURE.md`. The seed provides the files, the scope and decisions are yours to write. Each seed states its own caps, 12 decisions of at most 150 words and 6 risk bullets for the architecture record and 600 words for the requirements, and `canon context audit` gates on them. Edit a number in the record to loosen it.
 2. For a UI project, invoke `canon:design-extract` to draft `canon/DESIGN.md`. With no UI code yet it takes the greenfield path and proposes tokens from the requirements and a `## Personality` section. Skip for non-UI projects.
 3. Optionally invoke `canon:draft-diagram` to draft entries under `.canon/diagrams/` from the architecture and the requirements. One file per diagram kind, so a later refresh of one kind leaves the others untouched. It renders each diagram it writes to verify the layout, which downloads the Mermaid CLI on first use and takes about 15 seconds.
 4. Start the feature loop. See [AI workflow](../workflow/ai-workflow.md) for the per-feature sequence.

package/docs/workflow/visual-design-workflow.md

@@ -14,7 +14,7 @@ The tier framework sits alongside [Claude Design](../../wiki/claude/design.md),
 
 ## Tier 0: prose only
 
-The default. `canon/DESIGN.md` holds visual intent as prose plus token tables for color, typography, spacing, borders, motion, and iconography. `.claude/WIREFRAMES.md` holds each surface's regions and states.
+The default. `canon/DESIGN.md` holds visual intent as token tables for color, typography, spacing, and borders, with one Personality paragraph and at most three one-line rules a section, motion and iconography included. `.claude/WIREFRAMES.md` holds each surface's regions and states.
 
 Claude Code reads both and writes the implementation. Works for CLI tools, internal dashboards, admin panels, and backend-focused projects.
 

package/package.json

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