A 200 response can still be wrong if the body breaks the contract

An API debugging observation about checking response body shape, missing fields, wrong types, stale data, and expected contract.

A 200 response only says the request completed. It does not prove the body matched the contract. If a list is empty, a field is missing, a type changes, or stale data returns after a write, I would record the route, reduced body, wrong field path, and expected shape before calling it successful.