Skip detail page SSR for HEAD requests

[cursor]

Changes

• Add a Next 16 src/proxy.ts guard for /detail/:path* that returns a no-store 200 for HEAD requests before the task detail page runs SSR loaders.
• Keep normal GET navigation flowing through to the existing detail page.
• Add focused unit coverage for the matcher, HEAD short-circuit, and GET pass-through behavior.

Testing Criteria

• yarn test src/proxy.test.ts - validates matcher scope plus HEAD/GET behavior.
• yarn lint:check -- src/proxy.ts src/proxy.test.ts - completed with existing repo warnings only, no errors.
• yarn tsc - attempted; blocked by existing unrelated SVG module declaration errors in src/icons/index.ts.
• Runtime check with yarn dev and curl -I against /detail/9474a765-95dc-445f-aaca-7f950acdbdce/iu?token=test-token returned 200 with cache-control: no-store, and the dev server logged no page-render errors for that HEAD request.

Notes

• Linear/Sentry triage: OUT-3848 links to Sentry TASKS-94 in the tasks project.
• Sentry aggregates show all 91 PrismaClientKnownRequestError events in the last 14 days are on HEAD /detail/[task_id]/[user_type], across 6 Sentry groups. TASKS-94 specifically failed in SubtaskService.getSubtaskCounts with Can't reach database server at aws-0-us-east-1.pooler.supabase.com:6543.

Impact & Surface Area of Change

• Only HEAD requests matching /detail/:path* are short-circuited.
• GET/POST/API traffic is not matched or changed.
• This reduces unnecessary database pressure from HEAD probes without changing the interactive task-detail page render path.

  

[linear-code]

OUT-3848

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jun 12, 2026 7:25pm