@erclx/canon 5.30.0 → 5.32.0

package/docs/agents/review-classification.md

@@ -1,76 +0,0 @@
----
-title: Review classification
-description: Deciding whether a changed set needs the review pass, the two tests it runs, why an empty set refuses rather than skipping, and the written fallback a target on an older binary falls back to
----
-
-# Review classification
-
-`canon autoship classify` answers the one decision the ship chain used to make by reading a bulleted list out of a skill body. It takes the names a branch changed and returns whether the review pass can be skipped, which file decided it, and which of the two tests that file failed.
-
-```bash
-canon autoship classify docs/index.md README.md
-canon autoship classify --json .claude/skills/deploy-check/SKILL.md
-```
-
-| Option   | Behavior                                                   |
-| -------- | ---------------------------------------------------------- |
-| `--json` | Add a machine-readable record on stdout, keeping the frame |
-
-Positional paths are the whole input. The verb never touches git, so it reads no baseline of its own and the caller hands over the set it already computed. A second read here could resolve a different range than the one the chain measured, which is the stale-baseline failure a prior row closed.
-
-Under `--json` the record holds stdout alone and the frame still renders on stderr, refusals included, which is the split `output-shape.md` fixes for every mode.
-
-## The two tests
-
-A branch skips review only when both hold across every changed name:
-
-- **Every path reads as prose.** The extension is `.md` or `.txt`, compared lowercased. Anything else is code, a config, or an asset.
-- **No path sits under a behavior path.** Markdown under one of those surfaces states what an agent does, so a change there is a behavior change wearing a prose extension.
-
-One failing file sends the whole branch to review. Documentation shipped beside a behavior change does not cancel it.
-
-The record names the first file to fail, tested in the caller's own order, and each file is read for its extension before its path. A set failing both tests reports one file and one test, which is all a caller needs to route.
-
-## The behavior paths
-
-Most carry two spellings, the one a surface authors at and the one it reaches a session at, so the rule reads the same in this toolkit and in a project that consumed one.
-
-| Surface           | Spellings                             |
-| ----------------- | ------------------------------------- |
-| Plugin skills     | `claude/skills/`, `.claude/skills/`   |
-| Governance rules  | `governance/rules/`, `.claude/rules/` |
-| Standards         | `standards/`                          |
-| Internal and seed | `internal/`, `tooling/`               |
-| Root instructions | `CLAUDE.md`                           |
-
-`standards/` carries one spelling. It never installs into a project, reaching a reader by resolution, so there is no consumed copy to name.
-
-`CLAUDE.md` is matched as a whole path rather than as a prefix, because a prefix reaches nothing that sits in no folder. A nested `docs/CLAUDE.md` stays informational.
-
-The set is data at `src/autoship/paths.ts`. That makes it permanently exempt from any later design that folds a machine-parsed list back into the surface citing it, per the toolkit's machine-parsed clause: a rule restating the list a parser reads is two sources for one list.
-
-## Exit codes and refusals
-
-| Code | Meaning                                                      |
-| ---- | ------------------------------------------------------------ |
-| `0`  | prose-only, so the review pass can be skipped                |
-| `1`  | refused, with `reason` naming the cause                      |
-| `2`  | review is needed, with `file` and `test` naming what decided |
-
-Branch on the record's `decision` rather than on the exit code. A shell function wrapping `canon` takes its status from whatever it runs last, so every non-zero exit can reach a caller as zero.
-
-An empty set refuses with `no-changes` rather than skipping. Both tests are universally quantified, so an empty set satisfies them vacuously, and reading that as prose-only would route a branch past review for having produced no output at all.
-
-## Why it is a verb
-
-The decision was three sentences in `auto-ship`'s review step, applied by a session reading a bulleted list of paths. It failed three times. A driven arm on 2026-08-30 staged `.claude/skills/deploy-check/SKILL.md`, which that list names, and the chain skipped review and opened a draft pull request anyway. The rule was correct and the session did not apply it, and the two fixes before that one were each a rewrite of the same prose.
-
-A rule a session can talk itself out of moves into a verb. That is the same argument the quiz-order draw in `canon teach lesson` was decided on: an instruction is a hope where a verb is a check.
-
-## The written fallback
-
-The verb ships with the CLI and Step 6 ships with the plugin, so a target holding an older binary meets a missing subcommand. The skill body keeps the written list and applies it by hand there, naming which of the two decided the run.
-
-The fallback is never a skip. Failing open is the exact defect the verb closes, so a body that skips on anything other than a `skip` record would ship every branch unreviewed the moment the subcommand went absent.
-
-Two copies of the path set is what the fallback costs, and it stands until a release retires the written half.

package/governance/rules/canon/601-indexes.md

@@ -1,9 +0,0 @@
----
-description: Check a folder's index before searching its contents
----
-
-# Indexes standards
-
-## Before searching
-
-- Check a folder's `index.md` before grepping its source or reading its files, starting with `canon/context/` for a domain and `canon/wireframes/` for a UI surface. It orients faster than a blind search.

package/governance/rules/canon/603-memory.md

@@ -1,11 +0,0 @@
----
-description: Keep memory writes scoped to .canon/memory/ and out of context-owned domains
----
-
-# Memory standards
-
-## Writing memory
-
-- Write all memory files to `.canon/memory/`, not `~/.claude/projects/`
-- A fact about a domain goes to that domain's `canon/context/` entry, not to memory. `canon:memory-capture` routes it there and `canon:context-fold` folds it in. Memory keeps only what no context entry owns. Report it rather than proceeding silently when either skill does not resolve. Both ship with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have them.
-- Never delete a memory entry. Retire one by moving it to `.canon/memory/archive/`, which `canon records push` backs. A bulk retire runs through the shell, where no file edit fires a path-scoped rule.

package/governance/rules/claude/565-behavior.md

@@ -1,27 +0,0 @@
----
-description: Handle judgment calls, scope discipline, and file-editing mechanics during a session
----
-
-# Behavior standards
-
-## Communication
-
-- Flag concerns or alternatives when a proposed change has tradeoffs worth discussing
-
-## Judgment calls
-
-- When facing a judgment call with 2-3 reasonable options mid-flow, pick one and state the tradeoff in one sentence. Enumerate options only when the user's preference is the deciding factor.
-- Put a call the user's preference decides through the structured question surface, such as `AskUserQuestion` in Claude Code, and fall back to a numbered list in one message where none exists. Rank the recommendation first and mark it, order the rest behind it, and give each option its cost, since an option with no stated cost is picked blind.
-- Author the real choices only. A structured surface appends its own trailing escapes for a free-text answer and for reopening the question as conversation, so never write either as an option. On the numbered-list fallback, say that answering outside the list is fine.
-- Answer from the artifact when one already put the question in writing with a suggestion, rather than re-asking it.
-
-## Scope discipline
-
-- Match edit scope to the request. Ship minimal v1 and queue extensions as follow-ups.
-- On simplification requests, edit only what the user named
-- Do not add features the user did not ask for
-- When rewriting a section, preserve existing code blocks, tables, and grouped examples unless the user asked to remove them
-
-## Editing mechanics
-
-- Edit an existing file with the file-editing tool, never a shell stream editor. An unescaped `&` in a `sed` replacement expands to the whole match, and `sed -i` exits zero when its pattern matches nothing, so both fail silently while reporting success. This governs edits you make, not stream editors written into a project's own scripts.

package/governance/rules/claude/567-planning.md

@@ -1,16 +0,0 @@
----
-description: Enforce planning standards before implementation
----
-
-# Planning standards
-
-## Planning
-
-- Confirm a numbered implementation plan before a change whose diff cannot be described in one sentence.
-- Challenge ambiguous or over-engineered requests before implementation.
-- Search the project, its dependencies, and the standard library for an existing implementation before writing new code.
-- State where the search ran and why each candidate was rejected. Do not assert a search without naming its results.
-- Propose the simplest solution that satisfies the requirement before implementing complex patterns.
-- Write or update tests as part of every implementation plan.
-- Write the test for a behavior before the code that implements it. Confirm visual output after implementing it, not before.
-- Run `canon gov test-order` before shipping a branch. Fix what it names as reaching history ahead of its test.

package/governance/rules/claude/575-hooks.md

@@ -1,16 +0,0 @@
----
-description: State the hook stdin guard and the silencing rule for .claude/hooks scripts
-paths:
-  - '.claude/hooks/**/*.sh'
----
-
-# Hook standards
-
-## Reading a payload
-
-- Open a hook that reads a payload with a bounded `IFS= read -r -d '' -t 2 input`, exiting non-zero on an empty payload. An unbounded `cat` blocks forever against a hand run or an open socket, holding the session open with it.
-
-## Silencing output
-
-- Before silencing a hook's output, name the stage that catches the same failure. A hook that is the only enforcer of a rule makes its documented guarantee false when it discards that output.
-- Where no other stage catches the failure, capture the output into a variable, exit 0 on success, and emit the error lines as `additionalContext`.

package/governance/rules/claude/576-settings.md

@@ -1,13 +0,0 @@
----
-description: State the autoContinueAtUsageLimit inversion and the autoCompactWindow cap for .claude/settings.json
-paths:
-  - '.claude/settings.json'
----
-
-# Settings standards
-
-## Session budget settings
-
-- Never set `autoContinueAtUsageLimit` in this file. Its scope is user or managed, and a repository file setting it while no user, `--settings`, or managed value does makes Claude Code read the setting as off, so writing `true` here turns the behavior off for every operator carrying no value of their own.
-- Treat `autoCompactWindow` as capped at the model's own context window. A value above that cap is inert on a session running a smaller window and bites only on one running the larger, so name the window a recorded value is meant for.
-- Record why a session budget setting is left unset in the project's own development notes rather than in this file. JSON carries no pointer, so a session reading the settings file alone concludes the setting is unconfigured and sets it again.

package/governance/rules/claude/592-claude-md.md

@@ -1,19 +0,0 @@
----
-description: Enforce the CLAUDE.md edit protocol and the test routing a fact into it rather than a rule
-paths:
-  - 'CLAUDE.md'
----
-
-# CLAUDE.md standards
-
-## Editing
-
-- Show the proposed change as a fenced `diff` block in chat first, then wait for approval before calling the file-editing tool.
-
-## Routing
-
-- Keep a rule here when it applies every session regardless of what is being edited, on firing alone.
-- Move a rule into `.claude/rules/` when it fires only on a specific path being edited and violating it ships silently, the same firing axis judged the other way.
-- Route a rule failing either half to a context entry or a skill body rather than here. Firing is one axis of three. Conditional presence and updatability are the other two, and this rule states the first alone.
-- Name a rule's tier rather than a rule file. A path-scoped rule reaches the session on its own glob and needs no pointer from here.
-- Point at a skill by name where one applies. A skill loads only when invoked, so an unreferenced skill is one no session finds.

package/governance/rules/lang/120-bash.md

@@ -1,18 +0,0 @@
----
-description: Route bash script authoring to the wrapper skill, and name the lint gate
-paths:
-  - '**/*.sh'
----
-
-# Bash standards
-
-## Skill routing
-
-- Use `canon:bash-cli-script` before writing a script, and follow its guards on what a shell script may be.
-- Load the skill's own reference template rather than hand-rolling logging patterns outside it.
-- Report it rather than proceeding silently when the skill does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.
-
-## Lint gate
-
-- Format with `shfmt --write --indent 2` and lint with `shellcheck --severity=warning` before committing a script.
-- Fix a shellcheck finding at the source. Suppress one with a directive comment only for a genuine false positive, and state why beside the suppression.

package/governance/rules/standards/architecture.md

@@ -1,13 +0,0 @@
----
-# Generated by `canon gov regen` from standards/architecture.md. Edit that frontmatter, not this file.
-description: Shape and content rules for canon/ARCHITECTURE.md
-paths:
-  - 'canon/ARCHITECTURE.md'
----
-
-# Architecture standards
-
-## Authority
-
-- Follow the architecture standard for shape and content rules for canon/ARCHITECTURE.md. It is the single source. Read it with `canon standards architecture`.
-- Add a decision here only when it fills one of the standard's slots, and write any other decision into the context entry for the domain it constrains. At the record's stated cap, merge or retire an entry before adding one.

package/governance/rules/standards/groundwork.md

@@ -1,13 +0,0 @@
----
-# Generated by `canon gov regen` from standards/groundwork.md. Edit that frontmatter, not this file.
-description: Folder layout, ordinal naming, reserved numbering, frontmatter and dating, required file contents, and conventions for a measurement track
-paths:
-  - '.canon/groundwork/**'
----
-
-# Groundwork standards
-
-## Authority
-
-- Follow the groundwork standard for folder layout, ordinal naming, reserved numbering, frontmatter and dating, required file contents, and conventions for a measurement track. It is the single source. Read it with `canon standards groundwork`.
-- Follow the groundwork spikes standard for `08-spikes.md` and the folders holding what a spike produced. Read it with `canon standards groundwork-spikes`.

package/governance/rules/standards/intake.md

@@ -1,12 +0,0 @@
----
-# Generated by `canon gov regen` from standards/intake.md. Edit that frontmatter, not this file.
-description: Folder layout, ordinal naming, reserved index number, frontmatter and dating, the item template, the answer contract, and retrieval
-paths:
-  - '.canon/intake/**'
----
-
-# Intake standards
-
-## Authority
-
-- Follow the intake standard for folder layout, ordinal naming, reserved index number, frontmatter and dating, the item template, the answer contract, and retrieval. It is the single source. Read it with `canon standards intake`.

package/governance/rules/standards/markdown.md

@@ -1,16 +0,0 @@
----
-# Generated by `canon gov regen` from standards/markdown.md. Edit that frontmatter, not this file.
-description: Headings, paragraph and list structure, code spans, the date form, punctuation, emphasis, file references, American spelling, and frontmatter wording
-paths:
-  - '**/*.md'
----
-
-# Markdown standards
-
-## Authority
-
-- Follow the markdown standard for headings, paragraph and list structure, code spans, the date form, punctuation, emphasis, file references, American spelling, and frontmatter wording. It is the single source. Read it with `canon standards markdown`.
-- Read it before a substantial markdown edit. Do not work the banned characters from memory.
-- Run `canon markdown audit <path>` after the edit, and rewrite the sentence carrying a hit rather than swapping the token for a near-synonym.
-- Voice, rhythm, and sentence construction are a separate topic. `800-prose` routes them.
-- Load the `canon:draft-figure` skill before drafting or revising a Mermaid fence or a figure, and report it rather than proceeding silently when it does not resolve.

package/governance/rules/standards/memory.md

@@ -1,12 +0,0 @@
----
-# Generated by `canon gov regen` from standards/memory.md. Edit that frontmatter, not this file.
-description: Filename and type prefix, frontmatter, the body shape per type, links between entries, and the lifecycle from write to retire
-paths:
-  - '.canon/memory/**'
----
-
-# Memory standards
-
-## Authority
-
-- Follow the memory standard for filename and type prefix, frontmatter, the body shape per type, links between entries, and the lifecycle from write to retire. It is the single source. Read it with `canon standards memory`.

package/governance/rules/standards/ready.md

@@ -1,13 +0,0 @@
----
-# Generated by `canon gov regen` from standards/ready.md. Edit that frontmatter, not this file.
-description: Folder layout, ordinal naming, the overview frontmatter, the thin-plan contract, and the archive lifecycle for a finished-file handoff
-paths:
-  - '.canon/ready/**'
----
-
-# Ready standards
-
-## Authority
-
-- Follow the ready standard for folder layout, ordinal naming, the overview frontmatter, the thin-plan contract, and the archive lifecycle for a finished-file handoff. It is the single source. Read it with `canon standards ready`.
-- Load the `canon:draft-ready` skill to write a ready folder, its overview, the thin plan, and the task row. It owns the procedure. Report it rather than proceeding silently when it does not resolve, since it ships with the plugin and this rule ships with the CLI.

package/governance/rules/standards/requirements.md

@@ -1,12 +0,0 @@
----
-# Generated by `canon gov regen` from standards/requirements.md. Edit that frontmatter, not this file.
-description: Shape and content rules for canon/REQUIREMENTS.md
-paths:
-  - 'canon/REQUIREMENTS.md'
----
-
-# Requirements standards
-
-## Authority
-
-- Follow the requirements standard for shape and content rules for canon/REQUIREMENTS.md. It is the single source. Read it with `canon standards requirements`.

package/governance/rules/standards/session.md

@@ -1,13 +0,0 @@
----
-# Generated by `canon gov regen` from standards/session.md. Edit that frontmatter, not this file.
-description: Filename and location, the sections a handoff carries, the write and read procedures, and how a role extends it
-paths:
-  - '.canon/tasks/session-*.md'
----
-
-# Session map standards
-
-## Authority
-
-- Follow the session standard for filename and location, the sections a handoff carries, the write and read procedures, and how a role extends it. It is the single source. Read it with `canon standards session`.
-- Follow this rule rather than the tasks rule for a `session-` file. A handoff is not a task and carries neither `## Outcomes` nor `## Findings`.

package/governance/rules/standards/tasks.md

@@ -1,15 +0,0 @@
----
-# Generated by `canon gov regen` from standards/tasks.md. Edit that frontmatter, not this file.
-description: Folder layout, filename convention, file format, origin lines, and archiving for task files under .canon/tasks/
-paths:
-  - '.canon/tasks/**'
----
-
-# Tasks standards
-
-## Authority
-
-- Follow the tasks standard for folder layout, filename convention, file format, origin lines, and archiving for task files under .canon/tasks/. It is the single source. Read it with `canon standards tasks`.
-- Follow the board standard for `priority.md` and `backlog.md`, their readiness groups, and row order. Read it with `canon standards board`.
-- Never hand-edit `.canon/tasks/index.md`. A hook regenerates it from sibling frontmatter.
-- Follow the task decline standard for a task decided against. Read it with `canon standards tasks-decline`.

package/governance/rules/standards/teach.md

@@ -1,14 +0,0 @@
----
-# Generated by `canon gov regen` from standards/teach.md. Edit that frontmatter, not this file.
-description: Workspace layout, ordinal naming, frontmatter, and the mission and learning-record formats for a learning workspace
-paths:
-  - '.canon/teach/**'
----
-
-# Teach standards
-
-## Authority
-
-- Follow the teach standard for workspace layout, ordinal naming, frontmatter, and the mission and learning-record formats for a learning workspace. It is the single source. Read it with `canon standards teach`.
-- Follow the glossary standard for the glossary every workspace carries at its root. It is the single source for the entry shape, the ordering, and which terms the file carries. Read it with `canon standards glossary`.
-- Report it rather than proceeding silently when that file does not resolve. It ships with the plugin and this rule ships with the CLI, so a project that installed governance alone does not have it.

package/governance/rules/standards/wiki.md

@@ -1,13 +0,0 @@
----
-# Generated by `canon gov regen` from standards/wiki.md. Edit that frontmatter, not this file.
-description: Folder split, frontmatter, naming convention, and sourcing for a wiki reference page
-paths:
-  - 'wiki/**/*.md'
----
-
-# Wiki standards
-
-## Authority
-
-- Follow the wiki standard for folder split, frontmatter, naming convention, and sourcing for a wiki reference page. It is the single source. Read it with `canon standards wiki`.
-- Read it before drafting a page. Do not work the placement criterion or the naming convention from memory.

package/governance/rules/standards/wireframes.md

@@ -1,13 +0,0 @@
----
-# Generated by `canon gov regen` from standards/wireframes.md. Edit that frontmatter, not this file.
-description: Shape and content rules for canon/wireframes/<surface>.md files
-paths:
-  - 'canon/wireframes/**'
----
-
-# Wireframe standards
-
-## Authority
-
-- Follow the wireframes standard for shape and content rules for canon/wireframes/<surface>.md files. It is the single source. Read it with `canon standards wireframes`.
-- Read it before adding or revising a surface.

package/governance/rules/writing/800-prose.md

@@ -1,15 +0,0 @@
----
-description: Route markdown edits to the write-human skill for voice, rhythm, sentence construction, and information density
-paths:
-  - '**/*.md'
----
-
-# Markdown voice standards
-
-## Authority
-
-- Load the `canon:write-human` skill for voice, rhythm, sentence construction, and information density. It is the single source for all four.
-- Load it before drafting a passage, not after revising one.
-- Report it rather than proceeding silently when the skill does not resolve.
-- Do not work these rules from memory.
-- Punctuation, formatting, and file references are a separate topic. The markdown rule routes them.

package/src/autoship/classify.ts

@@ -1,75 +0,0 @@
-import {
-  BEHAVIOR_FILES,
-  BEHAVIOR_PREFIXES,
-  PROSE_EXTENSIONS,
-} from '@/autoship/paths'
-
-/**
- * Which of the two tests a file failed.
- *
- * Named apart rather than folded into one boolean, because the repair differs.
- * A non-prose extension means the branch carries code and review is ordinary. A
- * behavior path means prose that states what an agent does, which is the half
- * three sessions read past.
- */
-export type FailedTest = 'extension' | 'behavior-path'
-
-/** Why a classification produced no reading. */
-export type ClassifyRefusal = 'no-changes'
-
-export type Classification =
-  | { readonly kind: 'skip' }
-  | {
-      readonly kind: 'review'
-      readonly test: FailedTest
-      readonly file: string
-    }
-  | { readonly kind: 'refused'; readonly reason: ClassifyRefusal }
-
-/**
- * Prefix-anchored against the folders, matching how `resolveCoverage` reads the
- * label map, and equality against the whole paths a prefix cannot reach.
- */
-function underBehaviorPath(path: string): boolean {
-  if (BEHAVIOR_FILES.some((file) => file === path)) return true
-  return BEHAVIOR_PREFIXES.some((prefix) => path.startsWith(prefix))
-}
-
-function readsAsProse(path: string): boolean {
-  const lowered = path.toLowerCase()
-  return PROSE_EXTENSIONS.some((extension) => lowered.endsWith(extension))
-}
-
-/**
- * Decides whether a branch's changed set skips the review pass.
- *
- * The skip needs both tests to pass: every name reads as prose, and no name
- * sits under a behavior path. One behavior file sends the whole branch to
- * review, since documentation shipped beside a behavior change does not cancel
- * it.
- *
- * An empty set refuses rather than skipping. Both tests are universally
- * quantified, so an empty set satisfies them vacuously, and reading that as
- * prose-only would route a branch past review for having produced no output at
- * all.
- *
- * Names only. The caller hands the set the ship chain already computed, so no
- * second baseline is read here and the stale-baseline half stays closed.
- */
-export function classifyChanges(paths: readonly string[]): Classification {
-  if (paths.length === 0) return { kind: 'refused', reason: 'no-changes' }
-
-  // First failure in the caller's order wins, and each file is tested for its
-  // extension before its path. A set failing both tests reports one file and
-  // one test, which is all the branch needs to route.
-  for (const path of paths) {
-    if (!readsAsProse(path)) {
-      return { kind: 'review', test: 'extension', file: path }
-    }
-    if (underBehaviorPath(path)) {
-      return { kind: 'review', test: 'behavior-path', file: path }
-    }
-  }
-
-  return { kind: 'skip' }
-}

package/src/autoship/paths.ts

@@ -1,50 +0,0 @@
-/**
- * The surfaces where markdown states what an agent does, and the extensions
- * that read as prose, held as data one command parses.
- *
- * Lifted verbatim in content from the list `auto-ship` Step 6 carried, whose
- * written fallback copy now sits in `auto-ship/references/verb-absent.md`,
- * which a session was asked to apply by hand. It failed that
- * application three times, so the set moved here and the body now calls a verb
- * that reads it. Being machine-parsed makes it permanently exempt from any
- * later design that folds a standard back into the surface citing it, per the
- * machine-parsed clause in `canon/context/standards/resolution.md`.
- */
-
-/**
- * Path prefixes under which a markdown change is a behavior change.
- *
- * Most carry two spellings, the one a surface authors at and the one it reaches
- * a session at, so the rule reads the same in this toolkit and in a project
- * that consumed one. `standards/` carries one: it never installs into a
- * project, reaching a reader by resolution, so no `.claude/` spelling exists
- * to name.
- */
-export const BEHAVIOR_PREFIXES = [
-  'claude/skills/',
-  '.claude/skills/',
-  'governance/rules/',
-  '.claude/rules/',
-  'standards/',
-  'internal/',
-  'tooling/',
-] as const
-
-/**
- * Behavior surfaces named as whole paths rather than as prefixes.
- *
- * A path prefix reaches nothing that sits in no folder, which is what the root
- * instruction file is. Matching is equality rather than a suffix test, so a
- * nested `docs/CLAUDE.md` stays informational the way the body's "at the
- * repository root" qualifier says it should.
- */
-export const BEHAVIOR_FILES = ['CLAUDE.md'] as const
-
-/**
- * Extensions a changed file may carry for the branch to read as prose-only.
- *
- * Compared lowercased, so a `README.MD` is not routed to review for its
- * spelling. Everything else is code, a config, or an asset, and one of them
- * sends the whole branch to review.
- */
-export const PROSE_EXTENSIONS = ['.md', '.txt'] as const