@erclx/canon 4.67.0 → 4.68.0

package/src/claude/cases/{claude-workflow.ts → workflow.ts}

@@ -1,8 +1,8 @@
 import type { SkillCase } from '@/claude/skills-rank'
 
 /**
- * The `claude-*` skill family: feature planning, review, and the session
- * artifacts that coordinate work across sessions.
+ * The session workflow skills: feature planning, review, and the artifacts
+ * that coordinate work across sessions.
  *
  * Every positive is phrased away from its skill's own quoted trigger, since a
  * verbatim trigger passes by construction and proves nothing about a prompt in
@@ -10,33 +10,33 @@ import type { SkillCase } from '@/claude/skills-rank'
  * an explicit `Do NOT` boundary against each other, since a boundary in a
  * body does not reach the field a router reads.
  */
-export const CLAUDE_WORKFLOW_CASES: readonly SkillCase[] = [
+export const WORKFLOW_CASES: readonly SkillCase[] = [
   {
     prompt: 'Go fix everything the reviewer flagged on my open PR.',
-    expect: 'claude-address-review',
+    expect: 'review-address',
   },
   {
     prompt:
       'Run the whole implement, verify, review, and ship pipeline for the approved plan.',
-    expect: 'claude-autoship',
+    expect: 'auto-ship',
   },
   {
     prompt: "Pull together a design system from what's already in the app.",
-    expect: 'claude-design-extract',
+    expect: 'design-extract',
   },
   {
     prompt: 'Draw me a diagram of how the pieces of this system connect.',
-    expect: 'claude-diagram',
+    expect: 'draft-diagram',
   },
   {
     prompt:
       'Bring the internal planning docs under .claude up to date with what we decided this session.',
-    expect: 'claude-docs',
+    expect: 'docs-fold',
   },
   {
     prompt:
       'Sketch out a plan for adding this new capability before we touch any code.',
-    expect: 'claude-feature',
+    expect: 'plan-feature',
   },
   {
     prompt:
@@ -46,43 +46,43 @@ export const CLAUDE_WORKFLOW_CASES: readonly SkillCase[] = [
   {
     prompt:
       'We need to measure this properly before committing to an approach.',
-    expect: 'claude-groundwork',
+    expect: 'plan-groundwork',
   },
   {
     prompt: 'Take this pile of raw notes and turn it into filed items.',
-    expect: 'claude-intake',
+    expect: 'plan-intake',
   },
   {
     prompt: 'Walk me through the open intake items so I can decide on each.',
-    expect: 'claude-intake-answer',
+    expect: 'plan-intake-answer',
   },
   {
     prompt:
       "Draft a diff-based proposal for tightening this passage in the standard, don't just edit it.",
-    expect: 'claude-markdown-propose',
+    expect: 'markdown-propose',
   },
   {
     prompt: 'Pull the durable lessons out of this session before it ends.',
-    expect: 'claude-memory-capture',
+    expect: 'memory-capture',
   },
   {
     prompt:
       'Go through the memory folder and propose what to do with each entry.',
-    expect: 'claude-memory-review',
+    expect: 'memory-review',
   },
   {
     prompt:
       'Take on the orchestrator role and coordinate the parallel feature builds.',
-    expect: 'claude-orchestrate',
+    expect: 'role-orchestrator',
   },
   {
     prompt:
       'I am writing the plan for a row another session will build. What may I write, and where do I read what is already in flight?',
-    expect: 'claude-planner',
+    expect: 'role-planner',
   },
   {
     prompt: 'Post a formal review with findings on that open pull request.',
-    expect: 'claude-pr-review',
+    expect: 'review-pr',
   },
   {
     prompt:
@@ -92,7 +92,7 @@ export const CLAUDE_WORKFLOW_CASES: readonly SkillCase[] = [
   {
     prompt:
       'Look over everything that changed on this branch for bugs and edge cases.',
-    expect: 'claude-review',
+    expect: 'review-branch',
   },
   {
     prompt: 'Draft me a script with beats for a screencast recording.',
@@ -101,7 +101,7 @@ export const CLAUDE_WORKFLOW_CASES: readonly SkillCase[] = [
   {
     prompt:
       "Check whether my installed Claude seed docs have drifted from the toolkit's.",
-    expect: 'claude-seed-sync',
+    expect: 'seed-sync',
   },
   {
     prompt: 'Turn this topic into a slide deck I can render.',
@@ -110,37 +110,37 @@ export const CLAUDE_WORKFLOW_CASES: readonly SkillCase[] = [
   {
     prompt:
       'Check whether the markdown I changed violates any authoring standards.',
-    expect: 'claude-standards-audit',
+    expect: 'standards-audit',
   },
   {
     prompt: 'Open a new entry on the task board for this piece of work.',
-    expect: 'claude-tasks',
+    expect: 'task-board',
   },
   {
     prompt: 'Open a learning workspace so I can study this topic properly.',
-    expect: 'claude-teach',
+    expect: 'teach-workspace',
   },
   {
     prompt: 'Generate the Playwright tests I need after this UI change.',
-    expect: 'claude-ui-test',
+    expect: 'ui-test',
   },
   {
     prompt:
       'Look over the interface and tell me what feels unfinished or confusing.',
-    expect: 'claude-ux-audit',
+    expect: 'ux-audit',
   },
   {
     prompt: 'Tell me the paint and layout cost of this page right now.',
-    expect: 'claude-ux-measure',
+    expect: 'ux-measure',
   },
   {
     prompt:
       'I am building this branch for another session. What am I on the hook for, and what is off limits?',
-    expect: 'claude-worker',
+    expect: 'role-worker',
   },
   {
     prompt: 'Get me set up in a fresh Claude Code worktree for this branch.',
-    expect: 'claude-worktree',
+    expect: 'session-worktree',
   },
 
   // Negatives: pairs whose bodies already carry an explicit Do NOT boundary.
@@ -151,23 +151,23 @@ export const CLAUDE_WORKFLOW_CASES: readonly SkillCase[] = [
   },
   {
     prompt: 'Sort through this brain dump and write it up as findings.',
-    expect: 'claude-intake',
+    expect: 'plan-intake',
   },
   {
     prompt:
       "Go through what's still unanswered in the intake folder and decide.",
-    expect: 'claude-intake-answer',
+    expect: 'plan-intake-answer',
   },
   {
     prompt: 'Check this markdown against the house style rules.',
-    expect: 'claude-standards-audit',
+    expect: 'standards-audit',
   },
   {
     prompt: 'Find the rough, unfinished-feeling spots in this interface.',
-    expect: 'claude-ux-audit',
+    expect: 'ux-audit',
   },
   {
     prompt: 'Tell me the render cost of this page in the browser.',
-    expect: 'claude-ux-measure',
+    expect: 'ux-measure',
   },
 ]

package/src/commands/sync.ts

@@ -265,7 +265,7 @@ function renderTooling(report: CheckReport): void {
 /**
  * Seeds print their own section because no sync command applies them. A `stale`
  * seed is safe to take whole and a `drifted` one holds edits, which is the split
- * `claude-seed-sync` reads to decide what needs a section-level merge.
+ * `seed-sync` reads to decide what needs a section-level merge.
  */
 function renderSeeds(report: CheckReport): void {
   const notable = report.seeds.entries.filter(
@@ -283,7 +283,7 @@ function renderSeeds(report: CheckReport): void {
     logWarn(`${entry.rel} (${entry.state})`)
   }
 
-  logInfo('Run /canon:claude-seed-sync to reconcile these section by section.')
+  logInfo('Run /canon:seed-sync to reconcile these section by section.')
 }
 
 /**
@@ -399,7 +399,7 @@ async function runSync(target: string): Promise<number> {
 
   if (existsSync(join(resolved, '.claude'))) {
     process.stderr.write(
-      `${GREY}Tip: run \`/claude-seed-sync\` to audit seed drift per section, preserving local customizations.${NC}\n`,
+      `${GREY}Tip: run \`/seed-sync\` to audit seed drift per section, preserving local customizations.${NC}\n`,
     )
   }
 

package/src/design/tokens.ts

@@ -354,7 +354,7 @@ export const TOKENS: DesignTokens = {
     'Motion is not used. No transition, animation, or keyframe declaration appears on any rendered surface, and the capture pipeline screenshots a static frame.',
 
   iconography:
-    "No icon library is installed. `assets/brand/mark.svg` is the one authored icon, embedded inline in the hero topbar, and the surfaces otherwise draw literal glyph characters: `│ ├ ✓ ! ✗ + - ◆ ◇ ❯` for the terminal framing. The same mark also ships as a favicon on every rendered surface, as three independently-maintained copies that track different accents by design rather than by drift: `regen-hero.sh` derives one from the live SVG colored with whatever `--color-accent` (`#e0724b`) the fetched token CSS carries, `src/design/render.ts` carries the path data as a hardcoded literal colored via `colorValue('light-accent')` (`#a4471c`), since a data URI has no CSS context and that page renders on light chrome, and `claude-teach`'s `SKILL.md` names one in prose colored `rgb(224,114,75)`, the same value as the dark accent written as decimal rather than hex to clear the shipped-references gate's commit-sha check. Unifying the three or repairing the one that looks drifted would break the fit each was chosen for.",
+    "No icon library is installed. `assets/brand/mark.svg` is the one authored icon, embedded inline in the hero topbar, and the surfaces otherwise draw literal glyph characters: `│ ├ ✓ ! ✗ + - ◆ ◇ ❯` for the terminal framing. The same mark also ships as a favicon on every rendered surface, as three independently-maintained copies that track different accents by design rather than by drift: `regen-hero.sh` derives one from the live SVG colored with whatever `--color-accent` (`#e0724b`) the fetched token CSS carries, `src/design/render.ts` carries the path data as a hardcoded literal colored via `colorValue('light-accent')` (`#a4471c`), since a data URI has no CSS context and that page renders on light chrome, and `teach-workspace`'s `SKILL.md` names one in prose colored `rgb(224,114,75)`, the same value as the dark accent written as decimal rather than hex to clear the shipped-references gate's commit-sha check. Unifying the three or repairing the one that looks drifted would break the fit each was chosen for.",
 }
 
 /** A role's value, or `undefined` where the record declares no such role. */

package/src/gov/restated.ts

@@ -24,7 +24,7 @@ export const RULES_REL = join('governance', 'rules')
 /**
  * Path pairs whose duplication is deliberate and already recorded.
  *
- * The seed is authored from the always-loaded file and `claude-seed-sync`
+ * The seed is authored from the always-loaded file and `seed-sync`
  * exists to reconcile the two, so a bullet appearing in both is the design
  * rather than a defect. Excluding by pair rather than by content is what the
  * plan settled on: the duplication is a location fact this repository already
@@ -574,7 +574,7 @@ function authorityFor(
   if (candidate.kind === 'seed') {
     return {
       authority: 'claude-md',
-      reason: `${INSTRUCTIONS_REL} is authored first and the seed carries it to a target, so an edit starts there and reaches the seed through claude-seed-sync`,
+      reason: `${INSTRUCTIONS_REL} is authored first and the seed carries it to a target, so an edit starts there and reaches the seed through seed-sync`,
     }
   }
 

package/src/markdown/structure.ts

@@ -26,7 +26,7 @@ const HEADING = /^#{1,6}\s/
  * run and a false one shortens every run around it until the measure stops
  * reporting, which is the dearer of the two.
  *
- * A colon ends most markers and not all of them. `claude-pr-review` writes
+ * A colon ends most markers and not all of them. `review-pr` writes
  * three colon-less ones into every body it posts and a bold path heading for
  * each file it reviews, so requiring the colon held a real seam out. Two
  * signals stand in where the colon is absent, because the shape a marker has to

package/src/migrate/rename.ts

@@ -46,8 +46,9 @@ export interface RenameRuleSpec {
    * A rename whose tokens are whole names wants this, and one whose tokens are
    * word stems cannot have it. `aitk` is a stem that legitimately carries a
    * suffix, as in `aitk-allow-superseded`, so requiring a boundary there would
-   * leave every hyphenated form behind. A skill name is not a stem, and
-   * `claude-worktree` inside `claude-worktrees` is a different subject: the
+   * leave every hyphenated form behind. A skill name is not a stem, and the
+   * spelling below is the pre-rename one on purpose (canon-keep-retired):
+   * `claude-worktree` inside `claude-worktrees` is a different subject, the
    * wiki page about the harness feature, which the rename must not move.
    */
   readonly wholeToken?: boolean
@@ -88,7 +89,7 @@ const NEVER_MATCHES = '(?!)'
  *
  * A plain word boundary rejects a following letter and accepts a following
  * hyphen, since `\b` reads a hyphen as the end of a word. That leaves
- * `claude-intake` matching inside `claude-intake-answer`, with the ordering of
+ * `plan-intake` matching inside `plan-intake-answer`, with the ordering of
  * the alternation the only thing standing between them. Naming the characters
  * that continue an identifier holds on both, so the ordering and the boundary
  * each cover what the other could miss, and a slash, a dot, or a backtick

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 {

package/standards/groundwork.md

@@ -156,7 +156,7 @@ A lean is weaker than the suggestion a plan file carries. It records the current
 ## Conventions
 
 - State a number with what it settles. The strongest sections are the ones where a measurement answers a named question and says so.
-- Route a finding that would change an existing standard or rule through `claude-intake`. Only a demonstrated failure changes one.
+- Route a finding that would change an existing standard or rule through `plan-intake`. Only a demonstrated failure changes one.
 - Let the file count follow the number of genuinely separable questions, not the importance of the topic. A large topic with one question is a small folder.
 
 ## Anti-patterns

package/standards/snippets.md

@@ -38,7 +38,7 @@ Overlapping a skill that does the same job is not disqualifying on its own. A sn
 ## Use patterns
 
 - Run-as-is: invoke and send immediately. The snippet is self-contained and needs no extra context.
-- Invoke-then-add-context: invoke the snippet, then append specifics in the same message (e.g. invoke `claude-feature`, then add the feature name or extra constraints)
+- Invoke-then-add-context: invoke the snippet, then append specifics in the same message (e.g. invoke `plan-feature`, then add the feature name or extra constraints)
 - Invoke-on-history: invoke after a discussion. The snippet uses prior conversation as implicit context with no additional input needed (e.g. invoke `claude-figma` after discussing a design).
 
 ## Authoring

package/standards/tasks.md

@@ -47,7 +47,7 @@ The handoff takes one file per session for the reason a task does. A single shar
 
 The catalog is the one reader that filters nothing, so it carries a row per sibling alongside the tasks. That is what a folder catalog is for, and the handoffs are what make it worth stating: a board accumulates one row per session that ever wrote one, with nothing pruning them. Anything reading the catalog as the backlog therefore does its own filtering, and a reader that takes every row as a task reports the handoffs as queued work.
 
-The `claude-tasks` skill creates and archives task files, and the archive carries the task's plan with it. `claude-docs` marks outcomes `[x]` in an existing file. Neither does the other's job.
+The `task-board` skill creates and archives task files, and the archive carries the task's plan with it. `docs-fold` marks outcomes `[x]` in an existing file. Neither does the other's job.
 
 ## Ordering
 
@@ -219,9 +219,9 @@ A project that archived plans before the folder nested under `.canon/plans/` hol
 
 One plan per task. A plan cited by two tasks is a misfile rather than a shape to design for, which is why the sweep counts citations before archiving: the count is a guard against the misfile stranding a pointer, not support for the shape.
 
-`canon tasks plan-link <task> <plan>` writes or corrects the `Plan:` line, mirroring how `canon tasks pull-request` writes its own. `claude-feature` calls it right after the plan file lands, when an existing task names the feature, so the line is a mechanical write rather than hand-edited markdown.
+`canon tasks plan-link <task> <plan>` writes or corrects the `Plan:` line, mirroring how `canon tasks pull-request` writes its own. `plan-feature` calls it right after the plan file lands, when an existing task names the feature, so the line is a mechanical write rather than hand-edited markdown.
 
-`Groundwork:` points at `../groundwork/<slug>/`, the folder `claude-groundwork` fills. It names the surface it points at the way `Plan:` does. Use this key alone. `Research record` and `Decision record` are earlier spellings of the same thing and both convert to it.
+`Groundwork:` points at `../groundwork/<slug>/`, the folder `plan-groundwork` fills. It names the surface it points at the way `Plan:` does. Use this key alone. `Research record` and `Decision record` are earlier spellings of the same thing and both convert to it.
 
 `Intake:` points at `../intake/<slug>/`, the folder an intake pass fills. Use it rather than `Groundwork:`, because a groundwork track measures one question in depth while an intake dispositions many across a tree, and one key covering both loses which kind of pass produced the task. The line names the folder rather than an item inside it. A task routinely promotes several items at once, so an anchored line would name one and drop the rest, and the item numbers belong in that task's `## Findings`.
 

package/standards/teach.md

@@ -15,7 +15,7 @@ Governs a learning workspace under `.canon/teach/<nn>-<topic>/`: folder layout,
 
 Does not govern:
 
-- The frontmatter, entry shape, and ordering of the glossary the workspace holds: the `claude-teach` skill, which carries that reference
+- The frontmatter, entry shape, and ordering of the glossary the workspace holds: the `teach-workspace` skill, which carries that reference
 - What a lesson teaches, how it sequences difficulty, and what makes one worth returning to, which belong to the surface driving the workspace
 - Where a durable page goes once it leaves the workspace, which belongs to the routing test the destination surface states
 - One question measured in depth before anyone can plan against it: `groundwork.md`
@@ -113,7 +113,7 @@ Take the date and the rung from what the surface driving the workspace reports r
 
 ## GLOSSARY.md
 
-Required in every workspace, holding one entry per term the subject defines. The glossary reference the `canon:claude-teach` skill carries fixes what an entry looks like, how the file orders and groups them, and which terms it carries, so this standard states only that the file exists and sits at the workspace root. That reference ships with the plugin rather than installing here, because a promoted glossary keeps its shape wherever it lands and no project folder covers every destination. Say so and stop rather than working the shape from memory when the project has no plugin to read it from.
+Required in every workspace, holding one entry per term the subject defines. The glossary reference the `canon:teach-workspace` skill carries fixes what an entry looks like, how the file orders and groups them, and which terms it carries, so this standard states only that the file exists and sits at the workspace root. That reference ships with the plugin rather than installing here, because a promoted glossary keeps its shape wherever it lands and no project folder covers every destination. Say so and stop rather than working the shape from memory when the project has no plugin to read it from.
 
 Name the lesson or reference page a term first appears in as that reference requires. A workspace is the case it was written for, so a glossary here has a first appearance to name.
 

package/tooling/base/configs/.husky/post-merge

@@ -7,10 +7,10 @@
 # to hand a worker. This is the only event that lands after a merge.
 #
 # Candidates rather than closed tasks, because an all-`[x]` board entry does not
-# mean the work merged. `claude-docs` marks outcomes on the branch as step 1 of
+# mean the work merged. `docs-fold` marks outcomes on the branch as step 1 of
 # the ship chain, so a task can read closed while its pull request is still open
 # or already abandoned. The board is gitignored and an archived task has nothing
-# to recover it, so `claude-tasks` confirms the work is on `main` before moving
+# to recover it, so `task-board` confirms the work is on `main` before moving
 # anything and this output says so rather than implying the check is done.
 #
 # It announces and never moves a file. The board is gitignored, so a shell-side
@@ -58,4 +58,4 @@ done
 
 printf '\n📋 %s archive candidate(s) on the board:\n%s\n' "$count" "$closed"
 printf 'Outcomes are marked on the branch, so each still needs its work confirmed\n'
-printf 'on main. Run /claude-tasks, which checks that and sweeps the plan first.\n\n'
+printf 'on main. Run /task-board, which checks that and sweeps the plan first.\n\n'

package/tooling/claude/reference.md

@@ -20,8 +20,8 @@ The claude stack installs the `.claude/` workflow directory into a project. Stat
 .canon/
 ├── tasks/             ← seeded. One file per task plus a generated index.md, local scratch only. `archive/` holds the tasks that shipped.
 ├── diagrams/          ← seeded. Per-kind Mermaid views. `index.md` is the discovery anchor. `<kind>.md` files hold one diagram each, grouped by the `category` frontmatter field.
-├── plans/             ← execution detail for multi-step tasks. `feature-*.md` entries swept by claude-docs into `archive/`.
-├── review/            ← one subfolder per producer. `branch/` for claude-review, `feedback/` for canon feedback, `memory/` for claude-memory-review with its own `archive/`, `design/` for canon design render.
+├── plans/             ← execution detail for multi-step tasks. `feature-*.md` entries swept by docs-fold into `archive/`.
+├── review/            ← one subfolder per producer. `branch/` for review-branch, `feedback/` for canon feedback, `memory/` for memory-review with its own `archive/`, `design/` for canon design render.
 ├── tmp/               ← ephemeral scratch space, safe to delete without loss
 └── memory/            ← session facts no context entry owns. `index.md` regenerated by a hook.
 ```
@@ -48,7 +48,7 @@ Convert by hand, once per project:
 
 ## Upgrading a hand-appended memory index
 
-A project installed before the memory folder gained a generated index still holds `.canon/memory/MEMORY.md`, and its entries still carry `name` and `type` frontmatter. Nothing migrates it. `claude-memory-capture` stops appending rows once the new seed lands, so the old file freezes at whatever it held while the folder keeps growing past it.
+A project installed before the memory folder gained a generated index still holds `.canon/memory/MEMORY.md`, and its entries still carry `name` and `type` frontmatter. Nothing migrates it. `memory-capture` stops appending rows once the new seed lands, so the old file freezes at whatever it held while the folder keeps growing past it.
 
 Convert by hand, once per project:
 
@@ -58,7 +58,7 @@ Convert by hand, once per project:
 
 ## Upgrading from a single-file diagram set
 
-A project installed before the diagram surface became a folder still holds `.claude/DIAGRAMS.md`. Unlike the board, this one migrates itself. The `claude-diagram` skill reads the flat file when `.canon/diagrams/` holds no entries, splits it by kind into the folder, and reports what it wrote. The old file stays on disk so the split can be compared against its source, and deleting it is a manual step once that check passes.
+A project installed before the diagram surface became a folder still holds `.claude/DIAGRAMS.md`. Unlike the board, this one migrates itself. The `draft-diagram` skill reads the flat file when `.canon/diagrams/` holds no entries, splits it by kind into the folder, and reports what it wrote. The old file stays on disk so the split can be compared against its source, and deleting it is a manual step once that check passes.
 
 ## Gitignore
 
@@ -79,7 +79,7 @@ The first entry covers the whole record root, so a record folder added later nee
 - Ships as a seed with placeholder project name, description, and key paths. Fill these in after init.
 - Section layout: `Context`, `Indexes`, `Markdown`, `Key paths`, `Spelling`, `Snippets`, `Tasks`, `Memory`. Each section groups rules that share a surface so skills can detect, extend, or skip by heading.
 - The memory rules favor signal over volume. Saving only after a second occurrence or an explicit user correction keeps entries focused on patterns worth preventing, not first-occurrence slips. The 3-line cap stops the built-in auto-memory from drifting into narrative writeups that bury the rule underneath the recovery story.
-- The `Context` section points at `.claude/` state docs one line. `claude-feature` does the parallel read when invoked. The seed intentionally does not re-list every file.
+- The `Context` section points at `.claude/` state docs one line. `plan-feature` does the parallel read when invoked. The seed intentionally does not re-list every file.
 
 ## Seed docs
 

package/tooling/claude/seeds/.claude/hooks/pr-create-log.sh

@@ -1,7 +1,7 @@
 #!/usr/bin/env bash
 
 # Reminds a worker session of the pull-request announcement it owes and logs
-# the creation as a denominator for the miss rate `claude-worker` cannot
+# the creation as a denominator for the miss rate `role-worker` cannot
 # measure on its own. Follows path-form.sh's precedent: a PostToolUse hook
 # returning hookSpecificOutput.additionalContext is the shipped route back
 # into a session's own turn.
@@ -51,5 +51,5 @@ mkdir -p "$log_dir"
 session=$(printf '%s' "$input" | jq -r '.session_id // "unknown"')
 printf -- '- %s session=%s pr=%s\n' "$(date -u +%Y-%m-%dT%H:%M:%SZ)" "$session" "$url" >>"$log_dir/log.md"
 
-msg="Pull request $url just opened. If this session holds a worker's channel obligation, announce it to the controller now, per claude-worker."
+msg="Pull request $url just opened. If this session holds a worker's channel obligation, announce it to the controller now, per role-worker."
 jq -nc --arg msg "$msg" '{hookSpecificOutput:{hookEventName:"PostToolUse",additionalContext:$msg}}'