npm - @erclx/canon - Versions diffs - 4.66.0 → 4.68.0 - Mend

@erclx/canon 4.66.0 → 4.68.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (156) hide show

package/src/teach/nav.ts CHANGED Viewed

@@ -1,8 +1,10 @@
 import { existsSync } from 'node:fs'
 import { readFile, writeFile } from 'node:fs/promises'
 import { join, relative } from 'node:path'
+import { TEACH_STYLESHEET_COMPONENTS } from '@/design/components'
 import { buildDesignCss } from '@/design/css'
 import { parseFrontmatter, readField } from '@/indexes/frontmatter'
+import { TEACH_FONT_FACES } from '@/teach/fonts'
 import {
   listWorkspaces,
   readWorkspace,
@@ -500,7 +502,7 @@ function renderRootPage(workspaces: readonly WorkspaceSummary[]): string {
     })
     .join('')
-  return `${pageHead('Learning workspaces', undefined, buildDesignCss(undefined, { embedFonts: true }))}<body>
+  return `${pageHead('Learning workspaces', TEACH_STYLESHEET, undefined)}<body>
 ${renderHeader(segments, track)}
 <main class="wide-body">
@@ -784,6 +786,14 @@ export async function generateNav(
   const rootPath = join(dir, 'index.html')
   await writeFile(rootPath, renderRootPage(listed.workspaces))
+  await writeFile(
+    join(dir, TEACH_STYLESHEET),
+    buildDesignCss(undefined, {
+      embedFonts: TEACH_FONT_FACES,
+      components: TEACH_STYLESHEET_COMPONENTS,
+    }),
+  )
   const contents: string[] = []
   const skipped: LessonSkipped[] = []
   let lessons = 0

package/src/teach/workspace.ts CHANGED Viewed

@@ -1,10 +1,12 @@
 import { existsSync } from 'node:fs'
 import { mkdir, readdir, readFile, writeFile } from 'node:fs/promises'
 import { join, relative } from 'node:path'
+import { TEACH_STYLESHEET_COMPONENTS } from '@/design/components'
 import { buildDesignCss } from '@/design/css'
 import { parseFrontmatter, readField } from '@/indexes/frontmatter'
 import { type BodyLine, bodyLines } from '@/markdown/scan'
 import { recordDir } from '@/record-root'
+import { TEACH_FONT_FACES } from '@/teach/fonts'
 export const TEACH_REFUSALS = [
   'no-teach',
@@ -1046,7 +1048,8 @@ export async function writeStylesheet(
     path,
     buildDesignCss(undefined, {
       banner: STYLESHEET_BANNER,
-      embedFonts: true,
+      embedFonts: TEACH_FONT_FACES,
+      components: TEACH_STYLESHEET_COMPONENTS,
     }),
   )

package/standards/groundwork.md CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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 CHANGED Viewed

@@ -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}}'

/package/claude/skills/{claude-memory-review → memory-review}/references/receipt-format.md RENAMED Viewed

File without changes

/package/claude/skills/{claude-orchestrate → role-orchestrator}/scripts/watch.sh RENAMED Viewed

File without changes

/package/claude/skills/{claude-teach → teach-workspace}/references/lesson-craft.md RENAMED Viewed

File without changes

/package/claude/skills/{claude-teach → teach-workspace}/references/pedagogy.md RENAMED Viewed

File without changes

/package/claude/skills/{claude-teach → teach-workspace}/references/promotion.md RENAMED Viewed

File without changes