Handle invalid Copilot launch tokens

[cursor]

Changes

• Added getSafeTokenPayload to safely validate Copilot launch token payloads without leaking SDK authorization failures into server-render errors.
• Updated the root and client task pages to validate token payloads before downstream data fetches and render the existing invalid-token silent error when authorization fails.
• Added unit coverage for valid, unauthorized, and malformed token payload paths.

Testing Criteria

• yarn test --runTestsByPath src/app/api/tests/utils/tokenPayload.test.ts --runInBand
• yarn lint:check passes with existing React hook/compiler warnings.
• yarn tsc --noEmit still fails on pre-existing missing SVG module declarations in src/icons/index.ts.

Notes

• Related Sentry issue: TASKS-82 / Linear OUT-2995.
• Seer Autofix analysis was unavailable because the Sentry org has no budget for Seer Autofix.

Impact & Surface Area of Change

• Affects the root task board page and client task board page token bootstrap path.
• Invalid or cross-environment Copilot tokens should now show the existing invalid-token UI instead of creating unhandled Next.js server-render Sentry events.

  

[linear-code]

OUT-2995

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 19, 2026 9:56pm

[priosshrsth]

@arpandhakal This PR actually looks good to me. Instead of throwing error, this silently captures, empty or invalid token and show error UI. wdyt?