mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 20:42:43 +00:00
Marc-André BombeckandClaude Opus 4.8
a3e741c23c
Tighten the operator-finalised mood catalog to three RATED factors and a trimmed default BINARY tag set. - Seed `factor_sadness` (RATED, 1..5, inverse — higher = worse) under the `factors` category, with its label in all six locales and a CloudRain glyph. The RATED set is now work / sleep quality / sadness. - Retire `factor_conflict`, `factor_family`, `factor_social`, `factor_stress`: flip each to BINARY and deactivate. The catalog rows stay so historical entries still resolve their labels (the insights read joins by id without an active filter); they just leave the RATED set and the default picker. - Trim the default BINARY tag set roughly in half: deactivate the sleep-tag category (now covered by the sleep-quality slider), the mood level restatements, the nutrition long-tail, and low-signal day-type tags. Kept rows are the high-signal, correlatable tags. Nothing is deleted; inactive rows still resolve labels for existing entries. Reference-data only — no schema change, idempotent upsert + closed-key updates, no per-user data touched. 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).