chaffjs 0.35.0 → 0.36.0

package/dist/structure/written-resolve.d.ts

@@ -6,7 +6,7 @@ export type WrittenReading = {
 };
 /**
  * 平文の見出しの番地と、参照（Section 6.1(i)）の親（6.1）が木の条か平文の見出しとしてあり、その範囲の本文に札「(i)」が
- * 書かれているかを引く関数。範囲ごとの札は、要るときに一度だけ読む。Pure.
+ * 書かれているか（札を行の頭に入れ子で書いた箇条書きも読む）を引く関数。Pure.
  */
 export declare const writtenReading: (nodes: readonly StructureNode[], source: string) => WrittenReading;
 //# sourceMappingURL=written-resolve.d.ts.map

package/dist/structure/written-resolve.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"written-resolve.d.ts","sourceRoot":"","sources":["../../src/structure/written-resolve.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAOlD,mEAAmE;AACnE,MAAM,MAAM,cAAc,GAAG;IAAE,QAAQ,CAAC,SAAS,EAAE,SAAS,MAAM,EAAE,CAAC;IAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,SAAS,EAAE,aAAa,KAAK,OAAO,CAAA;CAAE,CAAC;AAyBpI;;;GAGG;AACH,eAAO,MAAM,cAAc,GAAI,OAAO,SAAS,aAAa,EAAE,EAAE,QAAQ,MAAM,KAAG,cAmBhF,CAAC"}
+{"version":3,"file":"written-resolve.d.ts","sourceRoot":"","sources":["../../src/structure/written-resolve.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,cAAc,CAAC;AAQlD,mEAAmE;AACnE,MAAM,MAAM,cAAc,GAAG;IAAE,QAAQ,CAAC,SAAS,EAAE,SAAS,MAAM,EAAE,CAAC;IAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,SAAS,EAAE,aAAa,KAAK,OAAO,CAAA;CAAE,CAAC;AAoCpI;;;GAGG;AACH,eAAO,MAAM,cAAc,GAAI,OAAO,SAAS,aAAa,EAAE,EAAE,QAAQ,MAAM,KAAG,cAchF,CAAC"}

package/dist/structure/written-resolve.js

@@ -1,4 +1,5 @@
 import { headingRegions, parentAndLabels, writtenHeadings, writtenSubdivisions } from "./written-headings.js";
+import { hasListPath, listLabels } from "./written-list-path.js";
 const targetOf = (node) => String(node.attrs["target"] ?? "");
 /**
  * 括弧の小見出しを読む範囲。木の条は、項や号を一つも読まなかったときだけ、その条の始まりから次の平文の見出しまで。
@@ -21,28 +22,33 @@ const treeRegions = (nodes, headings) => {
     });
     return regions;
 };
+/** 範囲の本文を read で読んだ結果。範囲ごとに、要るときに一度だけ読む。 */
+const perRegion = (source, read) => {
+    const cache = new Map();
+    return ([start, end]) => {
+        const key = `${String(start)}:${String(end)}`;
+        const found = cache.get(key) ?? read(source.slice(start, end));
+        cache.set(key, found);
+        return found;
+    };
+};
 /**
  * 平文の見出しの番地と、参照（Section 6.1(i)）の親（6.1）が木の条か平文の見出しとしてあり、その範囲の本文に札「(i)」が
- * 書かれているかを引く関数。範囲ごとの札は、要るときに一度だけ読む。Pure.
+ * 書かれているか（札を行の頭に入れ子で書いた箇条書きも読む）を引く関数。Pure.
  */
 export const writtenReading = (nodes, source) => {
     const references = nodes.filter((node) => node.kind === "reference").map((node) => ({ start: node.span.start, end: node.span.end, target: targetOf(node) }));
     const headings = writtenHeadings(references, source);
     const written = headingRegions(headings, source.length);
     const tree = treeRegions(nodes, headings);
-    const labels = new Map();
-    const labelsIn = ([start, end]) => {
-        const key = `${String(start)}:${String(end)}`;
-        const found = labels.get(key) ?? writtenSubdivisions(source.slice(start, end));
-        labels.set(key, found);
-        return found;
-    };
+    const labelsIn = perRegion(source, writtenSubdivisions);
+    const listIn = perRegion(source, listLabels);
     const regionsOf = (address) => [...(tree.get(address) ?? []), ...(written.get(address) ?? [])];
     const subdivision = (reference) => {
         const wanted = parentAndLabels(targetOf(reference), String(reference.attrs["label"] ?? ""));
         if (wanted === undefined)
             return false;
-        return regionsOf(wanted.parent).some((region) => wanted.labels.every((label) => labelsIn(region).has(label)));
+        return regionsOf(wanted.parent).some((region) => wanted.labels.every((label) => labelsIn(region).has(label)) || hasListPath(listIn(region), wanted.labels));
     };
     return { addresses: headings.map((heading) => heading.address), subdivision };
 };

package/dist/structure/written-resolve.js.map

@@ -1 +1 @@
-{"version":3,"file":"written-resolve.js","sourceRoot":"","sources":["../../src/structure/written-resolve.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,cAAc,EAAE,eAAe,EAAE,eAAe,EAAE,mBAAmB,EAAuB,MAAM,uBAAuB,CAAC;AASnI,MAAM,QAAQ,GAAG,CAAC,IAAmB,EAAU,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,EAAE,CAAC,CAAC;AAErF;;;GAGG;AACH,MAAM,WAAW,GAAG,CAAC,KAA+B,EAAE,QAAmC,EAAyB,EAAE;IAClH,MAAM,OAAO,GAAG,IAAI,GAAG,EAAoB,CAAC;IAC5C,oCAAoC;IACpC,IAAI,IAAI,GAAG,CAAC,CAAC;IACb,KAAK;SACF,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,CAAC,CAAC;SAClG,QAAQ,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC;SAC7D,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE;QAChB,OAAO,CAAC,QAAQ,CAAC,IAAI,CAAC,EAAE,KAAK,IAAI,QAAQ,CAAC,IAAI,IAAI,CAAC,IAAI,CAAC,KAAK;YAAE,IAAI,IAAI,CAAC,CAAC;QACzE,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,EAAE,KAAK,IAAI,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QAC5E,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC;QAC9C,KAAK,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC,CAAC;QACnC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,OAAO,EAAE,KAAK,CAAC,CAAC;IACnC,CAAC,CAAC,CAAC;IACL,OAAO,OAAO,CAAC;AACjB,CAAC,CAAC;AAEF;;;GAGG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,KAA+B,EAAE,MAAc,EAAkB,EAAE;IAChG,MAAM,UAAU,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,WAAW,CAAC,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,CAAC,IAAI,CAAC,KAAK,EAAE,GAAG,EAAE,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,MAAM,EAAE,QAAQ,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC;IAC7J,MAAM,QAAQ,GAAG,eAAe,CAAC,UAAU,EAAE,MAAM,CAAC,CAAC;IACrD,MAAM,OAAO,GAAG,cAAc,CAAC,QAAQ,EAAE,MAAM,CAAC,MAAM,CAAC,CAAC;IACxD,MAAM,IAAI,GAAG,WAAW,CAAC,KAAK,EAAE,QAAQ,CAAC,CAAC;IAC1C,MAAM,MAAM,GAAG,IAAI,GAAG,EAA+B,CAAC;IACtD,MAAM,QAAQ,GAAG,CAAC,CAAC,KAAK,EAAE,GAAG,CAAS,EAAuB,EAAE;QAC7D,MAAM,GAAG,GAAG,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC;QAC9C,MAAM,KAAK,GAAG,MAAM,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,mBAAmB,CAAC,MAAM,CAAC,KAAK,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC,CAAC;QAC/E,MAAM,CAAC,GAAG,CAAC,GAAG,EAAE,KAAK,CAAC,CAAC;QACvB,OAAO,KAAK,CAAC;IACf,CAAC,CAAC;IACF,MAAM,SAAS,GAAG,CAAC,OAAe,EAAY,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,EAAE,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;IACjH,MAAM,WAAW,GAAG,CAAC,SAAwB,EAAW,EAAE;QACxD,MAAM,MAAM,GAAG,eAAe,CAAC,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC,SAAS,CAAC,KAAK,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;QAC5F,IAAI,MAAM,KAAK,SAAS;YAAE,OAAO,KAAK,CAAC;QACvC,OAAO,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,CAAC,CAAC;IAChH,CAAC,CAAC;IACF,OAAO,EAAE,SAAS,EAAE,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,OAAO,CAAC,EAAE,WAAW,EAAE,CAAC;AAChF,CAAC,CAAC"}
+{"version":3,"file":"written-resolve.js","sourceRoot":"","sources":["../../src/structure/written-resolve.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,cAAc,EAAE,eAAe,EAAE,eAAe,EAAE,mBAAmB,EAAuB,MAAM,uBAAuB,CAAC;AACnI,OAAO,EAAE,WAAW,EAAE,UAAU,EAAE,MAAM,wBAAwB,CAAC;AASjE,MAAM,QAAQ,GAAG,CAAC,IAAmB,EAAU,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,QAAQ,CAAC,IAAI,EAAE,CAAC,CAAC;AAErF;;;GAGG;AACH,MAAM,WAAW,GAAG,CAAC,KAA+B,EAAE,QAAmC,EAAyB,EAAE;IAClH,MAAM,OAAO,GAAG,IAAI,GAAG,EAAoB,CAAC;IAC5C,oCAAoC;IACpC,IAAI,IAAI,GAAG,CAAC,CAAC;IACb,KAAK;SACF,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,SAAS,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,IAAI,KAAK,MAAM,CAAC,CAAC;SAClG,QAAQ,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC;SAC7D,OAAO,CAAC,CAAC,IAAI,EAAE,EAAE;QAChB,OAAO,CAAC,QAAQ,CAAC,IAAI,CAAC,EAAE,KAAK,IAAI,QAAQ,CAAC,IAAI,IAAI,CAAC,IAAI,CAAC,KAAK;YAAE,IAAI,IAAI,CAAC,CAAC;QACzE,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,IAAI,CAAC,EAAE,KAAK,IAAI,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC;QAC5E,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC;QAC9C,KAAK,CAAC,IAAI,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC,CAAC;QACnC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,OAAO,EAAE,KAAK,CAAC,CAAC;IACnC,CAAC,CAAC,CAAC;IACL,OAAO,OAAO,CAAC;AACjB,CAAC,CAAC;AAEF,4CAA4C;AAC5C,MAAM,SAAS,GAAG,CAAI,MAAc,EAAE,IAAyB,EAA2B,EAAE;IAC1F,MAAM,KAAK,GAAG,IAAI,GAAG,EAAa,CAAC;IACnC,OAAO,CAAC,CAAC,KAAK,EAAE,GAAG,CAAC,EAAE,EAAE;QACtB,MAAM,GAAG,GAAG,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,MAAM,CAAC,GAAG,CAAC,EAAE,CAAC;QAC9C,MAAM,KAAK,GAAG,KAAK,CAAC,GAAG,CAAC,GAAG,CAAC,IAAI,IAAI,CAAC,MAAM,CAAC,KAAK,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC,CAAC;QAC/D,KAAK,CAAC,GAAG,CAAC,GAAG,EAAE,KAAK,CAAC,CAAC;QACtB,OAAO,KAAK,CAAC;IACf,CAAC,CAAC;AACJ,CAAC,CAAC;AAEF;;;GAGG;AACH,MAAM,CAAC,MAAM,cAAc,GAAG,CAAC,KAA+B,EAAE,MAAc,EAAkB,EAAE;IAChG,MAAM,UAAU,GAAG,KAAK,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,IAAI,KAAK,WAAW,CAAC,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,EAAE,KAAK,EAAE,IAAI,CAAC,IAAI,CAAC,KAAK,EAAE,GAAG,EAAE,IAAI,CAAC,IAAI,CAAC,GAAG,EAAE,MAAM,EAAE,QAAQ,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC,CAAC;IAC7J,MAAM,QAAQ,GAAG,eAAe,CAAC,UAAU,EAAE,MAAM,CAAC,CAAC;IACrD,MAAM,OAAO,GAAG,cAAc,CAAC,QAAQ,EAAE,MAAM,CAAC,MAAM,CAAC,CAAC;IACxD,MAAM,IAAI,GAAG,WAAW,CAAC,KAAK,EAAE,QAAQ,CAAC,CAAC;IAC1C,MAAM,QAAQ,GAAG,SAAS,CAAC,MAAM,EAAE,mBAAmB,CAAC,CAAC;IACxD,MAAM,MAAM,GAAG,SAAS,CAAC,MAAM,EAAE,UAAU,CAAC,CAAC;IAC7C,MAAM,SAAS,GAAG,CAAC,OAAe,EAAY,EAAE,CAAC,CAAC,GAAG,CAAC,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,EAAE,GAAG,CAAC,OAAO,CAAC,GAAG,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;IACjH,MAAM,WAAW,GAAG,CAAC,SAAwB,EAAW,EAAE;QACxD,MAAM,MAAM,GAAG,eAAe,CAAC,QAAQ,CAAC,SAAS,CAAC,EAAE,MAAM,CAAC,SAAS,CAAC,KAAK,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;QAC5F,IAAI,MAAM,KAAK,SAAS;YAAE,OAAO,KAAK,CAAC;QACvC,OAAO,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,MAAM,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,QAAQ,CAAC,MAAM,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,CAAC,IAAI,WAAW,CAAC,MAAM,CAAC,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,CAAC,CAAC,CAAC;IAC9J,CAAC,CAAC;IACF,OAAO,EAAE,SAAS,EAAE,QAAQ,CAAC,GAAG,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,OAAO,CAAC,EAAE,WAAW,EAAE,CAAC;AAChF,CAAC,CAAC"}

package/dist/title-line.d.ts

@@ -0,0 +1,21 @@
+/**
+ * How a reader tells a title from a sentence. dangling-figure-reference reads a caption of any labelled thing; duplicate-
+ * definition reads where an attached instrument starts. Their notions differ, so each says how.
+ */
+export type TitleNotion = {
+    /** A title ending in one of these is a sentence or runs on. duplicate-definition also refuses a trailing `: ; ,`. */
+    readonly sentenceEnd: RegExp;
+    /** Every word longer than three letters starts with a capital. dangling-figure-reference only: Figure 3 shows the trend. */
+    readonly capitalised: boolean;
+    /**
+     * "any-whitespace": the document's edge may be reached across any whitespace (a line of U+3000 or NBSP before the
+     * first line). "blank-line": only lines of spaces and tabs count. dangling-figure-reference takes the first.
+     */
+    readonly edge: "any-whitespace" | "blank-line";
+};
+/**
+ * The line from lineStart to lineEnd (-1: the last line) is a title: rest, the words after its label and number, are a
+ * short title, and a blank line or the document's edge is on both sides.
+ */
+export declare const isTitleLine: (source: string, lineStart: number, lineEnd: number, rest: string, notion: TitleNotion) => boolean;
+//# sourceMappingURL=title-line.d.ts.map

package/dist/title-line.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"title-line.d.ts","sourceRoot":"","sources":["../src/title-line.ts"],"names":[],"mappings":"AAGA;;;GAGG;AACH,MAAM,MAAM,WAAW,GAAG;IACxB,qHAAqH;IACrH,QAAQ,CAAC,WAAW,EAAE,MAAM,CAAC;IAC7B,4HAA4H;IAC5H,QAAQ,CAAC,WAAW,EAAE,OAAO,CAAC;IAC9B;;;OAGG;IACH,QAAQ,CAAC,IAAI,EAAE,gBAAgB,GAAG,YAAY,CAAC;CAChD,CAAC;AA2BF;;;GAGG;AACH,eAAO,MAAM,WAAW,GAAI,QAAQ,MAAM,EAAE,WAAW,MAAM,EAAE,SAAS,MAAM,EAAE,MAAM,MAAM,EAAE,QAAQ,WAAW,KAAG,OAG7B,CAAC"}

package/dist/title-line.js

@@ -0,0 +1,27 @@
+// A title written on a line of its own, as a plain-text heading (Exhibit A to Merger Agreement, ANNEX 1): a few words with
+// no full stop, and a blank line or the document's edge on both sides. Pure.
+/** A title runs at most this many words after its label and number. */
+const TITLE_MAX_WORDS = 6;
+/** A word this long or shorter may stay in lower case in a title (to, of, the, and). */
+const TITLE_SMALL_WORD = 3;
+const BLANK_LINE = /\n[ \t\r]*\n[ \t\r]*$/u;
+const ENDS_LINE = /^[ \t\r]*\n/u;
+const BLANK = /^[ \t\r]*$/u;
+const LOWER_START = /^\p{Ll}/u;
+const isShortTitle = (rest, notion) => {
+    const title = rest.trim();
+    const words = title.split(/\s+/u).filter((word) => word !== "");
+    return (words.length <= TITLE_MAX_WORDS &&
+        !notion.sentenceEnd.test(title) &&
+        (!notion.capitalised || words.every((word) => word.length <= TITLE_SMALL_WORD || !LOWER_START.test(word))));
+};
+const isAloneBefore = (before, notion) => before === "" || BLANK_LINE.test(`\n${before}`) || (notion.edge === "any-whitespace" && before.trim() === "");
+const isAloneAfter = (after, isLastLine, notion) => isLastLine || ENDS_LINE.test(after) || BLANK.test(after) || (notion.edge === "any-whitespace" && after.trim() === "");
+/**
+ * The line from lineStart to lineEnd (-1: the last line) is a title: rest, the words after its label and number, are a
+ * short title, and a blank line or the document's edge is on both sides.
+ */
+export const isTitleLine = (source, lineStart, lineEnd, rest, notion) => isShortTitle(rest, notion) &&
+    isAloneBefore(source.slice(0, lineStart), notion) &&
+    isAloneAfter(lineEnd === -1 ? "" : source.slice(lineEnd + 1), lineEnd === -1, notion);
+//# sourceMappingURL=title-line.js.map

package/dist/title-line.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"title-line.js","sourceRoot":"","sources":["../src/title-line.ts"],"names":[],"mappings":"AAAA,2HAA2H;AAC3H,6EAA6E;AAkB7E,uEAAuE;AACvE,MAAM,eAAe,GAAG,CAAC,CAAC;AAC1B,wFAAwF;AACxF,MAAM,gBAAgB,GAAG,CAAC,CAAC;AAC3B,MAAM,UAAU,GAAG,wBAAwB,CAAC;AAC5C,MAAM,SAAS,GAAG,cAAc,CAAC;AACjC,MAAM,KAAK,GAAG,aAAa,CAAC;AAC5B,MAAM,WAAW,GAAG,UAAU,CAAC;AAE/B,MAAM,YAAY,GAAG,CAAC,IAAY,EAAE,MAAmB,EAAW,EAAE;IAClE,MAAM,KAAK,GAAG,IAAI,CAAC,IAAI,EAAE,CAAC;IAC1B,MAAM,KAAK,GAAG,KAAK,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,KAAK,EAAE,CAAC,CAAC;IAChE,OAAO,CACL,KAAK,CAAC,MAAM,IAAI,eAAe;QAC/B,CAAC,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,KAAK,CAAC;QAC/B,CAAC,CAAC,MAAM,CAAC,WAAW,IAAI,KAAK,CAAC,KAAK,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,IAAI,gBAAgB,IAAI,CAAC,WAAW,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,CAAC,CAC3G,CAAC;AACJ,CAAC,CAAC;AAEF,MAAM,aAAa,GAAG,CAAC,MAAc,EAAE,MAAmB,EAAW,EAAE,CACrE,MAAM,KAAK,EAAE,IAAI,UAAU,CAAC,IAAI,CAAC,KAAK,MAAM,EAAE,CAAC,IAAI,CAAC,MAAM,CAAC,IAAI,KAAK,gBAAgB,IAAI,MAAM,CAAC,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC;AAEhH,MAAM,YAAY,GAAG,CAAC,KAAa,EAAE,UAAmB,EAAE,MAAmB,EAAW,EAAE,CACxF,UAAU,IAAI,SAAS,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,KAAK,CAAC,IAAI,CAAC,KAAK,CAAC,IAAI,CAAC,MAAM,CAAC,IAAI,KAAK,gBAAgB,IAAI,KAAK,CAAC,IAAI,EAAE,KAAK,EAAE,CAAC,CAAC;AAExH;;;GAGG;AACH,MAAM,CAAC,MAAM,WAAW,GAAG,CAAC,MAAc,EAAE,SAAiB,EAAE,OAAe,EAAE,IAAY,EAAE,MAAmB,EAAW,EAAE,CAC5H,YAAY,CAAC,IAAI,EAAE,MAAM,CAAC;IAC1B,aAAa,CAAC,MAAM,CAAC,KAAK,CAAC,CAAC,EAAE,SAAS,CAAC,EAAE,MAAM,CAAC;IACjD,YAAY,CAAC,OAAO,KAAK,CAAC,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,OAAO,GAAG,CAAC,CAAC,EAAE,OAAO,KAAK,CAAC,CAAC,EAAE,MAAM,CAAC,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chaffjs",
-  "version": "0.35.0",
+  "version": "0.36.0",
   "description": "Prose validation harness. Finds what is hard to read, and never rewrites it for you.",
   "keywords": [
     "chaff",
@@ -88,8 +88,8 @@
   },
   "dependencies": {
     "@anthropic-ai/sdk": "^0.125.0",
-    "@chaffjs/lang-en": "0.32.0",
-    "@chaffjs/lang-ja": "0.34.0",
+    "@chaffjs/lang-en": "0.33.0",
+    "@chaffjs/lang-ja": "0.35.0",
     "character-entities": "^2.0.2",
     "mdast-util-from-markdown": "^2.0.3",
     "mdast-util-frontmatter": "^2.0.1",

package/rules/all-caps-shouting.yaml

@@ -41,8 +41,8 @@ example:
       Do not delete the log. Do not delete this file before the audit.
 
 not_flagged:
-  ja: 三語以上の連なりだけを見ます。略語の並び（文書のほかの所で小文字で書かれない語）とコードは見ません。仕様書の MUST や SHALL は慣習の大文字として数えません。段落の頭に置いた大文字の見出し語（「AGENCY:」「WORKING GROUP MEMBERS」のように、コロンで終わるか一行で段落になるもの）と、本文でその見出し語を挙げた所も見ません。法令と文学の文書では既定で止めています（大文字で目立たせる決まりや、題を大文字で組む慣習があるため）。
-  en: Only runs of three or more words. Runs of acronyms (words never written in lower case elsewhere) and code are not reported, and MUST or SHALL in a specification count as conventional capitals. A caption in capitals that opens a paragraph and ends in a colon or stands alone ("AGENCY:", "WORKING GROUP MEMBERS"), and prose naming such a caption, are not reported either. The legal and literature presets turn it off, since contracts set disclaimers in capitals by rule and older texts set titles that way.
+  ja: 三語以上の連なりだけを見ます。略語の並び（文書のほかの所で小文字で書かれない語）とコードは見ません。仕様書の MUST や SHALL は慣習の大文字として数えません。段落の頭に置いた大文字の見出し語（「AGENCY:」「WORKING GROUP MEMBERS」のように、コロンで終わるか一行で段落になるもの）と、本文でその見出し語を挙げた所も見ません。文書の頭で最初の文より前にある、全部の行が大文字で文で終わらない段落（「BOARD OF GOVERNORS」で始まるレターヘッドや宛名）も見ません。法令と文学の文書では既定で止めています（大文字で目立たせる決まりや、題を大文字で組む慣習があるため）。
+  en: Only runs of three or more words. Runs of acronyms (words never written in lower case elsewhere) and code are not reported, and MUST or SHALL in a specification count as conventional capitals. A caption in capitals that opens a paragraph and ends in a colon or stands alone ("AGENCY:", "WORKING GROUP MEMBERS"), and prose naming such a caption, are not reported either. Nor is a paragraph at the head of the document, before its first sentence, whose lines are all in capitals and end no sentence, such as a letterhead or an addressee block ("BOARD OF GOVERNORS"). The legal and literature presets turn it off, since contracts set disclaimers in capitals by rule and older texts set titles that way.
 level_meaning:
   ja: "{limit} 箇所あれば指摘"
   en: reported once there are {limit}

package/rules/announced-count-mismatch.yaml

@@ -9,8 +9,8 @@ name:
   en: A list that does not have the number of items announced
 
 why:
-  ja: 「以下の3点」と書いたのに、すぐ下の箇条書きが2つや4つだと、読み手は抜けた項目があるのか、数え間違いなのかを確かめることになります。項目を足したり消したりしたあとに、予告の数を直し忘れると起きます。箇条書きのすぐ前の文が、「以下の」「次の」のような先を指す語か、終わりのコロン（：）と一緒に数（3点、2つ、4項目）を書いているときだけ、その数を箇条書きのいちばん外側の項目の数と比べます。「出席者（6名）：田中、鈴木、…」のように、ラベルの後ろの括弧に数を書き、コロンの後ろに読点やコンマで区切って名前を並べた行も、括弧の数と並べた名前の数を比べます。
-  en: 'When a sentence says "the following three steps" and the list right below it has two or four, the reader has to check whether an item is missing or the count is wrong. It happens when an item is added or removed and the count is not updated. The number is compared with the items at the top level of the list only when the sentence right before the list announces it, with a word pointing ahead ("following", "below") or a colon at its end, and the number names what the list holds ("three steps", "two reasons"). A line with a count in brackets after a label and names after the colon, split at commas ("Attendees (6): Tanaka, Suzuki, ..."), is checked the same way: the count against the names listed.'
+  ja: 「以下の3点」と書いたのに、すぐ下の箇条書きが2つや4つだと、読み手は抜けた項目があるのか、数え間違いなのかを確かめることになります。項目を足したり消したりしたあとに、予告の数を直し忘れると起きます。箇条書きのすぐ前の文が、「以下の」「次の」のような先を指す語か、終わりのコロン（：）と一緒に数（3点、2つ、4項目）を書いているときだけ、その数を箇条書きのいちばん外側の項目の数と比べます。箇条書きのすぐ上が「3行要約」のように数と見出しの語だけの一行なら、その数も比べます。「出席者（6名）：田中、鈴木、…」のように、ラベルの後ろの括弧に数を書き、コロンの後ろに読点やコンマで区切って名前を並べた行も、括弧の数と並べた名前の数を比べます。
+  en: 'When a sentence says "the following three steps" and the list right below it has two or four, the reader has to check whether an item is missing or the count is wrong. It happens when an item is added or removed and the count is not updated. The number is compared with the items at the top level of the list only when the sentence right before the list announces it, with a word pointing ahead ("following", "below") or a colon at its end, and the number names what the list holds ("three steps", "two reasons"). A line right above the list that holds only a number and a heading word ("Three-line summary") is compared too. A line with a count in brackets after a label and names after the colon, split at commas ("Attendees (6): Tanaka, Suzuki, ..."), is checked the same way: the count against the names listed.'
 
 message:
   ja: 「{phrase}」と予告していますが、すぐ下の箇条書きは{listed}項目です

package/rules/bare-url-mix.yaml

@@ -51,8 +51,8 @@ example:
       Prices are on [the pricing page](https://example.com/pricing). Send questions through [the contact form](https://example.com/contact) today.
 
 not_flagged:
-  ja: 山括弧で囲んだ URL（<https://…>）、言葉が URL のリンク、コードと引用の中の URL は指しません。参照の形のリンク（[言葉][1]）は言葉のリンクに数えません。言葉のリンクが指摘に要る数に届かない文書と、URL をそのまま書くほうが多い文書も指しません。
-  en: A URL in angle brackets ("<https://…>"), a link whose text is the URL, and URLs in code or quotations are not reported; reference-style links ("[text][1]") are not counted as worded links; nor is a document with fewer worded links than the level needs, or one where bare URLs are not the few.
+  ja: 山括弧で囲んだ URL（<https://…>）、言葉が URL のリンク、コードと引用の中の URL、項目の値として行に一つだけ書いた URL（**ライセンス本文** https://…）は指しません。参照の形のリンク（[言葉][1]）は言葉のリンクに数えません。言葉のリンクが指摘に要る数に届かない文書と、URL をそのまま書くほうが多い文書も指しません。
+  en: A URL in angle brackets ("<https://…>"), a link whose text is the URL, URLs in code or quotations, and a URL that is a field's value alone on its line ("**Licence text** https://…") are not reported; reference-style links ("[text][1]") are not counted as worded links; nor is a document with fewer worded links than the level needs, or one where bare URLs are not the few.
 level_meaning:
   ja: 言葉のリンクが {limit} 個以上ある文書で指摘
   en: reported in a document with {limit} or more worded links

package/rules/bracket-nesting.yaml

@@ -41,8 +41,8 @@ example:
       The fee is waived on request for members, including student members under 25.
 
 not_flagged:
-  ja: 二重までの括弧、開きの無い閉じ括弧（「1)」）、コードと数式（$…$）の中の括弧、波括弧は数えません。
-  en: Two levels of brackets, a closing bracket with no opener ("1)"), brackets in code or in a formula ($…$), and curly braces are not counted.
+  ja: 二重までの括弧、開きの無い閉じ括弧（「1)」）、コードと数式（$…$）の中の括弧、波括弧は数えません。そのとおりに打ち込む文字列の引用（件名に「応募（総務課）」と記載、「【様式】（氏名）」とファイル名を変更）は、中の括弧が文字列の一部で外せないので、一つの括弧として数えます。
+  en: Two levels of brackets, a closing bracket with no opener ("1)"), brackets in code or in a formula ($…$), and curly braces are not counted. A quotation of a string to type as it stands (an e-mail subject, a file name, as in with the subject line “Entry (Training)”) counts as one bracket, since its own brackets cannot be taken out.
 level_meaning:
   ja: 括弧の重なり {limit} 重まで
   en: brackets nested up to {limit} deep

package/rules/bracket-width-consistency.yaml

@@ -44,8 +44,8 @@ example:
       会議（定例）は月曜です。報告（月次）は金曜です。資料（最新版）を配ります。
 
 not_flagged:
-  ja: 日本語の字に接する括弧だけを数えます。英語の中の括弧（f(x)、API(s)）、コード、鉤括弧で引いたものの中は数えません。
-  en: Only brackets touching Japanese text. Brackets in English text (f(x)), code, and 「」 quotations are not counted.
+  ja: 日本語の字に接する括弧だけを数えます。英語の中の括弧（f(x)、API(s)）、式の括弧（賃金 × (1 - 時間 ÷ 月平均)）、コード、鉤括弧で引いたものの中、行の頭のリンクで引いた外のページの題名（- [題名 (版)](https://…)）は数えません。
+  en: Only brackets touching Japanese text. Brackets in English text (f(x)), brackets in a formula (賃金 × (1 - 時間 ÷ 月平均)), code, 「」 quotations, and the title of an outside page quoted by a link at a line's head (- [Title (draft)](https://…)) are not counted.
 level_meaning:
   ja: 少ないほうの書き方が {limit} 箇所あれば指摘
   en: reported once the less common way appears {limit} times

package/rules/broken-link.yaml

@@ -61,5 +61,5 @@ example:
       Gather the tools. See [Setup](#setup) for more.
 
 not_flagged:
-  ja: 見出しの名前は字と数字だけで比べ、大文字小文字や記号の違いは問いません。「[1][2]」のような文献の番号、「A[i][j]」のような添字、使われていない定義も指しません。
-  en: Heading anchors are compared on letters and digits only, ignoring case and punctuation. Citation numbers ("[1][2]"), subscripts ("A[i][j]") and definitions no link uses are not reported.
+  ja: 見出しの名前は字と数字だけで比べ、大文字小文字や記号の違いは問いません。「[1][2]」のような文献の番号、「A[i][j]」のような添字、使われていない定義、サイトが定義を足す名前を省いた画像の参照（「![完了][]」の印）も指しません。
+  en: Heading anchors are compared on letters and digits only, ignoring case and punctuation. Citation numbers ("[1][2]"), subscripts ("A[i][j]"), definitions no link uses and an image reference with its label left out ("![Complete][]", a status icon the site defines) are not reported.

package/rules/cliche.yaml

@@ -1,8 +1,9 @@
 id: cliche
 layer: L2
 status: stable
-how_to_find: phrase-match
+how_to_find: phrase-in-use
 word_list: cliche
+extra_word_lists: [mention-cue]
 requires: [pos]
 languages: [ja, en]
 severity: info
@@ -47,8 +48,8 @@ example:
       The new cache cuts load time from 2 seconds to 0.5.
 
 not_flagged:
-  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.
+  ja: 一覧にある言い回しだけを見ます。見出しの中は見ず、本文の文だけを見ます。ほかの規則が見る言い回し（closing-cliche の「いかがでしたか」、ai-tell の「深く掘り下げる」「game-changer」、empty-intensifier の「needless to say」）は入れていません。「結論から言うと」は人の記事にも同じくらいあるので、「〜まとめ」「〜な件」は普通の文（まとめました、重要な件）と分けられないので見ません。文学と講演の書き起こしは対象にしません。言い回しを言葉として名指しているだけのもの（「徹底解説」という言い方、the phrase "low-hanging fruit"）も指しません。
+  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. A phrase that is only named as a term ("when saying raising the bar", the phrase "low-hanging fruit", 「徹底解説」という言い方) is not reported.
 level_meaning:
   ja: 当てはまる言い回しが {limit} 箇所あれば指摘
   en: reported once there are {limit}

package/rules/code-fence-language-mix.yaml

@@ -121,8 +121,8 @@ example:
       ```
 
 not_flagged:
-  ja: 字下げだけのコードブロック、引用の中のブロックは見ません。言語名の無いブロックが {limit} 個を超えるとき、または言語名のあるブロックより多いときは、使い分けとみなして指しません。
-  en: Indented code blocks and blocks inside a quotation are not read. When more than {limit} blocks lack a language, or they are as many as those with one, it is taken as a choice and not reported.
+  ja: 字下げだけのコードブロック、引用の中のブロック、書式の型だけを書いたブロック（<MAJOR>.<MINOR>.<PATCH>）は見ません。言語名の無いブロックが {limit} 個を超えるとき、または言語名のあるブロックより多いときは、使い分けとみなして指しません。
+  en: Indented code blocks, blocks inside a quotation, and blocks that hold only a format template (<MAJOR>.<MINOR>.<PATCH>) are not read. When more than {limit} blocks lack a language, or they are as many as those with one, it is taken as a choice and not reported.
 level_meaning:
   ja: 言語名の無いブロックが {limit} 個以下で、ある方より少ないとき指摘
   en: reported when {limit} or fewer blocks lack a language and they are fewer than those with one

package/rules/comparative-without-baseline.yaml

@@ -42,8 +42,8 @@ example:
     after: We rewrote the parser. The new engine is twice as fast as version 2.
 
 not_flagged:
-  ja: 同じ文か直前の文に比べる相手（従来、以前、前回、昨年、「〜より」「〜に比べて」）がある比較、「より多くの」「より詳しく」のような決まった言い方、程度を言う語が続かない「さらに」（さらに、〜します）、条件の下の比較（入れるとより良くなる）は指しません。
-  en: 'A comparison whose sentence or the one before names a baseline ("than", "previous", "before", "compared"), a comparative before a noun ("better results", read only in Japanese), a comparative that does not close its clause ("runs faster on large files"), and one under a condition or a hypothesis ("if it looks better", "would be easier") are not reported.'
+  ja: 同じ文か直前の文に比べる相手（従来、以前、前回、昨年、「〜より」「〜に比べて」「〜一方」）がある比較、「より多くの」「より詳しく」のような決まった言い方、程度を言う語が続かない「さらに」（さらに、〜します）、条件の下の比較（入れるとより良くなる）、今より良くする目当て（より良い社会、より良いものにする、より簡単にする）は指しません。
+  en: 'A comparison whose sentence or the one before names a baseline ("than", "previous", "before", "compared", "whereas"), one that goes past what was just named ("even better", "still faster"), a comparative before a noun ("better results", read only in Japanese), a comparative that does not close its clause ("runs faster on large files"), one under a condition or a hypothesis ("if it looks better", "would be easier"), and an aim to make something better than it is now (より良い社会, より良いものにする, より簡単にする in Japanese) are not reported.'
 
 rewrite:
   depth: light

package/rules/dangling-figure-reference.yaml

@@ -59,5 +59,5 @@ example:
       Figure 2: Costs by month
 
 not_flagged:
-  ja: 図や表を行の頭に一つも書いていない文書、長い語の一部（地図3、一覧表2）、別の法令の別表（法別表第二）、図の数（図3枚）、コードの中は見ません。
-  en: 'A document that labels no figure or table at the start of a line, a figure of another document ("Figure 5 of the 2024 report"), and code are not checked.'
+  ja: 図や表を行の頭に一つも書いていない文書、長い語の一部（地図3、一覧表2）、別の法令の別表（法別表第二）、図の数（図3枚）、コードの中は見ません。前後を空行に挟まれた、題だけの短い行（Exhibit A to Merger Agreement）も見出しとして、そこにあるとみなします。
+  en: 'A document that labels no figure or table at the start of a line, a figure of another document ("Figure 5 of the 2024 report"), and code are not checked. A short title on a line of its own between blank lines ("Exhibit A to Merger Agreement") is read as a heading, so that exhibit is there.'

package/rules/date-without-year.yaml

@@ -29,6 +29,14 @@ how_to_fix:
 
 levels: { strict: warning, normal: info, relaxed: info }
 
+options:
+  dated_genres:
+    kind: words
+    default: [business/meeting-notes, business/email]
+    about:
+      ja: 頭の日付が、書かれたことの起きた日（会議の日、手紙の日）になっている genre。その日付から5か月以内の月日は、その年と読む。Web ページの頭の日付は載せた日で、月日はどの年のこともある
+      en: Genres whose date at the top is the day the text is about (the meeting, the letter). A day and month within five months of it is read as that year's. A web page's date at the top is the day it was posted, and its days and months may be any year's
+
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: structure
@@ -64,8 +72,8 @@ example:
       - October 28, 2026: results sent
 
 not_flagged:
-  ja: 年のある日付がみな同じ年の文書では、年の無い日付を指しません（どの年か読み手に分かるため）。年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）も、書き方の選び方として指しません。ただしどちらの場合も、年をまたぐ日付は指します。見出しが年を名指す節（「2026年度の予定」「令和8年の行事」「FY27」）の日付は、見出しから年が決まるので指しません。どの年のものでもない日付も指しません。毎年の日（毎年4月1日、決算日は12月31日、年末年始閉庁日（12月29日～1月3日）、4月1日から翌年3月31日まで、1月1日から12月31日までのような一年の期間）と、例の日付（例えば…4月1日に届いた場合、例：のあとの日付、例の項目に続く「もし…」の項目）です。年のある日付が一つも無い文書、月だけ・年だけの日付は見ません。
-  en: A document whose dated dates are all in one year is not reported, since the reader can tell the year. A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported either. In both, a date across the turn of a year is still reported. A date in a section whose heading names the year ("2026 events", "FY27-Q2") takes its year from the heading and is not reported. Nor is a date of no one year, such as a day that comes round every year ("every year on April 1", "each December 31", "the fiscal year end is March 31", "April 1 to March 31 of the following year", a whole year such as "January 1 to December 31") and a date in a worked example ("for example, a request received on April 1", the dates after "e.g.", a list item opening with "If" just after an example's item). A document with no dated date, and month-only and year-only dates, are not checked.
+  ja: 年のある日付がみな同じ年の文書では、年の無い日付を指しません（どの年か読み手に分かるため）。年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）も、書き方の選び方として指しません。ただしどちらの場合も、年をまたぐ日付は指します。見出しが年を名指す節（「2026年度の予定」「令和8年の行事」「FY27」）の日付は、見出しから年が決まるので指しません。文書の日付を頭に書いた議事録や手紙（dated_genres の genre。題の下の「2024年1月17日」の行）では、その日付から5か月以内に収まる月日もその年と読めるので指しません。どの年のものでもない日付も指しません。毎年の日（毎年4月1日、決算日は12月31日、年末年始閉庁日（12月29日～1月3日）、4月1日から翌年3月31日まで、1月1日から12月31日までのような一年の期間）と、例の日付（例えば…4月1日に届いた場合、例：のあとの日付、例の項目に続く「もし…」の項目）です。年のある日付が一つも無い文書、月だけ・年だけの日付は見ません。
+  en: A document whose dated dates are all in one year is not reported, since the reader can tell the year. A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported either. In both, a date across the turn of a year is still reported. A date in a section whose heading names the year ("2026 events", "FY27-Q2") takes its year from the heading and is not reported. In minutes or a letter (the genres of the dated_genres option) that carry their own date at the top ("January 17, 2024" under the title), a day and month within five months of that date takes the year that puts it there, and is not reported. Nor is a date of no one year, such as a day that comes round every year ("every year on April 1", "each December 31", "the fiscal year end is March 31", "April 1 to March 31 of the following year", a whole year such as "January 1 to December 31") and a date in a worked example ("for example, a request received on April 1", the dates after "e.g.", a list item opening with "If" just after an example's item). A document with no dated date, and month-only and year-only dates, are not checked.
 rewrite:
   depth: light
   ja:

package/rules/defined-term-form.yaml

@@ -83,8 +83,8 @@ example:
       3. You must not resell the Services.
 
 not_flagged:
-  ja: 定義そのもの（以下「本サービス」という、「本サービス」とは）、定義より前の使用（use-before-definition が見ます）、文の頭の大文字、小文字の使用が {limit} 個を超えるか大文字の使用より多い語（ふつうの意味で使っているとみなす）は指しません。定義の文の中の使用（「顧客」とは、表紙に「顧客」と書いた者をいう）も見ません。法令・規程（statute の profile で読む文書）は、語そのものを指すために語をかぎ括弧に入れる（「株主」とあるのは、「個人情報」の定義）ので、かぎ括弧に入れ直した語は指しません。小文字の語句は、形容詞で始まるもの、形容詞や所有の語が前に付くもの（its own confidential information、additional terms of service）は普通の語句として見ません。「本」と「本件」を入れ替えた形は、その形も定義した語であるとき、長い語の一部（見本物品）のときは見ません。長くした語は、指す語（当該・前記・同・各）が前に付いただけのもの、二字以下の語（提供、登録）を長くしたもの、定義の文がその長い語を書いているもの（東京都（以下「都」という。））、その長い語も定義した語であるもの、複数形（Boxes）は見ません。
-  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"). A statute or a regulation (a document read with the statute profile) quotes a term to talk about the term itself ("controller" has the same meaning as in Part 3), so a quoted term is not reported there. A lower-case phrase that starts with an adjective, or that an adjective or a possessive comes before (its own confidential information, additional terms of service), is the ordinary phrase and is not reported. A term with its other prefix (本件業務 for 本業務) is not reported when that form is defined too, or inside a longer word (見本物品). A longer word is not reported when only a pointing word comes before the term (当該管理責任者), when the term has two characters or fewer (提供, 登録), when the definition itself writes the longer word (東京都（以下「都」という。）), when the longer word is defined too, or when it is a plural (Boxes).'
+  ja: 定義そのもの（以下「本サービス」という、「本サービス」とは）、定義より前の使用（use-before-definition が見ます）、文の頭の大文字、小文字の使用が {limit} 個を超えるか大文字の使用より多い語（ふつうの意味で使っているとみなす）は指しません。定義の文の中の使用（「顧客」とは、表紙に「顧客」と書いた者をいう）も見ません。法令・規程（statute の profile で読む文書）は、語そのものを指すために語をかぎ括弧に入れる（「株主」とあるのは、「個人情報」の定義）ので、かぎ括弧に入れ直した語は指しません。小文字の語句は、形容詞で始まるもの、形容詞や所有の語や名詞が前に付くもの（its own confidential information、additional terms of service、a common parent、a limited liability company）、of と冠詞の無い名詞が後ろに続くもの（certificates of deposit）、別の定義した語の一部であるもの（Certificate of Merger と定義した文書の certificate of merger）は普通の語句として見ません。ただし、the other party、such company のように指す語が前に付くものは指します。引用符に入れた語でも、前の語がその語を語として挙げているもの（the definition of "Material Adverse Effect"、the term "Affiliate"）は見ません。「本」と「本件」を入れ替えた形は、その形も定義した語であるとき、長い語の一部（見本物品）のときは見ません。長くした語は、指す語（当該・前記・同・各）が前に付いただけのもの、二字以下の語（提供、登録）を長くしたもの、定義の文がその長い語を書いているもの（東京都（以下「都」という。））、その長い語も定義した語であるもの、複数形（Boxes）は見ません。
+  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"). A statute or a regulation (a document read with the statute profile) quotes a term to talk about the term itself ("controller" has the same meaning as in Part 3), so a quoted term is not reported there. A lower-case phrase that starts with an adjective, or that an adjective, a possessive or a noun comes before (its own confidential information, additional terms of service, a common parent, a limited liability company), one followed by "of" and a bare noun (certificates of deposit), and one inside another defined term (certificate of merger where Certificate of Merger is defined) is the ordinary phrase and is not reported; after a pointing word (the other party, such company) it is. Nor is a quoted term that the words before it name as a term (the definition of "Material Adverse Effect", the term "Affiliate"). A term with its other prefix (本件業務 for 本業務) is not reported when that form is defined too, or inside a longer word (見本物品). A longer word is not reported when only a pointing word comes before the term (当該管理責任者), when the term has two characters or fewer (提供, 登録), when the definition itself writes the longer word (東京都（以下「都」という。）), when the longer word is defined too, or when it is a plural (Boxes).'
 level_meaning:
   ja: 小文字の使用が {limit} 個以下で、大文字の使用より少ないとき指摘
   en: lower-case uses reported when they are {limit} or fewer and fewer than the capitalised ones

package/rules/doubled-punctuation.yaml

@@ -9,8 +9,8 @@ name:
   en: Doubled punctuation
 
 why:
-  ja: 「。。」「、、」「、。」のように句読点が二つ並ぶのは、打ち直しや貼り付けで残った印です。読み手はそこで止まり、急いで書いた文書に見えます。同じ印を三つ以上並べたもの（「...」「。。。」）はわざと伸ばした書き方なので数えません。「e.g.,」「etc.;」のような略語の点の後ろの読点、「、.NET」のように次の語の頭の点、「1..10」「../」のような範囲や道のり、コードと URL も数えません。「!!」「??」は文体の選び方なので見ません。
-  en: Two punctuation marks side by side ("..", ",,", "i.e.,,") are left over from an edit or a paste. The reader stops there, and the document looks rushed. Three or more of the same mark ("...") are drawn out on purpose and are not counted, nor is the comma or semicolon after an abbreviation's period ("e.g.,", "etc.;"), a period that starts the next word (".NET"), a range or path ("1..10", "../"), code or a URL. "!!" and "??" are a matter of style and are not checked.
+  ja: 「。。」「、、」「、。」のように句読点が二つ並ぶのは、打ち直しや貼り付けで残った印です。読み手はそこで止まり、急いで書いた文書に見えます。同じ印を三つ以上並べたもの（「...」「。。。」）はわざと伸ばした書き方なので数えません。「e.g.,」「etc.;」のような略語の点の後ろの読点、英字の会社の名前の形の点と「，」（INC.、 CO.，LTD.）、「、.NET」のように次の語の頭の点、「1..10」「../」のような範囲や道のり、コードと URL も数えません。「!!」「??」は文体の選び方なので見ません。
+  en: Two punctuation marks side by side ("..", ",,", "i.e.,,") are left over from an edit or a paste. The reader stops there, and the document looks rushed. Three or more of the same mark ("...") are drawn out on purpose and are not counted, nor is the comma or semicolon after an abbreviation's period ("e.g.,", "etc.;"), the points and comma of a company form in a Japanese sentence ("INC.、", "CO.，LTD."), a period that starts the next word (".NET"), a range or path ("1..10", "../"), code or a URL. "!!" and "??" are a matter of style and are not checked.
 
 message:
   ja: 「{marks}」と句読点が重なっています
@@ -41,5 +41,5 @@ example:
       We will send the file today, as agreed.
 
 not_flagged:
-  ja: 「...」「。。。」のように三つ以上並べたものと、そのすぐ後ろの一つの印（「...。」「、、、。」）、「e.g.,」「etc.;」のような略語の後ろ、「1..10」「../」のような範囲と道のり、「!!」「??」とコロンは指しません。
-  en: Three or more of one mark ("...", "。。。") and one mark right after them ("...。", "、、、。"), the mark after an abbreviation ("e.g.,", "etc.;"), ranges and paths ("1..10", "../"), "!!", "??" and colons are not reported.
+  ja: 「...」「。。。」のように三つ以上並べたものと、そのすぐ後ろの一つの印（「...。」「、、、。」）、「e.g.,」「etc.;」のような略語の後ろ、英字の会社の形（INC.、 CO.，LTD.）、「1..10」「../」のような範囲と道のり、「!!」「??」とコロンは指しません。
+  en: Three or more of one mark ("...", "。。。") and one mark right after them ("...。", "、、、。"), the mark after an abbreviation ("e.g.,", "etc.;") or a company form ("CO.，LTD."), ranges and paths ("1..10", "../"), "!!", "??" and colons are not reported.

package/rules/doubled-word.yaml

@@ -11,8 +11,8 @@ name:
   en: Word written twice
 
 why:
-  ja: 「資料をを送ります」「確認確認します」のように同じ語が続くのは、消し忘れか、書き換えの途中で残った語です。読み手はつまずき、急いで書いた文書に見えます。重ねて「それぞれの」を言う名詞（人・単位・時・場所。「個人個人」「一行一行」「毎年毎年」）、名詞や形容詞を重ねて強める形（「駄目駄目」「若い若い」）、擬音・擬態語（「ムクムク」「もちもち」）、笑い声（「ははは」）、決まった言い回し（「などなど」「あるある」）は、重ねるのが正しい書き方なので数えていません。
-  en: The same word twice in a row ("the the"), or two words where English takes one ("our the platform"), is left over from an edit. The reader stumbles, and the document looks rushed. Repeats that grammar allows ("had had", "that that", "is, is") and repeats for emphasis ("very very") are not counted.
+  ja: 「資料をを送ります」「確認確認します」のように同じ語が続くのは、消し忘れか、書き換えの途中で残った語です。読み手はつまずき、急いで書いた文書に見えます。括弧の注を挟んで同じ助詞が二度ある形（「本規約は（以下、規約）は」）も、注を書き足したときの消し忘れです。重ねて「それぞれの」を言う名詞（人・単位・時・場所。「個人個人」「一行一行」「毎年毎年」）、名詞や形容詞を重ねて強める形（「駄目駄目」「若い若い」）、擬音・擬態語（「ムクムク」「もちもち」）、笑い声（「ははは」）、決まった言い回し（「などなど」「あるある」）は、重ねるのが正しい書き方なので数えていません。
+  en: The same word twice in a row ("the the"), or two words where English takes one ("our the platform"), is left over from an edit. The reader stumbles, and the document looks rushed. In Japanese, the same particle on both sides of a parenthetical aside (本規約は（以下、規約）は) is left over the same way. Repeats that grammar allows ("had had", "that that", "is, is") and repeats for emphasis ("very very") are not counted.
 
 message:
   ja: 「{word}」で語が重なっています。どちらかが余分です

package/rules/duplicate-definition.yaml

@@ -82,5 +82,5 @@ example:
       Users may use the Service free of charge.
 
 not_flagged:
-  ja: 二つの定義が食い違っているかは決めません。二つ目を指すだけです。語を名前にした見出しは定義に数えません。英語で、括弧に引用符だけで入れた語句のうち、名前らしく大文字で始めていない語を含むもの（("The key point is")）は、例を引いたものとして定義に数えません。
-  en: 'Whether the two definitions conflict is not decided; only the second is pointed at. A heading that names the term is not a definition. In English, a phrase quoted alone in brackets with a word a name would capitalise left in lower case ("The key point is") quotes an example, and is not a definition.'
+  ja: 二つの定義が食い違っているかは決めません。二つ目を指すだけです。語を名前にした見出しは定義に数えません。英語で、括弧に引用符だけで入れた語句のうち、名前らしく大文字で始めていない語を含むもの（("The key point is")）は、例を引いたものとして定義に数えません。添付した文書（前後を空行に挟まれた「Exhibit A to Merger Agreement」のような題の行から後ろ）は別の文書なので、その中の定義は、本文の定義とは比べず、添付した文書の中でだけ比べます。
+  en: 'Whether the two definitions conflict is not decided; only the second is pointed at. A heading that names the term is not a definition. In English, a phrase quoted alone in brackets with a word a name would capitalise left in lower case ("The key point is") quotes an example, and is not a definition. An attached instrument (from a title line such as "Exhibit A to Merger Agreement" between blank lines) is a separate document: its definitions are compared only with each other, not with those of the body.'

package/rules/duration-mismatch.yaml

@@ -62,8 +62,8 @@ example:
       The trial runs for 3 months from April 1, 2026 (until June 30, 2026).
 
 not_flagged:
-  ja: 三通りの数え方（終わりを含める、含めない、初日を数えずに過ぎた日）のどれとも合わないときだけ指します。「約3か月」「3か月程度」のような目安の期間、日付が三つ以上か期間が二つ以上ある文、年を書いた日付と書かない日付の組は見ません。「最大3泊」のような目安の泊数と、日付の無い泊数も見ません。勤務時間は、実働の書いていない所、長さの無い休憩（休憩あり）、一行に時間の範囲が二つ以上ある所（シフト表は行ごとに実働を書いた行だけ）、「翌」などの印の無い日をまたぐ範囲を見ません。勤務表は、休憩か実働の列の無い表、読めない升（休憩なし、単位の無い休憩の数、片方にだけ午前・午後を書いた時刻）のある行、夜勤などの印の無い文書で日をまたぐ行を見ません。
-  en: Only an end that matches none of the three ways of counting is pointed out. A rough length ("about 3 months"), a sentence with three or more dates or two or more lengths, and a pair of one date with a year and one without are left alone. So are a rough number of nights ("up to 3 nights") and nights written without dates. Working hours are left alone without a stated total, with a break of no length ("breaks provided"), with two or more ranges of time on a line (a shift table only on rows that state their own hours), and across midnight without a next-day mark. In a timesheet, a table without a Break or an Hours column, a row with a cell that cannot be read exactly (no break, a bare number of break, a.m. or p.m. on only one time), and a row across midnight in a document that does not mention night work are left alone.
+  ja: 三通りの数え方（終わりを含める、含めない、初日を数えずに過ぎた日）のどれとも合わないときだけ指します。「約3か月」「3か月程度」のような目安の期間、「週3日」「月10日」のような期間あたりの日数と「週休2日制」「4週8休」の中の数、日付が三つ以上か期間が二つ以上ある文、年を書いた日付と書かない日付の組は見ません。「最大3泊」のような目安の泊数と、日付の無い泊数も見ません。勤務時間は、実働の書いていない所、長さの無い休憩（休憩あり）、一行に時間の範囲が二つ以上ある所（シフト表は行ごとに実働を書いた行だけ）、「翌」などの印の無い日をまたぐ範囲を見ません。勤務表は、休憩か実働の列の無い表、読めない升（休憩なし、単位の無い休憩の数、片方にだけ午前・午後を書いた時刻）のある行、夜勤などの印の無い文書で日をまたぐ行を見ません。
+  en: Only an end that matches none of the three ways of counting is pointed out. A rough length ("about 3 months"), a count in each period ("3 days a week"), a sentence with three or more dates or two or more lengths, and a pair of one date with a year and one without are left alone. So are a rough number of nights ("up to 3 nights") and nights written without dates. Working hours are left alone without a stated total, with a break of no length ("breaks provided"), with two or more ranges of time on a line (a shift table only on rows that state their own hours), and across midnight without a next-day mark. In a timesheet, a table without a Break or an Hours column, a row with a cell that cannot be read exactly (no break, a bare number of break, a.m. or p.m. on only one time), and a row across midnight in a document that does not mention night work are left alone.
 rewrite:
   depth: light
   ja:

package/rules/email-greeting-closing.yaml

@@ -76,8 +76,8 @@ example:
       Best regards,
       Ichiro
 not_flagged:
-  ja: 引用した返信（「>」の行）と、ヘッダーと署名（「-- 」の後ろ）は見ません。手紙の頭（日付、「保護者各位」のような宛名、差出人、表題）のように文で終わらない行が続くときは、挨拶をその後ろの最初の文までに探します。挨拶と結びの言い方は決めず、語彙表のどれかがあれば足ります。メール・手紙のジャンルでだけ見ます。
-  en: 'Quoted replies (lines starting with ">"), the header and the signature after "-- " are not read. When a letter opens with lines that end no sentence (the date, the address block, the sender, a title), the greeting is looked for up to the first sentence after them. Which greeting or closing is used is not decided; any word in the lexicon will do. Only the email and letter genre runs this rule.'
+  ja: 引用した返信（「>」の行）と、ヘッダーと署名（「-- 」の後ろ）は見ません。手紙の頭（日付、「保護者各位」のような宛名、差出人、表題）のように文で終わらない行が続くときは、挨拶をその後ろの最初の文までに探します。最初の文より前に「発信者：」のようなメモの形の項目名があれば、メモとして挨拶も結びも求めません。挨拶と結びの言い方は決めず、語彙表のどれかがあれば足ります。メール・手紙のジャンルでだけ見ます。
+  en: 'Quoted replies (lines starting with ">"), the header and the signature after "-- " are not read. When a letter opens with lines that end no sentence (the date, the address block, the sender, a title), the greeting is looked for up to the first sentence after them. A memo, with a label such as "TO:" or "SUBJECT:" in capitals before the first sentence, is asked for neither a greeting nor a closing. Which greeting or closing is used is not decided; any word in the lexicon will do. Only the email and letter genre runs this rule.'
 rewrite:
   depth: light
   ja:

package/rules/email-subject-length.yaml

@@ -77,8 +77,8 @@ example:
       Best regards,
       Ichiro
 not_flagged:
-  ja: 「件名：」の行が無いメールや手紙、引用した返信の中の件名は見ません。メール・手紙のジャンルでだけ見ます。
-  en: 'An email or letter without a "Subject:" line, and subjects inside a quoted reply, are not checked. Only the email and letter genre runs this rule.'
+  ja: 「件名：」の行が無いメールや手紙、引用した返信の中の件名は見ません。「件名：」の後ろが空なら次の行を件名として読みます（項目名と値を二段に組んだ文書）。ただし次の行が挨拶、文、別の項目なら件名は空です。メール・手紙のジャンルでだけ見ます。
+  en: 'An email or letter without a "Subject:" line, and subjects inside a quoted reply, are not checked. When nothing follows the colon, the next line with text is read as the subject (a form that sets the label and the value in two columns), unless that line is a greeting, a sentence or another field. Only the email and letter genre runs this rule.'
 level_meaning:
   ja: 件名 {limit} 字まで
   en: up to {limit} characters in the subject

package/rules/empty-table-cell.yaml

@@ -58,8 +58,8 @@ example:
       | Oct 28 | Takahashi | Set the briefing date |
 
 not_flagged:
-  ja: 一番左の列は見ません（空欄で「上と同じ」を表す書き方があるため）。同じ列に空欄が二つ以上ある列、本文の行が三つより少ない表、「—」「なし」と書いたセルは指しません。合計・小計・税の行（「| 合計 | | | 48,400円 |」）、期間の合計の行（週計）、差し引きで決まる金額の行（総支給額）の数量や単価の空欄も指しません。金額の列（ほかの行がどれも数字を書いている一番右の列）の空欄は指します。Markdown の表でだけ動きます。
-  en: The first column is not checked, since a blank there often means "same as above". A column with two or more blanks, a table with fewer than three body rows, and a cell holding "—" or "none" are not reported. Nor are the quantity and unit-price blanks of a total, subtotal or tax row ("| Total | | | $612.00 |"), a period total ("Week total") or a computed amount ("Gross pay"); a blank in its amount column (the rightmost column every other row fills with a figure) still is. Markdown tables only.
+  ja: 一番左の列は見ません（空欄で「上と同じ」を表す書き方があるため）。同じ列に空欄が二つ以上ある列、本文の行が三つより少ない表、「—」「なし」と書いたセルは指しません。合計・小計・税の行（「| 合計 | | | 48,400円 |」）、期間の合計の行（週計）、差し引きで決まる金額の行（総支給額）の数量や単価の空欄も指しません。金額の列（ほかの行がどれも数字を書いている一番右の列）の空欄は指します。合計の語で始まるか終わる見出し、またはコロンで終わる見出しのすぐ後ろの空欄も、その後ろの升が埋まっていれば指しません（元の表で二つの列にまたがっていた見出しを Markdown に直すと、こう空くため。「| 得点合計 | | 8 |」）。Markdown の表でだけ動きます。
+  en: The first column is not checked, since a blank there often means "same as above". A column with two or more blanks, a table with fewer than three body rows, and a cell holding "—" or "none" are not reported. Nor are the quantity and unit-price blanks of a total, subtotal or tax row ("| Total | | | $612.00 |"), a period total ("Week total") or a computed amount ("Gross pay"); a blank in its amount column (the rightmost column every other row fills with a figure) still is. Nor is a blank right after a label that starts or ends with a total word or ends in a colon, when the cell after it is filled, since a label that spanned two columns in the source table leaves that blank once written as Markdown ("| Total score |  | 8 |"). Markdown tables only.
 rewrite:
   depth: light
   ja:

package/rules/footnote-mismatch.yaml

@@ -59,8 +59,8 @@ example:
       [^2]: During the trial period.
 
 not_flagged:
-  ja: Markdown の脚注（[^1] と行頭の [^1]:）と、※ に一桁か二桁の番号を付けた印（※1、（※2））を読みます。※ の注が文書に一つも無いときは、注を別の所（表や別紙）に置いた文書と読んで言いません。※ の後ろに数が続くもの（※2018年度）は注の番号ではありません。コードの中は読みません。
-  en: Markdown footnotes ([^1] and a line starting "[^1]:") and a ※ with a one- or two-digit number (※1, (※2)) are read. When a document has no ※ note at all, its notes are taken to be elsewhere (a table, an annex) and nothing is reported for ※. A ※ before a longer number ("※2018") is not a note mark. Code is not read.
+  ja: Markdown の脚注（[^1] と行頭の [^1]:）と、※ に一桁か二桁の番号を付けた印（※1、（※2））を読みます。※ の注が文書に一つも無いときは、注を別の所（表や別紙）に置いた文書と読んで言いません。※ の後ろに数が続くもの（※2018年度）と英語の序数（※1st Party）は注の番号ではありません。引用（>）の中の印も注を指していると読みます。コードの中は読みません。
+  en: Markdown footnotes ([^1] and a line starting "[^1]:") and a ※ with a one- or two-digit number (※1, (※2)) are read. When a document has no ※ note at all, its notes are taken to be elsewhere (a table, an annex) and nothing is reported for ※. A ※ before a longer number ("※2018") or an English ordinal ("※1st Party") is not a note mark. A mark inside a quotation (">") still points to its note. Code is not read.
 
 rewrite:
   ja:

package/rules/heading-echo.yaml

@@ -60,8 +60,8 @@ example:
       Attach the receipt and submit it by the end of the month.
 
 not_flagged:
-  ja: 短い見出し（言葉が少なく、重なりを測れないもの）は見ません。見出しの頭の番号の札（例 3：、Step 3:、1.、第2章）は重なりに数えません。中身の置き場所（リンク、URL、コードで書いたファイルのパス）へ読者を渡す文（詳しくは `docs/api.md` にあります。）は繰り返しではありません。見出しの直後が名前だけの行（レターヘッド）や項目と値の行（担当者：山田）なら、書式の頭で、繰り返しではありません。
-  en: Headings too short to measure an overlap are not checked. A number label at the head of a heading (Step 3:, Example 4:, 1., Chapter 2:) is not counted in the overlap. A sentence that sends the reader to where the content lives (a link, a web address, a file path in code, as in The full reference is in `docs/api.md`.) is not an echo. A name alone (a letterhead) or a field and its value (a contact name after its label) right under the heading is the top of a form, not an echo.
+  ja: 短い見出し（言葉が少なく、重なりを測れないもの）は見ません。見出しの頭の番号の札（例 3：、Step 3:、1.、第2章）は重なりに数えません。中身の置き場所（リンク、URL、コードで書いたファイルのパス）へ読者を渡す文（詳しくは `docs/api.md` にあります。）は繰り返しではありません。見出しの直後が名前だけの行（レターヘッド）や項目と値の行（担当者：山田）なら、書式の頭で、繰り返しではありません。見出しが扱うものの名前だけの行（「実施要綱について」の下の「実施要綱」、「ご意見をお聞かせください」一覧）は、リンクや添付の札で、繰り返しではありません。行頭の項目名（「## Project Status」の下の「Current project status：Ongoing」）は報告の書式の札なので、重なりは値の側だけで測ります。
+  en: Headings too short to measure an overlap are not checked. A number label at the head of a heading (Step 3:, Example 4:, 1., Chapter 2:) is not counted in the overlap. A sentence that sends the reader to where the content lives (a link, a web address, a file path in code, as in The full reference is in `docs/api.md`.) is not an echo. A name alone (a letterhead) or a field and its value (a contact name after its label) right under the heading is the top of a form, not an echo. A line that only names what the heading is about (Annual maintenance schedule under About the annual maintenance schedule, or a list titled with the quoted heading) is the label of a link or an attachment, not an echo. A field label opening the line (the Current project status field under Project Status) belongs to a report template, so only the value is measured against the heading.
 level_meaning:
   ja: 見出しと直後の文の重なりが {limit}% 以上なら指摘
   en: reported when the first sentence overlaps the heading by {limit}% or more

package/rules/ime-residue.yaml

@@ -37,8 +37,8 @@ example:
       この資料はとてもおもしろいです。
 
 not_flagged:
-  ja: 大文字（A 社、B さん）、二字以上の英字（while 文、note）、コードの中は指しません。後ろに助詞が続く一字（変数 x が、まず x を、を x で）は変数の名と読み、一字の後ろが漢字のもの（の x 座標）も指しません。片仮名の後ろの一字（サイズ m、プラン b）は記号と読み、パスの中（/docs/…）も見ません。
-  en: Capitals (A社, Bさん), runs of two or more letters (while文, note) and code are not reported. A letter followed by a particle (変数xが, まずxを, をxで) is read as the name of a variable, and a letter followed by a kanji (のx座標) is not reported either. A letter after katakana (サイズm, プランb) is read as a label, and paths (/docs/…) are not read.
+  ja: 大文字（A 社、B さん）、二字以上の英字（while 文、note）、コードの中は指しません。後ろに助詞が続く一字（変数 x が、まず x を、を x で）は変数の名と読み、一字の後ろが漢字のもの（の x 座標）も指しません。片仮名の後ろの一字（サイズ m、プラン b）は記号と読み、パスの中（/docs/…）も見ません。母音の一字（e ラーニング、i モード）は、ローマ字入力ならすぐ仮名になるので残りではなく、語の一部と読みます。
+  en: Capitals (A社, Bさん), runs of two or more letters (while文, note) and code are not reported. A letter followed by a particle (変数xが, まずxを, をxで) is read as the name of a variable, and a letter followed by a kanji (のx座標) is not reported either. A letter after katakana (サイズm, プランb) is read as a label, and paths (/docs/…) are not read. A lone vowel (eラーニング, iモード) is part of the word, since romaji input turns a vowel into kana at once and never leaves it behind.
 sources: [textlint-ja-presets]
 rewrite:
   depth: light