mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
Marc-André Bombeck
b6ded4d1f9
The nightly insight pre-pass runs ~04:30, before last night's sleep has synced, so the morning digest and health score reference the day without the current sleep. Close the gap the event-driven way instead of an on-mount generation. A day's digest is now provisional until the sleep-dependent output has been regenerated with last night's sleep, and final after. The lifecycle is driven by a real marker (User.morningDigestRefreshedOn, the user-local date the refresh completed), not a heuristic: it flips the instant the refresh runs, ahead of the snapshot cache that feeds the sleep last-seen fallback. A day with no sleep device stays honestly provisional and keeps the sleep-pending note rather than showing a stale final score. When a completed sleep segment for last night lands from any of the three sleep transports — Withings sync-sleep, the WHOOP sync, the Apple-Health measurement batch — a debounced morning-digest-refresh job is enqueued. "Last night" is judged in the user's profile timezone, so a full-history re-sync never re-triggers for an old night. The queue singletonKey plus the marker collapse the many samples of one night, across all sources, into one refresh per user per local morning; the job re-runs the same comprehensive pipeline the nightly cron uses (forced, so the content-hash gate turns a no-change regen into a cheap no-op) and stamps the marker. A hard generation failure leaves the day provisional and hands recovery to the existing 45-minute briefing-retry machinery.
prisma/
The database layer. HealthLog runs PostgreSQL 16 via Prisma 7. This directory holds the single schema file and the forward-only migration history; the generated client is emitted elsewhere.
Contents
schema.prisma— 61 models, one file.cuid()primary keys,snake_casecolumns via@map(...), encrypted columns mostly suffixed*Encrypted(search the file; there are 24 encrypted column references). Thegenerator clientblock emits to../src/generated/prisma(imported as@/generated/prisma).migrations/— numbered, forward-only SQL migrations (0001_…upward).migration_lock.tomlpins the provider topostgresql.
Migration workflow
# author a migration from a schema edit
pnpm dlx prisma migrate dev --name <short_snake_case_name>
# regenerate the client after any schema change
pnpm dlx prisma generate
Number a new migration with the next free prefix. The production entrypoint runs prisma migrate deploy on boot, so every migration must apply cleanly forward — there is no down-migration path. Always include the migration file in the same change as the schema edit.
Conventions
- Encryption is fail-closed:
*Encryptedcolumns are written through@/lib/crypto(AES-256-GCM, versioned key ids); never store plaintext in an encrypted column. Key rotation isscripts/rotate-encryption-key.ts+docs/ops/encryption-key-rotation.md. - The generated client under
src/generated/prismais build output — do not edit it. - Schema-touching changes that affect the API surface must regenerate
docs/api/openapi.yaml(see../CLAUDE.md).
Related: ../src/lib/README.md (db.ts, rollups/), ../docs/ops/ (migrations + backup runbooks).