[vvillait88]

Summary

Maintenance sweep: relocks the dev tools, pytest 9.1.1 to 9.2.0, ruff 0.17.2 to 0.17.3 and ty 0.0.92 to 0.0.94 (uv lock --upgrade, which moves nothing else). OSV over uv.lock is clean, and Dependabot's last runs succeeded.

Worked with: Varun.

No release: only dev-group tools moved, which are not in the wheel or sdist.

Type of change

• Bug fix (no breaking change)
• New feature (no breaking change)
• Breaking change (existing callers must update)
• Docs, tests, or internal maintenance only

Public API

None.

Test plan

As CI runs them: ruff check ., ruff format --check ., ty check agentscore/, vulture (min confidence 80) and pytest tests/ (172 passed, 2 skipped), all exit 0. osv-scanner scan --lockfile uv.lock reports no issues.

Checklist

• Tests cover the new behavior, and the suite passes locally (no behavior change; suite passes)
• Lint, format, and type checks pass
• Docs and README examples updated if the public surface changed (no public surface change)
• No secrets, credentials, or personal data in the diff or the tests

[vvillait88]

Review (fresh context, read-only)

Verdict: approve, no findings.

• Only uv.lock changes, and only three versions move in it: pytest 9.1.1 to 9.2.0, ruff 0.17.2 to 0.17.3, ty 0.0.92 to 0.0.94. pyproject.toml is untouched.
• "No release" holds by effect: the wheel's runtime requirements come from [project].dependencies (httpx, certifi), which did not change, and the lock is not shipped in the wheel or sdist. pytest sits in the dev extra with an unchanged >=7.0 range, so its published metadata is identical too.
• I did not re-run the gates here; CI is the gate for that.