feat: prepare the next visit from the server's notable window

The block under a planned visit read the day index and up to twelve days
to find what changed, so a dose change on a quiet day could fall out of
the picked days. It now reads GET /api/day/notable for the stretch from
the last visit to today: every change the server names, every notable
reading.

Add a guard that walks every chart, chart mount and calendar heatmap and
fails when one drawn in days lacks the day doors and is not on the
reasoned NOT_HERE list. Give the dose-strength curve, the efficacy chart,
the mood dimensions, the intraday pulse header and the environment note
the same doors.
This commit is contained in:
Marc-André Bombeck committed 2026-10-08 15:30:12 +02:00
1 parent 866e871102
commit c41ec02e92
24 files changed
+1048 -385

No files matched your search

+3
View File
@@ -15,4 +15,7 @@ export const dayKeys = {
day: (date: string) => ["day", "detail", date] as const,
/** `GET /api/day/index`: the window bounds are the key. */
dayIndex: (from: string, to: string) => ["day", "index", from, to] as const,
/** `GET /api/day/notable`: what changed in a window, for a visit. */
dayNotable: (from: string, to: string) =>
["day", "notable", from, to] as const,
};