API status, empty-body, and binary-safe output contracts

For sentry api, treat only HTTP 200–299 as success and preserve rawApiRequest() status text. JSON mode retains {status, statusText, body} and applies --fields only to body. Verbose logs must include both status and status text. Empty textual failures need HTTP and request context; test them with an explicit empty-body route because the mock server’s unmatched route returns JSON unlike real Django 404s. Successful Uint8Array bodies bypass formatters unchanged. Binary failures expose only status, content type, and byte count—never raw bytes or JSON coercion. Prompts must not block scripts or contaminate stdout JSON. Reuse one success predicate across output and telemetry, with boundary tests for 199, 200, 299, and 300.