[cd-dspy] Swap pip → uv in CI workflow

[haasonsaas]

Summary

• Replace python -m pip install --upgrade pip && python -m pip install -e .[dev] in both test and coq-smoke jobs with astral-sh/setup-uv@v8.1.0 (pinned by full SHA) followed by uv pip install --system -e '.[dev]'.
• No version pin changes, no --user.

Why

Hardens CI against the PyPI partial-read timeouts that took down post-merge evals on main in evalops/maestro-internal#1492. uv resumes partial downloads and retries on connection drops by default, removing a class of transient failures that pip cannot recover from. This workflow has no CLI tool installs, so no uv tool install retry wrapper is needed — that pattern lands when CLI tools show up.

Files changed

• .github/workflows/ci.yml

Test plan

• Confirm all three matrix shards (3.10, 3.11, 3.12) of test pass Install dependencies.
• Confirm coq-smoke passes Install Python dependencies and the smoke test still runs.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Low risk workflow-only change that alters how dependencies are installed in CI; main potential issue is uv behavior differences or setup action failures affecting CI runs.

Overview
CI now installs Python dependencies via uv instead of pip in both the test and coq-smoke jobs.

The workflow adds an astral-sh/setup-uv step (pinned SHA) and replaces the previous pip upgrade/install command with uv pip install --system -e '.[dev]'.

^{Reviewed by Cursor Bugbot for commit 1b97570. Bugbot is set up for automated code reviews on this repo. Configure here.}