fix: add --project flag to uv entrypoint for GitHub Actions compatibility

[jmeridth]

Problem

The uv migration introduced a runtime regression in the Docker image. GitHub Actions' Docker container runner overrides the working directory to /github/workspace via --workdir, which causes uv run to not find the pyproject.toml at /action/workspace. It falls back to system Python (which has no packages installed), resulting in:

ModuleNotFoundError: No module named 'github3'

Fix

Add --project /action/workspace to the ENTRYPOINT so uv always discovers the project and its .venv regardless of the runtime working directory.

Testing

Verified locally with Docker:

Test	Outcome
Before fix (--workdir /github/workspace)	ModuleNotFoundError: No module named 'github3' ❌
After fix (--project /action/workspace)	Imports succeed, runs correctly ✅

[Copilot]

Pull request overview

Fixes a runtime regression in the Docker-based GitHub Action caused by GitHub Actions overriding the container working directory, which prevented uv run from discovering the project and virtual environment.

Changes:

• Updates the Docker image ENTRYPOINT to pass --project /action/workspace to uv run so dependency resolution is independent of the runtime working directory.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.