mirror of
https://github.com/MBombeck/HealthLog.git
synced 2026-11-08 12:32:43 +00:00
Marc-André Bombeck
70e40e097d
Measured against the route declarations on this tree: The health-background section names allergies, family history and the profile facts, and omits visits, the practices behind them and the vaccination record — all three of which `scope.ts` puts in that section, so a grant is narrower on the page than it is in the product. "Aggregate surfaces appear only on a whole-record grant" is true and incomplete: a whole-record grant does not open them equally either. The daily digest and the dashboard's snapshot answer at read, the health score, the dashboard's summary and the insights need manage. The write level lists seven creates against twelve WRITE declarations. A visit, a practice, a vaccination dose and the booster reminder it suggests were missing, and the guide said nothing about the creates that need manage inside a section a write grant can otherwise add to, or about the vault taking no delegated write at any level. "Exports, the health-record archive" sat under what a delegate cannot reach, while `POST /api/export/health-record` answers at manage on a whole-record grant and its own comment says why. The row is about the full exports and the encrypted archive; the doctor report is named as the exception it is. The sharing-denial guard's docblock carried the same class of stale claim — 116 fenced modules, 26 never published — and that gap is closed on this tree. The caveat becomes an assertion: a new leg recomputes the fenced modules from the route sources and requires every one to be published, and it names no number, because a hard-coded figure is what turned the paragraph into a false statement about the contract. It fails when a published path is withheld from it.