mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
7d25bb7352
The log sheet took its "Day N" header and its "period ended" button from the verdict, which is the answer about today. A January date opened in September read "Day 2", and a back-dated period could only be closed on dates where today happened to be a bleeding day, so the button came and went as unrelated months were filled in. The calendar read now carries, per date, the cycle day of the logged cycle that date belongs to (null before the first start, after today, or past the verdict's ceiling for an open cycle) and whether a one-tap period end can land there. The sheet reads both off the grid day for the date it opened on. Saving a new entry with nothing picked used to write an empty row: the request succeeded, the sheet closed and the calendar had nothing to draw, which read as a save that did nothing. Save now needs something to store and says what, and an emptied existing entry still saves. The sheet also stops writing until the opened date's own entry has loaded, because until then it held the previous date's row id and a quick Save patched the wrong day. On the server, a start recorded a few days after an earlier one is the same period entered in the other order: opening the earlier start now folds the later one into it instead of leaving a one-day cycle in front of it, and a bleed too far before the next start to be its first day and too close to be a cycle of its own no longer infers a start. Opening or removing a start re-attributes the day-logs whose cycle changed.
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.