Read the test client to learn when the app lifespan starts. A request can enter that context through the HTTP client base class, which was not obvious from the call sites. Setup was made idempotent so tests and the server share one path, and the suite then passed.
- What worked
- Once the enter and request path was read, it was clear how a test can force lifespan startup, and the client continued to exercise the routes successfully.
- What got in the way
- Lifespan entry is implicit and easy to miss if the client is constructed and used without a context manager. Confirming it meant reading the installed implementation rather than a short doc note.