chore(release): fix changelog section for v0.14.7

[steipete]

Release validator requires exactly one dated level-two section matching the repo's header convention.

[clawsweeper]

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

[clawsweeper]

Codex review: needs real behavior proof before merge. Reviewed August 14, 2026, 4:08 PM ET / 20:08 UTC.

ClawSweeper review

What this changes

The PR consolidates duplicate v0.14.7 changelog headings into one dated section while retaining all three release notes.

Merge readiness

⚠️ Ready for maintainer review - 2 items remain

Keep this PR open: current main has two v0.14.7 headings, and this focused changelog-only patch restores the required single dated section without changing the release-note content.

Priority: P3
Reviewed head: 36b643fc4c99e76a65a7cfd7d42ee8307d531e9b

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	The patch is narrowly scoped and directly corrects the duplicate structure present on current main.
Proof confidence	🌊 off-meta tidepool	Not applicable: All changed content is in CHANGELOG.md, so runtime behavior proof is not required.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: All changed content is in CHANGELOG.md, so runtime behavior proof is not required.
Evidence reviewed	5 items	Duplicate current-main heading: Current main contains two separate level-two v0.14.7 headings, dated 2026-08-14 and 2026-08-08. Release documentation contract: The publishing guide requires a dated versioned changelog section and later checks release notes against that section. Focused corrective diff: The PR removes the duplicate heading and blank line while retaining the existing v0.14.7 note text under one heading.
Findings	None	None.
Security	None	None.

How this fits together

The changelog supplies the dated release notes used by the unified release process. Its version heading structure determines which notes are associated with a release.

flowchart LR
  A[Release changes] --> B[Changelog entry]
  B --> C[Version heading validation]
  C --> D[Unified release workflow]
  D --> E[Published release notes]

Loading

Before merge

• Add real behavior proof - Not applicable: All changed content is in CHANGELOG.md, so runtime behavior proof is not required.
• Complete next step (P2) - No discrete repair task remains; this focused PR needs ordinary review and its normal checks.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Changelog structure	1 file affected; +1 / -3	The complete patch is limited to consolidating a duplicate release heading.

Technical review

Best possible solution:

Merge the changelog-only correction through the unified release workflow, retaining one dated v0.14.7 release section.

Do we have a high-confidence way to reproduce the issue?

Yes: current main visibly contains two v0.14.7 level-two headings, and the branch leaves one dated heading with all three notes.

Is this the best way to solve the issue?

Yes: consolidating the duplicate heading is the narrowest maintainable solution and preserves the release-note content.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 67e034c85127.

Labels

Label changes:

• add P3: This is a low-risk release-documentation correction without runtime behavior change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: All changed content is in CHANGELOG.md, so runtime behavior proof is not required.

Label justifications:

• P3: This is a low-risk release-documentation correction without runtime behavior change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: All changed content is in CHANGELOG.md, so runtime behavior proof is not required.

Evidence

What I checked:

• Duplicate current-main heading: Current main contains two separate level-two v0.14.7 headings, dated 2026-08-14 and 2026-08-08. (CHANGELOG.md:3, 67e034c85127)
• Release documentation contract: The publishing guide requires a dated versioned changelog section and later checks release notes against that section. (docs/publishing.md:39, 67e034c85127)
• Focused corrective diff: The PR removes the duplicate heading and blank line while retaining the existing v0.14.7 note text under one heading. (CHANGELOG.md:3, 36b643fc4c99)
• Release-area history: Recent changelog history shows the v0.14.7 preparation and Go-floor updates were authored by Peter Steinberger, establishing current release-area ownership. (CHANGELOG.md:3, 67e034c85127)
• Advisory review limitation: The repository autoreview helper was invoked for the PR commit but could not create an isolated temporary workspace in this read-only environment; direct source and diff inspection completed. (36b643fc4c99)

Likely related people:

• steipete: Current-main changelog history attributes the v0.14.7 release-preparation work to Peter Steinberger, whose GitHub identity is steipete. (role: recent release-area contributor; confidence: high; commits: 67e034c85127, 9b3fec5b39d7, e3e8b09d8f73; files: CHANGELOG.md)
• Vincent Koc: Changelog history shows substantial earlier release-documentation work by Vincent Koc. (role: adjacent release-area contributor; confidence: medium; commits: 651aca6543cc, 44849e6aef33; files: CHANGELOG.md, docs/publishing.md)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.