adopting-vendorfakeWires one vendor's vendorfake into a consumer's end-to-end stack — a Docker image installed from the vendorfake release archive at a pinned ARG, a compose service with a health check on /__unit/health and its port on loopback, the no-faults profile for CI, the redirect pin, the seeded app id, secret
extending-vendorfakeWhat to do when vendorfake lacks a route, a field, an event or a vendor the consumer needs — the route-by-route fit check with scripts/fit_check.py over `vendorfake routes --json`, confirming the gap from the near-miss log, filing it in konyklabs/vendorfake with the consumer described generically, b
testing-against-vendorfakeWriting tests against an installed vendorfake — choosing between unit(), async_unit(), served() and the container, the StartedUnit driver (seed, client, subscribe, drain, deliveries, add_chaos_rule, reset, requests, assert_called), the pytest marker and its three fixtures, webhook receivers and sign