@erclx/aitk 3.10.0 → 3.11.1

package/docs/agents/audits.md

@@ -57,11 +57,11 @@ The verdict is published as a field as well as an exit code. A reader branching
 
 A per-machine folder that is not on this disk reports as `absent` and moves neither the verdict nor the exit code. Every one of those folders is gitignored, so a fresh clone and every CI run carry none of them, and counting six expected absences as failures pins the verdict at `incomplete` forever. A signal that never changes is one nobody reads after the second time they see it.
 
-Which refusals count as an absence is declared per audit rather than inferred from the corpus alone. A per-machine corpus counts a missing folder. An upstream corpus counts every reason the advisory verb publishes, since each of the three means there is nothing resolved to measure. The secret scan overrides its tracked default for the three reasons that mean the project publishes nothing at all.
+Which refusals count as an absence is declared per audit rather than inferred from the corpus alone. A per-machine corpus counts a missing folder. An upstream corpus counts every reason the advisory verb publishes, since each of the three means there is nothing resolved to measure. Several tracked audits override that default too, wherever the corpus not being there is the ordinary state of a target rather than a broken checkout: the secret scan for a project that publishes nothing, the skill corpora and the citation reach check for a project holding no skills tree, and the context audit for a project that adopted none of the folders it measures.
 
 Everything else stays `unmeasured`. That covers a tree git cannot list, which is a broken checkout, and a package declaring no `files` field, where a publish would pack the whole tree and the scan read none of it. Both are a corpus that exists and went unread, so softening either would report a pass over a shipped tree nobody measured.
 
-The override exists because the corpus answers the wrong question for one audit. What earns it is `private: true`, the one declaration that a package is never published, so a project carrying it reports an absent corpus rather than a broken one. Without that the aggregate would report `incomplete` in every such project on every run, which is the permanent signal this section opens by rejecting.
+Each override exists because the corpus answers the wrong question for that audit. The secret scan earns its from `private: true`, the one declaration that a package is never published, so a project carrying it reports an absent corpus rather than a broken one. Without that the aggregate would report `incomplete` in every such project on every run, which is the permanent signal this section opens by rejecting.
 
 `upstream` is the third corpus value, carried by the advisory check alone. Its count moves when someone publishes rather than when someone edits here, so it is kept out of the retained baseline for the mirror image of the reason gitignored scratch is, and an offline run reports it absent rather than pinning the verdict at `incomplete` on every machine without a network.
 

package/docs/agents/records.md

@@ -23,7 +23,7 @@ aitk records validate intake --json
 
 It reads and never writes, and the reason splits by kind. A session record is per-machine scratch with no history behind it, so a repair that guessed wrong could not be undone. A standard installs into every target and is cited by bare filename, so a rename the verb performed would reach further than the file it moved, which is why a finding naming one says so.
 
-`standards` reads the authoring root at `standards/` where it exists and the installed copy at `.claude/standards/` otherwise. The authoring root wins because the installed tree is generated from it in the toolkit, where a fix written to the copy is discarded by the next regen. A project that consumed the corpus holds only the second, so one precedence serves both. The walk stays flat, matching install and the catalog, so `standards/bundled/` is out of range. Location decides that rather than subject, since a member there reaches its readers as a copy in each consuming skill and never as an installed file, which is the same reason install and sync skip the folder. What it costs is that a standard moved into the fan-out leaves the validator with nothing reporting the move.
+`standards` reads the authoring root at `standards/` where it exists and the installed copy at `.claude/standards/` otherwise. The authoring root wins because the installed tree is generated from it in the toolkit, where a fix written to the copy is discarded by the next regen. A project that consumed the corpus holds only the second, so one precedence serves both. The walk stays flat, matching install and the catalog.
 
 Nothing fires it automatically. The five record folders are gitignored, so the standards-audit hook exits early on them and any check reading changed files from git never lists one. The corpus is tracked and still unreached, since the markdown audit reads content across the files git lists and rules on no filename. The verb runs at the moment a session claims the record is finished, which is the same placement `aitk tasks validate` takes over the board.
 

package/docs/agents/teach.md

@@ -5,7 +5,7 @@ description: Listing learning workspaces and the ordinal a new one takes, openin
 
 # Teach
 
-Learning workspaces sit under `.claude/teach/<nn>-<topic>/`, and `standards/teach.md` fixes their layout, naming, and file formats, apart from the glossary, whose shape `standards/bundled/glossary.md` fixes and fans out into the `claude-teach` skill, so it travels with the file wherever a promotion lands it. Every verb here resolves that folder against the main worktree root rather than against the working directory, so a session standing in a linked worktree reaches the one workspace the learner has rather than opening a second.
+Learning workspaces sit under `.claude/teach/<nn>-<topic>/`, and `standards/teach.md` fixes their layout, naming, and file formats, apart from the glossary, whose shape `standards/glossary.md` fixes, cited from the `claude-teach` skill, so it travels with the file wherever a promotion lands it. Every verb here resolves that folder against the main worktree root rather than against the working directory, so a session standing in a linked worktree reaches the one workspace the learner has rather than opening a second.
 
 That root resolution is also why the writing verbs exist at all. The file-editing tools refuse a main-root path from a linked worktree and offer a worktree copy instead, and a caller naming only the destination reports a success that did not happen. A whole-file create still goes out as a shell heredoc. Changing a line inside a file that already exists has no shell route, because the stream editors are banned, so `resource` and `glossary` are the route for the two files a running workspace edits.
 

package/docs/ai-workflow.md

@@ -214,12 +214,13 @@ This section is the corpus the coverage claim is measured against: every name `a
 
 ### Check the work before it leaves the branch
 
-| Skill                         | When to use                                                           |
-| ----------------------------- | --------------------------------------------------------------------- |
-| `aitk:claude-review`          | On the local branch diff, before anything is pushed                   |
-| `aitk:claude-standards-audit` | When changed markdown has to answer to the authoring standards        |
-| `aitk:claude-ux-audit`        | To read UI source for missing states, edge cases, and inconsistencies |
-| `aitk:claude-ux-measure`      | To start the interface and measure paint, processor, and layout cost  |
+| Skill                          | When to use                                                                             |
+| ------------------------------ | --------------------------------------------------------------------------------------- |
+| `aitk:claude-review`           | On the local branch diff, before anything is pushed                                     |
+| `aitk:claude-standards-audit`  | When changed markdown has to answer to the authoring standards                          |
+| `aitk:claude-markdown-propose` | When a markdown claim needs rewriting and the change should wait for an answer per file |
+| `aitk:claude-ux-audit`         | To read UI source for missing states, edge cases, and inconsistencies                   |
+| `aitk:claude-ux-measure`       | To start the interface and measure paint, processor, and layout cost                    |
 
 ### Ship it
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@erclx/aitk",
   "type": "module",
-  "version": "3.10.0",
+  "version": "3.11.1",
   "description": "Infrastructure and quality tooling for developer workflows",
   "license": "MIT",
   "bin": {

package/scripts/core/check-skill-paths.sh

@@ -20,6 +20,5 @@ matches=$(grep -rnE "$BANNED_PATH_PATTERN" "$SKILLS_DIR" || true)
 echo "Shipped skills reference a repo-local path that does not exist in a target project:"
 echo "$matches" | sed "s|^$PROJECT_ROOT/||"
 echo
-echo "Reach supporting prose through an aitk docs command, a bundled reference, or inlined text."
-echo "A match inside a references/ folder is a generated copy. Fix the source under standards/bundled/."
+echo "Reach supporting prose through an aitk docs command, a standard cited at the flat root, or inlined text."
 exit 1

package/scripts/core/verify.sh

@@ -267,11 +267,6 @@ main() {
   run_check "assert_hero_stamp" "The hero set disagrees with the stamp written when the image was captured. Run aitk capture assets/hero.html and commit all three files together."
   log_info "Hero clean"
 
-  log_step "Skill references"
-  run_check "bash $PROJECT_ROOT/scripts/core/regen-skill-references.sh" "Skill-reference regen failed"
-  assert_no_drift "claude/skills/*/references" "Skill references drifted. Run bun run check and commit the updated reference files."
-  log_info "Skill references clean"
-
   log_step "Tooling paths"
   run_check "bash $PROJECT_ROOT/scripts/core/regen-tooling-paths.sh" "Tooling-path regen failed"
   assert_no_drift "claude/skills/toolkit-cli/SKILL.md" "The overwrite contract drifted from what the stacks hold. Run bun run check and commit claude/skills/toolkit-cli/SKILL.md."

package/src/audits/catalog.ts

@@ -1,4 +1,6 @@
+import type { SkillsAuditRefusal } from '@/claude/skills-audit'
 import type { ReachRefusal } from '@/claude/skills-reach'
+import type { ContextAuditRefusal } from '@/context/audit'
 import type { AuditRefusal } from '@/deps/audit'
 import type { RestatedRefusal } from '@/gov/restated'
 import type { LabelAuditRefusal } from '@/labels/audit'
@@ -465,6 +467,12 @@ export const AUDITS: readonly AuditSpec[] = [
     argv: ['context', 'audit', '--json'],
     gatingExits: [EXIT_FINDINGS],
     corpus: 'tracked',
+    // The one reason this verb refuses for that is an absence rather than a
+    // break, on the same test the reach check and the skill audit take: no
+    // target adopts `.claude/context/`, `.claude/diagrams/`, and
+    // `.claude/wireframes/` all at once, so without the allowance every such
+    // project reports the verb unmeasured on every run and never changes.
+    absentReasons: ['no-folders'] satisfies ContextAuditRefusal[],
     counts: contextCounts,
   },
   {
@@ -484,6 +492,10 @@ export const AUDITS: readonly AuditSpec[] = [
     argv: ['claude', 'skills', 'audit', '--json'],
     gatingExits: [EXIT_FINDINGS],
     corpus: 'tracked',
+    // The one reason this verb refuses for, and it is an absence for the same
+    // reason the reach check's is: a project carrying neither `claude/skills/`
+    // nor `.claude/skills/` has adopted no skill convention this audit reads.
+    absentReasons: ['no-corpus'] satisfies SkillsAuditRefusal[],
     counts: skillCounts,
   },
   {
@@ -520,6 +532,14 @@ export const AUDITS: readonly AuditSpec[] = [
     argv: ['records', 'validate', kind, '--json'],
     gatingExits: [],
     corpus,
+    // `standards` is the one tracked kind here, so it takes none of the
+    // per-machine default the other five inherit from their corpus. A target
+    // reads standards through `aitk standards` rather than a copy in its own
+    // tree, so carrying neither `standards/` nor `.claude/standards/` is the
+    // ordinary state of every project but this repository.
+    ...(kind === 'standards' && {
+      absentReasons: ['no-folder'] satisfies RecordRefusal[],
+    }),
     counts: findingsOnly,
   })),
   {

package/src/claude/skills-audit.ts

@@ -25,6 +25,13 @@ export const CORPORA: readonly string[] = [
   join('.claude', 'skills'),
 ]
 
+/**
+ * The one reason this audit refuses. A project carrying neither corpus is the
+ * ordinary state of a target that has not adopted either skills convention,
+ * the same absence `no-skills` reads for the shipped citation reach check.
+ */
+export type SkillsAuditRefusal = 'no-corpus'
+
 /** Kebab-case, which the standard states as no spaces, capitals, or underscores. */
 const KEBAB_CASE = /^[a-z0-9]+(?:-[a-z0-9]+)*$/
 

package/src/commands/claude.ts

@@ -20,6 +20,7 @@ import {
   REQUIREMENT_SECTIONS,
   type SkillFinding,
   type SkillsAudit,
+  type SkillsAuditRefusal,
 } from '@/claude/skills-audit'
 import {
   type RoutingRefusal,
@@ -862,8 +863,11 @@ async function runSkillsAudit(
 
   if (report.corpora.length === 0) {
     return refuseAudit(
+      'no-corpus',
       `No skill corpus under ${root}. Looked for ${CORPORA.join(' and ')}.`,
       gateOnly,
+      root,
+      opts.json ?? false,
     )
   }
 
@@ -910,16 +914,26 @@ async function runSkillsAudit(
   return auditExitCode(report)
 }
 
-function refuseAudit(message: string, gateOnly: boolean): number {
+function refuseAudit(
+  reason: SkillsAuditRefusal,
+  message: string,
+  gateOnly: boolean,
+  root: string,
+  emitJson: boolean,
+): number {
   if (gateOnly) {
     frameError(message)
-    return 1
+  } else {
+    intro('aitk claude skills audit')
+    logStep('Refused')
+    logWarn(message)
+    outro()
+  }
+
+  if (emitJson) {
+    process.stdout.write(`${JSON.stringify({ root, reason, message })}\n`)
   }
 
-  intro('aitk claude skills audit')
-  logStep('Refused')
-  logWarn(message)
-  outro()
   return 1
 }
 

package/src/commands/comments.ts

@@ -88,6 +88,12 @@ async function runScan(
     logStep('Refused')
     logWarn(languages)
     outro()
+
+    if (emitJson) {
+      process.stdout.write(
+        `${JSON.stringify({ root, reason: 'bad-languages', message: languages })}\n`,
+      )
+    }
     return 1
   }
 

package/src/commands/context.ts

@@ -1,6 +1,7 @@
 import { resolve } from 'node:path'
 import type { Command } from 'commander'
 import {
+  type ContextAuditRefusal,
   type EntryReport,
   governsContent,
   type LengthCause,
@@ -157,12 +158,17 @@ async function runAudit(
   // short a required section, which is the pass a gate exists to prevent.
   if (gateOnly && widened) {
     return refuse(
+      'conflicting-options',
       '--citations-only runs the citation check alone, so --gate would widen the gate to findings the run never measures. Pass one.',
       gateOnly,
+      root,
+      opts.json ?? false,
     )
   }
 
-  if (typeof names === 'string') return refuse(names, gateOnly)
+  if (typeof names === 'string') {
+    return refuse('bad-folder-list', names, gateOnly, root, opts.json ?? false)
+  }
 
   // The root base is opt-in. A target carrying a root `wireframes/` would
   // otherwise be audited against a standard it never adopted, on a bare run
@@ -173,8 +179,11 @@ async function runAudit(
   })
   if (folders.length === 0) {
     return refuse(
+      'no-folders',
       `No audited folder found ${named ? 'under .claude/ or the project root' : 'under .claude/'}. Looked for: ${names.join(', ')}.`,
       gateOnly,
+      root,
+      opts.json ?? false,
     )
   }
 
@@ -190,16 +199,22 @@ async function runAudit(
   const cited = presentNames(folders)
   if (gateOnly && cited.length === 0) {
     return refuse(
+      'no-citation-scope',
       `The citation check spells the .claude/ prefix and no audited folder resolved there. Looked for: ${names.join(', ')}.`,
       gateOnly,
+      root,
+      opts.json ?? false,
     )
   }
 
   const citations = await auditCitations(root, cited)
   if (citations.kind === 'unavailable') {
     return refuse(
+      'no-git',
       'git could not list the tree, so no citation was checked. Run inside a git repository.',
       gateOnly,
+      root,
+      opts.json ?? false,
     )
   }
 
@@ -308,16 +323,26 @@ async function runAudit(
   return gating ? EXIT_GATE : 0
 }
 
-function refuse(message: string, gateOnly: boolean): number {
+function refuse(
+  reason: ContextAuditRefusal,
+  message: string,
+  gateOnly: boolean,
+  root: string,
+  emitJson: boolean,
+): number {
   if (gateOnly) {
     frameError(message)
-    return 1
+  } else {
+    intro('aitk context audit')
+    logStep('Refused')
+    logWarn(message)
+    outro()
+  }
+
+  if (emitJson) {
+    process.stdout.write(`${JSON.stringify({ root, reason, message })}\n`)
   }
 
-  intro('aitk context audit')
-  logStep('Refused')
-  logWarn(message)
-  outro()
   return 1
 }
 

package/src/commands/gov.ts

@@ -506,12 +506,12 @@ function runTestOrder(opts: TestOrderOptions): number {
   if (report.kind === 'unreadable') {
     intro('aitk gov test-order')
     logStep('Refused')
-    logError(report.reason)
+    logError(report.message)
     outro()
 
     if (emitJson) {
       process.stdout.write(
-        `${JSON.stringify({ ok: false, reason: report.reason })}\n`,
+        `${JSON.stringify({ root, reason: report.reason, message: report.message })}\n`,
       )
     }
 

package/src/commands/markdown.ts

@@ -2,7 +2,7 @@ import { readFile } from 'node:fs/promises'
 import { resolve } from 'node:path'
 import type { Command } from 'commander'
 import { BAN_SETS, emptyBanSets } from '@/markdown/bans'
-import { resolveMarkdown } from '@/markdown/files'
+import { type MarkdownAuditRefusal, resolveMarkdown } from '@/markdown/files'
 import { isGating } from '@/markdown/gate'
 import {
   type BanFinding,
@@ -119,15 +119,21 @@ async function runAudit(
 
   if (scope.kind === 'unavailable') {
     return refuse(
+      'no-git',
       'git could not list the tree, so no corpus was built. Run inside a git repository.',
+      root,
+      opts.json ?? false,
     )
   }
 
   if (scope.files.length === 0) {
     return refuse(
+      paths.length === 0 ? 'no-markdown' : 'no-match',
       paths.length === 0
         ? 'No markdown file in the tree.'
         : `No markdown file matched: ${scope.unmatched.join(', ')}`,
+      root,
+      opts.json ?? false,
     )
   }
 
@@ -203,11 +209,21 @@ async function runAudit(
   return gating ? EXIT_GATE : 0
 }
 
-function refuse(message: string): number {
+function refuse(
+  reason: MarkdownAuditRefusal,
+  message: string,
+  root: string,
+  emitJson: boolean,
+): number {
   intro('aitk markdown audit')
   logStep('Refused')
   logWarn(message)
   outro()
+
+  if (emitJson) {
+    process.stdout.write(`${JSON.stringify({ root, reason, message })}\n`)
+  }
+
   return EXIT_REFUSED
 }
 

package/src/context/audit.ts

@@ -15,6 +15,22 @@ import { isStubSeed } from '@/seed-marker'
  * any markdown file, so they are stated at the attribute tier and measured by
  * `aitk markdown audit` rather than here.
  */
+/**
+ * Every reason `aitk context audit` refuses for.
+ *
+ * `no-folders` is the one ordinary absence: a project that never adopted
+ * `.claude/context/`, `.claude/diagrams/`, or `.claude/wireframes/` names no
+ * corpus this audit can measure, the same state `no-skills` reads for the
+ * skill corpora. The other four are a malformed invocation or a checkout git
+ * cannot read, which stay a break rather than an absence.
+ */
+export type ContextAuditRefusal =
+  | 'conflicting-options'
+  | 'bad-folder-list'
+  | 'no-folders'
+  | 'no-citation-scope'
+  | 'no-git'
+
 export const LENGTH_CHECKPOINT = 150
 
 /**

package/src/gov/test-order.ts

@@ -44,6 +44,21 @@ export interface Scope {
   readonly testSuffixes: readonly string[]
 }
 
+/**
+ * Every reason `aitk gov test-order` refuses for.
+ *
+ * None is an ordinary absence. A depth-1 checkout falls back to the root
+ * commit and reports zero rather than reaching any of these, so what remains
+ * is a repository with no commit at all or a git operation that failed
+ * outright, both a broken checkout rather than a target's ordinary state.
+ */
+export type TestOrderRefusal =
+  | 'no-history'
+  | 'no-log'
+  | 'no-tree'
+  | 'bad-base'
+  | 'no-base'
+
 export type TestOrderReport =
   | {
       readonly kind: 'measured'
@@ -56,7 +71,11 @@ export type TestOrderReport =
       /** Changed paths outside the pairing's reach, named rather than counted. */
       readonly ignored: readonly string[]
     }
-  | { readonly kind: 'unreadable'; readonly reason: string }
+  | {
+      readonly kind: 'unreadable'
+      readonly reason: TestOrderRefusal
+      readonly message: string
+    }
 
 export interface TestOrderOptions {
   /** The far side of the range, defaulting to the merge base against the trunk. */
@@ -258,7 +277,8 @@ export function readTestOrder(
   if (head === undefined) {
     return {
       kind: 'unreadable',
-      reason: `No git history under ${root}. History is the only surface carrying the ordering, so there is nothing to read.`,
+      reason: 'no-history',
+      message: `No git history under ${root}. History is the only surface carrying the ordering, so there is nothing to read.`,
     }
   }
 
@@ -277,7 +297,8 @@ export function readTestOrder(
   if (log === undefined) {
     return {
       kind: 'unreadable',
-      reason: `Reading history between ${base} and HEAD failed under ${root}.`,
+      reason: 'no-log',
+      message: `Reading history between ${base} and HEAD failed under ${root}.`,
     }
   }
 
@@ -285,7 +306,8 @@ export function readTestOrder(
   if (tree === undefined) {
     return {
       kind: 'unreadable',
-      reason: `Reading the tree at ${base} failed under ${root}. Without it a test written before the range reads as absent.`,
+      reason: 'no-tree',
+      message: `Reading the tree at ${base} failed under ${root}. Without it a test written before the range reads as absent.`,
     }
   }
 
@@ -323,13 +345,14 @@ function resolveBase(
   root: string,
   ref: string | undefined,
   head: string,
-): string | { kind: 'unreadable'; reason: string } {
+): string | { kind: 'unreadable'; reason: TestOrderRefusal; message: string } {
   if (ref !== undefined) {
     const resolved = revParse(root, ref)
     if (resolved === undefined) {
       return {
         kind: 'unreadable',
-        reason: `Ref ${ref} resolves to no commit in ${root}. Pass a commit this tree carries.`,
+        reason: 'bad-base',
+        message: `Ref ${ref} resolves to no commit in ${root}. Pass a commit this tree carries.`,
       }
     }
     return resolved
@@ -345,7 +368,8 @@ function resolveBase(
   if (rootCommits === undefined || rootCommits === '') {
     return {
       kind: 'unreadable',
-      reason: `No base resolves against ${root}. Fetch origin or pass --base.`,
+      reason: 'no-base',
+      message: `No base resolves against ${root}. Fetch origin or pass --base.`,
     }
   }
 

package/src/markdown/files.ts

@@ -19,6 +19,16 @@ export type FileScope =
     }
   | { readonly kind: 'unavailable' }
 
+/**
+ * Every reason `aitk markdown audit` refuses for.
+ *
+ * None is an ordinary absence. `no-git` is a broken checkout the way it is
+ * for the secret scan, and a tree tracked by git carrying no markdown file at
+ * all, or an argument matching none, is a corpus this run could not build
+ * rather than a target that adopted none of the convention this check reads.
+ */
+export type MarkdownAuditRefusal = 'no-git' | 'no-markdown' | 'no-match'
+
 function isDirectory(path: string): boolean {
   try {
     return statSync(path).isDirectory()

package/src/records/backup.ts

@@ -32,6 +32,7 @@ export const BACKED_FOLDERS = [
   'intake',
   'memory',
   'plans',
+  'proposals',
   'review',
   'tasks',
   'teach',

package/src/records/validate.ts

@@ -1115,9 +1115,7 @@ export async function validateRecords(
     )
   }
 
-  // The walk stays flat, matching install and the catalog. `standards/bundled/`
-  // is a subfolder whose members are named for the skill that reads them rather
-  // than for a path they govern, so the derivation below reports every one.
+  // The walk stays flat, matching install and the catalog.
   if (kind === 'standards') {
     return validateFiles(
       dir,

package/{claude/skills/git-split/references → standards}/branch.md

@@ -1,7 +1,6 @@
 ---
 title: Branch reference
 description: Branch naming format and type conventions
-consumers: git-branch, git-split, git-pr, claude-worktree
 ---
 
 # Branch reference

package/{claude/skills/git-commit/references → standards}/commit.md

@@ -1,7 +1,6 @@
 ---
 title: Commit reference
 description: Commit message format and type conventions
-consumers: git-commit, git-stage
 ---
 
 # Commit message reference

package/{claude/skills/claude-teach/references → standards}/glossary.md

@@ -1,7 +1,6 @@
 ---
 title: Glossary reference
 description: Frontmatter, entry shape, ordering, and the rules deciding which terms a glossary carries
-consumers: claude-teach
 ---
 
 # Glossary reference

package/standards/index.md

@@ -8,14 +8,19 @@ subtitle: Reference docs for consistent authoring across the toolkit and target
 Reference docs for consistent authoring across the toolkit and target projects.
 
 - [Architecture reference](architecture.md): Shape and content rules for .claude/ARCHITECTURE.md
+- [Branch reference](branch.md): Branch naming format and type conventions
+- [Commit reference](commit.md): Commit message format and type conventions
 - [Context entry reference](context.md): Shape and content rules for .claude/context/<domain>.md entries
 - [Design reference](design.md): Shape and content rules for .claude/DESIGN.md
 - [Diagram reference](diagrams.md): Shape and content rules for .claude/diagrams/<kind>.md files
+- [Glossary reference](glossary.md): Frontmatter, entry shape, ordering, and the rules deciding which terms a glossary carries
 - [Groundwork reference](groundwork.md): Folder layout, reserved numbering, frontmatter and dating, required file contents, and conventions for a measurement track
 - [Intake reference](intake.md): Folder layout, reserved index number, frontmatter and dating, the item template, the answer contract, and retrieval
+- [Issue reference](issue.md): GitHub issue title, labels, and body conventions
 - [Markdown reference](markdown.md): Headings, paragraph and list structure, code spans, the date form, punctuation, emphasis, file references, banned words, and frontmatter wording
 - [Memory reference](memory.md): Filename and type prefix, frontmatter, the body shape per type, links between entries, and the lifecycle from write to retire
 - [Plan reference](plan.md): Filename and slug, required sections, the suggested-and-answer contract, and the lifecycle from the live folder to the archive
+- [Pull request reference](pr.md): Pull request title and body conventions
 - [Publish reference](publish.md): Scan an author runs against finished text, the cross-reference form each destination takes, and the response to an unreadable source
 - [Readme reference](readme.md): Readme voice, structure, and content conventions
 - [Requirements reference](requirements.md): Shape and content rules for .claude/REQUIREMENTS.md
@@ -23,6 +28,7 @@ Reference docs for consistent authoring across the toolkit and target projects.
 - [Session map reference](session.md): Filename and location, the sections a handoff carries, the write and read procedures, and how a role extends it
 - [Claude skill reference](skill.md): Claude skill structure and authoring rules
 - [Slug reference](slug.md): Transform from a git branch name to a slug, and the three responses to an empty result
+- [Snippet reference](snippets.md): Snippet reference and authoring conventions
 - [Standard reference](standard.md): Shape and content rules for authoring a standard
 - [Tasks reference](tasks.md): Folder layout, filename convention, readiness groups, and content rules for .claude/tasks/
 - [Teach reference](teach.md): Workspace layout, ordinal naming, frontmatter, and the mission and learning-record formats for a learning workspace

package/standards/{bundled/issue.md → issue.md}

@@ -1,7 +1,6 @@
 ---
 title: Issue reference
 description: GitHub issue title, labels, and body conventions
-consumers: git-issue
 ---
 
 # Issue reference

package/standards/{bundled/pr.md → pr.md}

@@ -1,7 +1,6 @@
 ---
 title: Pull request reference
 description: Pull request title and body conventions
-consumers: git-split, git-pr
 ---
 
 # Pull request reference

package/standards/{bundled/snippets.md → snippets.md}

@@ -1,7 +1,6 @@
 ---
 title: Snippet reference
 description: Snippet reference and authoring conventions
-consumers: create-snippet
 ---
 
 # Snippet reference