@erclx/canon 4.110.0 → 4.112.0

package/src/design/favicon.ts

@@ -31,3 +31,11 @@ export function renderFavicon(mark: string, colors: FaviconColors): string {
 </svg>
 `
 }
+
+/**
+ * The `<link rel="icon">` a page carries the rendered favicon in, inlined so a
+ * generated page needs no sibling file and no href that varies with its depth.
+ */
+export function faviconLink(svg: string): string {
+  return `<link rel="icon" href="data:image/svg+xml,${encodeURIComponent(svg)}">`
+}

package/src/design/tokens.ts

@@ -381,7 +381,7 @@ export const TOKENS: DesignTokens = {
   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 ships in six independently-maintained copies that carry different colors by design rather than by drift, each fitted to the chrome it renders on: the dark accent for a dark-chrome surface, the light accent for a light-chrome one, and the pair the web favicon takes from `src/design/favicon.ts`. Unifying them or repairing the one that looks drifted would break the fit each was chosen for. `canon/context/design.md` carries which file holds each copy.',
+    'The same mark ships in five independently-maintained copies that carry different colors by design rather than by drift, each fitted to the chrome it renders on: the dark accent for a dark-chrome surface, the light accent for a light-chrome one, and the pair the web favicon takes from `src/design/favicon.ts`, which teach pages also take by rendering the live mark. Unifying them or repairing the one that looks drifted would break the fit each was chosen for. `canon/context/design.md` carries which file holds each copy.',
   ].join('\n'),
 }
 

package/src/shipped/references.ts

@@ -172,8 +172,7 @@ const DOCS_PATH = /(?<![\w./-])docs\/[^\s`)\]]*\.md\b/g
  * deliberate placeholder rather than a real citation. A body illustrating
  * the shape a project's own `standards/<name>.md` takes writes a bracketed
  * token this pattern also matches, such as `standards/<slug>.md` in
- * `create-standard/SKILL.md` or `standards/<name>.md` in
- * `migration-standards-drop/SKILL.md`, and neither names a real file. A bare,
+ * `create-standard/SKILL.md`, which names no real file. A bare,
  * non-bracketed match now reports whether or not the file exists, unlike
  * `DOCS_PATH`, which still gates on existence: a same-repository citation
  * under this corpus names no target project's own tree the way a `docs/`

package/src/sync/reverse.ts

@@ -1,4 +1,4 @@
-import { existsSync, readFileSync, statSync } from 'node:fs'
+import { existsSync, statSync } from 'node:fs'
 import { join } from 'node:path'
 import { execaSync } from 'execa'
 import { gitEnv } from '@/git-env'
@@ -11,15 +11,6 @@ import {
 
 const CLAUDE_DIR = '.claude'
 
-/**
- * A `CLAUDE.md` past this many lines has more in it than the always-load tier
- * is for. The figure is the checkpoint `standards/context.md` sets for
- * a context entry, raised because `CLAUDE.md` legitimately carries more than
- * one domain. It gates a proposal rather than a failure, so being approximate
- * costs a line an operator can ignore.
- */
-const CLAUDE_MD_LINES = 250
-
 /**
  * Who put an unclaimed folder in the target. A dropped folder and one the
  * project wrote are the same bytes at the same path, so this is traced from the
@@ -45,26 +36,14 @@ export interface UnclaimedFolder {
   readonly since?: string
 }
 
-/**
- * A proposal-only skill with a live case in this target. The skills propose and
- * never execute, so the report names one rather than queueing a change.
- */
-export interface MigrationCandidate {
-  readonly skill: string
-  /** What was measured, so the proposal is checkable before it is run. */
-  readonly reason: string
-}
-
 export interface ReverseReport {
   readonly unclaimed: readonly UnclaimedFolder[]
-  readonly migrations: readonly MigrationCandidate[]
   /** Set when the walk needed history to run and this toolkit has none. */
   readonly historyUnavailable: boolean
 }
 
 const EMPTY_REVERSE: ReverseReport = {
   unclaimed: [],
-  migrations: [],
   historyUnavailable: false,
 }
 
@@ -89,10 +68,9 @@ export function buildReverseReport(
   target: string,
 ): ReverseReport {
   const roots = readDroppedRoots(toolkitRoot)
-  const migrations = detectMigrations(target)
 
   if (roots === undefined) {
-    return { unclaimed: [], migrations, historyUnavailable: true }
+    return { unclaimed: [], historyUnavailable: true }
   }
 
   const unclaimed: UnclaimedFolder[] = []
@@ -106,7 +84,7 @@ export function buildReverseReport(
     }
   }
 
-  return { unclaimed, migrations, historyUnavailable: false }
+  return { unclaimed, historyUnavailable: false }
 }
 
 export function emptyReverseReport(): ReverseReport {
@@ -206,55 +184,6 @@ function covers(index: HistoryIndex, sourceRel: string): boolean {
   return index.get(sourceRel) !== undefined
 }
 
-/**
- * Live cases for the two proposal-only skills no other report field names.
- * Without this, both are documented and unreachable.
- *
- * Both tests read what the skill itself acts on, so a proposal the report makes
- * is one the skill has work to do for. A context tier that already holds files
- * settles the `docs/` split, whether or not the toolkit is what made it.
- */
-export function detectMigrations(target: string): MigrationCandidate[] {
-  const found: MigrationCandidate[] = []
-  const claudeMd = join(target, 'CLAUDE.md')
-
-  if (existsSync(claudeMd)) {
-    const lines = countLines(readFileSync(claudeMd, 'utf8'))
-    if (lines > CLAUDE_MD_LINES) {
-      found.push({
-        skill: 'migration-claude-md',
-        reason: `CLAUDE.md carries ${lines} lines, past the ${CLAUDE_MD_LINES} the three-tier split is for`,
-      })
-    }
-  }
-
-  const docs = listFiles(join(target, 'docs')).filter(isMarkdown).length
-  const context = listFiles(join(target, CLAUDE_DIR, 'context')).length
-
-  if (docs > 0 && context === 0) {
-    found.push({
-      skill: 'migration-context',
-      reason: `${docs} markdown files under docs/ with no canon/context/ tier`,
-    })
-  }
-
-  return found
-}
-
-function isMarkdown(rel: string): boolean {
-  return rel.endsWith('.md')
-}
-
-/**
- * Lines as `wc -l` counts them, so the figure in the reason matches what an
- * operator gets from the shell. Splitting alone overstates a file ending in a
- * newline by one, and the reason states a measurement rather than a rank.
- */
-function countLines(content: string): number {
-  const parts = content.split('\n')
-  return parts.at(-1) === '' ? parts.length - 1 : parts.length
-}
-
 /**
  * Every file under a directory, dotfiles included. A dropped root can hold any
  * extension, so this does not filter to markdown the way the domain walk does.

package/src/teach/nav.ts

@@ -1,4 +1,4 @@
-import { existsSync } from 'node:fs'
+import { existsSync, readFileSync } from 'node:fs'
 import { readFile, writeFile } from 'node:fs/promises'
 import { join, relative } from 'node:path'
 import {
@@ -6,7 +6,9 @@ import {
   TEACH_STYLESHEET_COMPONENTS,
 } from '@/design/components'
 import { buildDesignCss } from '@/design/css'
+import { FAVICON_COLORS, faviconLink, renderFavicon } from '@/design/favicon'
 import { parseFrontmatter, readField } from '@/indexes/frontmatter'
+import { PROJECT_ROOT } from '@/project-root'
 import { TEACH_FONT_FACES } from '@/teach/fonts'
 import {
   listWorkspaces,
@@ -23,7 +25,33 @@ import {
   writeStylesheet,
 } from '@/teach/workspace'
 
-const FAVICON = `<link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='10 10 80 80'%3E%3Cpath d='M34,20 L15,28 L15,72 L34,80 Z M66,20 L85,28 L85,72 L66,80 Z' fill='rgb(224,114,75)' /%3E%3Crect x='44' y='15' width='12' height='70' rx='2' fill='rgb(224,114,75)' /%3E%3C/svg%3E" />`
+const BRAND_MARK = 'assets/brand/mark.svg'
+
+/**
+ * The link `teach-workspace` once had a session write by hand into every page.
+ * A lesson keeps whatever sits outside its marked regions, so the old icon
+ * would stay beside the spliced one. Matching the exact string the skill
+ * mandated removes it without touching a link an author chose on purpose.
+ */
+const HAND_WRITTEN_ICON = `<link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='10 10 80 80'%3E%3Cpath d='M34,20 L15,28 L15,72 L34,80 Z M66,20 L85,28 L85,72 L66,80 Z' fill='rgb(224,114,75)' /%3E%3Crect x='44' y='15' width='12' height='70' rx='2' fill='rgb(224,114,75)' /%3E%3C/svg%3E" />`
+
+function dropHandWrittenIcon(html: string): string {
+  return html
+    .split('\n')
+    .filter((line) => line.trim() !== HAND_WRITTEN_ICON)
+    .join('\n')
+    .replaceAll(HAND_WRITTEN_ICON, '')
+}
+
+/**
+ * Built from the brand mark and the favicon's own pair, the same two inputs
+ * `web/public/favicon.svg` is generated from, so every teach page carries the
+ * icon the landing page does rather than a copy of its own.
+ */
+function teachFavicon(): string {
+  const mark = readFileSync(join(PROJECT_ROOT, BRAND_MARK), 'utf8')
+  return faviconLink(renderFavicon(mark, FAVICON_COLORS))
+}
 
 /**
  * Narrower and steeper than the mark it replaces, with round caps and joins.
@@ -164,6 +192,7 @@ const GLOSSARY_FILTER_SCRIPT = `<script>
 (function () {
   var input = document.getElementById("gfilter");
   var list = document.getElementById("gloss");
+  var count = document.getElementById("gloss-count");
   if (!input || !list) return;
   function updateGroups() {
     list.querySelectorAll(".gloss-group").forEach(function (heading) {
@@ -186,6 +215,10 @@ const GLOSSARY_FILTER_SCRIPT = `<script>
     });
     list.classList.toggle("none", n === 0);
     updateGroups();
+    if (count) {
+      var total = list.querySelectorAll(".gterm").length;
+      count.textContent = (n === total ? total : n + " of " + total) + (total === 1 ? " term" : " terms");
+    }
   });
   var clear = list.querySelector(".clear");
   if (clear) {
@@ -517,14 +550,16 @@ interface CrumbSegment {
 
 /**
  * Every ancestor renders as a link, and the current page renders as plain
- * text, whether or not it still carries a jump widget of its own.
+ * text, whether or not it still carries a jump widget of its own. A link's
+ * label sits in its own span because `text-box` is ignored on the
+ * `inline-flex` link, so the cap trim needs a plain box to land on.
  */
 function renderBreadcrumb(segments: readonly CrumbSegment[]): string {
   return segments
     .map((segment, index) => {
       const text =
         segment.href !== undefined
-          ? `<a class="crumb" href="${segment.href}">${escapeHtml(segment.label)}</a>`
+          ? `<a class="crumb" href="${segment.href}"><span class="crumb-t">${escapeHtml(segment.label)}</span></a>`
           : `<span class="crumb crumb-here">${escapeHtml(segment.label)}</span>`
 
       const jump = segment.jump
@@ -655,7 +690,7 @@ function pageHead(
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>${escapeHtml(title)}</title>
-${FAVICON}
+${teachFavicon()}
 ${style}
 ${headScript('index')}
 </head>
@@ -859,6 +894,12 @@ function renderGlossaryGroup(group: GlossaryGroup): string {
   return `<h3 class="gloss-group">${escapeHtml(group.heading)}</h3>${entries}`
 }
 
+function termCount(shown: number, total: number): string {
+  const noun = total === 1 ? 'term' : 'terms'
+
+  return shown === total ? `${total} ${noun}` : `${shown} of ${total} ${noun}`
+}
+
 function renderGlossarySection(
   entries: readonly string[],
   metas: readonly LessonMeta[],
@@ -867,8 +908,8 @@ function renderGlossarySection(
     .map(renderGlossaryGroup)
     .join('')
 
-  return `<h2>Glossary <span class="count">${entries.length}</span></h2>
-<input class="filter" type="search" id="gfilter" aria-label="Filter glossary terms" aria-controls="gloss" placeholder="term">
+  return `<h2>Glossary</h2>
+<div class="filter-row"><input class="filter" type="search" id="gfilter" aria-label="Filter glossary terms" aria-controls="gloss" placeholder="Filter terms"><span class="filter-count" id="gloss-count" aria-live="polite">${termCount(entries.length, entries.length)}</span></div>
 <div class="gloss" id="gloss"><p class="empty">No term matches that. <button type="button" class="clear">Clear the filter</button></p>${rendered}</div>
 `
 }
@@ -910,7 +951,7 @@ function renderRootPage(workspaces: readonly WorkspaceSummary[]): string {
           ? 'Live'
           : 'Open'
       const blurb = `${workspace.lessons} lesson(s) &middot; ${workspace.reference} reference page(s) &middot; ${workspace.terms} term(s)`
-      const inner = `<span class="num">${ordinalOf(workspace)}</span><b>${escapeHtml(titleCase(workspace.topic))}</b><span class="state${state === 'Live' ? ' done' : ''}">${state}</span><span class="blurb">${blurb}</span>`
+      const inner = `<span class="num">${ordinalOf(workspace)}</span><b>${escapeHtml(titleCase(workspace.topic))}</b><span class="state">${state}</span><span class="blurb">${blurb}</span>`
 
       return href === undefined
         ? `<li class="soon"><a href="#" aria-disabled="true" tabindex="-1">${inner}</a></li>`
@@ -1009,7 +1050,7 @@ async function renderContentsPage(
   const lessonRows = metas
     .map(
       (meta, index) =>
-        `<li><a href="${TEACH_LESSONS}/${meta.file}"><span class="num">${String(index + 1).padStart(2, '0')}</span><b>${escapeHtml(meta.title)}</b><span class="state done">Written</span><span class="blurb">${escapeHtml(meta.lede)}</span></a></li>`,
+        `<li><a href="${TEACH_LESSONS}/${meta.file}"><span class="num">${String(index + 1).padStart(2, '0')}</span><b>${escapeHtml(meta.title)}</b><span class="blurb">${escapeHtml(meta.lede)}</span></a></li>`,
     )
     .join('')
 
@@ -1123,7 +1164,7 @@ async function rewriteLesson(
 ): Promise<LessonRewritten | LessonRefused> {
   const file = metas[index].file
   const path = join(root, detail.path, TEACH_LESSONS, file)
-  let html = await readFile(path, 'utf8')
+  let html = dropHandWrittenIcon(await readFile(path, 'utf8'))
 
   const teachPrefix = '../../'
   const workspacePrefix = '../'
@@ -1172,11 +1213,12 @@ async function rewriteLesson(
   const regions: ReadonlyArray<readonly [Region, string]> = [
     // The stepper follows the workspace stylesheet so it wins the cascade at
     // equal specificity, which is what reaches a workspace seeded before it.
-    // The head script settles the panel before first paint, so it rides in the
-    // one region that sits inside `<head>`.
+    // The icon and the head script both belong in `<head>`, so they ride in the
+    // one region that sits there rather than a fifth marker every seeded
+    // lesson would lack.
     [
       'style',
-      `<style>\n${legacy ? css : `${css}\n${QUIZ_CSS}`}\n</style>\n${headScript('lesson')}`,
+      `${teachFavicon()}\n<style>\n${legacy ? css : `${css}\n${QUIZ_CSS}`}\n</style>\n${headScript('lesson')}`,
     ],
     ['header', header],
     ['footnav', `${renderFootNav(metas, index)}\n${PANE_CLOSE}`],

package/claude/skills/migration-claude-md/REQUIREMENT.md

@@ -1,40 +0,0 @@
----
-name: migration-claude-md
-description: Why a bloated CLAUDE.md is rebalanced by proposal rather than by edit, and what the seed baseline settles
----
-
-# Migration claude md requirement
-
-## Gap
-
-Without this skill, a session asked to slim `CLAUDE.md` deletes sections it judges stale and writes the rest into files it creates in the same pass, so a classification the user disagrees with is no longer one command to undo. The file is always-load context, so a wrong move costs every later session rather than one.
-
-Three more failures share a cause. The session has no baseline for what belongs in `CLAUDE.md`, so it reads toolkit-seeded always-load behavior as bloat and proposes moving it, and the next seed sync puts it back. A section carrying a rule and a narrative together gets sorted whole into one bucket, which loses half of it either way. And a target that already exists gets written over, since a proposal blind to the folder cannot tell a create from a collision.
-
-The skill also writes into `canon/context/`, a folder `migration-context` moves files into. A proposal drafted before those moves land cannot see the entries they create, so a move that should have resolved to an append reads as a create.
-
-## Must
-
-- Classify every `##` section against the three tiers in a fixed order, so the same section lands the same way twice
-- Treat a section matching the seed baseline as always-load by definition and propose no move for it
-- Read the existing rules and context folders before resolving a target, so an existing entry resolves to an append and a taken rule slot resolves to a conflict
-- Derive a rule's glob from the scope the section names rather than from the folder it describes
-- Propose and stop, leaving every file write and the `CLAUDE.md` edit to the user
-- Report the already-lean case as a pass rather than manufacturing moves to justify the run
-
-## Must not
-
-- Sort a section holding both a rule and a narrative into either bucket. Flag it for a manual split.
-- Create a rule file, create a context entry, or edit `CLAUDE.md`
-- Propose a move onto an existing rule path. Report it as a conflict and skip it.
-
-## Guards
-
-- No `CLAUDE.md` at the project root stops before any classification runs
-- Fewer than three `##` sections reports the file already lean, since a rebalance needs something to rebalance
-
-## Out of scope
-
-- Relocating `docs/` files, which `migration-context` proposes into this same `canon/context/` folder. Run that skill first when both apply, so Step 3 reads a folder its moves have already populated.
-- Scaffolding the rule files it proposes, which `create-rule` does with the numbering and frontmatter
-- Regenerating `canon/context/index.md`, which `canon indexes regen` does once the user has applied the moves

package/claude/skills/migration-claude-md/SKILL.md

@@ -1,79 +0,0 @@
----
-name: migration-claude-md
-description: Classifies each section of a target project's bloated `CLAUDE.md` into the three-tier context model and proposes moves to path-scoped rules or context entries, keeping only always-load behavior in `CLAUDE.md`. Use when asked to "slim CLAUDE.md", "migrate CLAUDE.md to rules", "rebalance CLAUDE.md", or when a project's `CLAUDE.md` has grown large. Do NOT move `docs/` files (that is `migration-context`) and do NOT auto-execute. Proposal only.
----
-
-# Claude md migrate
-
-Rebalance a large `CLAUDE.md` so only always-load behavior stays in it, path-scoped behavior becomes a rule, and domain narrative becomes a context entry. Every move is a proposal the user applies by hand.
-
-Run `migration-context` first when both apply. Its moves populate `canon/context/`, and Step 3 has to read the folder those moves left so an existing entry resolves to an append rather than blocking the move that should have created it.
-
-A project the surface move has not reached keeps its context folder under `.claude/` rather than `canon/`. Read and propose entries into whichever root already carries the folder, and propose `canon/` only when neither does, since a new `canon/` folder would hide every entry the old one holds.
-
-## Guards
-
-- If no `CLAUDE.md` exists at `pwd`, stop: `❌ No CLAUDE.md found at the project root.`
-- If `CLAUDE.md` has fewer than three `##` sections, stop: `✅ CLAUDE.md is already lean. Nothing to rebalance.`
-
-## Step 1: discover
-
-Run these in parallel from `pwd`:
-
-- Read `CLAUDE.md`
-- `ls .claude/rules/ 2>/dev/null`: existing rule subdirs and numbers for placement
-- `ls canon/context/ 2>/dev/null`: existing context entries for conflict checks
-- `canon claude seeds list --json 2>/dev/null`: the base seed set. Read the `CLAUDE.md` entry's `content` as the always-load baseline. Skip this input when `canon` is not installed.
-
-## Step 2: classify each section
-
-Split `CLAUDE.md` by `##` heading. Score each section against this order:
-
-1. **Always-load.** Stays in `CLAUDE.md`. Signals: cross-cutting behavior that applies every session, output and formatting rules, project-wide invariants, conventions with no file scope. A section that matches the seed baseline is always-load by definition. Keep it and propose no move.
-2. **Path-scoped.** Propose a rule. Signals: behavior that only applies when working in a folder (`frontend/`, `backend/`) or on a file type, framework-specific conventions, "when editing X do Y" phrasing. Derive the glob from the named scope.
-3. **Domain narrative.** Propose a context entry. Signals: prose describing how a system or domain is built, decisions, gotchas, structure. Not do-or-do-not rules.
-4. **Mixed.** Both rule and narrative in one section. Flag as "needs manual split". Do not propose a single target.
-
-## Step 3: resolve targets
-
-For each section proposed for a move:
-
-- Path-scoped: propose `.claude/rules/<subdir>/<n>-<slug>.md` with a `paths:` glob. Pick the subdir and a free number the way `create-rule` does. If `.claude/rules/<subdir>/` already holds a rule on the topic, mark as "conflict" and skip.
-- Domain narrative: propose `canon/context/<domain>.md`. If the entry already exists, flat or as a same-named `canon/context/<domain>/` folder, propose appending to the file that owns it rather than creating a duplicate flat entry beside a domain already split.
-
-## Step 4: output
-
-Print one grouped proposal block. Omit empty groups.
-
-```markdown
-## Keep in CLAUDE.md
-
-- `## <heading>` (<one-line reason: always-load behavior>)
-
-## Extract to a path-scoped rule
-
-- `## <heading>` → `.claude/rules/<subdir>/<n>-<slug>.md`, paths `<glob>` (<reason>)
-
-## Extract to a context entry
-
-- `## <heading>` → `canon/context/<domain>.md` (<reason>)
-- `## <heading>` → `canon/context/<domain>/<sub-area>.md`, appending to the domain's existing sibling file (<reason>)
-
-## Needs manual split
-
-- `## <heading>` (rule and narrative mixed)
-
-## Conflicts
-
-- `## <heading>` → `.claude/rules/<subdir>/<n>-<slug>.md` already exists. Skipping.
-
-## Reminder
-
-Scaffold each rule with create-rule, which carries the rule standard.
-Follow the context standard for each new context entry.
-Run canon indexes regen after adding context entries.
-```
-
-If every section classified as always-load, output: `✅ CLAUDE.md holds only always-load behavior. No moves proposed.`
-
-Do not edit `CLAUDE.md`, and do not create the rule or context files. The user reviews the proposal, then applies each move by hand.

package/claude/skills/migration-context/REQUIREMENT.md

@@ -1,36 +0,0 @@
----
-name: migration-context
-description: Scope boundary for the docs audience split and its ordering against the other two migrations
----
-
-# Migration context requirement
-
-## Gap
-
-Without this skill, a session judges a `docs/` file agent-facing, moves it, and rewrites the inbound links in the same pass, so a classification the user rejects is no longer one command to undo.
-
-Three more failures share a cause. The skill reads a folder two other surfaces also write, and a proposal blind to them destroys work.
-
-A seed-derived `development.md` moved out of `docs/` comes back on the next seed sync. A move onto an existing `canon/context/` filename overwrites the entry sitting there. A proposal drafted while `migration-claude-md` is proposing entries into the same folder cannot see those targets, and running the two in the wrong order turns a legitimate move into a skipped conflict.
-
-## Must
-
-- Classify by audience signal in the file rather than by its name or its folder position
-- Propose and stop. The `git mv` commands and the link fixes stay the user's to run.
-- Report every inbound reference to a moved path as a TODO line, leaving the reference itself untouched
-- Defer a seed-derived file to the seed sync path rather than proposing a move for it
-- Skip a move whose destination already exists and report it as a conflict
-
-## Must not
-
-- Sort a file carrying both audiences into either bucket. Flag it for a manual split, since a whole-file move and a silent split are both wrong.
-- Descend into `docs/` subfolders. List them for manual review and leave them alone.
-
-## Guards
-
-- A missing `docs/` directory, or one holding no top-level markdown, stops before any classification runs
-
-## Out of scope
-
-- Classifying `CLAUDE.md` sections, which `migration-claude-md` proposes into this same `canon/context/` folder. Run this skill first when both apply, so that skill's append-or-create check reads a folder the moves have already populated.
-- Regenerating `canon/context/index.md`, which `canon indexes regen` does once the user has applied the moves

package/claude/skills/migration-context/SKILL.md

@@ -1,97 +0,0 @@
----
-name: migration-context
-description: Classifies markdown files in a target project's `docs/` folder and proposes `git mv` commands to relocate agent-flavored content to `canon/context/`. Use when asked to "migrate docs to context", "move docs to context", "split docs", or to align an existing project with the three-tier context model. Do NOT auto-execute moves or rewrite inbound links. Proposal only.
----
-
-# Claude context migrate
-
-Run this skill before `migration-claude-md` when both apply. That skill proposes entries into the same `canon/context/` folder, and an entry landing there first makes the corresponding move here read as a conflict and get skipped, which loses the richer `docs/` file.
-
-A project the surface move has not reached keeps its context folder under `.claude/` rather than `canon/`. Read and propose moves into whichever root already carries the folder, and propose `canon/` only when neither does, since a new `canon/` folder would hide every entry the old one holds.
-
-## Guards
-
-- If no `docs/` directory exists at `pwd`, stop: `❌ No docs/ directory found.`
-- If `docs/` contains no `.md` files at the top level, stop: `❌ No markdown files in docs/.`
-- This skill operates on flat `docs/*.md` only. Subfolders under `docs/` are listed in the output as "manual review needed" and skipped.
-
-## Step 1: discover
-
-Run these in parallel from `pwd`:
-
-- `ls docs/*.md 2>/dev/null`: list flat markdown files
-- `ls docs/*/ 2>/dev/null`: detect subfolders for the manual-review note
-- `ls canon/context/ 2>/dev/null`: detect already-migrated content for conflict checks
-- `canon claude seeds list --json 2>/dev/null`: get the canonical seed list to identify seed-derived files
-
-Read each discovered `docs/*.md` file in parallel.
-
-## Step 2: classify
-
-For each file, score against this rule order:
-
-1. **Seed-derived.** Filename matches `development.md` or `ci.md` and content shape resembles the toolkit's base seed (frontmatter plus a Setup or Triggers section plus tables for scripts or checks). These belong to the seed-migration path. Do not propose a move here.
-2. **Agent-flavored.** Score the following signals. Classify as agent-flavored when two or more match:
-   - Dense file paths in code fences
-   - Sections titled "Anti-patterns", "Layer responsibilities", "Conventions", or "Commands"
-   - Tables of CLI commands
-   - Explicit "do not" rules
-3. **Human-only.** Default fallback when no agent signals match. Typical signals:
-   - Tutorial prose
-   - Sections titled "Welcome", "Getting started", "Contributing", or "Installation"
-   - Second-person narrative aimed at new contributors
-4. **Mixed.** Both agent and human signals present. Flag as "needs manual split". Do not propose a move.
-
-## Step 3: check conflicts and inbound links
-
-For every file proposed for a move:
-
-- If `canon/context/<filename>` already exists, or a same-named folder exists at `canon/context/` with `<filename>`'s `.md` extension dropped, mark as "conflict" and skip the move. A folder of the same name is still a collision, since the domain already lives there split into siblings.
-- Run `git grep -n "docs/<filename>"` (or grep equivalent) to list inbound references in `CLAUDE.md`, `README.md`, and other markdown. Report each as a TODO line. Do not rewrite.
-
-## Step 4: output
-
-Print one grouped proposal block. Omit empty groups.
-
-```markdown
-## Move to canon/context/
-
-- docs/<file>.md → canon/context/<file>.md (<one-line reason>)
-
-## Keep in docs/
-
-- docs/<file>.md (<one-line reason>)
-
-## Defer to seed-sync
-
-- docs/<file>.md (matches toolkit base seed)
-
-## Needs manual split
-
-- docs/<file>.md (mixed agent and human signals)
-
-## Conflicts
-
-- docs/<file>.md → canon/context/<file>.md already exists. Skipping.
-
-## Subfolders (manual review)
-
-- docs/<subfolder>/
-
-## Suggested git mv commands
-
-git mv docs/<file>.md canon/context/<file>.md
-
-## Inbound links to fix after moves
-
-- CLAUDE.md:42 references docs/<file>.md
-- README.md:17 references docs/<file>.md
-
-## Reminder
-
-Run canon indexes regen to update canon/context/index.md.
-```
-
-If every file classified as "Keep in docs/", output: `✅ All docs/ content is human-facing. No moves proposed.`
-
-Do not execute the `git mv` commands. Do not edit `CLAUDE.md` or `README.md`. The user runs the commands and fixes the links manually after reviewing.

package/claude/skills/migration-standards-drop/REQUIREMENT.md

@@ -1,55 +0,0 @@
----
-name: migration-standards-drop
-description: Why the standards-tree drop ships as an ordered proposal, what the two pre-delete reads catch, and why one citation form serves every surface inside a target
----
-
-# Migration standards drop requirement
-
-## Gap
-
-Without this skill, nothing names the tree. The sync engine registers governance alone and the unmigrated scan carries an empty root-layout set, both by decision rather than by omission, so a target holding 21 installed standards files reports clean and the drop runs off whoever remembers to look. The census that found the population walked one folder on one machine and moved the count from four to seven.
-
-The order is the second failure and it has two halves. A session that deletes before syncing lands the installed rules citing a path it removed, and one that sweeps before syncing repoints citations the sync then rewrites.
-
-The delete otherwise runs blind in two directions. Two of the five targets measured on 2026-08-28 carried a runtime reader, one a hook hand-parsing a standard for its banned-word set, and a hook whose input is gone audits nothing while reporting a clean run. In the other direction, nothing separates a file the project wrote from a toolkit copy by name, and the corpus had moved on from all 20 files at one target, so a content diff sorts every file as changed and a session reading that diff either keeps everything or loses the one file no corpus carries.
-
-The repoint form is the fourth. A session applying the citation rule it knows from a shipped skill writes `${CLAUDE_SKILL_DIR}/../../standards/<name>.md`, which from a project-local skill at `.claude/skills/<name>/` resolves back into the tree the same pass deleted, and reports the sweep finished.
-
-The last is the name map. `prose` split into `markdown.md` plus the `write-human` skill and resolves as no standard, so a mechanical one-to-one repoint produces a citation to nothing and every check on it passes.
-
-## Must
-
-- Detect from a read of `.claude/standards/` itself, since no report names the tree and a session waiting for one waits forever
-- Report the state a binary behind the published version puts the sync in, before naming a sync a stale binary would run
-- Split the tree against `canon standards list --json` three ways, separating an unchanged toolkit copy from a drifted one and from a name that resolves to no standard
-- Name every runtime reader ahead of any delete, splitting a reader from a citation by whether the file is markdown, and say when the search could not run
-- Give every citation inside a target one target form, `canon standards <name>`, and say why the plugin-root form fails there
-- Order the proposal sync, drop, sweep, and state that the sweep re-reads after the sync rather than before it
-- Report an unmatched name as the user's to place, naming the `prose` split as the recorded instance
-- Report the measured empty case as a pass, since the guard is what proves the read ran
-
-## Must not
-
-- Run the sync, delete or move a file under the tree, or rewrite a citation
-- Sort a drifted file as project-authored or as toolkit-owned on a content diff alone
-- Propose the plugin-root citation form for a surface inside a target
-- Relocate the install stamp. One visit per target is cheaper than two and a skill is not a visit, so the stamp rides with whatever else reaches the target.
-- Stay in the catalog on the author typing its name alone. Nothing can answer that before the skill has run, so read the census back once it has and retire it if the answer is nobody.
-
-## Guards
-
-- A directory with no `.claude/` stops, since nothing there installed a tree
-- A `.claude/standards/` holding no markdown is the pass rather than a refusal
-- No `canon` on `PATH` stops, since every citation this move writes names a verb the target has to run
-
-## Out of scope
-
-- Classifying `CLAUDE.md` sections into the three-tier model: `migration-claude-md`
-- Relocating `docs/` files by audience: `migration-context`
-- Splitting a retired `.claude/` file into the folder that replaced it, which pairs one file against one folder rather than dropping a corpus: `migration-superseded`
-- Reconciling a seed file against its source section by section: `seed-sync`
-- Applying the drop and the sweep, which the user does after reviewing
-
-## Why it ships while its consumer row is parked
-
-The one task performing this move is parked on the operator declining outside-repository work, so the skill arrives with three known consumers and no live instance. It ships anyway, because the parked row is about who is authorized to visit a target rather than about the move being wrong, and the skill is what makes the move repeatable by whoever is authorized. The evidence behind it comes from the census rather than from a run, which is the weaker of the two and is recorded here as such.