Marc-André Bombeck 0dcafeeb70 fix(visits): open an upcoming appointment where it lives ...

Visits are the second tab of `/checkups`, and the bare path opens the
first one, the preventive-care list, which never shows an appointment.
Every surface that listed an upcoming appointment linked it there: the
dashboard's next-appointment line, the Today rail item, the Today
overview fact and the appointment's push notification. A tap on the
appointment landed on the list it is not on.

Each now opens the visit itself (`/checkups?visit=<id>`), or the visits
tab (`/checkups?view=visits`) for a line naming several appointments.
The checkups page reads `view` to pick a tab. The rail item stops
borrowing the check-up item's action: it carries its own label
("View appointment") and intent `visit.view`. The appointment push names
its visit through the producer's `metadata.url` override; a check-up's
push keeps the checkups list.

The same mis-route sat on three links that lead to visits without
being upcoming: a condition's visit rows, the address book's back link
and the onboarding and timeline prompts to add a visit.

`visit-link-guard.test.ts` keeps the visit paths in the builder and
counts every bare `/checkups` per file, each with the reason it names
the checkups list.

2026-10-21 12:22:36 +02:00

..

__tests__

fix(timeline): keep every medication still taken on its row, and the chronicle honest

2026-10-09 16:05:40 +02:00

lanes.ts

refactor(visits): build every link to a visit in one place

2026-10-21 12:22:22 +02:00

load-timeline.ts

fix(timeline): keep every medication still taken on its row, and the chronicle honest

2026-10-09 16:05:40 +02:00

readiness.ts

fix(visits): open an upcoming appointment where it lives

2026-10-21 12:22:36 +02:00

series.ts

fix(timeline): read the sleep line as time asleep per night

2026-10-09 14:11:46 +02:00