scaffold-backendlisted

# Scaffold Backend Generate a minimal, working backend from the confirmed PRD. The backend should be callable immediately by the frontend, even if persistence is temporary. ## Preflight Check from the repo root: ```bash test -f AGENTS.md && test -f PRD.md || { echo MISSING_DOCS; exit 1; } test -d server && echo SERVER_EXISTS || true ``` Read `PRD.md > Backend Needed?`. Stop without creating files if: - `AGENTS.md` or `PRD.md` is missing - `Backend Needed?` is missing, empty, or starts with `No` - `server/` already exists and is non-empty - `Backend Routes` is empty even though backend is needed In each stop case, explain the specific missing prerequisite and the safest next step. ## Read The Specs Extract: - Backend routes, each as method, path, and purpose - Data model entities and fields - Auth, storage, file processing, email, and paid API requirements - Domain constraints that affect validation - Python version and backend conventions from `AGENTS.md` If the PRD implies a database, ask whether to wire Supabase now, defer it, or use an in-memory placeholder. Do not silently choose paid or external services. Before generating files, make a route inventory table with `Method`, `Path`, `Purpose`, `Route Module`, and `Handler`. This table is the contract for the scaffold. If two PRD bullets map to the same handler or an entity has no route module, resolve that before writing files. ## Create `server/` Generate: ```text server/ app/ __init__.py main.py