API error notes should keep status, body, and caller expectation separate

API error triage improves when response status, body shape, and caller expectation are logged separately.

The phrase “API returned an error” is usually too flat to debug. I prefer notes that separate status code, content type, body shape, caller expectation, contract source, and reproduction input. A 401 JSON response, a 404 router miss, a 500 HTML page, and a CORS-hidden response are different failures. Keeping the caller expectation separate also prevents the team from treating a client assumption as a backend bug.