Merge pull request #907 from marionbarker/working-docs

modify graphics and words for Loop 3.6.0

Author: marionbarker

docs/browser/bb-update.md

@@ -115,6 +115,15 @@ Digital Service Act Compliance
 
 Open your *GitHub* account and select your <code>LoopWorkspace repository</code> from your repositories list.
 
+### Special Instructions for 3.6.0
+
+When updating to version 3.6.0, there are two "extra" things to do.
+
+* [Add Variable](prepare-fork.md#add-variable){: target="_blank" } to enable automatic renewal of certificates
+* Manually update (sync) the fork - as described in this section
+    * With automatic build, you typically let the automatic process update the fork for you
+    * In this case, a third-party repository was removed by *GitHub* at the same time version 3.6.0 was released - this change prevented any builds from working - including the automatic sync that normally happens
+
 ### Up to Date or Behind
 
 The bullets below show typical messages when you are building the `main` branch. If you are building a different `branch`, the messages show that `branch name` instead of `main`.

docs/loop-3/img/meal-bolus-rec.svg

@@ -1,31 +1,21 @@
-## Updates with version 3 and later
-
-* Loop 3 uses the setting name of Glucose Safety Limit, which has the same meaning as Suspend Threshold in Loop 2
-* With Loop 3.2 and later
-    * Loop automatic delivery of insulin is limited when users IOB is two times the [<code>Maximum Bolus</code>](../../loop-3/therapy-settings.md#maximum-bolus) amount
-* Bolus Row: 
-    * With Loop 3.0 and later
-        * The Recommended Bolus is provided AND the default for the Bolus is the recommended value
-        * If the user taps on the Bolus row, the amount is modified to 0 and the keyboard is opened for entry
-
 ## Meal Bolus
 
-The **Meal Bolus** screen is entered following a carb entry or edit action, the active button might be **Save and Bolus** or, if no bolus was recommended, **Save without Bolusing**. 
+The **Meal Bolus** screen is entered following a carb entry or edit action, the active button might be **Save Carbs & Deliver** or, if no bolus was recommended, **Save without Bolusing**. 
 
 The **Save** refers to saving the Carb entry or Carb edit that led to this screen in addition to saving the amount that might be bolused. It can also refer to saving a fingerstick value entered in the Meal Bolus screen (Loop 3 only).
 
 You can review the carb information at the [Meal Entry](carbs.md) link.
 
 !!! Important "Avoid Double Entry of Carbohydrates"
-    Carbohydrates are saved when the `Save and Bolus` or `Save without Bolusing` button is tapped in the Meal Bolus Screen. Once that the button is tapped, carbohydrates are saved. That is true even if the bolus does not go through to the pump.
+    Carbohydrates are saved when the `Save Carbs & Deliver` or `Save without Bolusing` button is tapped in the Meal Bolus Screen. Once that the button is tapped, carbohydrates are saved. That is true even if the bolus does not go through to the pump.
 
     If you see a notification after saving a carbohydrate entry, check carbohydrates entries in the *Loop* app. Do **not** just add the entry again without checking.
 
 ### Accept Recommendation
 
 The graphic below shows the Meal Bolus screen after the user entered carbs and tapped continue:
 
-* The left graphic shows a case where a bolus is recommended - tapping on the **Save and Deliver** button saves the carbs and delivers the bolus
+* The left graphic shows a case where a bolus is recommended - tapping on the **Save Carbs & Deliver** button saves the carbs and delivers the bolus
 * The right graphic shows a case where no bolus is recommended - tapping on the **Save without Bolusing** saves the carbs
 * These graphics are taken from a small phone - the left graphic shows all the information at once whereas the right graphic has an extra information message that requires the user to scroll to see the **Recommended Bolus** and **Bolus** rows
 * For both graphics
@@ -46,15 +36,15 @@ This section is a continuation of the information presented in the [Accept Recom
 
 * The left side shows a modified bolus less than the recommended bolus
 * The right side shows a modified bolus greater than the recommended bolus
-* The **Glucose** prediction graph updates with changes to the **Bolus** value, giving the user the opportunity to accept or change their proposed value before tapping **Save and Deliver**
+* The **Glucose** prediction graph updates with changes to the **Bolus** value, giving the user the opportunity to accept or change their proposed value before tapping **Save Carbs & Deliver**
 * At the next Loop cycle, the app modifies insulin delivery based on the saved information
     * For the example with bolus less than recommended amount:
         * Loop will **NOT** begin to automatically increase insulin delivery until the current glucose is above the bottom of the **Correction** range
         * The recommendation to add insulin when the current glucose is below the **Correction Range** is only offered as a manual feature and is limited to an amount predicted to maintain glucose above the **Safety Threshold**
     * For the example with bolus greater than recommended amount:
         * Loop will probably issue an automatic temp basal of 0 U/hr
         * This is a common "super-bolus" scenario; in other words, "borrow" basal for the meal bolus to limit post meal spikes
-* Remember - the **Glucose** prediction is what happens if you **Save and Deliver** and then no further adjustments are made to insulin delivery by Loop
+* Remember - the **Glucose** prediction is what happens if you **Save Carbs & Deliver** and then no further adjustments are made to insulin delivery by Loop
 
 ![meal bolus when bolus recommended is decreased on left and increased on right](../../loop-3/img/meal-bolus-mod-rec.svg){width="900"}
 {align="center"}

docs/operation/features/bolus.md

@@ -1,18 +1,5 @@
 ## Meal Entry
 
-### Loop 3 Updates:
-
-* [Time](#time): Loop 3 adds the +/- 15 minute buttons to adjust time for entry
-* [Food Type](#food-type): emoji keyboard
-    * Loop 3 initially displays Medium emojis and the association of some emojis with absorption time has been improved
-* [Absorption Time](#absorption-time): values for fast, medium and slow
-    * Loop 3 uses 30 minutes, 3 hr, 5 hr
-* [Meal Bolus](bolus.md#meal-bolus): Loop 3 fills in the Bolus row with Recommended Bolus
-* [Large Meal Warning](#large-meal-warning)
-    * The warning limit of 99 g was chosen to assist in catching mistakes such as entering 115 grams instead of 15 grams
-* [Override Active Warning](#override-active-warning)
-    * A warning is presented when entering carbs while an override with sensitivity other than 100% is active
-
 ### New with Version 3.4.x
 
 The [Favorite Foods](../../loop-3/features.md#favorite-foods){: target="_blank" } feature was added with version 3.4.x. This is an even faster way to enter meals than is described in the next section, Meal Entry - Fast Version.
@@ -60,9 +47,9 @@ Tap the meal entry icon on the toolbar to open the **Add Carb Entry** screen:
 
 1. Enter number of grams of carbs in the Amount Consumed row (keyboard appears automatically)
 1. Tap continue to advance to the **Meal Bolus** screen (as shown in the graphic below)
-1. Tap Save and Deliver to Save the carbs and Deliver the recommended bolus
+1. Tap Save Carbs & Deliver to Save the carbs and Deliver the recommended bolus
 
-The carbs are not saved until the [**Meal Bolus**](bolus.md#meal-bolus) screen is completed.
+The carbs are saved as soon as the [**Meal Bolus**](bolus.md#meal-bolus) screen is completed.
 
 * If no bolus is recommended in the **Meal Bolus** screen:
     * A No Bolus Recommended warning appears with the reason why
@@ -73,7 +60,7 @@ The carbs are not saved until the [**Meal Bolus**](bolus.md#meal-bolus) screen i
 {align="center"}
 
 !!! warning "Carbs are Saved in Meal Bolus Screen"
-    Carbohydrates are saved when the `Save and Bolus` or `Save without Bolusing` button is tapped in the Meal Bolus Screen. Once that the button is tapped, carbohydrates are saved. That is true even if the bolus does not go through to the pump.
+    Carbohydrates are saved when the `Save Carbs & Deliver` or `Save without Bolusing` button is tapped in the Meal Bolus Screen. Once that the button is tapped, carbohydrates are saved. That is true even if the bolus does not go through to the pump.
 
     If you see a notification after saving a carbohydrate entry, check carbohydrates entries in the *Loop* app. Do **not** just add the entry again without checking.
 

docs/operation/features/carbs.md

@@ -12,55 +12,13 @@ Please read this entire page before using any version of *Loop* other than the r
 
 ## Updates in `dev`
 
-This section provides an overview of changes to `dev` compared to `Loop 3.4.4`. These will be included in the next release, planned as `Loop 3.6.0`. 
+This section provides an overview of changes to `dev` compared to `Loop 3.6.0`. 
 
-In the meantime, the version number remains `3.5.0` in the `dev` branch.
+There are no updates at this time, but that can change without warning. Be very cautious building `dev` branch.
 
-### Add Automatic Certificate Generation and Renewal
+## Updates from 3.4 to 3.6
 
-These changes in the build process only work when `dev` is your default branch. Once `Loop 3.6.0` is released, these changes will work with the `main` branch.
-
-Automatic certificate generation and renewal requires a `Variable` be added to your organization or your repository. Please see these instructions: [Add Variable](../browser/prepare-fork.md#add-variable){: target="_blank" }
-
-### Maintenance Updates
-
-These maintenance changes do not affect the functioning of the *Loop* app but do enable continued build with current iOS, Xcode and macOS versions, as well as continued operation of the GitHub Actions (Browser Build) capability.
-
-* LoopWorkspace PR 234: Modify GitHub action files to enable automatic renewal of certificates when they expire or are revoked (details were in the previous section)
-* LoopWorkspace PR 241, Loop PR 2303: Modify the way the Loop app is versioned - it is now updated in the LoopWorkspace repository instead of the Loop repository - this simplifies version releases
-* LoopWorkspace PR 243: Update GitHub action files to use fastlane 2.227.1 and Xcode 16.3
-
-### Feature Updates
-
-These are changes in reponse to feature requests (`Loop Issues`) that were implemented in the noted submodule. The LoopWorkspace respository was subsequently updated to include the feature.
-
-| Loop Issue | Submodule Updated | PR in Submodule | Request | Modification |
-|:--|:--|:--|:--|:--|
-| [2168](https://github.com/LoopKit/Loop/issues/2168){: target="_blank" } | Loop | [2300](https://github.com/LoopKit/Loop/pull/2300){: target="_blank" } | Request for message change helpful for little loopers with multiple caregivers; avoid double carbohydrate entry | Change button label to `Save Carbs & Deliver` |
-
-### Bug Fixes
-
-These are fixes in reponse to specific bug reports (`Loop Issues`) that were implemented in the noted submodule. The LoopWorkspace respository was subsequently updated to include the bug fix.
-
-| Loop Issue | Submodule Updated | PR in Submodule | Description |
-|:--|:--|:--|:--|
-| [2159](https://github.com/LoopKit/Loop/issues/2159){: target="_blank" } | Loop | [2163](https://github.com/LoopKit/Loop/pull/2163){: target="_blank" } | Glucose change graph 'predicted' effects are inconsistent at different times or between orientations |
-| [2196](https://github.com/LoopKit/Loop/issues/2196){: target="_blank" } | Loop | [2295](https://github.com/LoopKit/Loop/pull/2295){: target="_blank" } | Bolus progress can display a stale total delivery value (UI bug only) |
-| [2265](https://github.com/LoopKit/Loop/issues/2265){: target="_blank" } | G7SensorKit | [34](https://github.com/LoopKit/G7SensorKit/pull/34){: target="_blank" } | No G7 CGM Updates - Loop Failure |
-| [2291](https://github.com/LoopKit/Loop/issues/2291){: target="_blank" } | G7SensorKit | [35](https://github.com/LoopKit/G7SensorKit/pull/35){: target="_blank" } | Backfill from G7 Created Bad Data |
-
-### OmniBLE and OmniKit Updates
-
-Updates were made to the Omnipod pump submodules: OmniBLE and OmniKit. Unless otherwise noted, the following functional updates were made to both submodules with the PR numbers included in parentheses:
-
-* Miscellaneous Omnipod code improvements & cleanup (PR 135, 44)
-* Unacknowledged command handling fixes and PodCommsSession improvements (PR 136, 45)
-* DASH (OmniBLE only): Don't fail on ack comms error if validated response has been received (PR 137)
-* Eros (OmniKit only): return clock icon when isClockOffset is true (PR 46)
-* DASH (OmniBLE only): Use alternate type 7 getStatus call for standalone getStatus sessions (matches the Insulet PDM) (PR 138)
-* Improved unacknowledged command recovery (PR 139, 47)
-* Logic fix for 049 pod fault with concurrent temp basal commands; fixed Trio Issue (PR 140, 48)
-* Logic fix for pump manager returns bogus podSuspended; fixed Trio Issue (PR 141, 49)
+All updates are reported in [`Loop 3.6.0`](releases.md#loop-v360){: target="_blank" }
 
 ## Updates from 3.2 to 3.4
 

docs/operation/features/img/loop-3-meal-entry-easy.svg

@@ -25,20 +25,22 @@ Releases from `Loop 3.4.4` and older are reported at [*GitHub*&nbsp;_<span trans
 
 ### Loop v3.6.0
 
-*Loop* v3.6.0 was released on TBD April 2025.
+*Loop* v3.6.0 was released on 23 April 2025.
 
 * [Link to release notes for Loop 3.6.0](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.6.0){: target="_blank" }
 
 #### 3.6.0 Highlights
 
 * Add Automatic Certificate Generation and Renewal
 * Implement updates to minimize Dexcom G7 outages that were reported over the last few months, possibly related to iOS 18 changes
-* Modify the bolus after meals button to explicitly say `Save Carbs & Deliver`
-* Updates to Omnipod Eros and DASH repositories: some bug fixes, some improved responses
+* Modify the bolus after meals button to say `Save Carbs & Deliver`
+* Update Omnipod Eros and DASH repositories: some bug fixes, some improved responses
 * Fix a few bugs
     * Fixed: Stale value of the total bolus in the Bolus Progress Display in HUD - UI Bug only
     * Fixed: Glucose change graph 'predicted' effects are inconsistent at different times or between orientations
-    * Fixed: Dexcom G7 calibration flags were not decoded correctly and some backfill messages could be left over from a previous sensor and provide erroneous date data
+    * Fixed: Dexcom G7 calibration flags were not decoded correctly
+    * Fixed: Dexcom G7 rare but significant date offset for glucose data
+        * If the backfillFinished message was not detected and a stale backFill message was applied to a new sensor, the date for that glucose reading would be in error
     * Fixed: The Algorithm Experiments screen could show stale selections - UI Bug only
     * Not Fixed: The Basal Rate section of the Therapy Settings screen does not update until you exit the screen and then return (this will be addressed in a future update) - UI Bug only, and only seen on some phone hardware (like SE phones) with iOS 18