docs(changelog): name 0.24.1 as the sole claimant of metamodelVersion 0.11

The section already attributed the `0.10` → `0.11` move to the #342 XOR
relaxation. What it did not say is that shipping it SPENDS the slot.

That gap was not hypothetical: a parallel branch had planned its own vocabulary
change to "ride the existing 0.11", reasoning that v0.24.0 shipped 0.10 so 0.11
was unclaimed. It is claimed — by this release — so that work moves to 0.12. Left
unsaid, it would have surfaced as a red gate at the END of a long plan instead of
at its start, and `check-metamodel-version.mjs` would not have caught it there
either: that change is prose-only on a byte-gated description, which the gate WARNs
on rather than classifies.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DhpswkF1NvwxhFWMmdAT15

Author: dmealing

CHANGELOG.md

@@ -64,7 +64,12 @@ array — so presence and content are asked as separate questions.
 **`metamodelVersion` moves `0.10` → `0.11`** — `@fields` becomes optional on both node
 types, which the gate classifies as additive. The package line stays a PATCH; that
 severance is exactly what [ADR-0035 Amendment 2](docs/RELEASING.md) is for, and post-1.0
-the changelog is the only signal on the metadata axis.
+the changelog is the only signal on the metadata axis. **This relaxation is `0.11`'s sole
+claimant** — the slot is spent by shipping it, so the next registered-vocabulary change
+moves to `0.12`, whatever else is in flight when it lands. Worth stating because it has
+already been misread once: unreleased work on another branch touched the same number on
+the reasoning that `0.11` was still unclaimed, which would have surfaced as a red gate at
+the end of that work rather than at its start.
 
 **Two things this took, worth recording.** The Java port needed a fix the other three did
 not: beyond the registry declaration, `ValidationPhase.validateIdentityNode` carried a