chaffjs 0.15.0 → 0.17.0

package/rules/sentence-initial-conjunction-run.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 接続詞で始まる文が {count} 文続いています（{limit} 文まで）
-  en: "{count} sentences in a row open with a conjunction (limit {limit})"
+  en: "{count} {count|sentence|sentences} in a row {count|opens|open} with a conjunction (limit {limit})"
 
 how_to_fix:
   ja: どれか 1 つを残して、他は前の文に繋ぐか独立させてください。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
-use_for: [blog, business]
+use_for: [blog, business, legal, docs, academic, literature, speech]

package/rules/sentence-rhythm.yaml

@@ -27,4 +27,4 @@ levels:
   normal: 30
   relaxed: 20
 
-use_for: [blog]
+use_for: [blog, legal, docs, academic, literature, speech]

package/rules/stray-space.yaml

@@ -0,0 +1,38 @@
+id: stray-space
+layer: L3
+status: experimental
+how_to_find: stray-space
+# どの境目が一続きの語句の中かは、語の品詞で決める。品詞が無ければ動かない。
+requires: [pos]
+languages: [ja]
+severity: warning
+
+name:
+  ja: 語句の途中に空白がある
+  en: Stray space inside a phrase
+
+why:
+  ja: 「こころさんが 払った」「確認 しました」のように、一続きに読む語句の途中に空白が入ると、読み手はそこで区切れるのかと迷います。打ち直しや貼り付けで残りやすく、目で見ても気づきにくい空白です。chaff は二つの境目を別々に数えます。助詞の後ろ（「が 払った」、文節の切れ目）と、文節を始められない語の前（「アプリ が」の助詞、「行き ます」の助動詞、「確認 しました」の「する」）です。文節ごとに空けて書く分かち書き（子ども向けの文や、日本語を学ぶ人向けの文）は書き方の一つなので、chaff はどちらが正しいかを決めず、文書の中で空けたほうが少ないときだけ、その空白を指摘します。名詞どうしのあいだ（「担当 田中」の名札と値、「赤坂 文弥」の名前、「サムネイル キャッシュ」の複合語）は書き方として空けることが多いので数えません。句点で終わらない行（歌、名札と値、表のような行）、見出し、表、行頭の全角空白の字下げ、行頭の項目の記号（「イ　」）の後ろ、Markdown の改行、鉤括弧（「」『』）で引いたものの中、英字・数字との境目（latin-spacing が見ます）も数えません。
+  en: A space inside what reads as one phrase in Japanese (こころさんが 払った, 確認 しました) makes the reader wonder whether the phrase breaks there. It is typically left over from retyping or pasting and is easy to miss by eye. chaff counts two kinds of joint separately, after a particle (が 払った, the break between phrases) and before a word that cannot start a phrase (a particle as in アプリ が, an auxiliary as in 行き ます, or する after a noun as in 確認 しました). Spacing every phrase (分かち書き, as in text for children or for learners of Japanese) is a way of writing, so chaff does not decide which is right; it reports the spaces only when the document spaces less often than it does not. A space between two nouns (a label and its value as in 担当 田中, a name as in 赤坂 文弥, a compound as in サムネイル キャッシュ) is often written on purpose and is not counted. Neither are lines that do not end with a full stop (verse, labels and values, table-like lines), headings, tables, a full-width indent at the start of a line, the space after an item mark at the start of a line (イ　), a Markdown line break, the inside of a quotation in 「」 or 『』, or a boundary with Latin letters or digits (latin-spacing looks at those).
+
+message:
+  ja: "「{before}」と「{after}」のあいだに空白があります（この文書では {of} 箇所のうち {count} 箇所が空いている）"
+  en: 'Space between "{before}" and "{after}" ({count} of {of} in this document are spaced)'
+
+messages:
+  between-phrases:
+    ja: "助詞「{before}」と「{after}」のあいだに空白があります（この文書は文節のあいだをふつう詰めて書く。{of} 箇所のうち {count} 箇所が空いている）"
+    en: 'Space after the particle "{before}" before "{after}" (this document usually writes phrases without a space; {count} of {of} are spaced)'
+  inside-phrase:
+    ja: "「{before}」と「{after}」は一続きの語句ですが、あいだに空白があります（{of} 箇所のうち {count} 箇所が空いている）"
+    en: '"{before}" and "{after}" read as one phrase but are separated by a space ({count} of {of} are spaced)'
+
+how_to_fix:
+  ja: 空白を消して詰めてください。文節ごとに空ける書き方をしているなら、文書全体でそろえてください。
+  en: Delete the space. If the document spaces its phrases on purpose, do so throughout.
+
+# 何箇所空いていれば指摘するか。1 は「1 箇所でも空いていれば」。
+levels: { strict: 1, normal: 1, relaxed: 3 }
+
+# 歌の行は句点で終わらないので、ジャンルを問わず数えない。
+use_for: [business, blog, technical, legal, docs, academic, literature, speech]

package/rules/taigen-dome-in-prose.yaml

@@ -16,7 +16,7 @@ why:
 
 message:
   ja: 本文に体言止めが {count} 文あります（{limit} 文まで）
-  en: "{count} sentences end on a noun in the body text (limit {limit})"
+  en: "{count} {count|sentence|sentences} {count|ends|end} on a noun in the body text (limit {limit})"
 
 how_to_fix:
   ja: 述語を足してください。「〜が課題。」を「〜が課題です。」に。
@@ -24,4 +24,4 @@ how_to_fix:
 
 levels: { strict: 2, normal: 4, relaxed: 8 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/title-case-consistency.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 3, normal: 2, relaxed: 1 }
 
-use_for: [blog, business, technical]
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]

package/rules/total-mismatch.yaml

@@ -23,4 +23,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 1, relaxed: 1 }
 
-use_for: [business, technical, blog]
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]

package/rules/undefined-acronym.yaml

@@ -14,6 +14,7 @@ extra_word_lists:
     emphasis-word,
     numbered-division,
     honorific,
+    name-title,
     date-time-unit,
     http-method,
   ]
@@ -30,12 +31,12 @@ why:
 
 message:
   ja: 「{word}」が説明なしで使われています（説明のない略語 {count} 個）
-  en: '"{word}" is used without an expansion ({count} such acronyms)'
+  en: '"{word}" is used without an expansion ({count} such {count|acronym|acronyms})'
 
 how_to_fix:
-  ja: 初出のところで括弧に入れて展開してください。「CI（継続的インテグレーション）」のように。
-  en: Expand it in brackets at first use.
+  ja: 初出のところで括弧に入れて展開してください。「CI（継続的インテグレーション）」のように。読み手が名前として知っている略語（社名など）なら、chaff.yaml の names に並べると求めません。
+  en: Expand it in brackets at first use. If your readers know it as a name (a company, say), list it under names in chaff.yaml and it is not asked for.
 
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
-use_for: [business, technical]
+use_for: [business, technical, legal, docs, academic, literature, speech]

package/rules/unqualified-superlative.yaml

@@ -17,7 +17,7 @@ why:
 
 message:
   ja: 「{matched}」に比べる相手がありません（そういう言い方が {count} 箇所）
-  en: '"{matched}" has nothing to compare against ({count} such claims)'
+  en: '"{matched}" has nothing to compare against ({count} such {count|claim|claims})'
 
 how_to_fix:
   ja: 比較対象か条件を添えてください。「社内の 3 案のうち最も速い」のように。
@@ -25,4 +25,4 @@ how_to_fix:
 
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
-use_for: [business, blog]
+use_for: [business, blog, legal, docs, academic, literature, speech]

package/skills/chaff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: chaff
-description: "Check prose with chaff (npx chaffjs): run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why. Use when asked to lint, proofread or tighten documents, or to set up a team's writing rules."
+description: "Check prose with chaff (npx chaffjs): pick the genre preset for the kind of document (contract, statute, manual, FAQ, paper, fiction, transcript…), run it on Markdown or text, read each finding, fix the text or record why not, and tune chaff.yaml with rules --json and relax --why. Use when asked to lint, proofread or tighten documents, or to set up a team's writing rules."
 ---
 
 # Checking writing with chaff
@@ -9,12 +9,30 @@ chaff finds what makes writing hard to read — long sentences, padding, mixed s
 contract — and never rewrites anything. Reading the findings and changing the text is your part. Japanese and
 English documents both work; the language is detected per file.
 
+## Pick the genre first
+
+A genre is a preset for one kind of document: which rules run, where their limits are, and how the document is
+read. A contract checked as a blog post gets wrong findings, so choose the genre before reading any finding.
+
+1. Name the kind from the document itself. `npx chaffjs genres` lists every genre with what it is for:
+   `legal/contract`, `legal/statute`, `docs/manual`, `docs/faq`, `academic/paper`, `literature/fiction`,
+   `speech/transcript`, `business/report`, `technical/spec`, …
+2. Unsure? Run once without `--genre`. When the file looks like another kind, the line under the header says so
+   (`Looks like: Contract and terms. Try --genre legal/contract`); use that genre if it fits.
+3. Run with it: `npx chaffjs --genre legal/contract contract.md`. For a folder of one kind,
+   `npx chaffjs init --genre legal/contract` writes it into `chaff.yaml` (always pass `--genre`: without it,
+   `init` asks at a terminal).
+4. The header's first line shows the genre used and where it came from. Check it before trusting the findings.
+
+A rule the genre turns off is listed under "did not run" with the genre as the reason. That is the preset's
+choice, not a gap; turn it back on (`rules:` in `chaff.yaml`) only when the person asks.
+
 ## Run it
 
 ```sh
-npx chaffjs <file|dir|glob>...     # human-readable, one block per finding (a folder or glob picks up .md / .markdown / .mdx; name a .txt file directly)
-npx chaffjs . --compact            # two lines per finding: line:col severity message, then the rule id
-npx chaffjs <file> --experimental  # also the experimental rules
+npx chaffjs --genre <genre> <file|dir|glob>...   # human-readable, one block per finding (a folder or glob picks up .md / .markdown / .mdx; name a .txt file directly)
+npx chaffjs . --compact                          # two lines per finding: line:col severity message, then the rule id
+npx chaffjs <file> --experimental                # also the experimental rules
 ```
 
 A run exits 1 when a finding is an `error`. It also exits 1 when it could not check anything: no file to
@@ -39,15 +57,16 @@ relaxing a rule.
 
 ## Tune chaff.yaml
 
-- `npx chaffjs init` writes a commented `chaff.yaml` when there is none (an existing one is left as it is), and
-  adds `.chaff-cache/` and `.env*` to `.gitignore`.
-- `npx chaffjs rules --json` prints every rule with its levels, the setting in effect (`now`) and why a rule is
-  off. Read it instead of guessing rule names or limits.
+- `npx chaffjs init --genre <genre>` writes a commented `chaff.yaml` for that genre when there is none (an
+  existing one is left as it is), and adds `.chaff-cache/` and `.env*` to `.gitignore`.
+- `npx chaffjs rules --json [--genre <genre>]` prints every rule with its levels, the setting in effect (`now`,
+  the genre's preset included) and why a rule is off. Read it instead of guessing rule names or limits.
 - A level is `strict` / `normal` / `relaxed` / `off`; when even `relaxed` is too tight, a positive number is the
   limit itself (`max-sentence-length: 260`).
 - `prefer:` maps spellings to the team's (`e-mail: email`); `preferred-term: normal` turns the rule on.
 - Unknown rule names and unreadable values are reported on stderr — read stderr after editing `chaff.yaml`.
-- `genre:` sets the kind of document (`npx chaffjs genres` lists them); `--genre` overrides it for one run.
+- `genre:` sets the kind of document; `by_path` sets one per folder; `--genre` overrides both for one run.
+  `rules:` wins over the genre's preset.
 
 ## Structured documents
 

package/src/address-chain.ts

@@ -78,7 +78,7 @@ const chainAt = (patterns: Compiled, text: string, start: number): { readonly sp
   const firstEnd = matchEnd(patterns.address, text, start);
   if (firstEnd === undefined) return undefined;
   const { spans, cuts } = readChain(patterns, text, { start, end: firstEnd });
-  const cut = [...cuts].reverse().find((candidate) => endsHere(patterns, text, candidate.end));
+  const cut = cuts.findLast((candidate) => endsHere(patterns, text, candidate.end));
   return cut === undefined ? undefined : { spans: spans.slice(0, cut.addresses), end: cut.end };
 };
 

package/src/backends/anthropic.ts

@@ -4,6 +4,7 @@ import { join } from "node:path";
 import Anthropic from "@anthropic-ai/sdk";
 import { toFailure } from "./types.ts";
 import type { Failure, Judge, Prompt } from "./types.ts";
+import type { Texts } from "../ui.ts";
 
 type AnthropicResponse = { readonly content: readonly { readonly type: string; readonly text?: string | undefined }[] };
 
@@ -58,4 +59,7 @@ export const judge =
   };
 
 /** 認証が無いときに人へ見せる案内。 */
-export const SETUP_HINT = "ANTHROPIC_API_KEY を設定するか、ant auth login を実行してください。";
+export const SETUP_HINT: Texts<string> = {
+  ja: "ANTHROPIC_API_KEY を設定するか、ant auth login を実行してください。",
+  en: "Set ANTHROPIC_API_KEY, or run ant auth login.",
+};

package/src/backends/openai.ts

@@ -1,6 +1,7 @@
 import OpenAI from "openai";
 import { toFailure } from "./types.ts";
 import type { Failure, Judge, Prompt } from "./types.ts";
+import type { Texts } from "../ui.ts";
 
 type OpenAIResponse = { readonly choices: readonly { readonly message: { readonly content: string | null } }[] };
 
@@ -43,4 +44,4 @@ export const judge =
     return body;
   };
 
-export const SETUP_HINT = "OPENAI_API_KEY を設定してください。";
+export const SETUP_HINT: Texts<string> = { ja: "OPENAI_API_KEY を設定してください。", en: "Set OPENAI_API_KEY." };

package/src/backends/types.ts

@@ -17,11 +17,12 @@ const BACKENDS: readonly BackendName[] = ["anthropic", "openai"];
 export const isBackend = (value: unknown): value is BackendName => BACKENDS.some((name) => name === value);
 
 /** API が返した失敗。生のスタックトレースを人に見せないための、最小の分類。 */
-export type Failure = { readonly kind: "auth" | "quota" | "api"; readonly status: number | undefined; readonly message: string };
+/** message is the provider's own words, undefined when it gave none: the screen says so in the reader's language. */
+export type Failure = { readonly kind: "auth" | "quota" | "api"; readonly status: number | undefined; readonly message: string | undefined };
 
 const statusOf = (value: unknown): number | undefined => (typeof value === "number" ? value : undefined);
 
-const messageOf = (value: unknown): string => (typeof value === "string" && value.length > 0 ? value : "原因は返ってきませんでした");
+const messageOf = (value: unknown): string | undefined => (typeof value === "string" && value.length > 0 ? value : undefined);
 
 const kindOf = (status: number | undefined): Failure["kind"] => {
   if (status === 401 || status === 403) return "auth";

package/src/baseline.ts

@@ -29,7 +29,7 @@ export const readBaseline = (path: string): Baseline | undefined => {
 };
 
 export const writeBaseline = (path: string, entries: readonly string[]): void => {
-  const sorted = [...entries].sort((left, right) => left.localeCompare(right, "en"));
+  const sorted = entries.toSorted((left, right) => left.localeCompare(right, "en"));
   const body = { version: 1, created: new Date().toISOString().slice(0, 10), entries: sorted };
   writeFileSync(path, `${JSON.stringify(body, null, 2)}\n`, "utf8");
 };

package/src/calendar-number.ts

@@ -0,0 +1,84 @@
+import { digitRunAround } from "./number-name.ts";
+import type { ProseDocument, Span, Token } from "./plugin.ts";
+
+/**
+ * 日付・時刻として書かれた数（9月、3時、2026年、10月1日、10時5分）。数を詰めて書くのが決まりで、空け方の好みではない。
+ * 長さ（3ヶ月、3時間、3日間）は別の語で書くので、ここには入らない。
+ *
+ * 単位は語彙表から渡す。chained は日付・時刻の単位を大きい順に（年月日時分秒）。大きい単位の後ろに小さい単位を続けて書けば
+ * 一つの日付・時刻になる。「2008年 2年連続」のように同じ単位や大きい単位が続けば、別のものの始まり。
+ * positional は数の後ろに置くだけで位置を言う単位（月、時）。year は 4 桁の数の後ろで暦の年を言う単位（年、年度）。
+ * 「5日」「5分」「3年」のように、単位だけでは長さと見分けのつかないものは、位置を言う単位と続けて書いたときだけ日付・時刻と読む。
+ */
+export type CalendarUnits = { readonly chained: readonly string[]; readonly positional: ReadonlySet<string>; readonly year: ReadonlySet<string> };
+
+/** 日付・時刻の数の並び。first は日付の頭の数、inner は前の単位に続く数（2026年9月の 9）。unit は数の後ろの単位（月）。 */
+export type CalendarRun = { readonly run: Span; readonly place: "first" | "inner"; readonly unit: string };
+
+/** 数の並びと、その後ろの単位の終わり（文の中の位置）。rank は chained の中の単位の順（無ければ -1）、anchored は単位だけで日付・時刻と分かるもの。 */
+type Part = { readonly run: Span; readonly unit: string; readonly unitEnd: number; readonly rank: number; readonly anchored: boolean };
+
+const DIGIT = /\d/u;
+const CALENDAR_YEAR = /^\d{4}$/u;
+
+/** text の中の数の並び（数字・小数点・ハイフン）を左から。 */
+export const digitRuns = (text: string): Span[] => {
+  const runs: Span[] = [];
+  let at = 0;
+  while (at < text.length) {
+    const run = DIGIT.test(text[at] ?? "") ? digitRunAround(text, at) : undefined;
+    if (run !== undefined) runs.push(run);
+    at = Math.max(run?.end ?? 0, at + 1);
+  }
+  return runs;
+};
+
+/** 空白 1 つを越えた位置。 */
+const pastSpace = (text: string, at: number): number => (text[at] === " " ? at + 1 : at);
+
+const isUnit = (surface: string, units: CalendarUnits): boolean => units.chained.includes(surface) || units.positional.has(surface) || units.year.has(surface);
+
+const isAnchor = (digits: string, surface: string, units: CalendarUnits): boolean =>
+  units.positional.has(surface) || (units.year.has(surface) && CALENDAR_YEAR.test(digits));
+
+/** 数のすぐ後ろ（空白 1 つまで）の語が日付・時刻の単位なら、その組。語の切れ目が合わなければ組にしない。 */
+const partOf = (text: string, run: Span, tokens: readonly Token[], base: number, units: CalendarUnits): Part | undefined => {
+  const unit = tokens.find((token) => token.span.start === base + pastSpace(text, run.end));
+  if (unit === undefined || !isUnit(unit.surface, units)) return undefined;
+  const rank = units.chained.indexOf(unit.surface);
+  return { run, unit: unit.surface, unitEnd: unit.span.end - base, rank, anchored: isAnchor(text.slice(run.start, run.end), unit.surface, units) };
+};
+
+/** 前の組の単位のすぐ後ろ（空白 1 つまで）から始まり、単位が前より小さい組か。 */
+const continues = (text: string, previous: Part | undefined, part: Part): boolean =>
+  previous !== undefined && previous.rank >= 0 && part.rank > previous.rank && part.run.start === pastSpace(text, previous.unitEnd);
+
+/** 前の組に続く組を、同じ日付・時刻にまとめる。 */
+const chainsOf = (text: string, parts: readonly Part[]): Part[][] =>
+  parts.reduce<Part[][]>((chains, part) => {
+    const chain = chains.at(-1);
+    if (chain !== undefined && continues(text, chain.at(-1), part)) chain.push(part);
+    else chains.push([part]);
+    return chains;
+  }, []);
+
+/**
+ * 文 text の中の、日付・時刻の数の並び。tokens は文書全体の座標で、base は text の先頭の位置。
+ * 品詞が無ければ判断せず、何も返さない。
+ */
+export const calendarRuns = (text: string, tokens: readonly Token[] | undefined, base: number, units: CalendarUnits): CalendarRun[] => {
+  if (tokens === undefined) return [];
+  const parts = digitRuns(text).flatMap((run) => partOf(text, run, tokens, base, units) ?? []);
+  return chainsOf(text, parts)
+    .filter((chain) => chain.some((part) => part.anchored))
+    .flatMap((chain) => chain.map((part, index): CalendarRun => ({ run: part.run, place: index === 0 ? "first" : "inner", unit: part.unit })));
+};
+
+const patternList = (doc: ProseDocument, id: string): string[] => (doc.lexicons[id] ?? []).map((entry) => entry.pattern);
+
+/** 文書の言語の、日付・時刻の単位の語彙表。表の無い言語では空で、日付・時刻の数は見つからない。 */
+export const calendarUnitsOf = (doc: ProseDocument): CalendarUnits => ({
+  chained: patternList(doc, "date-time-unit"),
+  positional: new Set(patternList(doc, "calendar-unit")),
+  year: new Set(patternList(doc, "calendar-year-unit")),
+});

package/src/cli-args.ts

@@ -2,8 +2,8 @@
  * Options of the commands that take files to check, whose value is the next argument. That value is not a file.
  * `--why` (relax), `--format` and `--language` (tree) belong to commands that read their own arguments.
  */
-export const VALUE_FLAGS: readonly string[] = ["--sarif", "--genre", "--rule", "--line"];
+const VALUE_FLAGS: ReadonlySet<string> = new Set(["--sarif", "--genre", "--rule", "--line"]);
 
 /** The arguments that name what to check: everything that is neither an option nor an option's value. */
 export const targetsOf = (args: readonly string[]): string[] =>
-  args.filter((arg, index) => !arg.startsWith("--") && !(index > 0 && VALUE_FLAGS.includes(args[index - 1] ?? "")));
+  args.filter((arg, index) => !arg.startsWith("--") && !(index > 0 && VALUE_FLAGS.has(args[index - 1] ?? "")));

package/src/cli-text.ts

@@ -1,7 +1,9 @@
 // What the command line says, in Japanese and English. Per-file text follows the file's language; the rest
 // follows hostLanguage (chaff.yaml's language, else the terminal's locale).
 import type { Texts } from "./ui.ts";
+import { counted, formFor } from "./render/plural.ts";
 import type { GenreSetting } from "./genre-check.ts";
+import type { ProfileSetting } from "./profile/check.ts";
 
 /** Where a file's genre came from, as the header names it. */
 export type GenreSource = "--genre" | "by_path" | "config" | "default" | "front-matter" | "path" | "content";
@@ -12,11 +14,11 @@ const USAGE_JA = `chaff — 文章の読みにくいところを見つけます
   chaff .                        この場所の Markdown を全部
   chaff test <file|dir>...       意味を読む検査も動かす（API key が要ります）
                                  判定役は chaff.yaml の ai_backend で選びます
-  chaff init                     chaff.yaml を作る
+  chaff init                     chaff.yaml を作る（端末ならジャンルを尋ねる。--genre <ジャンル> でも選べる）
   chaff --version                chaffjs と言語パッケージの版
   chaff eval <dir>               手元の文書で閾値を測り直す
   chaff explain <rule>           そのルールの意図と根拠を読む
-  chaff genres                   ジャンルの一覧
+  chaff genres                   ジャンル（文書の種類）の一覧と、それぞれ何向けか
   chaff tree <file> [--format sexp|json]  文書を番地の付いた木にする（条・項・定義・参照）
   chaff cite <原文> <引用.json>           回答の引用（番地と引用文）が原文にあるかを確かめる
   chaff rules --json             いまの設定を JSON で出す（AI に渡す用）
@@ -46,11 +48,11 @@ const USAGE_EN = `chaff — finds what makes writing hard to read. It never rewr
   chaff .                        every Markdown file here
   chaff test <file|dir>...       also run the checks that read meaning (needs an API key)
                                  the judge is chosen by ai_backend in chaff.yaml
-  chaff init                     create chaff.yaml
+  chaff init                     create chaff.yaml (asks for the genre at a terminal; --genre <genre> chooses it)
   chaff --version                the version of chaffjs and its language packages
   chaff eval <dir>               re-measure the limits on your own documents
   chaff explain <rule>           read what a rule is for and why
-  chaff genres                   list the genres
+  chaff genres                   list the genres (kinds of document) and what each is for
   chaff tree <file> [--format sexp|json]  the document as a tree of addresses (sections, clauses, definitions, references)
   chaff cite <source> <quotes.json>       check that quoted passages (address and text) are in the source
   chaff rules --json             the current settings as JSON (to give to an AI)
@@ -79,22 +81,25 @@ export type CliText = {
   readonly languageName: (language: string) => string;
   readonly genreSource: Readonly<Record<GenreSource, string>>;
   readonly header: (path: string, genre: string, language: string, from: string, shelved: number, hushed: number) => string;
+  readonly suggested: (name: string, genre: string) => string;
+  readonly suggestedNote: (name: string, genre: string, used: string) => string;
   readonly noMarkdown: (targets: string) => string;
   readonly noMarkdownHere: string;
   readonly noAdapter: (language: string) => string;
   readonly unknownGenre: (genre: string, where: string, known: readonly string[]) => string;
   readonly genreWhere: (where: GenreSetting, files: readonly string[]) => string;
   readonly unreadFrontMatterGenre: (path: string, genre: string, known: readonly string[]) => string;
+  readonly unknownProfile: (profile: string, where: string, known: readonly string[]) => string;
+  readonly profileWhere: (where: ProfileSetting, files: readonly string[]) => string;
   readonly unknownRule: (id: string) => string;
   readonly unknownRuleWithList: (id: string, list: string) => string;
   readonly unnamed: string;
   readonly sarifWritten: (path: string, count: number) => string;
   readonly unchanged: string;
-  readonly findingsUnit: string;
+  readonly findingsUnit: (count: number) => string;
   readonly watching: (files: number, findings: number) => string;
   readonly watchHint: string;
   readonly baselineDone: (files: number, entries: number, file: string) => readonly string[];
-  readonly genres: (list: readonly string[]) => string;
   readonly unit: (ruleId: string, language: string) => string;
 };
 
@@ -115,6 +120,9 @@ export const CLI_TEXT: Texts<CliText> = {
       [`${path}   ${genre} · ${language}   ジャンルは${from}から`, shelved > 0 ? `   棚上げ ${shelved} 件` : "", hushed > 0 ? `   stet ${hushed} 件` : ""].join(
         "",
       ),
+    suggested: (name, genre) => `   ${name}のようです。--genre ${genre} を試せます`,
+    suggestedNote: (name, genre, used) =>
+      `  ジャンルを決めていないので、${used} として見ました。${name}なら、--genre ${genre} でその種類の書き方に合わせて見ます（npx chaffjs genres で一覧）。`,
     noMarkdown: (targets) => `Markdown が 1 つも見つかりませんでした: ${targets}`,
     noMarkdownHere: "Markdown が 1 つも見つかりませんでした。",
     noAdapter: (language) => `言語 "${language}" のアダプタがありません。`,
@@ -126,12 +134,15 @@ export const CLI_TEXT: Texts<CliText> = {
     },
     unreadFrontMatterGenre: (path, genre, known) =>
       `${path}: front matter の genre "${genre}" はジャンルではないので読みませんでした。使えるのは ${known.join("、")} です。`,
+    unknownProfile: (profile, where, known) =>
+      `文書の種類 "${profile}" はありません（${where}）。使えるのは ${known.join("、")} と、種類を使わない none です。`,
+    profileWhere: (where, files) => (where === "config" ? "chaff.yaml の profile" : `chaff.yaml の by_path、files: ${files.join(", ")}`),
     unknownRule: (id) => `${id} というルールはありません。npx chaff rules --json で一覧が出ます。`,
     unknownRuleWithList: (id, list) => `${id} というルールはありません。\n一覧:\n${list}`,
     unnamed: "(名前なし)",
     sarifWritten: (path, count) => `\n  SARIF を書きました: ${path}（${count} 件）`,
     unchanged: "変わりませんでした",
-    findingsUnit: " 件",
+    findingsUnit: () => " 件",
     watching: (files, findings) => `\n  ${files} ファイルを見ています。いまの指摘は ${findings} 件です。`,
     watchHint: "  保存するたびに、変わったところだけ出します。止めるには Ctrl-C。\n",
     baselineDone: (files, entries, file) => [
@@ -144,8 +155,6 @@ export const CLI_TEXT: Texts<CliText> = {
       `  ${file} を commit してください。`,
       "",
     ],
-    genres: (list) =>
-      ["", "  使えるジャンル:", ...list.map((genre) => `    ${genre}`), "", "  chaff.yaml の genre に書くか、--genre で指定します。", ""].join("\n"),
     unit: (ruleId, language) => {
       if (ruleId === "bold-density") return "1000 字あたりの箇所数";
       if (ruleId !== "max-sentence-length") return "回";
@@ -166,6 +175,9 @@ export const CLI_TEXT: Texts<CliText> = {
     },
     header: (path, genre, language, from, shelved, hushed) =>
       [`${path}   ${genre} · ${language}   genre from ${from}`, shelved > 0 ? `   ${shelved} shelved` : "", hushed > 0 ? `   ${hushed} stet` : ""].join(""),
+    suggested: (name, genre) => `   Looks like: ${name}. Try --genre ${genre}`,
+    suggestedNote: (name, genre, used) =>
+      `  No genre was set, so this was checked as ${used}. If it is ${name}, --genre ${genre} checks it the way that kind is written (npx chaffjs genres lists them).`,
     noMarkdown: (targets) => `No Markdown files found: ${targets}`,
     noMarkdownHere: "No Markdown files found.",
     noAdapter: (language) => `No language package for "${language}".`,
@@ -176,25 +188,27 @@ export const CLI_TEXT: Texts<CliText> = {
     },
     unreadFrontMatterGenre: (path, genre, known) =>
       `${path}: the front matter's genre "${genre}" is not a genre, so it was not used. The genres are ${known.join(", ")}.`,
+    unknownProfile: (profile, where, known) =>
+      `There is no document profile "${profile}" (${where}). The profiles are ${known.join(", ")}; none uses no profile.`,
+    profileWhere: (where, files) => (where === "config" ? "profile in chaff.yaml" : `by_path in chaff.yaml, files: ${files.join(", ")}`),
     unknownRule: (id) => `There is no rule named ${id}. npx chaff rules --json lists them.`,
     unknownRuleWithList: (id, list) => `There is no rule named ${id}.\nRules:\n${list}`,
     unnamed: "(no name)",
-    sarifWritten: (path, count) => `\n  Wrote SARIF: ${path} (${count} finding${count === 1 ? "" : "s"})`,
+    sarifWritten: (path, count) => `\n  Wrote SARIF: ${path} (${counted(count, "finding")})`,
     unchanged: "no change",
-    findingsUnit: " findings",
-    watching: (files, findings) => `\n  Watching ${files} file${files === 1 ? "" : "s"}. ${findings} finding${findings === 1 ? "" : "s"} now.`,
+    findingsUnit: (count) => ` ${formFor(count, "finding", "findings")}`,
+    watching: (files, findings) => `\n  Watching ${counted(files, "file")}. ${counted(findings, "finding")} now.`,
     watchHint: "  Each save prints only what changed. Ctrl-C to stop.\n",
     baselineDone: (files, entries, file) => [
       "",
-      `  Checked ${files} file${files === 1 ? "" : "s"}.`,
+      `  Checked ${counted(files, "file")}.`,
       "",
-      `  Recorded ${entries} finding${entries === 1 ? "" : "s"} in ${file}.`,
+      `  Recorded ${counted(entries, "finding")} in ${file}.`,
       "  They will not be reported again; only new ones will.",
       "",
       `  Commit ${file}.`,
       "",
     ],
-    genres: (list) => ["", "  Genres:", ...list.map((genre) => `    ${genre}`), "", "  Set one with genre in chaff.yaml, or with --genre.", ""].join("\n"),
     unit: (ruleId, language) => {
       if (ruleId === "bold-density") return "places per 1000 characters";
       if (ruleId !== "max-sentence-length") return "times";