vmware-aiops 2.4.0__tar.gz → 2.4.2__tar.gz

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "vmware-aiops",
   "displayName": "VMware AIops",
-  "version": "2.4.0",
+  "version": "2.4.2",
   "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "author": {
     "name": "Wei Zhou",

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/.mcp.json

@@ -5,7 +5,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aiops==2.4.0",
+        "vmware-aiops==2.4.2",
         "vmware-aiops-mcp"
       ]
     }

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: vmware-aiops
-Version: 2.4.0
+Version: 2.4.2
 Summary: VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool
 Project-URL: Homepage, https://github.com/vmware-skills/VMware-AIops
 Project-URL: Repository, https://github.com/vmware-skills/VMware-AIops
@@ -12,13 +12,13 @@ License-File: LICENSE
 Requires-Python: >=3.10
 Requires-Dist: apscheduler<4.0,>=3.10
 Requires-Dist: httpx<1.0,>=0.27
-Requires-Dist: mcp[cli]<2.0,>=1.28
+Requires-Dist: mcp[cli]<2.0,>=1.30
 Requires-Dist: pyaml<27.0,>=24.0
 Requires-Dist: python-dotenv<2.0,>=1.0
 Requires-Dist: pyvmomi<10.0,>=8.0.3.0
 Requires-Dist: rich<16.0,>=13.0
 Requires-Dist: typer<1.0,>=0.12
-Requires-Dist: vmware-monitor<3.0,>=2.3.1
+Requires-Dist: vmware-monitor<3.0,>=2.4.2
 Requires-Dist: vmware-policy<2.0,>=1.23.1
 Description-Content-Type: text/markdown
 

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/RELEASE_NOTES.md

@@ -1,3 +1,82 @@
+## v2.4.2 — a login refused for lack of a role says so; an unreadable host is not called unreachable (2026-10-19)
+
+Needs vmware-monitor 2.4.2 (now the floor). Found on a vCenter 8.0.3 lab with two restricted SSO accounts
+(follow-up to AIops#47).
+
+* **A login vCenter refuses with `NoPermission` gets the role error, not the raw fault.** For an account with no
+  permission anywhere, vCenter refuses the login itself (`System.View` on the root folder), so the post-login
+  no-role check never ran and `doctor` and every tool showed the raw fault with a connectivity hint. It now raises
+  the no-role error: the "no vSphere role / Global Permissions" remedy only for a vCenter target and `System.View`;
+  an ESXi target or another privilege gets a neutral text naming the (sanitized) privilege. A wrong password
+  (`InvalidLogin`) is unchanged. Same text as vmware-monitor.
+* **vmk tools and `cluster info` no longer call an unreadable host unreachable.** When the account cannot read a
+  host's connection state, `list_host_vmks` rows and the vmk write tools' refusal say the account cannot read the
+  host (`reachable: false` means "not read"), instead of advising a reconnect. `cluster info` colours the state
+  yellow, not red.
+* **From vmware-monitor 2.4.2 (through `get_cluster_health_summary` / `get_cross_vcenter_attention`):** a host this
+  account cannot read is counted `hosts_unreadable` with a warning issue `host_unreadable`, not ranked as a
+  critical `host_down`.
+
+## Unreleased — follow-ups to the 2.4.1 review
+
+* **Previews show policy refusals.** `restore_vm_clean_slate`, `provision_vm_guest` and
+  `run_vm_guest_command_with_output` were refused by `rules.yaml` only at `confirm=True`; the preview now lists that
+  refusal in `blast_radius.blockers`, so the user sees it before agreeing.
+* **A delete that powers the VM off first is checked as `power_off_vm` too:** the CLI `vm delete`, the TTL daemon,
+  and a plan rollback deleting the VM it created (checked when the VM is running or its state cannot be read). The
+  TTL daemon records one `delete_vm` row per change of outcome, as for a deny on `delete_vm`, and keeps the entry.
+  **Behaviour change for custom network roles:** a role that allows `set_vm_ttl` must also allow `power_off_vm`.
+* **Image cache:** writes take a lock across processes (a CLI and an MCP scan at the same time lost one side's
+  rows); a scan keeps rows on datastores it failed to browse (its own or legacy ones) and drops this target's rows
+  on datastores that no longer exist. A cache that cannot be written no longer fails the scan: the images come back
+  with a `cache_note`, as in vmware-storage.
+* **Each call is checked for what it will do, at the moment it does it.** `restore_vm_clean_slate` asks about
+  `power_off_vm` only when it actually powers the VM off; `provision_vm_guest` asks about the guest tools its step
+  types use (an exec-only provision is not refused by a deny on `upload_vm_guest_file`); a plan rollback asks about
+  the power-off after confirming it is the VM the plan created, just before powering it off.
+* **`set_vm_ttl` is checked as the deletion it schedules:** the preview lists a deny on `delete_vm` (and on
+  `power_off_vm` for a running VM), and `confirm=True` refuses it, instead of scheduling a TTL the daemon can never
+  act on. The daemon still asks again at expiry.
+* **`migrate_vm` previews run vCenter's own vMotion compatibility check** (`CheckMigrate_Task`, read-only): its
+  errors (CPU features, devices, networks, datastores) become blockers, with the CPU-feature remedy where it applies,
+  so a move vCenter would refuse is refused in the preview and before the CLI asks for confirmation; warnings are
+  shown and do not block. On a standalone ESXi host, or when the check cannot run, the preview says "not checked"
+  and does not block (vCenter checks again when the move starts). Plan migrate steps get the same check.
+* The TTL store takes the same cross-process lock as the image cache (`set_vm_ttl` and the daemon run in separate
+  processes).
+
+## v2.4.1 — fixes from the 2026-10-17 real-hardware read and write rounds
+
+* **Tools that run other tools' operations obey `rules.yaml` for those tools**, on the MCP and CLI surfaces.
+  `restore_vm_clean_slate`, the batch tools, `provision_vm_guest`, and the deploy tools' `power_on` / snapshot /
+  CPU-memory follow-ups are refused, with a `denied` audit row, when the policy denies the tool that does that part
+  (a deny on `revert_vm_snapshot` used to leave clean slate working; a deny on `power_on_vm` did not stop
+  `batch_clone_vms(power_on=True)`). A follow-up is checked only when the call asks for it. `run_vm_guest_command_with_output` is
+  checked as `run_vm_guest_command` (and `download_vm_guest_file`) too.
+* **Behaviour change for custom network roles:** a role check reads no arguments, so a role that allows
+  `deploy_vm_from_template`, `deploy_vm_from_ova` or `deploy_linked_clone` must now also allow `power_on_vm`,
+  `create_vm_snapshot` and `reconfigure_vm` (and one allowing `run_vm_guest_command_with_output` must allow
+  `run_vm_guest_command` and `download_vm_guest_file`), or every call is refused. The built-in `reader` and `admin`
+  roles are unaffected.
+* **Plan steps obey `rules.yaml`.** Each step of `apply_vm_plan` / `rollback_vm_plan` is authorized by vmware-policy
+  under the tool that does the same thing (a `delete_vm` step as `delete_vm`, `power_off` as `power_off_vm`, the
+  rollback that deletes a VM the plan created as `delete_vm`), at that tool's risk level — in the preview and again
+  just before the step runs, with a `denied` audit row. A deny on `delete_vm` used to stop the tool but not a plan step.
+* **Failures are failures.** Deploy, clone, linked clone, template conversion, ISO attach, `create_vm`, `migrate_vm`,
+  `reconfigure_vm` and `configure_cluster` with nothing to change returned their refusals as status strings, which
+  the MCP frame and the audit recorded as success; they now raise. A plan that stops part-way, a rollback that leaves
+  a step not undone, and a plan that fails validation now carry the family `error` key.
+* **`deploy_vm_from_template` works on a vCenter with standalone hosts**: the clone gets the template's resource
+  pool (it failed with `spec.location.pool`), and the tool now takes `target_host`.
+* **`scan_all_datastore_images` keeps each target's images**: the cache was one list replaced by every scan, so
+  scanning `datastore1` on an ESXi host erased what a vCenter scan had found. Entries now carry `target`; a corrupt
+  cache file is rebuilt by the next scan and explained by the error instead of a bare JSON error.
+* **`browse_datastore` sees every file** (`.ova`, `.ovf`, `.vmx`, `.log` were filtered out), `ds_path` is well formed
+  for ESXi and vCenter folder paths, and a leading `/` is refused with the corrected path, as vmware-storage does.
+* Error text names MCP tools and parameters (CLI form in brackets); doctor is suggested only for connectivity errors;
+  a CPU-feature vMotion refusal leads with the remedy; `get_vm_task_status` no longer says an unknown id means the
+  task finished; powering off a VM that is already off is a plain `noop`.
+
 ## v2.4.0 — roles for network callers (HLD §18)
 
 * Declares the role metadata vmware-policy ≥ 1.24.0 needs to apply **roles** to this server over HTTPS

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/openclaw.plugin.json

@@ -11,7 +11,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-aiops==2.4.0",
+        "vmware-aiops==2.4.2",
         "vmware-aiops-mcp"
       ]
     }

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zw008/vmware-aiops",
-  "version": "2.4.0",
+  "version": "2.4.2",
   "description": "AI-powered VMware vCenter/ESXi VM lifecycle and deployment with 61 MCP tools.",
   "private": true,
   "license": "MIT",

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vmware-aiops"
-version = "2.4.0"
+version = "2.4.2"
 description = "VMware vCenter/ESXi AI-powered VM lifecycle and deployment tool"
 readme = "README.md"
 license = "MIT"
@@ -18,12 +18,12 @@ dependencies = [
     "apscheduler>=3.10,<4.0",
     "httpx>=0.27,<1.0",
     "python-dotenv>=1.0,<2.0",
-    "mcp[cli]>=1.28,<2.0",
+    "mcp[cli]>=1.30,<2.0",
     "vmware-policy>=1.23.1,<2.0",
     # Read-only cluster-health triage (summary + HTML snapshot) is owned by
     # vmware-monitor; AIops delegates to it so a conversation with the AIops
     # entry point can produce the same report without duplicating the code.
-    "vmware-monitor>=2.3.1,<3.0",  # attention status floor + role-less login (AIops#47)
+    "vmware-monitor>=2.4.2,<3.0",  # unreadable host != down, login refused -> role error
 ]
 
 

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/vmware-skills/VMware-AIops",
     "source": "github"
   },
-  "version": "2.4.0",
+  "version": "2.4.2",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "vmware-aiops",
-      "version": "2.4.0",
+      "version": "2.4.2",
       "runtimeHint": "uvx",
       "packageArguments": [
         {

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/skills/vmware-aiops/SKILL.md

@@ -63,7 +63,7 @@ Read before connecting an agent. Per-tool inventory: `references/capabilities.md
 ## Quick Install
 
 ```bash
-uv tool install vmware-aiops==2.4.0
+uv tool install vmware-aiops==2.4.2
 vmware-aiops doctor
 vmware-aiops hub status   # see which family members are installed
 ```
@@ -303,7 +303,7 @@ The account has no vSphere role. Assign one (Read-Only or higher) on the vCenter
 ## Setup
 
 ```bash
-uv tool install vmware-aiops==2.4.0
+uv tool install vmware-aiops==2.4.2
 mkdir -p ~/.vmware-aiops
 vmware-aiops init  # generates config.yaml and .env templates
 chmod 600 ~/.vmware-aiops/.env

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/skills/vmware-aiops/references/setup-guide.md

@@ -6,13 +6,13 @@ All install methods fetch from the same source: [github.com/vmware-skills/VMware
 
 ```bash
 # Via PyPI (recommended for version pinning)
-uv tool install vmware-aiops==2.4.0
+uv tool install vmware-aiops==2.4.2
 
 # Via Skills.sh (fetches from GitHub)
-npx skills add vmware-skills/VMware-AIops#v2.4.0
+npx skills add vmware-skills/VMware-AIops#v2.4.2
 
 # Via ClawHub (fetches from ClawHub registry snapshot of GitHub)
-clawhub install @zw008/vmware-aiops --version 2.4.0
+clawhub install @zw008/vmware-aiops --version 2.4.2
 ```
 
 ### Claude Code
@@ -35,7 +35,7 @@ claude mcp add vmware-aiops -- vmware-aiops mcp
 
 ```bash
 # 1. Install from PyPI (source: github.com/vmware-skills/VMware-AIops)
-uv tool install vmware-aiops==2.4.0
+uv tool install vmware-aiops==2.4.2
 
 # 2. Verify installation source
 vmware-aiops --version  # confirms installed version
@@ -73,7 +73,7 @@ The `vmware-aiops` package installs a Python CLI binary and its dependencies (py
 ## Development Install
 
 ```bash
-git clone --branch v2.4.0 https://github.com/vmware-skills/VMware-AIops.git
+git clone --branch v2.4.2 https://github.com/vmware-skills/VMware-AIops.git
 cd VMware-AIops
 uv venv && source .venv/bin/activate
 # --no-sources: pyproject's [tool.uv.sources] points vmware-monitor at a sibling

vmware_aiops-2.4.2/tests/eval/regression/test_browse_ds_path_join.py

@@ -0,0 +1,79 @@
+"""browse_datastore must return a ds_path that deploy/attach tools can use.
+
+Regression source: real ESXi 8 host (home-esxi, 2026-10-17). The browse task
+reports each folder's ``folderPath`` with no trailing separator —
+``"[datastore1]"`` for the root, ``"[datastore1] backup"`` for a folder —
+and the old code glued the file name straight on, producing
+``"[datastore1] backupVMware-VCSA.iso"`` and ``"[datastore1]Hermers - TT"``.
+Agents pass that string into deploy_vm_from_ova / attach_iso_to_vm, so a
+malformed path breaks the very flow the browse exists for. The earlier tests
+mocked ``"[ds1] images/"`` (trailing slash), the one shape that hid the bug.
+"""
+from __future__ import annotations
+
+from types import SimpleNamespace
+
+import pytest
+from pyVmomi import vim
+
+from vmware_aiops.ops import datastore_browser as dsb
+
+
+@pytest.mark.unit
+@pytest.mark.parametrize(
+    ("folder", "name", "expected"),
+    [
+        # Root, as ESXi reports it: no space after the bracket.
+        ("[datastore1]", "Hermers - TT", "[datastore1] Hermers - TT"),
+        ("[datastore1]", "x.iso", "[datastore1] x.iso"),
+        # Root, as vCenter reports it: trailing space.
+        ("[datastore1] ", "x.iso", "[datastore1] x.iso"),
+        # Folder without a trailing slash (ESXi).
+        ("[datastore1] backup", "x.iso", "[datastore1] backup/x.iso"),
+        (
+            "[datastore1] Hermers - TT",
+            "Hermers - TT.vmdk",
+            "[datastore1] Hermers - TT/Hermers - TT.vmdk",
+        ),
+        ("[datastore1] a/b", "x.iso", "[datastore1] a/b/x.iso"),
+        # Folder with a trailing slash (vCenter) — must not double it.
+        ("[datastore1] backup/", "x.iso", "[datastore1] backup/x.iso"),
+    ],
+)
+def test_join_ds_path(folder, name, expected):
+    assert dsb._join_ds_path(folder, name) == expected
+
+
+@pytest.mark.unit
+def test_browse_root_returns_well_formed_paths_for_every_folder(monkeypatch):
+    """Root browse is recursive: subfolder rows come back too, each well formed."""
+    def _file(path):
+        return SimpleNamespace(path=path, fileSize=1024 * 1024, modification="2026-10-17")
+
+    results = [
+        SimpleNamespace(folderPath="[datastore1]", file=[_file("backup")]),
+        SimpleNamespace(folderPath="[datastore1] backup", file=[_file("x.iso")]),
+    ]
+    seen = {}
+
+    def fake_search(datastorePath, searchSpec):  # noqa: N803 — pyVmomi API names
+        seen["path"] = datastorePath
+        return SimpleNamespace(
+            info=SimpleNamespace(state=vim.TaskInfo.State.success, result=results, error=None)
+        )
+
+    monkeypatch.setattr(
+        dsb,
+        "find_datastore_by_name",
+        lambda si, name: SimpleNamespace(
+            browser=SimpleNamespace(SearchDatastoreSubFolders_Task=fake_search)
+        ),
+    )
+
+    rows = dsb.browse_datastore(object(), "datastore1")["items"]
+
+    assert seen["path"] == "[datastore1]"
+    assert {r["name"]: r["ds_path"] for r in rows} == {
+        "backup": "[datastore1] backup",
+        "x.iso": "[datastore1] backup/x.iso",
+    }

vmware_aiops-2.4.2/tests/eval/regression/test_browse_sees_every_file.py

@@ -0,0 +1,70 @@
+"""browse_datastore must see every file, and treat a leading '/' one way.
+
+Real hardware, 2026-10-17: vmware-aiops' search spec listed only IsoImageQuery,
+VmDiskQuery and FolderQuery under a comment saying "include all file types".
+A DatastoreBrowser query is a filter, not a hint -- with those three, .ova /
+.ovf / .vmx / .log files are never returned. On the lab vCenter it found 0 of
+the 2 OVAs on 'datastore1 (1)' that vmware-storage (which also passes the
+generic Query) found, so scan_all_datastore_images could not do the one job its
+description gives it: finding an OVA for deploy_vm_from_ova.
+
+The twin also drifted on a leading slash: vmware-aiops passed '/vcsa8' through,
+vmware-storage refused it as "absolute" (its 1.5.35 hardening). Both now refuse
+it, and the error names the corrected path.
+"""
+from __future__ import annotations
+
+from types import SimpleNamespace
+
+import pytest
+from pyVmomi import vim
+
+from vmware_aiops.ops import datastore_browser as dsb
+
+
+def _browse(monkeypatch, path=""):
+    seen: dict = {}
+
+    def fake_search(datastorePath, searchSpec):  # noqa: N803 -- pyVmomi API names
+        seen["path"] = datastorePath
+        seen["spec"] = searchSpec
+        return SimpleNamespace(
+            info=SimpleNamespace(state=vim.TaskInfo.State.success, result=[], error=None)
+        )
+
+    monkeypatch.setattr(
+        dsb,
+        "find_datastore_by_name",
+        lambda si, name: SimpleNamespace(
+            browser=SimpleNamespace(SearchDatastoreSubFolders_Task=fake_search)
+        ),
+    )
+    dsb.browse_datastore(object(), "datastore1", path=path, pattern="*.ova")
+    return seen
+
+
+@pytest.mark.unit
+def test_search_spec_includes_the_generic_file_query(monkeypatch) -> None:
+    spec = _browse(monkeypatch)["spec"]
+    # Exact type: every specific query subclasses Query, so isinstance would pass
+    # for the three that hid the OVAs.
+    assert any(type(q) is vim.host.DatastoreBrowser.Query for q in spec.query)
+
+
+@pytest.mark.unit
+def test_relative_path_is_joined_under_the_datastore(monkeypatch) -> None:
+    assert _browse(monkeypatch, "vcsa8")["path"] == "[datastore1] vcsa8"
+
+
+@pytest.mark.unit
+@pytest.mark.parametrize("path", ["/vcsa8", "//vcsa8"])
+def test_leading_slash_is_refused_with_the_fix(monkeypatch, path) -> None:
+    with pytest.raises(ValueError, match="path='vcsa8'"):
+        _browse(monkeypatch, path)
+
+
+@pytest.mark.unit
+@pytest.mark.parametrize("path", ["../other", "a/../../b", "x\x00y", "\\\\server\\share", "/"])
+def test_traversal_and_odd_paths_are_refused(monkeypatch, path) -> None:
+    with pytest.raises(ValueError, match="datastore-relative"):
+        _browse(monkeypatch, path)

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/tests/eval/regression/test_cli_writes_guarded.py

@@ -51,7 +51,9 @@ def _ops_refs(tree: ast.AST) -> tuple[dict[str, str], set[str]]:
     for n in ast.walk(tree):
         if isinstance(n, ast.ImportFrom) and n.module:
             parts = n.module.split(".")
-            if "ops" in parts:
+            # step_policy authorizes the operation; it is not the operation, and
+            # every composite command calls it (2026-10-17).
+            if "ops" in parts and parts[-1] != "step_policy":
                 if parts[-1] == "ops":
                     mods.update(a.asname or a.name for a in n.names)
                 else:

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/tests/eval/regression/test_code_review_fixes.py

@@ -127,7 +127,7 @@ def test_ttl_entry_kept_on_transient_failure(monkeypatch: pytest.MonkeyPatch) ->
     monkeypatch.setattr(scheduler, "remove_entry", removed.append)
     monkeypatch.setattr(
         scheduler, "delete_vm",
-        lambda si, name: (_ for _ in ()).throw(RuntimeError("vCenter task timeout")),
+        lambda si, name, **k: (_ for _ in ()).throw(RuntimeError("vCenter task timeout")),
     )
 
     scheduler._run_ttl_check(MagicMock())
@@ -143,7 +143,7 @@ def test_ttl_entry_removed_when_vm_already_gone(monkeypatch: pytest.MonkeyPatch)
     monkeypatch.setattr(scheduler, "remove_entry", removed.append)
     monkeypatch.setattr(
         scheduler, "delete_vm",
-        lambda si, name: (_ for _ in ()).throw(VMNotFoundError("VM 'ttl-vm' not found")),
+        lambda si, name, **k: (_ for _ in ()).throw(VMNotFoundError("VM 'ttl-vm' not found")),
     )
 
     scheduler._run_ttl_check(MagicMock())
@@ -156,7 +156,7 @@ def test_ttl_entry_removed_on_success(monkeypatch: pytest.MonkeyPatch) -> None:
     removed: list[str] = []
     monkeypatch.setattr(scheduler, "get_expired_entries", lambda: [_ttl_entry()])
     monkeypatch.setattr(scheduler, "remove_entry", removed.append)
-    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: f"VM '{name}' deleted")
+    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: f"VM '{name}' deleted")
 
     scheduler._run_ttl_check(MagicMock())
     assert removed == ["ttl-vm"]

{vmware_aiops-2.4.0 → vmware_aiops-2.4.2}/tests/eval/regression/test_daemon_calls_are_audited.py

@@ -71,7 +71,7 @@ def ttl(monkeypatch):
 
 def test_a_ttl_delete_writes_one_vm_delete_row(ttl, monkeypatch):
     scheduler, removed = ttl
-    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: f"VM '{name}' deleted")
+    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: f"VM '{name}' deleted")
 
     scheduler._run_ttl_check(MagicMock())
 
@@ -88,7 +88,7 @@ def test_a_ttl_delete_writes_one_vm_delete_row(ttl, monkeypatch):
 def test_a_failed_ttl_delete_is_recorded_as_error_and_the_entry_kept(ttl, monkeypatch):
     scheduler, removed = ttl
 
-    def boom(si, name):
+    def boom(si, name, **k):
         raise RuntimeError("vCenter task timeout")
 
     monkeypatch.setattr(scheduler, "delete_vm", boom)
@@ -106,7 +106,7 @@ def test_a_ttl_vm_already_gone_is_recorded_and_the_stale_entry_dropped(ttl, monk
 
     scheduler, removed = ttl
 
-    def gone(si, name):
+    def gone(si, name, **k):
         raise VMNotFoundError(f"VM '{name}' not found")
 
     monkeypatch.setattr(scheduler, "delete_vm", gone)
@@ -122,7 +122,7 @@ def test_a_ttl_vm_already_gone_is_recorded_and_the_stale_entry_dropped(ttl, monk
 def test_a_ttl_delete_refused_by_policy_never_runs(ttl, monkeypatch):
     scheduler, removed = ttl
     deleted: list[str] = []
-    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: deleted.append(name))
+    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: deleted.append(name))
 
     def deny(skill, tool, params=None, *, risk_level="low", target=""):
         raise PolicyDenied(
@@ -144,7 +144,7 @@ def test_a_refused_ttl_entry_writes_one_row_per_outcome_not_one_per_minute(ttl,
     failing entry wrote a delete_vm row on every run — 1,440 a day per entry, on
     this lab whose rules.yaml denies delete_vm — burying real calls."""
     scheduler, removed = ttl
-    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: None)
+    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: None)
 
     def deny(skill, tool, params=None, *, risk_level="low", target=""):
         raise PolicyDenied(
@@ -165,7 +165,7 @@ def test_a_failing_ttl_delete_writes_again_only_when_its_outcome_changes(ttl, mo
     scheduler, removed = ttl
     attempts: list[str] = []
 
-    def flaky(si, name):
+    def flaky(si, name, **k):
         attempts.append(name)
         if len(attempts) <= 3:
             raise RuntimeError("vCenter task timeout")
@@ -315,7 +315,7 @@ def test_a_ttl_vm_whose_name_is_ambiguous_is_not_deleted_and_the_entry_dropped(t
 
     scheduler, removed = ttl
 
-    def ambiguous(si, name):
+    def ambiguous(si, name, **k):
         raise AmbiguousVMError(f"2 VMs are named '{name}'.")
 
     monkeypatch.setattr(scheduler, "delete_vm", ambiguous)
@@ -332,7 +332,7 @@ def test_daemon_rows_say_daemon_not_mcp(ttl, monkeypatch):
     """HLD §16 D-14: a TTL delete made by the daemon is not an MCP call. Without
     an explicit surface the row read `mcp-stdio` — non-empty, and wrong."""
     scheduler, _removed = ttl
-    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name: f"VM '{name}' deleted")
+    monkeypatch.setattr(scheduler, "delete_vm", lambda si, name, **k: f"VM '{name}' deleted")
 
     scheduler._run_ttl_check(MagicMock())