feat: add totalFetched property to FuryMetricSnapshot and update fetchMetric to include total items fetched

Co-authored-by: Copilot <copilot@github.com>

frontend/src/components/dashboard/FuryDashboard.tsx

@@ -266,6 +266,7 @@ function FuryDashboard() {
                     </Heading>
                   </Box>
                   <Badge alignSelf="flex-start" colorScheme="gray">
+                    {metric.totalFetched ? `${metric.totalFetched} fetched • ` : ""}
                     {metric.summary.count} pts / {range}
                   </Badge>
                 </Flex>

frontend/src/components/dashboard/furyDashboardApi.ts

@@ -76,6 +76,8 @@ export interface FuryMetricSnapshot {
   previous: FuryReading | null
   readings: FuryReading[]
   summary: FurySummary
+  // total number of items fetched from the upstream API (before client-side filtering)
+  totalFetched?: number
   unit: string
 }
 
@@ -191,9 +193,7 @@ const fetchMetric = async <TMetricKey extends FuryMetricKey>(
 
   // Ensure the snapshot reflects only the requested range — some upstream
   // proxies may ignore `start_date`/`end_date`, so filter client-side.
-  const filteredReadings = readings.filter(
-    (r) => new Date(r.updateTime).getTime() >= startMs,
-  )
+  const filteredReadings = readings.filter((r) => new Date(r.updateTime).getTime() >= startMs)
 
   return {
     description: config.description,
@@ -202,6 +202,7 @@ const fetchMetric = async <TMetricKey extends FuryMetricKey>(
     latest: filteredReadings[0] ?? null,
     previous: filteredReadings[1] ?? null,
     readings: filteredReadings,
+    totalFetched: allItems.length,
     summary: calculateSummary(filteredReadings, summarySinceMs),
     unit: config.unit,
   }