PRICE-02 round 3: say that hourly and static plans change too, test plans built off the hour, exact period end and the Home page path, production-shaped real-year replay

Docs and tests only; no change under goodwe_controller/app.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC

goodwe_controller/DECISIONS/PRICE-02-the-verdict-skips-ended-periods.md

@@ -15,8 +15,14 @@ ended (`end <= now`, the span `price._cover_table()` gives, as
 
 - Taken in the verdict, not when the plan is built: a plan built at 03:00 is
   still used at 03:20, and the Home chart keeps the day's earlier bars.
-- An hourly point that is still current stays in, so hourly feeds and the
-  static day/night plan give the same verdict as before.
+- An hourly point that is still current stays in. But an hourly or static plan
+  is rebuilt every 30 min counted from add-on start, so it is usually off the
+  hour and, until the next refresh, holds the hour that has just ended. That
+  hour is dropped too (round 3, owner-accepted 2026-10-22). On a day/night
+  tariff all day hours tie and the old verdict took the first, the ended one,
+  so it paused the trade every hour until the refresh: 91 on/off changes over
+  2 days with the refresh at :10, 4 now (4 before as well, with the refresh on
+  the hour). With the refresh on the hour nothing changes.
 - `now` is required: keyword-only, no default, like the other three arguments. A
   caller that could leave it out would get the elapsed periods back and the
   defect with them. A test that wants the whole series passes an instant before it.
@@ -26,8 +32,10 @@ ended (`end <= now`, the span `price._cover_table()` gives, as
   that say "cheapest hour" (AUDIT-01 T1-T5) are not touched here.
 - Not changed here: F2 (static profile sampled at HH:00) and F3 (carried value).
 
-Measured: with price off, and on a static tariff, every command over the
-modes-off replay is byte-identical. On the dynamic replay every command is
+Measured: with price off, every command over the modes-off replay is
+byte-identical. On a static tariff rebuilt on the hour it is too; rebuilt 20
+min off the hour the commands differ (digest 79f06d6381ff3358 on release/1.0,
+18de19d9fe919fe5 here), for the reason above. On the dynamic replay every command is
 the same too; only a sale's sentence quotes a smaller "above the cheapest"
 figure once the first cheap period is over. The identity pins in
 `test_modes_p3.py` and `test_price_run_fixes.py` hide just that figure and the
@@ -67,3 +75,13 @@ one. The replay in `test_arbitrage.py` (synthetic year, hourly) gives the same
 ledger on the old and the new code once its ties are broken (280 round trips,
 85 held, both): it printed one maximum twice per day, and the old fixture
 tested the first of them only because its plan began at midnight.
+
+## Battery throughput (round 3)
+
+On real 15-minute days the trade runs longer: about 1.5 to 2.5 times the
+minutes spent charging or discharging, with fewer on/off switches (for example
+78 -> 68, 92 -> 72). Through a modelled 10 kWh battery that is 27.5 -> 42.6 kWh
+over 16 days (2026-09-02 to 09-17, a decision every minute, refresh at :00 or
+:10, tomorrow's prices known always or from 13:00; reviewer's sim). Charge to
+discharge reversals are unchanged (10 -> 10, 13 -> 13). More cycling is the
+price of not pausing.