mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 04:32:42 +00:00
Marc-André Bombeck
95140e5aa7
A taken, skipped or auto-missed row counted as resolving every occurrence within six hours of its anchor. The radius was sized for the twice-daily 12 h gap, so on any schedule whose neighbouring doses sit closer than that (19:49 and 23:59, 08:00 and 12:00, every four hours) the first dose's row resolved the second occurrence too: the next-due walk jumped to tomorrow, the card offered tomorrow's first dose, and a skip pressed next landed there. The second dose could not be logged from the card at all. Reproduced with a Europe/Berlin account on 19:49 + 23:59: the 19:49 take left the 23:59 row pending and the skip was written to tomorrow's 19:49. The compliance-journey e2e spec exposed the same thing in every run that started after noon, when its twin slot is 23:59. Rule, in slot-resolution.ts and shared by the list's next-due, the card's overdue search and the compliance current-cycle descriptor: a row resolves exactly one occurrence, the one nearest its anchor, and only within the drift radius. An exact match short-circuits; a drifted anchor is measured against every occurrence the schedule emits within the radius and loses to any nearer one (ties go to the earlier occurrence), so the effective reach is min(radius, half the gap to the neighbour) and a sibling can never be swallowed. Rolling cadences skip the nearest test, their occurrences are at least a day apart. Ad-hoc rows keep the one-minute epsilon, now in the cycle descriptor as well, so the card's due slot and its cycle state agree. The drift tolerance itself stays: it covers a row whose anchor sits off the canonical instant, a pre-snap row or an instant that moved under it across a DST shift, which is what the radius was introduced for in v1.15.10.
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— theapiHandlerwrapper 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 QueryqueryKey/mutationKeyarrays (enforced by an ESLint rule); per-feature files behind theindex.tsbarrel.safe-fetch.ts— the one documented outbound-egress entry (redirect: "manual"+ timeout; optional connect-time DNS-rebinding pin). Rawfetch(underlib/+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-channelsenders/, retry policy, VAPID config.jobs/— pg-boss workers: reminders, insight pre-generation, backups, retention sweeps, integration backfills. Recurring work belongs here, not inscripts/.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 medicationcompliance.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 fordocs/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 SSRFisPublicUrlfloor.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__/.