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

[mergify]

✨ The pull request #349 has been manually updated. The pull request #342 has been re-embarked. ✨

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

This pull request has been created by Mergify to speculatively check the mergeability of [#342 + #349].
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
  • chore(deps): update pre-commit hook astral-sh/ruff-pre-commit to v0.15.12 #349
• files ~= .pre-commit-config.yaml
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

---
checking_base_sha: 03bbb7f9f3a9b9b850bbebbd279248984b95a963
previous_failed_batches: []
pull_requests:
  - number: 342
    scopes: []
  - number: 349
    scopes: []
scopes: []
...

[warestack]

🛡️ Warestack Governance Checks

No governance rules are configured for this repository yet.

Warestack lets your team define, enforce, and audit engineering standards directly on GitHub Pull Requests — without leaving your workflow.

Get started in 2 minutes:

1. Claim your Warestack profile to activate governance for MH0386/MH0386.github.io
2. Configure rules for PR quality, CI requirements, commit conventions, and more
3. Receive automated feedback on every PR

---

This message will disappear once your installation is linked to a Warestack account. It will not be posted again on future PRs once you've claimed your profile.

[deepsource-io]

DeepSource Code Review

We reviewed changes in a4ccdc8...fdcf154 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Python		Apr 21, 2026 6:19p.m.	Review ↗
Secrets		Apr 21, 2026 6:19p.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[sourcery-ai]

Reviewer's Guide

This PR refreshes CI tooling and Python/dev tooling versions by bumping multiple GitHub Actions pins, updating pre-commit hooks and Ruff/uv versions, and regenerating the lockfile to match.

File-Level Changes

Change	Details	Files
Update GitHub Actions pins for scripts, artifact handling, caching, and Pages uploads to newer versions.	Bump actions/github-script from v8 to v9 in the code-simplifier workflow for all script-driven steps Upgrade actions/upload-artifact from v7.0.0 to v7.0.1 in code-simplifier artifact upload steps, including detection and safe-output manifests Update actions/cache SHA for v5 in the deploy workflow cache step Upgrade actions/upload-pages-artifact from v4 to v5 in the deploy workflow upload step Bump actions/github-script from v8 to v9 in the agentics-maintenance workflow for discussion/issue/PR cleanup, permission checks, and operation runner	.github/workflows/code-simplifier.lock.yml .github/workflows/agentics-maintenance.yml .github/workflows/deploy.yml
Refresh local tooling and pre-commit configuration for uv and Ruff, including Python and dev dependency constraints.	Update uv-pre-commit hook revision from 0.11.3 to 0.11.7 and ruff-pre-commit from v0.15.9 to v0.15.11 in pre-commit config Tighten project Python requirement from >=3.14.3,<3.15 to >=3.14.4,<3.15 in pyproject.toml Increase dev dependency floor for Ruff from >=0.15.9 to >=0.15.10 in pyproject.toml Regenerate the uv.lock file to align with the updated toolchain and dependency constraints	.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