Harden server fetch JSON parsing

[cursor]

Changes

• Added contextual JSON parsing/error handling to fetchWithErrorHandler, including URL/body token redaction and response body previews for non-JSON responses.
• Routed homepage, client page, async fetchers, configure, detail, and template server-side app API fetches through the shared helper.
• Added focused tests for successful JSON parsing, non-JSON success responses, and non-OK non-JSON responses.

Testing Criteria

• yarn test src/app/_fetchers/fetchWithErrorHandler.test.ts --runInBand
• yarn lint:check (passes with existing warnings)
• yarn tsc --noEmit (blocked by existing SVG module declaration errors in src/icons/index.ts, unrelated to this change)

Notes

• Linear: OUT-3750
• Sentry: TASKS-88

Impact & Surface Area of Change

• Server-side data fetches for task board initial render and related pages now retry through the shared helper and emit actionable, redacted errors if an internal API returns non-JSON text/HTML instead of JSON.
• The underlying upstream/internal API failure will still surface, but future Sentry events should identify the endpoint/status/body preview instead of only SyntaxError: Unexpected token 'A' from Undici JSON parsing.

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 18, 2026 5:17pm

[linear-code]

OUT-3750