fix(medications): every intake path converges on the slot, and caches cannot resurrect a pre-write body

The external ingest endpoint was the one intake writer that never
attributed to the minted band: it stored a bare row beside the pending
slot, so an early take through the API showed as the last intake while
the slot kept demanding a dose, the ledger recorded an extra plus a
miss, and the day tally counted both. It now resolves the band and
converges onto the pending row like every other path, the Telegram
confirm and skip buttons do the same preferring the reminder's own
slot, and the nightly convergence pass heals the pairs this has
already produced — one band match, one live anchor row, both days'
rollups recomputed. The cache layer fences in-flight builders on
invalidation so a read can neither join a pre-write build nor have a
background refresh re-cache a pre-write body as fresh. Ad-hoc rows no
longer resolve a different slot through the six-hour radius, a bounded
early grace credits a take up to an hour before the window without
crossing the previous band, day-scale cadences taken early downgrade
the slot-day prompt instead of inviting a double dose, the overdue
pill ignores the projector's pending mints, created intakes carry the
same plausibility bounds as edits, slot moves keep the recorded
injection site and dose, both affected days recompute on a moved
toggle, deliberate slot-less skips converge instead of orphaning, the
coach reads adherence from the ledger, the cards and quick-add run in
the user's timezone with the served next-due as the gate, and
schedule-revision, wipe and restore writes invalidate the caches they
feed.

docs/api/openapi.yaml

@@ -2118,7 +2118,7 @@ paths:
       summary: List medications for the calling user
       description: Returns every medication owned by the caller (active + paused), ordered by `createdAt DESC`. Each row
         carries its nested `schedules`, the joined clinical `category`, the latest non-skipped `lastTakenAt`, and the
-        count of intake events scheduled for today (`todayEventCount`). The response is cached server-side for 60 s per
+        count of today's actioned intake events (`todayEventCount`). The response is cached server-side for 60 s per
         user; writes flush the cache.
       responses:
         "200":
@@ -4890,6 +4890,7 @@ components:
           pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$
         takenAt:
           description: When the dose was actually taken. NULL when `skipped` is true; defaults to `now()` for non-skipped intakes.
+            Must not lie in the future (5-minute clock-skew allowance) nor more than 5 years in the past.
           type: string
           format: date-time
           pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$
@@ -8362,7 +8363,9 @@ components:
           type: integer
           minimum: 0
           maximum: 9007199254740991
-          description: Number of intake events scheduled for today (user-local day window).
+          description: "Number of ACTIONED intake events for today (user-local day window): rows with a recorded `takenAt` or an
+            explicit skip. Pending projector-minted rows do not count — the card overdue-pill suppression compares this
+            against the passed-dose count, and a pending mint must not read as covered."
       required:
         - id
         - name