docs(changelog): the [Unreleased] heading was stale, and a release would have mis-attributed 1.0.0

`## [Unreleased]` sat BELOW `## [1.0.0]`, left behind by the 1.0 cut: the cut wrote a
short framing entry and never converted the old heading under it, so ~1200 lines
of already-shipped 1.0.0 detail were still filed as unreleased.

That is not cosmetic. `scripts/release.mjs` promotes by inserting the new version's
heading directly after `## [Unreleased]` — so cutting 1.0.1 against this file would
have relabelled the whole 1.0.0 body as 1.0.1. The dry run did exactly that, which
is how it was found.

Fixed by putting each entry under the release that shipped it: #360's `field.map`
entry — the only `###` git shows added since v1.0.0 — moves into [1.0.1], the stale
heading is dropped so the rest folds back under [1.0.0] where it belongs, and a
fresh empty [Unreleased] goes on top for the next cut. My own one-line field.map
bullet is removed as redundant now that #360's full entry sits in the section.

Content is preserved: net -3 lines, and [1.0.0] keeps all 43 of its entries.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTcEKXTQMYt84fAjuw5A2M

Author: dmealing

CHANGELOG.md

@@ -8,6 +8,8 @@ promises the **software** surface, `metamodelVersion` promises the **metadata**
 `^1.0.0` accepts a MINOR — so **a release that moves `metamodelVersion` says so in its entry
 here.**
 
+## [Unreleased]
+
 ## [1.0.1] — 2026-09-10
 
 **Why this is a PATCH and not a MINOR.** `docs/RELEASING.md`'s table says an additive CLI
@@ -31,8 +33,6 @@ codegen outright. No adopter on 1.0.0 sees a behaviour change they did not alrea
   `KeyValuePair` structs instead of the values (which also left a map nested *inside* a value
   object unchecked). TypeScript, Python and Kotlin were never affected; scalar-valued maps
   (`@valueType`) carry no bean and are unchanged.
-- **`field.map` codegen completes on Java and C#** ([#360]). Before this a map-bearing entity
-  failed Spring/EF codegen at the unsupported-type throw, so no model could use it there.
 
 ### Changed
 
@@ -58,38 +58,6 @@ codegen outright. No adopter on 1.0.0 sees a behaviour change they did not alrea
 - `fixtures/conformance/CAPABILITIES.json` regenerated — it is derived from every fixture's
   `script.json` and **nothing reads it at test time**, which is why it had gone stale unnoticed.
 
-`metamodelVersion` is unchanged at **1.0** — no registered vocabulary moved.
-
-[#362]: https://github.com/metaobjectsdev/metaobjects/issues/362
-[#361]: https://github.com/metaobjectsdev/metaobjects/issues/361
-[#360]: https://github.com/metaobjectsdev/metaobjects/pull/360
-[#359]: https://github.com/metaobjectsdev/metaobjects/issues/359
-[F101]: https://github.com/metaobjectsdev/metaobjects/blob/main/docs/features/cli.md#the-prompt-directory-prompts-everywhere-f101
-
-## [1.0.0] — 2026-09-09
-
-**The stable release.** npm / PyPI / NuGet go to `1.0.0`; Maven Central to `8.0.0` (the
-historical major `7` plus one, per ADR-0035 §2's decouple ruling — Maven cannot move
-backwards). `metamodelVersion` freezes at **`1.0`**.
-
-What that promises, and what it does not, is in
-[`docs/compatibility-policy.md`](docs/compatibility-policy.md): the metamodel spine, the CLI,
-the wire format and the scaffold-and-own contract are covered; generated code is yours and
-disposable, so its internals are not. The two version axes stay separate (ADR-0035
-Amendment 2) — `^1.0.0` accepts `1.1.0`, so a release that moves `metamodelVersion` says so
-here.
-
-Upgrading from `0.x` is [`docs/features/migrations/0.x-to-1.0.md`](docs/features/migrations/0.x-to-1.0.md),
-and `meta upgrade --apply` rewrites what a retirement made illegal.
-
-The last open release gate was **G3d** — an adopter estate must run the RELEASE CANDIDATE
-with the drift gate ENFORCED before promote. It is closed: nine maintainer-owned estates ran
-`1.0.0-rc.7`/`rc.8` with their own gates enforced, across all four ports that have adopters
-(TypeScript, Python, Kotlin/JVM, and the D1/Cloudflare and Postgres deployments). What that
-found is in this entry and the ones below it.
-
-## [Unreleased]
-
 ### Fixed — `field.map` codegen completes: Java generates it, C# persists it
 
 The subtype is registered in all five ports and TypeScript, Kotlin and Python already
@@ -132,6 +100,35 @@ adopter who read "field.map now works" out of this entry would be over-reading i
 **`metamodelVersion` does not move**: no registered vocabulary changed, and
 `expected-registry.json` is untouched.
 
+`metamodelVersion` is unchanged at **1.0** — no registered vocabulary moved.
+
+[#362]: https://github.com/metaobjectsdev/metaobjects/issues/362
+[#361]: https://github.com/metaobjectsdev/metaobjects/issues/361
+[#360]: https://github.com/metaobjectsdev/metaobjects/pull/360
+[#359]: https://github.com/metaobjectsdev/metaobjects/issues/359
+[F101]: https://github.com/metaobjectsdev/metaobjects/blob/main/docs/features/cli.md#the-prompt-directory-prompts-everywhere-f101
+
+## [1.0.0] — 2026-09-09
+
+**The stable release.** npm / PyPI / NuGet go to `1.0.0`; Maven Central to `8.0.0` (the
+historical major `7` plus one, per ADR-0035 §2's decouple ruling — Maven cannot move
+backwards). `metamodelVersion` freezes at **`1.0`**.
+
+What that promises, and what it does not, is in
+[`docs/compatibility-policy.md`](docs/compatibility-policy.md): the metamodel spine, the CLI,
+the wire format and the scaffold-and-own contract are covered; generated code is yours and
+disposable, so its internals are not. The two version axes stay separate (ADR-0035
+Amendment 2) — `^1.0.0` accepts `1.1.0`, so a release that moves `metamodelVersion` says so
+here.
+
+Upgrading from `0.x` is [`docs/features/migrations/0.x-to-1.0.md`](docs/features/migrations/0.x-to-1.0.md),
+and `meta upgrade --apply` rewrites what a retirement made illegal.
+
+The last open release gate was **G3d** — an adopter estate must run the RELEASE CANDIDATE
+with the drift gate ENFORCED before promote. It is closed: nine maintainer-owned estates ran
+`1.0.0-rc.7`/`rc.8` with their own gates enforced, across all four ports that have adopters
+(TypeScript, Python, Kotlin/JVM, and the D1/Cloudflare and Postgres deployments). What that
+found is in this entry and the ones below it.
 
 ### Added — `meta verify` advises when a provider still carries the prop 1.0 renamed away