Replace unbounded exclusivity claims with verifiable bounded ones

A reviewer on a submission PR flagged "no other tool covers" as an absolute
claim the entry does not substantiate, and cited two projects with overlapping
Arabic/RTL coverage. The claim was unverified when written, which is the actual
error regardless of whether those specific counter-examples hold up — a repo
whose central rule is that every finding carries evidence cannot make an
unbounded negative claim about the entire ecosystem on the strength of not
having looked.

Four occurrences replaced across README.md, probe-rtl.js and the social
preview. The bounded form is stronger anyway: "axe and Lighthouse do not check
this" is specific, names the tools, and is verifiable by anyone in a minute.
"No tool does" is unfalsifiable by the person making it and false the moment
one counter-example exists.

The comparison table already made the bounded claim correctly, which is why it
needed no change.

Author: UXBYISSA

README.md

@@ -35,8 +35,8 @@ head/SEO tags, layout overflow, navigation timing.
 40 font sizes does not have a type scale, whatever the design file says),
 interaction-state coverage read from the stylesheets, and microcopy presence.
 
-**Semantic**, via a guided reading pass — the defects no automated tool detects
-because they require understanding what the words mean:
+**Semantic**, via a guided reading pass — defects that pass automated checking
+because they are structurally valid and only wrong in meaning:
 
 - placeholder copy shipped to production (`"traditional description for the premium plan"`, and lorem ipsum in the other locale)
 - marketing claims the product cannot fulfil (a template's "live instructor sessions" on a product with no instructors)
@@ -66,7 +66,8 @@ values that must match across languages, `hreflang` on both sides, whether the
 language switcher preserves the current route — and near-duplicate product
 names, which is how a one-character split like Limo/Lemo gets caught.
 
-*Arabic / RTL*, the part with no equivalent elsewhere:
+*Arabic / RTL*, the part that goes furthest beyond what general-purpose
+tooling checks:
 
 | Check | Catches |
 |---|---|

assets/social-preview.html

@@ -181,7 +181,7 @@ <h1>AUDIT THAT <em>MEASURES</em>, NOT GUESSES</h1>
         <div class="val ar pass">مجلد واحد</div>
         <div class="foot-rule">
           <div class="verdict">✕ FAIL</div>
-          <div class="claim">NO TOOL BUT THIS ONE CATCHES IT</div>
+          <div class="claim">AXE AND LIGHTHOUSE DO NOT CHECK THIS</div>
         </div>
       </div>
 

scripts/probe-rtl.js

@@ -1,9 +1,9 @@
 /**
  * probe-rtl.js — Arabic / RTL interface probe
  *
- * Catches the class of defect that no mainstream accessibility tool looks for,
- * because axe, Lighthouse and friends were built around English. Every check
- * here comes from a bug that ships regularly in real Arabic products:
+ * Catches a class of defect that axe and Lighthouse do not check for, because
+ * they were built around English. Every check here comes from a bug that ships
+ * regularly in real Arabic products:
  * an English `{count} {noun}` template applied to a language with six plural
  * forms, letter-spacing that severs a cursive script, three numeral systems on
  * one screen, a dialect mismatch that makes a product feel foreign to its own