Handle invalid task detail IDs without Prisma errors

[cursor]

Changes

• Treat malformed task detail IDs as non-renderable content in the detail-page loaders instead of allowing Prisma/Zod UUID errors to escape server rendering.
• Preserve escalation for unrelated Prisma known request errors so real data-integrity failures are still surfaced.
• Add focused loader tests for Prisma P2010 raw-query UUID errors, Prisma P2023 UUID errors, Zod UUID validation errors, and unrelated Prisma error rethrows.

Testing Criteria

• yarn test --runTestsByPath "src/app/detail/[task_id]/[user_type]/loaders.test.ts" --runInBand passed: 4 tests.
• yarn lint:check passed with existing React hook/compiler warnings.
• yarn tsc was attempted and still fails on the repository's pre-existing missing SVG module declarations in src/icons/index.ts.

Notes

• Linear and Sentry MCP access were unavailable (Linear tool calls returned 401 after discovery; Sentry MCP requires auth), so direct event stack/project metadata could not be retrieved. The trigger was in Triage and the Sentry-like issue title was investigated in the Tasks app repo.

Impact & Surface Area of Change

• Detail page server loaders for task, subtask status, and breadcrumb path. Regression focus: malformed or stale /detail/:task_id/:user_type URLs should render the existing deleted/not-found flow, while valid task detail pages and unrelated server errors should behave unchanged.

  

[linear-code]

OUT-3961

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jul 8, 2026 4:21pm