feat: workspace fetch optimization + parent tasks fetching

[priosshrsth]

Summary

resolves OUT-3705 OUT-3705: Optimize workspace to be fetched once per session

• Fetch workspace on client side and once per session
• Update rest of the codebase to use portalUrl from store rather than props.
• For subtasks we get the details of both tasks with single query instead of multiple
• resolves OUT-3695 OUT-3695: Remove customFields from clients response

Test plan

• App boots, workspace data appears in redux after first paint
• Detail page: sidebar + header breadcrumbs render correctly with portalUrl-dependent CTAs
• Home / client board: app bridges (CTAs, breadcrumbs) work
• Manage templates list + detail: app bridges work
• First-paint flash on portalUrl-dependent UI is not visually disruptive
• Subtask detail page: ancestor breadcrumbs render in correct root → leaf order (parent tasks ordering fix)

2026-05-07.15-11-44.mov

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 8, 2026 3:54am

[greptile-apps]

Greptile Summary

This PR delivers two optimizations targeting the feature/c1-optimization branch: it replaces the per-parent findFirstOrThrow fan-out in getTraversalPath with a single findMany + client-side reordering, and it moves workspace fetching from per-page SSR calls into a single SWR-backed client component (WorkspaceFetcher) mounted in the root layout that writes to the redux store.

• Parent-task fetch: N serial DB queries → 1 findMany; order is preserved via a Map indexed by the original parentIds array; missing IDs throw EXPECTATION_FAILED with the offending ID surfaced.
• Workspace fetch: Five SSR pages drop their getWorkspace calls and workspace prop drilling; all AppBridge hooks and layout components now read portalUrl from selectAuthDetails; first-paint undefined is tolerated because every AppBridge hook already guards on portalUrl in its effect deps.
• customFields in ClientResponseSchema: field is commented out rather than removed, silently dropping it from the inferred TypeScript type with no type-checker warning at callsites.

Confidence Score: 5/5

Safe to merge — all changed paths are well-guarded and the optimizations are straightforward.

The parent-task query consolidation is logically correct: order is explicitly re-applied from parentIds after the findMany, and missing entries throw with a clear error. The workspace SWR lift is a well-scoped refactor with no broken contracts — every AppBridge hook already handles an undefined portalUrl for one tick. The only new code concern is a dead parentTasksStartedAt variable that will generate a lint warning but has no runtime impact.

No files require special attention beyond the unused variable in tasks.service.ts and the pre-existing customFields comment-out in types/common.ts.

Important Files Changed

Filename	Overview
src/app/api/tasks/tasks.service.ts	Replaces N serial findFirstOrThrow calls with a single findMany + client-side reordering; parentTasksStartedAt is declared but never used (dead variable).
src/app/_fetchers/WorkspaceFetcher.tsx	New client component that fetches workspace once via SWR (60s dedup) when token is present and redux store has no workspace yet, then dispatches to redux.
src/app/api/workspace/route.ts	New authenticated GET handler wrapping getMemoizedWorkspace; correctly uses withErrorHandler and authenticate.
src/utils/copilotMemo.ts	Wraps copilot.getWorkspace() in React cache() — effective within RSC render trees but not across API route invocations (already flagged in prior review).
src/types/common.ts	customFields field commented out of ClientResponseSchema, silently dropping it from the inferred ClientResponse type (already flagged in prior review).
src/app/layout.tsx	Mounts WorkspaceFetcher once in the root layout inside a Suspense boundary — correct usage of useSearchParams in layout context.

_{Reviews (2): Last reviewed commit: "fix traversal" | Re-trigger Greptile}

[vercel]

Deployment failed with the following error:

Deploying Serverless Functions to multiple regions is restricted to the Pro and Enterprise plans.

Learn More: https://vercel.link/multiple-function-regions

[linear-code]

OUT-3695 Remove customFields from clients response

OUT-3705 Optimize workspace to be fetched once per session

[arpandhakal]

Lets consider testing in the platform itself in a custom app. That way we can ensure everything works including the app bridge.

[priosshrsth]

Lets consider testing in the platform itself in a custom app. That way we can ensure everything works including the app bridge.

@arpandhakal I already did that. See my recording, It includes me testing the breadcrumb and the collapsible menu on top right.