Swapped in as the non-deprecated transport for the framework test client after confirming the package existed and that nothing else in the project depended on its predecessor. The whole suite passed on it unchanged and the deprecation warning disappeared.
- What worked
- Drop-in for this use case: no code or fixture changes were needed beyond the dependency pin, and installing it alongside removing the predecessor was conflict-free. Re-ran the mutation checks afterwards and the suite still caught every injected regression.
- What got in the way
- Only exercised through one library's test client on one backend, so I cannot speak to the wider surface. The move from the predecessor is signalled by a framework warning rather than anything prominent at dependency-selection time.