Adopted-entity curation: user-asserted metadata from a new Adopted tab

CHANGELOG.md

@@ -2,7 +2,12 @@
 
 All notable changes to this project will be documented in this file.
 
-## [2.1.1]
+## [2.1.1] - 8/2026
+
+### Added
+
+- **Adopted entities can now be curated from the dashboard's new Adopted tab** — set a device class, a statistics class and whether the entity stays under
+  Diagnostics, with the change applied on an automatic reload.
 
 ### Fixed
 
@@ -19,7 +24,7 @@ All notable changes to this project will be documented in this file.
   grid.
 - **EVSE Charge Current Limit** is the first control here that changes something on a SPAN Drive rather than on the panel.
 - **The battery says when things run out** — Time to Priority Shed and Backup Time Remaining, beside its own power and link state.
-- **Vendor extensions are adopted on a reload**, so a device type or reading nobody has modelled no longer waits for a release.
+- **Vendor extensions are adopted on a reload**, so a device type or reading nobody has modeled no longer waits for a release.
 - **Your passphrase is no longer stored and the panel's certificate is pinned before credentials cross the network**, with control lockable or admin-only.
 - **Nothing you have moves** — entity ids, unique ids and history survive the upgrade.
 
@@ -89,7 +94,7 @@ This release requires Home Assistant 2026.8 to avoid a deprecated API — the ol
   battery and the dominant power source, and keeping its entity id and its history.
 - **`Grid Islandable` keeps working across the upgrade** by reflecting whether a Microgrid Interconnect Device is present, so a panel without one reads `Off`
   rather than going unavailable.
-- **Battery model may read differently after upgrading**, now showing the human-readable designation rather than the SKU, normalised in the library on both
+- **Battery model may read differently after upgrading**, now showing the human-readable designation rather than the SKU, normalized in the library on both
   sides of the upgrade so it lands once at this release.
 - **Five panel sensors are switched off for new installations** (#234) because of three SPAN-documented defects predating firmware r202633: **Feedthrough
   Produced Energy**, **Feedthrough Consumed Energy**, **Feedthrough Power**, and the two **Downstream** current sensors.
@@ -247,9 +252,9 @@ This release requires Home Assistant 2026.8 to avoid a deprecated API — the ol
 ### Changed
 
 - **Simulation moved to dedicated add-on** — Panel cloning and simulation are no longer part of the integration's options flow. A new `export_circuit_manifest`
-  service provides panel parameters to the standalone [SPAN Panel Simulator](https://github.com/SpanPanel/simulator) add-on, which now supports upgrade
-  modelling (evaluate firmware or integration upgrades in a sandbox before applying them to your real panel) and panel clone (replicate your panel's circuit
-  layout for testing).
+  service provides panel parameters to the standalone [SPAN Panel Simulator](https://github.com/SpanPanel/simulator) add-on, which now supports upgrade modeling
+  (evaluate firmware or integration upgrades in a sandbox before applying them to your real panel) and panel clone (replicate your panel's circuit layout for
+  testing).
 
 ### Fixed
 

custom_components/span_panel/__init__.py

@@ -77,6 +77,7 @@
 )
 from .control_gate import ControlGate, ControlLock, ControlPolicy
 from .coordinator import SpanPanelCoordinator
+from .curation import async_forget_curation, async_load_curation
 from .current_monitor import CurrentMonitor
 from .extension import async_notice_declined_extensions
 from .frontend import (
@@ -677,6 +678,7 @@ def _on_fatal_transport_error(error: SpanPanelError) -> None:
             panel_device_id=await ensure_device_registered(
                 hass, entry, snapshot, smart_device_name
             ),
+            curation=await async_load_curation(hass, entry),
         )
 
         # Before the forward, because a sub-device's `via_device_id` has to name a
@@ -750,6 +752,11 @@ async def async_remove_entry(hass: HomeAssistant, entry: SpanPanelConfigEntry) -
     The announcement record goes with them, and for a sharper reason: it outliving
     the entry would mean re-adding the same panel announces none of the entities
     it recreates, because every one of them is already recorded as announced.
+
+    The curation overlay goes for the same reason. Its keys are wire addresses
+    rather than registry ids, so a store left behind is one the next entry for
+    the same panel would load and apply, re-asserting metadata the user is no
+    longer here to have asked for.
     """
     async_clear_schema_issues(hass, entry)
     # The CA family too, for the same reason — and the two persistent ones most
@@ -760,6 +767,7 @@ async def async_remove_entry(hass: HomeAssistant, entry: SpanPanelConfigEntry) -
     async_clear_rest_tls_untrusted(hass, entry)
     async_clear_leaf_name_mismatch(hass, entry)
     await async_forget_announcements(hass, entry)
+    await async_forget_curation(hass, entry)
     await async_forget(hass, entry)