### [DOCS-20] Add CHANGELOG.md with initial version history

[orunganiekan]

Points: 200
Labels: documentation, release

Background
There is no CHANGELOG.md tracking version history, breaking changes, or feature additions. Contributors and users cannot see what changed between versions.

Task
Create CHANGELOG.md following the Keep a Changelog format. Document all current features as an initial [Unreleased] section, organized by: Added, Changed, Fixed, Security. Include dates and version placeholders.

Key files

• CHANGELOG.md (new)

Acceptance criteria

• Follows Keep a Changelog format
• Initial [Unreleased] section covers all existing features
• Organized into Added / Changed / Fixed / Security categories
• Each entry is one line with enough context to understand the change
• Links to relevant PRs or issues where available

[TheWeirdDee]

@TheWeirdDee has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I want to work on this because a CHANGELOG that actually reflects what the project does is only useful if someone reads the codebase carefully before writing it — not just scaffolds the format. I'll go through the existing features and commits, document them accurately under the right categories, and set up the structure so future entries are easy to add correctly.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @TheWeirdDee to this issue.

[ayo-ola0710]

@ayo-ola0710 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi , can i please handle these for you please , will delive asap

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayo-ola0710 to this issue.

[bartmedad-hub]

@bartmedad-hub has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

i would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bartmedad-hub to this issue.

[drips-wave]

Congratulations, @bartmedad-hub! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @bartmedad-hub: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊