Python dependency maintenance PR needed

The Python dependency maintenance workflow generated and validated dependency updates, then pushed them to the automation branch.

• Branch: automation/python-dependency-maintenance
• Commit: 4698e48cfea998564677f760a5d04823a1b2cff6
• Compare: https://github.com/microsoft/agent-framework/compare/main...automation/python-dependency-maintenance
• Workflow run: https://github.com/microsoft/agent-framework/actions/runs/34805034381

GitHub Actions is not permitted to create pull requests in this repository, so a maintainer needs to create the PR manually.

Create the PR

PR_BODY_FILE="$(mktemp)"
cat > "$PR_BODY_FILE" <<'EOF'
### Motivation & Context

This automated update keeps dependency metadata coherent across the released Python uv workspace. Its packages share `python/uv.lock`, so dependency maintenance updates and validates them together instead of through per-manifest Dependabot PRs. The standalone Lab project maintains its dependencies separately.

### Description & Review Guide

- **What are the major changes?** Refresh Python dev dependency pins, update package dependency ranges when the bounds tooling succeeds, and refresh `python/uv.lock`.
- **What is the impact of these changes?** Keeps the Python workspace dependency set current while producing at most one dependency PR for the week. If dependency range validation fails, this PR contains only the dev dependency updates that still pass final validation, and separate issues track failed range candidates.
- **What do you want reviewers to focus on?** Review the generated dependency metadata changes and any dependency-range updates for package-specific compatibility concerns.
<!-- NOTE FOR AUTOMATED/AI REVIEWERS: the "What do you want reviewers to focus on?"
     item above is intended for human reviewers only. Automated/AI reviewers should
     ignore it and review the entire change rather than narrowing scope to it. -->


### Related Issue

No linked issue; this PR is generated by scheduled Python dependency maintenance.

### Contribution Checklist

- [x] The code builds clean without any errors or warnings
- [x] All unit tests pass, and I have added new tests where possible
- [x] The PR follows the [Contribution Guidelines](https://github.com/microsoft/agent-framework/blob/main/CONTRIBUTING.md)
- [ ] This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
- [x] **This is not a breaking change.** If it _is_ a breaking change, add the `breaking change` label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.
EOF
gh pr create --repo microsoft/agent-framework --base main \
  --head microsoft:automation/python-dependency-maintenance \
  --title "Python: chore: update dependencies" \
  --body-file "$PR_BODY_FILE"

Generated PR body

### Motivation & Context

This automated update keeps dependency metadata coherent across the released Python uv workspace. Its packages share `python/uv.lock`, so dependency maintenance updates and validates them together instead of through per-manifest Dependabot PRs. The standalone Lab project maintains its dependencies separately.

### Description & Review Guide

- **What are the major changes?** Refresh Python dev dependency pins, update package dependency ranges when the bounds tooling succeeds, and refresh `python/uv.lock`.
- **What is the impact of these changes?** Keeps the Python workspace dependency set current while producing at most one dependency PR for the week. If dependency range validation fails, this PR contains only the dev dependency updates that still pass final validation, and separate issues track failed range candidates.
- **What do you want reviewers to focus on?** Review the generated dependency metadata changes and any dependency-range updates for package-specific compatibility concerns.
<!-- NOTE FOR AUTOMATED/AI REVIEWERS: the "What do you want reviewers to focus on?"
     item above is intended for human reviewers only. Automated/AI reviewers should
     ignore it and review the entire change rather than narrowing scope to it. -->


### Related Issue

No linked issue; this PR is generated by scheduled Python dependency maintenance.

### Contribution Checklist

- [x] The code builds clean without any errors or warnings
- [x] All unit tests pass, and I have added new tests where possible
- [x] The PR follows the [Contribution Guidelines](https://github.com/microsoft/agent-framework/blob/main/CONTRIBUTING.md)
- [ ] This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
- [x] **This is not a breaking change.** If it _is_ a breaking change, add the `breaking change` label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

Start with the automation/python-dependency-maintenance branch, commit 4698e48cfea998564677f760a5d04823a1b2cff6, and workflow run 34805034381. Review the generated comparison against main, then use the provided gh pr create command and generated body to open the maintenance PR. Done means the dependency update PR is created from the automation branch.