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/app/main.py

@@ -5260,6 +5260,11 @@ class Controller:
         return {
             "banner": banner, "level": level, "rows": rows, "checks": checks,
             "hint": self.hint,
+            # The action log itself, newest first. The page does not show it
+            # (UX-08 2d), but an installer can still read it in the `status`
+            # JSON, because several events (a dropped inverter's reason, the
+            # peak guard's projection) are written nowhere else.
+            "events": list(self.events),
         }
 
     async def handle_action(self, what: str):

goodwe_controller/app/p1.py

@@ -472,7 +472,7 @@ class P1Ingest:
         """
         self.parse_errors += 1
         self.last_error = str(err)
-        _LOG.warning("Meter reading refused: %s", err)
+        _LOG.warning("A meter message could not be read: %s", err)
 
     # -- what consumers read -------------------------------------------------
     def age_s(self) -> float | None: