Handle missing-token activity log requests

[cursor]

Changes

• Wrap GET /api/activity-logs/[id] with the shared withErrorHandler API wrapper.
• Add a regression test proving missing-token requests return a quiet 401 JSON response instead of surfacing as an unhandled route exception.

Testing Criteria

• yarn test src/app/api/tests/routes/activity-log-route.test.ts src/app/api/tests/utils/withErrorHandler.test.ts --runInBand — 2 suites / 11 tests passed.
• yarn prettier:check — passed.
• yarn lint:check — passed with existing React hook/compiler warnings.
• yarn tsc — still fails only on the known pre-existing SVG module declaration errors in src/icons/index.ts.

Notes

• Linear/Sentry direct reads were unavailable from this automation environment (Linear returned 401; Sentry MCP requires auth), but the issue title exactly matches the Tasks API auth error thrown by authenticate when no token query parameter is provided.

Impact & Surface Area of Change

• Scope is limited to the legacy activity-log detail API route. Authenticated successful behavior still calls the same ActivityLogService#get; expected client/auth errors now follow the same response and logging behavior as the rest of the authenticated API routes.

  

[linear-code]

OUT-3974

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jul 12, 2026 6:07pm