mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
fb960fb72e
The first cut kept only free-text check-ups due after their reminder and let every reminder with a measurement type roll on. A fortnightly PHQ-9 or GAD-7 reminder is a measurement reminder, and each one still jumped two weeks forward the morning it was sent without the questionnaire being filled. The rule is now the cycle length. A reminder whose next slot is more than seven days away, or that has no cadence, stays due after its reminder until it is satisfied (a matching reading, a lab result or "done"), skipped or snoozed, and is sent again at most once a week. A reminder on a weekly or shorter cycle rolls on as before. Appointments stay one-shot. A reading that lands on an open measurement reminder still sets lastSatisfiedAt and schedules the next cycle from itself. The 0355 repair drops its "no measurement type" condition for the same cycle rule, so the fortnightly questionnaires in the reported shape are put back on the day they were reminded.
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).