mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
a402eaaf15
A Coach retrieval tool that read the window and found nothing returned `reason: "no_data"` — the same code for two situations that have nothing in common: the record holds nothing for that metric, and the record holds a substantial history for it, all of it older than the window that was searched. Nothing downstream could tell them apart, so the Coach said the honest-sounding sentence for the wrong case, and then, having been told there was nothing there, changed the subject. Someone with a year of imported glucose readings was told the readings did not exist, on the same account whose glucose page was showing them. The window cap stays. It exists because a multi-year history does not fit a prompt budget, and widening it would only move the same failure. What was missing is the ability to say a different true sentence. - `tools/availability.ts` — one grouped aggregate per miss, no rows materialised, resolving four states: `no_data` (probe confirmed empty), `outside_window` (rows exist, older than the searched window; carries the count, the date range in the user's own timezone, and a bounded per-series mean/min/max), `unavailable_in_scope` (rows exist inside the window and the domain still produced none — a module is off), and `no_data_unconfirmed` (the probe itself failed; absence was never established, so it is not asserted). - Every empty read in the executor routes through it. A bare `no_data` can no longer be returned without the record having been checked. - The DATA INVENTORY carries the same distinction, so a domain the window cannot reach is advertised with what it holds instead of as absent — the model no longer skips the fetch, and a vague follow-up keeps the subject. - Both instructions that told the model to report absence and move on now branch on the reason code, and forbid answering about one metric by reporting another. - The out-of-window aggregate joins the authoritative set for the prose verifier, so the sentence the fix exists to make sayable is not elided. - A cross-cutting narration block that throws is now counted rather than vanishing into a `null` that looks like honest absence. - The medication-compliance page tells a failed read apart from an account with no medications, instead of inviting someone to re-enter what it already holds. Refs #648
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.