chore: back-merge main into dev after v0.2.14 release (#207)

[w7-mgfcode]

Summary

Back-merges main into dev after the v0.2.14 release so dev carries the release-please version bump. Closes #207.

main has 3 commits dev lacks — the #201 release merge, chore(main): release 0.2.14, and the #206 Release-PR merge. The only content delta is the 3 release-managed files:

• .release-please-manifest.json → 0.2.14
• pyproject.toml → 0.2.14
• CHANGELOG.md — v0.2.14 release notes

0 conflicts — dev's tip is already a parent of main's history (via the #201 merge), so this is a clean fast-forward of the release commits onto dev.

⚠️ Merge as a merge commit — not squash

Merge with "Create a merge commit" (gh pr merge <N> --merge). Squashing would stop main from becoming an ancestor of dev and the next release PR would re-conflict (this exact trap cost an extra round with PR #203 → #204).

Summary by Sourcery

Back-merge the v0.2.14 release changes from main into dev so the development branch reflects the latest released version.

New Features:

• Document and record the v0.2.14 release that includes UI interactivity improvements, an AI admin console, and agent reliability fixes.

Enhancements:

• Bump project version metadata from 0.2.13 to 0.2.14 in configuration and release manifest files.

Documentation:

• Add changelog entry for v0.2.14 including new UI features and updated planning/agent documentation.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Back-merges main into dev to carry the v0.2.14 release metadata, updating release-managed versioning files and changelog entries with no functional code changes.

Flow diagram for back-merging main into dev to carry v0.2.14 metadata

flowchart LR
    subgraph main_branch[main]
        A[.release-please-manifest.json
        version 0.2.14]
        B[pyproject.toml
        version 0.2.14]
        C[CHANGELOG.md
        add 0.2.14 notes]
    end

    subgraph dev_branch[dev]
        D[Previous versions
        up to 0.2.13]
    end

    main_branch -- back-merge --> dev_branch
    D --> E[dev now carries
    0.2.14 metadata]

Loading

File-Level Changes

Change	Details	Files
Update project version to 0.2.14 across release-managed metadata files.	Bump project version field from 0.2.13 to 0.2.14 in the Python project configuration. Update the release-please manifest to record 0.2.14 as the current released version.	pyproject.toml .release-please-manifest.json
Add v0.2.14 release notes to the changelog.	Insert a new 0.2.14 section with feature bullets describing UI interactivity, AI admin console, and agent reliability fixes. Document new and relocated agent- and planning-related docs under the 0.2.14 entry.	CHANGELOG.md

Possibly linked issues

• chore: back-merge main into dev after v0.2.14 release #207: The PR cleanly back-merges main into dev, adding the v0.2.14 release version and changelog changes described.

---

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: 5f935623-0ccf-4f5c-8c4b-d1d35e2f8e9f

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/back-merge-main-after-v0214

---

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