chaffjs 0.19.0 → 0.21.0

package/rules/excessive-hedging.yaml

@@ -1,6 +1,6 @@
 id: excessive-hedging
 layer: L2
-status: experimental
+status: stable
 how_to_find: hedging
 word_list: excessive-hedging
 # 1 つの文の重なりを数えるときの、それだけでは逃げていない包む言い方（「という状況です」、may）と、
@@ -35,6 +35,11 @@ how_to_fix:
 levels: { strict: 3, normal: 6, relaxed: 12 }
 
 use_for: [business, blog, technical, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  academic: "Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence."
+  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."
 sources: [femmer-2017]
 
 group: wording
@@ -56,6 +61,7 @@ level_meaning:
   ja: 1000 字あたり逃げの表現 {limit} 個まで（一文に重ねた逃げは、文書の長さによらず指摘）
   en: up to {limit} hedges per 1000 words (hedges stacked in one sentence are reported whatever the length)
 rewrite:
+  depth: light
   ja:
     direction: 重ねた逃げは一つだけ残すか、確かめたことなら全部外して言い切ってください。言い切れないなら、何が分かれば言い切れるかを書きます。
     pairs:

package/rules/exclamation-width-consistency.yaml

@@ -0,0 +1,64 @@
+id: exclamation-width-consistency
+layer: L1
+status: stable
+how_to_find: mark-consistency
+word_list: exclamation-width
+languages: [ja]
+severity: info
+
+name:
+  ja: ！？ の全角と半角の混在
+  en: Full-width and half-width ! and ? mixed
+
+why:
+  ja: 日本語の文の中で、感嘆符と疑問符を全角（！？）と半角（!?）で混ぜて書くと、別々の所から貼り合わせた文書に見えます。どちらが正しいかは決めません。日本語の字に接するものだけを、感嘆符と疑問符それぞれで数え、少ないほうを指します。
+  en: In a Japanese document, ! and ? written both full-width (！？) and half-width (!?) make it look pasted together. chaff does not pick a side; it counts only marks touching Japanese text, each kind apart, and points at the less common way.
+
+message:
+  ja: 「{mark}」と書いています（この文書はふつう「{usual}」。{of} 箇所のうち {count} 箇所が違う）
+  en: '"{mark}" here, where the document usually writes "{usual}" ({count} of {of})'
+
+# 少ないほうが 5 箇所以上で、全体の 2 割を超えるとき。書き損じではなく書き方が二通りあるので、1 件にまとめて両方の数を言う。
+messages:
+  mixed:
+    ja: "「{mark}」の仲間を、全角で {spaced} 箇所、半角で {touching} 箇所書いています。この文書には書き方が二通りあります"
+    en: '"{mark}" is written two ways in this document ({spaced} full-width, {touching} half-width)'
+
+how_to_fix:
+  ja: 文書の多いほうの書き方に合わせてください。
+  en: Match the way the rest of the document writes it.
+
+levels: { strict: 1, normal: 1, relaxed: 3 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: consistency
+summary:
+  ja: 日本語の文の中で、！？ の全角と半角（!?）が混ざっている所
+  en: Full-width ！？ and half-width !? mixed in one Japanese document
+example:
+  ja:
+    before: |
+      本当ですか？ 来週ですか？ 今日ですか?
+    after: |
+      本当ですか？ 来週ですか？ 今日ですか？
+
+not_flagged:
+  ja: 日本語の字に接するものだけを数えます。URL やコードの中の「?」、英語の文の中のものは数えません。
+  en: Only marks touching Japanese text. A ? in a URL, in code or in English text is not counted.
+level_meaning:
+  ja: 少ないほうの書き方が {limit} 箇所あれば指摘
+  en: reported once the less common way appears {limit} times
+rewrite:
+  depth: light
+  ja:
+    direction: 指された感嘆符・疑問符だけを、文書の多いほうの書き方（全角か半角）に替えてください。
+    pairs:
+      - before: 今日ですか?
+        after: 今日ですか？
+      - before: 完成しました!
+        after: 完成しました！
+    keep:
+      - 文の言葉
+    avoid:
+      - 感嘆符を増やしたり減らしたりする

package/rules/expletive-construction.yaml

@@ -1,6 +1,6 @@
 id: expletive-construction
 layer: L3
-status: experimental
+status: stable
 how_to_find: expletive
 requires: [pos]
 languages: [en]
@@ -25,6 +25,12 @@ how_to_fix:
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
 use_for: [blog, business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  academic: "Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence."
+  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."
 
 group: readability
 summary:

package/rules/fact-conflict.yaml

@@ -0,0 +1,113 @@
+id: fact-conflict
+layer: L3
+status: stable
+how_to_find: fact-conflict
+requires: [quantities]
+uses: [pos]
+severity: warning
+
+name:
+  ja: 同じ項目に違う値が書いてある
+  en: One item given two different values
+
+why:
+  ja: 同じ節の中で「締切：10月5日」と「締切：10月7日」のように、同じ項目に違う値を書くと、読み手はどちらを信じればよいか分かりません。日程や料金を直したときに、一か所だけ直し忘れると起きます。「項目：値」「項目は値です」と書いた所と表の升を読み、同じ節で同じ項目名（全角半角、大文字小文字は揃えて比べます）に、同じ単位で違う値があれば指します。
+  en: 'When one section says "Deadline: May 3" and later "Deadline: May 5", the reader cannot tell which to trust. It happens when a date or a price is changed in one place and not in the other. Values written as "Item: value" or "The item is value", and table cells, are read; the same item name (case and width aside) with two different values in the same unit within one section is pointed out.'
+
+message:
+  ja: 「{label}」が {value} と書かれていますが、同じ節の前の所では {other} です
+  en: '"{label}" is {value} here, but {other} earlier in the same section'
+
+how_to_fix:
+  ja: どちらの値が正しいかを確かめて、もう一方を直してください。別のもの（別の回、別の対象）の値なら、項目名にそれを書き分けてください（「第2回の締切」）。
+  en: Check which value is right and correct the other. If they are values of different things (another session, another group), say so in the item name ("Second session deadline").
+
+levels: { 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: 同じ節の中で、同じ項目（締切、料金など）に違う値を書いた所
+  en: The same item (a deadline, a fee) given two different values in one section
+example:
+  ja:
+    before: |
+      締切：10月5日
+
+      - 参加費：3,000円
+      - 締切：10月7日
+    after: |
+      締切：10月5日
+
+      - 参加費：3,000円
+      - 締切：10月5日
+  en:
+    before: |
+      Deadline: May 3, 2026
+
+      - Fee: $300
+      - Deadline: May 5, 2026
+    after: |
+      Deadline: May 3, 2026
+
+      - Fee: $300
+      - Deadline: May 3, 2026
+
+not_flagged:
+  ja: 違う見出しの下、違う親の項目の下、太字だけの行や「第2回：」のような行の後ろの値は、別のものの値として比べません。値の後ろに条件が続くもの（「3,000円から」「10月5日に開催」）、読点のあとから始まる項目名（「大人は、参加費は」）、単位の違う値（単位の食い違いは別に見ます）も比べません。同じ項目に三通り以上の値があれば、一覧として何も言いません。
+  en: Values under different headings, under different parent list items, or after a bold-only line or a line like "Session 2:" are taken as values of different things. A value followed by a condition ("$300 per person", "May 3 at noon"), a name that starts after a comma ("For adults, the fee"), and values in different units are not compared. An item with three or more different values is read as a list and left alone.
+rewrite:
+  depth: light
+  ja:
+    direction: 二つの値のどちらが正しいかを書き手に確かめ、もう一方を同じ値に直してください。どちらが正しいか文書から決まらないときは、推測で選ばずに書き手に聞いてください。
+    pairs:
+      - before: |
+          締切：10月5日
+          （中略）
+          締切：10月7日
+        after: |
+          締切：10月5日
+          （中略）
+          締切：10月5日
+      - before: |
+          参加費は3,000円です。
+          （中略）
+          参加費は3,500円です。
+        after: |
+          参加費は3,000円です。
+          （中略）
+          第2回の参加費は3,500円です。
+    keep:
+      - 正しいと確かめた値
+      - 項目名と単位
+    avoid:
+      - どちらが正しいかを推測で決める
+      - 片方の値を消して、項目ごと無くす
+  en:
+    direction: Ask the writer which of the two values is right and make the other match it. If the document does not settle it, ask rather than guess.
+    pairs:
+      - before: |
+          Deadline: May 3
+          (…)
+          Deadline: May 5
+        after: |
+          Deadline: May 3
+          (…)
+          Deadline: May 3
+      - before: |
+          The fee is $300.
+          (…)
+          The fee is $350.
+        after: |
+          The fee is $300.
+          (…)
+          The late fee is $350.
+    keep:
+      - the value confirmed as right
+      - the item name and the unit
+    avoid:
+      - guessing which value is right
+      - deleting one of them along with the item

package/rules/figure-reference-order.yaml

@@ -0,0 +1,115 @@
+id: figure-reference-order
+layer: L3
+status: stable
+how_to_find: figure-order
+severity: info
+
+name:
+  ja: 図や表を参照する順番と位置
+  en: Figures and tables referred to out of order or out of place
+
+why:
+  ja: 論文の図と表は、本文で初めて参照した順に番号を振り、参照の近くに置くのが決まりです。図2を図1より先に参照していたり、図が載った節を過ぎてから初めて参照していたりすると、読み手は図と本文の間を行ったり来たりします。図を入れ替えたり節を動かしたりしたあとに起きます。三つを見ます。初めての参照が番号の順になっていない図、キャプションのある節を過ぎて見出しを越えてから初めて参照する図、同じ種類のほかの図は参照しているのに一度も参照しない図です。
+  en: In a paper, figures and tables are numbered in the order the text first refers to them, and placed near that reference. When Figure 2 is referred to before Figure 1, or a figure is first referred to only after the section it appears in, the reader goes back and forth between the figure and the text. It happens after figures are swapped or sections moved. Three things are checked. A figure whose first reference comes out of numeric order; a figure first referred to only past a heading after its caption; and a figure never referred to while others of its kind are.
+
+message:
+  ja: "{label}の参照が番号の順になっていません"
+  en: "{label} is not referred to in numeric order"
+
+messages:
+  order:
+    ja: "{label}を初めて参照するのが、{after}より後です"
+    en: "{label} is first referred to after {after}"
+  late:
+    ja: "{label}を初めて参照するのが、図や表を載せた節より後です"
+    en: "{label} is first referred to only after the section it appears in"
+  unreferenced:
+    ja: "{label}は本文で一度も参照していません"
+    en: "{label} is never referred to in the text"
+
+how_to_fix:
+  ja: 初めて参照する順に図と表の番号を振り直すか、参照の順を入れ替えてください。図は初めて参照する所の近くに置き、参照しない図は参照を足すか消してください。
+  en: Renumber the figures and tables in the order they are first referred to, or reorder the references. Place each figure near its first reference, and refer to every figure or remove it.
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [academic, legal, docs, literature, speech]
+off_for:
+  legal: "A paper's citations, figures and abstract: only the academic paper genre turns these on."
+  docs: "A paper's citations, figures and abstract: only the academic paper genre turns these on."
+  literature: "A paper's citations, figures and abstract: only the academic paper genre turns these on."
+  speech: "A paper's citations, figures and abstract: only the academic paper genre turns these on."
+
+group: structure
+summary:
+  ja: 図2を図1より先に参照する、図を載せた節より後で初めて参照する、一度も参照しない図や表
+  en: A figure or table referred to before a lower-numbered one, first referred to only after its section, or never referred to
+example:
+  ja:
+    config: { genre: academic/paper }
+    before: |
+      # 昼寝と記憶
+
+      図2に時間ごとの再生率を示す。図1に研究の流れを示す。
+
+      図1　研究の流れ
+
+      図2　時間ごとの再生率
+    after: |
+      # 昼寝と記憶
+
+      図1に研究の流れを示す。図2に時間ごとの再生率を示す。
+
+      図1　研究の流れ
+
+      図2　時間ごとの再生率
+  en:
+    config: { genre: academic/paper }
+    before: |
+      # Naps and memory
+
+      Figure 2 shows recall by hour. Figure 1 shows the study design.
+
+      Figure 1: Study design
+
+      Figure 2: Recall by hour
+    after: |
+      # Naps and memory
+
+      Figure 1 shows the study design. Figure 2 shows recall by hour.
+
+      Figure 1: Study design
+
+      Figure 2: Recall by hour
+
+not_flagged:
+  ja: キャプション（行の頭の「図1　…」）を一つも書いていない種類の図、他の文書の図（「報告書の図5」）、リンクの字、番号が字や漢数字のもの（付録A、別表第一）は見ません。付録・別表・様式は文書の終わりに置くものなので、参照の順だけを見て、置き場所と参照の有無は見ません。見出しの無い文書では、節を越えたかどうかは見ません。論文のジャンルでだけ見ます。
+  en: 'A kind of figure the document never captions (a "Figure 1: …" line), figures of another document ("Figure 5 of the report"), link text, and numbers that are letters or numerals in words (Appendix A) are left alone. Appendices and annexes sit at the end, so only the order of their references is checked, not where they are or whether they are referred to. A document without headings is not checked for references past the section. Only the academic paper genre runs this rule.'
+rewrite:
+  depth: structure
+  ja:
+    direction: 初めて参照する順に番号が増えるよう、参照の順を入れ替えるか、図と表の番号を振り直してください。振り直すなら、キャプションとほかの参照も同じく直します。参照しない図には、本文に参照の文を足します。
+    pairs:
+      - before: 図2に時間ごとの再生率を示す。図1に研究の流れを示す。
+        after: 図1に研究の流れを示す。図2に時間ごとの再生率を示す。
+      - before: 結果を表2と表1にまとめた。
+        after: 結果を表1と表2にまとめた。
+    keep:
+      - 図と表の中身とキャプション
+      - 本文の主張
+    avoid:
+      - キャプションの番号だけを変えて本文の参照を残す
+      - 図の中身に無いことを参照の文に書く
+  en:
+    direction: Reorder the references, or renumber the figures and tables, so the numbers rise in the order of first reference. When renumbering, change the captions and every other reference to match. For a figure never referred to, add a sentence that refers to it.
+    pairs:
+      - before: Figure 2 shows recall by hour. Figure 1 shows the study design.
+        after: Figure 1 shows the study design. Figure 2 shows recall by hour.
+      - before: Table 2 and Table 1 summarise the results.
+        after: Table 1 and Table 2 summarise the results.
+    keep:
+      - what each figure and table shows, and its caption
+      - the claims of the text
+    avoid:
+      - changing a caption's number and leaving the references as they were
+      - describing in the reference what the figure does not show

package/rules/fullwidth-alnum-consistency.yaml

@@ -1,9 +1,9 @@
 id: fullwidth-alnum-consistency
 layer: L3
-status: experimental
+status: stable
 how_to_find: fullwidth-alnum
 languages: [ja]
-severity: warning
+severity: info
 
 name:
   ja: 英数字の全角と半角が混ざっている

package/rules/hankaku-kana.yaml

@@ -1,6 +1,6 @@
 id: hankaku-kana
 layer: L1
-status: experimental
+status: stable
 how_to_find: hankaku-kana
 languages: [ja]
 severity: warning

package/rules/heading-command-missing.yaml

@@ -0,0 +1,109 @@
+id: heading-command-missing
+layer: L1
+status: stable
+how_to_find: heading-command
+requires: [markdown]
+severity: info
+
+name:
+  ja: 見出しのコマンドやオプションが、その節のコードに無い
+  en: A heading names a command its section's code does not show
+
+why:
+  ja: 「## `--dry-run`」の節のコード例が「--dryrun」を使っていると、読み手はどちらが正しいか分かりません。コマンドやオプションの名前を変えたときに、見出しかコード例の片方だけを直すと起きます。見出しのコードの部分（`npm install`、`--force`、`init`）が、その節（次の同じ深さか浅い見出しまで）のコードブロックにもコードの部分にも無いとき指します。節にコードが一つも無ければ見ません。
+  en: 'When the section "## `--dry-run`" shows an example using "--dryrun", the reader cannot tell which is right. It happens when a command or an option is renamed and only the heading or only the example is updated. chaff points out a heading''s code part (`npm install`, `--force`, `init`) that appears in none of the code blocks or code spans of its section (up to the next heading of the same or a higher level). A section with no code at all is not checked.'
+
+message:
+  ja: 見出しの「{command}」が、この節のコードにありません
+  en: '"{command}" in this heading does not appear in the section''s code'
+
+how_to_fix:
+  ja: 見出しとコード例のどちらが今の名前かを確かめて、もう一方を直してください。
+  en: Check which of the heading and the example has the current name, and correct the other.
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [technical, docs, blog, legal, academic, literature, speech]
+off_for:
+  legal: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  academic: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  literature: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+  speech: "Code blocks, shell prompts, command headings and numbered steps belong to technical writing."
+
+group: facts
+summary:
+  ja: 見出しが名指すコマンドやオプションが、その節のコード例のどこにも無い所
+  en: A command or option named in a heading that the section's examples never use
+example:
+  ja:
+    config: { genre: docs/manual }
+    before: |
+      # 使い方
+
+      ## `--dry-run`
+
+      直さずに、直す所だけを見せます。
+
+      ```bash
+      npx chaffjs fix --dryrun README.md
+      ```
+    after: |
+      # 使い方
+
+      ## `--dry-run`
+
+      直さずに、直す所だけを見せます。
+
+      ```bash
+      npx chaffjs fix --dry-run README.md
+      ```
+  en:
+    config: { genre: docs/manual }
+    before: |
+      # Usage
+
+      ## `--dry-run`
+
+      Show what would change without changing it.
+
+      ```bash
+      npx chaffjs fix --dryrun README.md
+      ```
+    after: |
+      # Usage
+
+      ## `--dry-run`
+
+      Show what would change without changing it.
+
+      ```bash
+      npx chaffjs fix --dry-run README.md
+      ```
+
+not_flagged:
+  ja: コードの無い節、ファイル名や関数名（`config.yaml`、`useEffect`）を書いた見出し、コードの部分の無い見出しは見ません。`--force` は `--force-with-lease` の中にあっても、あったとは数えません。
+  en: "Sections with no code, headings naming a file or a function (`config.yaml`, `useEffect`), and headings with no code part are not checked. `--force` inside `--force-with-lease` does not count as shown."
+rewrite:
+  depth: light
+  ja:
+    direction: 見出しとコード例のどちらが今のコマンドやオプションの名前かを書き手に確かめ、もう一方を直してください。分からなければ推測で書き換えず、確かめるよう伝えます。
+    pairs:
+      - before: npx chaffjs fix --dryrun README.md
+        after: npx chaffjs fix --dry-run README.md
+      - before: "## `chaff lint`"
+        after: "## `chaff check`"
+    keep:
+      - 節の説明の文
+    avoid:
+      - どちらの名前が正しいかを推測で決める
+  en:
+    direction: Ask the writer which of the heading and the example has the current name of the command or option, and correct the other. If it is not clear, do not guess; ask.
+    pairs:
+      - before: npx chaffjs fix --dryrun README.md
+        after: npx chaffjs fix --dry-run README.md
+      - before: "## `chaff lint`"
+        after: "## `chaff check`"
+    keep:
+      - the section's explanation
+    avoid:
+      - guessing which name is right

package/rules/heading-echo.yaml

@@ -3,7 +3,7 @@ layer: L1
 status: stable
 how_to_find: heading-echo
 uses: [pos]
-severity: warning
+severity: info
 
 name:
   ja: 見出しの繰り返し
@@ -29,6 +29,11 @@ levels:
   relaxed: 75
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  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."
 
 group: readability
 summary:

package/rules/heading-level-skip.yaml

@@ -1,9 +1,9 @@
 id: heading-level-skip
 layer: L1
-status: experimental
+status: stable
 how_to_find: heading-level-skip
 requires: [markdown]
-severity: warning
+severity: info
 
 name:
   ja: 見出しの深さが飛んでいる
@@ -21,7 +21,7 @@ how_to_fix:
   ja: 一つ前の見出しより一段だけ深くしてください。文字の大きさを変えたいだけなら、深さではなく表示の設定で変えてください。
   en: Make the heading one level deeper than the one before it. If only the size on screen was the point, change the style instead of the level.
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 

package/rules/heading-numbering-mix.yaml

@@ -0,0 +1,141 @@
+id: heading-numbering-mix
+layer: L1
+status: stable
+how_to_find: heading-numbering
+requires: [markdown]
+severity: info
+
+name:
+  ja: 見出しの番号の付け方が揃っていない
+  en: Heading numbering mixed
+
+why:
+  ja: 「1. 概要」「2. 手順」と番号を付けた見出しの隣に番号の無い「まとめ」があったり、「1.」「2.」の隣に「3）」や「第4章」があったりすると、読み手は番号の無い見出しが別の扱いなのか、番号が抜けたのか迷います。目次や参照（「3 章で述べた」）とも合わなくなります。どちらの付け方が正しいかは決めず、同じ親の下の同じ深さの見出し（兄弟）のうち少ないほうを指します。番号を持つ語（第1章、Chapter 1）と、番号を付けないのがふつうの前後の見出し（目次、参考文献）は言語ごとの語彙表にあります。
+  en: A numbered "1. Overview" and "2. Steps" next to an unnumbered "Summary", or "1." and "2." next to "3)" or "Chapter 4", leave the reader unsure whether the odd one is meant to be different or lost its number, and the numbers stop matching the table of contents and cross-references. chaff does not pick a style; among headings with the same parent and depth (siblings) it points at the minority. Words that carry a number (Chapter 1, 第1章) and front and back matter that is never numbered (Contents, References) are in each language's lexicon.
+
+message:
+  ja: 見出し「{heading}」の番号の付け方が、兄弟の見出し（「{example}」など {count} 個）と違います
+  en: 'The heading "{heading}" is numbered differently from its siblings ("{example}" and {count} in all)'
+messages:
+  unnumbered:
+    ja: 見出し「{heading}」だけ番号がありません（兄弟の見出しは「{example}」など {count} 個が番号付き）
+    en: 'The heading "{heading}" has no number, while {count} of its siblings do ("{example}")'
+  numbered:
+    ja: 見出し「{heading}」だけ番号があります（兄弟の見出しは「{example}」など {count} 個が番号なし）
+    en: 'The heading "{heading}" is numbered, while {count} of its siblings are not ("{example}")'
+  style:
+    ja: 見出し「{heading}」の番号の書き方が、兄弟の見出し（「{example}」など {count} 個）と違います
+    en: 'The heading "{heading}" writes its number differently from {count} of its siblings ("{example}")'
+
+how_to_fix:
+  ja: 兄弟の見出しで番号の付け方を揃えてください。番号の無い見出しを本文の外に置くつもりなら、親を分けてください。
+  en: Number sibling headings the same way. If the unnumbered one is meant to sit outside the numbered body, give it a different parent.
+
+placeholders:
+  heading:
+    ja: 見出し
+    en: the heading
+  example:
+    ja: 兄弟の見出し
+    en: a sibling
+  count:
+    ja: 〇
+    en: N
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 「1. 概要」「2. 手順」「まとめ」や「1.」「2.」「3）」のように、兄弟の見出しで番号の付け方が混ざっている所
+  en: Sibling headings numbered in mixed ways, such as "1. Overview", "2. Steps", "Summary"
+example:
+  ja:
+    before: |
+      # 報告
+
+      ## 1. 概要
+
+      概要です。
+
+      ## 2. 手順
+
+      手順です。
+
+      ## まとめ
+
+      まとめです。
+    after: |
+      # 報告
+
+      ## 1. 概要
+
+      概要です。
+
+      ## 2. 手順
+
+      手順です。
+
+      ## 3. まとめ
+
+      まとめです。
+  en:
+    before: |
+      # Report
+
+      ## 1. Overview
+
+      The overview.
+
+      ## 2. Steps
+
+      The steps.
+
+      ## Summary
+
+      The summary.
+    after: |
+      # Report
+
+      ## 1. Overview
+
+      The overview.
+
+      ## 2. Steps
+
+      The steps.
+
+      ## 3. Summary
+
+      The summary.
+
+not_flagged:
+  ja: 兄弟が三つ未満の所、少ないほうと多いほうが同じ数の所、深さや親の違う見出しどうし（「1.」の下の「1.1」）は比べません。前後の見出し（目次、参考文献、付録）は兄弟に数えません。見出しの頭の数でも、区切りの記号の無い数（「2026年の計画」「3つの理由」）は番号と読みません。
+  en: Fewer than three siblings, a tie between the two sides, and headings at different depths or under different parents ("1." and "1.1") are not compared. Front and back matter (Contents, References, Appendix) is not counted among the siblings. A number at the head of a heading without a separator ("2026 roadmap", "3 reasons") is not read as a heading number.
+rewrite:
+  depth: light
+  ja:
+    direction: 兄弟の見出しで、多いほうの番号の付け方に揃えてください。番号の無い見出しに番号を足すか、番号の書き方（1. と 1））を一つにします。見出しの言葉は変えません。
+    pairs:
+      - before: 「## 1. 概要」「## 2. 手順」「## まとめ」
+        after: 「## 1. 概要」「## 2. 手順」「## 3. まとめ」
+      - before: 「## 1. 背景」「## 2. 方針」「## 3）課題」
+        after: 「## 1. 背景」「## 2. 方針」「## 3. 課題」
+    keep:
+      - 見出しの言葉と順番
+      - 見出しの深さ
+    avoid:
+      - 番号を付けない見出しを本文の中に残したまま、ほかの見出しの番号を外す
+  en:
+    direction: Number the sibling headings the way most of them are numbered. Add the missing number, or write every number in one style ("1." or "1)"). Keep the heading text.
+    pairs:
+      - before: '"## 1. Overview", "## 2. Steps", "## Summary"'
+        after: '"## 1. Overview", "## 2. Steps", "## 3. Summary"'
+      - before: '"## 1. Background", "## 2. Plan", "## 3) Risks"'
+        after: '"## 1. Background", "## 2. Plan", "## 3. Risks"'
+    keep:
+      - the heading text and order
+      - the heading depth
+    avoid:
+      - stripping the numbers from the other headings to match the odd one