chaffjs 0.25.0 → 0.27.0

package/dist/structure-shape/baseline-load.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"baseline-load.d.ts","sourceRoot":"","sources":["../../src/structure-shape/baseline-load.ts"],"names":[],"mappings":"AAIA,OAAO,EAA0B,KAAK,iBAAiB,EAAE,MAAM,eAAe,CAAC;AAY/E,oFAAoF;AACpF,eAAO,MAAM,kBAAkB,EAAE,iBAAkC,CAAC"}
+{"version":3,"file":"baseline-load.d.ts","sourceRoot":"","sources":["../../src/structure-shape/baseline-load.ts"],"names":[],"mappings":"AAGA,OAAO,EAA0B,KAAK,iBAAiB,EAAE,MAAM,eAAe,CAAC;AAY/E,oFAAoF;AACpF,eAAO,MAAM,kBAAkB,EAAE,iBAAkC,CAAC"}

package/dist/structure-shape/baseline-load.js

@@ -1,12 +1,11 @@
-import { readFileSync } from "node:fs";
-import { dirname, join } from "node:path";
-import { fileURLToPath } from "node:url";
+import { join } from "node:path";
 import { parse } from "yaml";
+import { PACKAGE_DIR, readText } from "../package-files.js";
 import { parseStructureBaseline } from "./baseline.js";
-const BASELINE_FILE = join(dirname(fileURLToPath(import.meta.url)), "..", "..", "structure-baseline.yaml");
+const BASELINE_FILE = join(PACKAGE_DIR, "structure-baseline.yaml");
 const readBaseline = () => {
     try {
-        return parseStructureBaseline(parse(readFileSync(BASELINE_FILE, "utf8")));
+        return parseStructureBaseline(parse(readText(BASELINE_FILE)));
     }
     catch (error) {
         throw new Error(`cannot read the structure baseline ${BASELINE_FILE}`, { cause: error });

package/dist/structure-shape/baseline-load.js.map

@@ -1 +1 @@
-{"version":3,"file":"baseline-load.js","sourceRoot":"","sources":["../../src/structure-shape/baseline-load.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,MAAM,SAAS,CAAC;AACvC,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAC1C,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,KAAK,EAAE,MAAM,MAAM,CAAC;AAC7B,OAAO,EAAE,sBAAsB,EAA0B,MAAM,eAAe,CAAC;AAE/E,MAAM,aAAa,GAAG,IAAI,CAAC,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,yBAAyB,CAAC,CAAC;AAE3G,MAAM,YAAY,GAAG,GAAsB,EAAE;IAC3C,IAAI,CAAC;QACH,OAAO,sBAAsB,CAAC,KAAK,CAAC,YAAY,CAAC,aAAa,EAAE,MAAM,CAAC,CAAC,CAAC,CAAC;IAC5E,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,IAAI,KAAK,CAAC,sCAAsC,aAAa,EAAE,EAAE,EAAE,KAAK,EAAE,KAAK,EAAE,CAAC,CAAC;IAC3F,CAAC;AACH,CAAC,CAAC;AAEF,oFAAoF;AACpF,MAAM,CAAC,MAAM,kBAAkB,GAAsB,YAAY,EAAE,CAAC"}
+{"version":3,"file":"baseline-load.js","sourceRoot":"","sources":["../../src/structure-shape/baseline-load.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,KAAK,EAAE,MAAM,MAAM,CAAC;AAC7B,OAAO,EAAE,WAAW,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAC;AAC5D,OAAO,EAAE,sBAAsB,EAA0B,MAAM,eAAe,CAAC;AAE/E,MAAM,aAAa,GAAG,IAAI,CAAC,WAAW,EAAE,yBAAyB,CAAC,CAAC;AAEnE,MAAM,YAAY,GAAG,GAAsB,EAAE;IAC3C,IAAI,CAAC;QACH,OAAO,sBAAsB,CAAC,KAAK,CAAC,QAAQ,CAAC,aAAa,CAAC,CAAC,CAAC,CAAC;IAChE,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,IAAI,KAAK,CAAC,sCAAsC,aAAa,EAAE,EAAE,EAAE,KAAK,EAAE,KAAK,EAAE,CAAC,CAAC;IAC3F,CAAC;AACH,CAAC,CAAC;AAEF,oFAAoF;AACpF,MAAM,CAAC,MAAM,kBAAkB,GAAsB,YAAY,EAAE,CAAC"}

package/dist/style-load.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"style-load.d.ts","sourceRoot":"","sources":["../src/style-load.ts"],"names":[],"mappings":"AAIA,OAAO,EAAc,KAAK,eAAe,EAAE,MAAM,kBAAkB,CAAC;AAcpE,yEAAyE;AACzE,eAAO,MAAM,UAAU,GAAI,MAAK,MAAmB,KAAG,SAAS,eAAe,EAQ7E,CAAC"}
+{"version":3,"file":"style-load.d.ts","sourceRoot":"","sources":["../src/style-load.ts"],"names":[],"mappings":"AAGA,OAAO,EAAc,KAAK,eAAe,EAAE,MAAM,kBAAkB,CAAC;AAcpE,yEAAyE;AACzE,eAAO,MAAM,UAAU,GAAI,MAAK,MAAmB,KAAG,SAAS,eAAe,EAQ7E,CAAC"}

package/dist/style-load.js

@@ -1,13 +1,12 @@
-import { readFileSync, readdirSync } from "node:fs";
-import { dirname, join } from "node:path";
-import { fileURLToPath } from "node:url";
+import { join } from "node:path";
 import { parse } from "yaml";
+import { PACKAGE_DIR, readDir, readText } from "./package-files.js";
 import { parseStyle } from "./style-parse.js";
-const STYLES_DIR = join(dirname(fileURLToPath(import.meta.url)), "..", "styles");
+const STYLES_DIR = join(PACKAGE_DIR, "styles");
 const loaded = { value: undefined };
 const readStyle = (dir, file) => {
     try {
-        return parseStyle(parse(readFileSync(join(dir, file), "utf8")), file);
+        return parseStyle(parse(readText(join(dir, file))), file);
     }
     catch (error) {
         throw new Error(`cannot read ${join(dir, file)}: ${error instanceof Error ? error.message : String(error)}`, { cause: error });
@@ -17,7 +16,7 @@ const readStyle = (dir, file) => {
 export const loadStyles = (dir = STYLES_DIR) => {
     if (dir === STYLES_DIR && loaded.value !== undefined)
         return loaded.value;
-    const styles = readdirSync(dir)
+    const styles = readDir(dir)
         .filter((file) => file.endsWith(".yaml"))
         .toSorted((left, right) => left.localeCompare(right, "en"))
         .map((file) => readStyle(dir, file));

package/dist/style-load.js.map

@@ -1 +1 @@
-{"version":3,"file":"style-load.js","sourceRoot":"","sources":["../src/style-load.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,WAAW,EAAE,MAAM,SAAS,CAAC;AACpD,OAAO,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AAC1C,OAAO,EAAE,aAAa,EAAE,MAAM,UAAU,CAAC;AACzC,OAAO,EAAE,KAAK,EAAE,MAAM,MAAM,CAAC;AAC7B,OAAO,EAAE,UAAU,EAAwB,MAAM,kBAAkB,CAAC;AAEpE,MAAM,UAAU,GAAG,IAAI,CAAC,OAAO,CAAC,aAAa,CAAC,MAAM,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,EAAE,QAAQ,CAAC,CAAC;AAEjF,MAAM,MAAM,GAAsD,EAAE,KAAK,EAAE,SAAS,EAAE,CAAC;AAEvF,MAAM,SAAS,GAAG,CAAC,GAAW,EAAE,IAAY,EAAmB,EAAE;IAC/D,IAAI,CAAC;QACH,OAAO,UAAU,CAAC,KAAK,CAAC,YAAY,CAAC,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,EAAE,MAAM,CAAC,CAAC,EAAE,IAAI,CAAC,CAAC;IACxE,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,IAAI,KAAK,CAAC,eAAe,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,KAAK,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,KAAK,EAAE,CAAC,CAAC;IACjI,CAAC;AACH,CAAC,CAAC;AAEF,yEAAyE;AACzE,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,MAAc,UAAU,EAA8B,EAAE;IACjF,IAAI,GAAG,KAAK,UAAU,IAAI,MAAM,CAAC,KAAK,KAAK,SAAS;QAAE,OAAO,MAAM,CAAC,KAAK,CAAC;IAC1E,MAAM,MAAM,GAAG,WAAW,CAAC,GAAG,CAAC;SAC5B,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;SACxC,QAAQ,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,IAAI,CAAC,aAAa,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC;SAC1D,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,SAAS,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC,CAAC;IACvC,IAAI,GAAG,KAAK,UAAU;QAAE,MAAM,CAAC,KAAK,GAAG,MAAM,CAAC;IAC9C,OAAO,MAAM,CAAC;AAChB,CAAC,CAAC"}
+{"version":3,"file":"style-load.js","sourceRoot":"","sources":["../src/style-load.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,KAAK,EAAE,MAAM,MAAM,CAAC;AAC7B,OAAO,EAAE,WAAW,EAAE,OAAO,EAAE,QAAQ,EAAE,MAAM,oBAAoB,CAAC;AACpE,OAAO,EAAE,UAAU,EAAwB,MAAM,kBAAkB,CAAC;AAEpE,MAAM,UAAU,GAAG,IAAI,CAAC,WAAW,EAAE,QAAQ,CAAC,CAAC;AAE/C,MAAM,MAAM,GAAsD,EAAE,KAAK,EAAE,SAAS,EAAE,CAAC;AAEvF,MAAM,SAAS,GAAG,CAAC,GAAW,EAAE,IAAY,EAAmB,EAAE;IAC/D,IAAI,CAAC;QACH,OAAO,UAAU,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC,CAAC,EAAE,IAAI,CAAC,CAAC;IAC5D,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,IAAI,KAAK,CAAC,eAAe,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,KAAK,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,EAAE,EAAE,EAAE,KAAK,EAAE,KAAK,EAAE,CAAC,CAAC;IACjI,CAAC;AACH,CAAC,CAAC;AAEF,yEAAyE;AACzE,MAAM,CAAC,MAAM,UAAU,GAAG,CAAC,MAAc,UAAU,EAA8B,EAAE;IACjF,IAAI,GAAG,KAAK,UAAU,IAAI,MAAM,CAAC,KAAK,KAAK,SAAS;QAAE,OAAO,MAAM,CAAC,KAAK,CAAC;IAC1E,MAAM,MAAM,GAAG,OAAO,CAAC,GAAG,CAAC;SACxB,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,QAAQ,CAAC,OAAO,CAAC,CAAC;SACxC,QAAQ,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,IAAI,CAAC,aAAa,CAAC,KAAK,EAAE,IAAI,CAAC,CAAC;SAC1D,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,SAAS,CAAC,GAAG,EAAE,IAAI,CAAC,CAAC,CAAC;IACvC,IAAI,GAAG,KAAK,UAAU;QAAE,MAAM,CAAC,KAAK,GAAG,MAAM,CAAC;IAC9C,OAAO,MAAM,CAAC;AAChB,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chaffjs",
-  "version": "0.25.0",
+  "version": "0.27.0",
   "description": "Prose validation harness. Finds what is hard to read, and never rewrites it for you.",
   "keywords": [
     "chaff",
@@ -41,8 +41,29 @@
     "./grade": {
       "types": "./src/grade-api.ts",
       "import": "./dist/grade-api.js"
+    },
+    "./browser": {
+      "types": "./src/browser.ts",
+      "import": "./dist/browser.js"
+    },
+    "./browser-files": {
+      "types": "./src/browser-files.ts",
+      "import": "./dist/browser-files.js"
     }
   },
+  "browser": {
+    "./src/package-files.ts": "./src/browser/package-files.ts",
+    "./src/adapter-import.ts": "./src/browser/adapter-import.ts",
+    "./src/detectors/index.ts": "./src/browser/detectors.ts",
+    "./src/custom/bounded-match.ts": "./src/browser/bounded-match.ts",
+    "./src/config/working-dir.ts": "./src/browser/working-dir.ts",
+    "./dist/package-files.js": "./dist/browser/package-files.js",
+    "./dist/adapter-import.js": "./dist/browser/adapter-import.js",
+    "./dist/detectors/index.js": "./dist/browser/detectors.js",
+    "./dist/custom/bounded-match.js": "./dist/browser/bounded-match.js",
+    "./dist/config/working-dir.js": "./dist/browser/working-dir.js",
+    "node:path": "./dist/browser/path.js"
+  },
   "files": [
     "LICENSE",
     "README.md",
@@ -66,8 +87,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.125.0",
-    "@chaffjs/lang-en": "0.22.0",
-    "@chaffjs/lang-ja": "0.24.0",
+    "@chaffjs/lang-en": "0.24.0",
+    "@chaffjs/lang-ja": "0.26.0",
     "mdast-util-from-markdown": "^2.0.3",
     "mdast-util-frontmatter": "^2.0.1",
     "mdast-util-gfm-table": "^2.0.0",

package/rules/agreement-slip.yaml

@@ -5,7 +5,7 @@ how_to_find: agreement-slip
 requires: [pos]
 languages: [en]
 extra_word_lists: [singular-determiner, plural-determiner, invariant-noun, count-adjective, dependent-possessive, finite-auxiliary, misnumbered-phrase]
-severity: warning
+severity: info
 
 name:
   ja: 語の形が合っていない
@@ -31,7 +31,7 @@ how_to_fix:
   ja: 限定詞か名詞のどちらかに揃えてください（a significant change / significant changes）。所有の語なら、主語の語に直してください（Your can → You can、their is → there is）。
   en: Make the determiner and the noun agree ("a significant change" or "significant changes"). For a possessive, write the subject you meant ("Your can" becomes "You can", "their is" becomes "there is").
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
 off_for:

package/rules/change-rate-mismatch.yaml

@@ -0,0 +1,44 @@
+id: change-rate-mismatch
+layer: L3
+status: stable
+how_to_find: change-rate
+requires: [structure]
+severity: warning
+
+name:
+  ja: 増減率が二つの値と合わない
+  en: A rate of change the two values do not give
+
+why:
+  ja: 「前年同月の1,000社から20%増えて1,200社」のように、もとの値・今の値・増減率を一つの文に書くと、読み手は率を確かめずに信じます。数字を一つだけ更新したとき、率だけを去年の文書から写したときに食い違います。一つの文に、もとの値（「から」「に比べて」の付いた値）、同じ単位の今の値、向きの語（増加、減少）の付いた百分率が一つずつあるとき、二つの値から率を計算して比べます。値は書いた桁までの丸めを認めます（12億円は11.5億円から12.5億円のどれか）。
+  en: When one sentence gives the earlier value, the current one and the rate of change ("1,200 companies, up 20% from 1,000"), readers trust the rate without checking it. It goes wrong when one figure is updated and the others are not, or when the rate is copied from last year's text. When a sentence has one earlier value (marked by "from" or "compared with"), one current value in the same unit, and one percentage with a word of direction (up, decline), chaff computes the rate from the two values and compares. Each value may be rounded to its last written digit ($12 million is anything from $11.5 million to $12.5 million).
+
+message:
+  ja: 「{rate}%」と書いていますが、二つの値からは {computed}% です
+  en: '"{rate}%" is written, but the two values give {computed}%'
+
+how_to_fix:
+  ja: 二つの値と率のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of the two values and the rate is right, and correct the others.
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+
+group: facts
+summary:
+  ja: 「1,000社から20%増えて1,200社」のように、一つの文の二つの値と増減率が合わない所
+  en: A rate of change that the two values in the same sentence do not give
+example:
+  ja:
+    before: 利用企業は1,300社となり、前年の1,000社から20%増えました。
+    after: 利用企業は1,300社となり、前年の1,000社から30%増えました。
+  en:
+    before: 1,300 companies used the app, up 20% from 1,000 companies a year earlier.
+    after: 1,300 companies used the app, up 30% from 1,000 companies a year earlier.
+
+not_flagged:
+  ja: 率が二つある文、もとの値が「から」「に比べて」で名指されていない文、同じ単位の今の値が一つでない文、向きの語が率のそばに無い文は比べません。「前年比20%増」のように値が一つしか無いもの、ポイントの差、倍は見ません。丸めで届く範囲の率は言いません。
+  en: 'A sentence with two rates, with no value marked as the earlier one, with no single current value in the same unit, or with no word of direction beside the rate is not compared. A change given with one value ("up 20% year on year"), percentage points and "times" are not read. A rate the rounding of the values can reach is not reported.'

package/rules/cliche.yaml

@@ -4,7 +4,7 @@ status: stable
 how_to_find: phrase-match
 word_list: cliche
 requires: [pos]
-languages: [en]
+languages: [ja, en]
 severity: info
 
 name:
@@ -12,15 +12,15 @@ name:
   en: Cliché
 
 why:
-  ja: 英語の「at the end of the day」「low-hanging fruit」「move the needle」のような決まり文句は、使われすぎて中身が抜けた比喩です。読み手は見慣れた形を読み飛ばし、この文書で何が言いたいのかが残りません。言い回しの一覧は言語ごとの語彙表にあり、それぞれに何を書けばよいかが付いています。
-  en: '"At the end of the day", "low-hanging fruit" and "move the needle" are figures of speech worn down to filler. The reader skims the familiar shape and learns nothing about this document. The phrases are listed in the lexicon, each with what to write instead.'
+  ja: 「今さら聞けない」「徹底解説」「〜の極意」や、英語の「at the end of the day」「low-hanging fruit」のような決まり文句は、使われすぎて中身が抜けた言い回しです。読み手は見慣れた形を読み飛ばし、この文書で何が言いたいのかが残りません。言い回しの一覧は言語ごとの語彙表にあり、それぞれに何を書けばよいかが付いています。
+  en: '"At the end of the day", "low-hanging fruit" and "move the needle" (今さら聞けない, 徹底解説) are figures of speech worn down to filler. The reader skims the familiar shape and learns nothing about this document. The phrases are listed in the lexicon, each with what to write instead.'
 
 message:
   ja: 「{matched}」は使い古された決まり文句です
   en: '"{matched}" is a cliché'
 
 how_to_fix:
-  ja: 決まり文句が指していた中身を、そのまま書いてください（low-hanging fruit → 簡単に済む作業の名前）。
+  ja: 決まり文句が指していた中身を、そのまま書いてください（徹底解説 → 何を説明するのか、low-hanging fruit → 簡単に済む作業の名前）。
   en: Say what the phrase stood for ("low-hanging fruit" → name the easy tasks).
 
 levels: { strict: 1, normal: 1, relaxed: 2 }
@@ -32,9 +32,14 @@ off_for:
 
 group: wording
 summary:
-  ja: 英語で、「at the end of the day」「low-hanging fruit」のような使い古された決まり文句
-  en: A worn phrase such as "at the end of the day" or "low-hanging fruit"
+  ja: 「今さら聞けない」「徹底解説」や「at the end of the day」のような、使い古された決まり文句
+  en: A worn phrase such as "at the end of the day" or "low-hanging fruit" (今さら聞けない, 徹底解説)
 example:
+  ja:
+    before: |
+      この記事では、今さら聞けない Git の基本を徹底解説します。
+    after: |
+      この記事では、Git を初めて使う人向けに、コミットとブランチの使い方を説明します。
   en:
     before: |
       At the end of the day, the new cache is faster.
@@ -42,14 +47,29 @@ example:
       The new cache cuts load time from 2 seconds to 0.5.
 
 not_flagged:
-  ja: 一覧にある言い回しだけを見ます。ほかの規則が見る言い回し（ai-tell の「game-changer」、empty-intensifier の「needless to say」）は入れていません。英語の文書だけで動き、文学と講演の書き起こしは対象にしません。
-  en: Only the phrases on chaff's list are checked. Phrases another rule reads ("game-changer" in ai-tell, "needless to say" in empty-intensifier) are not on it. English documents only; literature and speech transcripts are not checked.
+  ja: 一覧にある言い回しだけを見ます。見出しの中は見ず、本文の文だけを見ます。ほかの規則が見る言い回し（closing-cliche の「いかがでしたか」、ai-tell の「深く掘り下げる」「game-changer」、empty-intensifier の「needless to say」）は入れていません。「結論から言うと」は人の記事にも同じくらいあるので、「〜まとめ」「〜な件」は普通の文（まとめました、重要な件）と分けられないので見ません。文学と講演の書き起こしは対象にしません。
+  en: Only the phrases on chaff's list are checked, in body sentences; headings are not read. Phrases another rule reads (いかがでしたか in closing-cliche, "game-changer" in ai-tell, "needless to say" in empty-intensifier) are not on it. In Japanese, 結論から言うと is left out because human articles use it as often, and 〜まとめ and 〜な件 because ordinary sentences share them (まとめました, 重要な件). Literature and speech transcripts are not checked.
 level_meaning:
   ja: 当てはまる言い回しが {limit} 箇所あれば指摘
   en: reported once there are {limit}
 sources: [write-good, proselint]
 rewrite:
   depth: light
+  ja:
+    direction: 決まり文句を、この文書でそれが指している中身に置き換えてください。語彙表の言い回しごとの書き方に従います。本文が中身を言っていなければ、作らずに書き手に聞いてください。
+    pairs:
+      - before: この記事では、Docker の設定を徹底解説します。
+        after: この記事では、Docker のネットワーク設定の手順を説明します。
+      - before: 今さら聞けない SQL の書き方を紹介します。
+        after: SQL を初めて書く人向けに、SELECT 文の書き方を紹介します。
+      - before: 速く書くための極意は、毎日書くことです。
+        after: 速く書くには、毎日書いてください。
+    keep:
+      - 文が言っている主張
+      - 文の中の数・名前・日付
+    avoid:
+      - 決まり文句を別の決まり文句に替える
+      - 本文に無い数や日付を作る
   en:
     direction: Replace the cliché with what it stood for in this document, following the lexicon's note for the phrase. If the text does not say what that is, ask the writer rather than invent it.
     pairs:

package/rules/date-weekday-mismatch.yaml

@@ -10,8 +10,8 @@ name:
   en: Date and weekday disagree
 
 why:
-  ja: 「2026年10月1日（金）」のように、日付と曜日が食い違っていると、読み手はどちらが正しいのか確かめに行くことになります。日程を書き写すときや、年をまたいで予定を使い回すときに起きます。年まで書いた日付の曜日だけを、暦と比べます。
-  en: When a date and its weekday disagree ("Friday, 1 October 2026"), the reader has to find out which one is right. It happens when a schedule is copied, or reused for another year. Only dates written with their year are checked against the calendar.
+  ja: 「2026年10月1日（金）」のように、日付と曜日が食い違っていると、読み手はどちらが正しいのか確かめに行くことになります。日程を書き写すときや、年をまたいで予定を使い回すときに起きます。年を書いていない日付（メールの「10月9日（金）」）は、年を書いたすぐ前の日付（前に無ければ文書で最初のもの）から5か月以内に収まる年の日付として、暦と比べます。
+  en: When a date and its weekday disagree ("Friday, 1 October 2026"), the reader has to find out which one is right. It happens when a schedule is copied, or reused for another year. A date written without its year ("Friday, October 9" in an email) is checked as the date in the year that puts it within five months of the dated date just before it (or, with none before, the first one in the document).
 
 message:
   ja: 「{date}」は{actual}です（{written}と書いてあります）
@@ -40,5 +40,5 @@ example:
     after: The next meeting is on Thursday, 1 October 2026.
 
 not_flagged:
-  ja: 年を書いていない日付は、どの年か決まらないので暦と照らしません。
-  en: Dates without a year are not checked, since the year is unknown.
+  ja: 年を書いていない日付は、文書に年を書いた日付が無いときと、年を書いた日付から5か月より離れていてどちらの年とも読めるときは、暦と照らしません。
+  en: A date without its year is not checked when the document gives no date with a year, or when it is more than five months from the dated date and could be in either year.

package/rules/date-without-year.yaml

@@ -3,9 +3,8 @@ layer: L1
 status: stable
 how_to_find: date-without-year
 requires: [dates]
-# The dates come from the language package's date reader. English does not read a date written without its year yet,
-# so the rule checks Japanese only until it does.
-languages: [ja]
+# The dates come from the language package's date reader.
+languages: [ja, en]
 severity: info
 
 name:
@@ -50,6 +49,19 @@ example:
       - 2026年10月14日（水）：説明会
       - 2026年10月21日（水）：申込の締め切り
       - 2026年10月28日（水）：結果の連絡
+  en:
+    before: |
+      # Schedule
+
+      - October 14, 2026: briefing
+      - October 21, 2026: applications close
+      - October 28: results sent
+    after: |
+      # Schedule
+
+      - October 14, 2026: briefing
+      - October 21, 2026: applications close
+      - October 28, 2026: results sent
 
 not_flagged:
   ja: 年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）は、書き方の選び方として指しません。ただしその場合も、年をまたぐ日付は指します。月だけ・年だけの日付は見ません。
@@ -69,3 +81,16 @@ rewrite:
     avoid:
       - 曜日と合わない年を書く
       - 本文から決まらない年を推して書く
+  en:
+    direction: Add the year to the date that lacks one. Take it from the document's other dates and from the weekday, if one is written. Where the text does not settle it, leave "[year]" for the writer rather than inventing one.
+    pairs:
+      - before: "October 28: results sent"
+        after: "October 28, 2026: results sent"
+      - before: The next meeting is on January 15.
+        after: The next meeting is on January 15, 2027.
+    keep:
+      - the month, the day and the weekday
+      - how the other dates are written
+    avoid:
+      - a year that does not match the weekday
+      - guessing a year the text does not give

package/rules/defined-term-form.yaml

@@ -10,8 +10,8 @@ name:
   en: A defined term used in another form
 
 why:
-  ja: 契約では、定義した語は定義した形のまま使うのが決まりです。「本サービス」と定義したあとで「「本サービス」」とかぎ括弧を付け直すと、新しく定義し直したのか、同じものなのかが読み手に分かりません。英語では "Services" と定義した語を "services" と小文字で書くと、定義した意味なのか、ふつうの意味なのかが分かれ、争いのもとになります。定義の後ろで、かぎ括弧や引用符に入れ直した語と、大文字で定義した語を小文字で書いた所（大文字の使用より少ないとき）を指します。
-  en: 'A contract uses each defined term exactly as defined. Quoting a term again after its definition ("the "Services"") leaves the reader asking whether it is being defined anew. Writing "services" where "Services" is defined splits the defined sense from the ordinary one, which is where disputes start. chaff points at a term set in quotes again after its definition, and at a capitalised term written in lower case (when the capitalised uses are more).'
+  ja: 契約では、定義した語は定義した形のまま使うのが決まりです。「本サービス」と定義したあとで「「本サービス」」とかぎ括弧を付け直すと、新しく定義し直したのか、同じものなのかが読み手に分かりません。英語では "Services" と定義した語を "services" と小文字で書くと、定義した意味なのか、ふつうの意味なのかが分かれ、争いのもとになります。「本業務」と定義して「本件業務」と書くと、別の業務を指すのかと読めます。定義の後ろで、かぎ括弧や引用符に入れ直した語、大文字で定義した語を小文字で書いた所（大文字の使用より少ないとき）、頭の「本」と「本件」を入れ替えた語（その形も定義した語なら除きます）を指します。
+  en: 'A contract uses each defined term exactly as defined. Quoting a term again after its definition ("the "Services"") leaves the reader asking whether it is being defined anew. Writing "services" where "Services" is defined splits the defined sense from the ordinary one, which is where disputes start. In Japanese, 本件業務 written where 本業務 is defined reads as another task. chaff points at a term set in quotes again after its definition, at a capitalised term written in lower case (when the capitalised uses are more), and at a Japanese term written with its other prefix (本 for 本件 or the other way round), unless that form is defined too.'
 
 message:
   ja: 定義した「{term}」と違う形で使っています
@@ -24,6 +24,9 @@ messages:
   case:
     ja: 「{term}」は {line} 行目で大文字で定義した語ですが、ここは小文字です
     en: '"{term}" is defined with a capital on line {line}, but written in lower case here'
+  prefix:
+    ja: 「{term}」は {line} 行目で定義した語ですが、ここは「{written}」と書いています
+    en: '"{term}" is defined on line {line}, but written "{written}" here'
 
 how_to_fix:
   ja: 定義した語はかぎ括弧を付けずに使い、英語では定義のとおり大文字で始めてください。ふつうの意味で使うなら、別の言葉に替えます。
@@ -41,8 +44,8 @@ off_for:
 
 group: consistency
 summary:
-  ja: 契約や規約で、定義した語を定義のあとでかぎ括弧に入れ直したり、大文字で定義した語を小文字で書いたりしている所
-  en: A defined term quoted again after its definition, or a capitalised defined term written in lower case
+  ja: 契約や規約で、定義した語を定義のあとでかぎ括弧に入れ直したり、大文字で定義した語を小文字で書いたり、「本業務」を「本件業務」と書いたりしている所
+  en: A defined term quoted again after its definition, a capitalised defined term written in lower case, or a Japanese term with its other prefix (本件業務 for 本業務)
 example:
   ja:
     config: { genre: legal/contract }
@@ -78,8 +81,8 @@ example:
       3. You must not resell the Services.
 
 not_flagged:
-  ja: 定義そのもの（以下「本サービス」という、「本サービス」とは）、定義より前の使用（use-before-definition が見ます）、文の頭の大文字、小文字の使用が {limit} 個を超えるか大文字の使用より多い語（ふつうの意味で使っているとみなす）は指しません。定義の文の中の使用（「顧客」とは、表紙に「顧客」と書いた者をいう）も見ません。法令・規程のジャンルは、定義を指すために語をかぎ括弧に入れるので見ません。
-  en: 'The definitions themselves ("Services" means, (the "Services")), uses before the definition (use-before-definition reads those), capitals at the start of a sentence, and terms written in lower case more than {limit} times or more often than capitalised (taken as the ordinary word used on purpose) are not reported, nor is a use inside the defining sentence ("Customer" means the party named "Customer"). Statutes and regulations quote a term to point at its definition, so that genre does not run this rule.'
+  ja: 定義そのもの（以下「本サービス」という、「本サービス」とは）、定義より前の使用（use-before-definition が見ます）、文の頭の大文字、小文字の使用が {limit} 個を超えるか大文字の使用より多い語（ふつうの意味で使っているとみなす）は指しません。定義の文の中の使用（「顧客」とは、表紙に「顧客」と書いた者をいう）も見ません。法令・規程のジャンルは、定義を指すために語をかぎ括弧に入れるので見ません。「本」と「本件」を入れ替えた形は、その形も定義した語であるとき、長い語の一部（見本物品）のときは見ません。
+  en: 'The definitions themselves ("Services" means, (the "Services")), uses before the definition (use-before-definition reads those), capitals at the start of a sentence, and terms written in lower case more than {limit} times or more often than capitalised (taken as the ordinary word used on purpose) are not reported, nor is a use inside the defining sentence ("Customer" means the party named "Customer"). Statutes and regulations quote a term to point at its definition, so that genre does not run this rule. A term with its other prefix (本件業務 for 本業務) is not reported when that form is defined too, or inside a longer word (見本物品).'
 level_meaning:
   ja: 小文字の使用が {limit} 個以下で、大文字の使用より少ないとき指摘
   en: lower-case uses reported when they are {limit} or fewer and fewer than the capitalised ones

package/rules/demonstrative-opener-run.yaml

@@ -4,7 +4,7 @@ status: stable
 how_to_find: opener-run
 word_list: demonstrative-opener
 requires: [pos]
-languages: [ja]
+languages: [ja, en]
 severity: info
 
 name:
@@ -13,15 +13,15 @@ name:
 
 why:
   ja: 「これは」「その結果」「この方法は」のように指示語で始まる文が続くと、読み手は一文ごとに「どれのことか」を前に戻って確かめることになります。指すものが一つ前の文なのか、もっと前なのかも曖昧になります。数えるのは同じ段落の中の連続だけです。
-  en: In Japanese, sentence after sentence opening with a demonstrative (これは, その結果) sends the reader back each time to find what it points at, and blurs whether it means the last sentence or one before. Only runs within one paragraph are counted.
+  en: Sentence after sentence opening with a word that points back (This, That, It; これは, その結果) sends the reader back each time to find what it points at, and blurs whether it means the last sentence or one before. Only runs within one paragraph are counted.
 
 message:
   ja: 「{word}」など、指示語で始まる文が {count} 文続いています（{limit} 文まで）
-  en: '{count} sentences in a row open with a demonstrative such as "{word}" (limit {limit})'
+  en: '{count} sentences in a row open with a word that points back, such as "{word}" (limit {limit})'
 
 how_to_fix:
   ja: 指示語のどれかを、指している名詞に置き換えてください（その結果 → 調査の結果）。
-  en: Replace one of the demonstratives with the noun it points at (その結果 → 調査の結果).
+  en: Replace one of the demonstratives with the noun it points at (This → The new procedure; その結果 → 調査の結果).
 
 levels: { strict: 1, normal: 2, relaxed: 3 }
 
@@ -30,17 +30,22 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: readability
 summary:
   ja: 「これは」「その」「この」のような指示語で始まる文が、同じ段落の中で続く所
-  en: Japanese sentences in a row, within one paragraph, that open with a demonstrative (これ, その)
+  en: Sentences in a row, within one paragraph, that open with a word pointing back (This, That, It; これ, その)
 example:
   ja:
     before: |
       新しい手順を導入しました。これは作業を減らすためです。その結果、残業が減りました。この効果は来月も続く見込みです。
     after: |
       新しい手順を導入しました。作業を減らすためです。その結果、残業が減りました。残業の減少は来月も続く見込みです。
+  en:
+    before: |
+      We introduced a new procedure. This was meant to cut the work. It reduced overtime. That effect should continue next month.
+    after: |
+      We introduced a new procedure. This was meant to cut the work. The procedure reduced overtime, and the reduction should continue next month.
 
 not_flagged:
-  ja: 段落が変われば数え直します。「それぞれ」のように一語になったものと、接続詞の「そして」は数えません。
-  en: The count restarts at each paragraph. Words such as それぞれ and the conjunction そして are not counted.
+  ja: 段落が変われば数え直します。「それぞれ」のように一語になったものと、接続詞の「そして」は数えません。英語では、「This Agreement」「This section」のように文書そのものを指す書き出しと、「It is worth」「It seems」のように後ろを指す It は数えません。
+  en: The count restarts at each paragraph. Words such as それぞれ and the conjunction そして are not counted. In English, an opening that names the document itself ("This Agreement", "This section") and an "it" that stands for what follows ("It is worth", "It seems") are not counted.
 level_meaning:
   ja: 指示語で始まる文 {limit} 文の連続まで
   en: up to {limit} such sentences in a row
@@ -58,3 +63,15 @@ rewrite:
     avoid:
       - 指しているものを取り違える
       - 指示語を別の指示語（同様に、前述の）に替えるだけ
+  en:
+    direction: Of the demonstratives in the run, replace the ones whose referent is furthest away with the noun they point at. One that points at the sentence just before may stay.
+    pairs:
+      - before: We introduced a new procedure. This was meant to cut the work. It reduced overtime. That effect should continue next month.
+        after: We introduced a new procedure. This was meant to cut the work. The procedure reduced overtime, and the reduction should continue next month.
+      - before: The audit found three gaps. These came from an old manual. It is two years old. This will be fixed next month.
+        after: The audit found three gaps. They came from a manual that is two years old. We will revise the manual next month.
+    keep:
+      - what each word points at, and the order of the sentences
+    avoid:
+      - mistaking what a word points at
+      - swapping one pointer for another (the above, the former, said)

package/rules/max-sentence-length.yaml

@@ -79,6 +79,7 @@ use_for: [blog, business, technical, legal, docs, academic, literature, speech]
 off_for:
   literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
   speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
+  academic: measured by yarn rules:measure
   legal: measured by yarn rules:measure
 sources: [shibasaki-tamaoka-2010, yasashii-nihongo-2020, koyobun-2022, gov-uk-clear-language]
 

package/rules/no-mixed-desumasu.yaml

@@ -51,8 +51,8 @@ example:
       新しい料金は来月から始まります。請求書の形式も変わります。支払いの期限は月末です。古い料金は三月で終わります。
 
 not_flagged:
-  ja: どちらの調子が正しいかは決めません。多いほうに揃っていない、少ないほうの文だけを指します。本文と箇条書きは別々に数えます。箇条書きの中の少ないほうが文書全体では多いほうなら、その文は指しません。
-  en: Neither register is called right; only the sentences in the minority are pointed at. The body and each list are counted apart, and a sentence in a list's minority is left alone when its register is the document's majority.
+  ja: どちらの調子が正しいかは決めません。多いほうに揃っていない、少ないほうの文だけを指します。本文と箇条書きは別々に数えます。箇条書きの中の少ないほうが文書全体では多いほうなら、その文は指しません。項目や段落の頭の太字の札（「- **速く書ける。** 説明です。」の「速く書ける。」）は見出しと同じく文に数えません。
+  en: Neither register is called right; only the sentences in the minority are pointed at. The body and each list are counted apart, and a sentence in a list's minority is left alone when its register is the document's majority. A bold label that opens an item or a paragraph and is followed by more text on its line is a heading, not a sentence.
 level_meaning:
   ja: 少ないほうの調子の文が {limit} 文以下のとき、それを指摘
   en: reported when the minority register has {limit} sentences or fewer

package/rules/numbering-gap.yaml

@@ -10,8 +10,8 @@ name:
   en: Skipped or repeated number
 
 why:
-  ja: 第3条の次が第5条、(a) の次が (c)、同じ第2項が二つ。番号が飛ぶか重なると、読み手は何かが消えたのか、参照がどちらを指すのかを判断できません。同じ親の中で並ぶ番号だけを比べます。枝番号（第3条の2）は並びの外として扱います。
-  en: Article 5 right after Article 3, (c) right after (a), two paragraphs numbered 2. A reader cannot tell whether something was removed, or which one a reference means. Only numbers side by side under the same parent are compared.
+  ja: 第3条の次が第5条、(a) の次が (c)、同じ第2項が二つ。番号が飛ぶか重なると、読み手は何かが消えたのか、参照がどちらを指すのかを判断できません。同じ親の中で並ぶ番号だけを比べます。枝番号（第3条の2）は並びの外として扱います。Markdown の番号付きの箇条書き（手順の「1.」「2.」「4.」）も、書いた番号を比べます。表示は最初の番号から数え直しますが、原文と「手順4を参照」は書いた番号を見ます。
+  en: Article 5 right after Article 3, (c) right after (a), two paragraphs numbered 2. A reader cannot tell whether something was removed, or which one a reference means. Only numbers side by side under the same parent are compared. The numbers written on a Markdown ordered list (steps "1.", "2.", "4.") are compared too. The page renders them counted from the first, but the source and a "see step 4" use the numbers as written.
 
 message:
   ja: 「{previous}」の次が「{label}」です（{expected} 番目のはず）
@@ -74,5 +74,5 @@ example:
       Working hours are from nine to six.
 
 not_flagged:
-  ja: 同じ親の下で隣り合う番号だけを比べます。別の章の番号どうしは比べません。
-  en: Only numbers side by side under the same parent are compared.
+  ja: 同じ親の下で隣り合う番号だけを比べます。別の章の番号どうしは比べません。どの項目にも同じ番号（「1.」）を書いた箇条書きと、引用の中の箇条書きは見ません。
+  en: Only numbers side by side under the same parent are compared. A list that writes the same number on every item ("1." on each) and a list inside a quotation are not checked.

package/rules/one-sentence-paragraph-run.yaml

@@ -26,6 +26,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 off_for:
   legal: "A clause, a definition or a claim is a paragraph of one sentence by form."
   literature: "Dialogue and verse set each line apart."
+  academic: measured by yarn rules:measure
 
 group: readability
 summary:

package/rules/orthographic-variant.yaml

@@ -14,7 +14,7 @@ name:
 
 why:
   ja: 「出来る」と「できる」、「引っ越し」と「引越し」、「ウィンドウ」と「ウインドウ」、「e-mail」と「email」のように、同じ語を一つの文書の中で二通りに書くと、検索で別の語になり、読み手は別のものを指しているのかと迷います。どちらが正しいかは決めません。chaff は語の一覧を持たず、文書の中の語を読み（日本語）やならした綴り（カタカナ語と英字）で束ね、文書の中で少ないほうを指摘します。補助動詞と形式名詞（見て下さい、その事）は、本来の使い方（資料を下さい）と別に比べるので、「補助動詞はかなで書く」と決めた文書はそろっていると見ます。漢字の違う同音の語（書く・描く、機会・機械）は別の語と見ます。少ないほうが三分の一を超える文書は、使い分けていると見て言いません。
-  en: Writing one word two ways in one document (e-mail and email, GitHub and Github) makes search treat them as different words and leaves the reader wondering whether two things are meant. chaff does not decide which way is right and keeps no list of words; it groups the document's own words, by reading in Japanese and by spelling without hyphens and case in English, and points at whichever way the document uses less. The case of the first letter is left out, since a sentence or a title gives it (Email, email), and so are words in capitals only. It says nothing when the minority is more than a third, since the document then uses both on purpose.
+  en: Writing one word two ways in one document (e-mail and email, GitHub and Github) makes search treat them as different words and leaves the reader wondering whether two things are meant. chaff does not decide which way is right and keeps no list of words; it groups the document's own words, by reading in Japanese and by spelling without hyphens and case in English, and points at whichever way the document uses less. The case of the first letter is left out, since a sentence or a title gives it (Email, email), and so are words in capitals only, a name in capitals with an ending (SENDs) and the letters of an acronym picked out (CLImatology next to CLIPER). It says nothing when the minority is more than a third, since the document then uses both on purpose.
 
 message:
   ja: 「{written}」と書いています（この文書はふつう「{other}」と書く語です。{of} 箇所のうち {count} 箇所が違う）
@@ -56,8 +56,8 @@ example:
       Send the form by email. We answer every email within a day. Attach the receipt to the email.
 
 not_flagged:
-  ja: 読みが同じでも漢字の違う語（書く・描く）、補助動詞・形式名詞と本来の使い方の書き分け（見て下さい・資料を下さい）、書き分けが意味の違いになる語（成る・なる、言う・いう）、語末の「ー」だけの違い（katakana-long-vowel が見ます）、鉤括弧や引用符の中、chaff.yaml の names に書いた名前は見ません。英字は、頭の字の大文字小文字（Email と email）と、大文字だけの語（強調や略語）を書き方の違いにしません。少ないほうが三分の一を超えるときも言いません。文学のジャンルでは既定で止めています（その時代の書き方のため）。
-  en: The case of a word's first letter (Email, email; Long-Term, long-term) is not a spelling, nor is a word in capitals only (emphasis or an acronym). Hyphenated words that are another word (re-sign, resign), part of an address (github.com), anything in quotation marks and the team's names are not compared. Nothing is reported when the minority is more than a third. The literature preset turns it off, since old spelling belongs to its time.
+  ja: 読みが同じでも漢字の違う語（書く・描く）、補助動詞・形式名詞と本来の使い方の書き分け（見て下さい・資料を下さい）、書き分けが意味の違いになる語（成る・なる、言う・いう）、語末の「ー」だけの違い（katakana-long-vowel が見ます）、鉤括弧や引用符の中、語の直後のふりがなの括弧の中（HTTP（えいちてぃーてぃーぴー））、chaff.yaml の names に書いた名前は見ません。名詞に続けて書いたかなの名詞（全員ぶん）と慣用句の動詞（気をつける）は、同じ読みの語（文、名札を付ける）と別に比べます。英字は、頭の字の大文字小文字（Email と email）と、大文字だけの語（強調や略語）、大文字の名前に語尾が付いた語（関数名の SENDs）、同じ文の略語の字を示した語（CLIPER と並ぶ CLImatology）を書き方の違いにしません（HBase のような名前の大文字は比べます）。少ないほうが三分の一を超えるときも言いません。文学のジャンルでは既定で止めています（その時代の書き方のため）。
+  en: The case of a word's first letter (Email, email; Long-Term, long-term) is not a spelling, nor is a word in capitals only (emphasis or an acronym), nor a name in capitals with an ending (SENDs, OPENed), nor the letters of an acronym picked out beside it (CLImatology next to CLIPER). A name spelled with capitals (HBase) is still compared. Hyphenated words that are another word (re-sign, resign), part of an address (github.com), anything in quotation marks, a Japanese reading in brackets right after a word (HTTP（えいちてぃーてぃーぴー）) and the team's names are not compared. Nothing is reported when the minority is more than a third. The literature preset turns it off, since old spelling belongs to its time.
 level_meaning:
   ja: 少ないほうが語の {limit}% 以下のとき指摘
   en: reported when the minority spelling is {limit}% of the word's uses or less