[ondrejmirtes]

Every description on apiref.phpstan.org rendered as one long paragraph, for example TrinaryLogic.

1. Keep paragraphs apart. phpdoc-parser puts each paragraph into its own text node with an empty node in between. ApiGen dropped the empty nodes and joined the rest with a space. A small PhpDocResolver subclass keeps them as blank lines, and MarkdownConverter removes the spaces ApiGen's join adds around them. Lists, tables and code fences now render wherever they appear, not only at the start of a description. Namespace listings now show only the first paragraph as the short description, as ApiGen intends.
2. Use code fences in class PHPDocs. phpdoc-parser trims the first line of a paragraph, so indented code samples could never render as code blocks. TrinaryLogic, Type (including the getTemplateType() example, which used a @-template workaround), TypeTraverser::map(), VerbosityLevel, GeneralizePrecision, AccessoryType and ContainerExtensionsExtension now use ```php fences.

Checked by generating the docs before and after. Both runs produce 1776 files. Descriptions have 7542 → 8381 <p> elements and 13 → 33 links. Raw ``` text no longer appears outside the source listing pages; before, 160 lines showed it, including existing fenced examples in other PHPDocs that were broken by the join. The <pre> blocks that disappeared were all on namespace index pages, which used to show each class's full description.