@erclx/canon 4.66.0 → 4.68.0

package/src/migrate/skill-names.ts

@@ -0,0 +1,89 @@
+import { defineRenameRules, type RenameRules } from '@/migrate/rename'
+
+/**
+ * The twenty-five shipped skills that carried a `claude-` prefix, and the
+ * two-word name each takes instead.
+ *
+ * The plugin namespace already resolves every one of them as `canon:<name>`,
+ * so the prefix bought grouping rather than uniqueness, and the grouping it
+ * bought was the wrong axis: it marked which surface a skill reads rather than
+ * what the skill does. The prefixes that replace it name a phase or a role, so
+ * a listing groups the review triple, the three planning skills, and the three
+ * session roles together.
+ *
+ * Every name takes two words. Ten of these would have landed as a bare single
+ * word under a plain strip, and a bare word such as `review` or `docs` is a
+ * substring of ordinary prose with no token left for a later sweep to find.
+ */
+export const SKILL_NAME_MAP: Readonly<Record<string, string>> = {
+  'claude-address-review': 'review-address',
+  'claude-autoship': 'auto-ship',
+  'claude-design-extract': 'design-extract',
+  'claude-diagram': 'draft-diagram',
+  'claude-docs': 'docs-fold',
+  'claude-feature': 'plan-feature',
+  'claude-groundwork': 'plan-groundwork',
+  'claude-intake': 'plan-intake',
+  'claude-intake-answer': 'plan-intake-answer',
+  'claude-markdown-propose': 'markdown-propose',
+  'claude-memory-capture': 'memory-capture',
+  'claude-memory-review': 'memory-review',
+  'claude-orchestrate': 'role-orchestrator',
+  'claude-planner': 'role-planner',
+  'claude-pr-review': 'review-pr',
+  'claude-review': 'review-branch',
+  'claude-seed-sync': 'seed-sync',
+  'claude-standards-audit': 'standards-audit',
+  'claude-tasks': 'task-board',
+  'claude-teach': 'teach-workspace',
+  'claude-ui-test': 'ui-test',
+  'claude-ux-audit': 'ux-audit',
+  'claude-ux-measure': 'ux-measure',
+  'claude-worker': 'role-worker',
+  'claude-worktree': 'session-worktree',
+}
+
+/**
+ * The skill rename.
+ *
+ * It protects nothing. The `aitk` sweep had to guard a sibling repository
+ * whose name contained the token, and no string here contains a skill name
+ * while meaning something else: the one overlap in the map is
+ * `claude-intake` inside `claude-intake-answer`, which the longest-first
+ * ordering settles rather than a protected form. Reading that off the output
+ * would report a pass either way, since both rows land on a name opening with
+ * `plan-intake`, so the ordering is asserted directly.
+ *
+ * It matches whole tokens. A skill name is a complete name rather than a word
+ * stem, and the corpus holds one word that opens with a name and means
+ * something else: `wiki/claude/claude-worktrees.md` documents the harness
+ * feature, not the skill, and every sibling in that folder is named
+ * `claude-<topic>.md` for a Claude Code concept. Sixteen occurrences of it
+ * would have moved to a name the folder's own convention contradicts.
+ *
+ * No article fixup travels with it. `auto-ship` is the one destination opening
+ * on a vowel sound, and the corpus spells an article before it once, which is
+ * cheaper to repair by hand than to state as a rule the rest of the map never
+ * fires.
+ *
+ * The map's own module and its test state the rename rather than using the old
+ * names, so a sweep over them turns each key into its own replacement and
+ * leaves a rewriter that matches nothing. The changelog and an eval transcript
+ * are excluded on the argument the `aitk` preset already carries: each records
+ * what shipped or what a session ran under whatever name was current then, so
+ * rewriting one makes it testify to a release or a run that never happened.
+ *
+ * The record archives need no entry here. They are gitignored, so the tracked
+ * listing every sweep reads never reaches them.
+ */
+export const SKILL_NAME_RULES: RenameRules = defineRenameRules({
+  replacements: SKILL_NAME_MAP,
+  keepMarker: 'canon-keep-retired',
+  wholeToken: true,
+  excludedPrefixes: ['scripts/eval/result-'],
+  excludedPaths: [
+    'CHANGELOG.md',
+    'src/migrate/skill-names.ts',
+    'src/migrate/skill-names.test.ts',
+  ],
+})

package/src/pr/bijection.ts

@@ -99,7 +99,7 @@ function owesNoBullet(path: string): boolean {
  * names.
  *
  * An unanchored claim matches on a segment-anchored suffix, which is what lets
- * `claude-worker/SKILL.md` credit `claude/skills/claude-worker/SKILL.md`. That
+ * `role-worker/SKILL.md` credit `claude/skills/role-worker/SKILL.md`. That
  * asymmetry is deliberate: a partial spelling can confirm a changed file was
  * named and never accuse one of being absent, because nothing here separates a
  * path written short from a path written wrong.

package/src/pr/paths.ts

@@ -20,7 +20,7 @@ export interface PathClaim {
    * True when the first segment names an entry the tree actually holds.
    *
    * An unanchored claim is a path written partially, such as
-   * `claude-worker/SKILL.md` for a file under `claude/skills/`. It can confirm
+   * `role-worker/SKILL.md` for a file under `claude/skills/`. It can confirm
    * that a changed file was named and can never accuse one of being absent,
    * because the comparison has no way to tell a partial spelling from a
    * genuinely wrong one.
@@ -145,7 +145,7 @@ function maskSpans(text: string): string {
  * that came out. A path past the comma was left out of the claim set entirely
  * and fell to the unnamed direction, accepted here on the ground that the
  * direction reports without grading. It graded anyway, one consumer removed:
- * `claude-pr-review` reads `unnamed` as a question to put to the branch author,
+ * `review-pr` reads `unnamed` as a question to put to the branch author,
  * and on 2026-09-01 the question went to three pull requests over bullets that
  * had named the files all along, with `#1329` gaining bullets it did not need.
  *

package/src/shipped/references.ts

@@ -61,7 +61,7 @@ export const REFERENCE_MARKER = 'canon-allow-reference'
  * The leading boundary is what excludes the repair form by construction rather
  * than by exemption, and that is load bearing. A lookbehind rejecting a word
  * character before `#` never matches `erclx/canon#1299`, so a qualified
- * reference passes with no marker, and `claude/skills/claude-worktree/SKILL.md`
+ * reference passes with no marker, and `claude/skills/session-worktree/SKILL.md`
  * already ships `anthropics/claude-code#58345` in exactly that form.
  *
  * The trailing boundary is what the first shape of this pattern lacked, and it

package/src/sync/seeds-report.ts

@@ -34,7 +34,7 @@ export interface SeedsReport {
  * Classifies every seed the toolkit ships against the target's copy, and never
  * returns a change. Seeds are copy-once files a project is expected to edit, so
  * the engine's copy path would overwrite `CLAUDE.md` wholesale. Reporting alone
- * is what lets `claude-seed-sync` merge one section at a time instead.
+ * is what lets `seed-sync` merge one section at a time instead.
  *
  * Attribution reuses the history reader rather than the engine's own recovery
  * pass, which is private and takes a `SyncAdapter` seeds have no way to supply.

package/src/targets/pulls.ts

@@ -7,8 +7,8 @@ const GH_TIMEOUT_MS = 30_000
 /**
  * The two headings a review pass posts under.
  *
- * Owned by `claude-pr-review`, which states the full set once, and pinned here
- * the way `claude-orchestrate/scripts/poll.sh` pins them. All three surfaces
+ * Owned by `review-pr`, which states the full set once, and pinned here
+ * the way `role-orchestrator/scripts/poll.sh` pins them. All three surfaces
  * ship separately, so a heading added in that skill goes stale here with
  * nothing comparing the copies.
  */

package/src/tasks/answers.ts

@@ -186,7 +186,7 @@ export function resolvePlanReference(
   }
 
   // An archived plan answers every question and would report as launchable, so
-  // the name would clear a dispatch that `claude-autoship` Step 1 then refuses
+  // the name would clear a dispatch that `auto-ship` Step 1 then refuses
   // as already-shipped work. Catching it here is a step earlier than the worker.
   // Both roots, for the reason `resolveLivePlan` carries: the reference is a
   // string a caller wrote, and one spelling the root this tree has since left is

package/src/tasks/archive.ts

@@ -269,7 +269,7 @@ function isRowFor(line: string, target: string): boolean {
 
 /**
  * Resolves the `Plan:` target against the board and against the project root
- * both, which is how `claude-docs` reads the same line. It accepts `../plans/x.md`
+ * both, which is how `docs-fold` reads the same line. It accepts `../plans/x.md`
  * and `.canon/plans/x.md` as one file, so a gate reading only the first form
  * would pass the second and strand the plan this exists to protect.
  *
@@ -323,7 +323,7 @@ function atOneRoot(path: string, plans: string[], root: string): string {
 
 /**
  * Names the other live tasks whose `Plan:` line lands on the same file. This is
- * the rule `claude-docs` applies before it archives a plan, held here so one
+ * the rule `docs-fold` applies before it archives a plan, held here so one
  * question has one implementation: a plan another live task still cites is a
  * plan the sweep is correct to leave, and a guard that read the folder instead
  * refused every task sharing one plan and deadlocked the board against the
@@ -380,7 +380,7 @@ export type CitationOutcome = PlanCitations | ArchiveRefused
 
 /**
  * Answers where one task's plan sits and who else holds it, which is the whole
- * of the last-live-citation rule. `claude-docs` reads this rather than scanning
+ * of the last-live-citation rule. `docs-fold` reads this rather than scanning
  * the board itself, so the sweep that moves a plan and the gate that refuses a
  * task archive cannot drift into disagreeing about which plan is free.
  *
@@ -564,7 +564,7 @@ async function resolveStem(
 
 /**
  * Archives one task as a single unit: the move, the ordering-row removal, and
- * the index regen. The hook and `claude-tasks` both call this, so every gate
+ * the index regen. The hook and `task-board` both call this, so every gate
  * refuses rather than reports. A caller with nobody watching cannot act on a
  * warning, and two callers gating differently is the drift this exists to stop.
  */

package/src/tasks/record.ts

@@ -311,7 +311,7 @@ export async function recordPullRequest(
 
 /**
  * Records a plan's path on the task it belongs to, as the task's `Plan:` line.
- * `claude-feature` runs this right after the plan file lands, resolving the
+ * `plan-feature` runs this right after the plan file lands, resolving the
  * reference the same two ways `canon tasks plan-answers` does, through
  * `planCandidates`, so a bare slug and a board-relative path both resolve.
  *
@@ -346,7 +346,7 @@ export async function recordPlan(
 }
 
 /**
- * Marks the named outcomes `[x]` in place. `claude-docs` runs this against a
+ * Marks the named outcomes `[x]` in place. `docs-fold` runs this against a
  * board it can read and cannot edit from a linked worktree, and the positions
  * come from the read it already made.
  */

package/src/tasks/validate.ts

@@ -557,7 +557,7 @@ async function listTaskStems(dir: string): Promise<string[]> {
 
 /**
  * Resolves a pointer against the board and against the project root both, the
- * way `claude-docs` reads the same line. A fragment is dropped first, since an
+ * way `docs-fold` reads the same line. A fragment is dropped first, since an
  * anchor is part of the link and never part of the path.
  */
 function resolves(target: string, dir: string, root: string): boolean {