update LoopDocs for dev version 3.11.1 (#987)

Author: marionbarker

docs/browser/build-dev-browser.md

@@ -1,6 +1,6 @@
 ## Overview
 
-**This page is only relevant when building the `dev` branch with a browser.**
+**This page is only relevant when building the `dev` (or a feature) branch with a browser.**
 
 **For *Mac*, please see: [Build Loop `dev` with *Mac*](../build/build-dev-mac.md)**
 
@@ -28,27 +28,46 @@ The graphics on this page show the `dev` branch. If you want a different branch,
         * You cannot just rename your existing branch to `dev` - you must get the `dev` branch from LoopKit
     1. When you select the action `4. Build Loop` and then click on the `Run Workflow` dropdown, you must select `dev` there before clicking the green `Run workflow` button - see [Build `Branch`](#build-branch)
 
-
 ### Check Current `Branch`
 
 Your `LoopWorkspace fork` is at `https://github.com/username/LoopWorkspace` where you substitute your actual *GitHub* `username`. You need to be logged into *GitHub*. Review the graphic below as you go through the steps.
 
 1. Click on the `branch` icon to display the `branches` as shown in the lower half of the graphic below:
     * If the `branch` you want is not listed, then continue with Step 2
     * Otherwise, skip ahead to [Update `Branch`](#update-branch)
-1. Click on the `New branch` button and follow the [Add `Branch`](#add-branch) steps
+1. Click on the `New branch` button
+    * To add the `dev` branch, go to the [Add `Branch`](#add-branch) instructions
+    * To add a feature branch, start with [Feature `Branch`](#feature-branch) before continuing with the add `branch` instructions
 
 ![steps to add a branch](img/add-branch-01.svg){width="700"}
 {align="center"}
 
+### Feature `Branch`
+
+If you're building `dev`, you can skip ahead to [Add `Branch`](#add-branch).  If you're building a feature branch, copy the branch name into your paste buffer to minimize typographical errors.
+
+
+``` { .bash .copy }
+feat/pod-keep-alive
+```
+
+``` { .bash .copy }
+feat/dev-dana-medtrum
+```
+
+``` { .bash .copy }
+feat/eversense
+```
+
 ### Add `Branch`
 
 Each step in the list below matches with the number in the graphic. In the top half of the graphic, the left side shows the initial display and the right side shows the display after making the indicated selections:
 
 1. Click on the drop down menu labeled 1 in the graphic and choose LoopKit/LoopWorkspace as show in the top right graphic
 2. Click on the drop down menu labeled 2 in the graphic and choose `dev`
-3. Click on the `Branch` name box labeled 3 in the graphic and type `dev`
-    * The branch name in your `fork` should always match the branch name you are adding; check that you type it correctly
+3. Click on the `Branch` name box labeled 3 in the graphic and type `dev` or paste the feature branch name from your paste buffer
+    * The branch name in your `fork` should always match the branch name you are adding - it is best to use a paste buffer (to minimize typographical errors)
+    * See [Feature Branch](#feature-branch) if you need to fill your paste buffer
 4. Review the dialog items to make sure everything is correct and then tap on Create branch
 
 ![steps to add a branch continued](img/add-branch-02.svg){width="700"}

docs/build/build-dev-mac.md

@@ -13,7 +13,7 @@
 
 The same script is used to build the `dev` branch as is used to build the `main` branch. Copy and paste this command in any terminal. Follow the instructions on the screen. Choose Build Loop and then choose `dev` branch.
 
-``` { title="Copy and Paste to start the BuildLoop Script" }
+``` { .bash .copy title="Copy and Paste to start the BuildLoop Script" }
 /bin/bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/BuildSelectScript.sh)"
 ```
@@ -34,15 +34,15 @@ In the command (shown below), there is a space after the final quote, followed b
 
 > This is just an example. You need to substitute the branch you desire for `other-branch`. The example below uses a continuation character to put the extra characters on a new line to make this easier to read.
 
-``` { title="Replace <code>other-branch</code> with the desired branch" }
+``` { .bash .copy title="Replace <code>other-branch</code> with the desired branch" }
 /bin/bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/BuildLoop.sh)" \
    - other-branch
 ```
 
 If you want to customize this custom branch. You can call the Customization Select script after you download the custom branch. This script finds the most recent download in your ~/Downloads/BuildLoop folder. If you want to customize a specific branch, first set the terminal to be in the LoopWorkspace folder for the download you want to customize.
 
-``` { title="Copy and paste to start the CustomizationSelect script" }
+``` { .bash .copy title="Copy and paste to start the CustomizationSelect script" }
 /bin/bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/CustomizationSelect.sh)"
 ```

docs/build/cgm.md

@@ -14,15 +14,15 @@
         * *Dexcom* ONE+ (based off G7 sensor) is available in some countries
     - *Medtronic* sensors connected to a Loop-compatible *Medtronic* pumps
     - Some *Libre* sensors
-    - Eversense XL & 365 sensors
+    - Eversense E3 and 365 sensors
 
 !!! question "FAQs"
 
     - **"What about other *Libre* sensors?"**
         1. Only some *Libre* sensors have methods to read them directly on an iPhone
         2. There are more methods for Android
         3. See also [CGM Customization](../faqs/cgm-faqs.md#cgm-customization){: target="_blank" }
-    - **"What about Eversense?"** Refer to [CGMs Not Supported in the *Loop* App](#cgms-not-supported-in-the-loop-app)
+    - **"What about Eversense?"** Refer to [*Eversense* E3 and 365 CGM](#eversense-e3-and-365-cgm)
 
 
 ## Continuous Glucose Monitor (CGM)
@@ -59,13 +59,15 @@ With Loop 3.4 and newer versions, some *Libre* CGM are supported.
     * *Libre* 3
 * See [CGM Customization](../faqs/cgm-faqs.md#cgm-customization){: target="_blank" }
 
-## *Eversense* E3 & 365 CGM
+## *Eversense* E3 and 365 CGM
 ![img/eversense.png](img/eversense.png){width="150"}
 
 Both the Eversense E3 (90 days & 180 days) and the Eversense 365 (full year) transmitters are supported, on an experimental branch feat/eversense.
 
-Eversense E3 & 365 are implantable continuous glucose monitoring (CGM) systems with a sensor inserted under the skin and a removable on-body transmitter that sends real-time glucose data and alerts to the *Loop* app.
-Unlike traditional CGMs that require frequent sensor changes, Eversense reduces insertion frequency but requires regular fingerstick calibrations.
+* See [Loop Development: Branches](../version/development.md#branches){: target="_blank" } for more information on how to build this branch.
+
+Eversense E3 and 365 are implantable continuous glucose monitoring (CGM) systems with a sensor inserted under the skin and a removable on-body transmitter that sends real-time glucose data and alerts to the *Loop* app.
+Unlike traditional CGMs that require frequent sensor changes, Eversense reduces insertion frequency but requires weekly fingerstick calibrations.
 
 ## *Medtronic* CGM
 ![img/enlite.png](img/enlite.png){width="150"}
@@ -87,13 +89,13 @@ The *Loop* app can download *Dexcom* Share data for use in modeling glucose. How
 
 ## Nightscout as a Remote CGM
 
-Version 3 or later of the *Loop* app can use Nightscout as a remote source for CGM data. This requires cell or WiFi connection.
+The *Loop* app allows you to use Nightscout as a remote source for CGM data. This requires cell or WiFi connection.
 
 
 ## CGMs Not Supported in the *Loop* App 
 
 
-Currently, there are no solutions for *Eversense*, *Guardian* or *Libre 3* CGM to be used directly with the *Loop* app, but some [Uploaders](https://nightscout.github.io/uploader/uploaders/) to Nightscout are available using an Android phone. Version 3 or later of the *Loop* app allows the use of Nightscout as a CGM source.
+Currently, there are no solutions for *Guardian* or *Libre 3* CGM to be used directly with the *Loop* app, but some [Uploaders](https://nightscout.github.io/uploader/uploaders/) to Nightscout are available using an Android phone. Version 3 or later of the *Loop* app allows the use of Nightscout as a CGM source.
 
 ## Next Step
 

docs/faqs/cgm-faqs.md

@@ -4,7 +4,7 @@ The following CGM are supported by some or all versions of Loop:
 
 * All *Dexcom* CGM (Loop 3 and later)
 * Some *Libre* CGM (Loop 3.4 and later)
-* Eversense E3 & 365 (Loop 3.11 and later, via experimental branch)
+* Eversense E3 and 365 (Loop 3.11 and later, via an experimental feature branch)
 * Medtronic Enlite CGM when used with a compatible pump
 * Remote CGM (requires internet access)
     * *Dexcom* Share
@@ -131,7 +131,10 @@ If you prefer not to customize Loop, then you can configure [Nightscout](https:/
 
 ## Can I use Eversense E3 or Eversense 365?
 
-Using the experimental branch, feat/eversense using Loop 3.11.0, you can make a native connection to your Eversense E3 and 365.
+Using the experimental branch, feat/eversense using Loop 3.11.0 or newer, you can make a native connection to your Eversense E3 or 365.
+
+* See [Loop Development: Branches](../version/development.md#branches){: target="_blank" } for more information on how to build this branch.
+
 
 ## Can the *Loop* app read CGM data from Nightscout?
 

docs/version/development.md

@@ -4,7 +4,9 @@ The early history of the *Loop* app was touched on in the introductory [*LoopDoc
 
 The [*Loop* Releases](../version/releases.md) page lists releases since version 2.0 in reverse chronological order.
 
-The next version of the *Loop* app is developed using branch(es), independent of the released *Loop* version, which is found in <span>the `main` branch</span>. <span>The `dev` branch</span> is used by the developers to push out changes for users to test. You should only test a development branch if you are willing to be both an active participant with the developers to monitor announcements and provide feedback and to build frequently to obtain the latest feature or bug-fix that is being tested. If you are willing to help out - this is the way the next release of *Loop* is improved.
+The next version of the *Loop* app is developed using branch(es), independent of the released *Loop* version, which is found in <span>the `main` branch</span>. 
+
+<span>The `dev` branch</span> is used by the developers to push out changes for users to test. You should only test a development branch if you are willing to be both an active participant with the developers to monitor announcements and provide feedback and to build frequently to obtain the latest feature or bug-fix that is being tested. If you are willing to help out - this is the way the next release of *Loop* is improved.
 
 If you choose to use `dev`, you accept that this code is not released.
 
@@ -14,7 +16,8 @@ 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.10.0`. 
 
-A few days after v3.10.0 was released, the dev branch was updated to be identical to main except for version number of 3.11.0. Work leading to the next update for `dev` is found in the `update_dev_to_3.11.1` branch.
+The current version of `dev` is v3.11.1.
+
 
 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.
 
@@ -43,11 +46,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.10.0 | 10 Jan 2026 | release|
-| dev | 3.11.0 | 11 Jan 2026 | same as main, except version number |
-| [update_dev_to_3.11.1](#update-to-dev-3111) | 3.11.1 | 02 Feb 2026 | collect updates for the next version of dev <br>Details are in [PR 408](https://github.com/LoopKit/LoopWorkspace/pull/408) |
-| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)<br>- SHA `783d390` | 3.11.1 | 02 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 `0282e18` | 3.11.1 | 02 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`<br>  - SHA for MedtrumKit is `f21d808` |
-| [feat/eversense](#feature-branch-eversense-support) <br>- SHA `41d63dd` | 3.11.0 | 24 Jan 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 `a478d8f` |
+| dev | 3.11.1 | 17 Feb 2026 | updates with respect to `main` include<br>[PR 408](https://github.com/LoopKit/LoopWorkspace/pull/408) |
+| [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 `84bf0c7` | 3.11.0 | 17 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` |
 
 !!! 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.
@@ -68,24 +70,28 @@ For full instructions on building different branches, review these pages:
 * [Browser Build: Build a Version in Development](../browser/build-dev-browser.md#build-development-version){: target="_blank" }
 * [Mac Xcode: Build a Version in Development](../build/build-dev-mac.md#build-other-branches){: target="_blank" }
 
-For Browser Build, use the page linked above to add the desired branch name (from the table above) to your fork. In other words, where the directions indicate the `dev` branch, you substitute the branch name of interest.
+#### Browser Build
+
+Use the page linked above to add the desired branch name (from the table above) to your fork. In other words, where the directions indicate the `dev` branch, you substitute the branch name of interest.
+
+#### Mac-Xcode Build 
 
 For Mac Xcode build, the lines you need to copy and paste into a Terminal window are explicitly provided below:
 
 
-``` { title="Download and build the feat/pod-keep-alive branch" }
+``` { .bash .copy title="Download and build the feat/pod-keep-alive branch" }
 /bin/bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/BuildLoop.sh)" \
    - feat/pod-keep-alive
 ```
 
-``` { title="Download and build the feat/dev-dana-medtrum branch" }
+``` { .bash .copy  title="Download and build the feat/dev-dana-medtrum branch" }
 /bin/bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/BuildLoop.sh)" \
    - feat/dev-dana-medtrum
 ```
 
-``` { title="Download and build the feat/eversense branch" }
+``` { .bash .copy title="Download and build the feat/eversense branch" }
 /bin/bash -c "$(curl -fsSL \
   https://raw.githubusercontent.com/loopandlearn/lnl-scripts/main/BuildLoop.sh)" \
    - feat/eversense
@@ -179,15 +185,25 @@ While RileyLink is selected, the app is triggered by the RileyLink one minute he
 
 ### Feature Branch: Medtrum and Dana Support
 
-**Updates are believed to have fixed the active insulin issues reported for both Dana and Medtrum, but this should be tested by experts to confirm pumps are working well with Loop.**
+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.
+
+* 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
+
+Anyone uses these new pump managers need to be using either one of these branches:
+
+* `feat/dev-dana-medtrum` 
+* `feat/eversense` 
 
 !!! important "Experts Only"
-    Please only use the `feat/dev-dana-medtrum` branch if you are prepared to follow along in zulipchat and are willing to test an experimental branch to help test and resolve issues.
+    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 ensure you have the latest version of this branch by synching before you build:
-        * `feat/dev-dana-medtrum`
+    * 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
-        * Browser Build, the Build Loop action, with the `feat/dev-dana-medtrum` branch selected should automatically sync your fork for you
+        * Browser Build, the Build Loop action, with the `feat/dev-dana-medtrum` or `feat/eversense` branch selected should automatically sync your fork for you
 
 
 ### Feature Branch: Eversense Support