📘 DOCS-#92: Single-source release notes from CHANGELOG.md

[FernandoCelmer]

Description

Two changelogs drifted: CHANGELOG.md still listed 1.0.0 features under Unreleased, while docs/nav/development/release-notes.md had the real history. Now there is one:

• CHANGELOG.md — rewritten per Keep a Changelog with real versions (1.1.0, 1.0.1, 1.0.0), dates, issue links and compare/release links. Adds the v1.1.0 section (Add optional MCP server (email-profile[mcp]) #88 MCP server and plugin, Bump mkdocs-material to 9.7.7 (CVE-2026-73295, DOM XSS in search) #90 mkdocs-material CVE, security hardening).
• docs/nav/development/release-notes.md — now just {! CHANGELOG.md !} via mdx_include, so the site renders the root file. mkdocs build verified; headings 1.1.0, 1.0.1, 1.0.0 present.

pyproject.toml Changelog URL keeps pointing at the docs page, which is unchanged for readers.

Issue: 📌 ISSUE — Refs #92

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation updated (documentation was updated and published)

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[FernandoCelmer]

Superseded: the changelog work landed directly on develop/master (1f6d7b9…c3d1b95). Nothing left here.