UX-08 review: tighter notification texts, and two meaning fixes

- not delivering: the body said control keeps running and then "start
  control"; clearing it takes stop then start, and it now says so.
- peak reserve: the "reserve not set" branch is really soc_floor None,
  i.e. an inverter's cut-out level missing; it now names that. The title
  is true on all three branches ("Battery stopped limiting the peak").
- no semicolon run-ons in bodies (STYLE.md + test); loop-bound, circulating,
  meter-frozen and multi-unit over-rating bodies rewritten to match.
- allowlist cap is now exact, so a shrink cannot leave room to regrow.
- DOCS names the settings behind "peak reserve" and "cut-out level";
  DECISIONS no longer states the HA anchor behaviour as fact.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

goodwe_controller/test_peakguard.py

@@ -2528,7 +2528,7 @@ _body25 = hass25.last_message("goodwe_peak_soc_floor")
 def _says_scope(body):
     """SAFETY-25 in messages.peak_reserve()'s words: the reserve binds the peak
     guard only, and home use goes on discharging below it to the cut-out."""
-    return ("The reserve only limits peak shaving" in body
+    return ("The reserve only applies to keeping the peak down" in body
             and "normal home use can still discharge the battery below it" in body
             and "down to its cut-out level" in body)