ha-mcp-dev 7.13.0.dev1962__tar.gz → 7.13.0.dev1966__tar.gz

{ha_mcp_dev-7.13.0.dev1962/src/ha_mcp_dev.egg-info → ha_mcp_dev-7.13.0.dev1966}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ha-mcp-dev
-Version: 7.13.0.dev1962
+Version: 7.13.0.dev1966
 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.13.0.dev1962 → ha_mcp_dev-7.13.0.dev1966}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ha-mcp-dev"
-version = "7.13.0.dev1962"
+version = "7.13.0.dev1966"
 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-7.13.0.dev1962 → ha_mcp_dev-7.13.0.dev1966}/src/ha_mcp/strict_bps.py

@@ -8,7 +8,10 @@ the call carries an acknowledgment key that is published ONLY inside the
 best-practices skill content served by ``ha_get_skill_guide``. The block
 error tells the model exactly how to obtain the key but never the key
 itself, forcing it to actually fetch/read the best practices before
-writing.
+writing. It also pre-arms the model with a recovery hint for clients that
+validate tool calls against a stale cached tool schema and reject the
+``BestPracticeKey`` retry client-side (#1901) — that rejection never
+reaches the server, so it cannot be handled anywhere else.
 
 Strict mode is *effective* only when BOTH ``enable_mandatory_bps`` (the
 parent, #1182) and ``enable_strict_mandatory_bps`` (the child, #1779) are
@@ -161,8 +164,12 @@ def strict_bps_ack_line() -> str:
 def _raise_bps_ack_required_error(name: str) -> NoReturn:
     """Raise the structured block error for a gated write missing the key.
 
-    The message and suggestion tell the model how to obtain the key but
-    never contain the key itself.
+    Neither suggestion ever contains the key itself. The first tells the
+    model how to obtain it; the second pre-arms the model for clients
+    that validate tool arguments against a stale cached tool schema and
+    reject the ``BestPracticeKey`` retry client-side (#1901) — that
+    rejection never reaches the server, so this error is the only server
+    surface that can carry the recovery path.
     """
     reference_file = STRICT_BPS_GATED_TOOLS[name]
     message = (
@@ -178,7 +185,14 @@ def _raise_bps_ack_required_error(name: str) -> NoReturn:
             suggestions=[
                 f"Call ha_get_skill_guide(skill={_HA_BEST_PRACTICES_SKILL_NAME!r}, "
                 f"file={reference_file!r}), read the content, then retry with "
-                f"{STRICT_BPS_KEY_PARAM} set."
+                f"{STRICT_BPS_KEY_PARAM} set.",
+                f"If your client then rejects the retry with a schema-validation "
+                f"error such as 'must NOT have additional properties', it is "
+                f"validating against a stale cached tool schema from an older "
+                f"server version that lacks {STRICT_BPS_KEY_PARAM}. Ask the user "
+                f"to fully reload the client application (VS Code: run "
+                f"'Developer: Reload Window' — restarting the MCP server or "
+                f"resetting cached tools is not enough), then retry.",
             ],
             context={"tool_name": name, "strict_mandatory_bps": True},
         )

{ha_mcp_dev-7.13.0.dev1962 → ha_mcp_dev-7.13.0.dev1966/src/ha_mcp_dev.egg-info}/PKG-INFO

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