10.0.0 changelogs: package files miss root entries, #206 under Fixed, date to set at tag #279

Problem

A release-readiness check on main e465c45 compared the five 10.0.0 changelog sections with each other and with the closed issues. The root section's form, links and coverage pass: every breaking issue has a Breaking line, every addition has an Added line, and every link and anchor resolves. These need work:

Must change at the tag

• The date. All five headings say ## [10.0.0] — 2026-10-17, which is 9.1.0's date. No test or workflow checks it. Set it to the tag date in the commit that gets tagged.

Should fix

• Package changelogs miss root entries. NuGet's release notes link to these files. The entries came from commits that touched only the root changelog (16c5a26, 6db30a6, 8010f3f, 23cb85c, d0bb3b4).
  • Core is missing: the integer/decimal NUL refusal and the DateTimeOffset offset forms (Breaking), and the derived-record refusal, 0x/0o/0b and digit separators, dimension decoration and {{}}, and offsets up to ±15:59:59 (Fixed).
  • EF Core is missing the PostgreSQL 16 floor and Any/Count from VALUES.
  • EF Core NodaTime is missing the PostgreSQL 16 floor (The 10.x PostgreSQL floor is 16, not 14: state it, and test it in CI #215 carries package/efcore-nodatime).
  • NodaTime is missing the LocalDateTimeRange Z/Instant offset fix (LocalDateTime bounds and elements refuse Z and an offset that tsrange and DateTimeRange read #130/InstantRange and InstantSet read offsets beyond ±15:59:59 that timestamptz rejects #188) and the derived-record fix (Range unions are not closed: the synthesized protected copy constructor admits a sixth variant #206). Check whether the inverted-literal Breaking entry (An inverted range literal parses as empty on every entry point; PostgreSQL rejects it #114) applies to it too.
• Range unions are not closed: the synthesized protected copy constructor admits a sixth variant #206 is under Fixed (CHANGELOG.md:56), but it's labelled silent. Under the old rule (CONTRIBUTING.md, "A fix that changes an answer") a silent fix in 10.0.0 goes under Breaking. It also makes code that compiled throw at construction.

Nits

• Docs-only resolutions are handled unevenly. A discrete range read as [x,infinity) loses 9999-12-31; UpperBound disagrees between memory and server #117, A temporal literal with sub-microsecond digits is a different value than PostgreSQL reads from the same text #126, A server-side predicate over a stored NaN or infinite float answers in PostgreSQL's order; only loading throws #232 and A YearMonthRange column can't load an exclusive infinity) #258 have Docs: lines; IsAdjacentTo at the date extremes: memory says adjacent, PostgreSQL does not (MinValue/MaxValue are ±infinity there) #110, Document that a stored timerange bound of 24:00:00 fails to load #108 and Document (,max] at the discrete domain boundary: PostgreSQL raises integer out of range #132 have none.
• The Breaking lines for IsUnbounded, Overlaps and Any/Count link to migration.md#migration-from-v9x instead of their own subsections. The DateTimeOffset line links to a heading in the v8.x section.
• Under discussion: sort each section's lines by area prefix, and cut each to one sentence plus its link. The section averages about 430 characters per line.

Done when

The package sections carry every root entry that affects their package, #206 is under Breaking, and CONTRIBUTING.md says the date is set in the tagged commit.