@erclx/canon 4.67.0 → 4.69.0

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