update feature branch information and incorporate reviewer comments (#992)

marionbarker · web-flow · commit 4439577d077e · 2026-02-26T19:34:19.000-08:00
diff --git a/docs/loop-3/add-cgm.md b/docs/loop-3/add-cgm.md
@@ -181,9 +181,9 @@ Libre 3 sensors have started appearing as well, but are unsupported. Other Libre
  
 #### Add Eversense CGM
 
-With Eversense added to *Loop* you get direct connection to your transmitter for glucose readings and can configure alert notifications. Because the transmitter can only connect to one app at a time, disconnect from the Eversense app, after the initialization phase, and connect to the *Loop* app.
+With Eversense added to *Loop* you get direct connection to your transmitter for glucose readings and can configure alert notifications. Because the transmitter can only connect to one app at a time, you must first disconnect from the Eversense app before you can connect to the *Loop* app.
 
-The *Loop* app does not have glucose notification features, at this time. You can enable the on-transmitter notification within the *Loop* app, so the transmitter will vibrate to alert you of an issue.
+The *Loop* app does not have glucose notification features, at this time. You can enable the on-transmitter notification within the *Loop* app so the transmitter will vibrate to alert you of an issue.
 
 The pairing process of both transmitters are simple:
 
diff --git a/docs/loop-3/displays-v3.md b/docs/loop-3/displays-v3.md
@@ -124,35 +124,35 @@ Tapping on either the Active Insulin or Insulin Delivery charts will open your I
 
 #### Event History and Details
 
-The event history lists pump events such as Temp Basal and Bolus, Suspend and Resume along with other events provided by the pump manager. In general, when the pump returns to Scheduled basal, there is no indication in the list because that action is implied when the preceding Temp Basal event completed (the end of temp basal restores the pump to scheduled basal delivery unless a new temp basal rate event is started.)
+The event history lists pump events such as Temp Basal and Bolus, Suspend and Resume along with other events provided by the pump manager. In general, when the pump returns to Scheduled Basal, there is no indication in the list because that action is implied when the preceding Temp Basal event completed (the end of temp basal restores the pump to scheduled basal delivery unless a new temp basal rate event is started.)
 
 Additional details are available for every pump event. These are displayed by tapping on the event.
 
 #### Manual Bolus Example
 
-The graphic below shows pump event details for a manual bolus of 1 U. The indication this was a manual event initiated by the user is the `automatic` value is false. 
+The graphic below shows pump event details for a manual bolus of 1 U. The `automatic: false` indicates this was a manual event initiated by the user. 
 
 * The left side shows a bolus-in-progress
     * The variable `isMutable` remains true while the bolus is in progress
     * The `deliveredUnits` value is set to `nil` to indicate the final amount is not yet known
     * The value for `units` is the requested bolus amount
 * The right side shows the same event once delivery is finalized
     * The variable `isMutable` is set to false
-    * The `deliveredUnits` value is the final dose as reported by the pump manager and is used by *Loop* to update the earlier esimates *Loop* assumed for this event
+    * The `deliveredUnits` value is the final dose as reported by the pump manager and is used by *Loop* to update the earlier estimates *Loop* assumed for this event
 
 > ![figure showing event details for bolus](img/insulin-event-detail-bolus.svg){width="700"}
 {align="center"}
 
 #### Automatic Temporary Basal Rate Example
 
-The graphic below shows an automatic temporary basal event. The indication this was an automatic event initiated by *Loop* is the `automatic` value is true. 
+The graphic below shows an automatic temporary basal rate (TBR) event. The `automatic: true` indicates this was an automatic event initiated by *Loop*. 
 
 * The left side shows a temporary basal rate (TBR) in progress
     * The variable `isMutable` remains true while the TBR is in progress
     * The `deliveredUnits` value is set to `nil` to indicate the final amount is not yet known
     * The value for `units` is the current temporary basal rate (in U/hr)
     * The end date is based on the planned duration for this TBR
-* The right side shows this same event once it is finalized. In this case, the TBR was superceded by another command.
+* The right side shows this same event once it is finalized. In this case, the TBR was superceded by another command
     * The end date was updated to show the actual end time for this TBR
     * The variable `isMutable` is set to false
     * The `deliveredUnits` value is the final dose as reported by the pump manager and is used by *Loop* to update the earlier esimates *Loop* assumed for this event
diff --git a/docs/version/development.md b/docs/version/development.md
@@ -16,7 +16,7 @@ Please read this entire page before using any version of *Loop* other than the r
 
 This section provides an overview of changes to `dev` compared to `Loop v3.12.0`. 
 
-The current version of `dev` is v3.11.1 and will soon be updated to v3.13.0 to match the new release to v3.12.0.
+The current version of `dev` is v3.13.0 with code identical to that in the `main` branch.
 
 Please check the [development channel in zulipchat](https://loop.zulipchat.com/#narrow/channel/144182-development) for notifications when an update to the `dev` branch is expected so you will be prepared. Do this **before** you install a `dev` build from TestFlight.
 
@@ -45,10 +45,10 @@ The table below lists active branches. Note that updates may occur and be announ
 | <div style="width:140px"> branch | version # | <div style="width:140px">last updated | comments |
 |:--|:--|:--|:--|
 | main | 3.12.0 | 24 Feb 2026 | release|
-| dev | 3.11.1 | 17 Feb 2026 | code is currently the same as `main` |
-| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)<br>- SHA `04dc876` | 3.11.1 | 17 Feb 2026| - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods<br>  - SHA for OmniBLE is `9992773`<br>**Please read [Feature Branch: Pod Keep Alive Feature](#feature-branch-pod-keep-alive-feature)** |
-| [feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support) <br>- SHA `865110f` | 3.11.1 | 17 Feb 2026 | - adds experimental support for Dana and Medtrum pumps<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for DanaKit is `dbe63ae` (Known TBR issues)<br>  - SHA for MedtrumKit is `c79a883` (TBR issues fixed) |
-| [feat/eversense](#feature-branch-eversense-support) <br>- SHA `506d529` | 3.11.1 | 18 Feb 2026 | - adds experimental support for Eversense (includes Dana and Medtrum pumps support too)<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for Eversense is `4a40994` |
+| dev | 3.13.0 | 24 Feb 2026 | code is currently the same as `main` |
+| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)<br>- SHA `f51cf70` | 3.13.0 | 26 Feb 2026| - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods<br>  - SHA for OmniBLE is `9992773`<br>**Please read [Feature Branch: Pod Keep Alive Feature](#feature-branch-pod-keep-alive-feature)** |
+| [feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support) <br>- SHA `309b448` | 3.13.0 | 26 Feb 2026 | - adds experimental support for Dana and Medtrum pumps<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for DanaKit is `3970b2a` (TBR issues fixed)<br>  - SHA for MedtrumKit is `c79a883` (TBR issues fixed) |
+| [feat/eversense](#feature-branch-eversense-support) <br>- SHA `efe5f5c` | 3.13.0 | 26 Feb 2026 | - adds experimental support for Eversense (includes Dana and Medtrum pumps support too)<br>- this branch is ready for expert testers to evaluate and report back<br>  - SHA for Eversense is `e870c22` |
 
 !!! important "Eversense Support"
     The Eversense CGM is now supported by the *Loop* app in a feature branch. To simplify maintenance, the branch which supports Eversense also supports the two new pumps: Dana and Medtrum.
@@ -180,21 +180,32 @@ While RileyLink is selected, the app is triggered by the RileyLink one minute he
 
 ### Feature Branch: Medtrum and Dana Support
 
-General statement about these pump managers. These were created for use with Trio and, at the time, some of the differences between the way Loop and other OS-AID systems handle insulin accounting were not completely understood.
+!!! important "Check your settings, temp basal accounting corrected"
+    The accounting used by Loop requires specific feedback from the Pump Managers. This important information was not initially added to the Dana or Medtrum pump managers. Those both were developed first for Trio which uses a different algorithm and accounts for insulin dosing differently.
+
+    This oversight is fixed for both Dana and Medtrum.
+
+    * Medtrum was fixed on 17 Feb 2026
+    * Dana was fixed on 26 Feb 2026
+
+    If you were using Loop with one of these pumps before those dates, be aware that when you update your build, your settings may need to be adjusted.
+
+General statement about these pump managers. These were originally tested using experimental branches with Trio and, at the time, some of the differences between the way Loop and other OS-AID systems handle insulin accounting were not completely understood.
 
 * Initially the bolusing pump event problem was pointed out and a fix provided
-* There was still an issue with reporting temp basal pump events
-    * This issue was fixed for MedtrumKit on 17 Feb 2026
-    * See the now closed MedtrumKit Issue: [Loop and Medtrum Pump Manager: Basal Delivery Accounting is Not Correct](https://github.com/jbr7rr/MedtrumKit/issues/77)
-* Until there is time to ensure equivalent fixes to the DanaKit repository, those using Dana with Loop should only use Dosing Strategy of Automatic Bolus - the insulin accounting will still not be perfect, but using Automatic Bolus helps
+* There was still an issue with reporting temp basal pump events that was subsequently fixed
+    * This fix was brought into the Loop feature branches which include MedtrumKit on 17 Feb 2026
+        * For more information see the closed MedtrumKit Issue: [Loop and Medtrum Pump Manager: Basal Delivery Accounting is Not Correct](https://github.com/jbr7rr/MedtrumKit/issues/77#issuecomment-3915865502)
+    * This fix was brought into the Loop feature branches which include DanaKit on 26 Feb 2026
+        * For more information see the closed DanaKit Issue: [Loop and DanaKit: Observe Pump Event Details in Loop](https://github.com/bastiaanv/DanaKit/issues/32#issuecomment-3937294107)
 
-Anyone uses these new pump managers need to be using either one of these branches:
+Anyone using these new pump managers must build either one of these branches:
 
 * `feat/dev-dana-medtrum` 
 * `feat/eversense` 
 
 !!! important "Experts Only"
-    Please only use an experimental branch if you are prepared to follow along in zulipchat and are willing to help test and resolve issues.
+    Please only use a feature branch if you are prepared to follow along in zulipchat and are willing to help test and resolve issues.
 
     * Please ensure you have the latest version of a given branch by synching before you build:
         * Mac-Xcode: type `git pull --recurse` to update an existing clone or download a fresh copy
diff --git a/docs/version/releases.md b/docs/version/releases.md
@@ -50,22 +50,22 @@ Release information is found on the [*GitHub*&nbsp;_<span translate="no">LoopKit
 
 **Loop Features**
 
-* Improve Live Activity display
+* Improves Live Activity display
     * handles larger fonts, limits truncation, modifies some displays
     * fixes colored glucose plot bug [Issue 2392](https://github.com/LoopKit/Loop/issues/2392)
-* Support real-time APNS response for remote control commands
+* Supports real-time APNS response for remote control commands
     * This, in combination with *LoopFollow* version 4.5.1 or newer, provides real-time response to report the success of a remote command (or explict error message) returned to the originating *LoopFollow* phone
     * Please see [*LoopFollowDocs*: *Loop* Remote Control](https://loopfollowdocs.org/remote/remote-control-loop/) documentation
     * Support for real-time response in *Loop* added with [NightscoutService PR 19](https://github.com/LoopKit/NightscoutService/pull/19)
 
 **Miscellaneous Features**
 
-* Bring in pretty print for pump event details: [Loop PR 2403](https://github.com/LoopKit/Loop/pull/2403) and [LoopKit PR 586](https://github.com/LoopKit/LoopKit/pull/586)
+* Brings in pretty print for pump event details: [Loop PR 2403](https://github.com/LoopKit/Loop/pull/2403) and [LoopKit PR 586](https://github.com/LoopKit/LoopKit/pull/586)
     * makes the details much easier to interpret, see [Event History and Details](../loop-3/displays-v3.md#event-history-and-details){: target="_blank" }
     * adds a localized date to the pump event display
-* Update support files for Browser Build
-* Update translations
-* Add to the Loop Report Build Details section the list of all submodules used for that build including their branch name and SHA
+* Updates support files for Browser Build
+* Updates translations
+* Adds to the Loop Report Build Details section the list of all submodules used for that build including their branch name and SHA
     * This supports developers and testers working with development and feature branches
 
 - - -
