[rr-]

Numpydoc moves indented text before a section's first item into the long description. When that text came right after a summary with no blank line, blank_after_short_description stayed False, so compose wrote it straight under the summary and it read back as part of the summary. This affected every section with items: Parameters, Attributes, Other Parameters, Receives, Keyword Arguments, Returns, Yields, Raises and Warns.

• append_loose now marks such text as a paragraph of its own whenever compose would write it right after the summary, that is, unless a leading deprecation goes between them. The existing deprecation_keeps_blank_after_short cases keep their spacing.
• Google, ReST and Epydoc already set the flag, so only Numpydoc output changes.
• New test: the lead text reads back for Parameters, Attributes and Raises. I also checked all nine sections with items in every rendering.
• No existing round-trip exclusion goes away. None of them was this bug. google+numpydoc: list methods one item each #193 adds the one that was, (182, Numpydoc), and will drop it once based on this branch.
• just update-cases changes nothing.
• Parity against origin/main: 5 generated inputs differ, only in Numpydoc and auto, and only by blank_after_short_description turning True plus the compose output that follows from it.
• Bench against origin/main: max 1.02 on 3.14 and 1.01 on 3.8.