chore: organize CHANGELOG for v0.0.3 release

[hyunhee-jo]

Objective

CHANGELOG.md had all entries under [Unreleased] despite v0.0.1 and v0.0.2
already being published to PyPI. This makes it impossible for users to
see what changed between versions.

Approach

Reorganize CHANGELOG into proper Keep-a-Changelog structure with v0.0.1,
v0.0.2, and v0.0.3 sections, each listing the relevant changes from git
history. v0.0.3 covers all work since v0.0.2: demo notebook, governance
files, lint config/CI, and code formatting.

Evidence

Verified commit history against each version tag:

Version	Tag commits	CHANGELOG entries match
v0.0.1	cb85b3b..a01da1f (initial + workflow fixes)	Yes — Added section
v0.0.2	ceb5aaa (error messages)	Yes — Fixed section
v0.0.3	4aae3bc..cf80633 (docs, governance, lint)	Yes — Added/Changed/Fixed

Summary by CodeRabbit

• New Features

  • Added demo notebook
  • Added GitHub issue and pull request templates
  • Added security and editor configuration files

• Bug Fixes

  • Fixed RAG pipeline to no longer require token authentication
  • Improved error messages for missing input files and Java runtime issues

• Chores

  • Implemented CI lint workflow with code formatting standards

[coderabbitai]

Warning

Rate limit exceeded

@hyunhee-jo has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 58 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 19 minutes and 58 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: f92658bd-9d80-4ed1-bcb5-14b9b16ecb72

📥 Commits

Reviewing files that changed from the base of the PR and between 7ea6405 and 81c3a81.

📒 Files selected for processing (1)

• CHANGELOG.md

Walkthrough

Added changelog entries for versions 0.0.3, 0.0.2, and 0.0.1, documenting new features (demo notebook, CI lint workflow, config files), changes (line-length reformatting), and fixes (RAG pipeline token requirement, error messages).

Changes

Cohort / File(s)	Summary
Changelog Documentation CHANGELOG.md	Added release notes for versions 0.0.3, 0.0.2, and 0.0.1 with categorized entries for added features, changed items, and bug fixes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: add SECURITY.md, CODEOWNERS, and .editorconfig #6: This changelog explicitly records the addition of SECURITY.md and .editorconfig files that were introduced in that PR.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and clearly summarizes the main change: organizing the CHANGELOG for v0.0.3 release, which matches the changeset's focus of restructuring CHANGELOG.md into version-specific sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 7-22: The issue is missing blank lines after subsection headings
in CHANGELOG.md causing markdownlint MD022; update the file so each subsection
heading (e.g., the "### Added", "### Changed", "### Fixed" entries and the "##
[0.0.2] - 2026-04-10" section header) is followed by a single blank line before
the list or paragraph that follows, ensuring lines immediately after those
headings (lines referenced around "Added", "Changed", "Fixed" and the version
header) contain an empty line to satisfy MD022.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2a8df78d-1997-4de4-b57e-fffcc091e2c1

📥 Commits

Reviewing files that changed from the base of the PR and between cf80633 and 7ea6405.

📒 Files selected for processing (1)

• CHANGELOG.md