UX-10 review: the line as logged gets the red-alarm shape, clamp lines at 30 words, plain HA 400

Part 6 checked the quoted reason alone, so title + reason + tails logged
as 4+ sentences. It now also checks the whole line (at most 3 sentences,
none over 30 words); 25 lines failed and are rewritten (one-sentence
wrappers, two-sentence circulation and peak reasons, STALE_READING's
fixed limits on a DEBUG line). The clamp lines for one inverter are
pinned at 30 words with OUTPUT_CLAMP and the numbers kept. Home
Assistant's bare '400: Bad Request' while it loads becomes one plain
line; still WARNING, throttled, a failed write.

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

goodwe_controller/DOCS.md

@@ -1848,8 +1848,8 @@ Both are watched. A guard that watched only the emitted value would be silent on
 every standard configuration.
 
 **The integrator bound is not a bug, and it is reported as what it is.** It
-reads *"the correction the add-on builds up reached its +5000 W limit. The
-command this cycle was +2000 W"*, titled *"Battery is not keeping up"*, logged
+reads *"the correction the add-on builds up reached its +5000 W limit,
+command now +2000 W"*, titled *"Battery is not keeping up"*, logged
 as a `WARNING`, with an amber (not red) status row and its own notification
 (`goodwe_integrator_bound`), so it never replaces a software-fault notice still
 on screen. Brief engagements after a large load or solar step are normal. If it