chaffjs 0.20.0 → 0.22.0

package/rules/shell-prompt-mix.yaml

@@ -0,0 +1,128 @@
+id: shell-prompt-mix
+layer: L1
+status: stable
+how_to_find: shell-prompt
+requires: [markdown]
+severity: info
+
+name:
+  ja: シェルのコマンドにプロンプトを付けたり付けなかったりしている
+  en: Shell commands with and without a prompt
+
+why:
+  ja: 「$ npm install」と「npm install」が一つの文書に混ざっていると、読み手は「$」まで打つのか迷い、コピーしたコマンドが動かないこともあります。シェルのブロック（```bash、```console）のうち、全部の行にプロンプト（$）を付けたブロックと、一つも付けないブロックを比べ、少ないほうを指します。出力と一緒に書いたブロック（プロンプトのある行と無い行が混ざる）は見ません。どちらに揃えるかは決めません。
+  en: 'When "$ npm install" and "npm install" both appear in one document, the reader wonders whether to type the "$", and a copied command may fail. chaff compares shell blocks (```bash, ```console) whose every line has a prompt ($) with those where no line has one, and points at the fewer. A block that shows a command with its output (some lines prompted, some not) is not read. Which way is right is not decided.'
+
+message:
+  ja: このブロックだけ、コマンドへのプロンプト（$）の付け方がほかと違います（ほかの {majority} ブロック）
+  en: This block writes its commands with a prompt ($) differently from the other {majority} blocks
+
+how_to_fix:
+  ja: 多いほうに揃えてください。コピーして使うコマンドなら、プロンプトを付けないほうが打ち間違えません。
+  en: Match the majority. For commands meant to be copied, leaving the prompt out avoids pasting it.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+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: consistency
+summary:
+  ja: シェルのブロックで、「$」のプロンプトを付けたコマンドと付けないコマンドが混ざっている所
+  en: Shell blocks that write commands with a "$" prompt in some places and without it in others
+example:
+  ja:
+    config: { genre: docs/manual }
+    before: |
+      # 使い方
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      $ npx chaffjs README.md
+      ```
+    after: |
+      # 使い方
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      npx chaffjs README.md
+      ```
+  en:
+    config: { genre: docs/manual }
+    before: |
+      # Usage
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      $ npx chaffjs README.md
+      ```
+    after: |
+      # Usage
+
+      ```bash
+      npm install chaffjs
+      ```
+
+      ```bash
+      npx chaffjs init
+      ```
+
+      ```bash
+      npx chaffjs README.md
+      ```
+
+not_flagged:
+  ja: シェル以外の言語のブロック、言語名の無いブロック、コマンドと出力を一緒に書いたブロック、コメント（#）の行は見ません。少ないほうが {limit} ブロックを超えるときは使い分けとみなします。
+  en: Blocks in other languages or without a language, blocks that show a command with its output, and comment lines (#) are not read. When the fewer kind is more than {limit} blocks, it is taken as a choice.
+level_meaning:
+  ja: 少ないほうの書き方が {limit} ブロック以下のとき指摘
+  en: reported when the fewer style appears in {limit} blocks or fewer
+rewrite:
+  depth: light
+  ja:
+    direction: 指されたブロックのプロンプトを、文書の多いほうに揃えてください。付けない側に揃えるなら行の頭の「$ 」を消し、付ける側なら足します。コマンドそのものは変えません。
+    pairs:
+      - before: "$ npx chaffjs README.md"
+        after: "npx chaffjs README.md"
+      - before: "npm test"
+        after: "$ npm test"
+    keep:
+      - コマンドと引数
+    avoid:
+      - 出力の行にプロンプトを付ける
+  en:
+    direction: Bring the block's prompts in line with the document's majority. Toward no prompt, remove the "$ " at the start of each line; toward a prompt, add it. Leave the commands themselves unchanged.
+    pairs:
+      - before: "$ npx chaffjs README.md"
+        after: "npx chaffjs README.md"
+      - before: "npm test"
+        after: "$ npm test"
+    keep:
+      - the commands and their arguments
+    avoid:
+      - putting a prompt before an output line

package/rules/space-before-punctuation.yaml

@@ -1,6 +1,6 @@
 id: space-before-punctuation
 layer: L1
-status: experimental
+status: stable
 how_to_find: space-before-punctuation
 languages: [en]
 severity: warning

package/rules/spelling-consistency.yaml

@@ -1,6 +1,6 @@
 id: spelling-consistency
 layer: L3
-status: experimental
+status: stable
 how_to_find: spelling-variety
 word_list: spelling-variant
 extra_word_lists: [spelling-ize]
@@ -27,6 +27,8 @@ how_to_fix:
 levels: { strict: 49, normal: 34, relaxed: 20 }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "A narrator may hedge, speak with ら dropped, and spell as the work's time and place did."
 
 group: consistency
 summary:

package/rules/step-reference-missing.yaml

@@ -0,0 +1,85 @@
+id: step-reference-missing
+layer: L3
+status: stable
+how_to_find: step-reference
+severity: warning
+
+name:
+  ja: 無い手順を指す参照
+  en: A reference to a step that does not exist
+
+why:
+  ja: 「手順5を参照」と書いたのに手順が4つしか無ければ、読み手は手順5を探して手を止めます。手順を減らしたり並べ替えたりしたあとに、本文の参照だけが古い番号のまま残ると起きます。手順の番号と参照の番号を突き合わせれば、機械で言えます。
+  en: When the text says "see step 5" and there are only four steps, the reader stops to look for step 5. It happens when steps are removed or reordered and a reference keeps the old number. Matching the references against the steps' numbers is mechanical.
+
+message:
+  ja: 「{label}」を指していますが、手順は {last} までです
+  en: '"{label}" is referred to, but the steps end at {last}'
+
+how_to_fix:
+  ja: 指したい手順の番号を確かめて、参照を直してください。手順を消したのなら、参照の文も直します。
+  en: Check which step is meant and correct the reference. If the step was removed, rewrite the sentence that refers to it.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 「手順5を参照」のように、文書の手順の最後の番号を超える手順を指す参照
+  en: A reference such as "see step 5" past the last step the document has
+example:
+  ja:
+    before: |
+      1. アプリを開きます。
+      2. 設定を選びます。
+      3. 保存します。
+
+      うまくいかないときは、手順4からやり直してください。
+    after: |
+      1. アプリを開きます。
+      2. 設定を選びます。
+      3. 保存します。
+
+      うまくいかないときは、手順2からやり直してください。
+  en:
+    before: |
+      1. Open the app.
+      2. Choose Settings.
+      3. Save.
+
+      If it fails, start again from step 4.
+    after: |
+      1. Open the app.
+      2. Choose Settings.
+      3. Save.
+
+      If it fails, start again from step 2.
+
+not_flagged:
+  ja: 手順は、手順の語（手順、ステップ、Step）と番号で始まる見出しと、番号付きの箇条書きの項目です。手順が一つも無い文書の参照は、ほかの文書の手順かもしれないので言いません。番号付きの箇条書きがいくつかあれば、いちばん大きい番号を超える参照だけを言います。コードの中は読みません。
+  en: Steps are headings that start with a step word and a number (Step 3) and the items of numbered lists. In a document with no steps at all, a reference may be to another document's steps and is not reported. With several numbered lists, only a reference past the largest number is reported. Code is not read.
+
+rewrite:
+  ja:
+    direction: 指したい手順を確かめ、参照の番号を文書の手順の番号に合わせてください。手順を消したのなら、参照する文を直すか消します。
+    pairs:
+      - before: うまくいかないときは、手順4からやり直してください。（手順は3まで）
+        after: うまくいかないときは、手順2からやり直してください。
+      - before: 詳しくはステップ6を参照してください。（ステップは5まで）
+        after: 詳しくはステップ5を参照してください。
+    keep:
+      - 手順の中身と順番
+    avoid:
+      - どの手順を指すか確かめずに、最後の番号に直す
+  en:
+    direction: Find out which step is meant and correct the reference's number. If the step was removed, rewrite or remove the sentence that refers to it.
+    pairs:
+      - before: If it fails, start again from step 4. (three steps)
+        after: If it fails, start again from step 2.
+      - before: See Step 6 for the details. (five steps)
+        after: See Step 5 for the details.
+    keep:
+      - the steps and their order
+    avoid:
+      - changing the reference to the last step without checking which was meant

package/rules/step-statement-mix.yaml

@@ -0,0 +1,76 @@
+id: step-statement-mix
+layer: L3
+status: stable
+how_to_find: step-statement
+languages: [en]
+requires: [pos]
+severity: info
+
+name:
+  ja: 手順の中に、指示でなく説明の文の手順がある
+  en: A step written as a statement among instructions
+
+why:
+  ja: 番号を振った手順は、読み手がそのとおりに手を動かす指示です。「Open the app.」「Run the installer.」の中に「The installer asks for a password.」のような説明の文が混ざると、読み手はそれも自分のすることかと迷います。英語の番号付きの箇条書きで、主語と動詞で始まる項目（The installer asks、You click）が、動詞で始まる指示の項目より少ないとき、少ないほうを指します。日本語の手順の文末（〜します／〜してください と それ以外）は no-mixed-desumasu と list-item-form-mix が見るので、この rule は英語だけです。
+  en: 'A numbered procedure is a list of things for the reader to do. When "The installer asks for a password." sits among "Open the app." and "Run the installer.", the reader wonders whether that is a step to take too. In an English numbered list, chaff points at the few items that open with a subject and a verb (The installer asks, You click) among items that open with the verb. Japanese step endings (〜します / 〜してください against the rest) are checked by no-mixed-desumasu and list-item-form-mix, so this rule is for English only.'
+
+message:
+  ja: この手順は、ほかの {count} 個の指示と違い、主語で始まる説明の文です
+  en: This step is a statement that opens with its subject, unlike the other {count} instructions
+
+how_to_fix:
+  ja: 読み手のすることを命令の形で書いてください。結果の説明なら、前の手順の後ろの文にするか、手順の外に出します。
+  en: Write what the reader does, as an instruction. If it describes a result, make it a second sentence of the step before, or move it out of the list.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+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: consistency
+summary:
+  ja: 英語の番号付きの手順で、命令の形の項目の中に、主語で始まる説明の項目が混ざっている所
+  en: A numbered procedure that mixes a statement (The installer asks) into instructions (Run the installer)
+example:
+  en:
+    config: { genre: docs/manual }
+    before: |
+      # Install
+
+      1. Open the terminal on your computer.
+      2. Run the installer from the downloads folder.
+      3. The installer asks for your password.
+      4. Restart the computer when it finishes.
+    after: |
+      # Install
+
+      1. Open the terminal on your computer.
+      2. Run the installer from the downloads folder.
+      3. Type your password when the installer asks for it.
+      4. Restart the computer when it finishes.
+
+not_flagged:
+  ja: "番号の無い箇条書き、三つに満たない手順、指示が半分に満たない番号付きの箇条書き（用語と説明の一覧など）、短い項目（「Setup」）、動詞の前に札や前置きのある項目（「Guests: …」「On the left bar, select …」）、主語で始まる項目が {limit} 個を超えるか指示より多い手順は見ません。項目の最初の行の最初の文だけを見ます。"
+  en: 'Bulleted lists, procedures of fewer than three steps, numbered lists where instructions are half or fewer (a list of terms, say), short items ("Setup"), items with a label or an opening phrase before the verb ("Guests: …", "On the left bar, select …"), and procedures where statements are more than {limit} or not fewer than the instructions are not reported. Only the first sentence on each item''s own line is read.'
+level_meaning:
+  ja: 説明の項目が {limit} 個以下で、指示の項目より少ないとき指摘
+  en: reported when {limit} or fewer steps are statements and they are fewer than the instructions
+rewrite:
+  depth: light
+  en:
+    direction: Turn the statement into an instruction for the reader, with the verb first, or fold it into the step before as a second sentence. Keep what the step says happens; do not add steps.
+    pairs:
+      - before: 3. The installer asks for your password.
+        after: 3. Type your password when the installer asks for it.
+      - before: 2. You click Save to keep the file.
+        after: 2. Click Save to keep the file.
+    keep:
+      - the order of the steps
+      - the names of buttons, files and commands
+    avoid:
+      - adding a step the text does not have
+      - merging two steps the reader does separately

package/rules/stock-transition.yaml

@@ -1,6 +1,6 @@
 id: stock-transition
 layer: L2
-status: experimental
+status: stable
 how_to_find: stock-transition
 word_list: stock-transition
 uses: [pos]
@@ -28,6 +28,12 @@ levels:
   en: { strict: 4, normal: 6, relaxed: 10 }
 
 use_for: [technical/readme, 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: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 
 group: ai-tells
 summary:
@@ -54,6 +60,7 @@ level_meaning:
   ja: 決まった接ぎで始まる文が 1000 字あたり {limit} 個まで
   en: up to {limit} sentences per 1000 words opening with a stock transition
 rewrite:
+  depth: light
   ja:
     direction: 文頭の接ぎの語を消して読み返してください。繋がりが分からなくなる所だけ、前の文との関係（理由、例外、順番）を言葉で書きます。
     pairs:

package/rules/stray-space.yaml

@@ -1,11 +1,11 @@
 id: stray-space
 layer: L3
-status: experimental
+status: stable
 how_to_find: stray-space
 # どの境目が一続きの語句の中かは、語の品詞で決める。品詞が無ければ動かない。
 requires: [pos]
 languages: [ja]
-severity: warning
+severity: info
 
 name:
   ja: 語句の途中に空白がある

package/rules/summary-fact-mismatch.yaml

@@ -1,6 +1,6 @@
 id: summary-fact-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: summary-fact-mismatch
 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:
@@ -70,6 +72,7 @@ not_flagged:
   ja: 本文に同じ項目の値が二通り以上あるとき（回ごと、対象ごとの値）は、要約がどれと合うべきか決まらないので言いません。単位の違う値、条件の付いた値（「3,000円から」）も比べません。
   en: When the body gives the item more than one value (per session, per group), which one the summary should match is not settled, so nothing is said. Values in different units and values with a condition ("from $300") are not compared.
 rewrite:
+  depth: light
   ja:
     direction: 要約と本文のどちらの値が正しいかを書き手に確かめ、もう一方を直してください。要約の値を本文から写すときは、単位と条件も一緒に写します。
     pairs:

package/rules/table-header-variant.yaml

@@ -1,6 +1,6 @@
 id: table-header-variant
 layer: L2
-status: experimental
+status: stable
 how_to_find: table-header-variant
 requires: [markdown]
 severity: info
@@ -76,6 +76,7 @@ level_meaning:
   ja: 少ないほうの書き方が、その見出しの {limit}% 以下のとき指摘
   en: reported when the less common spelling is {limit}% of the header's uses or less
 rewrite:
+  depth: light
   ja:
     direction: 同じ欄の見出しを、文書の中で多いほうの書き方にそろえてください。表の中身と並びは変えません。
     pairs:

package/rules/table-row-overflow.yaml

@@ -0,0 +1,90 @@
+id: table-row-overflow
+layer: L1
+status: stable
+how_to_find: table-row-overflow
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 表の行のセルが見出しの行より多い
+  en: Table row with more cells than the header
+
+why:
+  ja: Markdown の表（GFM）は、見出しの行にある列の数だけセルを表示し、それより多いセルは黙って捨てます。値の中に「|」を書いた、列を足したのに見出しを直していない、といったときに起き、書いたはずの値が読み手には見えません。
+  en: A Markdown table (GFM) shows only as many cells as its header row has, and silently drops the rest. It happens when a value holds a "|", or when a column was added to the rows but not to the header, and the reader never sees the value that was written.
+
+message:
+  ja: この行はセルが {cells} 個あり、見出しの行の {columns} 列を超えた分は表示されません
+  en: "This row has {cells} cells; past the header's {columns} columns they are not shown"
+
+how_to_fix:
+  ja: 見出しの行に列を足すか、行のセルを減らしてください。値の中の「|」は「\|」と書きます。
+  en: Add the column to the header row, or remove the extra cell. Write a "|" inside a value as "\|".
+
+placeholders:
+  cells:
+    ja: 〇
+    en: N
+  columns:
+    ja: 〇
+    en: N
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 見出しの行より多いセルを持つ表の行（多い分は表示されない）
+  en: A table row with more cells than the header row (the extra ones are not shown)
+example:
+  ja:
+    before: |
+      | 項目 | 金額 |
+      | --- | --- |
+      | 会場 | 5万円 |
+      | 飲食 | 3万円 | 予備費込み |
+    after: |
+      | 項目 | 金額 | 備考 |
+      | --- | --- | --- |
+      | 会場 | 5万円 | |
+      | 飲食 | 3万円 | 予備費込み |
+  en:
+    before: |
+      | Item | Cost |
+      | --- | --- |
+      | Venue | $500 |
+      | Food | $300 | includes reserve |
+    after: |
+      | Item | Cost | Note |
+      | --- | --- | --- |
+      | Venue | $500 | |
+      | Food | $300 | includes reserve |
+
+not_flagged:
+  ja: 見出しの行よりセルが少ない行（空のセルとして表示されます）、「\|」と書いた値、コードと引用の中の表は指しません。
+  en: A row with fewer cells than the header (shown as empty cells), a value written with "\|", and tables in code or quotations are not reported.
+rewrite:
+  depth: light
+  ja:
+    direction: 見出しの行と行のセルの数を揃えてください。多いセルが値なら見出しに列を足し、値の中の「|」なら「\|」にします。値は消しません。
+    pairs:
+      - before: 「| 飲食 | 3万円 | 予備費込み |」（見出しは 2 列）
+        after: 見出しに「備考」の列を足し、「| 飲食 | 3万円 | 予備費込み |」
+      - before: 「| 区切り | a | b |」（見出しは 2 列、値が「a | b」）
+        after: 「| 区切り | a \| b |」
+    keep:
+      - 行に書いた値
+    avoid:
+      - はみ出したセルの値を消す
+  en:
+    direction: Make the row and the header hold the same number of cells. If the extra cell is a value, add the column to the header; if it is a "|" inside a value, write it as "\|". Do not drop the value.
+    pairs:
+      - before: '"| Food | $300 | includes reserve |" (the header has 2 columns)'
+        after: 'a "Note" column added to the header, and "| Food | $300 | includes reserve |"'
+      - before: '"| Separator | a | b |" (the header has 2 columns; the value is "a | b")'
+        after: '"| Separator | a \| b |"'
+    keep:
+      - the values written in the row
+    avoid:
+      - deleting the value that spilled over

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

@@ -25,6 +25,11 @@ how_to_fix:
 levels: { strict: 2, normal: 4, relaxed: 8 }
 
 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."
+  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."
+  docs/glossary: "A reader looks up one entry and reads only that. A definition is a noun phrase (風の吹いてくる方向。), and sibling entries share one wording on purpose (Portion of labor productivity change attributed to …), which no reader sees twice."
+  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:
@@ -45,6 +50,7 @@ level_meaning:
   ja: 本文の体言止め {limit} 文まで
   en: up to {limit} noun-ending sentences in the body
 rewrite:
+  depth: light
   ja:
     direction: 本文で名詞で止めた文に、文書の文体に合わせた述語（です・ます、または、だ・である）を足してください。見出し、箇条書き、表はそのままにします。
     pairs:

package/rules/tari-unpaired.yaml

@@ -0,0 +1,58 @@
+id: tari-unpaired
+layer: L3
+status: stable
+how_to_find: unpaired-parallel
+word_list: paired-parallel
+requires: [pos]
+languages: [ja]
+severity: info
+
+name:
+  ja: 対にならない「〜たり」
+  en: A single 〜たり with no partner
+
+why:
+  ja: 「〜たり」は「〜たり〜たりする」と対で並べる言い方です。「本を読んだり、映画を見ます」のように一つで止めて次の述語へ続けると、並べたはずのもう一つが抜け、何と何を並べたのかが読み手に分かりません。一つだけで例を挙げる「遅れたりする」「遅れたりもする」は正しいので指しません。
+  en: In Japanese, 〜たり lists actions in pairs (〜たり〜たりする). Used once and followed by another clause ("本を読んだり、映画を見ます"), the second half of the pair is missing. A single 〜たり closed by する (遅れたりする), which gives one example, is correct and not reported.
+
+message:
+  ja: 「{word}」が一つだけで、対になる「〜たり」がありません
+  en: '"{word}" is used once, with no second 〜たり to pair with'
+
+how_to_fix:
+  ja: 後ろの述語にも「〜たり」を付けて「する」で閉じてください（読んだり、映画を見ます → 読んだり、映画を見たりします）。
+  en: Add 〜たり to the second verb as well and close with する.
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Spoken 全然大丈夫, なので and より in a character's voice; classical verse has a たり that does not list."
+
+group: wording
+summary:
+  ja: 「本を読んだり、映画を見ます」のように、「〜たり」が一つで止まって対になっていない所
+  en: A Japanese 〜たり used once and followed by another clause, so its pair is missing
+example:
+  ja:
+    before: |
+      休日は本を読んだり、映画を見ます。
+    after: |
+      休日は本を読んだり、映画を見たりします。
+
+not_flagged:
+  ja: 一文に「〜たり」が二つ以上ある文と、一つでも「する」「もする」で閉じた文（遅れたりする）は指しません。「一日たりとも」の「たり」は並べる「たり」ではないので見ません。鉤括弧で引いた中は見ません。
+  en: Sentences with two or more 〜たり, and a single 〜たり closed by する (遅れたりする), are not reported. Nor is the たり of 一日たりとも, which does not list, nor anything quoted in 「」.
+rewrite:
+  depth: light
+  ja:
+    direction: 抜けたもう一つの動作にも「〜たり」を付け、最後を「する」で閉じてください。並べるつもりが無ければ「〜たり」を外して「〜し、」でつなぎます。
+    pairs:
+      - before: 休日は本を読んだり、映画を見ます。
+        after: 休日は本を読んだり、映画を見たりします。
+      - before: 会議では資料を配ったり、意見を聞きました。
+        after: 会議では資料を配り、意見を聞きました。
+    keep:
+      - 並べた動作と、その順
+    avoid:
+      - 並べる動作を本文に無いもので足す

package/rules/teki-overuse.yaml

@@ -1,6 +1,6 @@
 id: teki-overuse
 layer: L3
-status: experimental
+status: stable
 how_to_find: sentence-word-count
 word_list: teki-suffix
 requires: [pos]
@@ -45,6 +45,7 @@ level_meaning:
   ja: 一文の「〜的」{limit} 個まで
   en: up to {limit} 〜的 words in a sentence
 rewrite:
+  depth: light
   ja:
     direction: 「〜的」を、本文にある具体的な事柄（数、期間、対象、やり方）に置き換えてください。本文に無ければ作らず、「〜的」を一つ残すか、書き手に聞きます。
     pairs:

package/rules/title-case-consistency.yaml

@@ -1,6 +1,6 @@
 id: title-case-consistency
 layer: L3
-status: experimental
+status: stable
 how_to_find: title-case-mix
 languages: [en]
 severity: info

package/rules/title-length.yaml

@@ -1,6 +1,6 @@
 id: title-length
 layer: L1
-status: experimental
+status: stable
 how_to_find: title-length
 requires: [markdown]
 severity: info
@@ -50,6 +50,11 @@ by_genre:
     en: { strict: 14, normal: 18, relaxed: 22 }
 
 use_for: [blog, business, technical, docs, academic, legal, literature, speech]
+off_for:
+  legal: "A statute or contract opens with its first article, and its titles are formal names."
+  literature: "A story or poem chooses its own opening and its own title."
+  speech: "An address or a transcript is titled by occasion (第221回国会における…演説) and opens as spoken."
+  docs/faq: "A question is the heading: its length is the reader's question, not a name to shorten."
 
 group: readability
 summary:
@@ -80,6 +85,7 @@ level_meaning:
   ja: 題や見出しが {limit} 文字を超えたら指摘
   en: reported when a title or heading runs past {limit} words
 rewrite:
+  depth: light
   ja:
     direction: 見出しを、その節が何かを言う名前だけに縮めてください。理由・条件・対象・日付は、見出しのすぐ下の最初の文に移します。
     pairs: