Sync uv.lock to 0.2.3

b64f6a1 regenerated the lock for the 3.9 floor before bumping the version in
pyproject.toml, so the lock kept recording 0.2.2. CI runs uv sync --frozen,
which skips the freshness check, so this never surfaced -- but it reappeared
as a dirty working tree after any uv command, and would fail uv lock --check.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: jeromechoo