feat(insights): add generic per-metric assessment loader

Add a parameterised query key (insightsMetricStatus) and a
useInsightMetricStatus hook that reads the generic per-metric
assessment route GET /api/insights/metric-status?metric=<id>. The
seven bespoke status routes keep their own keys and hook union; this
one covers the HealthKit metric sub-pages that share a single route
keyed by the metric id. The hook mirrors the existing status loader:
8 s client ceiling, no inline retry, and the bounded preparing poll.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
(cherry picked from commit a3407a2f6c1e9f54c92a6f182db894ae0593e69f)

src/lib/query-keys.ts

@@ -103,6 +103,16 @@ export const queryKeys = {
     ["insights", "mood-status", locale] as const,
   insightsMedicationComplianceStatus: (locale: string) =>
     ["insights", "medication-compliance-status", locale] as const,
+  /**
+   * v1.8.7.1 — per-metric insight assessment for the HealthKit metric
+   * sub-pages. One generic route (`/api/insights/metric-status?metric=…`)
+   * backs every HealthKit metric, so the key is parameterised by the
+   * metric id alongside the locale rather than minting a bespoke factory
+   * entry per metric. The seven bespoke `*-status` routes above keep
+   * their own keys; this one covers the ~29 generic HealthKit pages.
+   */
+  insightsMetricStatus: (metric: string, locale: string) =>
+    ["insights", "metric-status", metric, locale] as const,
 
   medications: () => ["medications"] as const,
   medicationDetail: (id: string) => ["medications", id] as const,