Reconcile generated changelog with published release history #148

Problem

The current generated CHANGELOG starts with 0.1.0 - Unreleased and omits the published 0.1.x patch history. PyPI and GitHub both show 0.1.0 published on 2026-08-09 and the current published version 0.1.12 on 2026-09-24.

The source is release/changelog.json. The generator reproduces that stale state, and the existing historical-compatibility test requires exactly the original version set, preventing later release entries from being added.

Evidence and limits

• Published 0.1.0 and 0.1.12 provide publication dates and source comparisons.
• PyPI metadata independently confirms the published versions and upload dates.
• v0.1.2 has an annotated tag dated 2026-08-11. No matching release or artifact is currently listed in the GitHub/PyPI records. Do not describe that as a verified publication or invent its removal history.

Repair

Reconcile the structured release history with the actual records and regenerate CHANGELOG through validation/generate_changelog.py. Preserve the older beta history. Add clearly marked unreleased notes for the verified maintenance changes, including numerical compatibility limits, without creating a release, tag or deployment.

Allow additional release entries in the historical-compatibility test while retaining its requirement that the original compatibility history cannot disappear. Show that the existing test rejects valid additions, the correction accepts them, and removal of required historical compatibility data still fails. Run focused changelog/docs/hooks checks and current-head supported CI.

AI assistance

Codex found the stale generated history, inspected the generator and test, and checked the actual GitHub/PyPI release records. Codex is preparing the correction and verification; no independent human review is asserted.