[tannevaled]

rbgo reports RUBY_VERSION 4.0.9 since ruby#882, and BASELINE was re-recorded at that version on the pinned runner that enforces it: 23,511 → 23,673.

⛔ My grep found one of four; the tool's arithmetic found the rest

$ git grep -n "23,511\|23511" -- content
content/en/_index.md:13:...        # ONE hit

One hit reads exactly like "one place to fix", and that is what I concluded. Then tools/conformancefigure said:

4 total claim(s) and 2 version claim(s) checked against the gate's 23511
content/en/_index.md:13: claims 23673, the gate records 23511

Four checked, one disagreeing — so three claims still agreed with the old figure, in a directory I had just declared clean. They are written with a space, 23 511, which neither of my patterns could match:

content/en/conformance.md:209
content/en/conformance.md:262
content/en/roadmap.md:22

What caught it was not re-reading the page. It was a count that refused to add up. A tool that prints only its findings would have agreed with me; one that prints its denominator makes a too-narrow search self-refuting. Worth keeping in mind for any future checker here.

The known-limitation row is resolved, not deleted

The RUBY_VERSION row asked for "a CI sweep that moves CUR_VERSION without regenerating the baseline, so the ratchet names every file that moves in both directions." That sweep was run — both engines built from one commit minus the version string, over core and language together. The row now carries its result, including the two cautions the numbers need:

• +144 is a net, and 13 regressed is not 13 defects: six of the thirteen lost only examples the corpus stops asking for, each with a CLOSED guard in the census;
• core/objectspace/_id2ref_spec.rb reading 10 → 0 is eleven examples below 4.0 against one above it, not ten regressions.

The 27 that went red are the move's real remaining work, listed per item on ruby#799.

Also corrected

CUR_VERSION = RUBY_VERSION, so the shim cannot disagree with the interpreter — the "two copies, agreeing" wording predates ruby#845. And the baseline is recorded on the runner that enforces it, not on a laptop: one laptop reads +9 against CI for no change in the code.

Verified: go run ./tools/conformancefigure --root content/en now prints 4 total claim(s) and 2 version claim(s) checked against the gate's 23673 at Ruby 4.0.9.

🤖 Generated with Claude Code