@redocly/recheck 0.14.0 → 2.58.0

package/presets/inclusive-language/PROVENANCE.md

@@ -18,19 +18,19 @@ All `warn` severity (pure word-choice/terminology, no structural content —
 matching both flagships' "word choice → warn" policy) and all detection-only
 (`fix: false`, forced structurally — see `inclusive-language.ts`'s header).
 
-| Rule id | Term(s) | Google source | Microsoft source | Note |
-|---|---|---|---|---|
-| `inclusive-language/slave` | `slave` | C§3.5 row 2 ("Don't use. Instead, use alternative terms... such as worker or replica.") | a-z/master-slave (H.md row 46: "Don't use master/slave. Use primary/replica...") | Bare `master` excluded on both sides — too polysemous (master's degree, master key, git branch name); only the unambiguous `slave` ships as a swap. |
-| `inclusive-language/master-slave-pairing` | `master/slave`, `master-slave` | C§3.5 row 1 ("Never use in conjunction with slave... primary, main, original, parent... controller... leader, or active") | a-z/master-slave (H.md row 46) + bias-free-communication (E.md V25) | The two guides disagree on the replacement (primary/replica vs. primary/subordinate) — ships as `pattern`, matching `microsoft/master-slave`'s own resolution of the identical disagreement. |
-| `inclusive-language/blacklist-whitelist` | `blacklist`, `whitelist` (noun forms) | C§3.5 rows 3-4 | a-z/blacklist, a-z/whitelist (G.md row 58, H.md row 45) | Both guides separately caution the VERB forms don't take a word-for-word swap; message says so. Single-word replacement (`denylist`/`allowlist`) per spec, noting Microsoft's two-word preference. |
-| `inclusive-language/dmz` | `DMZ`, `demilitarized zone` | C§3.5 row 26 | a-z/demilitarized-zone-dmz (G.md row 61) + bias-free-communication | Rare exact match: both guides recommend the identical replacement, "perimeter network". Anchored against the real Korean-border sense (`(?!\s+(?:dividing|between|separating)\b)`), the same guard already proven necessary in `microsoft/bias-free-terms`. |
-| `inclusive-language/grayed-out` | `grayed-out`, `greyed-out` | C§3.5 row 20 | a-z/gray-grayed-out (G.md row 112) | Microsoft's own page: "Don't use gray or grayed out to describe commands or options that are in an unusable state—use not available or isn't available instead" — the shared conclusion is that the JARGON TERM itself should be avoided; Google's "unavailable" ships as the default replacement text. **Not** "shaded": the live page reserves "shaded" for describing the appearance of checkboxes that represent a mixture of settings, a narrower, different case, not a general alternate phrasing for "grayed out" (same distinction `recheck/microsoft`'s own PROVENANCE.md draws for its "shaded" entry). |
-| `inclusive-language/he-she` | `he/she`, `s/he` | Google pronouns page (via C/D.md context) | bias-free-communication V23 (E.md): "Don't use constructions like he/she and s/he." | `(s)he` and "his or her" are NOT independently Microsoft-confirmed as literal banned strings (V23's own caveat) — left out. |
-| `inclusive-language/nondisabled-person` | `normal person`, `healthy person` | D§3.6 row 45 (inclusive-documentation): "Don't describe people without disabilities as normal or healthy" | Microsoft accessibility table Row 5: "Person without a disability" preferred / "Non-disabled person, able-bodied person" acceptable | Matched phrase-level, never bare `normal`/`healthy` — both guides' own text (and `microsoft/accessibility-terms`'s collision note) flag the statistical/wellness senses of the bare words as unrelated and unaddressed. |
-| `inclusive-language/suffering-victim` | `suffering from`, `victim of` | D§3.6 row 43 (inclusive-documentation): "such as victim of, suffering from... instead, use... experiencing, living with" | Microsoft accessibility table Row 4 ("suffers from", "a victim of" in Do-not-use column) + bias-free V28 | Microsoft's own replacement for Row 4 is sometimes a fuller, condition-specific sentence rewrite, not a literal swap — message notes this. Microsoft's "affected by"/"stricken with" (also Row 4) are NOT Google-confirmed and are excluded. |
-| `inclusive-language/differently-abled` | `differently abled` | D§3.6 row 44 (inclusive-documentation, DETECT-ONLY, no replacement given): "physically challenged, special, differently abled, handi-capable" | Microsoft accessibility table Row 8 (Do-not-use column), preferred "person with cognitive disabilities, developmental disabilities, learning disabilities, or dyslexia" | Only "differently abled" is the exact shared string across the two guides' respective lists; Google's other three synonyms in the same row are not independently Microsoft-confirmed. Detection-only, no forced replacement: the two guides scope this euphemism to different specific disabilities. |
-| `inclusive-language/crippled` | `cripple`, `crippled` | D§3.6 row 27 (word-list#cripple): figurative → "slowed down"; of-person → person-first alternatives | Microsoft accessibility table Row 2 (Do-not-use column), preferred "person with limited mobility, person who has a mobility or physical disability" | Detection-only, no forced replacement — the two guides give different alternative sets for the figurative vs. person-reference senses. `microsoft/accessibility-terms` already ships `crippled` bare/unguarded with no demonstrated unrelated collision; this preset does the same for both `cripple` and `crippled`. |
-| `inclusive-language/nuke` | `nuke` | C§3.5 (word-list#nuke): "Don't use. Instead use remove or attack." | Militaristic-language "Never use" list (E.md V26): "...nuke, go nuclear..." | The one term drawn from Microsoft's militaristic list. No other Google-confirmed term overlaps that list. |
+| Rule id                                   | Term(s)                               | Google source                                                                                                                                 | Microsoft source                                                                                                                                                        | Note                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------------- | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------- | ----------------------------------------------------------------------------------------- |
+| `inclusive-language/slave`                | `slave`                               | C§3.5 row 2 ("Don't use. Instead, use alternative terms... such as worker or replica.")                                                       | a-z/master-slave (H.md row 46: "Don't use master/slave. Use primary/replica...")                                                                                        | Bare `master` excluded on both sides — too polysemous (master's degree, master key, git branch name); only the unambiguous `slave` ships as a swap.                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `inclusive-language/master-slave-pairing` | `master/slave`, `master-slave`        | C§3.5 row 1 ("Never use in conjunction with slave... primary, main, original, parent... controller... leader, or active")                     | a-z/master-slave (H.md row 46) + bias-free-communication (E.md V25)                                                                                                     | The two guides disagree on the replacement (primary/replica vs. primary/subordinate) — ships as `pattern`, matching `microsoft/master-slave`'s own resolution of the identical disagreement.                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `inclusive-language/blacklist-whitelist`  | `blacklist`, `whitelist` (noun forms) | C§3.5 rows 3-4                                                                                                                                | a-z/blacklist, a-z/whitelist (G.md row 58, H.md row 45)                                                                                                                 | Both guides separately caution the VERB forms don't take a word-for-word swap; message says so. Single-word replacement (`denylist`/`allowlist`) per spec, noting Microsoft's two-word preference.                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `inclusive-language/dmz`                  | `DMZ`, `demilitarized zone`           | C§3.5 row 26                                                                                                                                  | a-z/demilitarized-zone-dmz (G.md row 61) + bias-free-communication                                                                                                      | Rare exact match: both guides recommend the identical replacement, "perimeter network". Anchored against the real Korean-border sense (`(?!\s+(?:dividing                                                                                                                                                                                                                                                                                                                                                                                                                                                          | between | separating)\b)`), the same guard already proven necessary in `microsoft/bias-free-terms`. |
+| `inclusive-language/grayed-out`           | `grayed-out`, `greyed-out`            | C§3.5 row 20                                                                                                                                  | a-z/gray-grayed-out (G.md row 112)                                                                                                                                      | Microsoft's own page: "Don't use gray or grayed out to describe commands or options that are in an unusable state—use not available or isn't available instead" — the shared conclusion is that the JARGON TERM itself should be avoided; Google's "unavailable" ships as the default replacement text. **Not** "shaded": the live page reserves "shaded" for describing the appearance of checkboxes that represent a mixture of settings, a narrower, different case, not a general alternate phrasing for "grayed out" (same distinction `recheck/microsoft`'s own PROVENANCE.md draws for its "shaded" entry). |
+| `inclusive-language/he-she`               | `he/she`, `s/he`                      | Google pronouns page (via C/D.md context)                                                                                                     | bias-free-communication V23 (E.md): "Don't use constructions like he/she and s/he."                                                                                     | `(s)he` and "his or her" are NOT independently Microsoft-confirmed as literal banned strings (V23's own caveat) — left out.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `inclusive-language/nondisabled-person`   | `normal person`, `healthy person`     | D§3.6 row 45 (inclusive-documentation): "Don't describe people without disabilities as normal or healthy"                                     | Microsoft accessibility table Row 5: "Person without a disability" preferred / "Non-disabled person, able-bodied person" acceptable                                     | Matched phrase-level, never bare `normal`/`healthy` — both guides' own text (and `microsoft/accessibility-terms`'s collision note) flag the statistical/wellness senses of the bare words as unrelated and unaddressed.                                                                                                                                                                                                                                                                                                                                                                                            |
+| `inclusive-language/suffering-victim`     | `suffering from`, `victim of`         | D§3.6 row 43 (inclusive-documentation): "such as victim of, suffering from... instead, use... experiencing, living with"                      | Microsoft accessibility table Row 4 ("suffers from", "a victim of" in Do-not-use column) + bias-free V28                                                                | Microsoft's own replacement for Row 4 is sometimes a fuller, condition-specific sentence rewrite, not a literal swap — message notes this. Microsoft's "affected by"/"stricken with" (also Row 4) are NOT Google-confirmed and are excluded.                                                                                                                                                                                                                                                                                                                                                                       |
+| `inclusive-language/differently-abled`    | `differently abled`                   | D§3.6 row 44 (inclusive-documentation, DETECT-ONLY, no replacement given): "physically challenged, special, differently abled, handi-capable" | Microsoft accessibility table Row 8 (Do-not-use column), preferred "person with cognitive disabilities, developmental disabilities, learning disabilities, or dyslexia" | Only "differently abled" is the exact shared string across the two guides' respective lists; Google's other three synonyms in the same row are not independently Microsoft-confirmed. Detection-only, no forced replacement: the two guides scope this euphemism to different specific disabilities.                                                                                                                                                                                                                                                                                                               |
+| `inclusive-language/crippled`             | `cripple`, `crippled`                 | D§3.6 row 27 (word-list#cripple): figurative → "slowed down"; of-person → person-first alternatives                                           | Microsoft accessibility table Row 2 (Do-not-use column), preferred "person with limited mobility, person who has a mobility or physical disability"                     | Detection-only, no forced replacement — the two guides give different alternative sets for the figurative vs. person-reference senses. `microsoft/accessibility-terms` already ships `crippled` bare/unguarded with no demonstrated unrelated collision; this preset does the same for both `cripple` and `crippled`.                                                                                                                                                                                                                                                                                              |
+| `inclusive-language/nuke`                 | `nuke`                                | C§3.5 (word-list#nuke): "Don't use. Instead use remove or attack."                                                                            | Militaristic-language "Never use" list (E.md V26): "...nuke, go nuclear..."                                                                                             | The one term drawn from Microsoft's militaristic list. No other Google-confirmed term overlaps that list.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
 
 ## Excluded (single-guide coverage — the intersection principle)
 
@@ -75,6 +75,7 @@ the same reasoning applies here even though it happens to be
 Microsoft-only), `Asperger's`.
 
 ## Also excluded (present in both guides' broader word lists, but not shipped
+
 here as inclusive-language)
 
 - **`disable`/`disabled` (of a broken/malfunctioning system)** — Google
@@ -116,7 +117,7 @@ preset. This file was built by taking the **intersection** of those existing
 results: a term ships here only if it is independently `CONFIRMED` on at
 least one Google source AND at least one Microsoft source. Where only one
 guide covers a term, it is listed in "Excluded" above with the reason — that
-asymmetry is what keeps this preset safely composable onto *either* flagship
+asymmetry is what keeps this preset safely composable onto _either_ flagship
 without duplicating or contradicting either one's own word list.
 
 ### Duplicate-finding audit
@@ -131,13 +132,13 @@ that flagship's own preset too.
 
 Measured directly with `lintContent` over this preset's own violations
 fixture (`inclusive-language-violations.md`, which exercises all 11 shipped
-rules), stacked onto each flagship in turn (see `preset-composition.test.ts`'s
+rules), stacked onto each flagship in turn (see `presets.test.ts`'s
 "duplicate findings" describe block for the live, asserted counts):
 
-| Stacked with | Total problems | Duplicate positions | Rules that duplicate | Rules that are net-new |
-|---|---|---|---|---|
-| `recheck/google` | 32 | **11** | `slave`, `blacklist-whitelist`, `grayed-out`, `he-she`, `dmz`, `nuke`, `suffering-victim` (7 of 11) | `master-slave-pairing`, `nondisabled-person`, `differently-abled`, `crippled` (4 of 11) |
-| `recheck/microsoft` | 27 | **8** | `dmz`, `master-slave-pairing`, `nondisabled-person`, `differently-abled`, `crippled`, `blacklist-whitelist` (6 of 11) | `slave`, `grayed-out`, `he-she`, `suffering-victim`, `nuke` (5 of 11) |
+| Stacked with        | Total problems | Duplicate positions | Rules that duplicate                                                                                                  | Rules that are net-new                                                                  |
+| ------------------- | -------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
+| `recheck/google`    | 32             | **11**              | `slave`, `blacklist-whitelist`, `grayed-out`, `he-she`, `dmz`, `nuke`, `suffering-victim` (7 of 11)                   | `master-slave-pairing`, `nondisabled-person`, `differently-abled`, `crippled` (4 of 11) |
+| `recheck/microsoft` | 27             | **8**               | `dmz`, `master-slave-pairing`, `nondisabled-person`, `differently-abled`, `crippled`, `blacklist-whitelist` (6 of 11) | `slave`, `grayed-out`, `he-she`, `suffering-victim`, `nuke` (5 of 11)                   |
 
 **The union of the two "duplicates" columns is all 11 rules.** There is no
 rule in this preset that is simultaneously non-duplicate against BOTH