epubveri 0.12.5 — https://github.com/veripublica/epubveri/releases/latest
Sixteen items. Both of JSWolf's are in it.
<guide><referen/></guide> now errors, as it does in epubcheck. Our grammar allowed any element name there. The comment explaining why said that naming the child "would duplicate a violation the surrounding grammar already reports" — and nothing reported it. Fixing it turned up two more beside it: <tours>'s child must be named tour, and a <tour> must contain <site> elements. Both were silent here and both error in epubcheck.
The missing-nav error now points at <manifest> instead of the package root. Nothing about the finding was wrong, only where it said to look, which is the whole of the problem if your editor jumps to the position. The line matches epubcheck exactly now; the column still differs by one convention — we point at the start of a tag and it points at the end, consistently, everywhere.
The other fourteen came from running epubcheck over its own test fixtures and diffing the two outputs, which turns out to see a class our usual test run structurally cannot. Eleven were false positives — findings we made on markup epubcheck accepts — and the rest were things we owed and had not made.
One shape appeared in three unrelated places and is worth naming, since it is the failure a user cannot notice: a check that defers to another check which does not cover the case. The <guide> child above was one. The OCF filename rules asked the manifest href because "an existing file's real name is already checked" — the condition was inverted. A media overlay's targets were "collected by the overlay pass", which ran after the question was asked. None of the three was a wrong answer. Each was no answer at all.
Finally, a correction that goes the other way from yesterday's. The published corpus figure moves from 595 to 603 because the denominator grew: our own test harness had been wrapping loose fixtures in a way that stopped epubcheck asking about eight of them, so they could not be scored at all. That was our harness's doing, not the suite's. Fixed, and verified from epubcheck's side — handed the rebuilt books it now reports the finding the feature file expects, where before it reported nothing.