mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
Marc-André BombeckandClaude Opus 4.8
ac13dd28ed
- When the sensitive-category encryption preference is on (the default), encrypt the intent-revealing day-log fields (sexual activity, protection, pregnancy/progesterone tests, contraception) into an encrypted envelope and leave the queryable columns null, decrypting on read. The toggle now does what it says rather than storing those fields in plaintext. - Make the day-log write a partial merge so a re-log only overwrites the fields it carries, never nulling untouched ones (no more data loss when the same day is logged again). - Make the upsert collision-safe: a manual entry and an imported entry on the same date adopt one canonical row instead of throwing, and the single POST returns a clean conflict rather than a 500; one bad date no longer aborts a whole import. - Compare the decrypted note, not the ciphertext, so an unchanged re-log is a true no-op and stops needless re-sync. - Hoist cycle attribution out of the per-entry loop; map bulk failures to stable reason codes; audit the import goal change; mask the event name in discreet reminder pushes; add a one-tap hard-delete purge for all cycle data. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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).