Update AGENTS.md

Author: ryaneggz

AGENTS.md

@@ -12,8 +12,10 @@ backend:
     description: This is the REST API for the ./frontend and ./cli clients.
     deployment: https://chat.ruska.ai/docs
     commands:
-        - `make test` Run ALL test cases.
-        - `make format` Format project files. Use after making changes.
+        - `make test` Run ALL test cases (uses ENV_FILE=~/.env/orchestra/.env.backend).
+        - `make test ENV_FILE=~/.env/orchestra/.env.backend.test` Run tests with test env.
+        - `make format` Format project files with ruff. Use after making changes.
+        - `make lint` Lint check with ruff (no auto-fix).
         - `make dev` Run dev server.
         - `make seeds.user` Seed default users.
 frontend:
@@ -56,13 +58,15 @@ The main way external AI Agents find out information about RUSKA will be from th
 - `frontend/src` hosts the Vite/React client (`components`, `pages`, `routes`, `tests`), while `docs/`, `deployment/`, and `docker/` hold reference material and ops tooling.
 
 ## Build, Test, and Development Commands
-- Backend: `uv venv && source .venv/bin/activate && uv sync` installs dependencies, `bash backend/scripts/dev.sh` runs the API with reload, and `uv run pytest` (or `bash backend/scripts/test.sh`) executes the suite.
+- **Setup**: Run `make setup` from the repo root to install pre-commit hooks.
+- Backend: `cd backend && uv venv && source .venv/bin/activate && uv sync` installs dependencies, `make dev` runs the API with reload, and `make test` executes the suite. Use `ENV_FILE=~/.env/orchestra/.env.backend.test` for the test environment.
 - Frontend: `cd frontend && npm install`, `npm run dev` for local dev, `npm run build` for production bundles, and `npm run docs` regenerates MkDocs API docs.
 - Infrastructure: `docker compose up postgres pgadmin` provisions Postgres + PgAdmin; stop with `docker compose down`.
 
 ## Coding Style & Naming Conventions
-- Run `pre-commit run --all-files`; hooks call `make format` (Ruff) for Python and Prettier/ESLint for frontend changes.
-- Python modules use 4-space indents, `snake_case` files, and typed Pydantic models in `backend/src/schemas`. React code follows Prettier’s 2-space indent; components stay in `PascalCase`, hooks in `camelCase`.
+- Run `pre-commit run --all-files`; hooks run backend format/lint/test and frontend prettier/lint/test.
+- Python: ruff configured in `backend/pyproject.toml` with `line-length = 120`, select `["E", "F"]`. Per-file E402 ignores for files with `load_dotenv()` before imports. Use 4-space indents, `snake_case` files, typed Pydantic models in `backend/src/schemas`.
+- React: Prettier 2-space indent; components in `PascalCase`, hooks in `camelCase`.
 
 ## Testing Guidelines
 - Place backend unit specs in `backend/tests/unit` and integration cases in `backend/tests/integration`; seed demo data with `python -m seeds.user_seeder` when needed.
@@ -72,7 +76,7 @@ The main way external AI Agents find out information about RUSKA will be from th
 ## Commit & Pull Request Guidelines
 - Sign every commit with `git commit -s ...`; keep subject lines imperative and reference issues or tickets when helpful.
 - Before opening a PR, ensure `uv run pytest`, `npm run test`, and any affected docs or `.env` samples reflect your changes; squash WIP noise locally.
-- PRs target `main`, link tracking issues, provide concise change notes, and include screenshots or API traces for UI-facing work.
+- PRs target `development`, link tracking issues, provide concise change notes, and include screenshots or API traces for UI-facing work.
 
 ## Security & Configuration Tips
 - EXTREMELY IMPORTANT: NEVER read a .env* file in your exploration.