mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
Marc-André Bombeck
963f61cf0f
A lab report's reference range reaches the record by four paths. Three of them validate that the floor does not exceed the ceiling; the document path did not, and the catalog store writes what it is handed. An integration run against a real Postgres confirmed the consequence: a 100/30 pair landed on the row and on the freshly minted biomarker, so every later reading of that analyte inherited a window that cannot be true and a high value came back reassuring. Dropping beats swapping. A transposed pair says the transcription is wrong, not which of the two numbers is, and inventing an order would state something the report never printed. The verbatim string survives either way, so nothing the document actually said is lost. Three points, answering according to what each one is: - the extraction schema drops the pair, because every field there is catch-guarded so one bad value cannot sink a 120-fact document - the review-screen edit refuses with the wording the lab schemas already use, because a person can see both numbers and fix them - the commit path drops it as the last gate, which is what covers facts staged before this rule existed and confirmed afterwards parseReferenceRange has answered a transposed PRINTED window this way since it was written, and the commit path already counts a window it could not read at all. This extends both to the case that was readable and cannot be true.
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 renamedmiddleware). 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 inapiHandler. Seeapp/README.md.lib/— the server/runtime toolkit:apiHandler, auth, crypto, rollups, AI, notifications, pg-boss jobs, integrations, rate limiting. Seelib/README.md.components/— React components (shadcn/ui new-york, kebab-case files). Seecomponents/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 byprisma 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.