chaffjs 0.2.0 → 0.4.0

package/rules/oxford-comma-consistency.yaml

@@ -0,0 +1,26 @@
+id: oxford-comma-consistency
+layer: L3
+status: experimental
+how_to_find: oxford-comma
+languages: [en]
+severity: info
+
+name:
+  ja: 並列の読点が揃っていない
+  en: Oxford comma use is inconsistent
+
+why:
+  ja: 最後の and の前に読点を打つかは、スタイルガイドで割れます。どちらが正しいかは決めません。1 つの文書で混ざっていると、読み手は項目の切れ目を毎回読み直すことになります。
+  en: Whether to put a comma before the final "and" is a style-guide split. Neither is wrong. Mixed within one document, the reader re-parses every list.
+
+message:
+  ja: この文だけ並列の読点の打ちかたが他と違います（文書の中で {count} 文）
+  en: "This list punctuates differently from the rest ({count} in this document)"
+
+how_to_fix:
+  ja: 多いほうに揃えてください。
+  en: Match the majority.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+use_for: [blog, business, technical]

package/rules/paragraph-length-variance.yaml

@@ -0,0 +1,25 @@
+id: paragraph-length-variance
+layer: L1
+status: experimental
+how_to_find: paragraph-variance
+severity: info
+
+name:
+  ja: 段落の長さが揃いすぎている
+  en: Paragraph lengths are too uniform
+
+why:
+  ja: 人が書くと、言いたいことの重さで段落の長さは揺れます。揃いすぎは、埋めるために長さを合わせた跡です。
+  en: When a person writes, paragraph length follows what matters. Uniform length is the mark of filling a shape.
+
+message:
+  ja: 段落の長さのばらつきが {variance}% しかありません（{limit}% 以上ほしい）
+  en: Paragraph length varies by only {variance}% (want at least {limit}%)
+
+how_to_fix:
+  ja: 短くできる段落を短くしてください。全部を同じ長さにしないこと。
+  en: Let the short ones be short.
+
+levels: { strict: 40, normal: 30, relaxed: 20 }
+
+use_for: [blog]

package/rules/preamble-length.yaml

@@ -0,0 +1,25 @@
+id: preamble-length
+layer: L1
+status: experimental
+how_to_find: preamble-length
+severity: info
+
+name:
+  ja: 本題に入るまでが長い
+  en: Too long before the point
+
+why:
+  ja: 業務文書の読み手は結論を探しに来ています。最初の見出しまでに段落が重なると、探す手間だけが増えます。
+  en: A reader of a business document is looking for the decision. Paragraphs before the first heading only delay it.
+
+message:
+  ja: 最初の見出しまでに {count} 段落あります（{limit} 段落まで）
+  en: "{count} paragraphs before the first heading (limit {limit})"
+
+how_to_fix:
+  ja: 結論を先に書くか、前置きを見出しの下へ移してください。
+  en: Put the conclusion first, or move the preamble under a heading.
+
+levels: { strict: 1, normal: 2, relaxed: 4 }
+
+use_for: [business]

package/rules/proper-noun-density.yaml

@@ -0,0 +1,26 @@
+id: proper-noun-density
+layer: L3
+status: experimental
+how_to_find: proper-noun-density
+requires: [pos]
+severity: info
+
+name:
+  ja: 固有名詞が多い
+  en: Too many proper nouns
+
+why:
+  ja: 製品名・社名・人名が続くと、それを知らない読者は文の骨組みを見失います。知っている人には読めるので、書いた本人には気づきにくいところです。
+  en: A run of product, company and person names hides the shape of the sentence from anyone who does not already know them. It reads fine to the person who wrote it.
+
+message:
+  ja: 1000 語あたり {density} 個の固有名詞があります（{limit} 個まで）
+  en: "{density} proper nouns per 1000 words (limit {limit})"
+
+how_to_fix:
+  ja: 2 度目からは「その製品」「そのチーム」のように受けてください。初出で何者かを一言添えると、知らない人も読めます。
+  en: After first use, refer back to it. One phrase saying what it is lets a stranger keep reading.
+
+levels: { strict: 20, normal: 40, relaxed: 80 }
+
+use_for: [blog, business, technical]

package/rules/repeated-conjunction.yaml

@@ -0,0 +1,26 @@
+id: repeated-conjunction
+layer: L2
+status: experimental
+how_to_find: repeated-conjunction
+word_list: paragraph-opener
+severity: warning
+
+name:
+  ja: 段落が同じ調子で始まり続ける
+  en: Paragraphs keep opening the same way
+
+why:
+  ja: 接続詞で始まる段落は 1 つなら流れを作りますが、続くとどの段落も前の付け足しに見えて、話がどこへ向かっているのか分からなくなります。
+  en: One paragraph opening with a conjunction carries the flow. A run of them makes every paragraph an afterthought.
+
+message:
+  ja: 接続詞で始まる段落が {count} 続いています（{limit} まで）
+  en: "{count} paragraphs in a row open with a conjunction (limit {limit})"
+
+how_to_fix:
+  ja: どれか 1 つを残して、他は言いたいことから始めてください。
+  en: Keep one. Start the others with what you want to say.
+
+levels: { strict: 1, normal: 2, relaxed: 4 }
+
+use_for: [business, blog, technical]

package/rules/required-sections.yaml

@@ -0,0 +1,26 @@
+id: required-sections
+layer: L1
+status: experimental
+how_to_find: required-sections
+severity: error
+
+name:
+  ja: 必要な見出しが無い
+  en: A required heading is missing
+
+why:
+  ja: 「提案書にはリスクの節がある」のような取り決めは、組織ごとに違います。chaff は必須の見出しを持たず、chaff.yaml の required_sections に書かれた取り決めを守れているかだけを見ます。書いていなければ何も言いません。
+  en: '"A proposal has a risk section" is a decision each team makes. chaff holds no list of its own; it only checks the one written under `required_sections` in chaff.yaml. With nothing written, this rule says nothing.'
+
+message:
+  ja: 「{word}」の見出しがありません
+  en: 'No heading for "{word}"'
+
+how_to_fix:
+  ja: その見出しを足してください。要らないと思うなら、chaff.yaml の required_sections から外すのが筋です。
+  en: Add the heading. If it is not needed, the honest fix is to remove it from `required_sections`.
+
+# 何個足りなければ指摘するか。1 は「1 つでも足りなければ」。
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [business, blog, technical]

package/rules/rule-of-three.yaml

@@ -0,0 +1,25 @@
+id: rule-of-three
+layer: L1
+status: experimental
+how_to_find: rule-of-three
+severity: info
+
+name:
+  ja: 3 項目の箇条書きばかり
+  en: Everything comes in threes
+
+why:
+  ja: 3 つ並べると収まりがよいので、言いたいことが 2 つでも 4 つでも 3 つにされます。
+  en: Three items feel complete, so two become three and four become three.
+
+message:
+  ja: 箇条書き {total} 個のうち {count} 個が 3 項目です（{limit}% まで）
+  en: "{count} of {total} lists have exactly three items ({limit}% allowed)"
+
+how_to_fix:
+  ja: 数を合わせるために足した項目を消してください。2 つで足りるなら 2 つで。
+  en: Drop the item you added to reach three.
+
+levels: { strict: 50, normal: 70, relaxed: 90 }
+
+use_for: [blog]

package/rules/sasete-itadaku.yaml

@@ -0,0 +1,27 @@
+id: sasete-itadaku
+layer: L3
+status: experimental
+how_to_find: phrase-match
+word_list: sasete-itadaku
+languages: [ja]
+severity: info
+
+name:
+  ja: 「させていただく」が多い
+  en: Overused humble form
+
+why:
+  ja: 1 度なら丁寧ですが、重なると誰の判断で何をするのかが消えます。「検討させていただきます」は、検討するのかしないのかを言っていません。
+  en: Once it is polite. Repeated, it hides whose decision it is and what will actually happen.
+
+message:
+  ja: 「{matched}」が文書内に {count} 回あります（{limit} 回まで）
+  en: '"{matched}" appears {count} times in this document (limit {limit})'
+
+how_to_fix:
+  ja: 主語を立てて言い切ってください。「検討させていただきます」を「来週までに結論を出します」に。
+  en: Name the actor and commit. "We will look into it" becomes "we will decide by Friday".
+
+levels: { strict: 1, normal: 3, relaxed: 6 }
+
+use_for: [business, blog]

package/rules/section-length-uniformity.yaml

@@ -0,0 +1,25 @@
+id: section-length-uniformity
+layer: L1
+status: experimental
+how_to_find: section-uniformity
+severity: info
+
+name:
+  ja: 節の長さが揃いすぎている
+  en: Section lengths are too uniform
+
+why:
+  ja: 見出しごとに機械的に埋めると、節の長さが揃います。書くことの量は節ごとに違うはずです。
+  en: Filling every heading to the same size is what a template does, not what a writer does.
+
+message:
+  ja: 節の長さのばらつきが {variance}% しかありません（{limit}% 以上ほしい）
+  en: Section length varies by only {variance}% (want at least {limit}%)
+
+how_to_fix:
+  ja: 書くことの少ない節は短いままにしてください。
+  en: Let the thin sections stay thin.
+
+levels: { strict: 45, normal: 35, relaxed: 25 }
+
+use_for: [blog]

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

@@ -0,0 +1,27 @@
+id: sentence-initial-conjunction-run
+layer: L3
+status: experimental
+how_to_find: conjunction-run
+word_list: sentence-opener
+languages: [en]
+severity: info
+
+name:
+  ja: 接続詞で始まる文が続いている
+  en: Run of sentences opening with a conjunction
+
+why:
+  ja: 接続詞で始まる文は 1 つなら効きますが、続くとどの文も前の文の付け足しに見えて、何が主張なのかが分からなくなります。
+  en: One sentence opening with "And" or "But" lands. A run of them makes every sentence read as an afterthought.
+
+message:
+  ja: 接続詞で始まる文が {count} 文続いています（{limit} 文まで）
+  en: "{count} sentences in a row open with a conjunction (limit {limit})"
+
+how_to_fix:
+  ja: どれか 1 つを残して、他は前の文に繋ぐか独立させてください。
+  en: Keep one. Join the others to the previous sentence, or let them stand alone.
+
+levels: { strict: 1, normal: 2, relaxed: 4 }
+
+use_for: [blog, business]

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

@@ -0,0 +1,27 @@
+id: taigen-dome-in-prose
+layer: L3
+status: experimental
+how_to_find: noun-ending
+requires: [pos]
+languages: [ja]
+severity: info
+
+name:
+  ja: 体言止めが続いている
+  en: Too many noun-ending sentences
+
+why:
+  ja: 体言止めは 1 つなら効きますが、続くと文が途中で切れたように読めます。箇条書きでは普通の書きかたなので、本文だけを見ています。
+  en: One noun-ending sentence lands. Several in a row read as unfinished. Bullet lists are excluded, where the form is normal.
+
+message:
+  ja: 本文に体言止めが {count} 文あります（{limit} 文まで）
+  en: "{count} sentences end on a noun in the body text (limit {limit})"
+
+how_to_fix:
+  ja: 述語を足してください。「〜が課題。」を「〜が課題です。」に。
+  en: Add the predicate.
+
+levels: { strict: 2, normal: 4, relaxed: 8 }
+
+use_for: [blog, business, technical]

package/rules/title-case-consistency.yaml

@@ -0,0 +1,26 @@
+id: title-case-consistency
+layer: L3
+status: experimental
+how_to_find: title-case-mix
+languages: [en]
+severity: info
+
+name:
+  ja: 見出しの大文字化が揃っていない
+  en: Heading capitalisation is inconsistent
+
+why:
+  ja: Title Case と sentence case のどちらが正しいかは決めません。1 つの文書で混ざっていると、見出しの階層が変わったように見えます。
+  en: Neither Title Case nor sentence case is wrong. Mixed within one document, the headings look like they change level.
+
+message:
+  ja: この見出しだけ他と大文字化の流儀が違います（文書の中で {count} 個）
+  en: "This heading's capitalisation differs from the rest ({count} in this document)"
+
+how_to_fix:
+  ja: 多いほうに揃えてください。
+  en: Match the majority.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+use_for: [blog, business, technical]

package/rules/undefined-acronym.yaml

@@ -0,0 +1,25 @@
+id: undefined-acronym
+layer: L1
+status: experimental
+how_to_find: undefined-acronym
+severity: info
+
+name:
+  ja: 略語が説明なしで出てくる
+  en: Acronym never expanded
+
+why:
+  ja: 略語は読む人によって指すものが違います。社内で通じても、半年後の自分や別の部署には通じません。
+  en: An acronym means different things to different readers. What is obvious inside one team is not obvious outside it.
+
+message:
+  ja: 「{word}」が説明なしで使われています（説明のない略語 {count} 個）
+  en: '"{word}" is used without an expansion ({count} such acronyms)'
+
+how_to_fix:
+  ja: 初出のところで括弧に入れて展開してください。「CI（継続的インテグレーション）」のように。
+  en: Expand it in brackets at first use.
+
+levels: { strict: 1, normal: 3, relaxed: 6 }
+
+use_for: [business, technical]

package/rules/unqualified-superlative.yaml

@@ -0,0 +1,26 @@
+id: unqualified-superlative
+layer: L2
+status: experimental
+how_to_find: unqualified-superlative
+word_list: superlative
+severity: warning
+
+name:
+  ja: 比べる相手のない最上級
+  en: Superlative with nothing to compare
+
+why:
+  ja: 「最も速い」だけでは、何と比べて最もなのかがありません。比較対象も条件も無い最上級は、読み手に確かめようがありません。
+  en: '"The fastest" without saying than what leaves the reader nothing to check.'
+
+message:
+  ja: 「{matched}」に比べる相手がありません（そういう言い方が {count} 箇所）
+  en: '"{matched}" has nothing to compare against ({count} such claims)'
+
+how_to_fix:
+  ja: 比較対象か条件を添えてください。「社内の 3 案のうち最も速い」のように。
+  en: Name the comparison. "The fastest of the three options we tried."
+
+levels: { strict: 1, normal: 2, relaxed: 4 }
+
+use_for: [business, blog]

package/src/backends/anthropic.ts

@@ -0,0 +1,61 @@
+import { existsSync } from "node:fs";
+import { homedir } from "node:os";
+import { join } from "node:path";
+import Anthropic from "@anthropic-ai/sdk";
+import { toFailure } from "./types.ts";
+import type { Failure, Judge, Prompt } from "./types.ts";
+
+export type AnthropicResponse = { readonly content: readonly { readonly type: string; readonly text?: string | undefined }[] };
+
+/** judge が使うのは messages.create だけ。最小の面だけを要求する。テストで差し替えられる。 */
+export type AnthropicClient = { readonly messages: { readonly create: (params: Anthropic.MessageCreateParamsNonStreaming) => Promise<AnthropicResponse> } };
+
+const isTextBlock = (block: unknown): block is { readonly text: string } =>
+  typeof block === "object" && block !== null && "text" in block && typeof block.text === "string";
+
+export const DEFAULT_MODEL = "claude-opus-5";
+
+/**
+ * 認証情報があるか。
+ *
+ * env var を見るだけでは足りない。SDK は ANTHROPIC_API_KEY / ANTHROPIC_AUTH_TOKEN /
+ * `ant auth login` のプロファイル / Workload Identity の順に解決するので、env が
+ * 無くても通ることがある。逆に、無いまま呼ぶと SDK は型の無い素の Error を投げる
+ * （AnthropicError でも APIError でもない）ので、あとから種類で判別できない。
+ * だから先に確かめる。
+ */
+const ENV_KEYS = ["ANTHROPIC_API_KEY", "ANTHROPIC_AUTH_TOKEN", "ANTHROPIC_IDENTITY_TOKEN", "ANTHROPIC_IDENTITY_TOKEN_FILE"];
+
+export const configDir = (): string => process.env["ANTHROPIC_CONFIG_DIR"] ?? join(homedir(), ".config", "anthropic");
+
+export const hasCredentials = (profileDir: string = configDir()): boolean =>
+  ENV_KEYS.some((name) => (process.env[name] ?? "").length > 0) || existsSync(profileDir);
+
+export const isAuthFailure = (error: unknown): boolean =>
+  error instanceof Anthropic.AuthenticationError || (error instanceof Anthropic.APIError && error.status === 401);
+
+/** API が返した失敗だけを拾う。ネットワーク断やコードの誤りは、握りつぶさずそのまま投げる。 */
+export const describeFailure = (error: unknown): Failure | undefined => {
+  if (!(error instanceof Anthropic.APIError)) return undefined;
+  const raw: { status: unknown; message: unknown } = error;
+  return toFailure(raw);
+};
+
+export const judge =
+  (client?: AnthropicClient): Judge =>
+  async (prompt: Prompt): Promise<string> => {
+    const anthropic: AnthropicClient = client ?? new Anthropic();
+    const response = await anthropic.messages.create({
+      model: prompt.model,
+      max_tokens: 1024,
+      system: prompt.system,
+      output_config: { format: { type: "json_schema", schema: prompt.schema } },
+      messages: [{ role: "user", content: prompt.user }],
+    });
+    const body = response.content.map((block) => (isTextBlock(block) ? block.text : undefined)).find((text) => text !== undefined);
+    if (body === undefined) throw new Error("判定が返りませんでした");
+    return body;
+  };
+
+/** 認証が無いときに人へ見せる案内。 */
+export const SETUP_HINT = "ANTHROPIC_API_KEY を設定するか、ant auth login を実行してください。";

package/src/backends/openai.ts

@@ -0,0 +1,46 @@
+import OpenAI from "openai";
+import { toFailure } from "./types.ts";
+import type { Failure, Judge, Prompt } from "./types.ts";
+
+export type OpenAIResponse = { readonly choices: readonly { readonly message: { readonly content: string | null } }[] };
+
+/** judge が使うのは chat.completions.create だけ。最小の面だけを要求する。 */
+export type OpenAIClient = {
+  readonly chat: { readonly completions: { readonly create: (params: OpenAI.ChatCompletionCreateParamsNonStreaming) => Promise<OpenAIResponse> } };
+};
+
+export const DEFAULT_MODEL = "gpt-5";
+
+export const hasCredentials = (): boolean => (process.env["OPENAI_API_KEY"] ?? "").length > 0;
+
+export const isAuthFailure = (error: unknown): boolean => error instanceof OpenAI.APIError && error.status === 401;
+
+/** API が返した失敗だけを拾う。ネットワーク断やコードの誤りは、握りつぶさずそのまま投げる。 */
+export const describeFailure = (error: unknown): Failure | undefined => {
+  if (!(error instanceof OpenAI.APIError)) return undefined;
+  const raw: { status: unknown; message: unknown } = error;
+  return toFailure(raw);
+};
+
+/**
+ * 同じ JSON schema をそのまま使う。包みかたが違うだけで、返させる形は provider で変えない。
+ * 変えると、provider を替えたときに判定の意味まで変わる。
+ */
+export const judge =
+  (client?: OpenAIClient): Judge =>
+  async (prompt: Prompt): Promise<string> => {
+    const openai: OpenAIClient = client ?? new OpenAI();
+    const response = await openai.chat.completions.create({
+      model: prompt.model,
+      messages: [
+        { role: "system", content: prompt.system },
+        { role: "user", content: prompt.user },
+      ],
+      response_format: { type: "json_schema", json_schema: { name: "verdict", schema: prompt.schema, strict: true } },
+    });
+    const body = response.choices[0]?.message.content;
+    if (body === null || body === undefined) throw new Error("判定が返りませんでした");
+    return body;
+  };
+
+export const SETUP_HINT = "OPENAI_API_KEY を設定してください。";

package/src/backends/types.ts

@@ -0,0 +1,38 @@
+/**
+ * 判定役の面。ここまでが provider ごとに違い、ここから先は共通。
+ *
+ * 返すのは JSON の文字列で、Verdict への変換と検証は judge.ts が 1 箇所で行う。
+ * provider が増えても「返ってきた形の確かめかた」は増やさない。
+ */
+export type JsonSchema = Readonly<Record<string, unknown>>;
+
+export type Prompt = { readonly system: string; readonly user: string; readonly schema: JsonSchema; readonly model: string };
+
+export type Judge = (prompt: Prompt) => Promise<string>;
+
+export type BackendName = "anthropic" | "openai";
+
+export 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 };
+
+const statusOf = (value: unknown): number | undefined => (typeof value === "number" ? value : undefined);
+
+const messageOf = (value: unknown): string => (typeof value === "string" && value.length > 0 ? value : "原因は返ってきませんでした");
+
+const kindOf = (status: number | undefined): Failure["kind"] => {
+  if (status === 401 || status === 403) return "auth";
+  return status === 429 ? "quota" : "api";
+};
+
+/**
+ * SDK の APIError から Failure を作る。分類は provider で変えない。
+ * status と message は SDK 上 any なので、ここで 1 度だけ形を確かめる。
+ */
+export const toFailure = (error: { readonly status: unknown; readonly message: unknown }): Failure => {
+  const status = statusOf(error.status);
+  return { kind: kindOf(status), status, message: messageOf(error.message) };
+};

package/src/cli.ts

@@ -5,7 +5,7 @@ import { loadAdapter, packageFor } from "./adapter-load.ts";
 import { CONFIG_FILE, EMPTY, loadConfig, type Config } from "./config/load.ts";
 import { applyByPath } from "./config/by-path.ts";
 import { applyLevel } from "./config/write.ts";
-import { buildDocument } from "./document.ts";
+import { buildDocument, teamRules } from "./document.ts";
 import { guessLanguage } from "./detect.ts";
 import { collectTargets } from "./files.ts";
 import { BASELINE_FILE, fingerprint, readBaseline, splitByBaseline, writeBaseline } from "./baseline.ts";
@@ -22,7 +22,7 @@ import { renderExplain } from "./render/explain.ts";
 import { renderFriendly } from "./render/friendly.ts";
 import { rulesJson } from "./render/rules-json.ts";
 import { renderSummary, type FileOutcome } from "./render/summary.ts";
-import { runRules } from "./run.ts";
+import { neededBy, runRules } from "./run.ts";
 import type { Level, RuleDefinition } from "./plugin.ts";
 
 const USAGE = `chaff — 文章の読みにくいところを見つけます。文章は書き換えません。
@@ -30,6 +30,7 @@ const USAGE = `chaff — 文章の読みにくいところを見つけます。
   chaff <file|dir|glob>...       検査する（設定も API key も要りません）
   chaff .                        この場所の Markdown を全部
   chaff test <file|dir>...       意味を読む検査も動かす（API key が要ります）
+                                 判定役は chaff.yaml の ai_backend で選びます
   chaff init                     chaff.yaml を作る
   chaff eval <dir>               手元の文書で閾値を測り直す
   chaff explain <rule>           そのルールの意図と根拠を読む
@@ -43,6 +44,7 @@ const USAGE = `chaff — 文章の読みにくいところを見つけます。
   --experimental    試験中の rule も動かす
   --show-baseline   棚上げした分も含めて全部見る
   --watch           保存のたびに見直し、変わったところだけ出す
+  --dry-run         test で、何を AI に送るかだけを見る（API を呼びません）
 
 この箇所だけ黙らせる:  <!-- stet: rule-id — 理由 -->
 
@@ -92,9 +94,11 @@ const inspect = async (path: string, config: Config, argv: readonly string[]): P
   const language = applyByPath(config.byPath, config.baseDir, path).language ?? config.language ?? guessLanguage(source).language;
   const adapter = await loadAdapter(language);
   const { genre, from } = resolveGenre(path, source, config);
-  const doc = buildDocument(path, source, adapter);
   const rules = loadRules(language);
-  const raw = runRules(doc, rules, config.rules, config.experimental || argv.includes("--experimental"), genre);
+  const experimental = config.experimental || argv.includes("--experimental");
+  await adapter.prepare?.(neededBy(rules, config.rules, experimental, genre, language));
+  const doc = buildDocument(path, source, adapter, teamRules(config));
+  const raw = runRules(doc, rules, config.rules, experimental, genre);
   // 応答は 3 つ。stet で黙らせたものは、ここで落とす。
   const applied = applySuppressions(
     source,
@@ -177,7 +181,7 @@ const explain = (ruleId: string | undefined): number => {
     return 1;
   }
   const current = config.rules[rule.id] ?? (rule.status === "experimental" && !config.experimental ? "off" : "normal");
-  console.log(renderExplain(rule, current, language, unitOf(rule.id, language)));
+  console.log(renderExplain(rule, current, language, unitOf(rule.id, language), config.genre));
   return 0;
 };
 

package/src/commands/eval.ts

@@ -1,12 +1,13 @@
 import { readFile } from "node:fs/promises";
 import { loadAdapter } from "../adapter-load.ts";
 import { applyByPath } from "../config/by-path.ts";
-import { buildDocument } from "../document.ts";
+import { buildDocument, teamRules } from "../document.ts";
 import { guessLanguage } from "../detect.ts";
 import { collectTargets } from "../files.ts";
 import { loadRules } from "../rule-load.ts";
 import { evaluate } from "../eval.ts";
 import { renderEval } from "../render/eval.ts";
+import { neededBy } from "../run.ts";
 import type { Config } from "../config/load.ts";
 
 export type Context = {
@@ -32,7 +33,9 @@ export const runEval = async (targets: readonly string[], argv: readonly string[
       const source = await readFile(path, "utf8");
       const language = applyByPath(config.byPath, config.baseDir, path).language ?? config.language ?? guessLanguage(source).language;
       const adapter = await loadAdapter(language);
-      return { doc: buildDocument(path, source, adapter), language, genre: resolveGenre(path, source, config).genre };
+      const { genre } = resolveGenre(path, source, config);
+      await adapter.prepare?.(neededBy(loadRules(language), config.rules, config.experimental, genre, language));
+      return { doc: buildDocument(path, source, adapter, teamRules(config)), language, genre };
     }),
   );
   const language = docs[0]?.language ?? "ja";