ha-mcp-dev 8.2.0.dev2318__tar.gz → 8.2.0.dev2321__tar.gz

{ha_mcp_dev-8.2.0.dev2318/src/ha_mcp_dev.egg-info → ha_mcp_dev-8.2.0.dev2321}/PKG-INFO

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

{ha_mcp_dev-8.2.0.dev2318 → ha_mcp_dev-8.2.0.dev2321}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "8.2.0.dev2318"
+version = "8.2.0.dev2321"
 description = "Home Assistant MCP Server - Complete control of Home Assistant through MCP"
 readme = "README.md"
 # Upper bound widened to <3.15 so the package installs on Home Assistant's

{ha_mcp_dev-8.2.0.dev2318 → ha_mcp_dev-8.2.0.dev2321}/src/ha_mcp/settings_ui/locales/README.md

@@ -37,11 +37,16 @@ register the engine imitates, a component catalog left at a key or two rests
 entirely on whichever of them addresses the reader —
 `test_every_shipped_component_catalog_gets_reader_addressing_samples` pins that
 one. Leaving that catalog empty is fine, but the moment you author anything in
-it, at least one key must be one whose English addresses the reader in the
-second person, and it must carry a non-empty translation — a key left blank is
+it, at least two keys must be ones whose English addresses the reader in the
+second person, and each must carry a non-empty translation — a key left blank is
 skipped like a missing one rather than sampled empty. Most component strings do
 not address the reader, so starting at the top of the file leaves the catalog
-anchorless and that check red until you add one that does. To fill them in your own PR instead, run
+anchorless and that check red until you add ones that do. Two rather than one
+because the run likeliest to need the register is the one that rewords such a
+key: that queues it, and a queued key is dropped from the candidates, so a
+surface resting on a single anchor loses its register in exactly that run —
+`test_component_samples_survive_their_own_anchor_being_queued` pins the
+survival. To fill them in your own PR instead, run
 `scripts/translate_locales.py` yourself and review its output like any
 other diff. Also add the new code to the locale list in the repository-root
 `AGENTS.md`

{ha_mcp_dev-8.2.0.dev2318 → ha_mcp_dev-8.2.0.dev2321}/src/ha_mcp/settings_ui/locales/en.json

@@ -128,7 +128,7 @@
     "features.enable_strict_mandatory_bps.label": "Strict best-practices mode",
     "features.enable_strict_mandatory_bps.help": "Strict mode: prevents the client from using the tool until it can prove that it read the best practices. While on, the six best-practice write tools (automations, scripts, scenes, helpers, dashboards, raw YAML) are blocked and return an error directing the client to read the best-practices skill via ha_get_skill_guide and pass back the acknowledgment key it obtains there. While on, the ha_get_skill_guide tool is locked enabled — it is the only publisher of the acknowledgment key. Child of the \"Attach best-practice skills on writes\" option above and inert while that parent is off. Requires restart to take effect.",
     "features.enable_beta_features.label": "Enable beta features (master)",
-    "features.enable_beta_features.help": "⚠ DANGER — these tools can PERMANENTLY DAMAGE your Home Assistant installation. They write to your YAML config, your filesystem, install custom components, run arbitrary sandboxed Python, and edit tool docstrings the AI sees. There is no warranty and no support guarantee — you enable them at your OWN RISK. Take a Home Assistant backup before turning this on, and never enable in production without one. Master gate for the 5 experimental sub-flags below; sub-flags are ignored at runtime while this master is off, even when explicitly set to true. The same toggle is also surfaced in the web settings UI under \"Beta features (dangerous)\" — either surface reflects the other on restart.",
+    "features.enable_beta_features.help": "⚠ DANGER — these tools can PERMANENTLY DAMAGE your Home Assistant installation. They write to your YAML config, your filesystem, install custom components, run arbitrary sandboxed Python, and edit tool docstrings the AI sees. There is no warranty and no support guarantee — you enable them at your OWN RISK. Take a Home Assistant backup before turning this on, and never enable in production without one. Master gate for the experimental sub-flags below; sub-flags are ignored at runtime while this master is off, even when explicitly set to true. The same toggle is also surfaced in the web settings UI under \"Beta features (dangerous)\" — either surface reflects the other on restart.",
     "features.enable_yaml_config_editing.label": "Enable YAML config editing (beta)",
     "features.enable_yaml_config_editing.help": "Beta feature. Allows AI assistants to add, replace, or remove top-level keys in configuration.yaml and packages/*.yaml. Only whitelisted keys are allowed (e.g., template, sensor, command_line, mqtt, knx); core keys like homeassistant, http, and recorder are blocked. Each edit validates YAML syntax, runs a config check, and creates an automatic backup. Changes to most keys require a full HA restart to take effect. See docs/beta.md for known limitations. Dedicated tools (automations, scripts, scenes, helpers, template sensors) should be preferred when available. REQUIRES the master \"Enable beta features\" toggle above (and in the web UI) to be on — otherwise this sub-flag is ignored at runtime regardless of its value here.",
     "features.enable_yaml_edit_confirm.label": "Require confirmation for YAML edits (diff preview)",
@@ -441,7 +441,7 @@
     "addon.enable_security_policy_tool.name": "Let AI agents edit tool security policies",
     "addon.enable_security_policy_tool.description": "Registers the ha_manage_security_policy tool, which lets connected AI agents read and rewrite the tool security policies — including removing approval gates. Off by default. Independent of the Tool Security Policies option above: this controls who can edit the rules, not whether they are enforced. The tool cannot see or decide pending approvals. To keep a human in the loop, gate the tool before enabling it: switch on \"security gated\" for Manage Security Policy in the Tools tab of the web UI. Requires restart to take effect.",
     "addon.enable_auto_backup.name": "Enable auto-backup of edits",
-    "addon.enable_auto_backup.description": "Captures a per-entity snapshot before every wrapped write/destructive MCP tool call (automation, script, scene, helper, dashboard, label, category, group, zone, area, calendar, todo, entity, integration, and sibling remove/delete tools). Snapshots are saved as YAML files under /data/ha_mcp_backups/ (override via HAMCP_BACKUP_DIR) and listed, restored, or deleted via the Backups tab in the web settings UI or via ha_manage_backup(scope='edits', ...). Best-effort — failures log a WARNING but never block the underlying write. On by default; uncheck to opt out. Requires restart to take effect.",
+    "addon.enable_auto_backup.description": "Captures a per-entity snapshot before every wrapped write/destructive MCP tool call (automation, script, scene, helper, dashboard, dashboard resource, label, category, group, zone, area, calendar, todo, entity, device, integration, and sibling remove/delete tools). The auto-backup throttle bounds how often that happens: 0 (default) captures on every such call, N>0 at most one snapshot per N minutes per entity. Snapshots are saved as YAML files under /data/ha_mcp_backups/ (override via HAMCP_BACKUP_DIR) and listed, restored, or deleted via the Backups tab in the web settings UI or via ha_manage_backup(scope='edits', ...). For those domains the capture is best-effort — a failure logs a WARNING and the write proceeds. The file and raw-YAML tools are the exception: ha_write_file, ha_delete_file and ha_config_set_yaml treat the snapshot as a precondition, so a write through them is refused while this is off, and a failed capture blocks it. On by default; unchecking opts out of the best-effort captures and takes the file and raw-YAML tools out of service with them. Requires restart to take effect.",
     "addon.auto_backup_throttle_minutes.name": "Auto-backup throttle (minutes)",
     "addon.auto_backup_throttle_minutes.description": "Per-entity throttle window. 0 (default) captures a snapshot on every wrapped write. N>0 captures at most one snapshot per N minutes per entity. Range 0–1440.",
     "addon.auto_backup_retain_per_entity.name": "Auto-backup retention (per entity)",

ha_mcp_dev-8.2.0.dev2321/src/ha_mcp/settings_ui/locales/eo.json

@@ -0,0 +1,26 @@
+{
+  "meta": {
+    "native_name": "Esperanto",
+    "dir": "ltr"
+  },
+  "messages": {
+    "accessibility.storage_blocked": "Via retumilo blokas la konservadon de retejaj datumoj; viaj elektoj validas nur por ĉi tiu seanco.",
+    "actions.approve": "Aprobi",
+    "actions.deny": "Rifuzi",
+    "notice.restart.standalone": "⚠ Ŝanĝoj konservitaj. Restartigu la procezon ha-mcp, poste aktualigu la liston de MCP-iloj en via AI-kliento.",
+    "policies.operators.exists": "ekzistas",
+    "policies.operators.exists_long": "ekzistas (iu ajn valoro)",
+    "policies.operators.eq": "egalas",
+    "policies.operators.neq": "NE egalas",
+    "policies.operators.in": "estas unu el",
+    "policies.operators.not_in": "NE estas unu el",
+    "policies.operators.contains": "enhavas",
+    "policies.operators.regex": "kongruas kun regula esprimo",
+    "policies.operators.gt": "estas pli granda ol",
+    "policies.operators.lt": "estas pli malgranda ol",
+    "policies.pending.already_decided": "Ĉi tiu aprobo jam estis {decision}, eble de alia langeto aŭ seanco.",
+    "policies.pending.decision.approved": "aprobita",
+    "policies.pending.decision.denied": "rifuzita",
+    "visibility.errors.conflict": "La agordo estis ŝanĝita en alia langeto aŭ seanco. Reŝargu la paĝon, poste reapliku viajn ŝanĝojn."
+  }
+}

{ha_mcp_dev-8.2.0.dev2318 → ha_mcp_dev-8.2.0.dev2321}/src/ha_mcp/settings_ui/settings.js

@@ -1936,7 +1936,7 @@ const FEATURE_META = {
   },
   enable_beta_features: {
     label: "Enable beta features (master)",
-    help: "⚠ DANGER — these tools can PERMANENTLY DAMAGE your Home Assistant installation. They write to your YAML config, your filesystem, install custom components, run arbitrary sandboxed Python, and edit tool docstrings the AI sees. There is no warranty and no support guarantee — you enable them at your OWN RISK. Take a Home Assistant backup before turning this on, and never enable in production without one. Master gate for the 5 experimental sub-flags below; sub-flags are ignored at runtime while this master is off, even when explicitly set to true. The same toggle is also surfaced in the web settings UI under \"Beta features (dangerous)\" — either surface reflects the other on restart.",
+    help: "⚠ DANGER — these tools can PERMANENTLY DAMAGE your Home Assistant installation. They write to your YAML config, your filesystem, install custom components, run arbitrary sandboxed Python, and edit tool docstrings the AI sees. There is no warranty and no support guarantee — you enable them at your OWN RISK. Take a Home Assistant backup before turning this on, and never enable in production without one. Master gate for the experimental sub-flags below; sub-flags are ignored at runtime while this master is off, even when explicitly set to true. The same toggle is also surfaced in the web settings UI under \"Beta features (dangerous)\" — either surface reflects the other on restart.",
   },
   enable_yaml_config_editing: {
     label: "Enable YAML config editing (beta)",

{ha_mcp_dev-8.2.0.dev2318 → ha_mcp_dev-8.2.0.dev2321/src/ha_mcp_dev.egg-info}/PKG-INFO

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

{ha_mcp_dev-8.2.0.dev2318 → ha_mcp_dev-8.2.0.dev2321}/src/ha_mcp_dev.egg-info/SOURCES.txt

@@ -147,6 +147,7 @@ src/ha_mcp/settings_ui/settings.js
 src/ha_mcp/settings_ui/locales/README.md
 src/ha_mcp/settings_ui/locales/de.json
 src/ha_mcp/settings_ui/locales/en.json
+src/ha_mcp/settings_ui/locales/eo.json
 src/ha_mcp/settings_ui/locales/es.json
 src/ha_mcp/settings_ui/locales/fr.json
 src/ha_mcp/settings_ui/locales/it.json