Filed unassigned by the domain:devx execution seat while implementing #13745 (PR for claude/issue-13745-corpus-claim-ratchet-rows). ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:*.
The stale claim
.github/workflows/lint.yml, in the comment block above the Teaching-corpus lexical anti-drift ratchet step (run: pnpm check:corpus-claim-drift), on origin/main today:
# Table-driven by the #13582 triage ruling, carrying the `$exists` family
# ONLY — each further word (the retired `$regex` spelling, #13532's
# `visibleWhen` claims) pays its own baseline on its own card.
#13745 is that card, and it ships all three of the words this comment names as still outstanding: exists-portability (the (NoSQL) portability gloss), regex-retired and section-visiblewhen-unbound. Once it merges, every clause of the sentence is false — the table no longer carries the $exists family only, and the two words it forward-references are no longer pending.
The gate's own header, its VOCABULARY JSDoc and its --self-test enumeration are all updated by that PR. This one comment is not, because it lives in .github/**, which #13745's dispatch put ⛔ off that card's file surface (the PM's stated reason: lint.yml is a hot conflict file, and #13582 already paid one round of contention on it with PR #13584).
Why it is worth a card rather than a shrug
Same class as #11551, #10045 and #10713 — a workflow comment that carried measured facts and drifted silently. It is not read by anything, so nothing goes red; the only instrument is someone reading it, which is the exact failure mode the gate underneath it exists to mechanise.
The correcting wording, offered not imposed
# Table-driven by the #13582 triage ruling. #13582 shipped the `$exists`
# family alone; #13745 added the `(NoSQL)` portability gloss, the retired
# `$regex` spelling and #13532's `visibleWhen` claims, each with its own
# legitimate-usage survey. Each further word pays its own baseline on its
# own card, and the gate's `--self-test` pins the shipped row set as an
# exact enumeration.
⚠️ Sequencing: this is only true once #13745's PR merges. Landing it before that would make the comment false in the other direction.
Filed unassigned by the
domain:devxexecution seat while implementing #13745 (PR forclaude/issue-13745-corpus-claim-ratchet-rows). ⛔ Ungraded, ⛔ unclaimed, ⛔ nodomain:*.The stale claim
.github/workflows/lint.yml, in the comment block above the Teaching-corpus lexical anti-drift ratchet step (run: pnpm check:corpus-claim-drift), onorigin/maintoday:#13745 is that card, and it ships all three of the words this comment names as still outstanding:
exists-portability(the(NoSQL)portability gloss),regex-retiredandsection-visiblewhen-unbound. Once it merges, every clause of the sentence is false — the table no longer carries the$existsfamily only, and the two words it forward-references are no longer pending.The gate's own header, its
VOCABULARYJSDoc and its--self-testenumeration are all updated by that PR. This one comment is not, because it lives in.github/**, which #13745's dispatch put ⛔ off that card's file surface (the PM's stated reason:lint.ymlis a hot conflict file, and #13582 already paid one round of contention on it with PR #13584).Why it is worth a card rather than a shrug
Same class as #11551, #10045 and #10713 — a workflow comment that carried measured facts and drifted silently. It is not read by anything, so nothing goes red; the only instrument is someone reading it, which is the exact failure mode the gate underneath it exists to mechanise.
The correcting wording, offered not imposed