chore(repo): back-merge v0.2.21 release commits into dev (#366)

[w7-mgfcode]

Back-merges the v0.2.21 release commits from main into dev so main becomes an ancestor of dev (prevents future dev → main release-PR conflicts).

Brings in 3 commits dev lacks:

• 2712e49 chore(main): release 0.2.21 (bumps manifest + pyproject + CHANGELOG to 0.2.21)
• the release: promote dev to main for v0.2.21 — forecast champion selector A–C #364 and chore(main): release 0.2.21 #365 merge commits

After this, dev reads 0.2.21 in .release-please-manifest.json / pyproject.toml, matching main.

Closes #366.

⚠️ Merge with --merge (a real merge commit), NOT squash — squashing would not make main an ancestor of dev, which is the entire point of the back-merge.

Summary by Sourcery

Back-merge the 0.2.21 release into the dev branch so versioning and changelog align with main.

New Features:

• Introduce the 0.2.21 release featuring the forecast champion selector backend and UI slices across API, DB, and UI layers.

Bug Fixes:

• Include 0.2.21 stability fixes for agents, API, RAG, and UI, improving Ollama chat handling, experiment guardrails, and feature frame/version behavior.

Documentation:

• Bring in 0.2.21 documentation updates covering forecast champion selector design, showcase screenshots, and embedding auth behavior.

[sourcery-ai]

Reviewer's Guide

Back-merges the v0.2.21 release from main into dev so their histories align, updating dev’s version metadata and changelog to match main without introducing new functional code beyond the already-released changes.

File-Level Changes

Change	Details	Files
Align dev branch release metadata and changelog with v0.2.21 from main.	Add 0.2.21 release entry to the top of the changelog, including features, bug fixes, and documentation sections copied from main Bump the Python package version from 0.2.20 to 0.2.21 in the project configuration Update the release-please manifest to reference version 0.2.21 so future automated releases stay in sync	CHANGELOG.md pyproject.toml .release-please-manifest.json

Possibly linked issues

• #0: The PR performs the exact v0.2.21 main→dev back-merge with a real merge commit as the issue requests.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 19d867ec-31ce-4dfd-bb2a-1e864a475967

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/backmerge-v0.2.21

---

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

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}