epubveri for Sigil 0.3.0 — one setting, and one thing written down.
https://github.com/veripublica/epubv...g/sigil-v0.3.0
The order of the findings is a setting now, in the same JSON file as the display switches: "sort", one of severity (the default), severity-low, or document. It is written into the file on the first run, like the others, so the file shows that the choice exists.
Severest first was already what this plugin did. What changed is that you can ask for something else, and that each severity group now keeps the book's order instead of being re-sorted by file name. Advisory findings sort last, since they never move the verdict. The words are epubveri's own — the command line takes --sort severity and --sort document — and the calibre plugin's setting uses the same three, so the two never need different vocabulary.
A setting rather than clickable columns because Sigil draws the results table: its columns are File, Line, Offset and Message, and clicking Message sorts the severities alphabetically, which puts ERROR above FATAL. What the plugin hands over is the only correct severity order available here. Ran all three orders through Sigil's own launcher before releasing.
And one limit is now in the README rather than only in this thread: if you have edited the OPF in the session and not saved, a position in that file can be a line or two away from what Code View shows, because a plugin is handed a rebuild of a modified OPF rather than the text on screen. Everything else in the book, and an OPF you have not edited, matches exactly. DiapDealer is looking at whether the two ought to line up; if they come to, the note goes away.
Thanks again to PeterT for the Linux run and to DNSB for Windows on the last one.