@erclx/canon 5.68.0 → 5.69.0

package/claude/skills/plan-feature/references/plan.md

@@ -75,8 +75,9 @@ The document opens with `# Feature: <short title>` and one paragraph stating wha
 | `## Current behavior`  | each command run against the thing being changed and what it showed         | When the change touches something that runs       |
 | `## Constraints`       | durable rules the work must respect                                         | When supplied                                     |
 | `## Files to touch`    | each file with a one-line reason                                            | Always                                            |
-| `## Verbatim`          | settled wording that lands unchanged in an existing file, one H3 per block  | When wording is settled                           |
+| `## Verbatim`          | settled wording that lands unchanged in a file, one H3 per block            | When wording is settled                           |
 | `## Design references` | the tracked design folders the change builds against, each with its surface | When Files to touch names a rendered-surface file |
+| `## Reference images`  | the untracked images the plan was shaped against, each from the main root   | When an image shaped the plan                     |
 | `## Verification`      | the test or command that proves each outcome                                | Always                                            |
 | `## Risks`             | conflicts, coupling, and the tricky spots                                   | Always                                            |
 | `## Review focus`      | the inputs or states that would break the change, for the reviewer          | Always                                            |
@@ -166,22 +167,24 @@ Re-test a stamped constraint before honoring it, fetching and scoping the log in
 git fetch origin main --quiet && git log <commit>..origin/main --oneline -- <the paths the constraint names>
 ```
 
-### Fan-in and ready constraints
+### Fan-in constraints
 
 A batch in a fan-in set declares its side in a constraint bullet, ``Fan-in member of `feature-<integrator>` `` on a member and ``Fans in `feature-<a>`, `feature-<b>` `` on the integrator. `batches.md` holds when to fan in, and `canon records validate plans` reports `fan-in-unmatched` for a set whose two sides disagree.
 
-A constraint naming a `.canon/ready/` folder is a third shape beside the hold and the shared path. It makes that folder's files the verbatim source for the paths this plan's `## Files to touch` lists, per `ready.md`, so the executing session copies those paths rather than authoring them.
-
 ### Verbatim
 
-A `## Verbatim` section carries wording someone settled, landing in an existing file exactly as written. Wording the planner only proposes stays a `- Suggested:` question, and a whole new file goes in the ready folder per `ready.md`, so the two never describe the same file.
+A `## Verbatim` section carries wording someone settled, landing in a file exactly as written. Wording the planner only proposes stays a `- Suggested:` question, so the two never describe the same file.
 
 - Give each block an H3 naming it, then a lead sentence with the action, the full path, and the anchor, then a fenced `text` block holding the wording
-- Name the action as Add, Insert, or Replace. A Replace quotes the old line in the lead's code span.
+- Name the action as Add, Insert, Replace, or Create. A Replace quotes the old line in the lead's code span.
 - Write the block as the project's formatter leaves it, since a formatter that re-pads a table row or rewraps a line makes the grep fail on correct text
 - Name the outcome in a grep bullet and put a command past 200 characters in a fenced `bash` block under it, since `S4` reports a longer bullet
 - Give each block one `## Verification` bullet running `grep -cF -e` on its whole first line against its file, so a reworded line fails a check the reviewer already runs.
 
+A Create block makes a new file, so its lead names a path that does not exist yet and no anchor. Its grep bullet takes the first distinctive line, such as the `title:` line or the H1, since a markdown file opens on `---` and that line matches any file with frontmatter.
+
+Keep a Create block to 80 lines. A longer new file goes in `## Files to touch` for the executing session to write, since a plan carrying a whole skill body costs every session that reads it.
+
 ### Design references
 
 A plan whose `## Files to touch` names a rendered-surface file (`.tsx`, `.jsx`, `.astro`, `.vue`, `.svelte`, `.html`, or `.css`) carries this section. It tells the building session which accepted design to open before it writes a line.
@@ -191,6 +194,14 @@ A plan whose `## Files to touch` names a rendered-surface file (`.tsx`, `.jsx`,
 - Cite a tracked folder only, since the building session opens its light and dark images and its frame HTML from the working tree
 - `canon records validate plans` reports `section-missing` for a plan that names a rendered-surface file and omits the section
 
+### Reference images
+
+A plan shaped against an image no tracked folder holds carries this section, such as drive evidence, an image in an intake item, or a design board frame. It tells the building session which images to open before its first edit, and it stays apart from `## Design references`, which cites tracked folders alone.
+
+- Give each entry an image path and what the image shows, as one bullet
+- Write each path from the main worktree root, since these images are gitignored and a linked worktree holds no copy. A path relative to a linked worktree resolves nowhere.
+- Leave the section out when no image shaped the plan. It is optional, and `canon records validate plans` reports nothing on a plan without it.
+
 ### Verification
 
 Every outcome reaches the review with its proof named.
@@ -325,6 +336,10 @@ Add as <where> in `<path/to/file>`, after <anchor>.
 
 - `canon/design/<surface>/`: <the surface it governs>
 
+## Reference images
+
+- `.canon/intake/<nn>-<slug>/evidence/<name>.png`: <what the image shows>
+
 ## Verification
 
 ### <Outcome group>

package/claude/skills/plan-groundwork/SKILL.md

@@ -37,7 +37,7 @@ Write only inside `.canon/groundwork/<nn>-<slug>/`. A feature plan, source chang
 
 What a spike produces stays inside the track, under `.canon/groundwork/<nn>-<slug>/evidence/`, which the first rule already permits. Mode detection matches only top-level entries, so a nested folder cannot be mistaken for a track, and scratch holds only what can be deleted without loss.
 
-A `pick-by-eye` run invoked from inside a live track follows its own branch for this. It writes its renders to `evidence/` here, and drafts its candidates as pages on the Frameboard board at `.canon/canvas/` that its close deletes.
+A `design-pick` run invoked from inside a live track follows its own branch for this. It writes its renders to `evidence/` here, and drafts its candidates as pages on the Frameboard board `design-pick` resolves, where its close removes the round. On a board `canon/config/design.toml` names, the close keeps the picked page.
 
 ### Reading and backing
 

package/claude/skills/pr-evidence/references/evidence.md

@@ -63,9 +63,9 @@ canon pr evidence <number> --check --json
 - Skip filming when the record's `reel.head` is a prefix of the `tip` that `canon pr head <number> --json` reports, since the posted reel already shows this head
 - With no checklist from either source, skip silently, since nothing names an interaction to film
 
-Invoke `canon:ui-record` in pull request mode, passing the number, the local `url`, and the checklist. It films, checks each beat's closing still, pushes the reel to `canon/frames`, and hands back a `link` or a skip reason.
+Invoke `canon:ui-film` in pull request mode, passing the number, the local `url`, and the checklist. It films, checks each beat's closing still, pushes the reel to `canon/frames`, and hands back a `link` or a skip reason.
 
-Report it rather than proceeding silently when `canon:ui-record` does not resolve, and post the evidence without a reel.
+Report it rather than proceeding silently when `canon:ui-film` does not resolve, and post the evidence without a reel.
 
 - Hold a `link` for the evidence step, which embeds it under the addresses
 - Hold a skip's reason and message for the closing report. A skip never stops the chain, and a reel already on the comment carries forward under the older head it names.

package/claude/skills/role-orchestrator/references/orchestrator-launch.md

@@ -117,7 +117,7 @@ No branch and no worktree exist here and none is created. A planner writes one g
 claude --bg --model <model> -n "planner-<project>-<slug>" "Run /canon:role-planner, then /canon:plan-feature <task>. Your controller is the session whose sessionId is <dispatcher-id>. Resolve its current name from that id through canon sessions list --json, which carries sessionId per row, at the moment you send, and never resolve an addressee by name prefix. Message it when the plan lands, carrying the path and what the task file got wrong, and message it again if you stop on a question."
 ```
 
-`<task>` is the row's task file path and `<slug>` the slug its plan will take, resolved off the row. `<dispatcher-id>`, `<model>`, and `<project>` resolve as above, and the prefix reads `planner-` because it marks the role of the session it names.
+`<task>` is the row's task file path and `<slug>` the slug its plan will take, resolved off the row. `<dispatcher-id>`, `<model>`, and `<project>` resolve as above, and the prefix reads `planner-` because it marks the role of the session it names. Then wait per `orchestrator-planning-wait.md`.
 
 ### Which checks bind
 
@@ -131,9 +131,9 @@ What a planning dispatch owes instead is the reverse reading, since a row planne
 
 ### One row per dispatch
 
-A session reused across a batch pays the context load once and ages its picture of the tree while it works, which is why the in-flight read sits on the task rather than the batch. One that compacts mid-batch loses the reasoning behind its earlier plans with nothing reporting it.
+A reused session pays the context load once and ages its picture of the tree, which is why the in-flight read sits on each row. One that compacts loses the reasoning behind its earlier plans unreported, so `role-planner` stops it when the operator ends it or a compaction nears.
 
-Cap a reused session where the saving is worth it and say what the cap was.
+Hold all planning of a row any talk session has said by message it is planning, a drive session included, whether by a launch or by `plan-feature` here, unless the operator asks for a cold planner. That session holds what the operator said about the row, and plans a filed row only once it is named back to it.
 
 ## Dispatch a talk session
 

package/claude/skills/role-orchestrator/references/orchestrator-parked.md

@@ -95,7 +95,7 @@ A local formatter removing the shape on contact says nothing about a target runn
 
 ## The plan half
 
-Plan what the pass clears, and any `## Needs a plan` row whose only blocker is the missing plan. This pass runs while workers build and the session is idle, when planning costs the critical path nothing, and a row cleared with no plan is looked at again next pass.
+Plan what the pass clears, and any `## Needs a plan` row whose only blocker is the missing plan, skipping a row a talk session holds per `orchestrator-launch.md`. This pass runs while workers build and the session is idle, when planning costs the critical path nothing, and a row cleared with no plan is looked at again next pass.
 
 - Run `plan-feature` for each, carrying the constraint per in-flight track that `## The loop` in `role-orchestrator` requires
 - Verify each plan against the tree the way that step does, since several branches are already changing it

package/claude/skills/role-orchestrator/references/orchestrator-planning-wait.md

@@ -0,0 +1,24 @@
+---
+title: Orchestrator planning wait
+description: How the orchestrator waits in the background on a row whose plan a planner is still writing, through canon tasks launchable, and how it branches on the record the wait ends on
+---
+
+A row whose plan a planner is still writing has nothing to dispatch yet. Run the wait in the background rather than grepping the task file on a loop, and act on the wake:
+
+```bash
+canon tasks launchable <task> --wait --json
+```
+
+The verb resolves the task's `Plan:` line and runs the `plan-answers` gate on the plan it names, re-reading every 30 seconds for up to 1800 seconds by default. It keys on the line rather than the plan file. A planner links a plan only after it validates, so a half-written plan never wakes the loop.
+
+## Branch on the record
+
+Branch on the record's `reason` rather than on the exit code, which a shell function wrapping `canon` can flatten to zero.
+
+- `launchable`: the plan waits on nobody, so run `${CLAUDE_SKILL_DIR}/references/orchestrator-dispatch.md` from the candidate on, since the wait never reads the branch or the conflict check
+- `timeout`: read `plan` and `open` off the last reading, then act on which one held the row
+  - No `plan` means nothing was linked in time, so check the planner is still live and re-arm the wait
+  - A non-empty `open` names the questions holding the row, so report each label and reason to the operator, then re-arm the wait
+- A refusal such as `several-plans`, `archived`, or `no-match` means the row cannot launch as it stands, so name the reason and fall back to the human
+
+A one-shot read without `--wait` reports `reason: unlinked`, `open`, or `launchable` at once. It suits a pass that only needs the row's state now.

package/claude/skills/role-planner/SKILL.md

@@ -86,10 +86,11 @@ Each finding in that file opens with the bold source-and-date label that `${CLAU
 
 ## The channel
 
-The controlling session cannot watch this one read, so two messages are owed and nothing else.
+The controlling session cannot watch this one read, so the messages below are owed and nothing else.
 
 - Announce the record as the file lands, carrying its path and what the task file got wrong. Write no summary beside it, which is a second account of a document the reader is about to open.
 - Send a block out as a message before it becomes an interactive prompt.
+- Name the handed rows still unplanned when a reused session stops under `## Lifetime`
 - Send nothing on progress, which rebuilds on this side the poll the announcement retires on the other
 
 ### Addressing
@@ -120,5 +121,6 @@ The operator being present is an assumption the launch carries. A talk planner w
 ## Lifetime
 
 - The role runs from the launch to the record landing, and the operator closes a talk session. A session handed a second row works it under the same role and reads the tree again for it.
-- A reused session's picture of the tree ages, and it nears a compaction that silently drops the reasoning behind its earlier records. Cap a reused session rather than letting it run the board.
+- A reused session's picture of the tree ages, and a compaction silently drops the reasoning behind its earlier records
+- Run the in-flight read again before each handed row, and stop when the operator ends the session or a compaction nears, telling the controller which rows are still unplanned
 - Treat this body as possibly older than the branch under it. A plugin skill loads from the marketplace cache rather than from the working tree.

package/claude/skills/role-worker/SKILL.md

@@ -18,17 +18,16 @@ This body states the role, the boundaries, and the channel, and starts no step o
 
 ## Where the session stands
 
-- Resolve `.canon/plans/`, `.canon/tasks/`, `.canon/review/`, and `.canon/ready/` at the main worktree root, never the linked worktree. Being gitignored, they are absent there rather than empty.
+- Resolve `.canon/plans/`, `.canon/tasks/`, and `.canon/review/` at the main worktree root, never the linked worktree. Being gitignored, they are absent there rather than empty.
 - Report a plan that fails to resolve as unreadable from here, naming the main-root path. Reporting the task as having no plan is wrong about the world, and a reader cannot tell the two apart.
 - Build the plan the launch named. Never write a second one when the path fails to resolve, since a row citing a plan already has one.
 - Load `ui-craft` before editing a rendered surface, pointer rule or not
 - Keep a task list from launch, one item per slice, and tick each as its slice lands. Skip it on a host that offers no list tool, since the list is for the operator watching and not a gate.
 
-### Ready folders and the draft mark
+### The draft mark
 
-A ready folder and the draft mark each carry work another session already did, so this one preserves both.
+The draft mark holds the merge until the reviews close, so this session preserves it.
 
-- Copy a ready folder's files verbatim to the paths its plan's `**Constraints:**` block names, editing only what the gate or the overview's list requires, since a rewrite discards the handoff
 - The ship chain marks the pull request a draft, and only `canon pr lift` or the operator un-marks it
 - Report a flag reading ready once and leave it. It passed every gate the verb reads or a person readied it, which GitHub requires before a merge, so re-drafting fights them.
 - Leave the lift to the reviewers, who run `canon pr lift` on their close, with the controlling session as fallback
@@ -53,9 +52,9 @@ Run `canon pr drive-copy --json` before starting `dev`. On `copied`, start it wi
 
 A hand-run `git-ship` or `git-pr` starts no server, since only a worker has a lifetime to own one.
 
-### Building against a design reference
+### Building against design references and images
 
-A plan carrying a `**Design references:**` section names the accepted design for the surface it changes. Open it before building, since the build matches it and a worker that reads the dark image alone ships a light theme nobody saw.
+A plan's `## Design references` names the accepted design per surface, and `## Reference images` names images it was shaped against by main-root path. Either can appear alone. Open both before building, since a worker reading the dark image alone ships a light theme nobody saw.
 
 - Open each cited folder's light and dark images and its frame HTML before the first edit to that surface
 - Take sizes, spacing, and colors from the frame HTML rather than from the image

package/claude/skills/task-board/references/tasks.md

@@ -141,7 +141,7 @@ A task with no origin is lost context or work nobody decided to do. The reverse
 
 - Write the path relative to `.canon/tasks/`, as `../plans/`, `../groundwork/`, and `../intake/`. A path from the project root resolves to nothing in an editor rooted there.
 - `Issue:` stays a bare `#NNN`, since a full URL writes the remote into a gitignored file. Several issues list comma-separated, each getting a `git-pr` closing line.
-- `Ready:` links `../ready/<nn>-<slug>/`, the folder the plan copies from, only when it exists. `canon tasks archive` reads it to move the folder, falling back to a path in the plan.
+- `Ready:` is a line older tasks carry, linking `../ready/<nn>-<slug>/`. No new task gains one, and `canon tasks archive` still reads it to move and retarget the folder.
 
 ### The `Plan:` line
 

package/claude/skills/task-complete/references/receipt-sweep.md

@@ -37,7 +37,7 @@ A branch report is read once, by the session addressing it. The durable record i
 
 ### What stays
 
-Do not sweep `ux-audit-*.md` or `ux-measure-*.md`, which are standalone deliverables. They sit at `.canon/review/` itself rather than under a producer folder, so the glob never reaches them.
+Do not sweep `ui-audit-*.md` or `ui-measure-*.md`, which are standalone deliverables. They sit at `.canon/review/` itself rather than under a producer folder, so the glob never reaches them.
 
 Output one line per file swept:
 

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

@@ -1,9 +1,9 @@
 ---
-name: ux-audit
+name: ui-audit
 description: Why UI roughness is reported against stated intent rather than taste, and why the audit observes without fixing
 ---
 
-# UX audit requirement
+# UI audit requirement
 
 ## Gap
 
@@ -33,4 +33,4 @@ The pass slides into fixing what it finds, and then the audit and the change lan
 - Feature planning, which `plan-feature` owns
 - Verifying one specific change, which `ui-checklist` owns
 - Defining the intent it audits against, which the design document owns
-- Measuring what a running interface costs to paint, block, or shift, which `ux-measure` owns, while contrast stays here as two color values off the stylesheet
+- Measuring what a running interface costs to paint, block, or shift, which `ui-measure` owns, while contrast stays here as two color values off the stylesheet

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

@@ -1,16 +1,16 @@
 ---
-name: ux-audit
-description: Audits the current UI for incomplete, inconsistent, or confusing patterns. Reads DESIGN.md for intent, scans UI files, and outputs observations grouped by surface. Use when asked "audit the UX", "audit the UI", "UX audit", or "find UI roughness". Do NOT use for new feature planning or code changes, and do NOT use to measure what a running interface costs to paint, which is `ux-measure`.
+name: ui-audit
+description: Audits the current UI for incomplete, inconsistent, or confusing patterns. Reads DESIGN.md for intent, scans UI files, and outputs observations grouped by surface. Use when asked "audit the UX", "audit the UI", "UX audit", or "find UI roughness". Do NOT use for new feature planning or code changes, and do NOT use to measure what a running interface costs to paint, which is `ui-measure`.
 metadata:
   family: check
 ---
 
-# UX audit
+# UI audit
 
 ## Guards
 
 - If no UI files exist in the project (no JSX, TSX, Vue, Svelte, or HTML under `src/`), stop: `❌ No UI surfaces found to audit.`
-- If the request asks what the interface costs to paint, block, or shift at runtime, run nothing and name `ux-measure`, since this skill reads source and reaches no number a browser produces
+- If the request asks what the interface costs to paint, block, or shift at runtime, run nothing and name `ui-measure`, since this skill reads source and reaches no number a browser produces
 - Contrast is the exception and stays here, since two color values in the stylesheet's custom properties compute it, and the design document's lead names that stylesheet
 
 ## Step 1: read context
@@ -65,7 +65,7 @@ If nothing is wrong, use: `✅ No observations.`
 
 Derive `<slug>` per `${CLAUDE_SKILL_DIR}/../git-branch/references/slug.md`. Fall back to `latest` on an empty result.
 
-- Write the full report to `.canon/review/ux-audit-<slug>.md` at the main worktree root, resolved the way `session-worktree` does, creating the directory if needed and always overwriting
+- Write the full report to `.canon/review/ui-audit-<slug>.md` at the main worktree root, resolved the way `session-worktree` does, creating the directory if needed and always overwriting
 - The report is a main-root write, so it goes out as a heredoc, routed the way `session-worktree` states
 - With no observations, write `✅ No observations.` to the file with a timestamp
 - `.canon/review/` is gitignored, so do not stage or commit the file
@@ -76,7 +76,7 @@ Output only the summary line and the file path. Do not repeat the full report in
 
 ```plaintext
 X observations across N surfaces.
-📝 Wrote .canon/review/ux-audit-<slug>.md
+📝 Wrote .canon/review/ui-audit-<slug>.md
 ```
 
-If no observations: `✅ No observations. Wrote .canon/review/ux-audit-<slug>.md`
+If no observations: `✅ No observations. Wrote .canon/review/ui-audit-<slug>.md`

package/claude/skills/ui-checklist/REQUIREMENT.md

@@ -28,7 +28,7 @@ A file under a gitignored folder is unreadable to a pull request reviewer, and a
 
 ## Out of scope
 
-- Judging whether the UI is any good, which `ux-audit` owns
+- Judging whether the UI is any good, which `ui-audit` owns
 - The rules for choosing a test layer, which `test-craft` owns
 - Writing the test itself, which `test-first` owns
 - Posting the checklist, which `pr-evidence` owns as the sole consumer of the handoff file

package/claude/skills/ui-craft/SKILL.md

@@ -40,5 +40,5 @@ Read `${CLAUDE_SKILL_DIR}/references/adopted.md` only when extending this guidan
 - How a surface looks, being the layer order, the coherence locks, and the defaults a model reaches for: `design-taste`
 - The accepted designs under the design folder and how a reference lands there: `design-record`
 - The visual checklist a reviewer reads beside the screenshots: `ui-checklist`
-- Reading source for roughness a rule does not state: `ux-audit`
+- Reading source for roughness a rule does not state: `ui-audit`
 - Prose on the surface beyond its interface copy: the `write-human` skill

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

@@ -1,9 +1,9 @@
 ---
-name: ui-record
+name: ui-film
 description: Why recording a web app runs from beats the operator approved, one take per action, and stops at the clip a HyperFrames composition reads
 ---
 
-# UI record requirement
+# UI film requirement
 
 ## Gap
 

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

@@ -1,11 +1,11 @@
 ---
-name: ui-record
+name: ui-film
 description: Records real footage of a project's own web app for a video. Drafts a plain beat list from the ask, a HyperFrames storyboard, or a `ui-checklist`, gets the operator's approval, writes the take plan, films each beat through `canon take` as a sharp 4K clip with a click log and a per-frame camera track, and hands the set to HyperFrames to compose. Use when asked to "record the app", "film a demo of this feature", "get footage for the launch video", "record a clip for the pull request", or "shoot the takes for this storyboard". Do NOT use to compose, caption, or render the video, which HyperFrames owns, to drive a pull request's checklist, which is `review-ui`, or to drive the app looking for defects, which is `app-drive`.
 metadata:
   family: generate
 ---
 
-# UI record
+# UI film
 
 A take is real footage of the app doing one thing, filmed so the edit can zoom into it without going soft. This skill turns an ask into beats the operator approves in plain words, films one take per beat, and hands HyperFrames the clips, the logs, and the camera tracks. Canon renders nothing past the clip.
 

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

@@ -1,11 +1,11 @@
 ---
-title: UI record config
+title: UI film config
 description: What a take reads from canon/config/app-drive.toml, the access key it adds, and what to ask when the file is absent
 ---
 
-# UI record config
+# UI film config
 
-Read at Step 1 of `ui-record`. A take shares its project's drive config at `canon/config/app-drive.toml` rather than keeping a second file, since both build and serve the same app. The skill reads the file and never writes it.
+Read at Step 1 of `ui-film`. A take shares its project's drive config at `canon/config/app-drive.toml` rather than keeping a second file, since both build and serve the same app. The skill reads the file and never writes it.
 
 ```toml
 launch = "bun install --frozen-lockfile && bun run build && PREVIEW_PORT=4530 bun run preview"

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

@@ -1,11 +1,11 @@
 ---
-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
 
@@ -40,7 +40,7 @@ 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-record`'s write scope states
+- 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

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

@@ -1,11 +1,11 @@
 ---
 title: Pull request clip
-description: Pull request mode of ui-record, 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
+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-record` 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.
+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.
 
@@ -25,7 +25,7 @@ The mode holds only while the caller names it. An ordinary run that finds a pull
 - 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-record/pr-<number>/` at the current worktree's root in place of the video workspace, since a reel is thrown away once posted
+- 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
@@ -43,7 +43,7 @@ Keep the whole reel at or under 12 seconds. Each beat opens and closes on a 0.6
 ## Film the reel
 
 ```bash
-canon take <url> .canon/tmp/ui-record/pr-<number>/plan.json --out .canon/tmp/ui-record/pr-<number>/takes --reel .canon/tmp/ui-record/pr-<number>/reel.webp --json
+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.
@@ -69,7 +69,7 @@ Open each beat's `still.jpg`, the closing frame the record names in its `still`
 Stamp the pass in compact UTC and push the file:
 
 ```bash
-canon pr frames <number> --reel .canon/tmp/ui-record/pr-<number>/reel.webp --pass "$(date -u +%Y%m%dT%H%M%SZ)" --json
+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`

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
 

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/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