feat(billing): single-source usage via main-process relay

[k11kirky]

Problem

The renderer was polling the LLM gateway directly every 30 seconds to fetch usage data, coupling the renderer to the gateway and duplicating polling logic that the UsageMonitorService already handles.

Changes

The UsageMonitorService now caches the most recent usage snapshot (latestUsage) and emits a UsageUpdated event after every successful poll. Two new methods are exposed: getLatest() to retrieve the cached snapshot synchronously, and refreshNow() to trigger an immediate poll.

The usageMonitorRouter exposes these via three new tRPC endpoints: onUsageUpdated (a subscription that streams snapshots as they arrive), getLatest (a query to bootstrap the renderer before the first event), and refresh (a mutation to force an immediate poll). The llmGateway.usage query endpoint has been removed since it is no longer needed.

The useUsage hook in the renderer now subscribes to onUsageUpdated instead of polling on an interval. It bootstraps from getLatest on mount and exposes a refetch that calls the refresh mutation. The window-focus-based refetch interval logic has been removed entirely.

How did you test this?

Three new unit tests were added to service.test.ts:

• Verifies that UsageUpdated is emitted and the snapshot is cached on every successful poll.
• Verifies that UsageUpdated is not emitted and the snapshot remains null when the gateway throws.
• Verifies that refreshNow triggers a fresh poll and returns the resulting snapshot.

Publish to changelog?

No

[k11kirky]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• feat(billing): single-source usage via main-process relay #2358 👈 (View in Graphite)
• feat(agent): fill Skills/MCP/Rules categories in context breakdown #2357
• feat(sessions): context breakdown popover #2353
• feat(agent): emit per-category context token breakdown #2352
• feat(billing): threshold notification service with persisted dedupe #2351
• feat(billing): always-on Free sidebar bar with reset time #2350
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[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/usage-monitor/schemas.ts:24-25
The `UsageSnapshot` type alias is exported but never consumed — `service.ts` uses `UsageOutput | null` inline everywhere. The Zod schema `usageSnapshotOutput` is legitimately needed for tRPC output validation, but the TypeScript type alongside it is superfluous (simplicity rule #4).

```suggestion
export const usageSnapshotOutput = usageOutput.nullable();
```

### Issue 2 of 2
apps/code/src/renderer/features/billing/hooks/useUsage.ts:37
The entire `refreshMutation` object is listed as a `useCallback` dependency. `useMutation` returns a new object reference on every render (state fields like `isPending` change), so `refetch` is recreated every render. Depending on `refreshMutation.mutateAsync` directly is sufficient — that function reference is stable across renders.

```suggestion
  }, [refreshMutation.mutateAsync, queryClient, trpc.usageMonitor.getLatest]);
```

_{Reviews (1): Last reviewed commit: "feat(billing): single-source usage via m..." | Re-trigger Greptile}

[greptile-apps]

The UsageSnapshot type alias is exported but never consumed — service.ts uses UsageOutput | null inline everywhere. The Zod schema usageSnapshotOutput is legitimately needed for tRPC output validation, but the TypeScript type alongside it is superfluous (simplicity rule #4).

Suggested change

	export const usageSnapshotOutput = usageOutput.nullable();
	export type UsageSnapshot = UsageOutput | null;
	export const usageSnapshotOutput = usageOutput.nullable();

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/main/services/usage-monitor/schemas.ts
Line: 24-25

Comment:
The `UsageSnapshot` type alias is exported but never consumed — `service.ts` uses `UsageOutput | null` inline everywhere. The Zod schema `usageSnapshotOutput` is legitimately needed for tRPC output validation, but the TypeScript type alongside it is superfluous (simplicity rule #4).

```suggestion
export const usageSnapshotOutput = usageOutput.nullable();
```

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

The entire refreshMutation object is listed as a useCallback dependency. useMutation returns a new object reference on every render (state fields like isPending change), so refetch is recreated every render. Depending on refreshMutation.mutateAsync directly is sufficient — that function reference is stable across renders.

Suggested change

	}, [refreshMutation, queryClient, trpc.usageMonitor.getLatest]);
	}, [refreshMutation.mutateAsync, queryClient, trpc.usageMonitor.getLatest]);

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/code/src/renderer/features/billing/hooks/useUsage.ts
Line: 37

Comment:
The entire `refreshMutation` object is listed as a `useCallback` dependency. `useMutation` returns a new object reference on every render (state fields like `isPending` change), so `refetch` is recreated every render. Depending on `refreshMutation.mutateAsync` directly is sufficient — that function reference is stable across renders.

```suggestion
  }, [refreshMutation.mutateAsync, queryClient, trpc.usageMonitor.getLatest]);
```

How can I resolve this? If you propose a fix, please make it concise.