[bjorkert]

Trio uploads a PumpSuspend note when the pump suspends and a PumpResume note when it resumes, with no temp basal while suspended. The basal graph now pairs these notes and draws 0 in between, and the Basal info row shows 0 during an ongoing suspend. A suspend without a resume ends at the next temp basal, which covers pod changes where no resume is reported.

[bjorkert]

Tested end to end in the simulator: Trio (dev) with MedtrumKit against a simulated Medtrum Nano, uploading to a local mock Nightscout that LoopFollow on this branch followed.

Suspended for 30 minutes at 20:36 and resumed at 20:48. Trio uploaded the PumpSuspend and PumpResume notes, the Basal row showed 0,8 → 0 during the suspend (left), and the graph draws 0 between the notes and the scheduled basal after the resume (right). The narrow bar at 20:35 is the temp basal the suspend cut short.

Not reproduced: a suspend without a resume ending at the next temp basal. In these runs both MedtrumKit and OmnipodKit uploaded a PumpResume at patch and pod changes, so that path is covered by the unit tests only.

[marionbarker]

Approved by build, test with Loop URL and fact this is being used on developers phone who follows Trio URL.