docs(api): describe how a record-only schedule is kept on update

docs/api/openapi.yaml

@@ -23141,7 +23141,10 @@ components:
             information, but nothing is ever due: no reminder on any channel, no projected slot, no entry on the today
             list or the doses card, and no adherence figure anywhere. Existing intake history stays stored. Switching it
             back on resumes from that moment; the time it was off never counts as missed. Omitted on update leaves the
-            current value."
+            current value. On a medication whose tracking is off, an update that does not name `trackIntake` leaves its
+            stored schedule alone: `schedules`, `asNeeded` and `oneShot` in such a request are ignored (a client that
+            does not know the field cannot have seen the stored schedule, which is served in `recordedSchedules`). Name
+            `trackIntake` to change the schedule of such a medication."
           type: boolean
         schedules:
           type: array
@@ -23463,7 +23466,10 @@ components:
             information, but nothing is ever due: no reminder on any channel, no projected slot, no entry on the today
             list or the doses card, and no adherence figure anywhere. Existing intake history stays stored. Switching it
             back on resumes from that moment; the time it was off never counts as missed. Omitted on update leaves the
-            current value."
+            current value. On a medication whose tracking is off, an update that does not name `trackIntake` leaves its
+            stored schedule alone: `schedules`, `asNeeded` and `oneShot` in such a request are ignored (a client that
+            does not know the field cannot have seen the stored schedule, which is served in `recordedSchedules`). Name
+            `trackIntake` to change the schedule of such a medication."
           type: boolean
         schedules:
           type: array