mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
7ddcee0445
/api/auth/me/health-score-config shipped in v1.35.0 with a settings page in front of it and no entry in the contract at all — no path, no schemas, nothing. A client had the surface and no way to generate against it. This is publication only; the route does what it already did. Both verbs are registered off what the route actually returns rather than off a neighbour's shape. The asymmetry matters and is now written down: the request speaks the positive selection, the pillars that should count, while the response carries both sides resolved plus the recipe version. The column stores the complement, which is storage and no client's business. The response's updatedAt is documented as optional because it genuinely is absent until a selection exists — an account that never chose has nothing to guard a write against, and a decoder that required the field would break on that read. The PATCH 422 is written out rather than reusing the shared base-token response, because this route has four of them and a client branching on meta.errorCode needs all four: the breadth refusal with the sentence to show the person, the validation failure, the unparseable base token, and the non-JSON body. Naming only the token would have been a contract that omits the refusal people actually hit. The route test now drives the real route to produce each of those responses and asserts the published contract names every code that comes back, so a response the route can emit but the spec does not describe fails the suite. That closes the base-token ledger: nine routes emit invalid_base_updated_at and all nine now document it.
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.