Dedicated release notes hub with AI crawler support

What shipped

The publishing surface now separates factual release notes from broader narrative blog content.

• A canonical release hub lives at /releases.
• A /changelog alias resolves to the same release-note surface.
• Release pages clearly state product name, exact feature, release date, and what the update replaces.

AI retrieval and crawlability

The release hub is designed for real-time retrieval rather than hoping future model-training snapshots remember product updates correctly.

• robots and sitemap routes explicitly expose the update surface.
• Release notes use direct semantic headings and fact blocks instead of marketing-heavy copy.
• Machine-readable discovery is exposed through JSON documents.

What this replaces

This release replaces a publishing model where major updates could be buried inside ad hoc posts, making them harder for both users and AI systems to discover reliably.