@erclx/canon 4.110.0 → 4.112.0

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

@@ -1,113 +0,0 @@
----
-name: migration-standards-drop
-description: Proposes the ordered drop of an installed `.claude/standards/` tree and the repoint of every citation at `canon standards <name>`, separating a toolkit copy from a file the project wrote and naming any runtime reader before a delete is proposed. Use when asked to "drop the standards tree", "repoint the standards citations", "my project still has .claude/standards/", or when a toolkit update leaves an installed standards copy no command refreshes. Do NOT delete the tree, run the sync, or rewrite a citation. Proposal only.
----
-
-# Migration standards drop
-
-## Guards
-
-- If `.claude/` does not exist at `pwd`, stop: `❌ No .claude/ directory. Nothing here installed a standards tree.`
-- If `.claude/standards/` holds no markdown, that is the pass: `✅ No installed standards tree. Nothing to drop.`
-- If `canon` is not on `PATH`, stop: `❌ canon is not on PATH. Every citation this move writes names a verb the target has to run.`
-
-Detection is the directory read above and nothing else. No report names this tree, since the sync engine registers governance alone and the unmigrated scan covers a root layout an older toolkit wrote rather than a copy under `.claude/`. A session waiting for a command to raise the tree waits forever.
-
-## Step 1: read the version the sync would run from
-
-Run `canon sync --check . --json` and read its `skew` object. The sync in Step 5 installs the rules the running binary carries, so a binary predating the citation change installs rules naming the path this move removes, and the sweep then has more to fix than it started with.
-
-- `state` is `behind`: stop. `❌ The canon on PATH is <installed> against <latest> published. A gov sync from it installs rules citing the standards path. Update, then re-run.`
-- `state` is `unknown`: report the reason and continue. A version that could not be read is unread rather than stale.
-- `state` is `current`: continue.
-
-## Step 2: split the tree three ways
-
-Run `canon standards list --json`. Each entry carries `name` and `content`, so the comparison needs no second read. Match every `.claude/standards/<stem>.md` against `name`:
-
-- **Matched, content identical.** A toolkit copy the corpus still carries unchanged. The drop loses nothing.
-- **Matched, content differs.** A toolkit copy that has drifted, and the diff cannot say which side moved. Report it as a read the user owes rather than sorting it either way. All 20 files measured at one target on 2026-08-28 read as changed, because the corpus had moved on since the install, and none of them was project-authored.
-- **Unmatched.** No standard resolves under that name. Either the project wrote the file or the toolkit retired the name, and the catalog cannot separate the two.
-
-Report a project-authored file as one this move keeps. Its destination is `standards/<name>.md` at the project root, which `canon standards <name>` resolves ahead of the package corpus, so the citation form Step 4 gives every other file serves it too.
-
-`prose` is the recorded retirement. It split into `markdown.md` plus the `write-human` skill and resolves as no standard at all, so a citation repointed one-to-one from it names nothing. Report an unmatched name as the user's to place and name that split as the instance.
-
-## Step 3: name every runtime reader before naming a delete
-
-Run both from the project root, in parallel:
-
-- `git grep -ln 'claude/standards' -- '*.md'`: the citations Step 4 repoints
-- `git grep -ln 'claude/standards' -- . ':!*.md'`: the readers
-
-The extension is the split. Markdown cites the tree and a session reads the citation. A hook, a script, or a config opens a file under it at run time, and dropping the tree under one leaves a check whose input is gone reporting success. Two of the five targets in the 2026-08-28 census carried a reader, one of them a hook hand-parsing a standard for a banned-word set.
-
-Report each reader with what replaces it. A reader parsing a standard for a list the CLI now ships reads that list through the verb instead, which is `canon markdown audit <file> --json` for the banned-word case.
-
-When `pwd` is not a git work tree, say the reader search did not run rather than reporting no reader.
-
-## Step 4: give every citation one target
-
-Every citation repoints to `canon standards <name>`, whatever surface it sits on. One form rather than a choice per surface, which is the part a session gets wrong:
-
-- A rule under `.claude/rules/` is markdown a glob match loads, so `${CLAUDE_SKILL_DIR}` expands to nothing there
-- A project-local skill under `.claude/skills/<name>/` expands that variable to its own folder, so `${CLAUDE_SKILL_DIR}/../../standards/` resolves back into the tree being dropped
-- `CLAUDE.md` and a context entry expand no variable at all
-
-The plugin-root form belongs to a skill the toolkit ships beside its own corpus. Proposing it inside a target writes a path that resolves to the deleted tree.
-
-A citation naming a name Step 2 left unmatched carries no target. Report it under what the user supplies.
-
-## Step 5: output the ordered proposal
-
-The order is fixed and the reverse is the failure. Deleting before the sync lands the installed rules citing a path that is gone, and sweeping before the sync repoints citations the sync then rewrites. The sweep re-reads after the sync for that reason, since the sync fixes the rules it installed and leaves a project's own rules and prose alone.
-
-Take the drop command from whether the tree is tracked, read with `git ls-files .claude/standards`. A tracked tree goes out through `git rm -r` so the index moves with the files, and an untracked one through `rm -rf`. A tree holding both needs both commands, since `git rm -r` takes the tracked files, exits zero, and leaves every untracked one where it was.
-
-Print the blocks below, omitting any that is empty.
-
-````markdown
-## Drop
-
-`.claude/standards/` holds <n> files: <n> unchanged toolkit copies, <n> drifted, <n> matching no standard.
-
-## Read before dropping
-
-- `.claude/standards/<name>.md` drifted from the corpus copy. Confirm the project did not edit it.
-
-## Keep
-
-- `.claude/standards/<name>.md` matches no standard. Move it to `standards/<name>.md` at the project root, which `canon standards <name>` resolves first.
-
-## Runtime readers
-
-- `.claude/hooks/<file>.sh` parses a standard at run time. Route it through `canon markdown audit <file> --json` before the drop, or it reports a clean run having read nothing.
-
-## Citations to repoint
-
-- `CLAUDE.md:42` → `canon standards markdown`
-- `.claude/rules/canon/core/<n>-<slug>.md:8` → `canon standards skill`
-
-## You supply
-
-- The destination for the `prose` citations. It split into `markdown.md` plus the `write-human` skill, so no single name replaces it.
-
-## Run in this order
-
-```bash
-canon gov sync
-git rm -r .claude/standards
-```
-
-Then re-read the citations and repoint what the sync left.
-
-## Confirm
-
-Run `canon standards <name>` from inside this project for every name the repointed citations carry, and confirm each resolves.
-
-## Reminder
-
-Nothing above was written or run. The tree holds files a delete cannot recover, so the drop and the sweep are yours to apply.
-````
-
-Run nothing and write nothing: not the sync, not a delete or a move under `.claude/standards/`, not a citation rewrite. The install stamp is out of scope too, and travels with whatever else reaches this target. The user applies the move after reviewing it.

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

@@ -1,44 +0,0 @@
----
-name: migration-superseded
-description: Why a retired file's split ships as a proposal read from the destination standard, and why detection stops rather than falling back to a listing
----
-
-# Migration superseded requirement
-
-## Gap
-
-Without this skill, a target holding a retired `.claude/` file is told what replaced it and nothing else. The drift report names both halves and no command touches either, so the user hand-splits one file into a folder answering to a standard they have not read. The destination files land with frontmatter fields missing and filenames that sort out of order, which is the step the toolkit exists to remove.
-
-A second failure comes from the ordering nobody gets right unaided. A retired file committed before its ignore entry was written is tracked and ignored at once, and removing the entry first leaves the file tracked with nothing naming it. No report catches that state, so the mistake is discovered by whoever next wonders why a gitignored path keeps appearing in diffs.
-
-Two more follow from where a session looks when the report is thin. An uppercase stem under `.claude/` is not the test for a superseded file, so a session substituting a folder listing reaches `ARCHITECTURE.md`, `REQUIREMENTS.md`, and `DESIGN.md`, each a single file the layout intends to stay one, and proposes shredding three documents. A session falling back to the plugin's own copy of the destination standard proposes a shape the project never adopted, against content only the user can place.
-
-The last is the two-speed release skew arriving as a confident wrong answer. `superseded` reached a release in `0.46.0`, and an older CLI exits zero with a well-formed report that never mentions the field. A session reading that absent key as an empty array reports a clean layout to exactly the population holding the retired files.
-
-## Must
-
-- Take detection from the report's `superseded` array alone, and stop when the key is absent rather than treating it as empty
-- Resolve the governing standard by matching the replacement folder against the `appliesTo` the standards catalog declares, so a seed folder added later resolves without an edit to the body
-- Read the destination shape with `canon standards <name>`, report the root it answered from, and propose nothing for a folder the catalog names no standard for
-- Separate a folder no standard governs from one whose governing standard could not be read, since the catalog derives `appliesTo` from prose and answers an unparsed scope statement with an empty array
-- Name the untrack command ahead of the ignore entry whenever a retired file is both tracked and ignored, and say when the check could not run
-- Report what the destination standard leaves open, such as a phase label the retired file never recorded, rather than supplying a value for it
-- Report the measured empty case as a pass, since the guard is what proves the section ran
-
-## Must not
-
-- Write, move, or delete the retired file or its replacement, or create the destination folder
-- Run `git rm --cached` or edit the file carrying the ignore entry
-- Substitute a folder listing for the `superseded` array
-- Read the plugin's own copy of the destination standard when the target lacks that file
-
-## Guards
-
-- A directory with no `.claude/` stops, since nothing there was superseded and the report's sections would not be measured
-
-## Out of scope
-
-- Classifying `CLAUDE.md` sections into the three-tier model: `migration-claude-md`
-- Relocating `docs/` files by audience: `migration-context`
-- Reconciling a seed file against its source section by section, which diffs two files rather than splitting one into a folder: `seed-sync`
-- Applying the split and running the untrack, which the user does after reviewing

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

@@ -1,115 +0,0 @@
----
-name: migration-superseded
-description: Proposes how to split a retired `.claude/` file into the folder that replaced it, reading the destination shape from the standard that folder answers to. Use when asked to "split TASKS.md", "my .claude/DIAGRAMS.md was replaced by a folder", "migrate the superseded file", or after a drift report names a superseded artifact. Do NOT write to the retired file or to its replacement, and do NOT run the untrack command. Proposal only.
----
-
-# Migration superseded
-
-## Guards
-
-- If `.claude/` does not exist at `pwd`, stop: `❌ No .claude/ directory. Nothing here was superseded.`
-
-The guard is also what makes the report's `superseded` section measured. Every section is gated on the target being toolkit-managed, and a `.claude/` directory satisfies that gate, so the empty case below is a measured empty rather than a section that never ran.
-
-## Step 1: read the report
-
-Run `canon sync --check . --json` from the project root. Its `superseded` array is the detection. Each entry carries `rel`, the retired file, and `replacedBy`, the folder that took its job.
-
-An empty array is the pass: `✅ No superseded artifact. Every .claude/ file the seeds replaced is already a folder.`
-
-### When the report is unavailable
-
-Stop on any of three conditions, naming which one fired:
-
-- `canon` is not on `PATH`: `❌ canon is not on PATH. The superseded section is the only detection this skill has.`
-- The command exits non-zero: `❌ canon sync --check failed. Fix the report before proposing a split.`
-- The report parses and carries no `superseded` key at all: `❌ This canon predates the superseded field, which reached a release in 0.46.0. Upgrade, then re-run.`
-
-Test for the key rather than for emptiness. A current CLI reporting `"superseded": []` has looked and found nothing, which is the pass above, and reading an absent key as an empty answer reports a clean layout to the projects this skill exists for.
-
-No listing substitutes for the field. The pairing runs against the seed folder names the toolkit ships, and an uppercase stem is not the test, so a listing of `.claude/*.md` also reaches `ARCHITECTURE.md`, `REQUIREMENTS.md`, and `DESIGN.md`. Each of those is a single file the layout intends to stay one. A fallback that proposed splitting them would shred three documents to avoid reporting a stale CLI, which is why this skill stops where its siblings degrade.
-
-## Step 2: resolve the destination standard
-
-### Match the folder against the catalog
-
-Run `canon standards list --json` and match each entry's `replacedBy` against the `appliesTo` array the catalog declares. Resolve from the catalog rather than from the folder stem, so a seed folder the toolkit adds later resolves without an edit here.
-
-Compare on the folder rather than on the exact string. An `appliesTo` value matches when it equals `replacedBy` or begins with `replacedBy` followed by a slash. The report spells the folder `.canon/tasks` and the catalog spells it `.canon/tasks/`, and `memory` declares a filename pattern beneath its folder rather than the folder itself, so string equality matches nothing the catalog actually carries and sends every entry to a decline below.
-
-### Read the standard through the verb
-
-A match resolves to that standard's `name`. Read it with `canon standards <name>`, which writes the document to stdout and the root it answered from to stderr.
-
-The verb is the one route. It resolves `standards/<name>.md` at the project root first, which is where a project that authors standards of its own keeps them, and falls back to the corpus inside the canon package. No toolkit standard installs into a project, so there is no third path to test and no case where the shape is unreachable while the catalog names it.
-
-Report the root the frame named beside the proposal. A shape read from the project's own `standards/` is the project's stated agreement, and one read from the package is the toolkit's default, which is a difference the user weighs rather than a reason to refuse.
-
-### The states that end an entry
-
-Four states end an entry with no proposal. Name whichever one fired rather than collapsing them, because two of them are unmeasured and two are answers:
-
-- The catalog carries no `appliesTo` key: `⚠️ This canon emits no appliesTo, so which standard governs <replacedBy> is unread.`
-- No value covers `replacedBy` and some entry carries an empty `appliesTo`: an empty array is a scope statement that did not parse, so a no-match verdict is unread rather than negative. Name the standards that did not parse.
-- No value covers `replacedBy` and every array is populated: `⚠️ The toolkit ships no standard for <replacedBy>. Nothing states the destination shape.` No command fixes it, so name none.
-- The standard resolved in the catalog and `canon standards <name>` exits non-zero: name the standard and the exit, since the catalog and the read disagree and only one of them can be right.
-
-## Step 3: read the shape and map the file onto it
-
-Read the resolved standard and take four things from it: the filename convention, the required frontmatter, the required sections, and anything the folder holds that is not an item, such as a generated `index.md` no proposal may claim.
-
-Then read the retired file and split it at the boundary the standard implies, one destination file per item. Propose a filename per item from the convention, and name the frontmatter and sections each destination file owes.
-
-Report what the standard leaves open rather than inventing a value for it. A convention carrying a field the retired file never recorded, such as a phase label or a verified SHA, is the user's to supply, and a proposal that fills one in reads as a decision the split already made.
-
-## Step 4: check the ignore ordering
-
-Run both against each `rel`, in parallel:
-
-- `git ls-files --error-unmatch <rel> 2>/dev/null`: whether the file is tracked
-- `git check-ignore -v --no-index <rel> 2>/dev/null`: whether it is ignored, and which file and line names it
-
-`--no-index` is what makes the second read answer the question. `git check-ignore` consults the index by default and reports a tracked path as not ignored, so the flagless form returns nothing in exactly the tracked-while-ignored state this step exists to find, and the run reads a clean result off the one case that is not clean.
-
-A file that is both tracked and ignored carries an ignore entry added after the commit. Take it out of the index first, then remove the entry `check-ignore` named:
-
-```bash
-git rm --cached <rel>
-```
-
-Reversing the two leaves the file tracked with nothing naming it, and no report catches that state. Name both steps in that order and run neither. `git rm --cached` writes the index, which is a change to the project's own history even though no content moves.
-
-When `pwd` is not a git work tree, say the tracked check did not run rather than reporting the ordering as clear.
-
-## Step 5: output
-
-Print one block per superseded entry, then the shared reminder. Omit empty groups.
-
-```markdown
-## Split
-
-`.claude/TASKS.md` → `.canon/tasks/`, shaped by `canon standards tasks`
-
-## Proposed files
-
-- `.canon/tasks/vXX.Y-<slug>.md` ← the "<heading>" section
-- `.canon/tasks/vXX.Y-<slug>.md` ← the "<heading>" section
-
-Each carries `title` and `description` frontmatter, an `## Outcomes` heading, and a `## Findings` heading.
-
-## You supply
-
-- The phase label on each filename. The retired file records no version.
-
-## Untrack before editing the ignore entry
-
-git rm --cached .claude/TASKS.md
-
-Then remove the `.claude/TASKS.md` line from `.gitignore:12`.
-
-## Reminder
-
-Nothing above was written or run. The retired file holds content the project authored, so the split is yours to apply and the destination folder shape is what this proposal supplies.
-```
-
-Do not create the destination folder. Do not write, move, or delete the retired file. Do not run `git rm --cached`. The user applies the split after reviewing it.