@erclx/canon 5.44.0 → 5.45.0

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

@@ -10,35 +10,27 @@ paths:
 
 ## Framework
 
-- Use `pytest` for all tests. Do not use `unittest.TestCase`.
-- Place tests under `tests/`, mirroring the `src/` package layout.
-- Name files `test_*.py` and test functions `test_*`.
+- Write tests as plain `pytest` functions, never `unittest.TestCase` subclasses, which lose fixtures and parametrization.
 
 ## Fixtures
 
-- Use `@pytest.fixture` over setup and teardown methods.
-- Place shared fixtures in `conftest.py` at the narrowest scope that needs them.
-- Set `scope=` (`"session"`, `"module"`, `"function"`) explicitly when reuse matters.
-- Use `tmp_path` and `monkeypatch` over hand-rolled temp directories or env stashes.
+- Write setup and teardown as a `@pytest.fixture` that yields, over setup and teardown methods.
+- Place a shared fixture in the `conftest.py` of the narrowest directory whose tests need it.
+- Widen a fixture's `scope=` past the `function` default only for state no test mutates.
+- Use `tmp_path` and `monkeypatch` over hand-rolled temp directories or environment stashes, since both undo themselves.
 
 ## Parametrize
 
 - Use `@pytest.mark.parametrize` for table-driven cases over per-case test functions.
-- Use `ids=` to label parametrized cases when their repr is unclear.
 
 ## Async
 
-- Mark async tests with `@pytest.mark.asyncio` or configure `asyncio_mode = "auto"`.
-- Do not start a fresh event loop inside tests.
+- Mark each async test `@pytest.mark.asyncio`, or set `asyncio_mode = "auto"`, since strict mode runs only marked tests.
+- Run on the event loop `pytest-asyncio` provides. Never call `asyncio.run()` or create a loop inside a test.
 
 ## Assertions and mocks
 
-- Use plain `assert` over `self.assertEqual`. Pytest rewrites assertions for readable diffs.
-- Use `pytest.raises(...)` over `try/except` for expected exceptions.
-- Use `monkeypatch.setattr` or `unittest.mock.patch` over ad hoc module rewrites.
-- Do not make real network calls. Use `responses`, `httpx_mock`, or fakes.
-
-## Conventions
-
-- Arrange, act, assert per test, with one logical assertion group.
-- Use descriptive `test_*` names that read as the assertion. Do not prefix with `should_`.
+- Use plain `assert`, which pytest rewrites to report the values, over `self.assertEqual`.
+- Use `pytest.raises(...)` over `try` and `except` for an expected exception.
+- Patch with `monkeypatch.setattr` or `unittest.mock.patch`, never by assigning a module attribute by hand.
+- Do not make real network calls. Use `responses`, `pytest-httpx`, or a fake.

package/governance/rules/lib/testing-ts.md

@@ -12,29 +12,20 @@ paths:
 ## Unit and integration
 
 - Use Vitest for unit and integration tests.
-- Co-locate unit tests with their respective components.
-- Use `userEvent` over synthetic events for interaction simulation.
-- Use MSW for network mocking. Do not mock fetch or axios manually.
-- Select elements by accessibility attributes first (`getByRole`, `getByLabelText`).
+- Simulate interaction with `userEvent` over `fireEvent`, since it refuses what a browser would, such as a click on a hidden element.
+- Mock the network with MSW. Never mock `fetch` or axios by hand, and never let a unit test make a real call.
+- Query by role or label first, such as `getByRole` and `getByLabelText`, and by test ID only when neither matches.
 
 ## End-to-end
 
 - Use Playwright for end-to-end tests.
-- Place all Playwright tests within the `e2e/` directory.
-- Never place Playwright tests inside `src/`.
-- Scope the three rules above to tests the Playwright runner executes. A Vitest test importing a browser driver to exercise project code stays beside its module, where Vitest looks for it.
-- Keep specs apart from their fixtures, page objects, and helpers inside `e2e/`. Load the `canon:codebase-layout` skill for the folder shape.
+- Place every test the Playwright runner executes under `e2e/`, never `src/`. A Vitest test that drives a browser stays beside its module.
 
 ## Timers and async
 
-- Never use `vi.useFakeTimers()` in `beforeEach` when tests use `waitFor`, `act`, or `userEvent`.
-- Scope fake timers to the individual test that needs them.
-- Restore real timers with `vi.useRealTimers()` in a matching `afterEach`.
+- Pass `advanceTimers: vi.advanceTimersByTime` to `userEvent.setup()` whenever fake timers are on.
+- Restore real timers with `vi.useRealTimers()` in `afterEach`, after `vi.runOnlyPendingTimers()`.
 
 ## Conventions
 
-- Use `.test.ts` / `.test.tsx` for unit tests.
-- Use `.spec.ts` / `.spec.tsx` for integration tests and for Playwright tests under `e2e/`.
-- Do not make real network calls in unit tests.
-- `describe()` labels use the exact identifier of the subject under test in its natural casing.
-- `it()` descriptions use "should" + sentence case.
+- Name a unit test `.test.ts` or `.test.tsx`, and an integration or Playwright test `.spec.ts` or `.spec.tsx`.

package/governance/rules/lib/zod.md

@@ -9,17 +9,15 @@ paths:
 
 ## Type inference
 
-- Use `z.infer<typeof Schema>` to generate TypeScript types (Single Source of Truth).
-- Do not manually declare interfaces that duplicate Zod schemas.
-- Do not export the runtime Schema if only the inferred Type is required by consumers.
+- Derive a schema's type with `z.infer<typeof Schema>`, never a hand-written interface that duplicates the schema.
 
 ## Boundary validation
 
-- Use `.strict()` for untrusted external API boundaries to prevent data pollution.
-- Use `.parse()` for blocking validation (env vars) and `.safeParse()` for recoverable flows (forms).
-- Restrict `z.coerce` to I/O boundaries (e.g., URL params). Never use it for internal data flow.
+- Parse untrusted input with `z.strictObject()` so an unknown key fails, never with a method the Zod 4 changelog marks legacy.
+- Narrow a schema with `.pick()` or `.omit()`, never by passing unknown keys through with `z.looseObject()`.
+- Call `.parse()` where a failure should throw, and `.safeParse()` where the caller recovers, such as a form.
+- Restrict `z.coerce` to string input at an I/O boundary such as URL params, since it converts with `String()` or `Boolean()`.
 
 ## Schema safety
 
-- Use `z.unknown()` for truly ambiguous inputs instead of `z.any()`.
-- Prefer `.strict()` at boundaries or explicit `.pick()`/`.omit()` over `.passthrough()`.
+- Use `z.unknown()` for an input of unknown shape, never `z.any()`, which infers `any` and switches off checking downstream.

package/governance/rules/tooling/code-comments.md

@@ -16,14 +16,12 @@ paths:
 - Write a comment only when it records a fact the reader cannot recover from the code: an external contract, a rejected alternative, or the reason a surprising line is correct.
 - Do not restate in prose what the line beside it already says.
 - Do not comment a self-contained function whose signature and body already carry its behavior.
-- Let comment density follow how much of a file's behavior is decided outside that file. Treat density as an outcome, never as a target.
-- Do not add or delete a comment to move a file toward a density figure.
+- Do not add or delete a comment to move a file toward a density figure, since density follows how much of its behavior is decided outside it.
 
 ## What a comment may claim
 
-- State only what is true of the code as written.
+- Keep each comment true of the code as written, and update or delete one a change invalidates in that same change.
 - Describe a function's contract and its constraints, never its steps line by line.
-- Update or delete an invalidated comment in the same change that invalidates it.
 - Do not name a person, a ticket, or a date in place of the fact itself.
 
 ## What never goes in a comment

package/governance/rules/tooling/config-comments.md

@@ -1,5 +1,5 @@
 ---
-description: Keep comments terse in dotfiles, config, and workflow files
+description: Keep comments in dotfiles, config, and workflow files to what a key does or accepts
 paths:
   - '**/.env*'
   - '**/.gitignore'
@@ -16,7 +16,4 @@ paths:
 
 ## Comments
 
-- Keep each comment to one short line. Do not wrap a single key in a multi-line explanation.
-- Prefer a one-word category label over a sentence for a group header.
-- Match the comment density of the surrounding file. Do not add a verbose comment next to terse ones.
 - Comment what a key does or its allowed values. Do not restate the key name.

package/governance/rules/tooling/dependencies.md

@@ -15,7 +15,7 @@ paths:
 ## Declaration
 
 - Declare a package in the project manifest before importing it anywhere in the source.
-- Add a package with the package manager command that writes the manifest and the lockfile together, such as `bun add` or `uv add`. Never hand-edit the manifest and never install without recording the result.
+- Add a package with the command that writes the manifest and the lockfile together, such as `bun add` or `uv add`. Re-lock in the same change after any hand edit to the manifest.
 - Commit the lockfile with the manifest change in the same commit.
 - Declare a package used only by tests, builds, or tooling as a development dependency.
 - Never import a package that arrives only as a transitive dependency of another package.

package/governance/rules/ui/a11y.md

@@ -1,5 +1,5 @@
 ---
-description: Keyboard interaction, focus management, and ARIA accessibility for rendered UI
+description: Semantics, text alternatives, contrast, and reflow for rendered UI
 paths:
   - '**/*.tsx'
   - '**/*.jsx'
@@ -8,56 +8,27 @@ paths:
   - '**/*.css'
 ---
 
-# Accessibility and keyboard standards
+# Accessibility standards
 
-## Focus styles
+## Semantics
 
-- All interactive elements must use the project focus ring. Do not define per-component focus styles.
-- Never apply `outline-none` without a custom focus ring in the same rule.
-- Focus ring must have 3:1 contrast against its background in both light and dark modes.
+- Use a native `<button>` or `<a>` over a `<div>` or `<span>` carrying a click handler, since the native element brings its role, focus, and keyboard activation.
+- Spell an attribute the way the file's syntax spells it, being `onclick` and `tabindex` in HTML and Astro markup and `onClick` and `tabIndex` in JSX.
+- Give a custom control the role its pattern names, such as `combobox` or `listbox`, and keep `aria-expanded`, `aria-selected`, and `aria-checked` in step with what it shows.
+- Give an interactive element with no visible text label a name through `aria-label` or `aria-labelledby`.
 
-## Keyboard interaction model
+## Text alternatives
 
-- Tab / Shift+Tab: move focus sequentially through interactive elements in DOM order.
-- Enter: activates buttons and links, submits forms.
-- Space: activates buttons and checkboxes, toggles selection in listboxes.
-- Arrow keys: navigate within composite widgets. Do not let them exit the widget.
-- Escape: closes any overlay, popover, dialog, or dropdown. Cancels in-progress edits.
-- Do not introduce non-standard key bindings for common actions.
-- Give every author-defined drag a single-pointer alternative and a keyboard path, such as move buttons or arrow-key reordering (WCAG 2.2 Dragging Movements, 2.5.7).
+- Give every `<img>` an `alt`, and use `alt=""` for a decorative image.
+- Describe what an image means, or the action an icon control takes, never its appearance. Do not prefix it with "Image of" or "Photo of".
 
-## Pointer targets
+## Contrast and color
 
-- Size a web pointer target at least 24 by 24 CSS pixels, or space it so a 24 pixel circle centered on it touches no other target (WCAG 2.2 Target Size Minimum, 2.5.8).
-- Size a native touch target at the platform figure, 44 points on iOS and 48 dp on Android. Do not apply the web figure to native, and do not apply the native figure as the web minimum.
-
-## Composite widgets
-
-- Roving tabindex for interactive collections: one item in the tab sequence at a time.
-- Combobox: arrow keys navigate options, Enter selects, Escape closes, typing filters.
-
-## Focus management
-
-- Move focus into any overlay, popover, or dialog on open. Return focus to the trigger on close.
-- Never move focus on hover. Only on keyboard input or explicit pointer activation.
-- Do not let a sticky header, footer, or overlay fully cover the focused control. Scroll it into view clear of them (WCAG 2.2 Focus Not Obscured, 2.4.11).
-
-## ARIA semantics
-
-- Use semantic HTML over custom elements: `<button>` over a `<div>` carrying a click handler, `<a>` over a `<span>` carrying one.
-- A `<div>` with a click handler requires a role, a tab index, and keyboard handlers. Use `<button>` instead.
-- Spell an attribute the way the file's syntax spells it: `onclick` and `tabindex` in HTML and Astro markup, `onClick` and `tabIndex` in JSX.
-- Set role on custom controls: `role="combobox"`, `role="listbox"`, `role="menu"`, `role="option"`.
-- Synchronize state attributes with visual state: `aria-expanded`, `aria-selected`, `aria-checked`, `aria-disabled`.
-- Add `aria-label` or `aria-labelledby` to interactive elements with no visible text label.
-- Always provide `alt` on `<img>`. Use `alt=""` for decorative images.
-- Describe the content or function of the image, not its appearance. Do not prefix with "Image of" or "Photo of".
-- Alt text for functional images (icons, buttons) should describe the action, not the graphic.
-- Give the visual boundary of a control and every graphic that carries meaning at least 3:1 contrast against adjacent colors (WCAG Non-text Contrast, 1.4.11).
-- Never make color the only carrier of a state, error, or distinction. Pair it with text, an icon, or a pattern (WCAG Use of Color, 1.4.1).
+- Give a control's visual boundary and every graphic that carries meaning at least 3:1 contrast against adjacent colors (WCAG 1.4.11).
+- Never make color the only carrier of a state, error, or distinction. Pair it with text, an icon, or a pattern (WCAG 1.4.1).
 
 ## Reflow
 
-- 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. `surface-capture` states where the frame for it gets taken.
+- Let content reflow at 320 CSS pixels wide with no loss and no two-dimensional scrolling, except a data table, map, or diagram (WCAG 1.4.10).
+- Treat 320 as a 1280 pixel window at 400 percent zoom rather than a device width, so a layout breaking there breaks for a person who zooms.
+- Hold the same 320 floor for the content region beside persistent chrome a person can resize. This extends the criterion, which measures the viewport alone.

package/governance/rules/ui/copy.md

@@ -11,21 +11,18 @@ paths:
 
 ## Punctuation
 
-- Do not use em dashes (`—`) or semicolons (`;`). Use a comma or period, or restructure the sentence.
-- Do not add punctuation to button labels or short action strings.
+- 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
 
-- Use imperative verbs for actions: `Save`, `Delete`, `Connect`, `Cancel`.
-- Avoid padded phrasing: `Save` over `Save changes`, `Delete` over `Click to delete`.
+- 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
 
-- State what to do, not what went wrong: `Enter a valid email` over `Email is invalid`.
-- Keep messages short and actionable.
-- One sentence maximum.
+- 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
 
-- Show format examples over instructions: `name@example.com` over `Enter your email here`.
-- Reserve instructions for labels or helper text below the input.
+- 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/forms.md

@@ -1,5 +1,5 @@
 ---
-description: Form validation timing, save-blocking, and derived state for rendered forms
+description: Form validation timing, submission, error placement, and derived state for rendered forms
 paths:
   - '**/*.tsx'
   - '**/*.jsx'
@@ -11,35 +11,29 @@ paths:
 
 ## Validation timing
 
-- Validate on blur, not on every keystroke. Exception: realtime feedback that is explicitly part of the feature (e.g. character count, live search).
-- After a field shows its first error (on blur), re-validate on every change so the error clears as soon as the input becomes valid.
-- Apply the same validation timing to all fields in a form. Do not mix blur-only and change-only validation within one form.
-- Do not show an error on a field the user has never touched.
+- Validate when the person submits or continues, never when focus leaves a field. Realtime feedback the feature exists for, such as a character count, is the exception.
+- Re-validate a field on every change once it shows an error, so the error clears as soon as the input is valid.
 
-## Save blocking
+## Submission
 
-- Block save when any required field is empty, invalid, or has never been touched.
-- Treat whitespace-only values as empty for required fields.
+- Refuse a submit while a required field is empty, whitespace-only, or invalid, and show each error. Keep the submit button enabled rather than disabling it.
 
 ## Error placement
 
-- Show the error directly under the field that caused it, not under an unrelated field.
-- When a change to field A causes a conflict involving field B, show the error under field A (the field the user edited), not under field B.
-
-## Submission errors
-
-- When a failed submission carries several errors, move focus to a summary that links to each failing field. Keep the inline error beside each field.
+- Show each error next to the field that caused it, never under an unrelated field.
+- Show a cross-field conflict under the field the person edited, not under the field it conflicts with.
+- Move focus to an error summary linking to each failing field when a submission fails, and keep the inline error beside each field.
 
 ## Authentication and re-entry
 
-- Let a password manager fill sign-in fields and accept a pasted value. Do not block paste or autofill on a password or code field (WCAG 2.2 Accessible Authentication, 3.3.8).
-- Do not ask for information the user already gave earlier in the same flow. Prefill it or offer it for selection (WCAG 2.2 Redundant Entry, 3.3.7).
+- Let a password manager fill sign-in fields and accept a pasted value. Never block paste or autofill on a password or code field (WCAG 3.3.8).
+- Never ask again for information the person gave earlier in the same flow. Prefill it or offer it for selection (WCAG 3.3.7).
 
 ## Input sanitization
 
-- Trim leading and trailing whitespace from text inputs on blur or submit, not on every keystroke.
-- If a field is case-sensitive, surface that constraint near the field. Do not silently treat `Foo` and `foo` as different values without warning.
+- Trim leading and trailing whitespace from a text input on submit, never on every keystroke.
+- Say near a case-sensitive field that it is case-sensitive, rather than silently treating `Foo` and `foo` as different values.
 
 ## Derived display state
 
-- Reset status indicators, counts, and derived display values when their source input changes.
+- Reset a status indicator, count, or derived value to neutral when its source input changes.

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

@@ -13,19 +13,17 @@ paths:
 
 ## Sentence case
 
-- Use sentence case for all rendered interface text: headings, labels, nav items, tab titles, and dialog titles.
-- Retain original casing for proper nouns and product names: `GitHub`, `macOS`, `TypeScript`.
-- Treat title case on every heading as a template tell, since it reads as a default rather than a choice.
+- 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 one per three sections, with the first screen counting as one. More than `ceil(sections / 3)` is too many, and the fix is usually to delete the label, since a section's position already says what it is.
-- Treat the count as a judgment, since a glob cannot check it.
+- 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
 
-- The rule covers markup, MDX, and content modules under a `content/` folder. Copy kept elsewhere, such as a locale file, is not reached, so apply the same casing there without the rule firing.
+- 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 where the case needs it, such as an acronym, a brand mark, or a set-in-caps identity the design chose on purpose.
+- 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/keyboard.md

@@ -0,0 +1,38 @@
+---
+description: Focus styles, keyboard operation, focus management, and pointer targets for rendered UI
+paths:
+  - '**/*.tsx'
+  - '**/*.jsx'
+  - '**/*.astro'
+  - '**/*.html'
+  - '**/*.css'
+---
+
+# Keyboard and focus standards
+
+## Focus styles
+
+- Style focus through the project's one focus ring rather than a per-component focus style.
+- Never set `outline: none` or `outline-none` without a replacement focus indicator in the same rule.
+- Give the focus ring 3:1 contrast against its background in every theme the project ships.
+
+## Keyboard operation
+
+- Close a dialog, popover, menu, or inline confirmation on Escape, and cancel an in-progress edit the same way.
+- Bind no single printable character as a shortcut unless a person can turn it off or remap it, or it fires only while its control has focus (WCAG 2.1.4).
+- Give every author-defined drag a single-pointer alternative and a keyboard path, such as move buttons or arrow-key reordering (WCAG 2.5.7).
+
+## Composite widgets
+
+- Keep one item of a composite widget in the tab sequence, and move between its items with the arrow keys through roving `tabindex` or `aria-activedescendant`.
+- Open a combobox popup on Down Arrow, accept the focused option on Enter, and close the popup on Escape without changing the value.
+
+## Focus management
+
+- Move focus into a dialog when it opens, and return it to the element that opened it when it closes.
+- Never let a sticky header, footer, or overlay fully cover the focused control. Scroll it clear of them (WCAG 2.4.11).
+
+## Pointer targets
+
+- Size a web pointer target at least 24 by 24 CSS pixels, or space it so a 24 pixel circle centered on it touches no other target (WCAG 2.5.8).
+- Size a native touch target at the platform figure, 44 points on iOS and 48 dp on Android, and never swap the web and native figures.

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

@@ -11,9 +11,9 @@ paths:
 
 ## Default target
 
-- Open a link in the same tab. Reserve `target="_blank"` for a destination that would discard in-progress work if it replaced the current page, such as a document a user is midway through elsewhere.
-- Do not add `target="_blank"` as a default for every external link.
+- 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 page content, so a new tab leaves an empty tab behind.
+- 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.

package/governance/rules/ui/motion.md

@@ -12,12 +12,12 @@ paths:
 
 ## Moving content
 
-- Give any content that moves, blinks, or scrolls automatically for more than five seconds a control to pause, stop, or hide it (WCAG Pause, Stop, Hide, 2.2.2).
+- Give any content that moves, blinks, or scrolls automatically for more than five seconds a control to pause, stop, or hide it (WCAG 2.2.2).
 - Halt an auto-advancing carousel or ticker while it holds keyboard focus or pointer hover.
-- Do not flash content more than three times in any one second.
+- Never flash content more than three times in any one second (WCAG 2.3.1).
 
 ## Reduced motion
 
 - Honor `prefers-reduced-motion: reduce` for every animation and transition that conveys no state. Remove it or replace it with an instant change.
 - Keep essential state changes visible under reduced motion, using a fade or a static indicator instead of movement.
-- Do not start video or animated backgrounds on their own when the preference is set.
+- Start no video or animated background on its own when the preference is set.

package/governance/rules/ui/surface-capture.md

@@ -12,39 +12,27 @@ paths:
 
 ## What a surface is
 
-- A surface is anything the project renders for a person to look at. A framework route is one. A page the project generates is another, whoever generates it.
-- Judge a generated page by the same rule as a route. Reading its markup reports nothing about how it composes.
-- A component the production build strips out is not a surface, such as a dev-only scenario switcher gated behind a build flag. The build removes it before anything renders, so no comparison exists to capture.
+- Treat anything the project renders for a person as a surface, a generated page as much as a route.
+- Skip a component the production build strips out, such as a dev-only switcher.
 
 ## When to capture
 
-- Run the project's capture command after changing what a surface renders. Report it rather than proceeding silently when the project has none.
-- Capture against a running preview server. Do not capture against a dev server.
-- Capture every theme the surface ships. Do not capture the default theme alone.
-- Capture again after fixing a defect a capture found. A repair inside a shared stylesheet can cancel a rule written earlier in the same file.
+- Run the project's capture command against a preview server, never a dev server, after changing a surface. Report it when the project has none.
+- Capture every theme the surface ships, and again after fixing a defect a capture found.
 
 ## 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 `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 `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 `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.
-- Add a case to the capture record when adding a surface.
-- Remove a surface's case in the change that removes the surface.
+- Capture the full page, never a component in isolation.
+- Capture a layout case at 320, the reflow floor in `a11y`, plus each breakpoint in the `## Layout` section of `DESIGN.md`, or at 320 alone when there is none.
+- Capture resizable chrome at its narrowest and widest clamp, at the narrowest width keeping it persistent. Judge the content width beside it.
+- Capture a state case at one width rather than the full set.
+- Drive a state an initial render cannot reach, such as an open menu or a rail tracking scroll.
+- Add a surface's case with the surface, and remove it with the surface.
 
 ## Sharing a capture
 
-- Do not commit the sweep. It stays ignored.
-- Commit a flagged case's evidence output so the pull request carries the comparison, rather than attaching it by hand.
-- A project whose own established convention already commits that same comparison may route a flagged case's evidence there instead of a separate evidence folder. Only an established convention already committing the same comparison qualifies, not a preference for skipping a second folder.
-- Commit an evidence case for the first time only after running the capture twice with no code change between the runs and confirming the two outputs are byte-identical.
-- Mask the element carrying a value that moves between runs, such as an elapsed-time counter, a clock, or a relative date, in the state's capture case before the double capture, so the check still runs on everything else in the frame. Mask the smallest element holding the value, never the state.
-- Do not commit the state as evidence when the masked outputs still differ, which happens when the value's width reflows its neighbors. Name the variance in the pull request instead, and never re-run toward a match.
-- Recommitting an unbounded sweep on every run reaches a gigabyte of repository history inside a hundred merges. A small, committed evidence set is what a reviewer needs and what lets GitHub draw its own before-and-after comparison on the pull request.
-- `git-pr` and `git-followup` maintain a comparison comment on the pull request automatically once a case is committed, so a reviewer never has to open Files Changed to see it.
+- Write a capture into a folder named `evidence`, which the pull request comment collects from.
+- Commit a flagged case's evidence output and never the sweep, unless the project already commits the same comparison elsewhere.
+- Commit a new evidence case only after two captures with no code change between them match byte for byte.
+- Mask the smallest element holding a value that moves between runs, such as a clock, before the double capture.
+- Name the variance in the pull request when masked outputs still differ, never re-running toward a match.

package/governance/rules/ui/ux-completeness.md

@@ -10,56 +10,33 @@ paths:
 
 # UX completeness standards
 
-## Mutation feedback
+## Feedback
 
-- Every user-initiated mutation (save, delete, sync, import, export) must show inline feedback on success.
-- Feedback must be transient: auto-dismiss after 2-3 seconds without requiring user action.
-- Show inline error feedback when a mutation fails. Do not fail silently.
+- Confirm every user-initiated mutation, such as a save, delete, or import, inline on success, and show an inline error when it fails.
+- Auto-dismiss a success message only when its outcome stays visible elsewhere. Keep a message carrying the only copy of its information until dismissed (WCAG 2.2.1).
+- Show no optimistic status, such as a green dot or "connected", while unsaved edits are pending.
 
 ## Empty states
 
-- Every list, table, or collection view must handle the empty state explicitly.
-- Empty states must include a next action: a button, link, or instruction that tells the user what to do.
-- Distinguish between "nothing exists yet" (onboarding) and "nothing matches your filter" (recovery). Use different copy for each.
-- Filter-driven empty states must include a way to clear the filter (link or button).
+- Give every list, table, or collection an explicit empty state carrying a next action, such as a button or link.
+- Write different copy for "nothing exists yet" and "nothing matches your filter", and give the filtered state a way to clear the filter.
 
 ## Loading states
 
-- Every async operation visible to the user must show a loading indicator (spinner, skeleton, or disabled state).
-- Do not show stale content while new content is loading. Either show a loading state or keep the previous content with a progress indicator.
+- Show a progress indicator for any operation a person waits on for longer than about one second.
+- Mark previous content as updating while new content loads, rather than showing it unmarked as current.
 
 ## Destructive actions
 
-- Destructive actions (delete, disconnect, discard) must require confirmation before executing.
-- Confirmation UI must be dismissible via Escape in addition to a cancel button.
+- Confirm a destructive action, such as a delete, disconnect, or discard, before it runs, unless it can be undone afterward.
 
-## Inline confirmations
+## Element states
 
-- All inline confirmation rows (delete, discard, cancel) must be dismissible via Escape.
-- Confirmation labels and destructive buttons must have sufficient contrast in both light and dark modes.
+- Give every interactive element distinct hover, active, focus, and disabled styles.
+- Never flash an intermediate state, such as a light frame before a dark theme or a layout jump before data arrives. Reserve the space or settle it first.
 
-## Status indicators
+## Overflow
 
-- Status indicators (dots, badges, connection status) must reset to a neutral state when their source input changes.
-- Do not show optimistic status (green dot, "connected") while unsaved edits are pending.
-
-## State transitions
-
-- Do not flash intermediate states during transitions (e.g., white flash on theme load, layout jump before data arrives).
-- Use CSS transitions or deferred rendering to prevent visible flicker between states.
-
-## Interactive element states
-
-- All interactive elements must visually respond to hover, active, focus, and disabled states.
-- Disabled elements must use reduced opacity or muted colors and `cursor: not-allowed`.
-- Do not rely on a single state (e.g., focus only) to communicate interactivity.
-
-## Overflow and truncation
-
-- Long text in constrained containers must truncate with ellipsis, not overflow or wrap unexpectedly.
-- Truncated text must be accessible via `title` attribute or expandable interaction.
-
-## Scroll and clipping
-
-- Focus rings and interactive borders must not be clipped by parent `overflow: hidden` or `overflow: auto` containers.
-- Add padding or adjust overflow to prevent clipping on edge items in scrollable lists.
+- Truncate long text in a constrained container with an ellipsis rather than letting it overflow.
+- Expose truncated text through an expand control or full text on focus, never through a `title` tooltip alone.
+- Keep focus rings and interactive borders clear of a parent's `overflow` clipping, padding the edge items of a scrollable list.

package/package.json

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

package/scripts/core/install-check.sh

@@ -100,7 +100,7 @@ log_step "Assert scaffold"
 # 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" \
+for path in "CLAUDE.md" ".claude" "canon/context/index.md" \
   ".oxfmtrc.json" ".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

package/src/cli/help.ts

@@ -29,7 +29,6 @@ export const COMMAND_GROUPS: { title: string; rows: CommandRow[] }[] = [
       ['gov [cmd]', 'Governance rules'],
       ['tooling [cmd]', 'Tooling stacks'],
       ['claude [cmd]', 'Claude workflow'],
-      ['wiki [cmd]', 'Wiki pages'],
       ['indexes [cmd]', 'Regenerate index.md files'],
       ['docs [cmd|topic]', 'Emit toolkit reference docs'],
     ],