move Unreleased above v0.111.0 in CHANGELOG

[bborbe]

Problem

#85 anchored its ## Unreleased section above ## v0.110.0. v0.111.0 was released from a commit in between, and landed above it. Both merges were clean — nothing conflicted — leaving ## Unreleased stranded between two released sections:

## v0.111.0
## Unreleased    ← here
## v0.110.0

The releaser reads the newest section. With ## Unreleased sitting below a released one, it either renames a section in the wrong position or concludes there is nothing to ship. A release-check trigger fired after #85 merged produced no new tag, which is consistent with the latter — so #85's fix is on master but cannot currently be released.

Why the usual guard missed it

The changelog-fold check (git diff origin/master -- CHANGELOG.md | grep -E '^[-+]## ') passes at push time, because on the branch ## Unreleased genuinely is the top section. It only becomes wrong when someone else's release lands above it — after the check has already run and passed.

Worth knowing: anchoring a new ## Unreleased relative to a specific released version is what creates the exposure. Anchoring it to the top of the section list would not have.

Change

Pure reordering — ## Unreleased moved above ## v0.111.0. Bullet text unchanged (git diff touches 4 lines, 2 of them the same bullet moving).

Verification

grep -n '^## ' CHANGELOG.md | head -4
# 11: ## Unreleased
# 15: ## v0.111.0
# 19: ## v0.110.0
# 23: ## v0.109.3

After merge, a release check should cut the version carrying #85's Phase 5.5 fix.

[ben-s-pull-request-reviewer]

The diff is a pure CHANGELOG.md reordering — ## Unreleased moved above ## v0.111.0. Per the changelog guide, ## Unreleased must go directly above the highest ## vX.Y.Z (newest version first). The post-change CHANGELOG is correctly ordered.

No code files changed. Step 4 is not applicable (no rule-relevant source files). The change is clean.

{
  "verdict": "approve",
  "summary": "CHANGELOG-only reorder placing `## Unreleased` above `## v0.111.0` — correct per changelog convention. No code changes.",
  "comments": [],
  "concerns_addressed": []
}