CHANGELOG 2.3.0: no line for the Generators fixes #102 and #106, or for SuperStrong.Types and the README introduction (#122) #154

Found by a pre-release sweep of release/2.3.0 @ 99c6032 (the CHANGELOG check): each PR merged into release/2.3.0 was compared with the lines of ## 2.3.0 — Unreleased.

Problem

At the tag, the section becomes the GitHub release's notes and every package's nuget.org release notes (CONTRIBUTING, "Releasing", step 2), and it freezes there. CONTRIBUTING also says that "User-visible changes get a changelog entry." Three merged changes a consumer can see have no line:

#104 (the READMEs show the generated code) and #112 (Metalama introduced where the READMEs first name it) are docs-only. Whether they get a line is the maintainer's call. The section already lists docs changes (the site, the walkthrough, the comparison).

The rest of the section checks out:

• 24 lines, one per change.
• Absolute links (step 2 rewrites them to blob/v2.3.0/).
• 5,682 characters, well under nuget.org's 35,000.
• Every feature PR has its line.

The build and test PRs (#69, #80, #108, #123, #133, #140, #149, #150, #103, #105) are internal and need none.

Change

• Add a ### Fixed section with one line each for fix: CodeAnnotations builds its attribute constructions on use, not in static fields #102 and fix: a generated TryParse ends at its return, with no unreachable tail #106.
• Extend the Comparison line, or add one, for SuperStrong.Types and the README introduction (docs: introduce TypeKit by example, acknowledge Vogen, and add SuperStrong.Types to the comparison #122).
• Add lines for Oracle seeds report CAUGHT and pass when SQL Server fixture initialization fails #151 and CMTK0003 misses dropped async assertions through Task wrappers and branches #152 if they land before the tag.

Test

None. PackageReleaseNotesTests and ChangelogTests check the section's form and links, not whether it is complete.