build(test-celery-accumulating-baggage): Migrate from pip to uv

[ericapisani]

Summary

• Replace requirements.txt with pyproject.toml for dependency management
• Update run.sh and run-celery.sh to use uv run instead of manual venv/pip workflow
• Part of PY-2428 migration effort

Test plan

• Run ./run-celery.sh and verify the celery worker starts correctly
• Run ./run.sh and verify the app runs correctly

🤖 Generated with Claude Code

[linear-code]

PY-2432

PY-2428

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7824e3e. Configure here.}

[cursor]

Python 3.12 requirement mismatch

High Severity

The pyproject.toml now requires Python 3.12+, but the .python-version file still pins 3.11.6. This mismatch can cause uv run to fail, preventing the project from starting or running scripts like run.sh and run-celery.sh.

 

^{Reviewed by Cursor Bugbot for commit 7824e3e. Configure here.}

[cursor]

uv install lacks PATH refresh

Medium Severity

The uv installer doesn't update the PATH for the current shell, causing uv run to fail with "command not found" immediately after installation. This is particularly an issue if ~/.local/bin isn't already on PATH, and set -euo pipefail ensures the script exits.

 

^{Reviewed by Cursor Bugbot for commit 7824e3e. Configure here.}

[sentry]

Bug: The pyproject.toml requires Python >=3.12, but .python-version pins 3.11.6. This conflict will cause uv run commands to fail.
_{Severity: HIGH}

Suggested Fix

Align the Python versions. Either change requires-python in pyproject.toml to ">=3.11.6" or update the version in .python-version to 3.12 or a compatible newer version.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: test-celery-accumulating-baggage/pyproject.toml#L4

Potential issue: The `pyproject.toml` file specifies `requires-python = ">=3.12"`, while
the `.python-version` file in the same directory pins the version to `3.11.6`. When `uv
run` is executed, it reads both files and detects that the pinned interpreter version
does not satisfy the project's requirement. This will cause commands like `uv run celery
...` and `uv run python main.py` to fail with an incompatibility error on every
invocation in both `run.sh` and `run-celery.sh`.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[sentry]

Bug: The uv command will not be found immediately after installation because the script does not update the current shell's PATH.
_{Severity: HIGH}

Suggested Fix

After the installation command, add a line to update the PATH for the current session, such as export PATH="$HOME/.local/bin:$PATH", before calling uv run.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: test-celery-accumulating-baggage/run-celery.sh#L4-L6

Potential issue: The `run-celery.sh` and `run.sh` scripts attempt to install `uv` if
it's missing, but the installer does not update the `PATH` for the current shell
session. Consequently, the subsequent `uv run` command will fail with a "command not
found" error on any system where `uv` is not already installed and in the `PATH`. This
makes the scripts unreliable for first-time users.

_{Did we get this right? 👍 / 👎 to inform future reviews.}