Files
HealthLog/src
Marc-André Bombeck 8902d3985c fix(measurements,insights): source-collapse + timezone parity across multi-source surfaces
Four data-correctness fixes in the same class as the workouts-list
ordering bug (05f80ad37):

- GET /api/measurements groupBy=day: the raw-row scan ordered oldest
  first and sliced to `limit` before bucketing, so a long history never
  surfaced its recent days. Reads newest-first now. The per-day sum
  also ran over every source unfiltered — an Apple Health + Withings
  write for the same day doubled the total. Routes through
  pickCanonicalSourceRows first, matching the rollup tile's collapse.

- PR detection's cumulative-day picker summed every row on a calendar
  day regardless of source (false "record" days) and bucketed on the
  UTC calendar day instead of the user's timezone. Rewritten to
  source-collapse before summing and bucket on the user's IANA zone,
  reading through the worker's injected Prisma client so the existing
  dependency-injection contract for tests stays intact.

- The correlation-discovery matrix (the insights route, the per-metric
  assessment card, and the Coach's get_correlations tool — three
  independent copies of the same fetch) averaged cumulative types
  (steps, daylight) and sleep across mismatched grains: per-sample
  chunk means blended with drained daily totals, and sleep averaged
  per-stage segment durations instead of summing a night's total.
  Hoisted the grain resolution into one shared
  buildMeasurementDailySeries helper (source-collapsed day-sum for
  cumulative types, per-night reconstruction for sleep, mean
  unchanged for spot vitals) so all three surfaces agree.

Regression tests cover newest-first ordering, cross-source collapse
matching the rollup, PR no-double-count, and the shared grain helper.
2026-07-17 23:12:12 +02:00
..
2026-07-13 16:33:13 +05:30

src/

Application source. HealthLog is a Next.js 16 App Router project (output: "standalone", React 19, TypeScript strict). The path alias @/* resolves to this directory. Everything a request touches lives under here; the layout below follows the request flow rather than alphabetical order.

Request flow

client → src/proxy.ts → src/app/<route>/route.ts → src/lib/api-handler.ts → handler body → src/lib/api-response.ts → client
  • proxy.ts — the HTTP edge (Next.js 16's renamed middleware). Public-path allowlist, demo-mode mutation block, server-side onboarding redirect, worker-only refusal, x-request-id + CSP nonce generation, every security header.
  • app/ — App Router pages (RSC by default) and API routes. Every API route wraps its handler in apiHandler. See app/README.md.
  • lib/ — the server/runtime toolkit: apiHandler, auth, crypto, rollups, AI, notifications, pg-boss jobs, integrations, rate limiting. See lib/README.md.
  • components/ — React components (shadcn/ui new-york, kebab-case files). See components/README.md.

Other directories

  • hooks/ — shared React hooks (use- prefix, kebab-case).
  • types/ — shared TypeScript declarations.
  • generated/prisma/ — the generated Prisma client (do not edit; regenerated by prisma generate). Imported as @/generated/prisma.
  • instrumentation.ts — Next.js startup hook; boots the pg-boss worker registry and boot-time backfill queues.
  • __tests__/ — cross-cutting unit tests; most tests live in __tests__/ folders next to the code they cover.

Conventions

See ../CLAUDE.md for the full set. The load-bearing ones: RSC by default ("use client" only when a hook/state/browser API needs it); every API route wraps apiHandler and parses its body with Zod safeParse; userId is always narrowed from session or Bearer, never accepted as a body field; TanStack Query keys come only from src/lib/query-keys/; outbound HTTP goes through src/lib/safe-fetch.ts.