[matt-edmondson]

Fixes #170

Summary

LineTerminators.Split was a plain string.Split, so text ending in a line terminator kept an empty last element, and both of its callers wrote that element as a line:

• WriteAutoGeneratedHeader("Copyright (c) X\r\n") wrote a bare // between the copyright and // <auto-generated />.
• DocComment { Summary = "Hello.\n" } split the summary over three lines and added an empty /// line, where "Hello." alone gives /// <summary>Hello.</summary>. The same applied to every other element, <param> included.

Changes

• LineTerminators.Split drops one empty trailing element when there is more than one line. This follows the rule TemplateRendering.SplitLines already uses. It recognises every terminator: LF, CRLF, CR, NEL, LS and PS.
• A blank line inside the text, as in "A\n\nB", is still written as a bare // / ///, because only the tail is dropped.
• The method uses Array.Resize instead of lines[..^1], because the netstandard2.0 target has no RuntimeHelpers.GetSubArray.

Tests

• Header with a trailing terminator, once for each of the six terminators: no bare //.
• Header "A\n\nB\n" keeps its inner blank line.
• Summary = "Hello." followed by LF, CRLF or LS renders on one line.
• Summary = "A\nB\n" renders two content lines with no empty ///.
• A <param> whose text ends in \n renders on one line.
• All 12 new test cases fail on main and pass with the fix. I checked this by reverting LineTerminators.cs and running them again.
• Full suite: 261/261.

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud