ha-mcp-dev 7.9.0.dev738__tar.gz → 7.9.0.dev739__tar.gz

{ha_mcp_dev-7.9.0.dev738/src/ha_mcp_dev.egg-info → ha_mcp_dev-7.9.0.dev739}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 7.9.0.dev738
+Version: 7.9.0.dev739
 Summary: Home Assistant MCP Server - Complete control of Home Assistant through MCP
 Author-email: Julien <github@qc-h.net>
 License: MIT

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "7.9.0.dev738"
+version = "7.9.0.dev739"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 requires-python = ">=3.13,<3.14"

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/src/ha_mcp/config.py

@@ -535,7 +535,7 @@ def validate_settings() -> tuple[bool, str | None]:
 RegistryFieldType = type[bool] | type[int] | type[float] | type[str]
 
 # Closed set of UI section names. The advanced renderer in
-# settings_ui.py picks a DOM container per section; a typo would render
+# settings_ui/__init__.py picks a DOM container per section; a typo would render
 # the row into nothing.
 AdvancedSection = Literal[
     "connection",

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/src/ha_mcp/policy/persistence.py

@@ -1,4 +1,4 @@
-"""Atomic load/save for tool_policy.json (mirrors tool_config.json pattern in settings_ui.py)."""
+"""Atomic load/save for tool_policy.json (mirrors tool_config.json pattern in settings_ui/__init__.py)."""
 
 import json
 import os

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/src/ha_mcp/read_only.py

@@ -138,7 +138,7 @@ def _custom_tool_write(args: dict[str, Any]) -> str | None:
 # cache is only listable here). Everything NOT in this table and not
 # ``readOnlyHint=True`` is hidden and blocked outright.
 #
-# ``MANDATORY_TOOLS`` (settings_ui.py) intentionally needs no special
+# ``MANDATORY_TOOLS`` (settings_ui/__init__.py) intentionally needs no special
 # case here: every mandatory tool is either ``readOnlyHint=True`` or
 # present in this table (``ha_manage_backup``). The e2e test
 # ``test_real_catalog_mandatory_tools_stay_available``

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/src/ha_mcp/settings_ui/__init__.py

@@ -83,12 +83,13 @@ _PROCESS_STARTED_AT: float = time.time()
 logger = logging.getLogger(__name__)
 
 # Tools that are always enabled regardless of saved config — the server
-# strips them out of any disable list before applying. Three of these
+# strips them out of any disable list before applying. Five of these
 # overlap with DEFAULT_PINNED_TOOLS in transforms/categorized_search.py
-# (ha_search, ha_get_overview, ha_report_issue); ha_get_state
-# is mandatory but not pinned-by-default because it is reachable via the
-# ha_call_read_tool proxy when tool search is on. Keep these lists in
-# sync where it matters and divergent where it matters — don't merge them.
+# (ha_search, ha_get_overview, ha_report_issue, ha_get_skill_guide,
+# ha_manage_backup); ha_get_state is mandatory but not pinned-by-default
+# because it is reachable via the ha_call_read_tool proxy when tool search
+# is on. Keep these lists in sync where it matters and divergent where it
+# matters — don't merge them.
 MANDATORY_TOOLS: set[str] = {
     "ha_search",
     "ha_get_overview",
@@ -633,7 +634,7 @@ def apply_tool_visibility(
 _SETTINGS_JS_PATH = Path(__file__).parent / "settings.js"
 try:
     _settings_js_template = _SETTINGS_JS_PATH.read_text(encoding="utf-8")
-except FileNotFoundError as exc:  # pragma: no cover - packaging guard
+except OSError as exc:  # pragma: no cover - packaging guard
     raise ImportError(
         f"settings.js missing at {_SETTINGS_JS_PATH}. It must ship in "
         "package-data (wheel), MANIFEST.in (sdist), and the PyInstaller datas "
@@ -641,9 +642,10 @@ except FileNotFoundError as exc:  # pragma: no cover - packaging guard
     ) from exc
 # str.replace() silently no-ops on an absent token, and a *renamed* sentinel
 # (e.g. PINNED_DEFAULTS) slips past both the "__HA_MCP_" not-in test and the
-# node --check parse guard -- `const DEFAULT_PINNED = PINNED_DEFAULTS;` is valid
-# JS (only a runtime ReferenceError), so a drifted settings.js would ship a
-# broken page green. Assert both sentinels are present before substituting.
+# esbuild/jsdom JS harness (tests/js/harness.mjs) -- `const DEFAULT_PINNED =
+# PINNED_DEFAULTS;` is valid JS (only a runtime ReferenceError), so a drifted
+# settings.js would ship a broken page green. Assert both sentinels are present
+# before substituting.
 for _sentinel in ("__HA_MCP_DEFAULT_PINNED__", "__HA_MCP_MANDATORY__"):
     if _sentinel not in _settings_js_template:
         raise ImportError(
@@ -664,11 +666,11 @@ _SETTINGS_JS = _settings_js_template.replace(
 # read, no token substitution -- and is injected inline between the same
 # <style>/</style> tags so the served page stays byte-identical. It carries
 # the same import-time packaging dependency as settings.js, so the same
-# FileNotFoundError -> ImportError packaging guard applies.
+# OSError -> ImportError packaging guard applies.
 _SETTINGS_CSS_PATH = Path(__file__).parent / "settings.css"
 try:
     _SETTINGS_CSS = _SETTINGS_CSS_PATH.read_text(encoding="utf-8")
-except FileNotFoundError as exc:  # pragma: no cover - packaging guard
+except OSError as exc:  # pragma: no cover - packaging guard
     raise ImportError(
         f"settings.css missing at {_SETTINGS_CSS_PATH}. It must ship in "
         "package-data (wheel), MANIFEST.in (sdist), and the PyInstaller datas "
@@ -683,21 +685,23 @@ except FileNotFoundError as exc:  # pragma: no cover - packaging guard
 #   __HA_MCP_JS__          -> settings.js contents (inside <script>)
 #   __HA_MCP_THEME_PREFS__ -> per-request server-seeded theme prefs JSON,
 #                             substituted in _render_settings_html()
-# Same import-time packaging dependency as settings.js/css (wheel package-data
-# + MANIFEST.in); see _SETTINGS_JS_PATH above.
+# Same import-time packaging dependency as settings.js/css (wheel package-data,
+# MANIFEST.in, PyInstaller datas) and the same OSError guard -- but this loader
+# raises RuntimeError, not the ImportError that settings.js/css raise.
 _SETTINGS_HTML_PATH = Path(__file__).parent / "settings.html"
 try:
     _settings_html_template = _SETTINGS_HTML_PATH.read_text(encoding="utf-8")
 except OSError as exc:  # pragma: no cover - packaging guard
     raise RuntimeError(
         f"settings.html missing at {_SETTINGS_HTML_PATH}. It must ship in "
-        "the wheel (pyproject [tool.setuptools.package-data]) and the sdist "
-        "(MANIFEST.in)."
+        "package-data (wheel), MANIFEST.in (sdist), and the PyInstaller datas "
+        "(binary) -- this is a packaging bug, not a usage error."
     ) from exc
 
 # Fail fast if a marker was renamed in settings.html but not here (or vice
 # versa) — str.replace() silently no-ops on an absent token, which would ship a
-# page missing its CSS or JS. Assert all three markers are present.
+# page missing its CSS, JS, or server-seeded theme prefs. Assert all three
+# markers are present.
 for _sentinel in ("__HA_MCP_CSS__", "__HA_MCP_JS__", "__HA_MCP_THEME_PREFS__"):
     if _sentinel not in _settings_html_template:
         raise RuntimeError(
@@ -771,10 +775,10 @@ def _build_stub_policy_handlers(*, data_dir: Path) -> dict[str, Any]:
             {
                 "error": (
                     "Tool security policies live approvals are not active. "
-                    "Either the feature is turned off in addon config, the "
+                    "Either the feature is turned off in App (add-on) config, the "
                     "settings UI is running in stdio-sidecar mode, or the "
                     "policy package failed to import at startup. Check the "
-                    "addon log for ImportError / RuntimeError details if you "
+                    "App (add-on) log for ImportError / RuntimeError details if you "
                     "expected gating to be on."
                 )
             },
@@ -1388,7 +1392,7 @@ def build_settings_handlers(
                     "Unset DISABLED_TOOLS / PINNED_TOOLS first.",
                     suggestions=[
                         "Unset the DISABLED_TOOLS / PINNED_TOOLS environment "
-                        "variables (or remove them from your addon/Docker "
+                        "variables (or remove them from your App (add-on)/Docker "
                         "config), then restart to edit these tools from the UI.",
                     ],
                     context={"rejected": rejected},
@@ -1451,7 +1455,7 @@ def build_settings_handlers(
             return JSONResponse(
                 create_error_response(
                     ErrorCode.CONFIG_VALIDATION_FAILED,
-                    "Restart only available when running as an add-on",
+                    "Restart only available when running as an App (add-on)",
                     details="SUPERVISOR_TOKEN environment variable is not set",
                 ),
                 status_code=400,
@@ -1583,6 +1587,42 @@ def build_settings_handlers(
             }
         )
 
+    async def _live_addon_options() -> dict[str, Any]:
+        """Best-effort fetch of the add-on's current ``/data/options.json``.
+
+        Read-consistency with the add-on Configuration tab: the GET handlers
+        below otherwise display boot-time env values, so a user who edits the
+        add-on config (or saves from this web UI) WITHOUT restarting would see
+        stale values. For add-on-synced / schema-backed fields the live value
+        lives in Supervisor's options, so surface that — the latest SAVED
+        value, which is what becomes active after restart (the existing
+        "Restart required after save" banner conveys apply-on-restart).
+
+        Returns an empty dict outside add-on mode, without a live server, or
+        on any fetch failure, so callers fall back to the boot-env value and
+        the page never crashes or blanks a field.
+        """
+        if not is_running_in_addon() or server is None:
+            return {}
+        try:
+            options, err = await _supervisor_fetch_current_options(
+                server.settings.verify_ssl
+            )
+        except Exception as exc:  # pragma: no cover - defensive belt-and-braces
+            logger.debug(
+                "Live add-on options fetch raised %s — using boot-env values",
+                exc,
+            )
+            return {}
+        if err is not None:
+            logger.debug(
+                "Live add-on options fetch failed (%s): %s — using boot-env values",
+                err.kind,
+                err.message,
+            )
+            return {}
+        return options
+
     async def _get_feature_flags(_: Request) -> JSONResponse:
         """Return live feature-flag values + per-field origin + editable flag.
 
@@ -1613,10 +1653,23 @@ def build_settings_handlers(
         )
 
         settings = get_global_settings()
+        # Read-consistency with the add-on Configuration tab: a flag the user
+        # saved in the Config tab is already in Supervisor's live options, but
+        # the boot-env value goes stale until a restart. Surface the latest
+        # SAVED value for any flag present in live_options (see
+        # _live_addon_options) — not just origin=="addon" rows. On a dev add-on
+        # a flag saved before restart has origin "default"/"file" (its env var
+        # wasn't written at this boot), yet the fresh value is the one to show.
+        # Only origin=="env" stays pinned (an explicit env var the user must
+        # unset to change), and live_options is {} outside add-on mode so this
+        # is a no-op standalone.
+        live_options = await _live_addon_options()
         flags: dict[str, Any] = {}
         for field_name, env_name, ftype in FEATURE_FLAG_FIELDS:
             origin = get_feature_flag_origin(env_name)
             value = getattr(settings, field_name)
+            if field_name in live_options and origin != "env":
+                value = live_options[field_name]
             entry: dict[str, Any] = {
                 "value": value,
                 "origin": origin,
@@ -1796,7 +1849,7 @@ def build_settings_handlers(
                         (
                             f"{field_name!r} is locked by {origin}. "
                             f"Adjust the {env_name} env var "
-                            "(or addon configuration) instead."
+                            "(or App (add-on) configuration) instead."
                         ),
                     ),
                     status_code=400,
@@ -1917,7 +1970,7 @@ def build_settings_handlers(
                             "Supervisor helper returned ok=False with no error",
                             suggestions=[
                                 "Check the Home Assistant Supervisor logs and "
-                                + "the add-on logs for the underlying failure.",
+                                + "the App (add-on) logs for the underlying failure.",
                                 "Report this at "
                                 + "https://github.com/homeassistant-ai/ha-mcp/issues "
                                 + "if it persists. This indicates an internal bug.",
@@ -2286,6 +2339,11 @@ def build_settings_handlers(
         # called per field, and re-reading the file 17+ times would
         # produce duplicate WARNINGs on a corrupt file (one per field).
         overrides = _read_feature_flag_override_file()
+        # Read-consistency with the add-on Configuration tab: addon-synced
+        # fields (origin "addon") live in /data/options.json, so the boot-env
+        # value goes stale after a config edit without a restart. Surface the
+        # latest SAVED options value for those (see _live_addon_options).
+        live_options = await _live_addon_options()
         fields: list[dict[str, Any]] = []
         for (
             fname,
@@ -2296,6 +2354,8 @@ def build_settings_handlers(
         ) in ADVANCED_SETTINGS_FIELDS:
             origin = _origin_for_advanced_field(env_name, overrides=overrides)
             value: Any = getattr(settings, fname, None)
+            if origin == "addon" and fname in live_options:
+                value = live_options[fname]
             # Mask the token: never echo the actual long-lived access
             # token to the UI. The OAuth-mode sentinel survives so
             # operators can tell connection mode at a glance.
@@ -2456,7 +2516,7 @@ def build_settings_handlers(
                     create_error_response(
                         ErrorCode.VALIDATION_INVALID_PARAMETER,
                         f"{fname!r} is display-only. Modify via env var "
-                        "or addon configuration.",
+                        "or App (add-on) configuration.",
                     ),
                     status_code=409,
                 )
@@ -2475,11 +2535,11 @@ def build_settings_handlers(
                 # add-on-aware copy instead of implying a lever exists.
                 if addon_mode:
                     message = (
-                        f"{fname!r} is fixed by the add-on runtime and "
+                        f"{fname!r} is fixed by the App (add-on) runtime and "
                         "cannot be changed from the web UI."
                     )
                     suggestions = [
-                        "This value is baked into the add-on and is not "
+                        "This value is baked into the App (add-on) and is not "
                         "exposed as an editable setting.",
                     ]
                 else:
@@ -2640,7 +2700,7 @@ def build_settings_handlers(
                             "Supervisor helper returned ok=False with no error",
                             suggestions=[
                                 "Check the Home Assistant Supervisor logs and "
-                                + "the add-on logs for the underlying failure.",
+                                + "the App (add-on) logs for the underlying failure.",
                                 "Report this at "
                                 + "https://github.com/homeassistant-ai/ha-mcp/issues "
                                 + "if it persists. This indicates an internal bug.",

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/src/ha_mcp/settings_ui/settings.css

@@ -42,6 +42,7 @@
     /* App toolbar */
     --header-bg: #455a64;
     --header-text: #ffffff;
+    --header-shadow: 0 2px 4px rgba(0, 0, 0, 0.4);
 
     /* Cards */
     --card-shadow: none;
@@ -88,7 +89,7 @@
     position: sticky;
     top: 0;
     z-index: 10;
-    box-shadow: 0 2px 4px rgba(0, 0, 0, 0.4);
+    box-shadow: var(--header-shadow);
     flex-shrink: 0;
   }
   .header-inner { display: flex; align-items: center; gap: 12px; }
@@ -148,11 +149,12 @@
   }
   @media (prefers-reduced-motion: reduce) {
     .ha-toast, .ha-toast.leaving { animation: none; }
+    *, *::before, *::after { transition-duration: 0.01ms !important; }
   }
 
   /* ── MAIN CONTENT AREA ───────────────────────────────────────────────── */
   main {
-    max-width: 840px;
+    max-width: 1280px;
     margin: 0 auto;
     padding: 0 16px 32px;
   }
@@ -168,7 +170,7 @@
 
   /* ── VERSION FOOTER ──────────────────────────────────────────────────── */
   .version-footer {
-    margin-top: 32px; padding: 12px 0; font-size: 0.75rem;
+    max-width: 1280px; margin: 32px auto 0; padding: 12px 0; font-size: 0.75rem;
     color: var(--text-secondary); text-align: center;
     border-top: 1px solid var(--border); opacity: 0.7;
   }
@@ -359,6 +361,7 @@
   .badge.write     { background: var(--badge-write-bg);        color: var(--badge-write-text); }
   .badge.destructive { background: var(--badge-destructive-bg); color: var(--badge-destructive-text); }
   .badge.mandatory { background: var(--badge-mandatory-bg);    color: var(--badge-mandatory-text); }
+  .badge.unknown   { background: var(--surface-hover);         color: var(--text-secondary); }
 
   /* ── TOGGLE GROUPS & SWITCH ──────────────────────────────────────────── */
   .tool-toggles { display: flex; gap: 16px; align-items: center; }
@@ -758,18 +761,32 @@
 
   /* ── THEME CONTROL (in header) ───────────────────────────────────────── */
   .theme-control { display: inline-flex; align-items: center; gap: 6px; }
-  .theme-control-label { font-size: 0.75rem; color: rgba(255, 255, 255, 0.6); }
+  .theme-control-label { font-size: 0.75rem; color: var(--header-text); opacity: 0.7; }
   .theme-toggle {
-    background: rgba(255, 255, 255, 0.12); color: #fff;
-    border: 1px solid rgba(255, 255, 255, 0.2); border-radius: 4px;
-    padding: 4px 8px; font-size: 0.8rem; font-family: inherit; cursor: pointer; outline: none;
-  }
-  .theme-toggle:focus { border-color: rgba(255, 255, 255, 0.6); }
+    background: color-mix(in srgb, var(--header-text) 12%, transparent);
+    color: var(--header-text);
+    border: 1px solid color-mix(in srgb, var(--header-text) 25%, transparent);
+    border-radius: 4px;
+    padding: 4px 8px; font-size: 0.8rem; font-family: inherit; cursor: pointer;
+  }
+  /* The closed control sits on the header and uses the header text colour, so
+     it stays legible whether the header is dark (dark theme) or light (light
+     theme). The native <option> popup follows the page color-scheme, not the
+     header, so pin it to the surface palette; that keeps the options legible
+     in every theme regardless of the header text colour. */
+  .theme-toggle option { background: var(--surface); color: var(--text); }
+  .theme-toggle:focus-visible { outline: 2px solid var(--accent); outline-offset: 2px; }
 
   /* ── LIGHT THEME ─────────────────────────────────────────────────────── */
   :root[data-theme="light"] {
     color-scheme: light;
     --bg: #fafafa;
+    /* Light header to match the original UI — the #1695 redesign left the
+       header dark (#455a64) in both themes, which looked out of place in
+       light mode. A white header + hairline divider matches the page. */
+    --header-bg: #ffffff;
+    --header-text: #212121;
+    --header-shadow: 0 1px 0 var(--border);
     --surface: #ffffff;
     --surface-hover: #f5f5f5;
     --text: #212121;

{ha_mcp_dev-7.9.0.dev738 → ha_mcp_dev-7.9.0.dev739}/src/ha_mcp/settings_ui/settings.html

@@ -8,9 +8,10 @@
      /favicon.ico (which would 404 and log a console error, since the
      settings server serves no such asset in any deployment mode). -->
 <link rel="icon" href="data:,">
-<link rel="preconnect" href="https://fonts.googleapis.com">
-<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
-<link href="https://fonts.googleapis.com/css2?family=Roboto:wght@400;500;700&family=Roboto+Mono&display=swap" rel="stylesheet">
+<!-- Fonts are intentionally NOT loaded from a CDN: ha-mcp must stay self-contained
+     and work offline / air-gapped (no phoning out to Google on every load). The
+     font-family stack in settings.css falls back to Roboto-if-installed then the
+     system sans-serif. -->
 <script data-purpose="server-prefs" data-prefs="__HA_MCP_THEME_PREFS__">
   // #1574 review: theme/accessibility prefs also persist server-side
   // (theme_prefs.json) because stdio respawns its settings sidecar on a
@@ -161,44 +162,45 @@
 </div>
 <div class="restart-notice" id="restartNotice">
   <span class="restart-notice-text" id="restartNoticeText">
-    ⚠ Changes saved. Restart ha-mcp for them to take effect. On next
-    startup, ha-mcp fully removes disabled tools from the MCP tool list.
+    ⚠ Changes saved. Restart HA-MCP for them to take effect. On next
+    startup, HA-MCP fully removes disabled tools from the MCP tool list.
     Then reconnect or refresh the MCP server in your AI client (e.g.
-    re-add/refresh the connector in ChatGPT, or close and reopen Claude
-    Desktop) so it reloads the tool list. Restarting the add-on or Home
-    Assistant does NOT refresh your client's cached tool list.
+    refresh tool list on claude.ai, re-add/refresh the connector in
+    ChatGPT, or close and reopen Claude Desktop) so it reloads the tool
+    list. Restarting the App (add-on) or Home Assistant does NOT refresh your
+    client's cached tool list.
   </span>
-  <button class="restart-btn" id="restartBtn" style="display:none">Restart Add-on</button>
+  <button class="restart-btn" id="restartBtn" style="display:none">Restart App (add-on)</button>
 </div>
 <div class="panel active" id="panel-tools" role="tabpanel" aria-labelledby="tab-tools" tabindex="0">
   <div class="readonly-notice">
     Server-wide features (Tool Search, YAML config editing, filesystem
     tools, etc.) appear in both the <strong>Server Settings</strong>
-    tab and the add-on Configuration page; they're the same settings
+    tab and the App (add-on) Configuration page; they're the same settings
     either way. Either surface stays in sync with the other after the
-    addon restart. Changes require an MCP-host restart to apply.
+    App (add-on) restarts. Changes require HA-MCP to be restarted.
   </div>
   <div class="pin-notice show" id="pinNotice">
     Tools listed in the <code>DISABLED_TOOLS</code> or <code>PINNED_TOOLS</code>
     env vars are locked read-only; unset the env var to edit them here.
     Pin toggles only take effect when Tool Search is enabled (Server Settings tab
-    or add-on Configuration page).
+    or App (add-on) Configuration page).
   </div>
   <div class="summary" id="summary"></div>
   <div class="feature-row" id="readOnlyModeRow">
     <div class="feature-info">
-      <div class="feature-name">Read Only Mode</div>
+      <div class="feature-name" id="read-only-mode-label">Read Only Mode</div>
       <div class="feature-help">
         Turns off all write tools and blocks every tool from making
         write or destructive calls. Mixed read/write tools
-        (backups, add-ons, energy preferences, voice pipelines, and code
+        (backups, Apps (add-ons), energy preferences, voice pipelines, and code
         mode when enabled) stay available with their write operations
         blocked.
       </div>
     </div>
     <div class="feature-control">
       <label class="switch">
-        <input type="checkbox" id="read-only-mode-toggle">
+        <input type="checkbox" id="read-only-mode-toggle" aria-labelledby="read-only-mode-label">
         <span class="slider"></span>
       </label>
     </div>
@@ -207,7 +209,7 @@
     Could not read server settings. Read Only Mode status unknown; this
     view may not reflect what the server enforces.
   </div>
-  <input type="search" class="search" id="search" placeholder="Search tools..."
+  <input type="search" class="search" id="search" placeholder="Search tools..." aria-label="Search tools"
          autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false">
   <div id="groups"></div>
 </div>
@@ -218,10 +220,10 @@
     </svg>
     <div class="ha-alert-body">
       Settings on this tab save automatically. Changes take effect only after
-      you restart the add-on (applies them server-side) and reconnect or
+      you restart the App (add-on) (applies them server-side) and reconnect or
       refresh the MCP server in your AI client (reloads the tool list), e.g.
-      re-add or refresh the connector in ChatGPT, or close and reopen Claude
-      Desktop.
+      refresh tool list on claude.ai, re-add or refresh the connector in
+      ChatGPT, or close and reopen Claude Desktop.
     </div>
   </div>
 
@@ -273,8 +275,8 @@
     </div>
   </div>
   <div class="backup-filters">
-    <input type="text" id="backupDomain" placeholder="Domain (e.g. automation)">
-    <input type="text" id="backupEntity" placeholder="Entity ID">
+    <input type="text" id="backupDomain" placeholder="Domain (e.g. automation)" aria-label="Filter backups by domain">
+    <input type="text" id="backupEntity" placeholder="Entity ID" aria-label="Filter backups by entity ID">
     <button id="backupRefresh">Refresh</button>
     <button id="backupBulkDelete" class="danger">Bulk delete matching…</button>
   </div>
@@ -293,17 +295,17 @@
     <h3 style="font-size:1rem;margin-bottom:8px">Global settings</h3>
     <div class="feature-row">
       <div class="feature-info">
-        <div class="feature-name">Enable Tool Security Policies</div>
+        <div class="feature-name" id="policy-master-label">Enable Tool Security Policies</div>
         <div class="feature-help">
           Master switch. Mirrors the toggle in Server Settings. Off by
-          default. Toggle on and restart the addon to activate the
+          default. Toggle on and restart the App (add-on) to activate the
           gating middleware. While off, the rules below persist but
           aren't enforced.
         </div>
       </div>
       <div class="feature-control">
         <label class="switch">
-          <input type="checkbox" id="policy-master-toggle">
+          <input type="checkbox" id="policy-master-toggle" aria-labelledby="policy-master-label">
           <span class="slider"></span>
         </label>
       </div>
@@ -314,7 +316,7 @@
         <div class="feature-help">How long the middleware waits for an approval before timing out.</div>
       </div>
       <div class="feature-control">
-        <input type="number" id="policy-wait-seconds" min="5" max="600">
+        <input type="number" id="policy-wait-seconds" min="5" max="600" aria-label="Wait seconds (5-600)">
       </div>
     </div>
     <div class="feature-row">
@@ -323,7 +325,7 @@
         <div class="feature-help">How long a pending approval stays in the queue before expiring.</div>
       </div>
       <div class="feature-control">
-        <input type="number" id="policy-ttl-minutes" min="1" max="60">
+        <input type="number" id="policy-ttl-minutes" min="1" max="60" aria-label="Approval TTL minutes (1-60)">
       </div>
     </div>
     <div style="margin-top:10px; display:flex; align-items:center; gap:12px">
@@ -403,14 +405,18 @@
 </div>
 </main>
 <div class="modal-backdrop" id="modalBackdrop">
-  <div class="modal">
+  <div class="modal" role="dialog" aria-modal="true" aria-labelledby="modalTitle" tabindex="-1">
     <div class="modal-header">
       <span class="modal-title" id="modalTitle"></span>
-      <button class="modal-close" id="modalClose">×</button>
+      <button class="modal-close" id="modalClose" aria-label="Close">×</button>
     </div>
     <div class="modal-body" id="modalBody"></div>
   </div>
 </div>
+<!-- Static toast container: present in the DOM at load so the toast (which is
+     itself the ARIA live region) is appended into a stable parent instead of
+     being created from scratch on the first toast. -->
+<div id="ha-toast-region"></div>
 <script>__HA_MCP_JS__</script>
 <footer id="versionFooter" class="version-footer">
   <span id="versionFooterText"></span>