Fix Prettier formatting issues

app/admin/index.tsx

@@ -56,11 +56,7 @@ export default function OverviewDashboard() {
         />
         <View style={styles.row}>
           <View style={styles.halfCard}>
-            <MetricCard
-              label="Web"
-              value={data?.metrics.activeUsers.web ?? 0}
-              subtitle="users"
-            />
+            <MetricCard label="Web" value={data?.metrics.activeUsers.web ?? 0} subtitle="users" />
           </View>
           <View style={styles.halfCard}>
             <MetricCard

constants/AdminMetrics.ts

@@ -102,6 +102,8 @@ export const ADMIN_METRICS = {
 // Type Exports for Constants
 // ============================================================================
 
-export type ChartColor = (typeof ADMIN_METRICS.CHART_COLORS)[keyof typeof ADMIN_METRICS.CHART_COLORS]
-export type StatusColor = (typeof ADMIN_METRICS.STATUS_COLORS)[keyof typeof ADMIN_METRICS.STATUS_COLORS]
+export type ChartColor =
+  (typeof ADMIN_METRICS.CHART_COLORS)[keyof typeof ADMIN_METRICS.CHART_COLORS]
+export type StatusColor =
+  (typeof ADMIN_METRICS.STATUS_COLORS)[keyof typeof ADMIN_METRICS.STATUS_COLORS]
 export type AdminEndpoint = (typeof ADMIN_METRICS.ENDPOINTS)[keyof typeof ADMIN_METRICS.ENDPOINTS]

services/monitoring/sentry.ts

@@ -152,12 +152,15 @@ export function captureMessage(
  * Start a performance transaction span
  */
 export function startSpan(name: string, op: string) {
-  return Sentry.startSpan({
-    name,
-    op,
-  }, () => {
-    // Span callback - operations tracked here
-  })
+  return Sentry.startSpan(
+    {
+      name,
+      op,
+    },
+    () => {
+      // Span callback - operations tracked here
+    }
+  )
 }
 
 /**

specs/002-admin-stats-dashboard/checklists/requirements.md

@@ -36,12 +36,14 @@ All checklist items are complete. The specification is ready to proceed to `/spe
 ### Validation Details
 
 **Content Quality**: ✅ PASS
+
 - Specification focuses on WHAT users need (admin statistics dashboards) and WHY (operational monitoring, user engagement tracking, platform insights)
 - No mention of specific technologies like React, TypeScript, or Recharts in the specification itself
 - Written in plain language that non-technical stakeholders can understand
 - All mandatory sections (User Scenarios, Requirements, Success Criteria) are completed
 
 **Requirement Completeness**: ✅ PASS
+
 - No [NEEDS CLARIFICATION] markers present
 - All 42 functional requirements are specific and testable (e.g., "System MUST display active user counts separated by platform")
 - Success criteria are quantifiable (e.g., "Dashboard loads within 2 seconds", "95% platform detection accuracy")
@@ -51,6 +53,7 @@ All checklist items are complete. The specification is ready to proceed to `/spe
 - Dependencies on PostHog and Sentry for analytics are clearly stated
 
 **Feature Readiness**: ✅ PASS
+
 - Each functional requirement traces back to user stories and acceptance scenarios
 - User scenarios cover all primary flows: system health monitoring (P1), Golden Signals (P1), engagement tracking (P2), platform comparison (P2), navigation (P1), responsive design (P2)
 - Success criteria measure actual user outcomes (load time, accuracy, accessibility) rather than implementation details