fastapi-run

Run this project's app and drive it far enough to observe the behavior the user cares about. Don't just start it and call it done — exercise the actual flow. ## Steps 1. **Find the run command in CLAUDE.md.** Read CLAUDE.md — its **Commands** section is the source of truth for how this project installs, builds, and runs. Look for entries labeled run / start / serve / dev, a CLI entrypoint, or a server command (this project may expose more than one, e.g. a CLI *and* a server — pick the one that matches what the user asked for; if it's ambiguous, ask). 2. **Read any `.claude/rules/*.md`** whose `paths:` glob covers the code you're about to exercise — it may note required env vars, ports, or setup the command alone doesn't reveal. 3. **Fall back to the stack** only if CLAUDE.md names no run command (see the defaults below). 4. **Prepare the environment.** Install/build first *only if needed* (a fresh checkout, or the run command errors on missing deps) — e.g. the editable install or `npm install` from CLAUDE.md. If the app needs an env var, config file, or secret that isn't present, STOP and ask rather than inventing a value — a guessed secret produces a misleading failure. 5. **Run it, matched to the app's shape:** - **One-shot (CLI, script, build):** invoke it directly. Start with a cheap sanity call (`--help` / `--version`) to confirm it launches, then run a *representative real command* — the one that exercises the change or the behavior in question. - **Long-running...