When the user wants to virtualize HTTP services for testing — mocking downstream dependencies, simulating slow/error responses, recording-and-replay, or building a stub server for development. Use when the user mentions "WireMock," "stubFor," "mappings," "WireMockServer," "WireMock standalone," "request matching," "scenarios in WireMock," "fault injection," "WireMock Cloud," or "wiremock studio." For consumer-driven contracts see pact-contract-testing. For Karate's Netty mocks see karate. For language-native HTTP mocking see pytest-api / supertest.
