feat(code): cache per-task PR url + state for instant task switches

[richardsolomou]

Problem

Switching between tasks in the sidebar/task detail used to block on a gh pr list --head <branch> call to figure out which PR each task corresponds to. That made the PR badge in the sidebar and the "Open PR" button in the task header pop in noticeably late on every task switch — and on cold start, every visible card paid the cost simultaneously.

Changes

Per-task PR info is now cached on the workspaces SQLite row (pr_url, pr_state, pr_fetched_at) and served stale-while-revalidate.

• GitService.getTaskPrStatus returns the cached prState synchronously and schedules a deduplicated background revalidation. hasDiff for worktree tasks still computes inline because it's local-only and cheap.
• The background revalidation runs the same gh lookups as before, writes through to the workspaces row, and — when the value changed — emits WorkspaceService.taskPrInfoChanged.
• A new workspace.onTaskPrInfoChanged tRPC subscription is wired in App.tsx; the handler updates every matching getTaskPrStatus query via setQueriesData so the badge updates in place without a refetch.
• workspace.getCachedPrUrl(taskId) lets useTaskPrUrl fall back to the cached URL so the task header's PR button opens the right PR before the live gh lookups return.
• The taskPrInfoChanged emit uses a string literal (not the WorkspaceServiceEvent const) to avoid a circular import — workspace/service eagerly loads the DI container, which re-enters git/service.

Migration: 0007_stiff_reptil adds the three nullable columns to workspaces.

How did you test this?

• pnpm --filter @posthog/code typecheck ✅
• pnpm exec biome check apps/code/src ✅
• pnpm --filter @posthog/code test ✅ (1436 pass; the 23 archive integration failures pre-exist on main because git commit is blocked in this signed-commit environment — verified by re-running them on a clean tree)

No manual UI verification was possible from this environment.

Publish to changelog?

no

---

Created with PostHog Code

[greptile-apps]

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
apps/code/src/main/services/git/service.ts:1858-1862
The "no-op" guard uses `!fresh.hasDiff` to skip emitting, but since `hasDiff` is never persisted to the DB there is no baseline to compare against. For a worktree task that has uncommitted changes but no PR (`prUrl: null, prState: null, hasDiff: true`), this condition will always be `false`, so `updatePrCache` and `emit("taskPrInfoChanged")` are called on every revalidation cycle even when nothing has actually changed since the last one. The repeated `setQueriesData` calls in `App.tsx` are harmless because React detects identical data, but the extra DB writes accumulate silently.

```suggestion
        const cachedHasDiff = !cachedPrState && !cachedPrUrl;
        if (
          cachedPrUrl === fresh.prUrl &&
          cachedPrState === fresh.prState &&
          cachedHasDiff === fresh.hasDiff
        ) {
```

### Issue 2 of 2
apps/code/src/renderer/App.tsx:132-152
The `prUrl` from the `taskPrInfoChanged` payload is silently dropped here. When a background revalidation discovers a new PR URL (e.g., a PR is created after the task was first opened), the DB is updated and the event fires with the URL, but the `getCachedPrUrl` React Query cache is never invalidated or updated. Because `getCachedPrUrl` has `staleTime: 60_000`, the `cached?.prUrl` fallback in `useTaskPrUrl` will serve the old (null) value for up to a minute, defeating the fast-path for the "Open PR" button that this cache was introduced to provide.

```suggestion
      onData: ({ taskId, prUrl, prState, hasDiff }) => {
        // Push the fresh PR info into every matching getTaskPrStatus query
        // (one per cloudPrUrl variant) so the renderer re-renders without
        // waiting for the next staleTime-driven refetch.
        queryClient.setQueriesData<{
          prState: typeof prState;
          hasDiff: boolean;
        }>(
          {
            ...trpcReact.workspace.getTaskPrStatus.pathFilter(),
            predicate: (query) => {
              const [, params] = query.queryKey as [
                unknown,
                { input?: { taskId?: string } } | undefined,
              ];
              return params?.input?.taskId === taskId;
            },
          },
          () => ({ prState, hasDiff }),
        );
        // Keep getCachedPrUrl in sync so the "Open PR" fast-path stays warm.
        queryClient.setQueryData(
          trpcReact.workspace.getCachedPrUrl.queryKey({ taskId }),
          { prUrl },
        );
      },
```

_{Reviews (1): Last reviewed commit: "feat(code): cache per-task PR url + stat..." | Re-trigger Greptile}

[k11kirky]

getCachedPrUrl extends the exact router, repository pattern CLAUDE.md says not to extend

context: R10 / forbidden-patterns: "tRPC routers bypassing their service to call a repository. workspace.ts does this today; do not extend the pattern." This file is already pervasively guilty (togglePin, markViewed, getTaskTimestamps…), so it's consistent with its neighbors — but it's still net-new surface against an explicitly-named rule. Since GitService already owns the PR-cache writes, the natural home is a thin GitService.getCachedPrUrl(taskId) (or WorkspaceService) method, keeping the router a one-liner. Low effort, and it doesn't grow the debt the guide is trying to contain.

[richardsolomou]

moved to a thin GitService.getCachedPrUrl(taskId), router back to a one-liner. cc726b2