chore: auto upgrade uv.lock dependencies

[shenald-dev]

Upgraded dependencies to their latest compatible versions via uv lock --upgrade to improve security, performance, and maintainability. Verified tests and typechecks to ensure no regressions were introduced.

---

PR created automatically by Jules for task 10302111049234053032 started by @shenald-dev

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[shenald-dev]

Hey @shenald-dev, heads up — this PR has merge conflicts with main.

To fix:

git checkout jules-10302111049234053032-e99c9e68
git fetch origin && git merge origin/main

[shenald-dev]

Please resolve the merge conflicts with main before merging. After resolving, consider running uv sync to ensure the lock file is consistent and verify that the updated dependencies work as expected.

Reviewed — quality: high

[google-labs-jules]

Hey @shenald-dev, heads up — this PR has merge conflicts with main.

To fix:

git checkout jules-10302111049234053032-e99c9e68
git fetch origin && git merge origin/main

I have successfully resolved the merge conflicts with main and pushed the updated branch.

[shenald-dev]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s) (4 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-10302111049234053032-e99c9e68-1779336631102 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

[google-labs-jules]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s) (4 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-10302111049234053032-e99c9e68-1779336631102 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

I have successfully resolved the merge conflicts with main again and pushed the updated branch. Tests passed successfully.

[shenald-dev]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s) (4 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-10302111049234053032-e99c9e68-1779337953180 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

[google-labs-jules]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 1 file(s) (4 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-10302111049234053032-e99c9e68-1779337953180 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

I have successfully resolved the merge conflicts with main and pushed the updated branch. Tests passed successfully.

[shenald-dev]

Hey @shenald-dev, heads up — this PR has merge conflicts with main.

To fix:

git checkout jules-10302111049234053032-e99c9e68
git fetch origin && git merge origin/main

[google-labs-jules]

Hey @shenald-dev, heads up — this PR has merge conflicts with main.

To fix:

git checkout jules-10302111049234053032-e99c9e68
git fetch origin && git merge origin/main

I have successfully resolved the merge conflicts with main once again and pushed the updated branch. The tests passed successfully.

[shenald-dev]

Dependency updates look good. After merging, consider running uv sync in the main branch to ensure the lock file is consistent.

Reviewed — quality: high

[google-labs-jules]

Dependency updates look good. After merging, consider running uv sync in the main branch to ensure the lock file is consistent.

Reviewed — quality: high

Acknowledged. Thanks for the review.

[shenald-dev]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 5 file(s) (1 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-10302111049234053032-e99c9e68-1779411496200 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

[google-labs-jules]

@shenald-dev I went through the conflicts and resolved them — merged the changes from main into your branch. Resolved 5 file(s) (1 identical/safe files skipped).

⏳ CI needs to run on the new commits before merging. Will auto-merge on the next cycle if checks pass.

🔧 Used 3-way merge with ancestor context for more accurate resolution.

📦 A backup ref was created: refs/heads/conflict-backup-jules-10302111049234053032-e99c9e68-1779411496200 — you can restore from this if needed.

Take a look and let me know if anything looks off 👍

I have successfully resolved the merge conflicts with main once again and pushed the updated branch. The tests passed successfully.