UX-13 P4 review fixes (PR #146, comment 1887)

R1: first_start also needs a Store created at this boot (Store.fresh), so
    old never-started sites (both TEST-23 add-ons, one in shadow) stay on Home.
R2: a kettle skip after a fall says on the last step that the reading went down.
R3: the shadow switch goes only on the model the wizard posts, never into V.
R4: Home Assistant not answering is red on the last step.
R5: meter + solar + battery below -300 W flags a reversed battery sensor.
R6: the live checks say what to change and where.

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

goodwe_controller/app/uipage.py

@@ -291,19 +291,19 @@ SETUP_DONE = "setup_done"
 STARTED = "auto"
 
 
-def setup_needed(stored: dict, store_data, started) -> str | None:
+def setup_needed(stored: dict, store_data, started, fresh=False) -> str | None:
     """Why the page opens the wizard by itself, or None.
 
     "no_power_request": the stored options name no inverter to control, so
-    the add-on cannot start on them. "first_start": this /data has never been
-    through the wizard and control was never started or stopped, which is a
-    new install: config.yaml ships `auto_start` off, so it comes up stopped.
-    A site that runs, or ever ran, control is never sent to the wizard.
+    the add-on cannot start on them. "first_start": a new install. This boot
+    found no Store file (`fresh`), the wizard never saved and control was never
+    started or stopped. `fresh` is what tells a new install from an old site
+    that was never started, e.g. one left in shadow for weeks (TEST-23).
     `store_data` is the Store's dict (None: unknown, so no), `started` is
     whether control is started now."""
     if not power_request_entities(stored or {}):
         return "no_power_request"
-    if store_data is None:
+    if store_data is None or not fresh:
         return None
     if store_data.get(SETUP_DONE) or STARTED in store_data or started:
         return None