UX-13 P3 review: truthful peak lines, a clock-proof test, Simple stays default

- The peak limit's Why and plan block need a real power request (floor above
  0 W), not a blind or floor-limited guard. An Off battery gets the peak
  block only while it gives power. Why no longer says every battery gives.
- test_batteries_screen pins the fixture clock: unpinned it failed every
  morning. New checks cover the trade and cycle filters, the blind guard and
  an Off battery that A covers alone.
- Settings keeps only a picked view; a link to Installer is not remembered.
- Browser check: badges, unsaved change across views, locked value.

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

goodwe_controller/DECISIONS/UX-13-one-layout-table.md

@@ -93,8 +93,8 @@ What UX-02 made authoritative stays authoritative:
   existing `/action` values, not options, so the table places no key for
   them. The Batteries screen's Now, Today and Why lines are built in
   `homeview.py` from what the add-on knows this cycle; the plan per mode is
-  OPT-11 P3/P4, so until then Today says "Not planned yet"
-  (`test_batteries_screen.py`).
+  OPT-11 P3/P4, so until then Today says "Not planned yet" when no block
+  is planned for the battery (`test_batteries_screen.py`).
 
 ## 4. What this costs