chaffjs 0.20.0 → 0.22.0

package/rules/toc-heading-mismatch.yaml

@@ -0,0 +1,136 @@
+id: toc-heading-mismatch
+layer: L3
+status: stable
+how_to_find: toc-heading
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 見出しの無い目次の項目
+  en: A table-of-contents entry with no heading
+
+why:
+  ja: 目次に「3.2 費用」とあるのに本文にその見出しが無ければ、読み手は目次から探しても行き着けません。見出しを書き換えたり節を消したりしたあとに、目次だけが古いまま残ると起きます。目次の項目と見出しの言葉を突き合わせれば、機械で言えます。
+  en: When the table of contents lists "3.2 Costs" and the text has no such heading, the reader cannot get there from the contents. It happens when a heading is renamed or a section removed and the contents are left as they were. Matching the entries against the headings is mechanical.
+
+message:
+  ja: 目次の「{entry}」に合う見出しがありません
+  en: 'No heading matches the contents entry "{entry}"'
+
+how_to_fix:
+  ja: 目次を見出しに合わせて直すか、消えた節の項目を目次から消してください。
+  en: Update the entry to match the heading, or remove the entry for a section that is gone.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 目次（「目次」「Contents」の見出しの下の箇条書き）の項目のうち、文書のどの見出しとも合わないもの
+  en: An entry of the table of contents (the list under a "Contents" heading) that matches no heading of the document
+example:
+  ja:
+    before: |
+      ## 目次
+
+      - 1 概要
+      - 2 費用
+      - 3 日程
+
+      ## 1 概要
+
+      本書の概要です。
+
+      ## 2 料金
+
+      料金の説明です。
+
+      ## 3 日程
+
+      日程の説明です。
+    after: |
+      ## 目次
+
+      - 1 概要
+      - 2 料金
+      - 3 日程
+
+      ## 1 概要
+
+      本書の概要です。
+
+      ## 2 料金
+
+      料金の説明です。
+
+      ## 3 日程
+
+      日程の説明です。
+  en:
+    before: |
+      ## Contents
+
+      - 1 Overview
+      - 2 Costs
+      - 3 Schedule
+
+      ## 1 Overview
+
+      An overview.
+
+      ## 2 Fees
+
+      The fees.
+
+      ## 3 Schedule
+
+      The schedule.
+    after: |
+      ## Contents
+
+      - 1 Overview
+      - 2 Fees
+      - 3 Schedule
+
+      ## 1 Overview
+
+      An overview.
+
+      ## 2 Fees
+
+      The fees.
+
+      ## 3 Schedule
+
+      The schedule.
+
+not_flagged:
+  ja: 項目と見出しは、空白・記号・大文字小文字を無視して比べ、頭の番号（1.2、2-1）と、ページ番号（…… 12）を外しても比べます。リンクの項目は字の部分を比べます（リンクの行き先は broken-link が見ます）。目次の項目の半分より多くが見出しに合わない文書は、本文と別の章立ての目次と読んで言いません。Markdown の見出しのある文書だけを見ます。
+  en: Entries and headings are compared ignoring spaces, punctuation and case, and again without a leading number (1.2, 2-1) or a page number (.... 12). For a linked entry the link text is compared (broken-link checks where it points). When more than half of the entries match no heading, the contents are read as following another outline and nothing is reported. Only Markdown documents with headings are checked.
+
+rewrite:
+  ja:
+    direction: 目次の項目を、本文の見出しの言葉と番号に合わせてください。節を消したのなら、その項目を目次から消します。
+    pairs:
+      - before: 目次の「2 費用」（見出しは「2 料金」）
+        after: 目次の「2 料金」
+      - before: 目次の「4 付録」（本文に付録の節が無い）
+        after: 目次から「4 付録」を消す
+    keep:
+      - 本文の見出し
+      - 目次の並び順
+    avoid:
+      - 目次に合わせて本文の見出しを書き換える
+  en:
+    direction: Make each contents entry match the heading's words and number. If a section was removed, remove its entry.
+    pairs:
+      - before: The contents entry "2 Costs" (the heading is "2 Fees")
+        after: The contents entry "2 Fees"
+      - before: The contents entry "4 Appendix" (no appendix in the text)
+        after: The entry "4 Appendix" removed
+    keep:
+      - the headings in the text
+      - the order of the contents
+    avoid:
+      - renaming a heading in the text to match the contents

package/rules/topic-predicate-distance.yaml

@@ -1,6 +1,6 @@
 id: topic-predicate-distance
 layer: L3
-status: experimental
+status: stable
 how_to_find: topic-predicate-distance
 requires: [pos]
 languages: [ja]
@@ -24,6 +24,10 @@ how_to_fix:
 
 levels: { strict: 60, normal: 80, relaxed: 100 }
 
+# 法令と契約は、主題の後に要件と例外を挟んでから述語を置く。既定の上限では group の文書の大半に出たので、測って上げた（spec §21.1）。
+by_genre:
+  legal: { strict: 160, normal: 200, relaxed: 260 }
+
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
 group: readability
@@ -44,6 +48,7 @@ level_meaning:
   ja: 主題から述語まで {limit} 字まで
   en: up to {limit} characters between the topic and the predicate
 rewrite:
+  depth: light
   ja:
     direction: 主題（〜は）を述語の近くに動かすか、主題と述語の間に挟んだ説明を前の文に出してください。
     pairs:

package/rules/total-mismatch.yaml

@@ -1,6 +1,6 @@
 id: total-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: total-mismatch
 requires: [quantities]
 severity: error
@@ -24,6 +24,8 @@ how_to_fix:
 levels: { normal: error, relaxed: warning }
 
 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."
 sources: [de-marneffe-2008]
 
 group: facts

package/rules/translationese-density.yaml

@@ -1,6 +1,6 @@
 id: translationese-density
 layer: L2
-status: experimental
+status: stable
 how_to_find: phrase-density
 word_list: translationese
 uses: [pos]
@@ -27,6 +27,8 @@ how_to_fix:
 levels: { strict: 0, normal: 1, relaxed: 2 }
 
 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: ai-tells
 summary:
@@ -47,6 +49,7 @@ level_meaning:
   ja: 1000 字あたり翻訳調の言い回し {limit} 個まで
   en: up to {limit} translated phrasings per 1000 characters
 rewrite:
+  depth: light
   ja:
     direction: 英語の構文を写した言い回しを、日本語として素直な言い方に直してください。語彙表の語ごとの書き換え（〜を可能にする → 〜ができる）に従い、主語の「あなたは」「彼女は」は省くか名前で呼びます。書いてある事実は変えません。
     pairs:

package/rules/unbalanced-bracket.yaml

@@ -1,8 +1,8 @@
 id: unbalanced-bracket
 layer: L1
-status: experimental
+status: stable
 how_to_find: unbalanced-bracket
-severity: warning
+severity: info
 
 name:
   ja: 括弧が組になっていない
@@ -31,7 +31,7 @@ how_to_fix:
   ja: 足りない括弧を足すか、余分な括弧を消してください。全角と半角は、開きと閉じをそろえてください。
   en: Add the missing bracket or remove the extra one. Make the opening and closing marks the same width.
 
-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/unclosed-code-fence.yaml

@@ -0,0 +1,107 @@
+id: unclosed-code-fence
+layer: L1
+status: stable
+how_to_find: unclosed-code-fence
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 閉じていないコードブロック
+  en: Unclosed code fence
+
+why:
+  ja: 「```」で始めたコードブロックを閉じ忘れると、Markdown は文書の終わり（リストの項目の中ならその項目の終わり）までをすべてコードとして表示します。後ろの見出しも本文も等幅の字の塊になり、読み手には文書が壊れて見えます。
+  en: A code block opened with "```" and never closed runs to the end of the document (or of the list item it is in), so Markdown shows everything after it as code. The headings and text that follow turn into one block of monospaced text, and the document looks broken.
+
+message:
+  ja: 「{fence}」で始めたコードブロックが閉じていません
+  en: 'The code block opened with "{fence}" is never closed'
+
+how_to_fix:
+  ja: コードの終わりに、始めと同じ記号を同じ数以上並べた行（「```」）を足してください。
+  en: Add a line after the code with the same character, at least as many ("```").
+
+placeholders:
+  fence:
+    ja: 記号
+    en: the fence
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 「```」で始めたまま閉じていないコードブロック（後ろがすべてコードになる）
+  en: A code block opened with "```" and never closed (everything after it shows as code)
+example:
+  ja:
+    before: |
+      手順は次のとおりです。
+
+      ```sh
+      npm install
+
+      ## 確認
+
+      動くことを確かめます。
+    after: |
+      手順は次のとおりです。
+
+      ```sh
+      npm install
+      ```
+
+      ## 確認
+
+      動くことを確かめます。
+  en:
+    before: |
+      Install it first.
+
+      ```sh
+      npm install
+
+      ## Check
+
+      Make sure it runs.
+    after: |
+      Install it first.
+
+      ```sh
+      npm install
+      ```
+
+      ## Check
+
+      Make sure it runs.
+
+not_flagged:
+  ja: 閉じたコードブロック、字下げで書いたコードブロック、引用の中のコードブロックは指しません。
+  en: A closed code block, an indented code block, and a code block in a quotation are not reported.
+rewrite:
+  depth: light
+  ja:
+    direction: コードの終わりに閉じる行（「```」）を足してください。どこまでがコードかは、コマンドや出力の並びの終わりで決めます。コードの中身は変えません。
+    pairs:
+      - before: 「```sh」「npm install」「## 確認」
+        after: 「```sh」「npm install」「```」「## 確認」
+      - before: 「~~~」「SELECT 1;」のまま文書が終わる
+        after: 「~~~」「SELECT 1;」「~~~」
+    keep:
+      - コードの中身
+      - 始めの行の言語名
+    avoid:
+      - 後ろの本文までコードの中に入れる
+  en:
+    direction: Add a closing line ("```") where the code ends; the code ends where the commands or the output stop. Keep the code as it is.
+    pairs:
+      - before: '"```sh", "npm install", "## Check"'
+        after: '"```sh", "npm install", "```", "## Check"'
+      - before: 'the document ends after "~~~" and "SELECT 1;"'
+        after: '"~~~", "SELECT 1;", "~~~"'
+    keep:
+      - the code
+      - the language name on the opening line
+    avoid:
+      - putting the text after it inside the code block

package/rules/uncomparable-graded.yaml

@@ -0,0 +1,65 @@
+id: uncomparable-graded
+layer: L2
+status: stable
+how_to_find: phrase-match
+word_list: uncomparable-graded
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 比べられない形容詞に付けた程度
+  en: An uncomparable adjective given a degree
+
+why:
+  ja: 英語の「unique」「unanimous」「impossible」は、そうであるかないかの二つしかない状態を言います。「very unique」「more unanimous」と程度を付けても何も足されず、読み手は書き手が語の意味を確かめていないと受け取ります。語の一覧は言語ごとの語彙表にあります。
+  en: '"Unique", "unanimous" and "impossible" name a state that holds or does not. "Very unique" or "more unanimous" adds nothing, and tells the reader the writer did not weigh the word. The phrases are listed in the lexicon.'
+
+message:
+  ja: 「{matched}」は、程度の無い形容詞に程度を付けています
+  en: '"{matched}" grades an adjective that has no degrees'
+
+how_to_fix:
+  ja: 程度の語を外すか、本当に言いたい程度の言える語に替えてください（very unique → unique、または unusual）。
+  en: Drop the grade, or use a word that has degrees ("very unique" → "unique", or "unusual").
+
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: 'A narrator or a character may say "very unique"; the voice is the author''s choice.'
+
+group: wording
+summary:
+  ja: 英語で、「very unique」「more unanimous」のように、程度の無い形容詞に付けた程度
+  en: A degree given to an adjective that has none, such as "very unique" or "more unanimous"
+example:
+  en:
+    before: |
+      The design is very unique.
+    after: |
+      The design is unusual.
+
+not_flagged:
+  ja: 一覧にある組み合わせだけを見ます。「almost」「nearly」のように近さを言う語（almost unique、nearly impossible）は指しません。英語の文書だけで動き、文学のジャンルは対象にしません。
+  en: Only the pairs on chaff's list are checked. Words that say how close ("almost unique", "nearly impossible") are not reported. English documents only; literature is not checked.
+level_meaning:
+  ja: 当てはまる言い回しが {limit} 箇所あれば指摘
+  en: reported once there are {limit}
+sources: [proselint]
+rewrite:
+  depth: light
+  en:
+    direction: Drop the grade before the adjective, or swap the adjective for one that has degrees when a degree is meant. Change nothing else in the sentence.
+    pairs:
+      - before: The design is very unique.
+        after: The design is unusual.
+      - before: The vote was more unanimous than last year.
+        after: The vote was unanimous this year.
+      - before: A fix before Friday is extremely impossible.
+        after: A fix before Friday is impossible.
+    keep:
+      - the claim the sentence makes
+      - the rest of the sentence
+    avoid:
+      - adding a new grade ("truly unique") in place of the old one

package/rules/undefined-acronym.yaml

@@ -1,6 +1,6 @@
 id: undefined-acronym
 layer: L1
-status: experimental
+status: stable
 how_to_find: undefined-acronym
 word_list: common-acronym
 extra_word_lists:
@@ -40,7 +40,14 @@ how_to_fix:
 
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
+# 技術文書の読み手は、分野の略語を知っている。既定の数では group の文書の過半に出たので、測って上げた（spec §21.1）。
+by_genre:
+  technical: { strict: 3, normal: 5, relaxed: 8 }
+
 use_for: [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."
 sources: [plain-2011, jis-z8301-2019]
 
 group: readability

package/rules/unfilled-placeholder.yaml

@@ -1,6 +1,6 @@
 id: unfilled-placeholder
 layer: L2
-status: experimental
+status: stable
 how_to_find: unfilled-placeholder
 word_list: placeholder-word
 severity: warning

package/rules/unit-mismatch.yaml

@@ -1,6 +1,6 @@
 id: unit-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: unit-mismatch
 requires: [quantities]
 uses: [pos]
@@ -58,6 +58,7 @@ not_flagged:
   ja: 単位が同じ量（食い違いは fact-conflict が見ます）、種類の違う量（長さと重さ）、違う見出しや違う親の項目の下の量、2% までの差は見ません。GB や MB は 1000 倍でも 1024 倍でも合えば合うとみなします。
   en: Values in the same unit (fact-conflict looks at those), of different kinds (a length and a mass), under different headings or parent items, and differences within 2% are left alone. GB and MB agree when they match at either 1000 or 1024.
 rewrite:
+  depth: light
   ja:
     direction: 二つの量のどちらが正しいかを書き手に確かめ、もう一方を換算して直してください。どちらが正しいか文書から決まらないときは、推測で選ばずに書き手に聞いてください。
     pairs:

package/rules/unknown-word.yaml

@@ -1,6 +1,6 @@
 id: unknown-word
 layer: L2
-status: experimental
+status: stable
 how_to_find: unknown-word
 languages: [en]
 severity: info
@@ -32,6 +32,8 @@ placeholders:
 levels: { strict: warning, normal: info, relaxed: info }
 
 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: slips
 summary:
@@ -48,6 +50,7 @@ not_flagged:
   ja: 大文字を含む語、四字より短い語、コード・URL・メールアドレスの中の語、文書で二度以上使う語、一字違いの辞書の語が無い語、chaff.yaml の names に並べた語、語彙表 known-misspelling が別に言う語は指しません。
   en: Words with a capital letter, words shorter than four letters, words in code, URLs and email addresses, words used twice or more in the document, words with no dictionary word one letter away, words listed under names in chaff.yaml, and the misspellings known-misspelling reports are not reported.
 rewrite:
+  depth: light
   en:
     direction: If the flagged word is a typo, replace it with the suggested dictionary word, or another word the sentence means. If it is a real word or a name, leave it and add it to names in chaff.yaml.
     pairs:

package/rules/unqualified-superlative.yaml

@@ -1,6 +1,6 @@
 id: unqualified-superlative
 layer: L2
-status: experimental
+status: stable
 how_to_find: unqualified-superlative
 word_list: superlative
 extra_word_lists: [comparison-marker, superlative-scope, quantity-noun]
@@ -26,6 +26,11 @@ how_to_fix:
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
 use_for: [business, blog, 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."
 sources: [femmer-2017]
 
 group: wording

package/rules/unrendered-emphasis.yaml

@@ -0,0 +1,73 @@
+id: unrendered-emphasis
+layer: L1
+status: stable
+how_to_find: unrendered-emphasis
+requires: [markdown]
+severity: warning
+
+name:
+  ja: 太字にならずに見える「**」
+  en: Unrendered emphasis marks
+
+why:
+  ja: 「**」や「__」は、Markdown が対にできたときだけ太字になり、対にできなければそのまま記号として表示されます。閉じ忘れ（「**重要」）のほか、日本語では「**「重要」**です」のように括弧や句読点の内側に記号を置き、外側に字が続くと、CommonMark の決まりで閉じられず、読み手には「**」が見えます。
+  en: '"**" and "__" turn into bold only when Markdown can pair them; otherwise they show as written. Besides one left open ("**important"), a mark with punctuation inside and a letter outside (Japanese "**「重要」**です") cannot close under CommonMark''s rules, and the reader sees the "**".'
+
+message:
+  ja: 「{mark}」が太字にならず、そのまま表示されます
+  en: '"{mark}" is not turned into bold and shows as written'
+
+how_to_fix:
+  ja: 閉じ忘れなら閉じる「**」を足してください。括弧や句読点の内側に置いた記号は、括弧の外に出すか（「**「重要」**」の外側に空白を置く）、括弧ごと太字にしないでください。
+  en: If it was left open, add the closing "**". If punctuation sits inside the mark, move the mark outside the punctuation, or put a space outside it.
+
+placeholders:
+  mark:
+    ja: 記号
+    en: the mark
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 対にならず、太字にならないまま記号として見える「**」「__」
+  en: '"**" or "__" that Markdown cannot pair and shows as written'
+example:
+  ja:
+    before: 締め切りは**金曜日です。遅れないようにしてください。
+    after: 締め切りは**金曜日**です。遅れないようにしてください。
+  en:
+    before: The deadline is **Friday. Do not be late.
+    after: The deadline is **Friday**. Do not be late.
+
+not_flagged:
+  ja: 語の中の記号（「2**10」「snake__case」）、前後が空白の記号、三つ以上並んだ記号（区切りや記入欄の「____」）、「__init__」のような名前、コードと引用の中の記号は指しません。
+  en: A mark inside a word ("2**10", "snake__case"), a mark with spaces on both sides, runs of three or more (dividers and blanks to fill, "____"), names such as "__init__", and marks in code or quotations are not reported.
+rewrite:
+  depth: light
+  ja:
+    direction: 太字にしたい範囲を「**」で正しく囲んでください。閉じ忘れは閉じる記号を足し、括弧の内側に置いた記号は括弧の外に出します。言葉は変えません。
+    pairs:
+      - before: 締め切りは**金曜日です。
+        after: 締め切りは**金曜日**です。
+      - before: これは**「重要」**です。
+        after: これは「**重要**」です。
+    keep:
+      - 文の言葉
+      - 太字にしたい範囲
+    avoid:
+      - 太字をやめて記号だけ消すのか、閉じるのかを、文から読み取らずに決める
+  en:
+    direction: Wrap the words meant to be bold in a matching pair of "**". Add the missing closing mark, or move a mark outside the punctuation it sits inside. Keep the words.
+    pairs:
+      - before: The deadline is **Friday.
+        after: The deadline is **Friday**.
+      - before: Mark the task **done when it ships.
+        after: Mark the task **done** when it ships.
+    keep:
+      - the words
+      - the span meant to be bold
+    avoid:
+      - deciding whether to close or drop the mark without reading the sentence

package/rules/unused-definition.yaml

@@ -1,9 +1,9 @@
 id: unused-definition
 layer: L3
-status: experimental
+status: stable
 how_to_find: unused-definition
 requires: [structure]
-severity: warning
+severity: info
 
 name:
   ja: 定義したのに使っていない語
@@ -27,7 +27,7 @@ placeholders:
     ja: 〇〇
     en: the term
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
@@ -51,6 +51,7 @@ not_flagged:
   ja: 定義の書き方（「X」とは、以下「X」という）で書いた語だけを見ます。複数形と所有の形（Services、Seller's）は使用に数えます。同じ語の二つ目の定義は duplicate-definition が言います。
   en: Only terms defined in a recognised form ("X" means, (the "X")) are checked. Plurals and possessives (Services, Seller's) count as uses. A second definition of the same term is duplicate-definition's to report.
 rewrite:
+  depth: light
   ja:
     direction: 本文で使っていない定義を消してください。本文が同じものを別の語で呼んでいるなら、その語を定義した語に替えます。どちらかは書き手に聞きます。
     pairs:

package/rules/url-run-on.yaml

@@ -1,6 +1,6 @@
 id: url-run-on
 layer: L1
-status: experimental
+status: stable
 how_to_find: url-run-on
 severity: warning
 

package/rules/use-before-definition.yaml

@@ -1,9 +1,9 @@
 id: use-before-definition
 layer: L3
-status: experimental
+status: stable
 how_to_find: use-before-definition
 requires: [structure]
-severity: warning
+severity: info
 
 name:
   ja: 定義より前で使っている語
@@ -29,7 +29,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]
 
@@ -53,6 +53,7 @@ not_flagged:
   ja: 定義の条（「X」とは…をいう）で定義した語は、前で使っても言いません。定義の条は文書の頭にも終わりにも置く書き方があるためです。最初の一か所だけを指します。
   en: Terms defined in a definitions clause ("X" means ...) are not checked, since a definitions clause may come first or last. Only the first early use is pointed at.
 rewrite:
+  depth: structure
   ja:
     direction: 定義を、その語を最初に使う文へ移してください。移せないなら、前の文を定義した語を使わない書き方にします。
     pairs:

package/rules/vague-figure-reference.yaml

@@ -1,6 +1,6 @@
 id: vague-figure-reference
 layer: L2
-status: experimental
+status: stable
 how_to_find: vague-figure-pointer
 # 置き場所で指す言い方と、その言い方が指す種類（図・表）。図・表に名前を付ける語は dangling-figure-reference と同じ figure-label。
 # 箇条を置き場所で指す言い方は vague-clause-pointer。文書の構造の木に番号付きの条か章があるときだけ見る。
@@ -35,6 +35,8 @@ placeholders:
 levels: { strict: error, normal: warning, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
 sources: [jis-z8301-2019]
 
 group: structure

package/rules/vague-link-text.yaml

@@ -1,6 +1,6 @@
 id: vague-link-text
 layer: L1
-status: experimental
+status: stable
 how_to_find: vague-link-text
 word_list: vague-link-text
 requires: [markdown]
@@ -51,6 +51,7 @@ not_flagged:
   ja: 言葉の一部に「こちら」を含むだけのリンク（「料金表はこちら」）、URL をそのまま書いたリンク、参照の形のリンク（[こちら][1]）は指しません。Markdown でない文書と、引用（>）とコードの中のリンクも見ません。
   en: Link text that only contains such a word ("pricing here"), a bare or angle-bracket URL, and reference-style links ([here][1]) are not reported, nor are links in a quotation (>), in code, or in a document that is not Markdown.
 rewrite:
+  depth: light
   ja:
     direction: リンクの言葉を、行き先の名前（ページの題、資料の名前）に変えてください。「こちら」「ここ」は文から外し、文は行き先の名前を言う形に組み直します。行き先の URL は変えません。
     pairs: