chore: expand CHANGELOG.md to Keep-a-Changelog 1.1.0 format

[KooshaPari]

User description

Expands stub CHANGELOG.md to full Keep-a-Changelog 1.1.0 skeleton with all standard sections (Added/Changed/Deprecated/Removed/Fixed/Security). Companion to #209 CODEOWNERS expansion pattern.

Note

Low Risk
Low risk documentation-only change that does not affect runtime behavior or tooling configuration.

Overview
Updates CHANGELOG.md to follow the Keep a Changelog 1.1.0 template, rewriting the intro and expanding the [Unreleased] section to include the standard headings (Added/Changed/Deprecated/Removed/Fixed/Security).

Also normalizes existing Added items into consistent bullet formatting and adds the [Unreleased] compare link.

^{Reviewed by Cursor Bugbot for commit 9a8fc51. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

CodeAnt-AI Description

Expand the changelog to the standard Keep a Changelog layout

What Changed

• Updated the changelog intro wording to match the standard Keep a Changelog format
• Expanded the Unreleased section to include the full set of standard headings: Added, Changed, Deprecated, Removed, Fixed, and Security
• Cleaned up the existing release notes into consistent bullet formatting and added the Unreleased compare link

Impact

✅ Clearer release notes
✅ Easier tracking of upcoming changes
✅ Consistent changelog format

🔄 Retrigger CodeAnt AI Review

Details

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[coderabbitai]

Warning

Rate limit exceeded

@KooshaPari has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 58 minutes and 21 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 21 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 7e11f950-baeb-423e-aa8f-89d258a9d719

📥 Commits

Reviewing files that changed from the base of the PR and between a30dcf7 and 9a8fc51.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/expand-changelog

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch chore/expand-changelog

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[codeant-ai]

CodeAnt AI is running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Sequence Diagram

This PR restructures the changelog to follow the Keep a Changelog 1.1.0 format, adding standard Unreleased sections and a compare link to support clear, consistent release note preparation.

sequenceDiagram
    participant Developer
    participant Changelog
    participant ProjectUsers

    Developer->>Changelog: Add upcoming changes under Unreleased sections
    Developer->>Changelog: Use Unreleased compare link when preparing a release
    Changelog-->>ProjectUsers: Present structured release notes for each version
    ProjectUsers->>Changelog: Review Added, Changed, Deprecated, Removed, Fixed, Security items

Loading

---

Generated by CodeAnt AI

[codeant-ai]

🟠 Architect Review — HIGH

The new [Unreleased] compare link points to HEAD...HEAD, which always yields an empty diff and cannot show changes since the last release.

Suggestion: Point [Unreleased] to compare from the latest released tag (or an explicit bootstrap tag) to HEAD, and update this link as part of each release so it remains meaningful.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.

**Path:** CHANGELOG.md
**Line:** 25:25
**Comment:**
	*HIGH: The new `[Unreleased]` compare link points to `HEAD...HEAD`, which always yields an empty diff and cannot show changes since the last release.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

[codeant-ai]

CodeAnt AI finished running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI is running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Sequence Diagram

This PR restructures the changelog to follow the Keep a Changelog 1.1.0 template, defining how upcoming changes are recorded under Unreleased sections and later promoted to versioned release notes.

sequenceDiagram
    participant Maintainer
    participant Changelog
    participant Repository
    participant Reader

    Maintainer->>Changelog: Record changes under Unreleased sections
    Changelog-->>Maintainer: Structured list of upcoming changes

    Maintainer->>Changelog: Create new version entry from Unreleased
    Maintainer->>Repository: Commit changelog and tag release
    Reader->>Changelog: Read versioned release notes

Loading

---

Generated by CodeAnt AI

[codeant-ai]

🟠 Architect Review — HIGH

The [Unreleased] compare link uses HEAD...HEAD, which always produces an empty diff on GitHub and never shows unreleased changes.

Suggestion: Change the [Unreleased] link to compare from the latest release tag to HEAD (once a tag exists), or omit the compare link until an initial release tag is available.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.

**Path:** CHANGELOG.md
**Line:** 25:25
**Comment:**
	*HIGH: The `[Unreleased]` compare link uses `HEAD...HEAD`, which always produces an empty diff on GitHub and never shows unreleased changes.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

[codeant-ai]

CodeAnt AI finished running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI is running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Sequence Diagram

This PR restructures the changelog to follow the Keep a Changelog 1.1.0 template, standardizing how unreleased and future release notes are organized across sections like Added, Changed, Deprecated, Removed, Fixed, and Security.

sequenceDiagram
    participant Maintainer
    participant ChangelogFile
    participant ReleaseProcess
    participant Reader

    Maintainer->>ChangelogFile: Add upcoming changes under Unreleased sections
    Maintainer->>ChangelogFile: Normalize entries in standard headings
    ReleaseProcess->>ChangelogFile: Move Unreleased items to new version section
    Maintainer->>ChangelogFile: Update Unreleased compare link
    Reader->>ChangelogFile: Review grouped changes and upcoming updates

Loading

---

Generated by CodeAnt AI

[codeant-ai]

🟠 Architect Review — HIGH

The [Unreleased] compare link points to HEAD...HEAD, which compares the same commit to itself and always produces an empty diff, so users clicking it cannot see unreleased changes.

Suggestion: Update the [Unreleased] link to compare the latest release tag to HEAD (e.g., vX.Y.Z...HEAD) and adjust the base tag with each release so the link consistently reflects pending changes.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.

**Path:** CHANGELOG.md
**Line:** 25:25
**Comment:**
	*HIGH: The `[Unreleased]` compare link points to `HEAD...HEAD`, which compares the same commit to itself and always produces an empty diff, so users clicking it cannot see unreleased changes.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

[codeant-ai]

CodeAnt AI finished running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

CodeAnt AI is running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

Sequence Diagram

This PR restructures the changelog to follow the Keep a Changelog 1.1.0 template, adding standard Unreleased sections and a compare link to support consistent future release notes.

sequenceDiagram
    participant Developer
    participant Changelog
    participant ReleaseProcess

    Developer->>Changelog: Record upcoming changes under Unreleased sections
    Changelog-->>Developer: Provide standardized Added/Changed/Deprecated/Removed/Fixed/Security structure
    ReleaseProcess->>Changelog: Read Unreleased entries for next release
    Changelog-->>ReleaseProcess: Return grouped changes by category
    ReleaseProcess->>Changelog: Use Unreleased compare link to compute diff
    Changelog-->>ReleaseProcess: Provide changes between latest release and current head

Loading

---

Generated by CodeAnt AI

[codeant-ai]

🟠 Architect Review — HIGH

The [Unreleased] compare link uses HEAD...HEAD, which always yields an empty GitHub diff and therefore never shows the actual unreleased changes.

Suggestion: Update the [Unreleased] link to compare from the latest released tag to HEAD (and adjust it as new releases are cut), or omit the compare link until the first release tag exists.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.

**Path:** CHANGELOG.md
**Line:** 25:25
**Comment:**
	*HIGH: The `[Unreleased]` compare link uses `HEAD...HEAD`, which always yields an empty GitHub diff and therefore never shows the actual unreleased changes.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

[codeant-ai]

CodeAnt AI finished running the review.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn