Repository navigation
v0.42.3
Pre-release
One rule for the ampersand, in both grammars
A structural field escaped nothing and the body escaped everything, and each was wrong at one end. source: https://x.test/rechercher?q=marks©=1®=2 reached the reader as …?q=marks©=1®=2 — © and ® without a semicolon are in HTML5's legacy character-reference list, so a query string carrying either was silently destroyed. At the other end, the body escaped every & including inside your own raw HTML, so a hand-written <a href="?a=1&b=2"> came out &amp;: a dead link.
One sentence now covers both: escape an & outside a tag, leave what is inside one verbatim. It splits on the typography engine's own pattern, literally the same one — two mechanisms disagreeing about where a tag begins would protect different halves of the same document.
What stops being corrected, and is written down rather than discovered: a bare & inside a raw tag. That is your HTML, and repairing it would be the interference this tool declares it does not do.
An autolink is refused by name
<https://x.test> and <contact@x.test> still fail the build — <...> belongs to raw inline HTML here, and the two syntaxes want the same two characters. What changes is the diagnosis: it used to answer "unbalanced raw HTML (an unclosed or mismatched tag, e.g. a <div> in a fact-box)", which sends someone who wrote ordinary Markdown hunting for a tag they never typed.
It now names the autolink, quotes what you wrote, and gives the remedy for the form in front of it: [url](url) for an http(s) address, raw <a href="…"> for anything else — because a Markdown link takes http(s) and nothing else, so advising [a@b](mailto:a@b) would have been advice that does not work.
Migration
Rebuild. Nothing in the format changes, and no page of this repository moves.