[pre-commit.ci] pre-commit autoupdate

[pre-commit-ci]

updates:

• github.com/astral-sh/ruff-pre-commit: v0.16.1 → v0.16.2
• github.com/facebook/pyrefly-pre-commit: 1.2.0 → 1.3.0.dev1
• github.com/rvben/rumdl-pre-commit: v0.2.49 → v0.2.53
• github.com/astral-sh/ty-pre-commit: v0.0.65 → v0.0.69

Summary by Sourcery

Update pre-commit hook versions to use newer releases of existing linters and formatters.

Build:

• Bump ruff-pre-commit hook from v0.16.1 to v0.16.2 in the pre-commit configuration.
• Bump pyrefly-pre-commit hook from 1.2.0 to 1.3.0.dev1 in the pre-commit configuration.
• Bump rumdl-pre-commit hook from v0.2.49 to v0.2.53 in the pre-commit configuration.
• Bump ty-pre-commit hook from v0.0.65 to v0.0.69 in the pre-commit configuration.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
.pre-commit-config.yaml	22% smaller

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the versions of several pre-commit hooks (ruff, pyrefly, rumdl, ty) in .pre-commit-config.yaml to their newer releases, without changing hook configuration or adding/removing hooks.

File-Level Changes

Change	Details	Files
Update pinned versions of Python-related pre-commit hooks to newer releases.	Bump ruff-pre-commit from v0.16.1 to v0.16.2 for linting/formatting hooks. Bump facebook pyrefly-pre-commit from 1.2.0 to 1.3.0.dev1 for the pyrefly-check hook. Bump rumdl-pre-commit from v0.2.49 to v0.2.53 for the rumdl-fmt hook. Bump ty-pre-commit from v0.0.65 to v0.0.69 for the ty hook.	.pre-commit-config.yaml

---

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.

[codescene-access]

No application code in the PR — skipped Code Health checks.

See analysis details in CodeScene

Quality Gate Profile: Customizable Safeguards
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.

[sourcery-ai]

Hey - I've left some high level feedback:

• The pyrefly hook is now pinned to a dev release (1.3.0.dev1); consider whether you really want to track a dev version here or prefer a stable tag to avoid unexpected behavior changes from pre-release updates.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The pyrefly hook is now pinned to a dev release (`1.3.0.dev1`); consider whether you really want to track a dev version here or prefer a stable tag to avoid unexpected behavior changes from pre-release updates.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.69%. Comparing base (7a095e8) to head (b4a2033).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop      #49   +/-   ##
========================================
  Coverage    99.69%   99.69%           
========================================
  Files           23       23           
  Lines         3301     3301           
========================================
  Hits          3291     3291           
  Misses          10       10           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[llamapreview]

LlamaPReview — No blocking issues found

Safe to merge: four dev hook pins are bumped, all current-head CI (including pre-commit) is green, and user-facing presets are untouched.

2 non-blocking findings retained — highest: Repository's own type check now uses a prerelease tag.

Review details and evidence

Priority	File	Finding	Evidence
P2	lang/py/preset.yaml	User-facing py preset still pins older ruff and pyrefly revisions	confirmed
P2	.pre-commit-config.yaml	Repository's own type check now uses a prerelease tag	confirmed

Finding details

P2 · User-facing py preset still pins older ruff and pyrefly revisions

lang/py/preset.yaml

The root .pre-commit-config.yaml moves to ruff v0.16.2 and pyrefly 1.3.0.dev1, but the shipped py preset at lang/py/preset.yaml still pins the older revisions. This PR does not update generated user configs, so user output is unchanged. If mirroring the root config is intended, a follow-up should bump the preset pins or automate syncing.

Owner action: Consider a follow-up to bump lang/py/preset.yaml to match the new hook revisions if the mirroring is intended.

Verification boundary: confirmed; scope: bounded reviewed context.

Material unknowns

• Upstream release notes for the four new hook revisions were not independently inspected. Without them, the green pre-commit CI run at head already validates the new revisions against this repository, so the merge decision is unaffected.
  • Check: No action required for merge; optional curiosity check on upstream notes.

LlamaPReview checks

• Inspected matching PR-head repository snippets in .claude/docs/adr/0001-hook-profile-categories.md, .pre-commit-config.yaml, lang/py/preset.yaml.
• Inspected matching PR-head repository snippets in lang/py/preset.yaml.
• Read bounded PR-head context from .pre-commit-config.yaml.

---

Automated review by LlamaPReview · Free for public open-source projects.

[llamapreview]

P2 | Confidence: Medium

The pyrefly-pre-commit hook is bumped to the development tag 1.3.0.dev1. Exact-head CI passes with it, and no repository policy requires stable tags. The residual risk is future churn or instability in the repository's own type checks if upstream dev releases regress. Maintainers preferring stable pins can switch back in a follow-up.

Owner action: Optionally switch pyrefly-pre-commit back to a stable release in a follow-up if stable pins are preferred.

Evidence: bounded PR-head context from .pre-commit-config.yaml.