fix(daily-loop): thread the overdue medication id into the digest's Log-dose link

The Today digest's dose-window rail item linked to the bare /medications
list even though the overdue medication's id was already resolved
server-side alongside its name — a tap landed the user on a generic list
they then had to scan themselves.

buildMedsTodayBlock now carries nextDueMedicationId; the digest's
"Log dose" action links to /medications?highlight=<id> when the id is
known, falling back to the bare list for an older cached block. The
medications page reads the highlight param, scrolls the matching card
into view, and rings it briefly (mirrors the vault's duplicate-upload
highlight) in both the card grid and the table view. Regenerates
docs/api/openapi.yaml for the new medsToday field.

docs/api/openapi.yaml

@@ -23987,6 +23987,10 @@ components:
               anyOf:
                 - type: string
                 - type: "null"
+            nextDueMedicationId:
+              anyOf:
+                - type: string
+                - type: "null"
           required:
             - activeCount
             - scheduledToday
@@ -23995,12 +23999,14 @@ components:
             - nextDueAt
             - nextDueOverdue
             - nextDueMedicationName
+            - nextDueMedicationId
           additionalProperties: false
           description: "Today's medication block: active-medication count, today-window tally (scheduled / taken / skipped), and
             the earliest next-due slot across active medications. `nextDueOverdue: true` marks an OPEN overdue slot
-            (anchor passed, still inside its catch-up band). Staleness contract: the snapshot is cache-served, so a
-            `nextDueAt` in the past with `nextDueOverdue: false` means the anchor passed after the snapshot was built —
-            render the plain day summary, never an overdue state."
+            (anchor passed, still inside its catch-up band). `nextDueMedicationId` deep-links a consumer straight to the
+            overdue medication's card. Staleness contract: the snapshot is cache-served, so a `nextDueAt` in the past
+            with `nextDueOverdue: false` means the anchor passed after the snapshot was built — render the plain day
+            summary, never an overdue state."
         healthScore:
           anyOf:
             - type: object