Make MockVWS intercept both requests and httpx

[adamtheturtle]

Summary

• MockVWS now intercepts both requests (via responses) and httpx (via respx) simultaneously
• Removed MockVWSForHttpx class entirely — a single MockVWS class handles both HTTP libraries
• Simplified API: users no longer need to choose between two classes
• Updated all tests, documentation, and examples to reflect this change

Test plan

• ✅ All 49 existing tests pass (test suite covers both requests and httpx behavior)
• ✅ 3 new httpx-specific tests added to test_requests_mock_usage.py
• ✅ All linters pass (pre-commit hooks enforced)

---

Note

Medium Risk
Moderate risk due to behavioral changes in core test-mocking infrastructure and removal of a public class (MockVWSForHttpx), which may break existing consumers or subtly alter intercept/timeout behavior across HTTP clients.

Overview
Unifies HTTP client mocking so a single MockVWS context manager now intercepts both requests (via responses) and httpx (via respx) at the same time, including support for real_http, base URL path prefixes, and response delay/timeout behavior.

Removes the separate MockVWSForHttpx API from exports and docs, factors MissingSchemeError into _mock_common, and refactors the respx integration into a start_respx_router() helper; tests and documentation/examples are updated accordingly, with new coverage ensuring httpx traffic is intercepted/blocked as expected under MockVWS.

^{Written by Cursor Bugbot for commit fdfb20a. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Responses mock leaked if respx router setup fails

Medium Severity

In __enter__, self._mock.start() is called before start_respx_router(). If start_respx_router raises an exception, __exit__ never runs (the context manager wasn't successfully entered), so the responses mock remains active and silently intercepts all subsequent requests calls. Similarly in __exit__, if self._mock.stop() raises, self._router.stop() is skipped and the respx router stays active. Both resources need try/finally protection since neither cleanup is guaranteed to run if the other fails.

Additional Locations (1)

• src/mock_vws/_requests_mock_server/decorators.py#L263-L265