chore(addon): bump ha_mcp_tools to 0.5.1 + spell out tool names in rejects

Folds together three small things that share the same custom-
component file:

* Manifest bump 0.5.0 → 0.5.1 (was 0.6.0 in the earlier push;
  this is a small patch-shape change, not new capability — the
  PACKAGES_ONLY_YAML_KEYS branch is a routing addition, no new
  surface). Pattern mirrors homeassistant-ai#1459's bump on the same file.

* Patch76 follow-up #1 (PR comment 2026-05-28): spell each
  storage-mode tool out individually in the rejection guidance
  instead of the compact slash-form
  ``ha_config_set_automation/script/scene``. An agent reading
  the rejection at call time would otherwise parse that as one
  malformed tool name and fail to route. Locations:
  * ``__init__.py`` reject message
  * ``tools_yaml_config.py`` ``yaml_path`` parameter description

* Patch76 follow-up #2: ``TestHandleEditYamlConfigPathTraversal``
  pins the layering of ``os.path.normpath`` before the
  ``fnmatch`` package check so a crafted
  ``packages/../configuration.yaml`` cannot smuggle a
  PACKAGES_ONLY key (``automation``) into ``configuration.yaml``.
  Belt-and-suspenders against a future refactor reordering
  those two steps; defense is already correct by construction.

Updated tests for the spell-out:
* ``test_yaml_config.py`` E2E rejection asserts each tool name
  individually instead of the combined slash-string.
* ``test_yaml_dashboards.py::test_rejects_packages_only_key_in_configuration_yaml``
  does the same at the unit layer.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: kingpanther13

custom_components/ha_mcp_tools/__init__.py

@@ -774,7 +774,8 @@ def _parse_and_validate_yaml_path(
                     f"Key '{yaml_path}' is only allowed in packages/*.yaml "
                     "files, not in configuration.yaml. Move the edit to a "
                     "package file (e.g., packages/automations.yaml) or use "
-                    "ha_config_set_automation/script/scene for storage-mode."
+                    "ha_config_set_automation, ha_config_set_script, or "
+                    "ha_config_set_scene for storage-mode."
                 ),
             )
         allowed = (

custom_components/ha_mcp_tools/manifest.json

@@ -8,5 +8,5 @@
     "iot_class": "local_push",
     "issue_tracker": "https://github.com/homeassistant-ai/ha-mcp/issues",
     "requirements": ["ruamel.yaml>=0.18.0"],
-    "version": "0.5.0"
+    "version": "0.5.1"
 }

src/ha_mcp/tools/tools_yaml_config.py

@@ -111,9 +111,10 @@ async def ha_config_set_yaml(
                     "route. No other multi-segment paths are supported. "
                     "'automation', 'script', and 'scene' are accepted only when "
                     "file is under packages/*.yaml; in configuration.yaml use "
-                    "the dedicated ha_config_set_automation/script/scene tools "
-                    "(storage-mode). Not for template sensors or input_* "
-                    "helpers — those have dedicated tools."
+                    "the dedicated storage-mode tools "
+                    "(ha_config_set_automation, ha_config_set_script, "
+                    "ha_config_set_scene). Not for template sensors or "
+                    "input_* helpers — those have dedicated tools."
                 ),
             ),
         ],

tests/src/e2e/workflows/filesystem/test_yaml_config.py

@@ -488,8 +488,17 @@ async def test_packages_only_keys_rejected_in_configuration_yaml(
             assert "packages/*.yaml" in msg, (
                 f"{key} error message should mention packages/*.yaml: {data}"
             )
-            assert "ha_config_set_automation/script/scene" in msg, (
-                f"{key} error should point at storage-mode tools: {data}"
+            # Spell out each tool name individually — an agent reading
+            # the rejection would otherwise see the combined slash-form
+            # as a single (malformed) tool name and fail to route.
+            assert "ha_config_set_automation" in msg, (
+                f"{key} error should mention ha_config_set_automation: {data}"
+            )
+            assert "ha_config_set_script" in msg, (
+                f"{key} error should mention ha_config_set_script: {data}"
+            )
+            assert "ha_config_set_scene" in msg, (
+                f"{key} error should mention ha_config_set_scene: {data}"
             )
             # Rejected calls must not advertise reload metadata.
             assert data.get("post_action") is None, (

tests/src/unit/test_yaml_dashboards.py

@@ -221,7 +221,11 @@ def test_rejects_packages_only_key_in_configuration_yaml(self, parse, key):
         _, _, err = parse(key, is_package=False)
         assert err is not None
         assert "packages/*.yaml" in err
-        assert "ha_config_set_automation/script/scene" in err
+        # Spell each tool name out individually — an agent reading the
+        # rejection sees the combined slash-form as one malformed name.
+        assert "ha_config_set_automation" in err
+        assert "ha_config_set_script" in err
+        assert "ha_config_set_scene" in err
 
     def test_default_is_package_false(self, parse):
         # Omitting is_package must behave like is_package=False — no silent
@@ -693,3 +697,71 @@ def test_single_key_post_action_for_shell_command(
         )
         assert result["success"] is True, result
         assert result["post_action"] == "restart_required"
+
+
+class TestHandleEditYamlConfigPathTraversal:
+    """Path-traversal defense composes ``os.path.normpath`` before the
+    ``fnmatch`` package check, so a crafted ``packages/../configuration.yaml``
+    cannot smuggle a PACKAGES_ONLY key into ``configuration.yaml``."""
+
+    @pytest.fixture
+    def hass(self, tmp_path):
+        h = MM()
+        h.config = MM()
+        h.config.config_dir = str(tmp_path)
+        h.data = {DOMAIN: {"caller_token": _TEST_CALLER_TOKEN}}
+
+        async def _run(fn, *args):
+            return fn(*args)
+
+        h.async_add_executor_job = AsyncMock(side_effect=_run)
+        h.services = MM()
+        h.services.async_call = AsyncMock(return_value={"errors": None})
+        return h
+
+    @pytest.fixture
+    def call_factory(self):
+        def _make(data):
+            call = MM()
+            call.data = {**data, CALLER_TOKEN_FIELD: _TEST_CALLER_TOKEN}
+            return call
+
+        return _make
+
+    def _run(self, coro):
+        return asyncio.run(coro)
+
+    def test_packages_dotdot_normalizes_to_configuration_yaml_and_rejects(
+        self, tmp_path, hass, call_factory
+    ):
+        """``packages/../configuration.yaml`` → ``configuration.yaml`` after
+        normpath, so the ``packages/*.yaml`` fnmatch does not match and
+        ``yaml_path="automation"`` is rejected with the storage-mode pointer.
+
+        Pins the layering: normpath at __init__.py:330 must run before
+        the fnmatch package check at __init__.py:338 so a crafted path
+        cannot smuggle a PACKAGES_ONLY key into configuration.yaml. The
+        defense is correct by construction; this is belt-and-suspenders
+        against a future refactor reordering those two steps."""
+        from custom_components.ha_mcp_tools import _build_edit_yaml_config_handler
+
+        cfg = Path(tmp_path) / "configuration.yaml"
+        cfg.write_text("")
+
+        handler = _build_edit_yaml_config_handler(hass)
+        result = self._run(
+            handler(
+                call_factory(
+                    {
+                        "file": "packages/../configuration.yaml",
+                        "action": "add",
+                        "yaml_path": "automation",
+                        "content": "- id: x\n  alias: x\n",
+                        "backup": False,
+                    }
+                )
+            )
+        )
+        assert result["success"] is False
+        assert "packages/*.yaml" in result["error"]
+        assert "ha_config_set_automation" in result["error"]