Bump circulax to >=0.2.3

[cdaunt]

Bump the Circulax runtime dependency to >=0.2.3 and update uv.lock. Closes #321. Validation: uv lock --check; targeted tests 5 passed; git diff --check. Pre-commit unavailable because .pre-commit-config.yaml is absent.

Summary by Sourcery

Update Python project dependencies to require Circulax runtime version 0.2.3 or newer and refresh the uv lockfile accordingly.

Enhancements:

• Align dependency constraints with Circulax runtime >=0.2.3 to support newer runtime capabilities.

Build:

• Regenerate uv.lock to reflect updated dependency requirements.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the project’s runtime dependencies by adding Circulax with a minimum version requirement and regenerating the uv.lock file to reflect the new dependency set.

File-Level Changes

Change	Details	Files
Add Circulax as a required runtime dependency with a minimum version of 0.2.3.	Insert Circulax into the main dependencies list alongside existing runtime packages. Specify a minimum compatible version constraint (>=0.2.3) for Circulax to ensure use of recent runtime features and fixes.	pyproject.toml
Regenerate uv.lock to align the lockfile with the updated dependency graph.	Refresh resolved package versions and dependency tree to incorporate the new Circulax runtime requirement. Ensure lockfile integrity for reproducible installs after dependency changes.	uv.lock

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#321	Update the project’s Circulax dependency requirement to circulax>=0.2.3 in the main configuration (pyproject.toml).	✅
#321	Regenerate and update the uv.lock file so that the lockfile reflects the new Circulax dependency version constraint.	✅

---

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.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider adding an upper bound (e.g., <0.3) to the circulax dependency instead of a bare >=0.2.3 to reduce the risk of future breaking changes from newer major/minor releases.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider adding an upper bound (e.g., `<0.3`) to the `circulax` dependency instead of a bare `>=0.2.3` to reduce the risk of future breaking changes from newer major/minor releases.

---

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

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.