@erclx/canon 5.68.0 → 5.70.0

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-craft/references/copy.md

@@ -3,7 +3,10 @@
 ## Punctuation
 
 - Write no em dash (`—`) or semicolon in rendered copy. Use a comma or a period, or restructure the sentence.
-- Add no trailing punctuation to a button label or a short action string.
+- Add no trailing period, colon, or exclamation mark to a heading, label, link, button, nav item, caption, status, or one-sentence tagline. Keep the question mark a question needs.
+- Rewrite a two-sentence tagline as one sentence rather than keeping a period inside it.
+- End a one-sentence error or validation message with no period, such as `Enter an email address`.
+- Keep end punctuation on body copy, multi-sentence messages, and quoted text, which a reader reads as prose.
 
 ## Button copy
 

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
 
@@ -19,13 +19,15 @@ A session that does reach `canon take` writes the plan from its own reading of t
 - The session looks at a still of each take before handing it off or posting it as a pull request reel, and names a beat that fell back to the real-time route
 - HyperFrames receives the takes with what it needs to apply the camera and draw the cursor
 
-One video keeps its plan, takes, and composition in one workspace the operator can find, backed up without its media.
+One video keeps its plan, takes, and composition in one workspace the operator can find, backed up without its media. A README there records how to re-film the takes, and the composing session adds how to re-render.
+
+A session composing the takes finds the footage guidance HyperFrames lacks, being captions over app UI, other shapes, a README loop, and sped-up clips.
 
 ## Must not
 
 - Film before the operator approves, or with nobody there to approve, unless `pr-evidence` named pull request mode, whose still check stands in for the approval
 - Write a tracked file, the config included
-- Compose, caption, or render the video
+- Run the composition or render the video, or write any composition file
 - Trigger on anything but a request to record or film the app
 - Stay when no caller besides the operator reaches it, such as a pull request clip through `pr-evidence`, which a review checks
 

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.
 
@@ -71,12 +71,15 @@ canon take <url> .canon/video/<slug>/plan.json --out .canon/video/<slug>/takes -
 
 Branch on the record's `reason`, never on the exit code, which a shell function wrapping `canon` can flatten to zero.
 
-| Record               | Route                                                                                   |
-| -------------------- | --------------------------------------------------------------------------------------- |
-| No `reason`          | Continue to the stills                                                                  |
-| `target-missing`     | Find the target the record's `beat` names on the page, fix the plan, and film once more |
-| `server-unreachable` | Restart the server from Step 1 and film once more                                       |
-| Any other `reason`   | Report the `reason` and `message` to the operator and stop, since each is a setup step  |
+| Record                           | Route                                                                                                              |
+| -------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
+| No `reason`                      | Continue to the stills                                                                                             |
+| `target-missing` with `fallback` | Check the access before the selector, per the note below the table                                                 |
+| `target-missing`                 | Open the record's `still`, find the target the record's `beat` names on the page, fix the plan, and film once more |
+| `server-unreachable`             | Restart the server from Step 1 and film once more                                                                  |
+| Any other `reason`               | Report the `reason` and `message` to the operator and stop, since each is a setup step                             |
+
+A refusal carrying `fallback` means the screencast opened the address a second time, so a single-use link was spent before the step ran. Read `${CLAUDE_SKILL_DIR}/references/config.md` for the access the take opens with, and fix that before touching the target.
 
 A second refusal of the same kind stops the run and reports both records.
 
@@ -85,30 +88,40 @@ A second refusal of the same kind stops the run and reports both records.
 Open each beat's `takes/<dir>/still.jpg` before handing off, since a clip can film the wrong state cleanly. The verb writes it from the clip's closing frame, where the action's result shows.
 
 - Say what each still shows beside the beat it belongs to
-- Report a beat the record marks with `fallback` as filmed in real time at 1080p, which goes soft under a zoom, and offer to re-film it with the beat's input simplified
+- Report a beat the record marks with `fallback` as filmed in real time at 1080p, whose zoom stops near 1.35x rather than 1.8x, and offer to re-film it with the beat's input simplified
 
 ## Step 5: hand off
 
-Read `${CLAUDE_SKILL_DIR}/references/handoff.md` on reaching this step. It sets what HyperFrames receives and how a composition applies the camera track and draws the cursor.
+Read `${CLAUDE_SKILL_DIR}/references/handoff.md` on reaching this step, for what HyperFrames receives, where each composition lives, and how one applies the camera track and draws the cursor. Read `${CLAUDE_SKILL_DIR}/references/compose-craft.md` beside it, for the footage rules the HyperFrames skills lack.
 
 Close the throwaway copy per `isolate.md` when Step 1 built one, after the stills are read.
 
+### Write the workspace README
+
+Write the filming half of `.canon/video/<slug>/README.md`, so a later session can re-film without this one. The composing session adds the re-render half under its own heading, as `compose-craft.md` states.
+
+- Name what was filmed, beat by beat, and how to re-film each one with `canon take`
+- Say where each folder came from, being the plan, the takes, and the config keys the take read, with `access` described rather than copied when it carries a token
+- Write the file whole through the main-root route when none exists, with the filming half under a `## Filming` heading
+- Add a `## Filming` section when a README is already there, reading the file and writing it back whole, and never overwrite what another session wrote
+- Replace an existing `## Filming` section in place on a re-film, since the commands in it changed
+
 ## Output
 
 Emit the takes folder, one line per beat, and the next step.
 
 ```plaintext
-🎬 Filmed .canon/video/<slug>/takes/
+🎬 Filmed .canon/video/<slug>/takes/, re-film notes in .canon/video/<slug>/README.md
 
 01-open-the-kit  step  4.2 s  the board's first page with its frames filled in
 02-search-for-color  screencast (fallback)  3.8 s  the page list narrowed to two results
 
-Next: load hyperframes to compose, reading takes/take.json and the handoff notes
+Next: load hyperframes to compose, reading takes/take.json, handoff.md, and compose-craft.md
 ```
 
 ## What this delegates
 
 - `app-drive`'s `isolate.md` owns the throwaway copy and its close
 - `hyperframes-creative`'s story spine owns what a beat says to a viewer
-- `hyperframes` and its sibling skills own composing, captioning, and rendering the video
+- `hyperframes` and its sibling skills own composing, captioning, and rendering the video, and `compose-craft.md` adds only what app footage changes about their advice
 - `review-ui` owns driving a pull request's checklist

package/claude/skills/ui-film/references/compose-craft.md

@@ -0,0 +1,81 @@
+---
+title: Compose craft
+description: The footage rules a session composing ui-film takes follows where the HyperFrames skills say nothing, being captions over app UI, other shapes, the README loop, sped-up clips, storyboard headings, and the workspace README
+---
+
+# Compose craft
+
+Read at Step 5 of `ui-film`, and by the session that composes the takes, which the handoff's next line points here. HyperFrames owns composing, captioning, and rendering, so this file carries only what app footage changes about its advice and restates none of it.
+
+Each rule states the principle. Where a number appears, it is the case measured on one app's launch film, not a law for the next app.
+
+## Contents
+
+- [Captions over app footage](#captions-over-app-footage)
+- [Other shapes](#other-shapes)
+- [The README loop](#the-readme-loop)
+- [Sped-up clips](#sped-up-clips)
+- [Storyboard headings](#storyboard-headings)
+- [The workspace README](#the-workspace-readme)
+- [Sources](#sources)
+
+## Captions over app footage
+
+HyperFrames' caption guide places a landscape caption 80 to 120 px from the bottom and keeps it off a speaker's face. App footage has no speaker, and its bottom edge is often a toolbar where the beat's click lands.
+
+- Pick one caption position for the whole film, clear of the app's chrome where actions land, and keep every caption there, since a caption that moves between beats makes the viewer hunt for it
+- Back a caption over bright UI with the scrim HyperFrames' caption guide sizes to the text
+- Snapshot each caption's moment, and move a caption only when it covers its own beat's action
+- Write caption text by the interface copy rules in `ui-craft`'s `copy.md`, so a caption ends with no period
+
+## Other shapes
+
+Cut a square or vertical version only when the operator asks for one. A film with one shape needs nothing from this section, and the vertical caption band and safe boxes stay with HyperFrames' frame presets.
+
+- Start each shape as its own HyperFrames project, as `hyperframes-studio` states for a different aspect, in the workspace folder `handoff.md` names for it
+- Frame the shape by cropping a window of the page at 1x, never by scaling the 16:9 frame into it, since a page shrunk into a square leaves the action too small to read
+- Pan the window along the camera track's view center, so it follows the action the zoom would have aimed at. Frameboard's square cut used a 1080x1080 window.
+- Expect a screencast take to hold at 1x from a softer 1080p source, while a stepped take gives the same window two clip pixels per page pixel
+
+## The README loop
+
+Cut a README loop only when the operator asks for one. A README hero plays inline and silently, so it is a short loop rather than a cut of the film.
+
+- Cut it from the raw take showing the app's core action, rather than from a render, in the workspace folder `handoff.md` names for it
+- Crop it to the canvas, so no browser margin or page chrome outside the app shows
+- End it on the finished state, held long enough to read before the loop restarts
+- Export an animated WebP under about 2 MB, since a README renders one inline where a video needs a player. Frameboard's loop played inline at 1.72 MB.
+
+## Sped-up clips
+
+A clip the edit plays faster runs its zoom faster too, so a push that settled in real time pumps several times a beat.
+
+- Rebuild the beat's track for the playback rate with `canon take camera <dir>/log.json --rate <n> --out <file>`, and drive the wrapper from that file rather than from `camera.json`
+- Never scale `camera.json`'s times by hand, since the rebuilt track also keeps each push inside the 1 s ceiling at the new speed
+- Keep a typing beat at a rate where each word still reads, since a viewer cannot read a fill that finishes in a few frames
+
+## Storyboard headings
+
+- Write each frame heading as `## Frame N: title`, since the dash form in HyperFrames' `storyboard-format.md` example fails the markdown audit
+- Treat the parser's read of the colon form as assumed, since its lenient parse was not confirmed against its source
+- Title each frame as the beat the operator approved, so the frame, the take's folder, and the caption share one name a reader can follow across all three
+
+## The workspace README
+
+Step 5 writes the filming half of `.canon/video/<slug>/README.md`. The composing session adds its own half under its own heading.
+
+- Add how to re-render each project the workspace holds, naming its folder and the render command it runs
+- Name any track rebuilt with `--rate`, with the command that rebuilt it, since a re-film overwrites `camera.json` and leaves a rebuilt track stale
+- Leave the filming half as Step 5 wrote it, so the next session can re-film without reading the composition
+
+## Sources
+
+| Rule                        | Source                                                                                                   |
+| --------------------------- | -------------------------------------------------------------------------------------------------------- |
+| Caption placement and scrim | HyperFrames' `captions.md`, adjusted for footage with chrome along its bottom edge                       |
+| A new project per shape     | `hyperframes-studio`'s brief step, which starts a new project for a different aspect                     |
+| The 1080x1080 window        | Frameboard's launch film, cut square from stepped takes                                                  |
+| The 2 MB WebP loop          | Frameboard's README hero, an animated WebP cut from a raw take, which played inline at 1.72 MB           |
+| Rebuilding a sped-up track  | `canon take camera --help`, whose `--rate` divides every time in the log                                 |
+| Storyboard heading form     | HyperFrames' `storyboard-format.md` and the markdown audit's character bans, with the colon read assumed |
+| The README's two halves     | Frameboard's workspace, whose README recorded how to re-film and re-render after a session ended         |

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"
@@ -28,7 +28,12 @@ access = "/write?token=demo"
 - An absent `access` opens the served root
 - `personas` and `proposals` belong to `app-drive`, and a take reads neither
 
-Every beat opens the address fresh in its own browser, so a link the app honors once, such as a single-use edit ticket, serves one beat alone. Mint a fresh link and run `canon take` once per beat for such an app, or a later beat opens the page without the access the first one spent.
+### Single-use access
+
+Every beat opens the address fresh in its own browser, so a link the app honors once, such as a single-use edit ticket, serves one beat alone. A beat that falls back to the screencast opens the address a second time, so the fallback spends the link too, even within one beat.
+
+- Point `access` at a local redirect minting a fresh link per request, so each open gets its own, the one pattern that held across beats and fallbacks alike
+- Run `canon take` once per beat with a freshly minted link only where no redirect can be served, with `"route": "screencast"` on each so no fallback reopens it
 
 ## When the file is absent
 

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
 
@@ -14,7 +14,7 @@ Read at Step 5 of `ui-record`. Canon stops at the clip, and a HyperFrames compos
 | 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          |
+| `log.json`    | Every move, click, drag, key press, typing burst, and scroll, with its boxes |
 | `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 |
 
@@ -24,10 +24,10 @@ Every coordinate in the log and the track is in CSS pixels of a 1920x1080 page,
 
 Each frame carries `scale`, the view's top-left `x` and `y`, the `cursor`, and `ring`.
 
-- `scale` is 1 for the whole page and 1.8 at the deepest zoom
+- `scale` is 1 for the whole page and 1.8 at the deepest zoom, or about 1.35 on a screencast beat, and holds at 1 on a beat whose plan set `push: false`
 - `x` and `y` place the view's corner on the page, so the view spans `1920 / scale` by `1080 / scale` from there
 - `cursor` is the pointer's position on the page
-- `ring` runs from 0 to 1 across the 450 ms after a click and is `null` otherwise
+- `ring` runs from 0 to 1 across the 450 ms after a click and is `null` otherwise. On a drag it grows to 0.3, holds there from press to release, and runs on to 1 from the release.
 
 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.
 
@@ -40,11 +40,19 @@ 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
 
+A cut in another shape and the README loop are each a project of their own beside `composition/`, so one shape's edit never reflows another's. Each reads the takes from `../takes/` the same way.
+
+| Project                | Holds                                            |
+| ---------------------- | ------------------------------------------------ |
+| `composition/`         | The main cut, in the takes' 16:9 shape           |
+| `composition-<shape>/` | One other shape, such as `composition-square/`   |
+| `readme-loop/`         | The short silent loop a README plays as its hero |
+
 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.
@@ -62,6 +70,8 @@ The cursor stays outside the wrapper because a cursor inside it would scale with
 
 ## What the composition still owns
 
+Read `${CLAUDE_SKILL_DIR}/references/compose-craft.md` for the captions, the other shapes, the loop, and a sped-up clip, where app footage changes what HyperFrames advises.
+
 - The order and the cuts between takes, the captions, and any music or voice
 - Whether a take plays whole or trimmed. A trim keeps the track aligned only when it shifts the track by the same frames.
 - Motion blur stays off, by the operator's call on these takes

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
 
@@ -15,6 +15,7 @@ Read at Step 3 of `ui-record`, before writing the first beat. `canon take --help
 - [Targets](#targets)
 - [The pointer](#the-pointer)
 - [The zoom](#the-zoom)
+- [The harness route](#the-harness-route)
 - [Sources](#sources)
 
 ## The plan
@@ -44,6 +45,13 @@ A plan holds the approved beats in order. Each beat names its setup, which runs
 - Reach the beat's start state through `setup`, since every beat opens the page fresh and nothing a setup step does is filmed
 - Write the beat's `name` as the operator approved it, since it names the clip's folder
 
+### Server state
+
+Every beat reloads the page, never the server. An app holding its state in server memory keeps a change one beat made, so the next beat opens on it.
+
+- Undo the change in the next beat's `setup`, or order the beats so each one's result is the next one's start
+- Restart the server between beats only when neither works, since a restart costs the served address its warm start
+
 ## Frame-stepping limits
 
 A step beat runs the page on a virtual clock, one frame per step. Most pages film this way, and some inputs are known to stall it.
@@ -52,10 +60,11 @@ A step beat runs the page on a virtual clock, one frame per step. Most pages fil
 - A scroll has not been proven under frame stepping, and a smooth scroll can jump. Give a scroll its own beat so a fallback costs that beat alone.
 - An animated GIF can freeze, so expect one to hold its first frame
 - Set `"route": "screencast"` on a beat known to stall, rather than paying for the stall before the fallback
+- Set a top-level `"route": "screencast"` on a plan whose page stalls on every beat, and a beat naming its own `route` keeps it
 
 A fallback films the beat again from a fresh load, replaying its setup and the steps the stepper already ran. A beat whose steps persist in the app, such as a fill that renames something, would then start from the changed state, so set `"route": "screencast"` on it when it risks a stall.
 
-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.
+A screencast beat films in real time at 1920x1080, so its camera zooms only to about 1.35x before it would go soft. Tell the operator which beats ran that way.
 
 ### Reading a take back
 
@@ -68,6 +77,7 @@ Two rules hold once a beat is filmed.
 
 - Prefer a stable attribute, such as an `aria-label`, a `data-testid`, or an `id`, over a position like `:nth-child`
 - Use `text=<words>` for a control whose only stable handle is its label
+- Target a control with no visible text, such as an icon button, by its `aria-label`, since `text=` finds nothing on it
 - Use a `move` to a point only for a target the page reveals on hover, and follow it with the click
 - Read each target off the served page before writing it. The verb refuses `target-missing` rather than filming a guess, and a refusal costs a reload.
 
@@ -86,6 +96,22 @@ The camera track already carries the zoom, so these rules decide what to film fo
 - Expect a target filling most of the view to get less zoom, and one filling the page to get none
 - The push reaches 90% of its depth in about 633 ms, inside the 1 s ceiling a push onto an action keeps
 
+### Depth, opt-out, and speed
+
+Three controls change the push itself.
+
+- Expect a screencast beat's zoom to stop near 1.35x, since its clip has one pixel per page pixel, and a stepped beat's to reach 1.8x
+- Set `"push": false` on a beat the edit holds wide, such as one showing a whole layout change. Its track keeps the cursor and the click ring and drops the zoom.
+- Rebuild a beat's track with `canon take camera <dir>/log.json --rate <n> --out <file>` for a clip the edit plays `n` times faster, so the zoom settles on the clock a viewer sees
+
+## The harness route
+
+A beat driven from outside the page, such as a drag between two windows or an input the step kinds lack, cannot run as `canon take` steps. Until the verb can run an outside script itself, film it through a harness.
+
+- Drive the beat from a Playwright script that records the page and writes a log in the shape of a take's `log.json`
+- Build its camera track from that log with `canon take camera <log> --out <file>`, so the composition applies it like any other take
+- Tell the operator which beats ran this way, since their clips carry the harness's resolution rather than the stepper's
+
 ## Sources
 
 | Rule                       | Source                                                                                                                                                   |

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