Prep for v0.2.0 release

[brews]

I bumped the package version with uv version --bump=minor.

I updated the relevant section and links in CHANGELOG.md. Don't forget to update the URL in the links on the bottom of the page.

...Should start linking to PRs and contributors in CHANGELOG.md once things settle down.

After this merges, I'll go make a release in the GitHub web UI. I will create a new "v0.2.0" tag off the main branch. I'll copy the section of the CHANGELOG for this release and paste it as the release title and description. I'll hit the little button that adds an announcement to GH discussions for the release.

CI should push the release's published package to PyPI. (...Unless I forgot to update something after the org move.🤞)

After the release is published. I will check that CI pushed the package to PyPI successfully. If everything looks good I will do a new commit or PR for "post-release cleanup". This is usually just adding a new "Unreleased" section to the top of CHANGELOG.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.91%. Comparing base (68dbd96) to head (fcfb7aa).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #27   +/-   ##
=======================================
  Coverage   97.91%   97.91%           
=======================================
  Files           3        3           
  Lines          48       48           
=======================================
  Hits           47       47           
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.