@erclx/canon 5.67.0 → 5.69.0

package/claude/skills/{ui-record → ui-film}/references/handoff.md

@@ -1,21 +1,22 @@
 ---
-title: UI record handoff
+title: UI film handoff
 description: What HyperFrames receives from a take, the shape of the click log and camera track, and how a composition applies the camera and draws the cursor
 ---
 
-# UI record handoff
+# UI film handoff
 
-Read at Step 5 of `ui-record`. Canon stops at the clip, and a HyperFrames composition does the rest. This file states what the composition receives and how it uses each part, so a session composing later needs nothing from the session that filmed.
+Read at Step 5 of `ui-film`. Canon stops at the clip, and a HyperFrames composition does the rest. This file states what the composition receives and how it uses each part, so a session composing later needs nothing from the session that filmed.
 
 ## What the takes folder holds
 
-`take.json` lists every beat in plan order, with the folder, the route that filmed it, and the frame count. Each beat's folder holds three files.
+`take.json` lists every beat in plan order, with the folder, the route that filmed it, and the frame count. Each beat's folder holds four files.
 
-| File          | Holds                                                                    |
-| ------------- | ------------------------------------------------------------------------ |
-| `clip.mp4`    | H.264 at 60 fps, 3840x2160 when frame stepped, 1920x1080 when screencast |
-| `log.json`    | Every move, click, typing burst, and scroll, with each target's box      |
-| `camera.json` | One camera per frame of the clip, with the cursor and the click ring     |
+| File          | Holds                                                                        |
+| ------------- | ---------------------------------------------------------------------------- |
+| `clip.mp4`    | H.264 at 60 fps, 3840x2160 when frame stepped, 1920x1080 when screencast     |
+| `log.json`    | Every move, click, typing burst, and scroll, with each target's box          |
+| `camera.json` | One camera per frame of the clip, with the cursor and the click ring         |
+| `still.jpg`   | The clip's closing frame, the check on each take, which no composition needs |
 
 Every coordinate in the log and the track is in CSS pixels of a 1920x1080 page, whatever size the clip is. Every time is in milliseconds on the clip's own clock, so frame `n` sits at `n * 1000 / 60`.
 
@@ -30,6 +31,24 @@ Each frame carries `scale`, the view's top-left `x` and `y`, the `cursor`, and `
 
 The track is final. It already carries the easing, the spring, and the hold, so a composition sets each frame's values and never tweens between them.
 
+## Where the composition lives
+
+The HyperFrames project sits in the same workspace as the takes, so one folder holds everything a video is made from.
+
+```bash
+bunx -y hyperframes init .canon/video/<slug>/composition
+```
+
+- Use `bunx` when bun is available, falling back to `npx -y hyperframes init ...` otherwise
+- Prefix the path with the main worktree root when running from a linked worktree, as `ui-film`'s write scope states
+- Read each clip from `../takes/<dir>/clip.mp4`, relative to the project, rather than copying it in
+- Leave renders in the project's `renders/` folder, which `canon records push` skips along with `takes/`, `snapshots/`, `node_modules/`, and any video file
+- An image the composition adds under `assets/`, such as a logo, is backed up with the project's source
+
+Compose from a session started at the main worktree root. From a linked worktree or an isolated background session, `Write` and `Edit` refuse every file in `composition/` and redirect to a worktree copy no later session reads, so never take that redirect.
+
+Where composing from the main root is not possible, write each file whole through the route `${CLAUDE_SKILL_DIR}/../session-worktree/references/main-root-writes.md` states.
+
 ## Applying it in a composition
 
 Load `hyperframes-core` for placing the clip and `hyperframes-keyframes` for the wrapper's transform before writing the composition.

package/claude/skills/ui-film/references/pr-clip.md

@@ -0,0 +1,84 @@
+---
+title: Pull request clip
+description: Pull request mode of ui-film, run for pr-evidence with no operator present, covering the beat choice from the checklist, the length cap, the still check that stands in for approval, the reel flag, and the push to the frames branch
+---
+
+# Pull request clip
+
+Read at the top of `ui-film` when the caller names pull request mode. `pr-evidence` is the only caller, passing the pull request number, the `url` its `canon pr local` read returned, and the checklist text.
+
+This mode films a short reel of what the checklist asks a reviewer to try, hosts it on `canon/frames`, and hands back the link or the reason it skipped.
+
+## Contents
+
+- [What changes from an ordinary run](#what-changes-from-an-ordinary-run)
+- [Choose the beats](#choose-the-beats)
+- [Film the reel](#film-the-reel)
+- [Check each still](#check-each-still)
+- [Push the reel](#push-the-reel)
+- [What goes back to the caller](#what-goes-back-to-the-caller)
+
+## What changes from an ordinary run
+
+The mode holds only while the caller names it. An ordinary run that finds a pull request in its context still stops at Step 2 for approval.
+
+- Skip Step 1's throwaway copy. Film the address the caller passed, joined to the config's `access` value, and start no server.
+- Skip Step 2's approval. The beats come from a checklist a reviewer already reads, and the still check below is the guard against posting a wrong take.
+- Skip Step 5's handoff and its output block, since the reel is the product and HyperFrames composes nothing here
+- Write inside `.canon/tmp/ui-film/pr-<number>/` at the current worktree's root in place of the video workspace, since a reel is thrown away once posted
+- Ask nothing at any step. Every stop below is a skip with a reason, since the ship chain runs this with nobody to answer.
+
+## Choose the beats
+
+Take a beat from each checklist box that asks the reviewer to click, fill, or scroll something, in checklist order, up to three beats.
+
+- Skip a box ending in `(taste)`, since no driver judges it
+- Skip a box that asks only to look at a state the page opens on, since a screenshot already shows it
+- Name each beat after its box's text, cut to the action
+- Write the plan per `${CLAUDE_SKILL_DIR}/references/take-craft.md`, finding each target on the served page rather than guessing it
+- With no box left, skip as `no-interactive-box` and film nothing
+
+Keep the whole reel at or under 12 seconds. Each beat opens and closes on a 0.6 s hold, so give each action's `wait` only what its result needs to settle.
+
+## Film the reel
+
+```bash
+canon take <url> .canon/tmp/ui-film/pr-<number>/plan.json --out .canon/tmp/ui-film/pr-<number>/takes --reel .canon/tmp/ui-film/pr-<number>/reel.webp --json
+```
+
+Branch on the record's `reason`, never on the exit code.
+
+| Record          | Route                                                              |
+| --------------- | ------------------------------------------------------------------ |
+| No `reason`     | Sum the beats' `seconds` and continue to the stills                |
+| `reel-failed`   | Skip as `reel-failed` with the record's `message`                  |
+| Any other value | Skip under that `reason`, such as `target-missing` with its `beat` |
+
+When the beats sum past 12 seconds, drop the last beat from the plan and film once more. A second run past the cap skips as `over-cap`.
+
+## Check each still
+
+Open each beat's `still.jpg`, the closing frame the record names in its `still` field, and confirm it shows the state the beat's box describes. This check replaces the operator's approval, so it runs on every reel.
+
+- A still showing the wrong state skips the reel as `wrong-state`, naming the beat and what the still shows
+- A record whose beats carry no `still` field comes from a `canon` predating the still, so skip as `no-still` rather than posting a reel nothing checked
+- Read `fallback` on each beat the way an ordinary run does. A beat filmed by screencast still joins the reel, since the reel shrinks every beat to one width.
+
+## Push the reel
+
+Stamp the pass in compact UTC and push the file:
+
+```bash
+canon pr frames <number> --reel .canon/tmp/ui-film/pr-<number>/reel.webp --pass "$(date -u +%Y%m%dT%H%M%SZ)" --json
+```
+
+- `ok`: hold the record's `link`
+- `reel-too-large`: skip as `reel-too-large`, since GitHub would not render it
+- Any other `reason`: skip under it with the record's `message`
+
+## What goes back to the caller
+
+Hand `pr-evidence` one of two things and print nothing of your own:
+
+- The `link` from the push, which it passes to `canon pr evidence --reel`
+- A skip, as the reason and a one-line message, which its report names

package/claude/skills/{ui-record → ui-film}/references/take-craft.md

@@ -5,7 +5,7 @@ description: The filming rules a take plan follows, the frame-stepping limits, a
 
 # Take craft
 
-Read at Step 3 of `ui-record`, before writing the first beat. `canon take --help` carries every step kind, the target forms, and each refusal code, so this file carries the judgment and leaves the vocabulary to the verb.
+Read at Step 3 of `ui-film`, before writing the first beat. `canon take --help` carries every step kind, the target forms, and each refusal code, so this file carries the judgment and leaves the vocabulary to the verb.
 
 ## Contents
 
@@ -57,6 +57,13 @@ A fallback films the beat again from a fresh load, replaying its setup and the s
 
 A screencast beat films in real time at 1920x1080, which goes soft at the 1.8x zoom. Tell the operator which beats ran that way.
 
+### Reading a take back
+
+Two rules hold once a beat is filmed.
+
+- A stepped still is 3840x2160 and opens at 2000 wide. Crop it for text too small to read there, with `ffmpeg -v error -y -i <dir>/still.jpg -vf crop=<w>:<h>:<x>:<y> <dir>/crop.png` on the still's own pixels.
+- Read when something happened from `log.json` and `camera.json`, both on the clip's clock, never from a clock printed in the page, which starts before the first kept frame
+
 ## Targets
 
 - Prefer a stable attribute, such as an `aria-label`, a `data-testid`, or an `id`, over a position like `:nth-child`

package/claude/skills/{ux-measure → ui-measure}/REQUIREMENT.md

@@ -1,9 +1,9 @@
 ---
-name: ux-measure
+name: ui-measure
 description: Why a rendering cost question is answered with a number against a published threshold, and why the runner is detected rather than prescribed
 ---
 
-# UX measure requirement
+# UI measure requirement
 
 ## Gap
 
@@ -29,7 +29,7 @@ A session that does start one picks a runner on the spot, takes one noisy load,
 
 ## Out of scope
 
-- Judging the interface against stated intent, and contrast, which `ux-audit` owns from the stylesheet's color values
+- Judging the interface against stated intent, and contrast, which `ui-audit` owns from the stylesheet's color values
 - Writing behavioral tests against the interface, which `test-first` and `test-craft` own
 - Network waterfall, bundle size, and accessibility, which no skill measures
 - Fixing what the reading found, which a separate change owns

package/claude/skills/{ux-measure → ui-measure}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: ux-measure
-description: Measures paint, processor, and layout cost against a running interface and reports numbers against published thresholds. Detects the project's existing browser harness rather than requiring one. Use when asked "how fast is this page", "measure the UI", "what does this cost to render", "check Core Web Vitals", or "profile the interface". Do NOT use to judge UI quality by reading source, which is `ux-audit`.
+name: ui-measure
+description: Measures paint, processor, and layout cost against a running interface and reports numbers against published thresholds. Detects the project's existing browser harness rather than requiring one. Use when asked "how fast is this page", "measure the UI", "what does this cost to render", "check Core Web Vitals", or "profile the interface". Do NOT use to judge UI quality by reading source, which is `ui-audit`.
 metadata:
   family: check
 ---
 
-# UX measure
+# UI measure
 
 Report numbers. A sentence about what the source looks like is what this exists to replace, so every finding is a reading beside the threshold it is measured against.
 
@@ -13,7 +13,7 @@ Report numbers. A sentence about what the source looks like is what this exists
 
 - If the project names no command that serves an interface and the user names no URL, stop: `❌ Nothing to serve. Name a running URL or a command that starts one.`
 - Test for a servable interface rather than source under a folder, since this measures what a browser receives and never reads the tree behind it
-- If the request is about intent, consistency, missing states, or contrast, run nothing and name `ux-audit`. That skill reads source and this one runs the interface.
+- If the request is about intent, consistency, missing states, or contrast, run nothing and name `ui-audit`. That skill reads source and this one runs the interface.
 
 ## Step 1: reach the interface
 
@@ -116,7 +116,7 @@ Report the reading and stop there. A remedy is a change with its own review, so
 
 Derive `<slug>` per `${CLAUDE_SKILL_DIR}/../git-branch/references/slug.md`. Fall back to `latest` on an empty result.
 
-- Write the full reading to `.canon/review/ux-measure-<slug>.md` at the main worktree root, resolved the way `session-worktree` does, creating the directory if needed and always overwriting
+- Write the full reading to `.canon/review/ui-measure-<slug>.md` at the main worktree root, resolved the way `session-worktree` does, creating the directory if needed and always overwriting
 - The reading is a main-root write, so it goes out as a heredoc, routed the way `session-worktree` states
 - `.canon/review/` is gitignored, so do not stage or commit the file
 
@@ -126,5 +126,5 @@ Output the summary line and the file path. Do not repeat the table in chat.
 
 ```plaintext
 3 metrics measured against <url>. <n> past threshold.
-📝 Wrote .canon/review/ux-measure-<slug>.md
+📝 Wrote .canon/review/ui-measure-<slug>.md
 ```

package/docs/agents/audits.md

@@ -79,7 +79,7 @@ An audit that finds no corpus reports `absent`, which moves neither the verdict
 | `secrets`            | `canon secrets scan`                | Credential-shaped values in the shipped tree                                       | Gates          |
 | `labels`             | `canon labels audit`                | Changed paths no row of the label map reaches                                      | Reports        |
 | `restated`           | `canon gov restated`                | Instructions `CLAUDE.md` states that a second surface states too                   | Reports        |
-| `rules`              | `canon gov audit`                   | Rules past a shape limit, and here outside-practice rules short of a source ledger | Reports        |
+| `rules`              | `canon gov audit`                   | Rules past a shape limit, and here rules short of a ledger or out of step with one | Reports        |
 | `counts`             | `canon gov counts`                  | Sentences stating a closed catalog's size that disagree with the tree              | Reports        |
 | `census`             | `canon census`                      | File count, extension breakdown, and line total                                    | Reports        |
 | `deps`               | `canon deps audit`                  | Advisories against the resolved dependencies                                       | Reports        |

package/docs/agents/migrate.md

@@ -8,22 +8,22 @@ kind: reference
 
 `canon migrate <verb>` moves a project off a retired name or layout. Each verb reports its plan and writes nothing until `--write`, takes `--json`, and, except `rename`, takes `--root`. A second run rewrites nothing, which confirms the exclusions and markers fired.
 
-| Verb               | Moves                                                                                                           |
-| ------------------ | --------------------------------------------------------------------------------------------------------------- |
-| `status`           | Nothing. It lists every migration the project still needs, in run order.                                        |
-| `rename`           | The retired `aitk` name. `--scope target` rewrites toolkit-owned folders only.                                  |
-| `skill-names`      | Plugin skills off their `claude-` and `draft-` prefixes and other retired names, with every citation            |
-| `records`          | Session records from `.claude/` to `.canon/`, with every tracked citation                                       |
-| `surface-roots`    | Records such as `context/` and `REQUIREMENTS.md`, and the stamp folder, from `.claude/` to `canon/` by `git mv` |
-| `record-tree`      | Citations inside the `.canon/` folders a session still follows, listed below the table                          |
-| `rule-layout`      | A flat installed-rule layout onto the `canon/`-wrapped one                                                      |
-| `scratch-evidence` | A folder a durable record cites out of `.tmp/`, with its citations                                              |
-| `record-layout`    | Review receipts, memory archives, feedback, renders, picks, and evidence into their current folders             |
-| `session-defaults` | The seeded session defaults into an existing `.claude/settings.json`, listed below the table                    |
+| Verb               | Moves                                                                                                                 |
+| ------------------ | --------------------------------------------------------------------------------------------------------------------- |
+| `status`           | Nothing. It lists every migration the project still needs, in run order.                                              |
+| `rename`           | The retired `aitk` name. `--scope target` rewrites toolkit-owned folders only.                                        |
+| `skill-names`      | Plugin skills off their `claude-` and `draft-` prefixes and other retired names, with every citation                  |
+| `records`          | Session records from `.claude/` to `.canon/`, with every tracked citation                                             |
+| `surface-roots`    | Records such as `context/` and `REQUIREMENTS.md`, and the stamp folder, from `.claude/` to `canon/` by `git mv`       |
+| `record-tree`      | Citations inside the `.canon/` folders a session still follows, listed below the table                                |
+| `rule-layout`      | A flat installed-rule layout onto the `canon/`-wrapped one                                                            |
+| `scratch-evidence` | A folder a durable record cites out of `.tmp/`, with its citations                                                    |
+| `record-layout`    | Review receipts, memory archives, feedback, renders, picks, evidence, and the design board into their current folders |
+| `session-defaults` | The seeded session defaults into an existing `.claude/settings.json`, listed below the table                          |
 
 `record-tree` follows citations in `diagrams`, `memory`, `plans`, `proposals`, `review`, `tasks`, and `teach`. `session-defaults` denies `Agent`, `Task`, and both merge commands, and turns auto memory off. The bullets below add detail per verb.
 
-- `skill-names` takes no `--scope`, and skips the changelog, eval transcripts, and the pointer each renamed `draft-` skill leaves at its old name
+- `skill-names` takes no `--scope`, and skips the changelog, eval transcripts, replay fixtures, and the pointer each renamed `draft-` skill leaves at its old name
 - `surface-roots` moves `context/`, `wireframes/`, `ARCHITECTURE.md`, `REQUIREMENTS.md`, `DESIGN.md`, and the stamp folder, and leaves `rules/`, `skills/`, `hooks/`, and `settings.json` in place
 - `rule-layout` classifies each flat file against the stamp as clean, edited, or unclaimed. Clean and edited files move untouched, and an unclaimed name stays.
 - `record-layout` labels each evidence folder `(pick)` or `(evidence)` in the dry run

package/docs/agents/records.md

@@ -28,6 +28,7 @@ printf '.canon/\n' >> .gitignore
 ```
 
 - `push` commits every top-level folder under `.canon/` except `tmp`, `ordinal-locks`, and `.records.git`, then pushes. New folders list under `added`.
+- `push` backs up a video workspace under `video/` without its media, skipping `takes/`, `renders/`, `snapshots/`, `node_modules/`, and any `.mp4`, `.webm`, or `.mov` file.
 - `pull` restores the folders on a new machine after the setup above. It refuses rather than overwrite records the history lacks.
 - `size` reports one row per folder, heaviest first, with file count, bytes, and growth over 7 and 30 days. After a `pull` every file reads as new.
 - `prune-tmp` lists scratch untouched for 14 days and deletes it only with `--write`. It never offers `tmp/handoff/` or `tmp/pr/poll/`.

package/docs/target/migrations.md

@@ -48,9 +48,7 @@ Run it once, ahead of `canon gov sync` or `canon gov install`.
 
 ## Rename the skill citations, once
 
-Plugin skills dropped their `claude-` prefix, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. The five per-kind drafters merged into `write-doc`, and no pointer under an old name ships. <!-- canon-keep-retired -->
-
-The seven `draft-` skills took verb-first names for what each makes. `canon migrate skill-names --write` carries a project across, and a pointer under each old name answers a typed invocation until it retires.
+Plugin skills dropped their `claude-` prefix, so `canon:claude-docs` is now `canon:context-fold`. Five drafters merged into `write-doc`, seven `draft-` skills took verb-first names, and four joined their family. No old name keeps a pointer, and `canon migrate skill-names --write` moves a project. <!-- canon-keep-retired -->
 
 | Old name           | New name                                        |
 | ------------------ | ----------------------------------------------- |
@@ -58,17 +56,21 @@ The seven `draft-` skills took verb-first names for what each makes. `canon migr
 | `draft-figure`     | `draw-figure` <!-- canon-keep-retired -->       |
 | `draft-identity`   | `design-identity` <!-- canon-keep-retired -->   |
 | `draft-slides`     | `make-deck` <!-- canon-keep-retired -->         |
-| `draft-and-pick`   | `pick-by-eye` <!-- canon-keep-retired -->       |
+| `draft-and-pick`   | `design-pick` <!-- canon-keep-retired -->       |
 | `draft-ready`      | `plan-ready` <!-- canon-keep-retired -->        |
 | `draft-screencast` | `script-screencast` <!-- canon-keep-retired --> |
+| `pick-by-eye`      | `design-pick` <!-- canon-keep-retired -->       |
+| `ui-record`        | `ui-film` <!-- canon-keep-retired -->           |
+| `ux-audit`         | `ui-audit` <!-- canon-keep-retired -->          |
+| `ux-measure`       | `ui-measure` <!-- canon-keep-retired -->        |
 
 Replace a citation of a skill with no successor by hand, or delete the sentence.
 
-- `canvas` is now `canvas-board`. The sweep rewrites only `canon:canvas` and `skills/canvas`, so replace a bare prose mention by hand. <!-- canon-keep-retired -->
-- `draft-ready` is rewritten only as `canon:draft-ready` and `skills/draft-ready`, since bare it also describes a pull request. Replace a bare mention of the skill by hand. <!-- canon-keep-retired -->
+- `canvas` is now `canvas-board`. The sweep rewrites only `canon:canvas` and `skills/canvas`, so replace a bare mention by hand. <!-- canon-keep-retired -->
+- `draft-ready` is rewritten only as `canon:draft-ready` and `skills/draft-ready`, since bare it also describes a pull request, so replace a bare mention by hand. <!-- canon-keep-retired -->
 - `design-extract` and `sketch-design` are replaced by `canon:canvas-board`. <!-- canon-keep-retired -->
-- `review-branch`, `seed-sync`, `restate-plainly`, `bash-cli-script`, `canon-operator`, and `canon-rollout` have no successor <!-- canon-keep-retired -->
-- `create-standard`, `markdown-propose`, `memory-review`, `project-commands`, `repo-metadata`, and `ux-walkthrough` have no successor <!-- canon-keep-retired -->
+- `review-branch`, `seed-sync`, `restate-plainly`, `bash-cli-script`, `canon-operator`, `canon-rollout`, and `canon-feedback-triage` have no successor <!-- canon-keep-retired -->
+- `create-standard`, `markdown-propose`, `memory-review`, `project-commands`, `repo-metadata`, `ux-walkthrough`, and `plan-ready` have no successor <!-- canon-keep-retired -->
 
 The `memory` record kind left `canon records`, so `canon records validate memory` refuses as an unknown kind and `canon records migrate` is gone.
 
@@ -134,7 +136,7 @@ From the registry the walk reports `historyUnavailable`, so check both paths by
 | `plan-groundwork` | `groundwork`, `groundwork-spikes`                             |
 | `plan-intake`     | `intake`                                                      |
 | `plan-feature`    | `plan`, `plan-lifecycle`                                      |
-| `plan-ready`      | `ready`                                                       |
+| `plan-ready`      | `ready` <!-- canon-keep-retired -->                           |
 | `write-doc`       | `requirements`, `wiki`                                        |
 | `session-map`     | `session`                                                     |
 
@@ -160,7 +162,7 @@ A reference to a retired skill takes a hand edit.
 
 - Replace a `canon:teach-workspace` reference with `canon:teach-craft` by hand, since `canon migrate skill-names` does not rewrite it <!-- canon-keep-retired -->
 - Delete a `canon:make-deck`, `canon:script-screencast`, `canon:record-screencast`, `canon:read-frames`, or `canon:video-craft` reference, since none has a successor <!-- canon-keep-retired -->
-- Delete a `canon:canvas-board` reference too. Frameboard, which `canon:pick-by-eye` drives, reads each `.canon/canvas/` folder as a project, so move a kept page under one <!-- canon-keep-retired -->
+- Delete a `canon:canvas-board` reference too. Frameboard, which `canon:design-pick` drives, reads each `.canon/canvas/` folder as a project, so move a kept page under one <!-- canon-keep-retired -->
 
 ## Move decisions out of a held architecture record, once
 

package/docs/target/projects.md

@@ -56,7 +56,7 @@ Keep the `## Scripts` table in `canon/context/development/local-loop.md` current
 Before the first feature session:
 
 1. Fill `canon/REQUIREMENTS.md` with the problem, goals, and non-goals. The seed's 600-word cap gates under `canon context audit`.
-2. For a UI project, write `canon/DESIGN.md` from the seed and name the stylesheet in its lead, or work the direction out with `canon:pick-by-eye`
+2. For a UI project, write `canon/DESIGN.md` from the seed and name the stylesheet in its lead, or work the direction out with `canon:design-pick`
 3. Optionally invoke `canon:draw-figure` for an architecture view. The Mermaid CLI downloads on first use.
 4. Start the feature loop in [AI workflow](../workflow/ai-workflow.md)
 

package/docs/target/sync.md

@@ -48,7 +48,7 @@ Add `--json` for a machine-readable report and `--exit-code` to fail CI when a t
 - Tooling dependencies: a dependency on a later major than the stack pins reads as `ahead`, and sync leaves it
 - Index regeneration: `canon indexes regen`
 
-After `canon gov sync` applies, it lists each rule it copied with its globs and how many project files match. A `ui/` rule adds a pointer to `/canon:ux-audit`. `--json` writes `{ "coverage": [{ "rule", "paths", "files", "ui" }] }` to stdout, empty when nothing was copied, with `files` null outside git. The report never changes the exit code.
+After `canon gov sync` applies, it lists each rule it copied with its globs and how many project files match. A `ui/` rule adds a pointer to `/canon:ui-audit`. `--json` writes `{ "coverage": [{ "rule", "paths", "files", "ui" }] }` to stdout, empty when nothing was copied, with `files` null outside git. The report never changes the exit code.
 
 Try a scenario from [sandbox](../../canon/context/development/sandbox.md) before syncing a real project.
 

package/docs/workflow/skill-map-on-request.md

@@ -15,11 +15,10 @@ These skills serve a request rather than a moment. With the [skill map](skill-ma
 | `canon:create-rule`     | A project rule the toolkit does not ship          |
 | `canon:create-skill`    | A new `SKILL.md`                                  |
 | `canon:write-doc`       | A new `docs/` page, context entry, or `README.md` |
-| `canon:plan-ready`      | Finished files a worker should copy               |
 | `canon:draw-figure`     | A figure or architecture view inside a doc        |
 | `canon:ci-workflow`     | A GitHub Actions workflow file                    |
 | `canon:design-identity` | A logo mark and social card                       |
-| `canon:ui-record`       | Real footage of the app for a video               |
+| `canon:ui-film`         | Real footage of the app for a video               |
 
 ## Answer a question at any point
 

package/docs/workflow/skill-map.md

@@ -24,7 +24,7 @@ Groups run in the order a project meets them. Every name `canon claude skills li
 | `canon:backlog-triage`     | The backlog needs pruning                          |
 | `canon:plan-groundwork`    | The state is unmeasured and approaches compete     |
 | `canon:decision-escalate`  | Open decisions turn on your preference             |
-| `canon:pick-by-eye`        | The call is taste, wanting candidates side by side |
+| `canon:design-pick`        | The call is taste, wanting candidates side by side |
 | `canon:task-board`         | A decided item needs a file on the board           |
 | `canon:plan-feature`       | The approach is settled and needs a plan           |
 | `canon:codebase-layout`    | A change adds a file and needs a folder            |
@@ -53,8 +53,8 @@ Groups run in the order a project meets them. Every name `canon claude skills li
 | Skill                   | When to use                                    |
 | ----------------------- | ---------------------------------------------- |
 | `canon:document-health` | Documents must answer for length and staleness |
-| `canon:ux-audit`        | To read UI source for missing states           |
-| `canon:ux-measure`      | To measure paint, processor, and layout cost   |
+| `canon:ui-audit`        | To read UI source for missing states           |
+| `canon:ui-measure`      | To measure paint, processor, and layout cost   |
 | `canon:app-drive`       | To drive a built app with the operator         |
 
 ## Ship it
@@ -100,10 +100,9 @@ Groups run in the order a project meets them. Every name `canon claude skills li
 
 ## Keep the project current with the toolkit
 
-| Skill                         | When to use                                             |
-| ----------------------------- | ------------------------------------------------------- |
-| `canon:target-check`          | In a target, to compare each domain with the toolkit    |
-| `canon:target-update`         | After a release, to catch a target up to the toolkit    |
-| `canon:document-repair`       | Rewrite a failing docs folder to the limits and gate it |
-| `canon:canon-feedback`        | The toolkit is broken, missing, or off                  |
-| `canon:canon-feedback-triage` | In the toolkit repo, to file feedback issues            |
+| Skill                   | When to use                                             |
+| ----------------------- | ------------------------------------------------------- |
+| `canon:target-check`    | In a target, to compare each domain with the toolkit    |
+| `canon:target-update`   | After a release, to catch a target up to the toolkit    |
+| `canon:document-repair` | Rewrite a failing docs folder to the limits and gate it |
+| `canon:canon-feedback`  | The toolkit is broken, missing, or off                  |

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

@@ -72,7 +72,12 @@ A close posts as `## UI review closed`. The reviewers lift the draft mark on the
 
 ## Design authoring
 
-Most projects author design in the loop above and need nothing more. Start with `canon:pick-by-eye`, which drafts candidates as frames on a [Frameboard](https://www.npmjs.com/package/frameboard) board and takes your pick, then record the pick with `canon:design-record`. `canon:design-identity` drafts a logo mark and social card the same way.
+Most projects author design in the loop above and need nothing more. Start with `canon:design-pick`, which drafts candidates as frames on a [Frameboard](https://www.npmjs.com/package/frameboard) board and takes your pick, then record the pick with `canon:design-record`. `canon:design-identity` drafts a logo mark and social card the same way.
+
+A pick round drafts on `.canon/board/` unless the project names another board in `canon/config/design.toml`.
+
+- Set `board` when your design sync reads another Frameboard board, so the picked frame lands without a redraw.
+- Leave `project` unset to keep rounds in their own `picks` project on that board.
 
 A graphical tool earns its place when design is the product, a designer owns it, and it changes more often than code. Then the tool is the source of truth, and `canon/DESIGN.md` carries a top note naming the upstream project.
 

package/governance/ledger/claude/background.md

@@ -0,0 +1,26 @@
+---
+title: Background rule ledger
+description: Decisions behind governance/rules/claude/background.md, one row per bullet
+---
+
+# Background rule ledger
+
+The rule is a core rule, so every row is a house choice rather than a citation. Each names what goes wrong without its bullet and the option the bullet beat, with the date it was decided.
+
+## Slow commands
+
+| Bullet                            | Source                                                                                                                                                                                         | Read       |
+| --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Background past about a minute    | House choice: a foreground run holds the conversation, so the operator waits on a check they could have talked over. It beat a warning hook, which would only warn and still let the run block | 2026-10-26 |
+| Name the slow kinds               | House choice: a minute is a guess made before the run, and with no cases to match a session reads a full check as quick. It beat the threshold alone                                           | 2026-10-26 |
+| Keep a seconds command foreground | House choice: each wake costs a turn, so backgrounding a quick command spends two turns where one did. It beat backgrounding every command                                                     | 2026-10-26 |
+| End the turn on one status line   | House choice: a turn that stops silently leaves the operator unable to tell a wait from a stall. It beat ending on the tool call alone                                                         | 2026-10-26 |
+| Keep working beside a server      | House choice: a dev server or a watch never exits, so a session awaiting its wake waits forever. It beat treating every background command as awaited                                          | 2026-10-26 |
+
+## Waking
+
+| Bullet                            | Source                                                                                                                                                                                | Read       |
+| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Act on the wake, never a guess    | House choice: a session guessing a command is done reads a partial output as the result. It beat checking the output file on a hunch                                                  | 2026-10-26 |
+| No sleep, poll, or scheduled wait | House choice: a foreground sleep or poll holds the conversation the rule freed, and a scheduled prompt spends a turn on every check. It beat all three as ways to wait on one command | 2026-10-26 |
+| Keep a skill's own wait           | House choice: a skill owns the verb and the timeout it waits on, such as a review-state wait, and one rule-wide wait would override it. It beat a single wait for every caller        | 2026-10-26 |

package/governance/rules/claude/background.md

@@ -0,0 +1,19 @@
+---
+description: Run a command that may take more than about a minute in the background and resume on the harness wake, so the operator keeps the conversation
+---
+
+# Background standards
+
+## Slow commands
+
+- Start a command that may run past about a minute with `run_in_background: true`, since a foreground run holds the conversation. Revisit when a foreground Bash call stops blocking the turn.
+- Treat a full check, a sandbox run, a capture or render, a build, and a wait on another session as slow.
+- Keep a command expected to finish in seconds in the foreground, since each wake costs a turn.
+- End the turn on one line naming what runs, when the next step needs that command's result.
+- Keep working beside a server or a watch the session never waits on, since it never exits and its wake never comes.
+
+## Waking
+
+- Act on the wake the harness sends when an awaited command exits, never on a guess about when it is done. Revisit when a background Bash command stops waking the session at exit.
+- Never wait with a foreground `sleep`, a foreground poll loop, or a scheduled prompt for one wait. The background run and its wake replace all three.
+- Keep a skill's own wait as the skill states it, since the skill owns the verb and the timeout it waits on.

package/governance/stacks/base.toml

@@ -12,4 +12,5 @@ rules = [
   "tasks",
   "plan",
   "markdown",
+  "background",
 ]

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/canon",
   "type": "module",
-  "version": "5.67.0",
+  "version": "5.69.0",
   "description": "Runs your agent's work and keeps its code good, on one setup for every repo.",
   "license": "MIT",
   "bin": {
@@ -25,9 +25,9 @@
     "access": "public"
   },
   "scripts": {
-    "format": "oxfmt . && prettier --write --log-level warn 'web/**/*.astro' && shfmt --write --indent 2 scripts/ tooling/ claude/",
-    "check:format": "oxfmt --check . && prettier --check --log-level warn 'web/**/*.astro' && 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 {} +",
+    "format": "oxfmt . && prettier --write --log-level warn 'web/**/*.astro' && shfmt --write --indent 2 scripts/ tooling/ claude/ src/",
+    "check:format": "oxfmt --check . && prettier --check --log-level warn 'web/**/*.astro' && shfmt --diff --indent 2 scripts/ tooling/ claude/ src/",
+    "check:shell": "find scripts tooling claude src .claude/hooks -name '*.sh' -exec shellcheck --severity=warning {} + && find .husky -maxdepth 1 -type f -exec shellcheck --severity=warning --shell=sh {} +",
     "check:lint": "oxlint --disable-nested-config --max-warnings 0",
     "check:types": "tsc --noEmit",
     "check:install": "bun scripts/core/install-check.ts",
@@ -54,7 +54,9 @@
     "axe-core": "4.14.0",
     "commander": "^13.1.0",
     "execa": "^9.5.2",
-    "playwright-core": "1.64.1"
+    "pixelmatch": "8.0.0",
+    "playwright-core": "1.64.1",
+    "pngjs": "7.0.0"
   },
   "devDependencies": {
     "@astrojs/check": "^0.9.8",
@@ -66,6 +68,7 @@
     "@testing-library/jest-dom": "^6.9.1",
     "@types/bun": "^1.2.10",
     "@types/micromatch": "^4.0.10",
+    "@types/pngjs": "6.0.5",
     "astro": "^6.1.9",
     "husky": "^9.1.7",
     "micromatch": "^4.0.8",

package/scripts/ci/install-playwright-deps.sh

@@ -0,0 +1,52 @@
+#!/usr/bin/env bash
+# Installs the Playwright system packages for the named browsers, killing an
+# attempt that outlives its bound and retrying it. A degraded apt mirror hangs
+# one connection rather than failing it, so a step timeout alone turns the
+# hang into a red check and never recovers it, while a fresh attempt usually
+# lands on a healthy backend.
+#
+# Usage: install-playwright-deps.sh [--package <spec>] <browser>...
+# Exits 0 on the first success, 2 when no browser is named, and the last
+# attempt's code when every attempt fails.
+set -e
+
+package=playwright
+if [ "$1" = "--package" ]; then
+  package=$2
+  shift 2
+fi
+
+if [ $# -eq 0 ]; then
+  echo "Usage: install-playwright-deps.sh [--package <spec>] <browser>..." >&2
+  exit 2
+fi
+
+attempts=3
+bound=${INSTALL_ATTEMPT_SECONDS:-150}
+
+# The runner image sets these, yet a stalled log shows gaps of minutes, so
+# print what apt actually reads to settle whether they took effect
+apt-config dump | grep -E '^Acquire::(Retries|http::Timeout) ' || true
+
+status=0
+for attempt in $(seq 1 "$attempts"); do
+  if [ "$attempt" -gt 1 ]; then
+    # timeout runs as the runner user, and Linux drops its signal to the root
+    # apt-get playwright spawns through sudo. sudo relays it only to its own
+    # child shell, so a root apt-get or dpkg can outlive the kill and hold the
+    # lock the next attempt needs.
+    sudo pkill -KILL -x 'apt-get|dpkg' || true
+    # A kill during unpack leaves dpkg interrupted, which refuses the next
+    # install. Its own failure must not end the loop.
+    sudo dpkg --configure -a || echo "dpkg --configure -a failed before attempt ${attempt}" >&2
+  fi
+
+  status=0
+  timeout --kill-after=10 "$bound" bunx "$package" install-deps "$@" || status=$?
+  if [ "$status" -eq 0 ]; then
+    exit 0
+  fi
+  echo "attempt ${attempt}/${attempts} failed with exit ${status}" >&2
+done
+
+exit "$status"

package/src/claude/cases/authoring.ts

@@ -26,8 +26,8 @@ export const AUTHORING_CASES: readonly SkillCase[] = [
   },
   {
     prompt:
-      'I already wrote the finished skill files, package them as a ready folder with a plan and a task for a worker to copy.',
-    expect: 'plan-ready',
+      'I already wrote the finished wording for a small new reference file, put it in a plan so a worker lands it exactly as written.',
+    expect: 'plan-feature',
   },
   {
     prompt: 'This project has no README.md at all, write one from scratch.',

package/src/claude/cases/misc.ts

@@ -10,7 +10,7 @@ export const MISC_CASES: readonly SkillCase[] = [
   {
     prompt:
       'Show me a few different treatments for this callout so I can pick one by looking.',
-    expect: 'pick-by-eye',
+    expect: 'design-pick',
   },
   {
     prompt:

package/src/claude/cases/setup.ts

@@ -54,11 +54,6 @@ export const SETUP_CASES: readonly SkillCase[] = [
       "Whatever the right toolkit command is, get this project's rules installed.",
     expect: 'target-setup',
   },
-  {
-    prompt:
-      'File the open feedback issues on the toolkit repo into an intake folder.',
-    expect: 'canon-feedback-triage',
-  },
   // This answers one fixed question across a fixed domain list and repairs
   // nothing, which is what separates it from the setup skill above.
   {