@erclx/canon 5.42.0 → 5.44.0

package/claude/skills/teach-workspace/references/lesson-craft.md

@@ -51,8 +51,8 @@ Every element competes with the material for attention.
 Decide the figure once per lesson, before writing the body.
 
 1. Name the one relationship, boundary, path, or before-and-after the lesson is about. A lesson about none ends here, with `Figure: none, <why it names no structure>` on the reply.
-2. Hold it against the bar in `${CLAUDE_SKILL_DIR}/../draft-figure/references/figures.md`, which also carries the drawing rules.
-3. Draw it through `canon:draft-figure` into a `raw` block before the quiz, never inside it or after its feedback, which breaks the stepper's gating. Report an unresolved skill rather than drawing.
+2. Hold it against the bar in `${CLAUDE_SKILL_DIR}/../draw-figure/references/figures.md`, which also carries the drawing rules.
+3. Draw it through `canon:draw-figure` into a `raw` block before the quiz, never inside it or after its feedback, which breaks the stepper's gating. Report an unresolved skill rather than drawing.
 4. Or write one line on why prose carries it better, such as a structure an earlier lesson gave.
 
 A structure lesson takes step 3 or 4, never neither. Put the outcome on the reply's `Figure:` line, off the lesson page. Never draw to satisfy the step, or on every section (`## Restraint`).

package/claude/skills/ui-checklist/SKILL.md

@@ -43,6 +43,8 @@ Write each box so a session driving the running app can run it without guessing:
 | Taste | End the line with `(taste)` when the result is a judgment of look or feel. A driver reports such a box as needing a person's eyes rather than passing it.                       |
 | Setup | State inline any setup the page does not open in. End the line with `(local only)` when a hosted preview cannot reach that state, such as a stopped service or a seeded record. |
 
+When the plan cites `canon/design/<surface>/` under `**Design references:**`, name the reference as the comparison on each box for that surface, such as "→ matches `canon/design/<surface>/` in light and dark". The reviewer then judges the build against the accepted design instead of against taste.
+
 The checkbox stays `- [ ]` followed by the action and the result, since the evidence comment reads boxes by that shape. Only the UI reviewer ticks a box, stamping it with the commit it passed at, and the comment carries that tick forward only while the head it names is current.
 
 ## The missing-test list

package/claude/skills/write-doc/REQUIREMENT.md

@@ -0,0 +1,46 @@
+---
+name: write-doc
+description: Why a brand-new project document needs its kind's standard, a catalog collision check, and a confirm step, not the rewrite and refresh paths docs-sync and context-fold already own
+---
+
+# Write doc requirement
+
+## Gap
+
+Without this skill, a session drafting a document that has no prior version either invents a shape from memory or reaches for a rewrite or refresh surface. `docs-sync` and `context-fold` read an existing document and a diff, and a document that never existed has neither, so they report the request as unrelated to any change. Either way the document ships with no read of the standard its kind answers to and no check against the catalog for a sibling already covering the same ground under a different name.
+
+The same procedure ran as five skills, one per kind, each restating the read, the collision check, the confirm, and the write. They drifted on their own cadence, and five descriptions competed for one trigger, writing a new document.
+
+## Must
+
+- Resolve the kind from the destination the request names, and ask rather than defaulting when it names none, since a document in the wrong surface is invisible where a reader looks for it
+- Load exactly one kind reference per run, so every step that differs by kind lives in one file and the shared procedure in one body
+- Read the kind's standard before drafting, since its frontmatter contract and its reader questions make the document arguable against a sibling
+- Check the catalog by exact name and by title and description, since a subject can be covered under a name the request does not guess
+- Confirm the resolved path, the kind's detections, and the full content with the user before writing, since placement and detection are judgment calls with no diff to preview them against
+- Regenerate the catalog of the folder the document landed in, where the kind keeps one, so the next run's collision check sees it
+- Draft a README from the template for every detected project type and combine them, never the closest one, since a project that is a CLI and a plugin owes its reader both
+- Carry each kind's own musts in its reference: the root check for context, both placement tests and a fetched source for the wiki, and project detection and rendered-value badges for the readme
+
+## Must not
+
+- Rewrite, refresh, or sync a document that already exists. A collision refuses toward the surface that owns the existing document.
+- Hand-edit an `index.md`. It regenerates from sibling frontmatter, and a hand edit is overwritten on the next regen.
+- Substitute recall for a failed fetch on the wiki kind, or invent an image or a placeholder path on the readme kind.
+- Build a hand-drawn diagram loop for a docs page.
+- Widen the wiki's folder split to admit a subject its second placement test rejects. That is a change to the standard, argued there.
+- Assume this skill's routing needs no check. One description now covers four triggers, and a ranking over descriptions is a proxy for how Claude Code routes, so a review some months in should read real invocations back.
+
+## Guards
+
+- No subject given, for any kind but the readme: stop and ask what the document should cover.
+- No destination named: ask which kind rather than defaulting to `docs/`.
+- Every other guard is the kind's own, stated in its reference.
+
+## Out of scope
+
+- Rewriting or syncing an existing `docs/` page or an authored README against a diff: `docs-sync`
+- Refreshing an existing context entry: `context-fold`
+- Drafting a governance rule: `create-rule`
+- Drawing a figure or a diagram for a document: `draw-figure`
+- Voice, rhythm, punctuation, and formatting in the drafted document: the `write-human` skill and the markdown standard

package/claude/skills/write-doc/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: write-doc
+description: Drafts one brand-new project document from scratch against the standard for its kind, picking the kind from where it lands, a `docs/` page, a `canon/context/` entry, a wiki reference page, or a README.md. Checks the catalog for a name or topic collision, places it, confirms with the user, then writes. Use when asked to "write a new docs page for X", "write a context entry for X", "write a wiki page for X", or "write a README" where none exists yet. Do NOT use to rewrite or sync an existing page or README against a diff, which is `docs-sync`, or to refresh a context entry, which is `context-fold`.
+metadata:
+  family: generate
+---
+
+# Write doc
+
+Drafts one brand-new project document end to end: resolve its kind, read the standard that kind answers to, check the catalog for a collision, place it, draft, confirm with the user, then write.
+
+## Resolve the kind
+
+Each kind has one standard and one reference. Load the reference for the resolved kind and no other, since every step below that differs by kind lives there.
+
+| Kind    | Lands at                                                 | Standard                                                    | Reference                                     |
+| ------- | -------------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------- |
+| docs    | a page under `docs/`                                     | `${CLAUDE_SKILL_DIR}/../docs-sync/references/docs.md`       | `${CLAUDE_SKILL_DIR}/references/docs.md`      |
+| context | an entry under `canon/context/`                          | `${CLAUDE_SKILL_DIR}/../context-fold/references/context.md` | `${CLAUDE_SKILL_DIR}/references/context.md`   |
+| wiki    | a reference page on a subject owned outside this project | `${CLAUDE_SKILL_DIR}/references/wiki.md`                    | `${CLAUDE_SKILL_DIR}/references/wiki-kind.md` |
+| readme  | a `README.md`, at the root or in a folder                | `${CLAUDE_SKILL_DIR}/../docs-sync/references/readme.md`     | `${CLAUDE_SKILL_DIR}/references/readme.md`    |
+
+- Read the kind off the destination the request names: a path, a folder, or the document's own name, such as "a context entry" or "a wiki page".
+- Ask which kind when the request names no destination, offering the candidates the subject fits with the likeliest first
+- Never default to `docs/` without saying so, since a subject documented in the wrong surface is invisible to the session that looks for it in the right one
+- If no subject is given for any kind but readme, stop: `❌ No subject given. Name what this document should cover.`
+- A README covers the project or the folder it sits in, so its subject is the target path
+
+## Read
+
+Read these in parallel, from the project root where a path is relative:
+
+- The kind's standard from the table above: the reader the document serves, its frontmatter, its structure, and what it links out to rather than restates
+- `${CLAUDE_SKILL_DIR}/../markdown-craft/references/markdown.md`: punctuation and formatting for all generated text
+- The `write-human` skill: voice, rhythm, and sentence construction for all generated text
+- The kind's reference from the table above
+
+## Guards
+
+Run the guards the reference states before placing or drafting anything. Each one stops toward the surface that owns the case, and a stop writes nothing.
+
+## Placement
+
+Settle the path and check the catalog for a collision the way the reference states. An exact-name check alone misses a document already covering the subject under another name, so check the titles and descriptions of the catalog the placement step already reads, and stop the same way on a match.
+
+## Draft
+
+- Draft against the kind's standard, keeping its template and its section order.
+- Draft frontmatter where the standard requires it, then the body, following the reference for what the kind adds.
+- Write for a reader with no source open. Omit an expected section with nothing to put in it rather than padding it.
+
+## Confirm
+
+- Show the kind, the resolved path, whatever else the reference names for the preview, and the full drafted content before writing.
+- Confirm with the user, and wait for that answer rather than treating the tool permission dialog as the gate
+- The kind, the placement, and every detection the reference runs are judgment calls with no diff to preview them against, which is why the dialog cannot stand in
+
+## Write
+
+- Write the file at the confirmed path, creating the folder when it is absent unless the reference narrows that.
+- Run `canon markdown audit <path>` and fix every ban, density, and reference shape finding until a re-run reports none. The whole file is this run's draft, so every finding is its own.
+- Run `canon indexes regen <folder>` on the folder the reference names, so its `index.md` picks up the new document. Skip it where the reference says the kind keeps no catalog.
+
+## Response format
+
+### Preview
+
+**Kind:** `<docs | context | wiki | readme>`
+**Subject:** `<subject, or the target path for a README>`
+**Placement:** `<path>`
+<one line per preview field the reference names>
+
+```markdown
+<drafted frontmatter and body>
+```
+
+### After confirmation
+
+One line once the file is written and its audit reports nothing.
+
+```plaintext
+✅ Drafted: <path>
+```

package/claude/skills/{draft-doc → write-doc}/references/context.md

@@ -1,11 +1,11 @@
 ---
 title: Context kind
-description: The root check, guard, flat-file placement, three-question draft, and regen folder for a brand-new context entry, read by draft-doc once the request resolves to the context kind
+description: The root check, guard, flat-file placement, three-question draft, and regen folder for a brand-new context entry, read by write-doc once the request resolves to the context kind
 ---
 
 # Context kind
 
-`draft-doc` reads this file when the request resolves to an entry under `canon/context/`. An entry that already exists is refreshed by `context-fold`, never drafted here.
+`write-doc` reads this file when the request resolves to an entry under `canon/context/`. An entry that already exists is refreshed by `context-fold`, never drafted here.
 
 ## Root
 

package/claude/skills/{draft-doc → write-doc}/references/docs.md

@@ -1,11 +1,11 @@
 ---
 title: Docs kind
-description: The guard, placement, draft additions, and regen folder for a brand-new page under docs/, read by draft-doc once the request resolves to the docs kind
+description: The guard, placement, draft additions, and regen folder for a brand-new page under docs/, read by write-doc once the request resolves to the docs kind
 ---
 
 # Docs kind
 
-`draft-doc` reads this file when the request resolves to a page under `docs/`. A page that already exists is rewritten by `docs-sync`, never drafted here.
+`write-doc` reads this file when the request resolves to a page under `docs/`. A page that already exists is rewritten by `docs-sync`, never drafted here.
 
 ## Guards
 

package/claude/skills/{draft-doc → write-doc}/references/readme.md

@@ -1,11 +1,11 @@
 ---
 title: Readme kind
-description: The target default, authored-versus-scaffold guard, project detection, header block, and badges for a README.md, read by draft-doc once the request resolves to the readme kind
+description: The target default, authored-versus-scaffold guard, project detection, header block, and badges for a README.md, read by write-doc once the request resolves to the readme kind
 ---
 
 # Readme kind
 
-`draft-doc` reads this file when the request resolves to a `README.md`. An authored README is rewritten by `docs-sync`, never drafted here.
+`write-doc` reads this file when the request resolves to a `README.md`. An authored README is rewritten by `docs-sync`, never drafted here.
 
 The readme standard claims the voice of a repository-root README. `write-human` yields voice there and keeps rhythm, density, and the machine-tell catalog everywhere, the root README included.
 

package/claude/skills/{draft-doc → write-doc}/references/wiki-kind.md

@@ -1,11 +1,11 @@
 ---
 title: Wiki kind
-description: The root guard, both placement tests, catalog collision, sourcing from the owner, and vendor-folder regen for a brand-new wiki reference page, read by draft-doc once the request resolves to the wiki kind
+description: The root guard, both placement tests, catalog collision, sourcing from the owner, and vendor-folder regen for a brand-new wiki reference page, read by write-doc once the request resolves to the wiki kind
 ---
 
 # Wiki kind
 
-`draft-doc` reads this file when the request resolves to a wiki reference page. A page that already exists is edited against the same standard, never drafted a second time.
+`write-doc` reads this file when the request resolves to a wiki reference page. A page that already exists is edited against the same standard, never drafted a second time.
 
 The standard's `## Placement` section names the folder a page lands in and the vendor subfolder under it. Resolve both from the project root and call them `<wiki-root>` and `<vendor>` below, so the standard stays the one owner of the path.
 
@@ -19,7 +19,7 @@ The standard sets two tests and a page has to pass both. Run them before draftin
 
 | Test                                        | Fails on                                                                        | Refusal                                                                                                                                    |
 | ------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Owned outside this repository               | A subject describing how this repository works                                  | `❌ <subject> is owned by this project, so it belongs in the docs surface or a context entry. Re-run draft-doc naming that destination.`   |
+| Owned outside this repository               | A subject describing how this repository works                                  | `❌ <subject> is owned by this project, so it belongs in the docs surface or a context entry. Re-run write-doc naming that destination.`   |
 | Owned by the vendor the folder split covers | A third-party tool or a vendor-neutral concept, however reference-like it reads | `❌ <subject> is outside the wiki's folder split. Route it to the docs surface or a skill body rather than adding a second folder for it.` |
 
 On the first test, offer the docs or context kind of this skill. The standard names one owner and one subfolder for the second.
@@ -37,7 +37,7 @@ Do not widen the split to admit a subject. Adding a sibling folder is a change t
 
 The standard forbids working from training knowledge, so the draft is built on a read rather than on recall.
 
-Fetch current information through the `claude-code-guide` agent for any subject that agent covers, and write from its answer. Reach any other subject through the owner's own published documentation.
+Fetch a Claude Code subject from Anthropic's docs directly, starting at the index `https://code.claude.com/docs/llms.txt` and reading the `.md` form of the page it names, and write from that page. Reach any other subject through the owner's own published documentation.
 
 - Invoke `canon:search-craft` with the skill tool before that search, since finding the owner's documentation is its field-and-authority step. Report it when it does not resolve.
 - Say the fetch failed and stop rather than substituting recall, even for a subject the session believes it knows. A page sourced from memory ships looking identical to one that was checked.

package/claude/skills/{draft-doc → write-doc}/references/wiki.md

@@ -45,7 +45,7 @@ A page failing either is non-conforming even when it satisfies every shape rule
 
 - Close the intro paragraph with a `Source:` sentence naming the owner. Link the canonical page where one exists, and name the owner alone where the subject has no single URL.
 - Link a docs page in its fetchable form, `https://code.claude.com/docs/en/<page>.md`, so a session reads the live text rather than a copy.
-- Fetch current information through the `claude-code-guide` agent when the subject is Claude Code. Do not work from training knowledge.
+- Fetch a Claude Code subject directly, starting at the index `https://code.claude.com/docs/llms.txt`. Do not work from training knowledge.
 - Propose an addition or correction and wait for confirmation. Do not write to a wiki file unasked.
 
 ## Shape

package/docs/agents/audits.md

@@ -83,6 +83,7 @@ The placement entry runs pinned to `--backend off`, so its tally stays comparabl
 | `secrets`            | `canon secrets scan`                | Credential-shaped values in the shipped tree                                       | Gates          |
 | `labels`             | `canon labels audit`                | Changed paths no row of the label map reaches                                      | Reports        |
 | `restated`           | `canon gov restated`                | Instructions `CLAUDE.md` states that a second surface states too                   | Reports        |
+| `rules`              | `canon gov audit`                   | Rules past a shape limit, and here outside-practice rules short of a source ledger | Reports        |
 | `counts`             | `canon gov counts`                  | Sentences stating a closed catalog's size that disagree with the tree              | Reports        |
 | `census`             | `canon census`                      | File count, extension breakdown, and line total                                    | Reports        |
 | `deps`               | `canon deps audit`                  | Advisories against the resolved dependencies                                       | Reports        |

package/docs/agents/markdown-audit.md

@@ -45,8 +45,10 @@ A page marked `kind: reference` holds its opening, then `Output`, `Refusals`, an
 - A paragraph under a list item counts toward that bullet, never as a paragraph
 - A table, fence, list, heading, or bold section marker ends a run of paragraphs
 - A run whose every item opens with a bold label or a link is exempt, and numbered items never count
-- Only context entries, docs, skill bodies and references, tooling seeds and stack references, the wiki, `README.md`, and `CONTRIBUTING.md` take a finding
-- A bullet run gates everywhere those paths sit, and the rest gates under `GATED_PATHS` in `src/markdown/scope.ts`. Outside a canon checkout nothing gates.
+- Only context entries, docs, skill bodies, references, and requirements, tooling seeds and stack references, the wiki, `README.md`, and `CONTRIBUTING.md` take a finding
+- A bullet run gates on those paths, and the rest gates under `GATED_PATHS` in `src/markdown/scope.ts`. Outside a canon checkout nothing gates.
+
+A requirement is the one exception to both. It gates only once `GATED_PATHS` names its own file, never through its skill's prefix and never on a bullet run alone.
 
 Five measures report and never set the exit code on their own.
 

package/docs/agents/migrate.md

@@ -11,18 +11,20 @@ kind: reference
 | Verb               | Moves                                                                                                                                       |
 | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | `rename`           | The retired `aitk` name. `--scope target` rewrites toolkit-owned folders only.                                                              |
-| `skill-names`      | Plugin skills off their `claude-` prefix and other retired names, with every citation                                                       |
+| `skill-names`      | Plugin skills off their `claude-` and `draft-` prefixes and other retired names, with every citation                                        |
 | `records`          | Session records from `.claude/` to `.canon/`, with every tracked citation                                                                   |
 | `surface-roots`    | `context/`, `wireframes/`, `ARCHITECTURE.md`, `REQUIREMENTS.md`, `DESIGN.md`, and the stamp folder from `.claude/` to `canon/`, by `git mv` |
 | `record-tree`      | Citations inside `.canon/` folders a session still follows: `diagrams`, `memory`, `plans`, `proposals`, `review`, `tasks`, `teach`          |
 | `rule-layout`      | A flat installed-rule layout onto the `canon/`-wrapped one                                                                                  |
 | `scratch-evidence` | A folder a durable record cites out of `.tmp/`, with its citations                                                                          |
 | `record-layout`    | Review receipts, memory archives, feedback, renders, picks, and evidence into their current folders                                         |
+| `session-defaults` | The seeded session defaults into an existing `.claude/settings.json`: `Agent` and `Task` denied, auto memory off                            |
 
-- `skill-names` takes no `--scope` and skips the changelog and eval transcripts
+- `skill-names` takes no `--scope`, and skips the changelog, eval transcripts, and the pointer each renamed `draft-` skill leaves at its old name
 - `surface-roots` leaves `rules/`, `skills/`, `hooks/`, and `settings.json` where Claude Code reads them
 - `rule-layout` classifies each flat file against the stamp as clean, edited, or unclaimed. Clean and edited files move untouched, and an unclaimed name stays.
 - `record-layout` labels each evidence folder `(pick)` or `(evidence)` in the dry run
+- `session-defaults` adds a key only when absent. It never removes a deny entry or changes a set `autoMemoryEnabled`, and a missing settings file is nothing to do.
 
 ## Output
 
@@ -43,14 +45,15 @@ Three markers keep an old spelling on a line. Each also covers the nearest non-b
 
 ## Refusals
 
-| Verb               | Refuses when                                                                        |
-| ------------------ | ----------------------------------------------------------------------------------- |
-| `records`          | The project does not ignore `.canon/`. Run `canon tooling sync --write` first.      |
-| `records`          | A record folder already exists at the destination                                   |
-| `surface-roots`    | Any destination already exists under `canon/`, refusing the whole plan              |
-| `scratch-evidence` | A destination is occupied                                                           |
-| `record-layout`    | A destination already exists, each move refused on its own                          |
-| `rule-layout`      | A destination holds different bytes. Neither file is touched and other moves apply. |
+| Verb               | Refuses when                                                                          |
+| ------------------ | ------------------------------------------------------------------------------------- |
+| `records`          | The project does not ignore `.canon/`. Run `canon tooling sync --write` first.        |
+| `records`          | A record folder already exists at the destination                                     |
+| `surface-roots`    | Any destination already exists under `canon/`, refusing the whole plan                |
+| `scratch-evidence` | A destination is occupied                                                             |
+| `record-layout`    | A destination already exists, each move refused on its own                            |
+| `rule-layout`      | A destination holds different bytes. Neither file is touched and other moves apply.   |
+| `session-defaults` | The settings file is not valid JSON, or `permissions` or its `deny` has another shape |
 
 A `rule-layout` destination holding the same bytes marks a duplicate, which `--write` deletes.
 

package/docs/target/migrations.md

@@ -46,9 +46,22 @@ Run it once, ahead of `canon gov sync` or `canon gov install`.
 
 ## Rename the skill citations, once
 
-Plugin skills dropped their `claude-` prefix, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. The five per-kind drafters merged into `draft-doc`, and no pointer under an old name ships. <!-- canon-keep-retired -->
+Plugin skills dropped their `claude-` prefix, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. The five per-kind drafters merged into `write-doc`, and no pointer under an old name ships. <!-- canon-keep-retired -->
+
+The seven `draft-` skills took verb-first names for what each makes. `canon migrate skill-names --write` carries a project across, and a pointer under each old name answers a typed invocation until it retires.
+
+| Old name           | New name                                        |
+| ------------------ | ----------------------------------------------- |
+| `draft-doc`        | `write-doc` <!-- canon-keep-retired -->         |
+| `draft-figure`     | `draw-figure` <!-- canon-keep-retired -->       |
+| `draft-identity`   | `design-identity` <!-- canon-keep-retired -->   |
+| `draft-slides`     | `make-deck` <!-- canon-keep-retired -->         |
+| `draft-and-pick`   | `pick-by-eye` <!-- canon-keep-retired -->       |
+| `draft-ready`      | `plan-ready` <!-- canon-keep-retired -->        |
+| `draft-screencast` | `script-screencast` <!-- canon-keep-retired --> |
 
 - `canvas` is now `canvas-board`. The sweep rewrites only `canon:canvas` and `skills/canvas`, so replace a bare prose mention by hand. <!-- canon-keep-retired -->
+- `draft-ready` is rewritten only as `canon:draft-ready` and `skills/draft-ready`, since bare it also describes a pull request. Replace a bare mention of the skill by hand. <!-- canon-keep-retired -->
 - `design-extract` and `sketch-design` are replaced by `canon:canvas-board`. <!-- canon-keep-retired -->
 - `review-branch`, `seed-sync`, `restate-plainly`, `bash-cli-script`, `canon-operator`, and `canon-rollout` have no successor <!-- canon-keep-retired -->
 - `create-standard`, `markdown-propose`, `memory-review`, `project-commands`, `repo-metadata`, and `ux-walkthrough` have no successor <!-- canon-keep-retired -->
@@ -108,7 +121,7 @@ From the registry the walk reports `historyUnavailable`, so check both paths by
 | `context-fold`    | `context`                                                     |
 | `canvas-board`    | `canvas`, `design`                                            |
 | `docs-sync`       | `docs`, `readme`                                              |
-| `draft-figure`    | `figures`, `mermaid`                                          |
+| `draw-figure`     | `figures`, `mermaid`                                          |
 | `create-rule`     | `rule`                                                        |
 | `create-skill`    | `skill`, `skill-paths`, `skill-practice`, `skill-requirement` |
 | `git-branch`      | `branch`, `slug`                                              |
@@ -119,8 +132,8 @@ From the registry the walk reports `historyUnavailable`, so check both paths by
 | `plan-groundwork` | `groundwork`, `groundwork-spikes`                             |
 | `plan-intake`     | `intake`                                                      |
 | `plan-feature`    | `plan`, `plan-lifecycle`                                      |
-| `draft-ready`     | `ready`                                                       |
-| `draft-doc`       | `requirements`, `wiki`                                        |
+| `plan-ready`      | `ready`                                                       |
+| `write-doc`       | `requirements`, `wiki`                                        |
 | `session-map`     | `session`                                                     |
 
 The `standard` name became `skill-reference.md` in `create-skill`.
@@ -136,3 +149,14 @@ The wireframes record is retired, and nothing deletes what a project holds.
 ## Move decisions out of a held architecture record, once
 
 The toolkit no longer seeds `canon/ARCHITECTURE.md`, and a held file and its `CLAUDE.md` import stay. Move a trap a session would hit into that domain's `## Gotchas`, then delete the file and its `@canon/ARCHITECTURE.md` line.
+
+## Deny subagents and turn auto memory off, once
+
+The seeded `.claude/settings.json` now denies the `Agent` and `Task` tools and sets `autoMemoryEnabled` to `false`. `canon claude sync` never rewrites a settings file you hold, so it warns while the file holds neither default. Removing the deny later to allow subagents draws no warning.
+
+```bash
+canon migrate session-defaults --json
+canon migrate session-defaults --write --json
+```
+
+The verb only adds a key that is absent. A person who wants auto memory back sets it in their own `.claude/settings.local.json`.

package/docs/target/projects.md

@@ -57,7 +57,7 @@ Before the first feature session:
 
 1. Fill `canon/REQUIREMENTS.md` with the problem, goals, and non-goals. The seed's 600-word cap gates under `canon context audit`.
 2. For a UI project, write `canon/DESIGN.md` from the seed and name the stylesheet in its lead, or work the direction out with `canon:canvas-board`
-3. Optionally invoke `canon:draft-figure` for an architecture view. The Mermaid CLI downloads on first use.
+3. Optionally invoke `canon:draw-figure` for an architecture view. The Mermaid CLI downloads on first use.
 4. Start the feature loop in [AI workflow](../workflow/ai-workflow.md)
 
 ### Stack decision

package/docs/workflow/parallel-features.md

@@ -49,13 +49,14 @@ Merge order matters only when two branches touch the same file. Expect to rebase
 
 ## The task board
 
-`.canon/tasks/` is gitignored and resolves at the main worktree root, one file per task. A hook generates `index.md`, and `priority.md` carries execution order and blockers.
+`.canon/tasks/` is gitignored and resolves at the main worktree root, one file per task. A hook generates `index.md`, and `priority.md` carries execution order and blockers. `canon tasks place`, `promote`, `move`, and `block` write it, deriving every cell but `Waiting on`.
 
 `canon tasks validate` reports and never writes:
 
 - A row's cell count must match its header, and a `## Needs a plan` row stating its position is checked against where it sits
 - Every plan pointer resolves, every task file is named once, and every ready row names its files
-- A parked row is reported when its cited task reached the trunk
+- A parked row is reported when its cited task reached the trunk, whether the cell links it or names its bare label
+- A group header must be the columns the group owns, a `Touches` cell must match its plan, and a `Waiting on` cell renders at most 120 characters
 
 `canon:task-board` creates a task file, and `canon:task-complete` marks outcomes. The `post-merge` hook archives the task a merged pull request closed, with its plan, and a `post-rewrite` hook does the same for a rebase pull. Both archive only when the merge carried a PR number and the task is closed.
 

package/docs/workflow/skill-map-on-request.md

@@ -10,18 +10,24 @@ These skills serve a request rather than a moment. With the [skill map](skill-ma
 
 ## Generate an artifact on demand
 
-| Skill                     | When to use                                       |
-| ------------------------- | ------------------------------------------------- |
-| `canon:create-rule`       | A project rule the toolkit does not ship          |
-| `canon:create-skill`      | A new `SKILL.md`                                  |
-| `canon:draft-doc`         | A new `docs/` page, context entry, or `README.md` |
-| `canon:draft-ready`       | Finished files a worker should copy               |
-| `canon:draft-figure`      | A figure or architecture view inside a doc        |
-| `canon:ci-workflow`       | A GitHub Actions workflow file                    |
-| `canon:draft-slides`      | A deck rendered to editable PowerPoint            |
-| `canon:draft-screencast`  | A recording script with beats seeded              |
-| `canon:record-screencast` | Recording a screencast draft into a finished mp4  |
-| `canon:draft-identity`    | A logo mark and social card                       |
+| Skill                     | When to use                                                                        |
+| ------------------------- | ---------------------------------------------------------------------------------- |
+| `canon:create-rule`       | A project rule the toolkit does not ship                                           |
+| `canon:create-skill`      | A new `SKILL.md`                                                                   |
+| `canon:write-doc`         | A new `docs/` page, context entry, or `README.md`                                  |
+| `canon:draft-doc`         | Never on purpose. A pointer naming `write-doc` <!-- canon-keep-retired -->         |
+| `canon:plan-ready`        | Finished files a worker should copy                                                |
+| `canon:draft-ready`       | Never on purpose. A pointer naming `plan-ready` <!-- canon-keep-retired -->        |
+| `canon:draw-figure`       | A figure or architecture view inside a doc                                         |
+| `canon:draft-figure`      | Never on purpose. A pointer naming `draw-figure` <!-- canon-keep-retired -->       |
+| `canon:ci-workflow`       | A GitHub Actions workflow file                                                     |
+| `canon:make-deck`         | A deck rendered to editable PowerPoint                                             |
+| `canon:draft-slides`      | Never on purpose. A pointer naming `make-deck` <!-- canon-keep-retired -->         |
+| `canon:script-screencast` | A recording script with beats seeded                                               |
+| `canon:draft-screencast`  | Never on purpose. A pointer naming `script-screencast` <!-- canon-keep-retired --> |
+| `canon:record-screencast` | Recording a screencast draft into a finished mp4                                   |
+| `canon:design-identity`   | A logo mark and social card                                                        |
+| `canon:draft-identity`    | Never on purpose. A pointer naming `design-identity` <!-- canon-keep-retired -->   |
 
 ## Answer a question at any point
 

package/docs/workflow/skill-map.md

@@ -17,18 +17,19 @@ Groups run in the order a project meets them. Every name `canon claude skills li
 
 ## Decide what to build
 
-| Skill                      | When to use                                        |
-| -------------------------- | -------------------------------------------------- |
-| `canon:plan-intake`        | The input is a pile of findings                    |
-| `canon:plan-intake-answer` | An intake folder holds unread slots                |
-| `canon:backlog-triage`     | The backlog needs pruning                          |
-| `canon:plan-groundwork`    | The state is unmeasured and approaches compete     |
-| `canon:decision-escalate`  | Open decisions turn on your preference             |
-| `canon:draft-and-pick`     | The call is taste, wanting candidates side by side |
-| `canon:canvas-board`       | A direction should be drawn as editable frames     |
-| `canon:task-board`         | A decided item needs a file on the board           |
-| `canon:plan-feature`       | The approach is settled and needs a plan           |
-| `canon:codebase-layout`    | A change adds a file and needs a folder            |
+| Skill                      | When to use                                                                  |
+| -------------------------- | ---------------------------------------------------------------------------- |
+| `canon:plan-intake`        | The input is a pile of findings                                              |
+| `canon:plan-intake-answer` | An intake folder holds unread slots                                          |
+| `canon:backlog-triage`     | The backlog needs pruning                                                    |
+| `canon:plan-groundwork`    | The state is unmeasured and approaches compete                               |
+| `canon:decision-escalate`  | Open decisions turn on your preference                                       |
+| `canon:pick-by-eye`        | The call is taste, wanting candidates side by side                           |
+| `canon:draft-and-pick`     | Never on purpose. A pointer naming `pick-by-eye` <!-- canon-keep-retired --> |
+| `canon:canvas-board`       | A direction should be drawn as editable frames                               |
+| `canon:task-board`         | A decided item needs a file on the board                                     |
+| `canon:plan-feature`       | The approach is settled and needs a plan                                     |
+| `canon:codebase-layout`    | A change adds a file and needs a folder                                      |
 
 ## Build the feature
 

package/docs/workflow/visual-design-workflow.md

@@ -19,9 +19,9 @@ The default. `canon/DESIGN.md` holds visual intent as one Overview paragraph, at
 These skills cover the tier:
 
 - `canon:ui-checklist`, `canon:ux-audit`, and `canon:ux-measure` review and measure a UI
-- `canon:draft-and-pick` drafts candidates as frames on the canvas and takes your pick
+- `canon:pick-by-eye` drafts candidates as frames on the canvas and takes your pick
 - `canon:canvas-board` works a direction out as HTML frames you edit in the browser. Only the pick moves into `canon/DESIGN.md`.
-- `canon:draft-identity` drafts a logo mark and social card
+- `canon:design-identity` drafts a logo mark and social card
 
 Pick tier 0 when the UI is not the core product, decisions fit in sentences, and stakeholders review code.
 

package/governance/detect.toml

@@ -200,3 +200,7 @@ files = ["index.html", "*/index.html"]
 ["canvas"]
 deps = []
 files = [".canon/canvas"]
+
+["design-reference"]
+deps = []
+files = ["canon/design"]

package/governance/ledger/framework/astro.md

@@ -0,0 +1,73 @@
+---
+title: Astro rule ledger
+description: Sources for governance/rules/framework/astro.md, one row per bullet
+---
+
+# Astro rule ledger
+
+The field is front-end engineering, and the authority is the Astro documentation at docs.astro.build. The pages read name no current major, so most rows record the read date alone. The content rows follow the Astro 6 upgrade guide, which removed the legacy collection location.
+
+## Static first
+
+| Bullet                        | Source                                                                                                                                                                               | Read       |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- |
+| `.astro` without client state | [Islands architecture](https://docs.astro.build/en/concepts/islands/): Astro components "render to static HTML with no client-side runtime"                                          | 2026-10-18 |
+| Fetch in the frontmatter      | [Data fetching](https://docs.astro.build/en/guides/data-fetching/): "All Astro components have access to the global fetch() function in their component script", run "at build time" | 2026-10-18 |
+
+## Islands
+
+| Bullet                         | Source                                                                                                                                                                                                                            | Read       |
+| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Directive on the component     | [Template directives](https://docs.astro.build/en/reference/directives-reference/): "A client directive can only be used on a UI framework component that is directly imported into a .astro component"                           | 2026-10-18 |
+| Pick the directive by priority | [Template directives](https://docs.astro.build/en/reference/directives-reference/): `client:load` is for "Immediately-visible UI elements", `client:idle` for "Lower-priority UI elements", `client:visible` for "below the fold" | 2026-10-18 |
+
+## Routing and layouts
+
+| Bullet                        | Source                                                                                                                                                                                                    | Read       |
+| ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| `getStaticPaths()` for params | [Routing](https://docs.astro.build/en/guides/routing/): in static mode every parameter value needing a page comes from `getStaticPaths()`, while "In SSR mode, a page will be generated on request"       | 2026-10-18 |
+| Layouts with `<slot />`       | [Layouts](https://docs.astro.build/en/basics/layouts/): "Layouts are Astro components used to provide a reusable UI structure", with "a slot to specify where individual page content should be injected" | 2026-10-18 |
+
+## Content
+
+| Bullet                          | Source                                                                                                                                                                                                                            | Read                |
+| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- |
+| `src/content.config.ts` loaders | [Content collections](https://docs.astro.build/en/guides/content-collections/): "All of your build-time content collections are defined in a special src/content.config.ts file", with "two built-in loaders (glob() and file())" | 2026-10-18, Astro 6 |
+| Query through the API           | [Content collections](https://docs.astro.build/en/guides/content-collections/): "getCollection() fetches an entire collection and returns an array of entries"                                                                    | 2026-10-18          |
+
+## Styles and assets
+
+| Bullet            | Source                                                                                                                                                                       | Read       |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| Scoped by default | [Styles and CSS](https://docs.astro.build/en/guides/styling/): "Scoped styles should be used as often as possible" and "Global styles should be used only as-needed"         | 2026-10-18 |
+| Images in `src/`  | [Images](https://docs.astro.build/en/guides/images/): "We recommend that local images are kept in src/ when possible so that Astro can transform, optimize, and bundle them" | 2026-10-18 |
+
+## Environment
+
+| Bullet                    | Source                                                                                                                                                                                                                | Read       |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| `astro:env` and `PUBLIC_` | [Environment variables](https://docs.astro.build/en/guides/environment-variables/): "only environment variables prefixed with PUBLIC\_ are available in client-side code", and `astro:env` gives "a type-safe schema" | 2026-10-18 |
+
+## Declined
+
+Every bullet the rewrite removed or reshaped, grouped by why.
+
+### Contradicted by the docs
+
+- Replaced "content collections in `src/content/` with a `config.ts` schema". The [Astro 6 upgrade guide](https://docs.astro.build/en/guides/upgrade-to/v6/) removed that location in favor of `src/content.config.ts`.
+
+### Cut without a source or a bug class
+
+- Cut "do not add a framework integration until the first island needs it" as a dependency call with no page read taking a side.
+- Cut "keep islands leaf-level, never wrap layout chrome to enable nested islands", which no reviewer can check against one line.
+- Cut "use `[param].astro` and `[...rest].astro`" as the file convention Claude already follows. The kept routing bullet names the `getStaticPaths()` footgun instead.
+
+### Merged or reworded
+
+- Reworded the hedged "write pages and components as `.astro` unless interactivity requires an island" to a test on client state and event handlers.
+- Reworded the hedged "prefer server-rendered content over client-fetched data" to where the fetch call sits.
+- Reworded "apply `client:*` directives on the component boundary, not on parents" to the rule the directives reference states.
+- Reworded "prefer `client:visible` or `client:idle` over `client:load`" to the priority each directive is documented for.
+- Merged "access collection entries via `getCollection` and `getEntry`" into the query bullet.
+- Reworded "use `is:global` only in layouts" to include `:global()`, the selector the styling page names for the same case.
+- Extended "read environment variables via `import.meta.env`" with `astro:env`, the typed schema the docs now offer.