[CaffeinatedCoder]

Closes #154

Problem

At the tag, ## 2.3.0 becomes the GitHub release's notes and every package's nuget.org release notes. It had no line for three merged changes a consumer can see: the Generators fixes #102 (#90) and #106 (#100), and #122 (SuperStrong.Types in the comparison, the README introduced by example, Vogen thanked). It had no ### Fixed heading either.

Change

CHANGELOG.md, ## 2.3.0 only:

• New ### Fixed (after Changed, as in 2.1.0): fix: CodeAnnotations builds its attribute constructions on use, not in static fields #102 (the aspects keep no compilation objects in static fields, the design-time leak) and fix: a generated TryParse ends at its return, with no unreachable tail #106 (a generated TryParse ends at its return). fix: CodeAnnotations builds its attribute constructions on use, not in static fields #102 has no link, since no consumer page covers it; fix: a generated TryParse ends at its return, with no unreachable tail #106 links "Reading the generated code".
• Changed: the Comparison line now starts with SuperStrong.Types 1.0.0 joining the value-object table. A new README line covers the introduction by example and the Vogen thanks (docs: introduce TypeKit by example, acknowledge Vogen, and add SuperStrong.Types to the comparison #122).
• docs: the READMEs show the generated code for OrderId, Email and a closed set #104 (docs-only) gets a line under Added. The section already lists docs changes a reader can use, such as the site and the walkthrough. The folded generated code for OrderId, Email and a closed set is one of those, and a test holds it to the build.
• docs: introduce Metalama where the READMEs first mention it #112 (docs-only) shares docs: introduce TypeKit by example, acknowledge Vogen, and add SuperStrong.Types to the comparison #122's README line ("every README says what Metalama is where it first names it"). On its own it is a wording change to existing pages, too small for a line, but it belongs with the README introduction.

All 30 PRs merged into release/2.3.0 were compared against the section again. Every feature and user-visible docs PR now has exactly one line, and no conflict resolution left a duplicate. The build, test, spike and tooling PRs (#69, #80, #103, #105, #108, #123, #133, #140, #149, #150) need none. #142 is a test PR, but its README section on SQL Server differences already has a line, which stays. #151 and #152 are not merged yet, and their PRs add their own lines if they need them.

The section is 6,933 characters, under nuget.org's 35,000.

Tests

• ChangelogTests and PackageReleaseNotesTests: 25 passed.
• No new guard. Both tests check the section's form and links, not whether it is complete (as CHANGELOG 2.3.0: no line for the Generators fixes #102 and #106, or for SuperStrong.Types and the README introduction (#122) #154 says).

🤖 Generated with Claude Code