TARIFF-24 / SAFETY-125 forward-port: record text (review F2, F3, CHANGELOG nit)

- TARIFF-24 DECISIONS: the hold keeps a Cheap hours charge; a Leftover solar
  battery still stops without a forecast (it has no planned level, still true
  after OPT-28: `dayplan.plan()` returns None and `charge_to()` gives None).
  Adds "a run that has started runs to its end" for a give run begun in a hold.
- CHANGELOG 0.19.2: "when the period is over" -> "when the period would go
  over the limit".

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

goodwe_controller/CHANGELOG.md

@@ -7,7 +7,7 @@ No option was added, removed or renamed, and no default changed (86 options).
 **Existing installs need no option change:** options that start 0.19.1 also
 start 0.19.2. The change below applies with one inverter or two.
 
-**Charging from the grid now stays under this month's peak.** A late meter reading near a period's end could push a grid charge to full power. That could take the 15-minute period over the peak. Now the charge is cut back, with one inverter too. The peak guard line no longer says "under" when the period is over.
+**Charging from the grid now stays under this month's peak.** A late meter reading near a period's end could push a grid charge to full power. That could take the 15-minute period over the peak. Now the charge is cut back, with one inverter too. The peak guard line no longer says "under" when the period would go over the limit.
 
 Contents of this release, in merge order since 0.19.1 (`2932f3a`):
 

goodwe_controller/DECISIONS/TARIFF-24-modes-need-the-tariff-task.md

@@ -57,7 +57,10 @@ is read at most every 60 s and the plan key already holds "forecast or not", so
 the gap follows in the cycle the read changes, both ways, with one exception:
 a run planned with a forecast that is under way keeps that gap to its end
 (`Controller.weather_held()`), so a sensor that goes unavailable does not stop
-or restart a charge. The wider gap applies from the next run.
+or restart a Cheap hours charge (a Leftover solar battery still stops: without
+a forecast it has no planned level). The wider gap applies from the next run.
+A run that has started runs to its end: a give run that starts during the hold
+is kept after it (`keep_started()`), with no grid charge or sale.
 
 **Not changed.** Modes off (the site trade) keeps the doubt always. The
 shipped cost 0.10 still needs a gap of 0.10 even with a forecast: a 0.08