Roast — tests passing and fully-passing files, per release

A file counts as fully passing only when every single test in it passes — one failure anywhere and the whole file drops out of the count. That strict bar is why the right-hand number is small next to the 90% of individual tests passing on the left. Both series start before the first tag, mined from ROAST.md's own git history — one point per day; the %-series begins on Jul 10, when the current "declared" denominator was defined (earlier percentages used a different counting method and would not be comparable).

Documentation conformance — every documented example, run three ways

The same coloured verdicts the conformance page shows as dots, counted over time. ok is the one to watch: documentation, Rakudo and Raku++ all agreeing. Raku++ differs is the work list. The other three are not ours to fix — docs stale is where both engines agree against the documentation, Rakudo differs where Rakudo is the odd one out, and needs a human where all three disagree. Each point is one run of the comparison, not one release, so the line is only as dense as the snapshot has been taken.

Ecosystem — top-50 module battery, byte-identical runs

Benchmarks — kernel wall time in ms, lower is better

Three ways to run the same program: the Raku++ interpreter, the same source compiled to a native binary with --exe, and Rakudo as the reference. Absolute times from BENCHMARKS.md as committed at each release (same machine throughout).