fix(logs): replace .parse() with .safeParse() to prevent ZodError crash on self-hosted

[jared-outpost]

listLogs() and getLogsBatch() in src/lib/api/logs.ts were the only API functions using raw Zod .parse(), which throws an unhandled ZodError when a self-hosted instance returns a non-object response (HTML from a reverse proxy, plain text from an unsupported endpoint). Replaced with .safeParse() + ApiError, matching the pattern used by apiRequestToRegion and organizations.ts.

Added a safeParseResponse() helper that pre-checks typeof data, uses .safeParse(), and attaches Zod issues to Sentry context for diagnostics.

Testing

npx vitest run test/lib/api/logs.test.ts — 6 tests covering string, null, wrong-shape, and valid responses for both listLogs and getLogs. Full API test suite (182 tests) passes.

Closes #1095

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://cli.sentry.dev/_preview/pr-1096/
Built to branch gh-pages at 2026-06-12 08:04 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[github-actions]

Codecov Results 📊

✅ Patch coverage is 100.00%. Project has 5012 uncovered lines.
✅ Project coverage is 81.2%. Comparing base (base) to head (head).

Coverage diff

@@            Coverage Diff             @@
##          main       #PR       +/-##
==========================================
+ Coverage    81.19%    81.20%    +0.01%
==========================================
  Files          383       383         —
  Lines        26649     26657        +8
  Branches     17340     17346        +6
==========================================
+ Hits         21636     21645        +9
- Misses        5013      5012        -1
- Partials      1798      1797        -1

---

Generated by Codecov Action

[sentry]

Bug: The assertObjectResponse function logs a confusing error message, "received object", when the API response is null due to the typeof null === "object" JavaScript quirk.
_{Severity: LOW}

Suggested Fix

Modify the error message generation in assertObjectResponse to handle the null case specifically. Instead of just using typeof data, check if data === null and print "null" in the message. For example: ...received ${data === null ? 'null' : typeof data}. This will provide a clear and accurate error message.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: src/lib/api/logs.ts#L62-L64

Potential issue: When the API response data is `null`, the `assertObjectResponse`
function correctly throws an `ApiError`. However, due to the JavaScript quirk where
`typeof null` evaluates to `"object"`, the error message becomes `"Expected an object
but received object"`. This is self-contradictory and misleading for users, especially
in self-hosted environments where a `null` response is a possible edge case. This makes
diagnosing the underlying issue more difficult.

_{Did we get this right? 👍 / 👎 to inform future reviews.}