chore: replace em-dash with hyphen across text files

Author: web-flow

README.md

@@ -36,7 +36,7 @@ A custom integration that finds and deletes **orphan entities** - entities left
 
 ## Web Panel
 
-After installation, the **Orphan Cleaner** icon appears in the HA sidebar. All settings are controlled directly from the panel — no configuration flow needed after the initial setup.
+After installation, the **Orphan Cleaner** icon appears in the HA sidebar. All settings are controlled directly from the panel - no configuration flow needed after the initial setup.
 
 ### Controls
 
@@ -50,7 +50,7 @@ After installation, the **Orphan Cleaner** icon appears in the HA sidebar. All s
 | **Dry run** | Simulate deletion without removing anything (see below) |
 | **Filter** | Filter visible results by entity_id or platform |
 | **Select all / Deselect** | Bulk checkbox controls |
-| **Column headers** | Click to sort by Entity ID, Platform, Detection or Age — click again to reverse |
+| **Column headers** | Click to sort by Entity ID, Platform, Detection or Age - click again to reverse |
 | **Platform badge** | Click on any platform badge to instantly select all entities of that platform |
 | **Detection filter** | Dropdown to show only dead entry, unavailable, timestamp or heuristic entities |
 | **Delete selected** | Delete selected entities with a confirmation dialog |
@@ -64,11 +64,11 @@ Type a platform name or glob pattern in the **Ignore** field in the control bar
 
 A collapsible section below the control bar. Entries here are saved to the integration's config entry options and automatically loaded on every scan and page load. Supports:
 
-- **Platform names** — `tuya`, `shelly`, `imou_life`
-- **Platform globs** — `imou_*`, `tuya_*`
-- **Entity ID globs** — `sensor.old_*`, `*_deprecated`, `sensor.*_temp`
+- **Platform names** - `tuya`, `shelly`, `imou_life`
+- **Platform globs** - `imou_*`, `tuya_*`
+- **Entity ID globs** - `sensor.old_*`, `*_deprecated`, `sensor.*_temp`
 
-Entries are saved automatically when added or removed — no Save button needed. Use the **?** link for a full syntax reference.
+Entries are saved automatically when added or removed - no Save button needed. Use the **?** link for a full syntax reference.
 
 ### Save & Delete
 
@@ -81,7 +81,7 @@ Enable the **Dry run** checkbox in the toolbar before deleting. When active:
 - An amber warning banner appears to remind you that no changes will be made
 - **Delete selected** becomes **Simulate**
 - **Save & Delete** is hidden
-- Clicking **Simulate** highlights the selected entities with a `would delete` badge for 6 seconds and logs the result — nothing is actually removed
+- Clicking **Simulate** highlights the selected entities with a `would delete` badge for 6 seconds and logs the result - nothing is actually removed
 
 Dry run is also available as a parameter in the `orphan_cleaner.delete_orphans` service (see Services section).
 
@@ -117,21 +117,21 @@ Click any platform badge in the results table to instantly select all entities o
 
 ## Detection Methods
 
-### Method 1 — `orphaned_timestamp` (reliable)
+### Method 1 - `orphaned_timestamp` (reliable)
 
 Home Assistant sets this field in the registry when, after a full restart, an entity is not claimed by any integration. This is the official signal and is always active.
 
 **Min age (h)** filters out recently orphaned entities, useful if an integration is temporarily offline. Ages above 24 hours are displayed in days (e.g. `377d`) in the panel table.
 
-### Method 2 — Dead config entry
+### Method 2 - Dead config entry
 
 If an entity's `config_entry_id` points to a config entry that no longer exists or is in a `FAILED` / `NOT_LOADED` state, the entity is considered an orphan.
 
-### Method 3 — Unavailable state
+### Method 3 - Unavailable state
 
 Entities in `unavailable` state for longer than **Min age (h)** are flagged. Catches entities that HA marks with the yellow warning "no longer provided by the integration".
 
-### Method 4 — Heuristic (optional)
+### Method 4 - Heuristic (optional)
 
 Enabled by the **Heuristic** checkbox. Also flags entities with no `config_entry_id` and a platform not in the following exclusion list:
 
@@ -250,14 +250,14 @@ If you used **Save & Delete**, a backup file was written to `/config/orphan_clea
 
 ### What you can do
 
-- **Check if the entity was truly orphaned** — look at the `method` and `age_hours` fields. If `age_hours` is low, the integration may have been temporarily offline and the entity could reappear after a restart.
-- **Reinstall the integration** — if the platform (e.g. `tuya`, `shelly`, `zha`) is still active and the physical device is reachable, removing and re-adding the integration will recreate its entities automatically.
-- **Restore custom attributes manually** — if the entity reappears, you can reassign its area, icon, and aliases from the HA UI. The backup gives you the original `entity_id` to match it.
-- **Clean up the recorder** — if the entity had historical data and you want to remove it, use the `recorder.purge_entities` service with the `entity_id` from the backup.
+- **Check if the entity was truly orphaned** - look at the `method` and `age_hours` fields. If `age_hours` is low, the integration may have been temporarily offline and the entity could reappear after a restart.
+- **Reinstall the integration** - if the platform (e.g. `tuya`, `shelly`, `zha`) is still active and the physical device is reachable, removing and re-adding the integration will recreate its entities automatically.
+- **Restore custom attributes manually** - if the entity reappears, you can reassign its area, icon, and aliases from the HA UI. The backup gives you the original `entity_id` to match it.
+- **Clean up the recorder** - if the entity had historical data and you want to remove it, use the `recorder.purge_entities` service with the `entity_id` from the backup.
 
 ### What cannot be recovered
 
-- The entity registry entry itself — HA does not expose an API to re-insert entries manually.
+- The entity registry entry itself - HA does not expose an API to re-insert entries manually.
 - Historical recorder data is not deleted by this integration, but it will no longer be linked to an active entity.
 - If the underlying integration or device no longer exists, the entity cannot be recreated without it.
 
@@ -274,7 +274,7 @@ All API endpoints require Home Assistant authentication. The panel itself requir
 - **Always make a backup** before deleting entities in bulk. Use **Save & Delete** to automatically export a JSON record before each deletion.
 - Deleted entities are removed from the **registry**: historical data in the **recorder** remains but is no longer associated with an active entity. To clean the recorder as well, use the `recorder.purge_entities` service.
 - An entity with `orphaned_timestamp` may belong to an integration that is temporarily offline. Increase **Min age (h)** if you have unstable integrations.
-- Deletion is **irreversible**. Entities cannot be restored from the backup — the backup is a reference record only.
+- Deletion is **irreversible**. Entities cannot be restored from the backup - the backup is a reference record only.
 
 ---
 

custom_components/orphan_cleaner/__init__.py

@@ -1,5 +1,5 @@
 """
-Orphan Entity Cleaner — Custom Integration for Home Assistant.
+Orphan Entity Cleaner - Custom Integration for Home Assistant.
 """
 from __future__ import annotations
 
@@ -48,7 +48,7 @@ async def async_setup_entry(hass: HomeAssistant, entry: ConfigEntry) -> bool:
     except Exception:
         pass
 
-    # Use iframe panel pointing directly to panel.html — no JS cache issues
+    # Use iframe panel pointing directly to panel.html - no JS cache issues
     frontend.async_register_built_in_panel(
         hass,
         component_name="iframe",

custom_components/orphan_cleaner/config_flow.py

@@ -6,7 +6,7 @@
 
 
 class OrphanCleanerConfigFlow(config_entries.ConfigFlow, domain=DOMAIN):
-    """Single-step config flow — no parameters needed."""
+    """Single-step config flow - no parameters needed."""
 
     VERSION = 1
 

custom_components/orphan_cleaner/frontend/orphan-cleaner-panel.js

@@ -1,4 +1,4 @@
-// Orphan Entity Cleaner — Custom Panel per Home Assistant
+// Orphan Entity Cleaner - Custom Panel per Home Assistant
 // Registrato come panel_custom: riceve `hass` con il token già autenticato.
 
 class OrphanCleanerPanel extends HTMLElement {
@@ -163,9 +163,9 @@ class OrphanCleanerPanel extends HTMLElement {
   _updateStats() {
     const s = this._state;
     const he = s.allOrphans.filter(o => o.method === "heuristic").length;
-    this._setText("s-total",  s.total != null ? s.total : "—");
-    this._setText("s-orphan", s.allOrphans.length || (s.total != null ? "0" : "—"));
-    this._setText("s-heur",   s.total != null ? he : "—");
+    this._setText("s-total",  s.total != null ? s.total : "-");
+    this._setText("s-orphan", s.allOrphans.length || (s.total != null ? "0" : "-"));
+    this._setText("s-heur",   s.total != null ? he : "-");
     this._setText("s-sel",    s.selected.size);
   }
   _setText(id, val) {
@@ -231,7 +231,7 @@ class OrphanCleanerPanel extends HTMLElement {
         ? `<span class="badge badge-unavail">unavailable</span>`
         : `<span class="badge badge-heuristic">heuristic</span>`;
       const dis   = e.disabled_by ? `<span class="badge badge-disabled">disabled</span>` : "";
-      const age   = e.age_hours != null ? `${e.age_hours}h` : "—";
+      const age   = e.age_hours != null ? `${e.age_hours}h` : "-";
       return `<tr>
         <td class="td-chk"><input type="checkbox" data-eid="${e.entity_id}" ${chk}></td>
         <td><span class="eid">${e.entity_id}</span>${dis}</td>
@@ -417,14 +417,14 @@ class OrphanCleanerPanel extends HTMLElement {
     <div class="topbar-title">Orphan Entity Cleaner</div>
   </div>
   <div class="topbar-spacer"></div>
-  <div class="cfg-pill" id="cfg-pill">—</div>
+  <div class="cfg-pill" id="cfg-pill">-</div>
 </div>
 
 <div class="main">
   <div class="stat-row">
-    <div class="stat">          <div class="s-label">Total entities</div>  <div class="s-val" id="s-total">—</div></div>
-    <div class="stat s-danger"> <div class="s-label">Orphans found</div> <div class="s-val" id="s-orphan">—</div></div>
-    <div class="stat s-warn">   <div class="s-label">Heuristic</div><div class="s-val" id="s-heur">—</div></div>
+    <div class="stat">          <div class="s-label">Total entities</div>  <div class="s-val" id="s-total">-</div></div>
+    <div class="stat s-danger"> <div class="s-label">Orphans found</div> <div class="s-val" id="s-orphan">-</div></div>
+    <div class="stat s-warn">   <div class="s-label">Heuristic</div><div class="s-val" id="s-heur">-</div></div>
     <div class="stat s-ok">     <div class="s-label">Selected</div>    <div class="s-val" id="s-sel">0</div></div>
   </div>
 
@@ -451,7 +451,7 @@ class OrphanCleanerPanel extends HTMLElement {
     <h3>Available services</h3>
     <div class="service-row">
       <span class="svc-name">orphan_cleaner.scan</span>
-      <span class="svc-desc">Scans the registry and fires the <code>orphan_cleaner_orphans_found</code> event — useful in automations.</span>
+      <span class="svc-desc">Scans the registry and fires the <code>orphan_cleaner_orphans_found</code> event - useful in automations.</span>
     </div>
     <div class="service-row">
       <span class="svc-name">orphan_cleaner.delete_orphans</span>