v0.2.4

Nothing to upgrade for. No file under skills/, shell/ or tools/ differs from 0.2.3 except
the version string. A deck that passed 0.2.3 passes this one unchanged. The version moves because the
published line takes the next patch number, not because the plugin did.

What it carries is the project's own record. A finding this repository ranked, published and cited in
five documents turned out to have measured the wrong thing, and this release withdraws it.

The finding said three tool files were mostly docstring: 85%, 58% and 36%, against 30% for the whole
tools directory. Every one of those numbers counted triple-quoted string tokens. Measured by what
Python actually calls a docstring, the same files are 3.2%, 15.3% and 11.6%, against 16.3%. The file
reported at 85% is the least documented of the 38 files there. The strings being counted are the
probe pages and CSS blocks those tools write out, so the change the finding proposed would have
deleted two tools' own output.

Four figures agreed with each other and all four were about something else. The task is cancelled
rather than deleted, its measurements kept, and the corrections are marked in place in the audit
instead of edited away. The rule it left behind is that a share-of-file figure is a claim about a
unit, and the instrument has to count that unit.

What each release newly required

From docs/PUBLISHING.md §8.1, verbatim:

Version	What it newly required	What newly fails	The smallest edit
0.2.4	Nothing. Not "nothing required of a deck's content" as in 0.2.3 — nothing at all. No file under skills/, shell/ or tools/ differs from 0.2.3 but the version string, so the shared shell is byte-identical and shell.py check has nothing new to say	Nothing. Any deck that passed 0.2.3 passes 0.2.4 unchanged, and a deck already behind on the shell is behind by exactly what 0.2.3 said	None. If shell.py check reports a difference, it is 0.2.3's row, not this one