verify-live-integrationlisted

# Verify against the live dependency, not just mocks **A passing unit test against a mock proves your code matches the shape YOU assumed — not the shape the real dependency has.** Beta/third-party SDKs routinely differ from the assumption: a method is named `archive` not `delete`; a list returns reference *objects* not id *strings*; a field paginates; an endpoint 404s where you expected 200. Those bugs are invisible to mocks and only surface in production. Real example: a feature shipped with ~2300 green unit tests still had two beta-SDK shape bugs (a list returning objects, and "archive, no hard delete") that only appeared when the code ran against the live API. The tests were green because the mocks asserted the *assumed* shape. ## The discipline 1. **Flag every assumed shape.** Put a `VERIFY:` comment on any method name, return type, field, or status code you didn't confirm against the real API/docs. Make assumptions greppable. 2. **Introspect the real surface before trusting it.** In a real-creds environment (a scratch script, a one-off task, a REPL), dump the actual surface: - method names: `print([m for m in dir(client.x.y) if not m.startswith("_")])` - signatures: `inspect.signature(...)` - a **sample real response** — confirm object-vs-dict-vs-string, pagination, nesting, null shapes. 3. **Run a thin live smoke** of the real call path once (read-only or against a throwaway resource) and read the ACTUAL response, before relying on it in the reques