fastapi-depslisted

Upgrade dependencies without breaking the build. Move in small, verifiable steps — one batch at a time, tests green after each — rather than bumping everything at once and debugging the pile. ## Phase 1: Survey 1. **Read CLAUDE.md** for the package manager, the install command, and the test command. 2. **Read the manifest** (`pyproject.toml`, `package.json`, `go.mod`, `Cargo.toml`, …) and the lockfile. Note which versions are pinned exactly vs. ranged, and which deps are runtime vs. dev. 3. **List what's outdated.** Use the ecosystem's own tool (`pip list --outdated`, `npm outdated`, `go list -m -u all`, `cargo outdated`). Separate the upgrades into: - **patch/minor** — low risk, batchable. - **major** — has breaking changes; handle one at a time. 4. **Confirm a green baseline first.** Run the test suite *before* changing anything. If it's already red, stop — you can't attribute a later failure to an upgrade. ## Phase 2: Upgrade in order of risk 1. **Patch/minor first, as one batch.** Bump them, reinstall, run the full suite. If green, keep going. If red, narrow to the culprit (bisect the batch) before proceeding. 2. **Then majors, one at a time.** For each major bump: - **Read its changelog / migration notes** for the version range you're crossing — grep the codebase for the APIs it says changed, and check whether you use them. - Apply the bump and any required code changes together. - Run the suite. Only move to the next major once green. 3. **Respect the