@erclx/canon 5.34.0 → 5.36.0

package/docs/target/sync.md

@@ -30,7 +30,7 @@ A project that has never synced under a toolkit new enough to write a stamp fall
 
 Further causes sit outside the per-domain scan, each naming something that walk cannot see. A seed the project edited is reported under `seeds` and merged by hand, since no sync command touches a seed. A file a newer seed folder replaced is reported under `superseded`, such as `.claude/TASKS.md` against the `.canon/tasks/` that now ships, and nothing moves it because the content is the project's own. A domain sitting at the root layout with nothing under `.claude/` is reported under `unmigrated`, and no command moves it either. The project moves the content itself. A surface still at its `.claude/` spelling with nothing under `canon/`, such as `.claude/REQUIREMENTS.md`, is reported under `unmovedSurfaces`, since rules glob the `canon/` spelling alone, and `canon migrate surface-roots` moves it. <!-- canon-keep-surface-root -->
 
-`unmigrated` currently names no domain, since standards and snippets are the two the toolkit ever installed at the project root, standards closed its install channel, and snippets retired outright. A target still holding a root `standards/` folder from an older toolkit is carrying its own authoring surface now, not an unfinished install, and nothing proposes moving it. A leftover `.claude/snippets/` reports under `reverse` below instead.
+`unmigrated` currently names no domain, since snippets is the one the toolkit ever installed at the project root, and it retired outright. A leftover `.claude/snippets/` reports under `reverse` below instead.
 
 ### Rules you never received
 
@@ -40,7 +40,9 @@ Take a clean section as reporting rather than as delivering. Nothing here instal
 
 Since `canon gov install` records the stack you gave it, the list is read by comparing that stack's current rules against what you hold right now, with no date involved at all. That is what lets it name a rule the toolkit shipped before you last synced: nothing here depends on when you installed. A target stamped before this recording shipped falls back to the older read below.
 
-The fallback filters to what your stack can receive, read off the rule folders you already carry plus the folders the base stack takes whole. A rule under `lang/` or `ui/` belongs to some stacks and not others, so an unfiltered list would name rules you can never install. A target with neither a recorded stack nor a governance anchor reports nothing at all, since there is no date to measure against either.
+The fallback filters to what your stack can receive, read off the rule folders you already carry plus the folders holding a base rule. A rule under `lang/` or `ui/` belongs to some stacks and not others, so an unfiltered list would name rules you can never install. A target with neither a recorded stack nor a governance anchor reports nothing at all, since there is no date to measure against either.
+
+A target recorded on a stack the toolkit retired, such as `react` or `astro`, reads as having no recorded stack and takes this fallback, so it keeps receiving updates to the rules it holds and is offered new rules only in the rule folders it already carries. Run `canon gov detect . --stack node --json` to see which rules its manifests propose beyond those.
 
 In the fallback, an empty section is not proof either way when the toolkit running the check is not a full git clone. The read needs history to reach your anchor, and an install from the registry ships none, so the section goes quiet rather than saying it could not measure. Run the check from a clone before reading a clean result as a complete one. The stack-based read above is untouched by this, since it consults no history.
 
@@ -72,13 +74,11 @@ Reconcile the configs with `canon tooling diff <stack> <path>` to read which fil
 
 It never touches user-owned seed files. Governance rules in `.claude/rules/` and tooling configs refresh in place. Stale `.claude/GOV.md` from earlier installs is removed.
 
-Standards take no part in that run. Nothing installed them, so there is no copy to reconcile and no `canon standards sync` to reach for.
-
 ## Targeted
 
 - Claude seed docs such as `CLAUDE.md` and `canon/REQUIREMENTS.md`: merge by hand against the toolkit copy, section by section, keeping the project's customizations. A `stale` seed is safe to take whole.
 - Governance rules already installed: `canon gov sync <path>` diffs and applies, and never adds new rules. A rule your recorded stack lists reports as `missing` instead.
-- Tooling configs and seeds: `canon tooling <stack> <path>` overwrites golden configs and merges dictionary seeds, and drops every other seed once
+- Tooling configs and seeds: `canon tooling <stack> <path>` overwrites golden configs and copies each seed once, leaving an existing file alone
 - Reference docs for a stack: `canon tooling reference <stack>` reads and never writes, so there is nothing to sync
 - Index regeneration after markdown edits: `canon indexes regen`
 

package/docs/workflow/ai-workflow.md

@@ -17,7 +17,7 @@ Project docs split across three roots at the project root. What the project auth
 ```plaintext
 canon/
 ├── REQUIREMENTS.md  ← problem, goals, non-goals
-├── DESIGN.md        ← visual intent and token decisions (UI projects)
+├── DESIGN.md        ← visual intent, pointing at the stylesheet (UI projects)
 └── context/         ← per-domain narrative loaded on demand via index.md
 
 .claude/

package/docs/workflow/operating-model.md

@@ -18,12 +18,12 @@ This page covers the roles and the loop. For merge order and fan-out rules, see
 
 The split is by vantage, not by capability. All four are Claude Code sessions.
 
-| Role         | Session                               | Owns                                                    | Does not                          |
-| ------------ | ------------------------------------- | ------------------------------------------------------- | --------------------------------- |
-| Orchestrator | One warm, long-lived session          | The cross-feature call, deep PR review, merge order     | Edit tracked files, merge PRs     |
-| Reviewer     | One cold session per pull request     | The per-pull-request read, posted through `review-pr`   | Fix findings, lift a draft, merge |
-| Planner      | One session per row, warm or cold     | Measure the row against the tree, write one plan        | Enter a worktree, write the board |
-| Worker       | One cold worktree session per feature | Implement, self-check, open PR, answer the orchestrator | Write the shared board, merge     |
+| Role         | Session                               | Owns                                                 | Does not                           |
+| ------------ | ------------------------------------- | ---------------------------------------------------- | ---------------------------------- |
+| Orchestrator | One warm, long-lived session          | The cross-feature call, review dispatch, merge order | Review in place, edit, merge PRs   |
+| Reviewer     | One cold session per pull request     | One PR's read through `review-pr`, the lift on close | Fix findings, ready by hand, merge |
+| Planner      | One session per row, warm or cold     | Measure the row against the tree, write one plan     | Enter a worktree, write the board  |
+| Worker       | One cold worktree session per feature | Implement, self-check, open PR, answer the reviewer  | Write the shared board, merge      |
 
 Each role is asserted explicitly rather than inferred. The orchestrator loads
 `role-orchestrator` at the start of its session, a worker loads `role-worker`,
@@ -72,9 +72,9 @@ One feature travels this path end to end.
 
 1. The next feature is planned with `plan-feature`, writing a plan to `.canon/plans/`. The orchestrator runs it warm when the row turns on a contract other features consume or a dependency on another row, and dispatches a planner under `role-planner` otherwise. A cold planner measures the row against the tree rather than trusting what the row claims, and it reads what is in flight by composing the live session roster with open pull requests. A bare branch or worktree is not evidence on its own, since this repository leaves both behind after a squash merge.
 2. Orchestrator checks the plan waits on nobody, checks the branch is unclaimed, and checks no conflict holds the plan behind a track in flight, then dispatches a background worker with `claude --bg` against the plan, naming the branch and the model on the launch rather than leaving the worker to derive either. No count caps how many run at once. The branch travels as the argument to the worker's own worktree call, which is the one place the name is read rather than inferred. It falls back to naming the invocation for a human to run through `session-worktree` and `auto-ship` when the plan still waits on an answer only the operator can give, the branch check refuses, or a conflict holds the plan behind a track already in flight. Either way, the worker enters its own worktree, builds, self-checks, opens a PR, and stops at the PR boundary.
-3. A reviewer under `role-reviewer`, or the orchestrator, posts `review-pr` findings, and `review-ui` drives any visual checklist beside it.
-4. Orchestrator tells the session holding that branch to run `review-address` once the pass posted a finding at any severity, resolving the target then with `canon sessions list --branch` and reporting the invocation for the human when no live session holds it. The worker addresses the findings, rebases onto `origin/main` when a sibling landed first on a file it writes, then pushes a follow-up. A pass carrying only minor findings dispatches too, since the grade runs low often enough that a floor at should-fix loses fixes a worker would have made. `review-pr` states that threshold and the heading follows it, so an open heading is itself the signal to send.
-5. Orchestrator closes the review out with `review-pr` again. The second pass reads only the commits the follow-up added, or the worker's response alone when the follow-up added none, and posts under `## Review` when it finds anything and under `## Review closed` when it finds nothing, so a reader learns from the heading whether work is still owed and takes the merge decision from the counts on the line under it. A pass finding nothing where a close-out already stands rewrites that comment to cover what it read rather than posting a second one, so the thread carries one live verdict. Repeat from step 4 until a pass closes the review.
+3. Orchestrator dispatches a reviewer under `role-reviewer` for every pull request but a release one, which posts `review-pr` findings, and `review-ui` drives any visual checklist beside it.
+4. The reviewer tells the session holding that branch to run `review-address` once the pass posted a finding at any severity, resolving it with `canon sessions list --branch` and falling back to the orchestrator when none is live. The worker addresses the findings, rebases onto `origin/main` when a sibling landed first on a file it writes, then pushes a follow-up. A pass carrying only minor findings dispatches too, since the grade runs low often enough that a floor at should-fix loses fixes a worker would have made. `review-pr` states that threshold and the heading follows it, so an open heading is itself the signal to send.
+5. The worker asks that reviewer for the re-review directly, and the reviewer closes the review out with `review-pr` again. The second pass reads only the commits the follow-up added, or the worker's response alone when the follow-up added none, and posts under `## Review` when it finds anything and under `## Review closed` when it finds nothing, so a reader learns from the heading whether work is still owed and takes the merge decision from the counts on the line under it. A pass finding nothing where a close-out already stands rewrites that comment to cover what it read rather than posting a second one, so the thread carries one live verdict. Repeat from step 4 until a pass closes the review. Each reviewer then runs `canon pr lift`, which lifts the draft mark once every gate it reads is clear.
 6. The human reads the result and merges. After each merge, the orchestrator tells any trailing worker whose files the merged diff touches to run `review-address`, which rebases whether or not the review left anything open.
 
 There is no loop construct here. Each worker is a single build that halts at the
@@ -86,11 +86,11 @@ from merging promptly so the next PR does not rot against a moving main.
 
 The worker's chain carries no review step. The session that wrote the code is
 structurally blind to its own misreadings, because the same misreading wrote
-both the code and any review of it, so the first review a change gets is the
-orchestrator's.
+both the code and any review of it, so the first review a change gets is a
+dispatched reviewer's.
 
 - Worker gate, inside `auto-ship`: the session that wrote the code. Its job is "did I build the plan and does it pass?" The verify commands and the test order read decide whether the PR opens, and the draft mark holds the merge.
-- Orchestrator review, via `review-pr`: a fresh session with cross-feature context (the board, a sibling PR in flight, a downstream contract). Its job is "is this right and does it fit?" It can question the plan itself. This is the merge gate.
+- Reviewer pass, via `review-pr`: a fresh session holding one pull request, briefed with the cross-feature facts the orchestrator's wave pass found (a sibling PR in flight, a shared file, the merge order). Its job is "is this right and does it fit?" It can question the plan itself. This is the merge gate.
 
 The human read at merge is the final gate. No layer repeats another.
 
@@ -190,7 +190,7 @@ coordination costs more than the change it was too small.
 
 Two tiers hold work at different altitudes.
 
-- Tasks (`.canon/tasks/`): the active few pulled into the current turn, one file each. Gitignored, high churn. Shape governed by `canon standards tasks`. `priority.md` beside them carries execution order, and `backlog.md` carries what nobody is scheduling, both shaped by `canon standards board`.
+- Tasks (`.canon/tasks/`): the active few pulled into the current turn, one file each. Gitignored, high churn. Shape governed by the `task-board` skill. `priority.md` beside them carries execution order, and `backlog.md` carries what nobody is scheduling, both shaped by the same skill.
 - Edits: a few lines, done immediately with no ceremony.
 
 Nothing above these sequences work into versions. Scope is stated in
@@ -202,11 +202,9 @@ before another is carried nowhere at all.
 
 Review attention binds, and no number caps worker tracks, so stop adding once you cannot review every output. A row waits only on a conflict a merge cannot settle, which the `role-orchestrator` dispatch runbook states once. A shared file is not one: both rows build, and the branch merging second resolves any conflict in its own session after the first lands, since no practice source serializes on a file. [Fowler](https://martinfowler.com/articles/branching-patterns.html) has whoever integrates second check health "even if it's a clean merge", and [DORA](https://dora.dev/capabilities/trunk-based-development/) keeps branches to hours with no integration phase.
 
-Review splits by vantage. A reviewer under `role-reviewer` takes a pull
-request's read, first pass included, when three await one (a number set by
-hand), when a diff is too large to hold, or when it changes code or a skill or
-rule body. Prose stays with the orchestrator, which keeps one cross-branch pass
-per wave over file sets, the board, and merge order.
+Review splits by vantage. A reviewer under `role-reviewer` takes every pull
+request's read but a release one's and trades each round with the worker. The
+orchestrator keeps one cross-branch pass per wave over file sets and merge order.
 
 Inbound turns cost the controlling session as well, so weigh the spend before
 widening. A message from one of your other sessions arrives as a new turn

package/docs/workflow/skill-map.md

@@ -90,7 +90,7 @@ Each row sits under the group its skill's `metadata.family` names. The landing p
 
 | Skill                     | When to use                                                                                                 |
 | ------------------------- | ----------------------------------------------------------------------------------------------------------- |
-| `canon:role-orchestrator` | To assert the control session that owns the queue and reviews each worker's PR                              |
+| `canon:role-orchestrator` | To assert the control session that owns the queue and dispatches a reviewer for each worker's PR            |
 | `canon:role-planner`      | To assert the thinking role for a cold session writing a plan, a groundwork track, or an intake pass        |
 | `canon:role-reviewer`     | To assert the reviewing role for a cold session dispatched to review one pull request                       |
 | `canon:role-worker`       | To assert the worker role for a cold session building one branch under one plan                             |

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

@@ -14,19 +14,19 @@ The tier framework sits alongside [Claude Design](../../wiki/claude/design.md),
 
 ## Tier 0: prose only
 
-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.
+The default. `canon/DESIGN.md` holds visual intent, being one Overview paragraph, at most three one-line rules a section, and a table naming what each color and shape role is for. Its lead names the stylesheet the values live in, since a hand-typed copy of them drifts from the CSS.
 
 Claude Code reads it and writes the implementation. Works for CLI tools, internal dashboards, admin panels, and backend-focused projects.
 
 ### Seed shape
 
-The toolkit seed in `tooling/claude/seeds/canon/DESIGN.md` ships a token-table template with a starting set of roles, and `claude/skills/canvas-board/references/design.md` carries the same tables under `## Template` with placeholder rows. The column headers are what the renderer parses, so they stay verbatim in either, while the rows and values are the project's own.
+The toolkit seed in `tooling/claude/seeds/canon/DESIGN.md` ships an intent template with a starting set of roles, each naming its custom property, and `claude/skills/canvas-board/references/design.md` carries the same tables under `## Template` with placeholder rows. The column headers are what the parser reads, so they stay verbatim in either, while the rows are the project's own. The seed's lead asks for the project's own stylesheet, such as `src/styles/tokens.css` or a Tailwind `@theme` block, and falls back to `.claude/design/project/` only when the project has none.
 
 `canon design render` writes an HTML plus CSS preview to `.canon/tmp/render/design/` for eyeballing the current system without leaving Claude Code. See `canon/context/design/index.md`.
 
 A project wanting a neutral starting point to override runs `canon design install`, which copies one stylesheet to `.claude/design/base.css` carrying an achromatic token set as custom properties and two components built on them. Greys run from near-black to near-white and the accent is monochrome, so the only palette the project renders is one it writes itself. That file is toolkit-owned and `canon design sync` refreshes it, so a project overrides a value in `.claude/design/project/` instead, which sync never touches. Nothing arrives without that install, and the two channels are independent: a record the project wrote is its own, and the installed stylesheet is the toolkit's.
 
-A cell no source anchors ends in `? verify`, and the preview shows that marker beside the value rather than folding it in, so a swatch and a font sample stay built from the value alone. A confidence line above the sections names how many cells are anchored against how many are tagged, which is what tells a reader whether they are looking at a record of the code or a proposal about it. It reads the columns a source could anchor and leaves out the row names, so the ratio is not diluted by cells no tag could ever reach. The proposal path tags nearly all of them, so that count reads low on day one by design.
+A record generated from a token source carries the values in tables instead, which is the shape this toolkit's own record takes. There a cell no source anchors ends in `? verify`, and the preview shows that marker beside the value rather than folding it in, so a swatch and a font sample stay built from the value alone. A confidence line above the sections names how many cells are anchored against how many are tagged, which is what tells a reader whether they are looking at a record of the code or a proposal about it. It reads the columns a source could anchor and leaves out the row names, so the ratio is not diluted by cells no tag could ever reach. The proposal path tags nearly all of them, so that count reads low on day one by design.
 
 ### Tools
 

package/governance/detect.toml

@@ -21,71 +21,67 @@
 deps = []
 files = [".claude/skills", "claude/skills"]
 
-["700-ci-workflow"]
+["ci-workflow"]
 deps = []
 files = [".github/workflows"]
 
-["765-spelling"]
-deps = ["cspell"]
-files = [".cspell", "cspell.json", ".cspell.json", "cspell.config.*"]
-
-["775-dependencies"]
+["dependencies"]
 deps = []
 files = ["**/package.json", "**/pyproject.toml", "**/go.mod", "**/composer.json"]
 
-["780-config-comments"]
+["config-comments"]
 deps = []
 files = [".editorconfig", "**/Dockerfile*", "**/*.config.*", "**/.env.example"]
 
-["790-code-comments"]
+["code-comments"]
 deps = []
 files = ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx", "**/*.sh", "**/*.py"]
 
-["130-go"]
+["go"]
 deps = []
 files = ["**/go.mod"]
 
-["140-php"]
+["php"]
 deps = []
 files = ["**/composer.json"]
 
-["200-react"]
+["react"]
 deps = ["react"]
 files = []
 
-["210-astro"]
+["astro"]
 deps = ["astro"]
 files = ["**/astro.config.*"]
 
-["220-fastapi"]
+["fastapi"]
 deps = ["fastapi"]
 files = []
 
-["230-nextjs"]
+["nextjs"]
 deps = ["next"]
 files = ["**/next.config.*"]
 
-["250-tailwind"]
+["tailwind"]
 deps = ["tailwindcss", "@tailwindcss/vite", "@tailwindcss/postcss"]
 files = ["**/tailwind.config.*"]
 
-["260-shadcn"]
+["shadcn"]
 deps = []
 files = ["**/components.json"]
 
-["305-e2e-reliability"]
+["e2e-reliability"]
 deps = ["@playwright/test", "playwright", "cypress"]
 files = ["**/e2e"]
 
-["306-test-scope"]
+["test-scope"]
 deps = ["@playwright/test", "playwright", "cypress"]
 files = ["**/e2e"]
 
-["310-zod"]
+["zod"]
 deps = ["zod"]
 files = []
 
-["320-tanstack-query"]
+["tanstack-query"]
 deps = [
   "@tanstack/react-query",
   "@tanstack/vue-query",
@@ -95,23 +91,23 @@ deps = [
 ]
 files = []
 
-["335-testing-go"]
+["testing-go"]
 deps = []
 files = ["**/go.mod"]
 
-["336-testing-php"]
+["testing-php"]
 deps = ["phpunit/phpunit", "pestphp/pest"]
 files = ["**/phpunit.xml", "**/phpunit.xml.dist"]
 
-["340-pydantic"]
+["pydantic"]
 deps = ["pydantic"]
 files = []
 
-["350-security-web"]
+["security-web"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["360-security-server"]
+["security-server"]
 deps = [
   "express",
   "fastify",
@@ -133,7 +129,7 @@ deps = [
 ]
 files = []
 
-["370-database"]
+["database"]
 deps = [
   "prisma",
   "@prisma/client",
@@ -160,42 +156,42 @@ deps = [
 ]
 files = ["**/migrations", "**/schema.prisma", "**/*.sql"]
 
-["400-ui"]
+["copy"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["410-a11y"]
+["a11y"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["420-forms"]
+["forms"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["430-ux-completeness"]
+["ux-completeness"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["440-surface-capture"]
+["surface-capture"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["450-link-behavior"]
+["link-behavior"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["460-design-taste"]
+["design-taste"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["canon/DESIGN.md", "index.html", "*/index.html"]
 
-["465-interface-casing"]
+["interface-casing"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["470-motion"]
+["motion"]
 deps = ["react", "vue", "svelte", "astro", "next", "solid-js", "preact"]
 files = ["index.html", "*/index.html"]
 
-["480-canvas"]
+["canvas"]
 deps = []
 files = [".canon/canvas"]

package/governance/renames.toml

@@ -24,7 +24,6 @@
 "555-tasks" = "655-tasks"
 "558-plan" = "658-plan"
 "501-markdown" = "801-markdown"
-"065-spelling" = "765-spelling"
 "075-dependencies" = "775-dependencies"
 "080-config-comments" = "780-config-comments"
 "090-code-comments" = "790-code-comments"
@@ -33,3 +32,47 @@
 "655-tasks" = "tasks"
 "570-skill" = "skill"
 "801-markdown" = "markdown"
+"602-tasks" = "task-scope"
+"604-scratch" = "scratch"
+"605-worktrees" = "worktrees"
+"606-git" = "git"
+"611-indexes" = "indexes"
+"566-output" = "output"
+"000-code" = "routing"
+"010-testing" = "testing"
+"200-react" = "react"
+"210-astro" = "astro"
+"220-fastapi" = "fastapi"
+"230-nextjs" = "nextjs"
+"250-tailwind" = "tailwind"
+"260-shadcn" = "shadcn"
+"100-typescript" = "typescript"
+"110-python" = "python"
+"130-go" = "go"
+"140-php" = "php"
+"300-testing-ts" = "testing-ts"
+"305-e2e-reliability" = "e2e-reliability"
+"306-test-scope" = "test-scope"
+"310-zod" = "zod"
+"320-tanstack-query" = "tanstack-query"
+"330-testing-py" = "testing-py"
+"335-testing-go" = "testing-go"
+"336-testing-php" = "testing-php"
+"340-pydantic" = "pydantic"
+"350-security-web" = "security-web"
+"360-security-server" = "security-server"
+"370-database" = "database"
+"700-ci-workflow" = "ci-workflow"
+"775-dependencies" = "dependencies"
+"780-config-comments" = "config-comments"
+"790-code-comments" = "code-comments"
+"400-ui" = "copy"
+"410-a11y" = "a11y"
+"420-forms" = "forms"
+"430-ux-completeness" = "ux-completeness"
+"440-surface-capture" = "surface-capture"
+"450-link-behavior" = "link-behavior"
+"460-design-taste" = "design-taste"
+"465-interface-casing" = "interface-casing"
+"470-motion" = "motion"
+"480-canvas" = "canvas"

package/governance/rules/lib/{305-e2e-reliability.md → e2e-reliability.md}

@@ -32,4 +32,4 @@ paths:
 
 ## Authority
 
-- Follow `.claude/rules/canon/lib/300-testing-ts.md` for framework choice, file placement, and test naming.
+- Follow `.claude/rules/canon/lib/testing-ts.md` for framework choice, file placement, and test naming.

package/governance/rules/lib/{306-test-scope.md → test-scope.md}

@@ -20,5 +20,5 @@ paths:
 
 - Answer a question about the running page with a script against the dev server rather than with the suite.
 - Do not enable `fullyParallel` in `playwright.config.ts`.
-- Follow `.claude/rules/canon/ui/440-surface-capture.md` for capture scope.
-- Follow `.claude/rules/canon/lib/305-e2e-reliability.md` for waits and guards.
+- Follow `.claude/rules/canon/ui/surface-capture.md` for capture scope.
+- Follow `.claude/rules/canon/lib/e2e-reliability.md` for waits and guards.

package/governance/rules/ui/{410-a11y.md → a11y.md}

@@ -60,4 +60,4 @@ paths:
 
 - Let content reflow at a viewport 320 CSS pixels wide with no loss of content or function and no two-dimensional scrolling. Only content whose meaning depends on both axes, such as a data table, a map, or a diagram, may scroll sideways (WCAG Reflow, 1.4.10, Level AA).
 - Treat 320 as the criterion's own test condition rather than a device width. It is equivalent to a 1280 pixel window at 400 percent zoom, so a layout that breaks there breaks for a person who zooms.
-- Hold the same 320 floor for the content region beside persistent chrome a person can resize. The criterion measures the viewport, so this extension is this rule's own rather than the criterion's: a panel widened to 480 in a 768 window leaves 288 for the content, under the floor at a window the criterion passes. `440-surface-capture` states where the frame for it gets taken.
+- Hold the same 320 floor for the content region beside persistent chrome a person can resize. The criterion measures the viewport, so this extension is this rule's own rather than the criterion's: a panel widened to 480 in a 768 window leaves 288 for the content, under the floor at a window the criterion passes. `surface-capture` states where the frame for it gets taken.

package/governance/rules/ui/{440-surface-capture.md → surface-capture.md}

@@ -26,12 +26,12 @@ paths:
 ## What a capture covers
 
 - Capture the full page. Do not capture a component in isolation.
-- Declare the widths a layout case captures. Always include 320, the reflow floor from the reflow criterion in `410-a11y`, then add each breakpoint bucket the project writes rules for, read from the `## Layout` section of `DESIGN.md`.
+- Declare the widths a layout case captures. Always include 320, the reflow floor from the reflow criterion in `a11y`, then add each breakpoint bucket the project writes rules for, read from the `## Layout` section of `DESIGN.md`.
 - Fall back to the 320 floor alone when the project has no `DESIGN.md` or its record carries no `## Layout` section. Do not impose another project's breakpoints.
 - Add a layout case at each bound when a surface renders persistent chrome a person can resize, such as a draggable sidebar or a split pane, one with the chrome at its narrowest and one at its widest. Take both at the narrowest declared width where the chrome stays persistent rather than collapsing, since a frame where it has turned into an overlay shows none of the width it takes.
-- Read those bounds from the code that clamps the chrome, since `## Layout` has no slot for them. Judge each frame by the content width left beside the chrome rather than by the window width, against the 320 floor `410-a11y` holds for that region.
+- Read those bounds from the code that clamps the chrome, since `## Layout` has no slot for them. Judge each frame by the content width left beside the chrome rather than by the window width, against the 320 floor `a11y` holds for that region.
 - Apply the declaration to a case that covers layout only. A case driving a menu open or an answer chosen tests a state, so it takes one width rather than the full set.
-- Read a capture at 320 as proof that a frame was taken there, not that the page reflows correctly. The criterion is stated in `410-a11y` and nothing here enforces it.
+- Read a capture at 320 as proof that a frame was taken there, not that the page reflows correctly. The criterion is stated in `a11y` and nothing here enforces it.
 - Write the capture into a folder named `evidence`. The image is collected for the pull request comment when any segment of its path is literally `evidence` and its filename carries an image extension, so the folder name is fixed and its position in the tree is the project's own.
 - Several `evidence/` folders in one project is the ordinary shape rather than a problem to consolidate. One per surface is how a project with more than one rendered surface ends up.
 - Drive a state a screenshot cannot reach. An initial render reports nothing about a menu that opens, an answer that is chosen, or a rail that tracks scrolling.

package/governance/stacks/base.toml

@@ -1,9 +1,16 @@
 extends = ""
-# Four audience groups whole. Every rule authored under them ships to a base
-# consumer, so adding one is a single edit rather than a file and a name here.
-# `canon` carries the toolkit workflow and canonical-doc rules, `claude` the
-# session conduct and `.claude/` authoring rules, `tooling` the dev setup and
-# CI workflow rules, and `writing` the prose and document-shape rules. The
-# `code` group is left to the stacks that write code, so a docs or writing
-# project loads no rule it can never apply.
-rules = ["canon", "claude", "tooling", "writing"]
+# Named rule by rule rather than by folder, so a rule authored later under
+# `canon` or `claude` reaches no project until it is added here or proposed by
+# `canon gov detect`. Every other rule is opt-in.
+rules = [
+  "output",
+  "task-scope",
+  "scratch",
+  "worktrees",
+  "git",
+  "indexes",
+  "context",
+  "tasks",
+  "plan",
+  "markdown",
+]

package/governance/stacks/go.toml

@@ -0,0 +1,2 @@
+extends = "base"
+rules = ["code", "go", "testing-go"]

package/governance/stacks/node.toml

@@ -1,2 +1,2 @@
 extends = "base"
-rules = ["code", "100-typescript"]
+rules = ["code", "typescript", "testing-ts"]

package/governance/stacks/php.toml

@@ -0,0 +1,2 @@
+extends = "base"
+rules = ["code", "php", "testing-php"]

package/governance/stacks/python.toml

@@ -1,2 +1,2 @@
 extends = "base"
-rules = ["code", "110-python", "340-pydantic", "330-testing-py", "360-security-server", "370-database"]
+rules = ["code", "python", "testing-py"]

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/canon",
   "type": "module",
-  "version": "5.34.0",
+  "version": "5.36.0",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
   "license": "MIT",
   "bin": {
@@ -10,7 +10,6 @@
   "files": [
     "src",
     "scripts",
-    "standards",
     "governance",
     "tooling",
     "claude",
@@ -25,7 +24,6 @@
     "access": "public"
   },
   "scripts": {
-    "check:spell": "cspell '**' '.*/**' '.*' --no-progress --color --show-context",
     "format": "prettier --write --log-level warn --ignore-path .gitignore --ignore-path .prettierignore . && shfmt --write --indent 2 scripts/ tooling/ claude/",
     "check:format": "prettier --check --log-level warn --ignore-path .gitignore --ignore-path .prettierignore . && shfmt --diff --indent 2 scripts/ tooling/ claude/",
     "check:shell": "find scripts tooling claude .claude/hooks -name '*.sh' -exec shellcheck --severity=warning {} + && find .husky -maxdepth 1 -type f -exec shellcheck --severity=warning --shell=sh {} +",
@@ -71,7 +69,6 @@
     "@types/bun": "^1.2.10",
     "@types/micromatch": "^4.0.10",
     "astro": "^6.1.9",
-    "cspell": "^8.17.1",
     "happy-dom": "^20.14.5",
     "husky": "^9.1.7",
     "micromatch": "^4.0.8",

package/scripts/core/install-check.sh

@@ -97,23 +97,17 @@ log_step "Assert scaffold"
 # catches a failed domain, and the gate stays green while the target is
 # missing everything that domain provides.
 #
-# Standards name no path because that corpus never installs into a target. A
-# scaffold reads a standard through `canon standards <name>`, resolving against
-# the toolkit rather than a copy this gate could assert on. The two
+# Authoring references name no path because they ship inside the plugin's
+# skills rather than installing into a target. The two
 # rule paths stand for the `claude` and `canon` groups `base` takes whole.
 for path in "CLAUDE.md" ".claude/wiki/index.md" ".claude" "canon/context/index.md" \
-  ".prettierrc" ".editorconfig" ".lintstagedrc" ".husky/pre-commit" ".github/workflows/verify.yml" "scripts/verify.sh" \
-  ".claude/rules/canon/claude/566-output.md" ".claude/rules/canon/canon/604-scratch.md"; do
+  ".prettierrc" ".lintstagedrc" ".husky/pre-commit" ".github/workflows/verify.yml" "scripts/verify.ts" \
+  ".claude/rules/canon/claude/output.md" ".claude/rules/canon/canon/scratch.md"; do
   if [ ! -e "$TARGET_DIR/$path" ]; then
     log_error "Missing after canon init: $path"
   fi
   log_info "Found: $path"
 done
 
-if [ ! -x "$TARGET_DIR/scripts/verify.sh" ]; then
-  log_error "Not executable after canon init: scripts/verify.sh"
-fi
-log_info "Executable: scripts/verify.sh"
-
 log_step "Verification passed"
 log_info "Manual check still needed: bun link and global canon invocation"

package/src/audits/catalog.ts

@@ -468,7 +468,6 @@ const RECORD_KINDS: readonly (readonly [string, Corpus])[] = [
   ['plans', 'per-machine'],
   ['groundwork', 'per-machine'],
   ['intake', 'per-machine'],
-  ['standards', 'tracked'],
   ['teach', 'per-machine'],
 ]
 
@@ -588,14 +587,6 @@ export const AUDITS: readonly AuditSpec[] = [
     argv: ['records', 'validate', kind, '--json'],
     gatingExits: [],
     corpus,
-    // `standards` is the one tracked kind here, so it takes none of the
-    // per-machine default the other five inherit from their corpus. A target
-    // reads standards through `canon standards` rather than a copy in its own
-    // tree, so carrying no standards folder at all is the
-    // ordinary state of every project but this repository.
-    ...(kind === 'standards' && {
-      absentReasons: ['no-folder'] satisfies RecordRefusal[],
-    }),
     counts: findingsOnly,
   })),
   {

package/src/capture/frame-values.ts

@@ -121,9 +121,6 @@ const plural = (count: number, noun: string): string =>
 const frameRow = (cells: string): string =>
   `<span class="frame">│</span> <span class="ok">✓</span> ${cells}`
 
-/** Rule names carry a numeric prefix that orders the load, not the identity. */
-const slug = (name: string): string => name.replace(/^\d+-/, '')
-
 /** Indented to the depth a rule inside the `<style>` block sits at. */
 const indentTokens = (css: string): string =>
   css
@@ -194,13 +191,13 @@ export function buildFrameValues(catalogs: FrameCatalogs): FrameValues {
   }
 
   const tokenCss = indentTokens(catalogs.tokenCss)
-  const rules = gov.rules.map((entry) => slug(entry.name))
+  const rules = gov.rules.map((entry) => entry.name)
   // A rule no stack names is opt-in behind `--add`, so featuring one advertises
   // an entry no ordinary `canon gov install` delivers. The column samples the
   // stack-reached subset while its count and remainder describe the whole.
   const stacked = new Set(gov.stacks.flatMap((stack) => stack.rules))
   const deliveredEntries = gov.rules.filter((entry) => stacked.has(entry.name))
-  const deliveredRules = deliveredEntries.map((entry) => slug(entry.name))
+  const deliveredRules = deliveredEntries.map((entry) => entry.name)
 
   for (const [label, list] of [
     ['skills', skills],
@@ -236,7 +233,7 @@ export function buildFrameValues(catalogs: FrameCatalogs): FrameValues {
       const scope =
         globs.length > 0 ? clip(globs.join(' '), GLOB_WIDTH) : 'every session'
       return frameRow(
-        `<span class="name">${escape(pad(slug(entry.name), 24))}</span>` +
+        `<span class="name">${escape(pad(entry.name, 24))}</span>` +
           `<span class="domain">${escape(pad(`[${entry.domain}]`, 12))}</span>` +
           `<span class="muted">${escape(scope)}</span>`,
       )

package/src/claude/routing.ts

@@ -16,7 +16,7 @@ const PATH_TOKEN = /^[.A-Za-z0-9_][A-Za-z0-9._/-]*$/
 /** A placeholder segment, which a shape carries and a real path does not. */
 const SHAPE = /<[^>]*>/
 
-/** An alphabetic extension, which separates `cspell.json` from `3.6.0`. */
+/** An alphabetic extension, which separates `tsconfig.json` from `3.6.0`. */
 const EXTENSION = /\.[a-z]{2,5}$/
 
 /** Extensions a folder is probed with, so a glob narrowed by type still hits. */