chaffjs 0.20.0 → 0.22.0

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

@@ -1,6 +1,6 @@
 id: fact-conflict
 layer: L3
-status: experimental
+status: stable
 how_to_find: fact-conflict
 requires: [quantities]
 uses: [pos]
@@ -25,6 +25,8 @@ how_to_fix:
 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:
@@ -58,6 +60,7 @@ 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:

package/rules/figure-reference-order.yaml

@@ -1,6 +1,6 @@
 id: figure-reference-order
 layer: L3
-status: experimental
+status: stable
 how_to_find: figure-order
 severity: info
 
@@ -34,6 +34,11 @@ how_to_fix:
 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:
@@ -81,6 +86,7 @@ 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:

package/rules/footnote-mismatch.yaml

@@ -0,0 +1,91 @@
+id: footnote-mismatch
+layer: L3
+status: stable
+how_to_find: footnote-mismatch
+severity: warning
+
+name:
+  ja: 注の無い注の印と、印の無い注
+  en: A note mark with no note, or a note nothing points to
+
+why:
+  ja: 本文に「※3」や「[^3]」と書いたのに注3が無ければ、読み手は探しても見つからない注を探します。逆に、本文のどこも指さない注は、どの語の注か分かりません。注を消したり番号を振り直したりして、印と注の片方だけが残ったときに起きます。印と注の番号を突き合わせれば、機械で言えます。
+  en: When the text says "[^3]" or "※3" and there is no note 3, the reader looks for a note that is not there; a note nothing points to cannot be tied to any word. It happens when a note is deleted or the notes are renumbered and only one side is changed. Matching the marks against the notes' numbers is mechanical.
+
+message:
+  ja: 「{label}」の注がありません
+  en: 'There is no note for "{label}"'
+
+messages:
+  missing:
+    ja: 「{label}」の注がありません
+    en: 'There is no note for "{label}"'
+  unused:
+    ja: 注「{label}」を本文のどこも指していません
+    en: 'Nothing in the text points to the note "{label}"'
+
+how_to_fix:
+  ja: 注を足すか、印を消してください。注を振り直したなら、本文の印も同じ番号に直します。
+  en: Add the note or remove the mark. If the notes were renumbered, renumber the marks to match.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 本文の「※3」「[^3]」に対応する注が無い所と、本文のどこも指さない注
+  en: A note mark ("[^3]", "※3") with no note, or a note that nothing in the text points to
+example:
+  ja:
+    before: |
+      営業運行※1を開始し、料金※2は無料です。
+
+      ※1 特定の走行環境条件での運行
+    after: |
+      営業運行※1を開始し、料金※2は無料です。
+
+      ※1 特定の走行環境条件での運行
+      ※2 実証期間中に限ります
+  en:
+    before: |
+      The pilot starts in May[^1] and is free[^2].
+
+      [^1]: On weekdays only.
+    after: |
+      The pilot starts in May[^1] and is free[^2].
+
+      [^1]: On weekdays only.
+      [^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.
+
+rewrite:
+  ja:
+    direction: 印と注の番号を突き合わせ、注の無い印には注を足すか印を消し、どこからも指されない注には印を足すか注を消してください。
+    pairs:
+      - before: 料金※2は無料です。（注は ※1 だけ）
+        after: 料金※2は無料です。（※2 実証期間中に限ります、を足す）
+      - before: 本文に ※3 が無いのに「※3 予約が必要です」の注がある
+        after: 予約の要る語に ※3 を付ける
+    keep:
+      - 注の中身
+      - ほかの注の番号
+    avoid:
+      - 書き手が知らない注の中身を作る
+      - 印だけを消して、注が要る内容を本文から落とす
+  en:
+    direction: Match the marks against the notes. Add the missing note or remove its mark; for a note nothing points to, add the mark where it belongs or remove the note.
+    pairs:
+      - before: The pilot is free[^2]. (only [^1] is defined)
+        after: 'The pilot is free[^2]. (adds "[^2]: During the trial period.")'
+      - before: '"[^3]: Booking required." with no [^3] in the text'
+        after: '"Booking is required[^3]." where the note belongs'
+    keep:
+      - what each note says
+      - the numbers of the other notes
+    avoid:
+      - inventing what a note says
+      - removing a mark and with it a qualification the text needs

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-end-punctuation-mix.yaml

@@ -0,0 +1,158 @@
+id: heading-end-punctuation-mix
+layer: L1
+status: stable
+how_to_find: heading-end-punctuation
+word_list: heading-end-word
+requires: [markdown]
+severity: info
+
+name:
+  ja: 見出しの終わりの記号が揃っていない
+  en: Heading end punctuation mixed
+
+why:
+  ja: ほとんどの見出しが「手順」「注意点」のように記号なしで終わるのに、一つだけ「準備：」「確認。」と記号で終わっていたり、その逆だったりすると、読み手はその見出しだけ別の扱いなのかと迷い、目次でも浮いて見えます。直し忘れや、別の文書から貼った見出しによく出る形です。どちらの書き方が正しいかは決めず、同じ深さの見出しのうち少ないほうを指します。深さごとに比べるので、一段深い見出しをすべて「任意：」のような札にする書き方は指しません。
+  en: When most headings end bare ("Setup", "Notes") and one ends with a colon or a full stop ("Prerequisites:", "Checks."), or the other way round, the reader wonders whether that heading is meant to be different, and it stands out in the table of contents. It is usually a heading pasted from elsewhere or not yet tidied. chaff does not pick a style; it points at the smaller side among headings of the same depth. Depths are compared apart, so a depth whose headings are all labels ("Optional:") is not reported.
+
+message:
+  ja: 見出し「{heading}」の終わりの記号が、ほかの見出し（「{example}」など {count} 個）と違います
+  en: 'The heading "{heading}" ends differently from the other headings ("{example}" and {count} in all)'
+messages:
+  marked:
+    ja: 見出し「{heading}」だけ「{mark}」で終わっています（ほかの見出しは「{example}」など {count} 個が「：」「。」なしで終わる）
+    en: 'The heading "{heading}" ends with "{mark}", while {count} other headings end bare ("{example}")'
+  bare:
+    ja: 見出し「{heading}」だけ「：」「。」なしで終わっています（ほかの見出しは「{example}」など {count} 個が記号で終わる）
+    en: 'The heading "{heading}" ends bare, while {count} other headings end with a mark ("{example}")'
+
+how_to_fix:
+  ja: 見出しの終わりを、多いほうの書き方に揃えてください。記号なしの見出しが多ければ「：」や「。」を外します。
+  en: End the heading the way most headings end. If most end bare, drop the colon or the full stop.
+
+placeholders:
+  heading:
+    ja: 見出し
+    en: the heading
+  mark:
+    ja: 記号
+    en: the mark
+  example:
+    ja: ほかの見出し
+    en: another heading
+  count:
+    ja: 〇
+    en: N
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: consistency
+summary:
+  ja: 記号なしの見出しの中に「準備：」「確認。」のように記号で終わる見出しが混ざっている所（またはその逆）
+  en: A heading ending with a colon or a full stop among headings that end bare, or the other way round
+example:
+  ja:
+    before: |
+      # 作業の手引き
+
+      ## 準備
+
+      道具をそろえます。
+
+      ## 手順
+
+      順に進めます。
+
+      ## 確認：
+
+      結果を見ます。
+
+      ## 片付け
+
+      元に戻します。
+    after: |
+      # 作業の手引き
+
+      ## 準備
+
+      道具をそろえます。
+
+      ## 手順
+
+      順に進めます。
+
+      ## 確認
+
+      結果を見ます。
+
+      ## 片付け
+
+      元に戻します。
+  en:
+    before: |
+      # Working guide
+
+      ## Preparation
+
+      Gather the tools.
+
+      ## Steps
+
+      Work through them in order.
+
+      ## Checks:
+
+      Look at the result.
+
+      ## Cleanup
+
+      Put everything back.
+    after: |
+      # Working guide
+
+      ## Preparation
+
+      Gather the tools.
+
+      ## Steps
+
+      Work through them in order.
+
+      ## Checks
+
+      Look at the result.
+
+      ## Cleanup
+
+      Put everything back.
+
+not_flagged:
+  ja: 文書の題（最初の一つだけの一番上の見出し）は比べません。同じ深さの見出しが四つ未満の所、記号で終わる見出しと終わらない見出しが同じくらいある文書（少ないほうが四分の一を超える）は指しません。疑問符・感嘆符で終わる見出しは、記号なしと数えます。「…」や「etc.」「Inc.」のように言葉の一部の点で終わる見出しは比べません（点で終わる略語は言語ごとの語彙表にあります）。
+  en: The page title (a single top-level heading that opens the document) is not compared. Fewer than four headings at one depth, or where both ways are common (the smaller side above a quarter), is not reported. A heading ending with a question mark or an exclamation mark counts as bare. A heading ending with a full stop that is part of the words ("…", "etc.", "Inc.") is left out of the comparison; the abbreviations are in each language's lexicon.
+rewrite:
+  depth: light
+  ja:
+    direction: 見出しの終わりを、文書の多くの見出しと同じ書き方にしてください。記号を足すか外すだけで、見出しの言葉は変えません。
+    pairs:
+      - before: 「## 準備」「## 手順」「## 確認：」
+        after: 「## 準備」「## 手順」「## 確認」
+      - before: 「## 背景。」「## 方針。」「## 課題」
+        after: 「## 背景。」「## 方針。」「## 課題。」
+    keep:
+      - 見出しの言葉と深さ
+    avoid:
+      - 少ないほうに合わせて、ほかの見出しをすべて書き換える
+      - 見出しを文に書き直す
+  en:
+    direction: End the heading the way most of the document's headings end. Only add or drop the mark; keep the heading's words.
+    pairs:
+      - before: '"## Preparation", "## Steps", "## Checks:"'
+        after: '"## Preparation", "## Steps", "## Checks"'
+      - before: '"## Background.", "## Plan.", "## Risks"'
+        after: '"## Background.", "## Plan.", "## Risks."'
+    keep:
+      - the heading's words and depth
+    avoid:
+      - rewriting every other heading to match the odd one
+      - turning the heading into a sentence

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

@@ -1,9 +1,9 @@
 id: heading-numbering-mix
 layer: L1
-status: experimental
+status: stable
 how_to_find: heading-numbering
 requires: [markdown]
-severity: warning
+severity: info
 
 name:
   ja: 見出しの番号の付け方が揃っていない
@@ -42,7 +42,7 @@ placeholders:
     ja: 〇
     en: N
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
@@ -114,6 +114,7 @@ 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:

package/rules/hiragana-fukushi.yaml

@@ -1,6 +1,6 @@
 id: hiragana-fukushi
 layer: L3
-status: experimental
+status: stable
 how_to_find: phrase-match
 word_list: hiragana-fukushi
 uses: [pos]
@@ -26,6 +26,9 @@ how_to_fix:
 levels: { strict: 1, normal: 1, relaxed: 3 }
 
 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."
 
 group: readability
 summary:

package/rules/homophone-slip.yaml

@@ -1,6 +1,6 @@
 id: homophone-slip
 layer: L2
-status: experimental
+status: stable
 how_to_find: phrase-match
 word_list: homophone-slip
 requires: [pos]
@@ -26,6 +26,9 @@ how_to_fix:
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: 'A narrator and a character speak as they speak: dialect ("would of"), "So," and hearsay are the voice.'
+  speech: "A transcript keeps the speaker's words: hedges and ら dropped as spoken."
 
 group: slips
 summary:
@@ -45,6 +48,7 @@ level_meaning:
   ja: 取り違えが {limit} 箇所あれば指摘
   en: reported once there are {limit}
 rewrite:
+  depth: light
   en:
     direction: Correct only the confused word, to the form the lexicon gives.
     pairs: