merge queue: embarking main (a4ccdc8), #348, #337, #344, #370, #371, #372, #373, #349 and #342 together

[mergify]

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (a4ccdc8), #348, #337, #344, #370, #371, #372, #373, #349 and #342 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #342.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule pre-commit Updates for merge:

• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Required conditions to stay in the queue:

• author = renovate[bot]
  • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.11.11 #342
• files ~= .pre-commit-config.yaml
  • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.11.11 #342
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.11.11 #342
  • check-skipped = Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.11.11 #342
  • check-success = Mergify Merge Protections
    • chore(deps): update pre-commit hook astral-sh/uv-pre-commit to v0.11.11 #342

---
checking_base_sha: b4f9f3db2d355769509cdabc58cbb03b4d9a2ae8
previous_failed_batches: []
pull_requests:
  - number: 342
    scopes: []
scopes: []
...

[sourcery-ai]

Reviewer's Guide

This PR is a Mergify merge-queue batch that primarily refreshes CI tooling by bumping GitHub Actions pins, pre-commit hook versions, and Python/dev-tooling constraints to newer patch releases, with no functional application code changes.

Flow diagram for updated deploy workflow

flowchart TD
  Trigger[GitHub push to main or workflow_dispatch]
  Checkout[Checkout repository]
  CacheWeb[Cache .web directory using actions/cache@v5]
  SetupPython[Set up Python and dependencies]
  Build[Run uv and reflex to build frontend]
  UploadArtifact[Upload static site using actions/upload-pages-artifact@v5]
  DeployJob[Deploy to GitHub Pages]

  Trigger --> Checkout --> CacheWeb --> SetupPython --> Build --> UploadArtifact --> DeployJob

Loading

File-Level Changes

Change	Details	Files
Update CI workflows and development tooling to newer pinned versions for GitHub Actions, pre-commit hooks, and Python/dev dependencies.	Bump actions/github-script from v8 to v9 across automation workflows, keeping existing scripts and env usage intact. Upgrade actions/upload-artifact, actions/cache, and actions/upload-pages-artifact to newer pinned SHAs within the same major versions. Refresh pre-commit hooks for uv-pre-commit and ruff-pre-commit to newer revisions, retaining the same hook IDs and arguments. Tighten Python version requirement in pyproject.toml to >=3.14.4 and bump the minimum ruff dev dependency to 0.15.10. Regenerate or update the uv.lock file to match the new tooling and dependency constraints.	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml .pre-commit-config.yaml pyproject.toml uv.lock

---

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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud