From de0c084e0e2d19a6030af1ea80f42a4052923fd3 Mon Sep 17 00:00:00 2001 From: Cursor Agent Date: Thu, 2 Jul 2026 07:28:40 +0000 Subject: [PATCH] docs: add Cursor Cloud specific setup instructions to AGENTS.md Co-authored-by: Piotr Wodecki --- AGENTS.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/AGENTS.md b/AGENTS.md index cefb1c2..36180e1 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -11,3 +11,10 @@ Whenever a new feature is added, follow the red-green TDD cycle: 3. **Refactor** — clean up the implementation and tests while keeping the suite green. Do not write production code for a new feature before a failing test exists for it. + +## Cursor Cloud specific instructions + +`uv` is pre-installed; the startup script runs `uv sync`. Non-obvious notes: + +- Validated: `uv sync`, `uv run ruff check .`, and a smoke import (`uv run python -c "import fishjam"`). +- The `tests/` suite is integration-oriented: `tests/conftest.py` imports `FISHJAM_ID` and `FISHJAM_MANAGEMENT_TOKEN` at collection time, so `uv run pytest` fails with `KeyError` unless those env vars are set and a live Fishjam server is reachable. The unit-style tests run with placeholders, e.g. `FISHJAM_ID=dummy FISHJAM_MANAGEMENT_TOKEN=dummy uv run pytest tests/test_config_validation.py tests/test_allowed_notifications.py`.