UX-08 2d review: action log reachable in status JSON, engaged peak row pinned, imported keys expanded

- status_payload() also returns the action log as `events`. The page
  does not render it. Some entries (a dropped inverter's reason, the peak
  guard's projection, unplaced watts) are written nowhere else, and DOCS
  still points installers at the action log.
- test_peakguard pins the engaged row's ordered pair (the battery's share,
  then the limit).
- test_messages expands setting keys named by constants imported from
  another app module, so the shown-text 30-word scan counts them.
- p1.py: 'A meter message could not be read'. DOCS glossary: control
  board in plain words, with the hardware in an installer note.

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

goodwe_controller/DOCS.md

@@ -9,10 +9,10 @@ v0.1.0 and outdated; where it disagrees with this page, this page wins.
 
 ## Words used on this page
 
-- **Control board**: the small computer wired to the inverter's RS485 meter
-  bus (a T-CAN485 board with an ESP32 chip). It passes the add-on's power
-  request to the inverter. If the add-on goes quiet for about 30 seconds, it
-  sets the inverter to 0 W by itself.
+- **Control board**: the small computer on the inverter's meter cable. It
+  passes the add-on's power request to the inverter. If the add-on goes quiet
+  for about 30 seconds, it sets the inverter to 0 W by itself. (For
+  installers: a T-CAN485 board with an ESP32 chip on the RS485 bus.)
 - **Isolator**: the switch that cuts an inverter off from the mains. Switching
   it off stops the inverter, whatever the add-on or the control board asks.
 - **Developer Tools**: the Home Assistant page that lists every entity and its
@@ -3183,7 +3183,10 @@ buttons reach the inverter.
 
 *For installers: the Configuration page is UX-02. The line under the buttons is
 `messages.hint()`, the plain form of the newest entry of the add-on's own
-action log (`Controller.events`), which the page no longer shows.*
+action log (`Controller.events`). The page no longer shows that log, but the
+`status` JSON still carries its last 40 entries as `events`: open the add-on
+page and add `status` to its address. The action-log tables in this document
+refer to it.*
 
 ## Status page