mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 04:32:42 +00:00
Marc-André Bombeck
f9561395c7
The catalogue guard read the route tree plus a hand-kept list of library modules. The dose-history import builds its file-level codes in a module that list never named, so `empty_file`, `missing_required_columns`, `unreadable_json`, `json_not_an_array` and `json_carries_no_intake_time` shipped on `POST /api/medications/intake/dose-history-import` while the envelope's own description promised every code was enumerated below, and the guard was green because it had not read the file. The sweep now walks the import graph from every route under `src/app`: 1423 modules, resolved through the same `@/…` alias the app uses, with the generated client never opened. A code is read where it is written, however many hops from the route that answers with it, and nothing is hand-listed any more. Seeding from the whole app tree rather than `src/app/api` also reached the clinician share-link document route, whose three codes were missing for the same reason. A tuple of codes is read as a family, like the object form already was, which is what makes the import's union visible; the constant holding it is renamed to the `*_ERROR_CODES` spelling the sweep reads, since a list named for anything else is as likely to be nutrients as error codes. The two sync-ledger writers are cut out of the text first — `errorCode` on `IntegrationStatus` is a different field with the same name. Proven by breaking it both ways: dropping `empty_file` from the catalogue turns the guard red, and a code planted in `src/lib/analytics/compliance.ts`, a module no list ever named, turns it red naming that file.
docs/ — internal reference + operator playbooks
The user-facing documentation lives at https://docs.healthlog.dev — that's the canonical surface for self-hosting guides, integration walkthroughs, AI-provider setup, and the doctor-report workflow.
The files in this directory are the internal operator playbooks, audit notes, and machine-readable specs that ship alongside the source:
api/— the OpenAPI 3.1 spec for the native-client subset (iOS DTO codegen target). Seeapi/README.mdfor the preview commands. Also home to the MCP-server contract:api/mcp-capabilities.md(tools, resources, prompts, write model) andapi/mcp-skills.md(building a connector / skill).ops/— operator runbooks: deploy, backup / restore, encryption-key rotation, password reset and account recovery, env checks, TLS pinning, data repair. These are what an operator reaches for during an incident.self-hosting/— horizontal-scaling notes (HEALTHLOG_PROCESS_TYPE=web|worker|all) and the deploy-pipeline recipe. Routine install steps stay ondocs.healthlog.dev. Includesself-hosting/mcp.md— enabling the off-by-default MCP connector and pointing Claude.ai / ChatGPT / Claude Desktop at it, andself-hosting/sso.md— OIDC SSO login: IdP setup, the identity-pinning security model,OIDC_ONLYconsequences, and the break-glass runbook. Alsoself-hosting/geolite2.md— bringing your own offline GeoLite2 databases viaGEOLITE2_DIRinstead of sending login IPs to a third-party lookup. Andself-hosting/account-sharing.md— letting one account on the instance open another's health record: the three access levels, the eight sections a grant can be narrowed to, managed profiles for somebody with no login and the guardians who look after them, what revocation does and does not undo, and which trust properties of the instance are unchanged by any of it.migration/— migration notes. Currently only v1.3 to v1.4; later releases are covered byCHANGELOG.mdand https://docs.healthlog.dev.integrations/— per-integration reference (Withings, Fitbit, Google Health, WHOOP, Apple Health, AI providers, data import).adr/— architecture decision records.security/— threat-model notes.diagrams/— architecture diagrams rendered through docs.healthlog.dev.releases/— release imagery.apple-store-connect-checklist.md— the iOS submission gate.codex-protocol-spec.md— Codex / ChatGPT OAuth protocol reverse-engineering notes.ui-guidelines.md— UI / a11y house style.
If you're a self-hoster looking to spin up an instance, start at https://docs.healthlog.dev or jump to the Quick Start in the project README.