@erclx/canon 4.110.0 → 4.112.0

package/assets/brand/mark.svg

@@ -0,0 +1,10 @@
+<!-- A bound ledger: two pages fanned open around a spine, drawn as three
+     solid masses rather than thin strokes, so the shape survives being
+     rendered at favicon size instead of averaging into grey. The 10-unit
+     gap between each page and the spine, against an 80-unit frame, is what
+     keeps the split a visible channel at 16px; a first draft at half that
+     gap closed into an unreadable blob at the same size. -->
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="10 10 80 80">
+  <path d="M34,20 L15,28 L15,72 L34,80 Z M66,20 L85,28 L85,72 L66,80 Z" fill="currentColor" />
+  <rect x="44" y="15" width="12" height="70" rx="2" fill="currentColor" />
+</svg>

package/claude/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "canon",
   "description": "Automated governance, versioning, and discovery tools for Claude Code.",
-  "version": "4.110.0",
+  "version": "4.112.0",
   "author": {
     "name": "Eric Le",
     "url": "https://github.com/erclx"

package/claude/skills/auto-ship/REQUIREMENT.md

@@ -21,6 +21,7 @@ Review is the step that varies most. It gets skipped on a diff that needed one,
 - Own the review receipt's lifetime, since this chain writes it, cites it in its own closing block, and is the only body that can read whether the step keeping it is still using it
 - Delegate the ship sequence to `git-ship` rather than restating it, and name only what this chain adds to it
 - Open the pull request as a draft before the continuous integration watch begins, since a pull request marked after it is mergeable for the length of the run
+- Prove the draft target's head is the current branch and its state is open before marking it, and stop with nothing marked on a mismatch, since the number is retyped between steps and a draft mark on a release pull request holds that release
 - Name the recovery for the stop it took, since the value of stopping is that the user knows where to resume
 
 ## Must not

package/claude/skills/auto-ship/SKILL.md

@@ -190,14 +190,23 @@ This chain owns the receipt's lifetime, which is what makes the Output block's c
 
 Invoke `canon:git-ship`. That body owns the sequence, being the verify gate, memory capture, both doc syncs, staging, the commit grouping, the branch rename, the pull request, and the CI watch, along with the reason each step sits where it does. This step used to restate that list and the two drifted apart with nothing comparing them, so read the order there and never here.
 
-One thing this chain adds. Mark the pull request as a draft as soon as `git-ship`'s pull request step returns, ahead of its CI watch, then read the flag back:
+One thing this chain adds. Mark the pull request as a draft as soon as `git-ship`'s pull request step returns, ahead of its CI watch. Run it as one command, where the shell proves the target before the mark and reads the flag back after it:
 
 ```bash
+target=$(gh pr view <number> --json headRefName,state --jq '"\(.headRefName) \(.state)"') || exit 1
+if [ "$target" != "$(git branch --show-current) OPEN" ]; then
+  printf '❌ #%s reads "%s", not "%s OPEN". The draft mark was not written.\n' "<number>" "$target" "$(git branch --show-current)" >&2
+  exit 1
+fi
 gh pr ready --undo <number>
 gh pr view <number> --json isDraft
 ```
 
-Name the number `git-ship`'s pull request step returned on both calls rather than leaving either to resolve by branch. `${CLAUDE_SKILL_DIR}/../git-pr/REQUIREMENT.md` states why: a lookup that resolves by branch alone can return a closed pull request sharing that head, so the number is resolved once and reused rather than re-derived.
+Name the number `git-ship`'s pull request step returned in every position rather than leaving any to resolve by branch. `${CLAUDE_SKILL_DIR}/../git-pr/REQUIREMENT.md` states why: a lookup that resolves by branch alone can return a closed pull request sharing that head, so the number is resolved once and reused rather than re-derived.
+
+A refusal is a stop. Report the line the shell printed, then resolve the number from the `number=` and `head=` lines of `git-pr`'s output and re-run the command by hand. The comparison sits in the shell rather than in the session's reading of a printed value, which is the same split `git-pr`'s `assert_own_pr` makes, because the judgment that picked a wrong number is the one that would read the check.
+
+The number crosses from that step's output into a command this session types, which is the one place a number gets authored rather than derived. A number misread there, or inferred from the newest pull request in view, would draft a stranger's pull request. A release pull request is the worst such target, since the mark holds the release and this role may not lift it again.
 
 Report what the read returned rather than what the command printed, since the exit says the call ran and says nothing about the state. A `true` reports a draft. A `false` reports the pull request as opened ready and unsupervised, and the chain stops there. Never re-issue the undo on a disagreeing read, which fights whoever readied it instead of guarding anything.
 
@@ -243,3 +252,4 @@ Every stop point leaves recoverable state. The user resumes manually from the ap
 | Inherited review findings                  | Fix findings, run `/git-ship`                                                                                                                   |
 | Self-introduced finding survived           | Read the receipt for what the one repair pass left open, fix it, run `/git-ship`                                                                |
 | git-ship fails                             | Inspect hook or remote error, run again                                                                                                         |
+| Draft target is not this branch's          | Nothing was marked. Read the number and `head=` from `git-pr`'s output, confirm they match, then run the mark by hand                           |

package/claude/skills/canon-operator/REQUIREMENT.md

@@ -26,8 +26,8 @@ The last failure is a section no route reaches. `## Route` maps an intent or a d
 - Resolve every stack, rule, snippet, and standard name from a catalog at runtime
 - Run the CLI non-interactively and report the command run, what changed, and the full path of anything written
 - Read the overwrite contract from the body before any install or sync, and name each surface it lists as overwritten before running one
-- Read the reverse walk beside the forward sections, so a folder the toolkit stopped shipping and a migration with a live case both reach the user
-- Hand off a named migration to the skill the report names, and name an unmigrated domain's root and install path for the user to move themselves when no skill covers it
+- Read the reverse walk beside the forward sections, so a folder the toolkit stopped shipping reaches the user
+- Name an unmigrated domain's root and install path for the user to move themselves, since no skill covers the move
 - Route a measurement intent to the audit offers from the route table itself, rather than leaving the section reachable only by reading past the table
 - Rank a lifecycle row against the audit offers where the route table itself states it, so a session acting on the lifecycle row reads the ranking without opening the section being ranked
 - Offer every audit whose surface the target carries, and offer none whose surface it lacks

package/claude/skills/canon-operator/SKILL.md

@@ -25,10 +25,10 @@ Run `canon sync --check . --json` before routing. It reports what a target is be
 Read seven fields off the report and carry each to `## Route`:
 
 - `unmigrated`: a domain sitting at the root layout with nothing under `.claude/`. The most urgent finding, because that domain reports no drift of its own while being entirely behind
-- `superseded`: a file a newer seed folder replaced. No command moves it, since the content is the project's own, so this routes to the skill that proposes the split rather than ending at the report
+- `superseded`: a file a newer seed folder replaced. No command moves it, since the content is the project's own, so this routes to `canon:target-check` for the full per-domain reading rather than ending at the report
 - `seeds`: entries are `matching`, `stale`, `drifted`, or `missing`. Anything but `matching` needs the seed handoff
 - `domains[].entries`: per-file `stale`, `customized`, `stranded`, and `orphaned` as before
-- `reverse`: what the target holds that no live catalog claims. `unclaimed` lists folders at roots the toolkit stopped shipping, each with an `attribution` of `dropped`, `unattributed`, or `project`. Act on the first two and leave `project` alone, which history proved the project owns. `migrations` names a proposal-only skill with a live case here and the `reason` it was measured from
+- `reverse`: what the target holds that no live catalog claims. `unclaimed` lists folders at roots the toolkit stopped shipping, each with an `attribution` of `dropped`, `unattributed`, or `project`. Act on the first two and leave `project` alone, which history proved the project owns
 - `historyUnavailable` on a domain, on `seeds`, or on `reverse`: nothing could be dated, so treat every difference as unverified and say so rather than reporting a file as untouched. It is set on `reverse` when the toolkit itself ships without history, which is the registry-install case, so the walk found nothing rather than finding a clean target
 - `tooling`: read `measured` first. Every count under it is zero when it is false, which is an absence of measurement rather than a measured zero. Past that, `chain` names the stacks the install resolved, nearest first, and `counts.gitignore` counts the managed ignore entries the target is missing.
 
@@ -43,8 +43,7 @@ Map the stated intent, or what `## Diagnose` found, to one lifecycle phase, then
 The two can name different rows, and a reply answers both rather than picking one. Run or hand off what the finding names, then answer the intent in the same reply. A measurement intent therefore reaches the audit offers below even on a target whose diagnostic found scaffold work, which is the case a session leaving from the scaffold row would otherwise never read.
 
 - A domain in `unmigrated`: name it, the root path, and the install path. No command moves it, so the user runs the relocation themselves
-- An entry in `migrations`: hand off to the skill its `skill` field names, spelled as the report spells it. Both of them propose without writing, so the handoff is where this stops
-- Anything in `superseded`: name which files and what replaced them, then hand off to `migration-superseded`. Both skills propose, so neither moves nor deletes the file
+- Anything in `superseded`: name which files and what replaced them, then hand off to `canon:target-check`, which reports and never moves or deletes the file
 - A folder in `unclaimed`: name it and the attribution it carries. No command moves it and the content may be the project's own, so the decision is the user's
 
 - First-time scaffold of a fresh project: hand off to `target-setup`

package/claude/skills/git-pr/REQUIREMENT.md

@@ -23,6 +23,8 @@ A lookup that resolves by head branch alone carries its own failure. A branch na
 - Detect an open pull request and edit it in place, so a follow-up push keeps the body in sync instead of failing
 - Scope that detection to an open pull request on the current head and the default base, so neither a reused branch name nor a second base resolves the wrong one
 - Resolve the pull request once and reuse what that resolution returned, so the number recorded never depends on how a lookup ranks two pull requests sharing a head
+- Prove before every write to an existing pull request that its head is the current branch and its state is open, and refuse with nothing written on a mismatch, so a wrong number reaching a write never lands on another branch's pull request
+- Print the head branch beside the number, so a caller writing to the pull request later has a value to check the number against
 - Label from the paths the branch changed, against a map the project declares, so the label set belongs to the project rather than to the skill
 - Apply labels after the pull request exists, so a label the remote does not carry costs a warning rather than the pull request
 - Report a refused label, since a warning nothing surfaces leaves the run indistinguishable from one that labelled

package/claude/skills/git-pr/SKILL.md

@@ -135,23 +135,41 @@ This command reuses `.canon/tmp/pr/body.md`, which the pre-publish scan above al
 
 ```bash
 pr_labels="<comma-separated labels, empty when the map resolves to nothing>"
+head_branch=$(git branch --show-current)
 git push -u origin HEAD || exit 1
 base_branch=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name) || exit 1
-pr_number=$(gh pr list --head "$(git branch --show-current)" --base "$base_branch" --state open --json number --jq '.[0].number // empty')
+assert_own_pr() {
+  target=$(gh pr view "$1" --json headRefName,state --jq '"\(.headRefName) \(.state)"') || exit 1
+  if [ "$target" != "$head_branch OPEN" ]; then
+    printf 'Refused: #%s reads "%s", not "%s OPEN". Nothing was written to it.\n' "$1" "$target" "$head_branch" >&2
+    exit 1
+  fi
+}
+pr_number=$(gh pr list --head "$head_branch" --base "$base_branch" --state open --json number --jq '.[0].number // empty')
 if [ -n "$pr_number" ]; then
+  assert_own_pr "$pr_number"
   pr_url=$(gh pr edit "$pr_number" --title "<title>" --body-file .canon/tmp/pr/body.md) || exit 1
 else
   pr_url=$(gh pr create --title "<title>" --body-file .canon/tmp/pr/body.md) || exit 1
   pr_number=${pr_url##*/}
+  assert_own_pr "$pr_number"
 fi
 if [ -n "$pr_labels" ]; then
   gh pr edit "$pr_number" --add-label "$pr_labels" >/dev/null ||
     printf 'Label apply failed. Create a missing label with: gh label create <name>\n' >&2
 fi
 rm -rf .canon/tmp/pr/body
-printf 'number=%s\nurl=%s\n' "$pr_number" "$pr_url"
+printf 'number=%s\nurl=%s\nhead=%s\n' "$pr_number" "$pr_url" "$head_branch"
 ```
 
+### Binding every write to this branch's pull request
+
+`assert_own_pr` runs ahead of both writes this command makes to a pull request that already exists, the title and body edit and the label edit. It reads the target's head branch and state and refuses unless they are this branch and `OPEN`. A refusal exits before anything is written, so a wrong number costs the run rather than a stranger's pull request. The function lives only inside this command, so the steps below that post comments or record the task are covered by taking `<number>` from this output rather than by the check itself.
+
+The check compares a number against a branch and never derives a number from one, so it adds no lookup of the kind `### Resolving the pull request` retired. It holds whichever way a wrong number arrives. A number a session retyped by hand, or inferred from the newest pull request in view, reads as a foreign head here and stops.
+
+The last output line carries `head=` so a caller relaying the number holds a branch to compare it against rather than a bare integer. A caller that writes to the pull request itself, such as a draft mark, runs the same comparison in the shell first, reading `gh pr view <number> --json headRefName,state` and refusing unless it matches `head` and `OPEN`.
+
 ### Find the UI checklist
 
 `ui-checklist` writes a visual checklist to `.canon/tmp/handoff/ui-checklist/<slug>.md` at the main worktree root when a change needs visual verification, with `<slug>` derived per `${CLAUDE_SKILL_DIR}/../../standards/slug.md`. This skill is the file's sole consumer. Resolve the main root the way `session-worktree` does (`git worktree list --porcelain | grep -m 1 '^worktree ' | cut -d' ' -f2-`, falling back to `pwd`) and check for the file there. A missing file means no checklist was produced, and the two steps below each skip their checklist half.
@@ -238,7 +256,7 @@ canon pr evidence <number> --preview <url> --json
 
 ### Record the number on the task
 
-Write the `number` the final command printed onto the task the branch is closing. Do not resolve it again. `${CLAUDE_SKILL_DIR}/REQUIREMENT.md` states why: a lookup that resolves by branch alone can return a closed pull request sharing that head, so the number is resolved once and reused rather than re-derived.
+Write the `number` the final command printed onto the task the branch is closing. Do not resolve it again. A final command that refused on a head mismatch printed no number, so this step writes nothing on that run. `${CLAUDE_SKILL_DIR}/REQUIREMENT.md` states why: a lookup that resolves by branch alone can return a closed pull request sharing that head, so the number is resolved once and reused rather than re-derived.
 
 The task is the one whose `Plan:` line names the plan this branch implemented. Name that plan by its file, which is `.canon/plans/feature-<slug>.md` at the main worktree root with `<slug>` derived per `${CLAUDE_SKILL_DIR}/../../standards/slug.md`. `plan-feature` writes the plan under the branch slug, so the two correspond on any branch that came through the plan-to-execute path. When the session already knows which plan it implemented, because a caller read it earlier in the chain, use that filename instead of re-deriving.
 

package/claude/skills/target-check/references/domains.md

@@ -25,7 +25,7 @@ Read three fields off the same report, then two verbs:
 
 - `unmigrated`: a domain still at the root layout with nothing under `.claude/`. The most urgent finding, because such a domain reports no drift of its own while being entirely behind.
 - `superseded`: a file a newer seed folder replaced. No command moves it, since the content is the project's own.
-- `reverse`: `unclaimed` names folders at roots the toolkit stopped shipping, each with an `attribution` of `dropped`, `unattributed`, or `project`. `migrations` names a proposal-only skill with a live case here and the `reason` behind it.
+- `reverse`: `unclaimed` names folders at roots the toolkit stopped shipping, each with an `attribution` of `dropped`, `unattributed`, or `project`.
 - `canon context audit --json`: required sections, entry length, citations, and index drift across the context folder.
 - `canon records validate <kind> --json`, once per record folder the target carries.
 
@@ -33,7 +33,7 @@ Read three fields off the same report, then two verbs:
 - Behind: any of those carrying an entry. Name the entry and its attribution.
 - Unread: `historyUnavailable` set on `reverse`, a `reverse` key the report does not carry at all, or either verb refusing. A missing `reverse` key is a binary predating the field rather than a target with nothing unclaimed.
 
-Routes by finding. `unmigrated` routes to a relocation the user runs, since no command moves it. `superseded` routes to `migration-superseded`. A `migrations` entry routes to the skill its `skill` field names, spelled as the report spells it. An `unclaimed` folder carrying `project` attribution routes nowhere, since history proved the project owns it.
+Routes by finding. `unmigrated` routes to a relocation the user runs, since no command moves it. `superseded` routes to a split the user makes, since no command moves the content and no skill proposes it. An `unclaimed` folder carrying `project` attribution routes nowhere, since history proved the project owns it.
 
 ## 3. Governance rules
 

package/claude/skills/teach-workspace/SKILL.md

@@ -18,7 +18,7 @@ The shape of the workspace is fixed by `${CLAUDE_SKILL_DIR}/../../standards/teac
 - Write nothing outside the workspace folder, apart from the one handoff file Step 6 names. A durable page stays in `reference/` and is copied out by the skill that owns the destination, never by this one.
 - Do not open a second workspace on a subject one already covers. Resume that one.
 - Never promote a lesson. It is generated markup carrying a quiz and a learner, and no request makes it promotable.
-- Carry the toolkit's favicon on every page this skill writes, index and lesson alike, in the `<head>` verbatim: `<link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='10 10 80 80'%3E%3Cpath d='M34,20 L15,28 L15,72 L34,80 Z M66,20 L85,28 L85,72 L66,80 Z' fill='rgb(224,114,75)' /%3E%3Crect x='44' y='15' width='12' height='70' rx='2' fill='rgb(224,114,75)' /%3E%3C/svg%3E" />`
+- Never write a favicon link by hand. `canon teach nav` puts the toolkit's icon on every page it generates and inside a lesson's `style` region, so a hand-written one in a lesson's `<head>` gives the page two.
 
 ## Step 0: let the CLI resolve the workspace root
 

package/docs/agents/install-and-sync.md

@@ -256,11 +256,9 @@ seed tree rather than from a fixed set of filenames, so a folder added later is
 covered without a code change. Only an exact stem matches, which leaves a
 suffixed variant such as `TASKS-ARCHIVE.md` unreported.
 
-Route it to `migration-superseded`. That skill resolves the standard governing
-`replacedBy` from the `appliesTo` the standards catalog declares, reads the
-destination shape with `canon standards <name>`, and proposes the split without
-writing. Where a folder has no governing standard, the entry earns a named
-refusal rather than a shape nobody stated.
+No skill splits the file. The standard governing `replacedBy` is the one the
+`appliesTo` the standards catalog declares, and `canon standards <name>` reads
+its destination shape, so the split is the project's own to make.
 
 `unmigrated` names a domain sitting at the root layout an older toolkit installed
 to, with nothing at the path the current one reads. It carries `rootPath`,
@@ -350,7 +348,7 @@ check.
 `reverse` is the one section built by walking the target rather than the
 catalog. Every other surface enumerates toolkit-owned keys and asks whether the
 target matches, so a folder the toolkit deleted appears in none of them. It
-carries `unclaimed`, `migrations`, and `historyUnavailable`.
+carries `unclaimed` and `historyUnavailable`.
 
 `unclaimed` names a folder the target holds at a top-level path the toolkit once
 shipped and has since deleted. The candidate roots come from the toolkit's own
@@ -381,13 +379,6 @@ colliding on a retired name costs the walk no reads. The cost is that a file the
 toolkit shipped and the target renamed goes unmatched, the same limit the
 `unmigrated` count carries.
 
-`migrations` names a proposal-only skill with a live case in this target. It
-fires on a `CLAUDE.md` past 250 lines for `migration-claude-md`, and on a `docs/` folder
-holding markdown with no populated `canon/context/` for `migration-context`.
-Each entry carries the skill name and the measurement behind it, so a consumer
-can check the proposal before running it. Without the field both skills are
-documented and unreachable from any report.
-
 #### What counts toward the gate
 
 `unmigrated` counts toward `--exit-code`, since running the relocation closes it.

package/docs/agents/teach.md

@@ -172,7 +172,9 @@ canon teach nav regular-expressions --json
 
 With no topic it rewrites every workspace. The teach-root listing is always rewritten regardless, since it reports on every workspace and a scoped run leaving it stale would be a second kind of drift this verb exists to end.
 
-A lesson carries its chrome as four marker pairs the authoring skill writes empty: `canon:teach:style`, `canon:teach:header`, `canon:teach:footnav`, and `canon:teach:scripts`. This verb splices each one from the current workspace state, embedding the shared stylesheet and the script that settles the course panel before the page paints, rebuilding the course sidebar, the breadcrumb and jump menus, the prev/next footer nav, and the behavior scripts, and leaves the authored `<h1>`, lede, body, and quiz between the header and the footnav untouched.
+A lesson carries its chrome as four marker pairs the authoring skill writes empty: `canon:teach:style`, `canon:teach:header`, `canon:teach:footnav`, and `canon:teach:scripts`. This verb splices each one from the current workspace state, embedding the toolkit's favicon, the shared stylesheet, and the script that settles the course panel before the page paints, rebuilding the course sidebar, the breadcrumb and jump menus, the prev/next footer nav, and the behavior scripts, and leaves the authored `<h1>`, lede, body, and quiz between the header and the footnav untouched.
+
+It also deletes the one icon link the authoring skill used to have a session write by hand into a lesson's `<head>`, matched as that exact string, so the page keeps only the icon the `style` region carries. Any other link an author wrote stays.
 
 A workspace carrying no `course.css` gets its stylesheet pair seeded first, so the contents page it links is never unstyled, and an existing `course.css` is never overwritten. The embedded copy drops the seed's `@import` line, which resolved against the lesson's own folder and never loaded anything.
 

package/docs/target-projects.md

@@ -261,8 +261,6 @@ Each entry carries a verdict, since a dropped folder and one the project wrote a
 
 Nothing acts on any of them, and the verdict is what makes the list safe to read.
 
-The same field names a proposal-only skill with a live case here under `migrations`, which is how `canon:migration-claude-md` and `canon:migration-context` become reachable. Each entry carries the measurement behind the proposal rather than the proposal alone.
-
 Add `--json` for the machine-readable report, and `--exit-code` to fail a CI job when a target falls behind. Files the project authored itself never count toward that exit code, and neither do superseded artifacts, seed drift, tooling, or anything the reverse walk reports, since each names content the project is expected to edit or place itself. An unmigrated domain does count, because running the relocation closes it.
 
 Tooling reports under a section of its own, and `measured` there says whether the target ever recorded a chain. One that never ran a tooling sync reports unmeasured rather than clean, which is what separates tooling nobody has looked at from tooling that is current. A workspace root records nothing either way, since each package resolves its own chain.

package/docs/workflow/ai-workflow.md

@@ -285,17 +285,13 @@ This section is the corpus the coverage claim is measured against: every name `c
 
 ### Keep the project current with the toolkit
 
-| Skill                            | When to use                                                                            |
-| -------------------------------- | -------------------------------------------------------------------------------------- |
-| `canon:target-check`             | In a target project, to report per domain what it holds against what the toolkit ships |
-| `canon:seed-sync`                | After a toolkit update, to reconcile installed seeds without losing customizations     |
-| `canon:migration-claude-md`      | When `CLAUDE.md` grew past what always-load context should carry                       |
-| `canon:migration-context`        | When `docs/` holds agent-flavored files belonging in `canon/context/`                  |
-| `canon:migration-superseded`     | When a drift report names a `.claude/` file a folder has replaced                      |
-| `canon:migration-standards-drop` | When the project still holds an installed `.claude/standards/` tree                    |
-| `canon:canon-feedback`           | When something in the toolkit is broken, missing, or off, to open an issue on it       |
-| `canon:canon-feedback-triage`    | In the toolkit repo, to work through the open feedback issues                          |
-| `canon:canon-rollout`            | In the toolkit repo, to take one change out to every consuming project at once         |
+| Skill                         | When to use                                                                            |
+| ----------------------------- | -------------------------------------------------------------------------------------- |
+| `canon:target-check`          | In a target project, to report per domain what it holds against what the toolkit ships |
+| `canon:seed-sync`             | After a toolkit update, to reconcile installed seeds without losing customizations     |
+| `canon:canon-feedback`        | When something in the toolkit is broken, missing, or off, to open an issue on it       |
+| `canon:canon-feedback-triage` | In the toolkit repo, to work through the open feedback issues                          |
+| `canon:canon-rollout`         | In the toolkit repo, to take one change out to every consuming project at once         |
 
 ### Generate an artifact on demand
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/canon",
   "type": "module",
-  "version": "4.110.0",
+  "version": "4.112.0",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {
@@ -17,6 +17,7 @@
     "claude",
     "docs",
     "tsconfig.json",
+    "assets/brand/mark.svg",
     "!scripts/sandbox",
     "!scripts/eval",
     "!**/*.test.ts",

package/scripts/core/capture-home.sh

@@ -0,0 +1,59 @@
+#!/usr/bin/env bash
+# Builds the landing page, captures it, and stages the frames over
+# assets/evidence/home, the baseline `canon pr evidence` compares against.
+#
+# Two workflows call it. pr-visual-checks.yml stages the frames into the runner
+# tree to diff them against the baseline, and refresh-capture-frames.yml stages
+# them to commit as the new baseline. Both need the same frames, so one script
+# keeps the two from drifting apart.
+#
+# `tooling/web/configs/e2e/screenshot.ts` is reused as is. This checkout has no
+# web/package.json, so the preview server and the cases run against the
+# root-level scripts rather than through screenshot.sh, which assumes a
+# per-project `bun run build`/`bun run preview` pair.
+set -e
+set -o pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PROJECT_ROOT="${PROJECT_ROOT:-$(cd "$SCRIPT_DIR/../.." && pwd)}"
+
+PORT=4321
+BASE_URL="http://localhost:$PORT"
+BASELINE="$PROJECT_ROOT/assets/evidence/home"
+
+cd "$PROJECT_ROOT"
+
+bun run web:build
+
+bun run web:preview &
+PREVIEW_PID=$!
+trap 'kill "$PREVIEW_PID" 2>/dev/null || true' EXIT
+
+for _ in $(seq 1 40); do
+  curl -sSf "$BASE_URL/" >/dev/null 2>&1 && break
+  sleep 0.25
+done
+curl -sSf "$BASE_URL/" >/dev/null 2>&1 || {
+  echo "Preview server not responding on port $PORT after 10s." >&2
+  exit 1
+}
+
+(cd web && SCREENSHOT_BASE_URL="$BASE_URL" bun ../tooling/web/configs/e2e/screenshot.ts)
+
+# The committed tree is cleared first rather than copied over. A copy only adds
+# and overwrites, so a section dropped from the case list would leave its
+# frames in place and a diff would see no change. Clearing first shows that
+# section as a deletion.
+rm -rf "$BASELINE"
+mkdir -p "$BASELINE"
+cp -R web/screenshots/localhost/home/. "$BASELINE/"
+
+# The sweep holds all four widths and this repository commits two, 320 and
+# 1280. The case list is the place to change if that set moves.
+find "$BASELINE" \( -name '768--*.png' -o -name '1536--*.png' \) -delete
+
+# The shared golden config names the case that emulates nothing `default`, and
+# this repository's baseline names that frame `light`.
+find "$BASELINE" -name '*--default.png' -execdir sh -c 'mv "$1" "${1%--default.png}--light.png"' _ {} \;
+
+echo "capture-home: staged frames in assets/evidence/home"

package/src/claude/cases/setup.ts

@@ -1,9 +1,8 @@
 import type { SkillCase } from '@/claude/skills-rank'
 
 /**
- * `target-setup`, `migration-*`, `canon-*`, and `create-rule`: scaffolding,
- * proposal-only migrations, and the toolkit's own reference and feedback
- * surfaces.
+ * `target-setup`, `canon-*`, and `create-rule`: scaffolding and the
+ * toolkit's own reference and feedback surfaces.
  *
  * The five `target-setup` cases are one skill read through five entry phrasings
  * rather than five rows that collapsed to a duplicate. Each names a different
@@ -36,26 +35,6 @@ export const SETUP_CASES: readonly SkillCase[] = [
       'Check that the dev server actually starts and the end-to-end suite passes against the scaffold.',
     expect: 'target-setup',
   },
-  {
-    prompt:
-      'This CLAUDE.md file has grown huge, break it apart into the tiered context model.',
-    expect: 'migration-claude-md',
-  },
-  {
-    prompt:
-      'Move the agent-flavored docs out of the docs folder and into context.',
-    expect: 'migration-context',
-  },
-  {
-    prompt:
-      'This file was replaced by a folder, help me split its content into it.',
-    expect: 'migration-superseded',
-  },
-  {
-    prompt:
-      'This project still carries a copy of the standards folder, get rid of it and point everything at the CLI.',
-    expect: 'migration-standards-drop',
-  },
   {
     prompt:
       "Before I run this sync, tell me exactly what it's going to overwrite.",

package/src/commands/sync.ts

@@ -189,7 +189,6 @@ function renderCheck(report: CheckReport): void {
   }
 
   renderUnclaimed(report)
-  renderMigrations(report)
 
   outro()
   // Scanned domains only. Tooling renders a section on every managed target, so
@@ -334,21 +333,6 @@ function describeUnclaimed(entry: UnclaimedFolder): string {
   return `${counted}, content published at ${entry.since.slice(0, 7)}`
 }
 
-/**
- * The proposal-only skills no other field reaches.
- */
-function renderMigrations(report: CheckReport): void {
-  const { migrations } = report.reverse
-  if (migrations.length === 0) return
-
-  logStep('Migrations with a case here')
-
-  for (const candidate of migrations) {
-    logWarn(candidate.reason)
-    logInfo(`Run /canon:${candidate.skill} for a proposal.`)
-  }
-}
-
 async function runSync(target: string): Promise<number> {
   intro('canon sync')