fix: use actualTokens (API-reported) when uploading, matching extension display

The extension shows actualTokens > 0 ? actualTokens : estimatedTokens
(calculateDetailedStats line 1558). The sync service was only reading
cachedData.tokens (text-estimated ~20M) instead of cachedData.actualTokens
(API-reported ~1.2B), causing a ~57x undercounting on the server dashboard.

Apply the same preference: prefer actualTokens when available, fall back to
text-estimated tokens for files without API usage data.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: rajbos

vscode-extension/src/backend/services/syncService.ts

@@ -511,9 +511,15 @@ export class SyncService {
 			// combination gets a share of the total proportional to how many interactions it had.
 			// For the input/output split we use the output fraction from modelUsage (output tokens are
 			// not inflated by context the same way input tokens are).
-			const displayTokens: number = (typeof (cachedData as any).tokens === 'number' && (cachedData as any).tokens > 0)
-				? (cachedData as any).tokens as number
-				: 0;
+			// Mirror the extension's own token preference: prefer actual API-reported tokens when
+			// available (same logic as calculateDetailedStats: actualTokens > 0 ? actualTokens : estimatedTokens).
+			// Text-estimated tokens (~20M) are far smaller than API-actual numbers (~1.2B) because
+			// the estimators only measure visible conversation text, not the full context window.
+			const estimatedTokens: number = typeof (cachedData as any).tokens === 'number'
+				? (cachedData as any).tokens as number : 0;
+			const cachedActualTokens: number = typeof (cachedData as any).actualTokens === 'number'
+				? (cachedData as any).actualTokens as number : 0;
+			const displayTokens: number = cachedActualTokens > 0 ? cachedActualTokens : estimatedTokens;
 			const totalAllInteractions = Array.from(dayModelInteractions.values())
 				.reduce((sum, m) => { m.forEach(c => { sum += c; }); return sum; }, 0);