fix(scripts): the ratchet banner's own history clause was false — replace it with the mechanism

The repair's replacement prose asserted that the removed sentence "was false in
one half the day it was written". Re-measured with the shared CLOSING_TRIGGER
over each named file as of each merge commit, reading the blobs rather than the
pull-request titles:

  ff29450 (the commit that wrote the sentence)
    check-action-forward-parity.mjs   2 hits, both emitted messages
    check-type-check-coverage.mjs     3 hits, two emitters plus one noun
  2414e37   check-action-forward-parity.mjs -> 0   first half goes false
  fb7dfed   check-type-check-coverage.mjs   -> 1   second half goes false

Both halves were TRUE the day the sentence was written. The clause was a dated
reading with its date left implicit, asserted in the one place nothing re-reads
it, and it was wrong on its first day — which is the argument this change is
built on, arriving by being committed rather than by being made.

The banner now states the mechanism and stops there: such a sentence does not
stay true, it only waits, and what stood here is on the card. The corrected
reading moves to the pin's header, where a person deciding how to word the
banner will be looking, with the miss recorded beside it. The changeset carried
the same false clause and is corrected with it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015h79niBMyoB1xcaQje3uiz

Author: claude

.changeset/9906-lint-coverage-banner-cross-file-claim.md

@@ -4,8 +4,9 @@
 `scripts/check-lint-coverage.mjs`'s rule-2 ratchet banner no longer asserts, in
 the present tense, which other gates carry the closing-keyword shape
 (objectui#9906). It named two sibling gates and said the shape "still stands" in
-both; one half was false when the sentence was written and the other went false
-when the sibling was repaired. The trade-off the banner exists to explain —
+both; both halves were true when the sentence was written and both had gone
+false before anyone read it again, each falsified by a different pull request
+and neither by the one that wrote the sentence. The trade-off the banner exists to explain —
 spell the anchor `objectui#` rather than a bare `#`, so a quoted message cannot
 match GitHub's closing grammar — is unchanged, and the scope record of the
 repair that wrote it survives as history rather than as a reading of the tree.

scripts/__tests__/check-lint-coverage-closing-keyword.test.ts

@@ -131,9 +131,21 @@ function renderStaleEntry(rewrite: (source: string) => string = (source) => sour
  * about a different gate's source is a reading of a population that moves
  * without this file and re-derives never. objectui#9906 is that shape landed:
  * the banner said the closing-keyword spelling "still stands" in two named
- * sibling gates, one half was already false when it was written, and the other
- * went false two days later when the sibling was repaired. Nothing could have
- * noticed, because nothing read the sentence.
+ * sibling gates. Measured with the `CLOSING_TRIGGER` below, over each named
+ * file as of each merge commit rather than inferred from pull-request titles:
+ * both halves were TRUE the day the sentence was written, and it went stale in
+ * two steps — the first about 35 hours later, the second the same day after
+ * that — each step a different pull request and ⛔ neither of them the one that
+ * wrote the sentence. Nothing could have noticed, because nothing read it.
+ *
+ * ⚠️ That last reading is itself dated, and it lives HERE and on the card
+ * rather than in the banner, on purpose. This file is what a person opens when
+ * they are deciding how to word that banner, and the card carries the commits
+ * the reading was taken at. A first draft of the repair put a version of it in
+ * the banner instead — and got it backwards, claiming a half was already false
+ * on the day of writing. ⭐ A dated reading asserted where nothing re-reads it
+ * was wrong within one review round, which is the argument for this whole rule
+ * arriving by being committed rather than by being made.
  *
  * ⛔ This is NOT a check that any such claim is TRUE — no tree is scanned here
  * and none may be (the 2026-09-18 ruling closed the door on a new gate for

scripts/check-lint-coverage.mjs

@@ -120,8 +120,8 @@ for (const pkg of packages) {
 // re-answer that here, and ⛔ do not name which other gates carry the shape
 // today: a sentence in this banner about another gate's source is a reading
 // taken once, by someone who is not looking at that file, and re-derived
-// never. The one that stood here was false in one half the day it was written
-// (objectui#9906). Pinned by
+// never. Such a sentence does not stay true; it only waits. The one that stood
+// here, and how it went stale, are on objectui#9906. Pinned by
 // scripts/__tests__/check-lint-coverage-closing-keyword.test.ts, which reads
 // this module's text rather than trusting this comment — this paragraph
 // included, for the naming of any other gate.