Files
HealthLog/src/lib
BernhardBuckel d3916036c2 fix(labs): refuse a reading whose unit differs from its marker's
A numeric lab reading was stored with its value as received and the marker's
unit stamped on it, so 5.6 mmol/L against a marker kept in mg/dL became
5.6 mg/dL and read as far below range. Both the manual/API write and the
scan commit did this; nothing compared the two units.

- POST /api/labs returns 422 labs.unit.mismatch, with the marker's unit and
  the reading's unit in meta, and writes nothing. The unit is compared only
  when one was sent: on the biomarkerId path it may be omitted, and the
  marker's unit is then the stated one. A qualitative reading has no unit.
- The scan commit skips such a row with reason unit_mismatch, so the outcome
  reads partial or failed instead of a clean save, and the toast names the
  analytes concerned rather than saying "duplicates".
- The extract response carries the matched marker's unit. The review screen
  shows a calm badge on a row in another unit, starts it unticked like a
  duplicate, and treats it as a blocking error on the unit field if it is
  ticked anyway.
- A small lab-specific normaliser forgives spelling only: spacing, the micro
  prefix, the case of the litre, and a unit printed in capitals for a short
  list where capitals cannot mean another unit. Case is otherwise significant,
  so mIU/L and MIU/L, or g/L and G/L, are never merged.

The document-commit path already refuses a mismatch and is left as it is.
Readings stored wrongly before this cannot be identified, because the
original unit was never kept; they are not touched.

Adds EN and DE strings; the other locales are left to the maintainers. The
OpenAPI spec and the error-code catalogue carry the new code.

Fixes #1094
2026-10-03 15:44:51 +02:00
..
…
…
…
…
…
…
…
…
…

src/lib/

The server and runtime toolkit. Everything that is not a page, component, or route handler lives here: the API kit, auth, crypto, the rollup tier, AI providers, notifications, background jobs, and the integration clients. Route handlers and RSC pages compose these modules; the modules never reach back into app/.

Core request kit

  • api-handler.ts — the apiHandler wrapper every route uses. Auth resolver (cookie OR Bearer), requireAuth / requireAdmin (admin is cookie-only by construction), idempotency plumbing, Wide-Event builder, GlitchTip forwarder.
  • api-response.ts — the { data, error, meta? } envelope: apiSuccess / apiError, safeJson, trusted-proxy IP resolver, returnAllZodIssues + sanitiseZodIssues.
  • rate-limit.ts — Postgres-backed sliding-window limiter (single atomic upsert); multi-instance correct.
  • idempotency.ts — user-scoped idempotency keys that refuse to cache secret-shaped responses.
  • query-keys/ — the only legal source of TanStack Query queryKey / mutationKey arrays (enforced by an ESLint rule); per-feature files behind the index.ts barrel.
  • safe-fetch.ts — the one documented outbound-egress entry (redirect: "manual" + timeout; optional connect-time DNS-rebinding pin). Raw fetch( under lib/ + app/ is banned by ESLint.
  • db.ts — the Prisma client singleton.
  • crypto.ts — AES-256-GCM at rest with versioned key ids, fail-closed loader, rotation primitives.

Subsystems

  • auth/ — Postgres sessions, secure-cookie flag policy, passkey (WebAuthn) + Argon2id password, per-device refresh-token rotation, HMAC Bearer tokens.
  • ai/ — multi-provider insight + Coach engine: provider-chain.ts, hand-rolled {openai,anthropic,local,codex,mock}-client.ts, coach/, prompts/, citation + confidence helpers.
  • rollups/ — DAY/WEEK/MONTH/YEAR pre-aggregations for measurements, mood, and medication compliance. Read-swap pattern: probe the rollup, fall back to live SQL on a coverage miss.
  • notifications/ — the dispatcher cascade (APNs → Telegram → ntfy → Web Push), per-channel senders/, retry policy, VAPID config.
  • jobs/ — pg-boss workers: reminders, insight pre-generation, backups, retention sweeps, integration backfills. Recurring work belongs here, not in scripts/.
  • integrations/, withings/, whoop/, fitbit/ — OAuth clients and sync services for the device providers; sync/ holds the shared delta-feed plumbing.
  • analytics/ — trend calculations, cadence-aware medication compliance.ts, correlations.
  • insights/, fhir/, doctor-report-*.ts — insight pipeline, FHIR R4 export, client-side doctor-report PDF.
  • openapi/ — Zod registry that is the source of truth for docs/api/openapi.yaml.
  • logging/, observability/, monitoring/ — Wide-Event transports and the central redaction denylists (redact at the egress boundary, not the call site).
  • validations/ — shared Zod schemas, including the SSRF isPublicUrl floor.
  • i18n/, tz/ + timezone.ts, format*.ts — translations, timezone helpers (Berlin for display, UTC in DB), locale formatting.

Conventions

Kebab-case filenames. See ../../CLAUDE.md "Code conventions" and "Security-relevant patterns"; the critical-files map there cites the exact entry points. Most modules carry tests in a sibling __tests__/.