mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
05465a35a5
Invert the inbound-documents surface from an OCR inbox into a document library: a file can be stored without any AI provider, and extraction becomes an opt-in action on top. - Migration 0222: add `title` + `document_date` columns, a `(user_id, document_date)` index, the richer kind taxonomy (lab/imaging/prescription/insurance/vaccination), and a STORED status made the column default. The status enum is recreated so the new value can be set as the default within the migration transaction; kind values use ADD VALUE. Nullable columns, no backfill. - POST /api/documents/inbound is now store-only: bounded multipart read, magic-byte MIME sniff, AES-256-GCM at rest, persisted as STORED with no provider/consent/budget call and no egress. - POST /api/documents/inbound/[id]/extract carries the relocated extraction gauntlet (resolve provider, consent, rate-limit, budget, run, reconcile, stage facts) against an already-stored row; absent a provider it 422s the enhancement only and leaves the stored document intact. - PATCH /api/documents/inbound/[id] edits title/kind/documentDate field-by-field, owner-scoped by session userId. - GET /api/documents/inbound gains search, kind filter, documentDate range, sort, and keyset pagination via the parameter-bound query builder. - Extend the validation schemas + DTO, regenerate the OpenAPI contract, and add route tests for the store/extract/edit/list paths.
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).