[tannevaled]

Re-measured 2026-09-26. Small PR: this site was already the most accurate of the four, and most of what it says survived checking.

Version. The page named v0.2.0 (2026-09-21) as the current release, in the prose and in the go get snippet. The real latest tag is v0.4.0, cut 2026-09-26; main is exactly that tag (git describe --tags → v0.4.0). Also notes that go-embedded-ruby's interpreter currently pins v0.3.0, so the consumer is one release behind — useful to anyone wondering which grammar the interpreter has.

A claim that no longer reproduces. grammar.md said four files in the pinned ruby/spec language/ corpus — for_spec, block_spec, defined_spec, variables_spec — parse here but stop later in go-embedded-ruby's compiler, and called that consumer-side work. Re-run on 2026-09-26, all four execute and report results:

language/for_spec.rb       -> pass=29  fail=0 error=5
language/block_spec.rb     -> pass=163 fail=2 error=1
language/defined_spec.rb   -> pass=256 fail=2 error=0
language/variables_spec.rb -> pass=114 fail=5 error=0

The page now records that it stopped reproducing rather than repeating it.

The "all three parse now" note is re-verified against v0.4.0, and now says the probe carried a control that must fail (BEGIN { }) and did — so a reader can see the check was capable of returning "refused".

Checked and deliberately unchanged

ci.yml backs everything this site claims about CI: the 100 % coverage gate really does run on all three OS lanes (unlike the interpreter, which exempts windows), all six 64-bit targets really do run on every push (amd64/arm64 native, four under QEMU), and both js/wasm and wasip1/wasm are built — both of which compile here.

🤖 Generated with Claude Code