version up, runs, tsp eval

[ivylikethevine]

What's new

What changed and why

____________ used to [be/do/say] ____________ but now it [is/does/says] ____________ because of
____________.

Release note

none

Issue and discussion links

Link any relevant issues or discussions here.

Checklist

If one of these cannot be completed, give a justification.

• CI's checks pass locally (tests/ci_local.py, see docs/CONTRIBUTING.md)
• New behaviour has tests; coverage stays at 100%
• Affected docs are updated (README, and docs/CHANGELOG.md for user-facing changes)

AI disclosure

AI usage is allowed on this project, but "[agent] said _______" is not a valid excuse for problems
with the final product.

• (If applicable) This code was written with generative AI.
• (If yes to above) I have reviewed, understood, and stand behind this code as if it were
  entirely hand written.

[github-actions]

Annotation coverage on pydantic 2.13.5

	Typed as released	After --fix	After --fix --unsafe-fixes	Bindings
main	21.8%	50.5%	60.3%	3956
This PR	21.8%	50.4%	60.2%	3956
Change	+0.0 pts	-0.1 pts	-0.1 pts	+0

A check in one process takes 2.65s with this PR and 2.62s with main (+0.9%), each the median of 5 runs on this runner.

Each side fixes with its own constricter; this PR counts both, with --coverage and all-scopes. Measured at 00c83ea by this run.