[ps2]

Shows and records what Guard + Runway did on each run. It uses AlgorithmOutput.guardAndRunway from LoopKit/LoopAlgorithm#12 (merged); LoopKit/LoopAlgorithm#13 makes its bandDepth the actual lowering.

Predicted Glucose screen (only with Guard + Runway on)

• A new Guard + Runway row shows "Forecast lowered up to X (recent volatility Y)", or "Forecast not lowered while carbs are active". It also shows "Automatic dosing target lowered Z", or "not lowered".
• Checking or unchecking the row draws the comparison curve with or without the guard. Until now, with everything checked, the comparison curve could differ from the forecast with no explanation, because the forecast includes the guard and the comparison curve didn't.
• The Retrospective Correction row notes when the post-low rise cut is active.

Dosing decisions
The guardAndRunway entry in each decision's algorithmExperiments now records volatility, bandApplied, bandGain, bandDepth, runwayShift and postLowRiseCutActive alongside volatilityBaseline. That entry is already stored and uploaded to Nightscout and Tidepool, so the new values go there with no service changes. The decision recorded after a bolus is entered still has only the baseline.

Tested

• LoopTests pass (344).
• Checked in the simulator with the mock CGM and pump: the row shows the values, and unchecking it draws the comparison curve without the guard.
• The runway and rise-cut text were not seen in the simulator, because that needs a calm high or a recent low. The values behind them are covered by LoopAlgorithm's tests.