4 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude Opus 5.5	571b884315	UX-08 phase 2b review: keep over-rating evidence, pin latch clearing, plainer rows ... - During a bound episode an earlier over-rating count stays on the page (amber, under its own title); test_clamp pins it. - test_messages pins that every latch row says how it clears. - pv_entities description no longer claims the page names the entity (en, nl); allowlist hash updated for that option-desc line. - Plainer texts: multi-inverter direction banner, "fine now" after an episode, and the e-stop, peak-forecast and peak-guard-waiting rows move to messages.py. - TEL-12 DECISIONS points to UX-08 item 3 for the retired row rule. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-27 03:10:25 +02:00
adminandClaude Opus 5.5	d017fc67bf	UX-08 phase 2b: short, plain status rows and page banners ... Every Commissioning row and every page banner is now worded in app/messages.py (row_*, banner_*): one sentence of at most 15 words, a red row up to three sentences so a latch still says how it clears, banners at most 12 words. No row names a Home Assistant entity: sensors by their setting, solar sources by their place in the list. Reason codes and limits stay on the log line and event list; rows keep the numbers a reader acts on. UX-07 item 1: ClampWatchdog counts over-rating and integrator-bound engagements separately, and after an episode each count shows under its own alarm's title instead of both under "output clamp". No row colour, visibility or banner order changed. Rows carry an "id" so the tests pin meaning rather than wording. The row and banner kinds leave the allowlist (200 -> 168, cap equal). DOCS.md gains "Status page"; choices are in DECISIONS/UX-08-short-notifications.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LyR88rXETvwhTgx6yHE39p	2026-09-27 02:12:10 +02:00
adminandClaude Opus 5.5	7b65a3e69a	UX-08 review: tighter notification texts, and two meaning fixes ... - not delivering: the body said control keeps running and then "start control"; clearing it takes stop then start, and it now says so. - peak reserve: the "reserve not set" branch is really soc_floor None, i.e. an inverter's cut-out level missing; it now names that. The title is true on all three branches ("Battery stopped limiting the peak"). - no semicolon run-ons in bodies (STYLE.md + test); loop-bound, circulating, meter-frozen and multi-unit over-rating bodies rewritten to match. - allowlist cap is now exact, so a shrink cannot leave room to regrow. - DOCS names the settings behind "peak reserve" and "cut-out level"; DECISIONS no longer states the HA anchor behaviour as fact. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-27 01:18:55 +02:00
glenn schrooyenandClaude Opus 5.5	50ccea3dd7	UX-08 phase 2a: short, plain notifications, and a ratchet for the rest ... Every HA notification the add-on raises now has a title of at most 5 everyday words and a one-sentence body; a red alarm may use three so no action is lost. The texts live in app/messages.py, the rule in STYLE.md, and the detail that moved out in DOCS.md "Notifications", which each body links to. No notification_id, trigger or cadence changed. test_messages.py enforces the rule on every notification, fails any notification worded outside app/messages.py, and ratchets the kinds not yet rewritten (rows, banners, refusals, logs, options) through a shrinking allowlist of 200. Six tests re-pinned from prose to meaning. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LyR88rXETvwhTgx6yHE39p	2026-09-27 01:00:54 +02:00