@erclx/canon 5.31.0 → 5.33.0

package/src/tasks/branch.ts

@@ -14,10 +14,10 @@ const MARKDOWN = '.md'
  */
 export const PLAN_BRANCH_TYPE = 'feat'
 
-/** The description cap in `standards/branch.md`, in kebab-separated words. */
+/** The description cap in `claude/skills/git-branch/references/branch.md`, in kebab-separated words. */
 export const DESCRIPTION_WORD_CAP = 4
 
-/** The branch length cap in `standards/branch.md`, in characters. */
+/** The branch length cap in `claude/skills/git-branch/references/branch.md`, in characters. */
 export const BRANCH_LENGTH_CAP = 50
 
 export interface PlanBranch {
@@ -48,7 +48,7 @@ function slugOf(path: string): string {
  * of them name. It is the one derivation, so the collision check and the
  * worktree entry it gates cannot hold two answers for one plan.
  *
- * Conformance covers both caps `standards/branch.md` states, being the word
+ * Conformance covers both caps `claude/skills/git-branch/references/branch.md` states, being the word
  * count of the description and the length of the whole branch. A slug is a
  * plan's own filename rather than a name anyone chose for a branch, so a plan
  * can name a branch this refuses to grade as conforming, and reporting that is

package/src/tasks/label.ts

@@ -185,7 +185,7 @@ async function reserveLabel(root: string, label: string): Promise<boolean> {
  * the task file after this returns, so a reservation with no file behind it is
  * the ordinary state for a few seconds, and a scan blind to it would offer the
  * same label to every retry. Reservations are never expired: a claim that died
- * leaves a gap, and `standards/versioning.md` permits gaps.
+ * leaves a gap, and `claude/skills/git-commit/references/versioning.md` permits gaps.
  */
 export async function claimLabel(
   root: string,

package/src/tasks/reach.ts

@@ -11,7 +11,7 @@ const PLANS = 'plans'
 const MARKDOWN = '.md'
 const NONE_IDENTIFIED = 'None identified.'
 
-/** The one group a dispatch reads, per `standards/board.md`. */
+/** The one group a dispatch reads, per `claude/skills/task-board/references/board.md`. */
 const DISPATCH_GROUP = 'Run now'
 
 export const REACH_REFUSALS = [
@@ -146,7 +146,7 @@ function namesFile(span: string): boolean {
  * An entry carrying no colon at all is taken whole. The standard requires a
  * reason rather than the punctuation introducing it, so the alternative is
  * reading such an entry as declaring nothing, which reports every path it
- * names as undeclared. `standards/plan.md` fixes the colon form, so the
+ * names as undeclared. `claude/skills/plan-feature/references/plan.md` fixes the colon form, so the
  * conforming entry never reaches this fallback.
  *
  * A rename declares both sides, since both are paths the branch writes and

package/src/tasks/record.ts

@@ -420,7 +420,7 @@ async function openTask(
  * resolve the board root in-process.
  *
  * `branches` names the recording branch and every name it carried before a
- * rename, since `git-ship` renames a branch after `context-fold` has already
+ * rename, since `git-ship` renames a branch after `task-complete` has already
  * written the marker under the old name. Each comes off the `Pending branch:`
  * line even when the number was already listed, so a rerun repairs a stale
  * marker.
@@ -504,7 +504,7 @@ export async function recordPlan(
 }
 
 /**
- * Marks the named outcomes `[x]` in place. `context-fold` runs this against a
+ * Marks the named outcomes `[x]` in place. `task-complete` 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

@@ -18,7 +18,7 @@ const ORDERING_FILE = 'priority.md'
 const BACKLOG_FILE = 'backlog.md'
 
 /**
- * The readiness headings `standards/board.md` fixes. The names are the
+ * The readiness headings `claude/skills/task-board/references/board.md` fixes. The names are the
  * contract rather than a suggestion, so a board grouping under names of its own
  * reads as carrying no group at all and the run refuses instead of reporting a
  * clean board it never parsed.
@@ -597,7 +597,7 @@ async function listTaskStems(dir: string): Promise<string[]> {
 
 /**
  * Resolves a pointer against the board and against the project root both, the
- * way `context-fold` reads the same line. A fragment is dropped first, since an
+ * way `task-complete` 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/src/teach/workspace.ts

@@ -30,7 +30,7 @@ export interface TeachRefused {
   readonly detail: readonly string[]
 }
 
-/** The files and folders `standards/teach.md` fixes for a workspace. */
+/** The files and folders `claude/skills/teach-workspace/references/teach.md` fixes for a workspace. */
 export const TEACH_MISSION = 'MISSION.md'
 export const TEACH_RESOURCES = 'RESOURCES.md'
 export const TEACH_GLOSSARY = 'GLOSSARY.md'

package/src/upstream/cursor.ts

@@ -73,7 +73,7 @@ export function compareVersions(a: string, b: string): number {
 
 // `fetch` reads this file, so a write that half-lands would leave a reader on a
 // truncated cursor. A rename within one folder is atomic.
-async function writeAtomic(path: string, body: string): Promise<void> {
+export async function writeAtomic(path: string, body: string): Promise<void> {
   mkdirSync(dirname(path), { recursive: true })
   const temp = `${path}.${process.pid}.tmp`
   writeFileSync(temp, body)

package/src/upstream/due.ts

@@ -0,0 +1,128 @@
+import { existsSync, readFileSync } from 'node:fs'
+import { recordDir, SCRATCH } from '@/roots/record'
+import { compareVersions, writeAtomic, type Cursor } from '@/upstream/cursor'
+
+const DAY_MS = 86_400_000
+const DUE_AFTER_DAYS = 7
+
+// Ported from the groundwork's pre-filter script. It names canon's own surfaces,
+// so an Added line matching it is one a digest would act on.
+const VOCABULARY =
+  /plugin|skill|hook|SendMessage|ListAgents|agent view|agents view|worktree|subagent|background|routine|schedule|Monitor|mod\b|mods\b|CLAUDE\.md|rules|memory|permission|auto mode|stream-json|--bg|headless|-p\b|marketplace|session/i
+const ADDED = /^Added/
+const CACHE_MAX_AGE_MS = DAY_MS
+
+/** What the gap between the cursor and the installed version holds. */
+export interface Gap {
+  readonly releases: number
+  readonly lines: readonly string[]
+}
+
+export interface DueInput {
+  /** The installed Claude Code version, or null when it could not be read. */
+  readonly installed: string | null
+  readonly cursor: Cursor | null
+  /** Null when the feed was not read, so only the age path can decide. */
+  readonly gap: Gap | null
+  readonly now: Date
+}
+
+export type DueReason =
+  | 'no-cursor'
+  | 'week'
+  | 'vocabulary'
+  | 'current'
+  | 'recent'
+  | 'unknown-version'
+
+export interface DueResult {
+  readonly due: boolean
+  readonly reason: DueReason
+  /** Releases in the gap, or null when it was not read. */
+  readonly releases: number | null
+}
+
+export function passesVocabulary(line: string): boolean {
+  return ADDED.test(line) && VOCABULARY.test(line)
+}
+
+// A cursor date is a calendar day with no time, read at UTC midnight. An
+// unreadable one gives NaN, which fails the age test and leaves the vocabulary
+// path to decide.
+function ageInDays(date: string, now: Date): number {
+  return (now.getTime() - Date.parse(`${date}T00:00:00Z`)) / DAY_MS
+}
+
+/**
+ * Decides whether a digest is due.
+ *
+ * The age boundary is inclusive: a cursor exactly seven days old is due, since
+ * a week has passed. An installed version at or below the cursor is never due,
+ * which covers a downgrade as well as a run straight after a digest.
+ */
+export function decideDue(input: DueInput): DueResult {
+  const { installed, cursor, gap, now } = input
+  const releases = gap?.releases ?? null
+
+  if (cursor === null) return { due: true, reason: 'no-cursor', releases }
+  if (installed === null) {
+    return { due: false, reason: 'unknown-version', releases }
+  }
+  if (compareVersions(installed, cursor.version) <= 0) {
+    return { due: false, reason: 'current', releases }
+  }
+  if (ageInDays(cursor.date, now) >= DUE_AFTER_DAYS) {
+    return { due: true, reason: 'week', releases }
+  }
+  if (gap?.lines.some(passesVocabulary)) {
+    return { due: true, reason: 'vocabulary', releases }
+  }
+
+  return { due: false, reason: 'recent', releases }
+}
+
+/**
+ * One reading of the feed, kept so a wave of sessions starting together spends
+ * one request rather than one each.
+ */
+export interface DueCache {
+  readonly checkedAt: string
+  readonly installed: string
+  readonly cursor: string
+  /** Null when the read failed, so a failure is held for the day too. */
+  readonly gap: Gap | null
+}
+
+// Scratch rather than the upstream record folder, which a records push backs
+// whole. A file rewritten daily would add a commit to the history each time.
+const cachePath = (root: string): string =>
+  recordDir(root, SCRATCH, 'upstream-due', 'check.json')
+
+/** The stored reading when it is fresh and answers for this pair of versions. */
+export function readDueCache(
+  root: string,
+  installed: string,
+  cursor: string,
+  now: Date,
+): DueCache | null {
+  const path = cachePath(root)
+  if (!existsSync(path)) return null
+
+  try {
+    const cache = JSON.parse(readFileSync(path, 'utf8')) as DueCache
+    const age = now.getTime() - Date.parse(cache.checkedAt)
+    const isFresh = age >= 0 && age < CACHE_MAX_AGE_MS
+    const isSamePair = cache.installed === installed && cache.cursor === cursor
+
+    return isFresh && isSamePair ? cache : null
+  } catch {
+    return null
+  }
+}
+
+export async function writeDueCache(
+  root: string,
+  cache: DueCache,
+): Promise<void> {
+  await writeAtomic(cachePath(root), `${JSON.stringify(cache)}\n`)
+}

package/src/upstream/releases.ts

@@ -113,6 +113,7 @@ export async function walkReleases(
 
 export function githubPageFetcher(
   env: Record<string, string | undefined> = process.env,
+  signal?: AbortSignal,
 ): PageFetcher {
   const token = env.GH_TOKEN ?? env.GITHUB_TOKEN
   const headers: Record<string, string> = {
@@ -125,7 +126,7 @@ export function githubPageFetcher(
     try {
       const response = await fetch(
         `${RELEASES_URL}?per_page=${PER_PAGE}&page=${page}`,
-        { headers },
+        { headers, signal },
       )
       if (response.status === 403 || response.status === 429) {
         return {

package/standards/index.md

@@ -7,39 +7,4 @@ subtitle: Reference docs for consistent authoring across the toolkit and target
 
 Reference docs for consistent authoring across the toolkit and target projects.
 
-- [Architecture reference](architecture.md): Shape and content rules for canon/ARCHITECTURE.md
-- [Board reference](board.md): Readiness groups, row cells, and ordering for priority.md, the unordered backlog.md beside it, and the generated index under .canon/tasks/
-- [Branch reference](branch.md): Branch naming format and type conventions
-- [Canvas reference](canvas.md): Page folders, frame files, the layout.json shape, token resolution, and what a frame must not assume on a local design canvas
-- [Commit reference](commit.md): Commit message format and type conventions
-- [Context entry reference](context.md): Shape and content rules for canon/context/<domain>.md entries
-- [Design reference](design.md): Shape and content rules for canon/DESIGN.md
-- [Docs reference](docs.md): Reader and jurisdiction, frontmatter, page structure, what a page links out to, the diagram permission, and when a category earns a subfolder
-- [Figure reference](figures.md): When a figure earns its place, the render-first policy for a graph-shaped subject, freehand SVG as the escape hatch, and its wrapping, color, and accessibility rules
-- [Glossary reference](glossary.md): Frontmatter, entry shape, ordering, and the rules deciding which terms a glossary carries
-- [Groundwork spikes reference](groundwork-spikes.md): What each spike in a track's 08-spikes.md records, the sample rule, and the three folders that hold what a spike produced
-- [Groundwork reference](groundwork.md): Folder layout, ordinal naming, reserved numbering, frontmatter and dating, required file contents, and conventions for a measurement track
-- [Intake reference](intake.md): Folder layout, ordinal naming, reserved index number, frontmatter and dating, the item template, the answer contract, and retrieval
-- [Memory reference](memory.md): Filename and type prefix, frontmatter, the body shape per type, links between entries, and the lifecycle from write to retire
-- [Mermaid reference](mermaid.md): Direction and layout, node and edge budgets, accessibility fields, label punctuation, and render verification for a Mermaid diagram
-- [Plan lifecycle reference](plan-lifecycle.md): When a feature plan is written, where it lives, how it changes mid-flight, and its move to the archive
-- [Plan reference](plan.md): Filename and slug, the required sections, and the suggested-and-answer contract for a feature plan
-- [Pull request reference](pr.md): Pull request title and body conventions
-- [Publish reference](publish.md): Scan an author runs against finished text, the cross-reference form each destination takes, and the response to an unreadable source
-- [Readme reference](readme.md): Readme voice, structure, and content conventions
-- [Ready reference](ready.md): Folder layout, ordinal naming, the overview frontmatter, the thin-plan contract, and the archive lifecycle for a finished-file handoff
-- [Requirements reference](requirements.md): Shape and content rules for canon/REQUIREMENTS.md
-- [Governance rule reference](rule.md): Rule frontmatter, body shape, and voice for .claude/rules files
-- [Session map reference](session.md): Filename and location, the sections a handoff carries, the write and read procedures, and how a role extends it
-- [Skill path reference](skill-paths.md): Which root a file a skill body names resolves against, and how a body cites a standard
-- [Practice skill reference](skill-practice.md): Closing sections and source ledger for a skill carrying engineering practice
-- [Skill requirement reference](skill-requirement.md): Shape and content rules for the REQUIREMENT.md beside a skill
-- [Claude skill reference](skill.md): Skill structure and authoring rules for Claude Code
-- [Slug reference](slug.md): Transform from a git branch name to a slug, and the three responses to an empty result
 - [Standard reference](standard.md): Shape and content rules for authoring a standard
-- [Task decline reference](tasks-decline.md): Where a task decided against moves, the Declined line it carries, and what happens to its plan and board row
-- [Tasks reference](tasks.md): Folder layout, filename convention, file format, origin lines, and archiving for task files under .canon/tasks/
-- [Teach reference](teach.md): Workspace layout, ordinal naming, frontmatter, and the mission and learning-record formats for a learning workspace
-- [Versioning reference](versioning.md): Phase label vs semver discipline across tasks, PRs, reviews, issues, commits, and tags
-- [Wiki reference](wiki.md): Folder split, frontmatter, naming convention, and sourcing for a wiki reference page
-- [Wireframe reference](wireframes.md): Shape and content rules for canon/wireframes/<surface>.md files

package/standards/standard.md

@@ -1,10 +1,6 @@
 ---
 title: Standard reference
 description: Shape and content rules for authoring a standard
-paths:
-  - 'standards/**/*.md'
-rule:
-  - 'Read it before writing or editing a standard. Do not work the shape from memory.'
 ---
 
 # Standard reference
@@ -68,9 +64,7 @@ A standard failing these questions is non-conforming even when it satisfies ever
 
 - Start the file with a frontmatter block carrying at least `title` and `description`. A consuming surface may require more.
 - `title`: names the doc type in sentence case, suffixed `reference` (`Commit reference`, `Branch reference`)
-- `description`: one line naming what the standard covers. It becomes the index link label on install, and the generated rule's description and pointer bullet.
-- `paths` (optional): the globs where the standard applies, one per entry, copied verbatim into the rule `canon gov regen` generates for it. Omit it when no path should route to the standard, and no rule is generated.
-- `rule` (optional): operative bullets the generated rule carries after its pointer bullet, one per entry, each a full sentence. Quote an entry holding a backtick, a colon, or a leading `-`.
+- `description`: one line naming what the standard covers. It becomes the index link label on install.
 
 ## Structure
 

package/tooling/base/reference.md

@@ -29,7 +29,7 @@ Seeds live in `tooling/base/seeds/`. Sync drops each once on first install and n
 - `.lintstagedrc`: the glob map below.
 - `.prettierignore`: created empty. Projects add their own entries.
 - `.github/workflows/verify.yml`: runs on pull requests targeting `main` and on `workflow_dispatch`. A project with more than one language root adds its own jobs here.
-- `.github/pull_request_template.md`: `## Summary`, `## Key Changes`, `## Technical Context`, `## Testing`. A project adds the checklist lines its own review needs.
+- `.github/pull_request_template.md`: `## Summary`, `## Key changes`, `## Technical context`, `## Testing`. A project adds the checklist lines its own review needs.
 - `canon/context/`: extend the `ci` and `development` entries with project-specific commands, workflows, or deploy steps. Canonical rationale stays in this reference.
 
 ## Tool pairing
@@ -45,7 +45,7 @@ Seeds live in `tooling/base/seeds/`. Sync drops each once on first install and n
 
 - All shell scripts live in `scripts/`. Do not place a `.sh` file outside it.
 - Dictionaries live in `.cspell/`, hooks in `.husky/`, seeded context docs in `canon/context/`.
-- The `canon/context/` location matches the three-tier context model: project-wide invariants in `CLAUDE.md`, `canon/REQUIREMENTS.md`, and `canon/ARCHITECTURE.md`, path-scoped rules in `.claude/rules/`, and on-demand domain narrative in `canon/context/`. Indexes stay opt-in.
+- The `canon/context/` location matches the three-tier context model: project-wide invariants in `CLAUDE.md` and `canon/REQUIREMENTS.md`, path-scoped rules in `.claude/rules/`, and on-demand domain narrative in `canon/context/`. Indexes stay opt-in.
 
 ## Hooks
 

package/tooling/base/seeds/.github/pull_request_template.md

@@ -2,12 +2,12 @@
 
 <Action Verb> <Direct Object> to <Result>.
 
-## Key Changes
+## Key changes
 
 - <Verb> <specific component/file/function> (<reason if non-obvious>)
 - <Verb> <specific component/file/function>
 
-<!-- ## Technical Context (optional, omit for docs/config/trivial changes) -->
+<!-- ## Technical context (optional, omit for docs/config/trivial changes) -->
 <!-- - <Why this approach was taken, not what changed> -->
 
 ## Testing

package/tooling/claude/reference.md

@@ -10,11 +10,9 @@ The claude stack installs the `.claude/` workflow directory into a project. Stat
 CLAUDE.md              ← seeded. Project context and rules, auto-loaded by Claude Code each session
 
 canon/
-├── REQUIREMENTS.md    ← seeded. Project goals, non-goals, MVP scope
-├── ARCHITECTURE.md    ← seeded. Technical design decisions and open questions
+├── REQUIREMENTS.md    ← seeded. Project problem, goals, non-goals
 ├── DESIGN.md          ← seeded. Visual intent and the decisions behind it
-├── context/           ← seeded. Per-domain narrative. `index.md` is the discovery anchor.
-└── wireframes/        ← seeded. Per-surface regions and states. `index.md` is the discovery anchor; `<surface>.md` files hold the regions list, the states table, and the behavior bullets.
+└── context/           ← seeded. Per-domain narrative. `index.md` is the discovery anchor.
 
 .claude/
 ├── GOV.md             ← retired. Removed by `canon gov sync` if present from a prior install
@@ -23,10 +21,9 @@ canon/
 
 .canon/
 ├── tasks/             ← seeded. One file per task plus a generated index.md, local scratch only. `archive/` holds the tasks that shipped.
-├── plans/             ← execution detail for multi-step tasks. `feature-*.md` entries swept by context-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.
+├── plans/             ← execution detail for multi-step tasks. `feature-*.md` entries moved into `archive/` by `canon tasks archive` when the `post-merge` hook archives their task.
+├── review/            ← one subfolder per producer. `branch/` no longer written, `design/` for canon design render.
+└── tmp/               ← ephemeral scratch space, safe to delete without loss
 ```
 
 One ignore entry covers `.canon/` whole, so nothing under it is named separately and nothing tracked may ever land there. A project scaffolded before the move keeps its records under `.claude/`, and every command reads either root.
@@ -35,7 +32,7 @@ One ignore entry covers `.canon/` whole, so nothing under it is named separately
 
 A project installed before the split still holds its records under `.claude/`. `canon migrate records` moves them and repoints every tracked file that cites one, reporting the plan until `--write` is passed.
 
-Run `canon tooling sync claude . --write` first. The verb refuses while the project does not ignore `.canon/`, because every folder it relocates is ignored where it stands and landing one under a tracked root commits the memory pen. Until the move runs, this project's records sit at a root the shipped ignore set no longer names, so a `git add -A` in that window picks them up.
+Run `canon tooling sync claude . --write` first. The verb refuses while the project does not ignore `.canon/`, because every folder it relocates is ignored where it stands and landing one under a tracked root commits the task board and the plans. Until the move runs, this project's records sit at a root the shipped ignore set no longer names, so a `git add -A` in that window picks them up.
 
 The verb ships with the change that split the roots and is not in a published release yet, so an installed binary answers `unknown command` until one carries it. Run it out of a canon checkout in the meantime, as `bun src/cli.ts migrate records --root <project> --write`, and read the `ok` field out of `--json` rather than the exit code, which a shell wrapper around `canon` can flatten.
 
@@ -49,16 +46,6 @@ Convert by hand, once per project:
 2. Run `canon indexes regen --no-stage --root . .canon/tasks/<any-task>.md` to build the catalog.
 3. Delete `.claude/TASKS.md`, and swap its `.gitignore` entry for `.canon/tasks/`.
 
-## 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. `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:
-
-1. Rewrite each entry's `name` key to `title` and its `type` key to a sentence-case `category`, quoting any `description` that opens with a backtick or a colon so the frontmatter parses.
-2. Replace `MEMORY.md` with an `index.md` carrying `title` and `subtitle` frontmatter and nothing else.
-3. Run `canon indexes regen --no-stage --root . .canon/memory/index.md` to build the catalog, and compare its entry count against the file count before deleting anything.
-
 ## Gitignore
 
 - `# Claude`: `.canon/`, `.claude/worktrees/`, `.claude/.tmp/` <!-- canon-keep-record-root -->
@@ -76,8 +63,7 @@ The first entry covers the whole record root, so a record folder added later nee
 ## CLAUDE.md
 
 - 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`, `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.
+- Section layout: `Context`, `Commands`, `Key paths`. Each section groups rules that share a surface so skills can detect, extend, or skip by heading.
 - 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

@@ -24,8 +24,9 @@ IFS= read -r -d '' -t 2 input
 # its edit path prints a URL as well and is not an opening.
 command=$(printf '%s' "$input" | jq -r '.tool_input.command // empty')
 stdout=$(printf '%s' "$input" | jq -r '.tool_response.stdout // empty')
+is_hand_opened=false
 case "$command" in
-*"gh pr create"*) ;;
+*"gh pr create"*) is_hand_opened=true ;;
 *)
   printf '%s\n' "$stdout" | grep -qx 'opened=true' || exit 0
   ;;
@@ -57,4 +58,11 @@ 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 role-worker."
+# A pull request opened by hand skipped git-pr, so nothing has labelled it.
+# The verb is named only where the installed canon carries it, since a skill
+# can reach a target ahead of the release that ships the verb.
+if [ "$is_hand_opened" = true ] && canon labels apply --help >/dev/null 2>&1; then
+  msg="$msg Run canon labels apply ${url##*/} to label it."
+fi
+
 jq -nc --arg msg "$msg" '{hookSpecificOutput:{hookEventName:"PostToolUse",additionalContext:$msg}}'

package/tooling/claude/seeds/.claude/hooks/records-index.sh

@@ -1,12 +1,12 @@
 #!/usr/bin/env bash
 
-# Regenerates the index.md of a gitignored record folder, `tasks` or `memory`,
-# after a file in it changes.
+# Regenerates the index.md of the gitignored `tasks` record folder after a
+# file in it changes.
 #
-# These folders are gitignored, so the whole-repo walk in `bun run check` drops
-# them and never regenerates their index. Naming the file as a positional
+# That folder is gitignored, so the whole-repo walk in `bun run check` drops
+# it and never regenerates its index. Naming the file as a positional
 # argument to `canon indexes regen` below bypasses that filter, which makes this
-# hook the only trigger that reaches either folder.
+# hook the only trigger that reaches the folder.
 
 # Claude Code sends a payload and closes stdin. A bare read with nothing feeding
 # it blocks forever and holds the session open, so the read is bounded. `read`
@@ -31,11 +31,9 @@ file_path=$(printf '%s' "$input" | jq -r '.tool_input.file_path // empty')
 # said. The index then goes stale while every save reports success.
 #
 # A shell `case` `*` crosses `/`, so each arm also matches a file in a subfolder
-# the index does not render: an archived or declined task, a memory receipt, a
-# retired memory entry, or the index itself. Those exit here, before the regen
-# call. The exclusions are per folder, since a task under `review/` is indexed
-# and a memory `declined/` is not special. The arms are ordered tasks first,
-# and no path carries both segments today.
+# the index does not render: an archived or declined task, or the index itself.
+# Those exit here, before the regen call. A task under `review/` is
+# indexed, and no other folder is read.
 #
 # The walk-up boundary has to come from the path, not from the session. Shared
 # scratch resolves at the main worktree root, so a session inside a linked
@@ -45,8 +43,6 @@ file_path=$(printf '%s' "$input" | jq -r '.tool_input.file_path // empty')
 case "$file_path" in
 */.canon/tasks/index.md | */.canon/tasks/archive/* | */.canon/tasks/declined/*) exit 0 ;;
 */.claude/tasks/index.md | */.claude/tasks/archive/* | */.claude/tasks/declined/*) exit 0 ;;
-*/.canon/memory/index.md | */.canon/memory/review/* | */.canon/memory/archive/*) exit 0 ;;
-*/.claude/memory/index.md | */.claude/memory/review/* | */.claude/memory/archive/*) exit 0 ;;
 */.canon/tasks/*.md)
   folder=tasks
   base=.canon
@@ -55,14 +51,6 @@ case "$file_path" in
   folder=tasks
   base=.claude
   ;;
-*/.canon/memory/*.md)
-  folder=memory
-  base=.canon
-  ;;
-*/.claude/memory/*.md)
-  folder=memory
-  base=.claude
-  ;;
 *) exit 0 ;;
 esac
 root="${file_path%/"$base/$folder"/*}"