vmware-debug 1.11.1__tar.gz → 1.11.3__tar.gz

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "vmware-debug",
   "displayName": "VMware Debug",
-  "version": "1.11.1",
+  "version": "1.11.3",
   "description": "Read-only VMware incident correlation: timeline, spikes, root-cause routing. 2 MCP tools.",
   "author": {
     "name": "Wei Zhou",

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/.mcp.json

@@ -5,7 +5,7 @@
       "command": "uvx",
       "args": [
         "--from",
-        "vmware-debug==1.11.1",
+        "vmware-debug==1.11.3",
         "vmware-debug-mcp"
       ]
     }

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: vmware-debug
-Version: 1.11.1
+Version: 1.11.3
 Summary: VMware diagnostic brain — read-only incident triage, log/event correlation, and root-cause routing across the VMware skill family
 Project-URL: Homepage, https://github.com/vmware-skills/VMware-Debug
 Project-URL: Repository, https://github.com/vmware-skills/VMware-Debug
@@ -18,7 +18,7 @@ Requires-Dist: mcp[cli]<2.0,>=1.10
 Requires-Dist: pyyaml<7.0,>=6.0
 Requires-Dist: rich<15.0,>=13.0
 Requires-Dist: typer<1.0,>=0.12
-Requires-Dist: vmware-policy<2.0,>=1.10.0
+Requires-Dist: vmware-policy<2.0,>=1.12.0
 Description-Content-Type: text/markdown
 
 <!-- mcp-name: io.github.vmware-skills/vmware-debug -->

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/README-CN.md

@@ -33,7 +33,9 @@ vmware-debug categories          # 看它能诊断哪些症状类别
 - `list_symptom_categories`：症状类别及对应的排查路由（不知道查什么时用它）
 
 **事件信封**：`{ts, source, severity, entity, text, fields}`。agent 把各源事件归一成此形状再交给
-debug；debug 因此与其它包零运行时依赖。
+debug；debug 因此与其它包零运行时依赖。**请把每条事件的 `event_type` 保留在 `fields` 里**——
+分类器除了正文之外也匹配它，而现代 vSphere 多数事件是 `EventEx`：正文是一句通用套话，
+真正说明「这是什么事件」的只有 `eventTypeId`。
 
 ## 安全
 

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/RELEASE_NOTES.md

@@ -1,3 +1,111 @@
+## v1.11.3 — 398 tests never ran
+
+
+**`tests/__init__.py` was missing, and the whole suite -- 398 tests -- failed at
+collection.** `tests/eval/` and `tests/eval/regression/` were already packages,
+so `from tests.eval.regression._vsphere_event_vocabulary import ...` resolved
+only where the namespace-package fallback happened to work. It did not on
+Windows. One file.
+
+**The suite now runs on a cp936 machine.** Round 3 of the VCF 9 field testing ran
+on Windows Server 2025 with locale cp936. Across the family four repos' suites --
+1687 tests -- never executed at all, dying at collection reading our own UTF-8
+sources, and 101 more failed the same way. Most of those were the tests that
+verify the destructive-operation guardrails: the guardrails were fine, the tests
+that check them could not open a file. On the UTF-8 CI every one of them was
+green. A security test that cannot run is not a security test.
+
+Every text read and write here names its encoding now, `tests/` included -- the
+previous round fixed only the package, which is why this came back. A gate in
+`family_smoke` scans both trees by AST, and the whole family's suites were re-run
+under an ASCII locale to confirm: 15 of 15 green, from 1 of 15.
+
+**`--help` no longer dies on a console that cannot encode it.** On any console
+whose encoding cannot carry the characters in our own help text, `--help` exited
+with a `UnicodeEncodeError` traceback -- unavailable exactly on the machines
+where it is most needed. Four repos were affected; the handler is now relaxed in
+all fifteen so a glyph degrades instead of killing the command.
+
+**Unknown tool arguments are refused instead of dropped.** The schema declared
+`additionalProperties: false` and the runtime accepted them anyway, so a filter
+argument whose name a model guessed wrong returned the *unfiltered* result with
+nothing to indicate anything had been discarded. Fixed in vmware-policy 1.12.0
+and in force here.
+
+Requires vmware-policy 1.12.0.
+
+## v1.11.2 — the resolver hijack, the discarded event identifier, and a parameter that did nothing
+
+Three findings from the 2026-08-30 real-hardware re-test. 
+
+**Importing this package no longer disables another skill's policy rules.**
+`vmware_debug.mcp_server.server` registered a `vmware_policy` environment
+resolver at import time, answering `local` for every target it was asked about.
+That slot is process-global — one function for every skill in the interpreter —
+so in an MCP host that loads several of these skills, importing vmware-debug
+replaced whatever a sibling had installed and every one of that sibling's targets
+began resolving to `local`. A rule scoped to `environments: [production]` then
+matches nothing, and denies nothing. The re-test measured a rule going DENY to
+ALLOW that way.
+
+The registration is gone rather than moved. The old note here argued it sat at
+import so `build_server()` would not re-register a constant; that answered the
+wrong question, since re-registering costs nothing and registering at all costs a
+sibling its rules. vmware-debug has no target config and no connection, so
+`resolve_environment`'s documented default — unlabeled, matching no
+environment-scoped rule — is the honest answer.
+
+**`case_plan(max_steps=...)` now reaches the planner.** The MCP tool declared the
+parameter and called `api.plan()` without it, so every plan came back at 6 steps
+however many were asked for, while the ops layer has always honoured the cap and
+a storage case has fourteen reachable tools. The result's own note ended with
+"pass a larger max_steps to see them" — advice to do the one thing that could not
+work. Values below 1 are now refused rather than obeyed: `[:0]` returns an empty
+plan, which reads as "nothing left to fetch", and `[:-3]` silently drops the last
+three steps. The default now comes from one constant instead of being typed out
+at three layers.
+
+**Symptom classification reads the event's own identifier.** `normalize_event`
+has always preserved `event_type` / `eventTypeId` in `fields`, and the classifier
+read only the prose. Modern vSphere sends most events as `EventEx`, where the
+message is generic boilerplate ("Issue detected on esx01") and the whole identity
+is a string like `esx.problem.scsi.device.io.latency.high` — which names its
+subsystem outright. vmware-monitor hit this on real hardware and fixed it on its
+side; vmware-debug had the same defect on the receiving side. camelCase and
+punctuation are split so a two-word keyword can reach an identifier
+(`HostShutdownEvent` becomes `host shutdown`); nothing here decides a category,
+it only makes an existing keyword reachable.
+
+**On the unclassified share: measured, explained, and not inflated.** Against
+pyVmomi's registry of all 427 vSphere event types the taxonomy reads 124 and
+misses 303, and the misses are not subsystems it lacks. They are events whose
+subsystem already has a category, spelled the way a server records a fact rather
+than the way an operator describes a symptom: `VmPoweredOnEvent` against "power
+on", `HostCnxFailedTimeoutEvent` against "connection lost", `DasHostFailedEvent`
+against "high availability", `VmMigratedEvent` against "vmotion". No keywords were
+added. Sixty more phrases would close today's list and lose on the next vSphere
+release, which is what a hand-maintained vocabulary does — so the taxonomy is
+unchanged, the finding is recorded as a regression test with the corpus and the
+named examples, and a test fails if the phrase list is later padded.
+
+Reading the identifier is worth exactly one type out of 427 on this corpus,
+because for a classic event the message and the class name say the same words.
+That number is pinned too, so no coverage claim can be borrowed from it. The
+value is on `EventEx`, which a list of class names cannot represent.
+
+What did change is the advice. The coverage note told the reader that unmatched
+events might "name a subsystem this taxonomy does not know" and to go find that
+subsystem's read tools — a false premise followed by a wasted call. It now names
+the actual mechanism, says to pass `event_type`, and says to force the category
+with `case_plan(category=...)` when you already believe you know it.
+
+The re-test also reported a missing `causal_chains` key "which the docs imply".
+No document in this repository promises one, and `incident_timeline`'s RETURNS
+list is accurate. Rather than invent a key or simply reply that the claim is
+wrong, the checkable form of the concern is now a test: whatever the docstring
+lists, the tool returns, and whatever the tool returns, the docstring lists.
+
+
 ## v1.11.1 — the schema an agent reads now carries the descriptions
 
 Parameter descriptions reach the JSON schema for the first time. An MCP client

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "vmware-debug"
-version = "1.11.1"
+version = "1.11.3"
 description = "VMware diagnostic brain — read-only incident triage, log/event correlation, and root-cause routing across the VMware skill family"
 readme = "README.md"
 license = "MIT"
@@ -21,7 +21,7 @@ dependencies = [
     "typer>=0.12,<1.0",
     "rich>=13.0,<15.0",
     "mcp[cli]>=1.10,<2.0",
-    "vmware-policy>=1.10.0,<2.0",
+    "vmware-policy>=1.12.0,<2.0",
     # Imported directly by ops/cases/grading.py for the rules file. It has
     # always arrived transitively via vmware-policy; a package should
     # declare what it imports rather than rely on a dependency's dependency.

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/server.json

@@ -7,12 +7,12 @@
     "url": "https://github.com/vmware-skills/VMware-Debug",
     "source": "github"
   },
-  "version": "1.11.1",
+  "version": "1.11.3",
   "packages": [
     {
       "registryType": "pypi",
       "identifier": "vmware-debug",
-      "version": "1.11.1",
+      "version": "1.11.3",
       "runtimeHint": "uvx",
       "packageArguments": [
         {

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/skills/vmware-debug/SKILL.md

@@ -133,6 +133,9 @@ The four writes go to `$OPS_HOME` (default `~/.vmware/cases/`) and nowhere else.
 **Event envelope** (input to `incident_timeline`): `{ts, source, severity, entity, text, fields}`.
 See `references/event-envelope.md`. The agent normalises each source's events into this
 shape; debug stays source-agnostic and has no dependency on the other packages.
+Keep each event's `event_type` in `fields` — the classifier matches it as well as
+the message, and on a modern `EventEx` it is the only thing that says what the
+event was.
 
 ## The Investigation Ledger
 

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/skills/vmware-debug/references/event-envelope.md

@@ -14,7 +14,8 @@ runtime dependency** on the other packages (no version lockstep, no heavy instal
   "severity": "error",
   "entity":   "vm-web01",
   "text":     "Device naa.600... performance has deteriorated",
-  "fields":   { "host": "esxi-03", "datastore": "ds1" }
+  "fields":   { "event_type": "esx.problem.scsi.device.io.latency.high",
+                "host": "esxi-03", "datastore": "ds1" }
 }
 ```
 
@@ -24,8 +25,23 @@ runtime dependency** on the other packages (no version lockstep, no heavy instal
 | `source` | string | `monitor` \| `aria` \| `loginsight` \| `nsx` \| `nsx-security` \| `storage` \| ... The catalogue in `rules/evidence_sources.yaml` spells the same skills `vmware-monitor`, `vmware-aria`, `vmware-log-insight`. Both spellings are understood wherever a skill is named — `case_readiness(available_skills=...)`, and the grader's count of independent sources, which treats two spellings of one skill as one source. |
 | `severity` | string | Free text; normalised to `critical`/`error`/`warning`/`info`/`unknown`. |
 | `entity` | string | The object the event is about (VM/host/datastore). May be empty. |
-| `text` | string | Human-readable message — this is what the symptom classifier matches on. |
-| `fields` | object | Any source-specific extras; preserved, never dropped. |
+| `text` | string | Human-readable message. Matched by the symptom classifier. |
+| `fields` | object | Any source-specific extras; preserved, never dropped. `event_type` / `eventTypeId` is matched by the classifier too — see below. |
+
+### `fields.event_type` is worth passing
+
+The classifier matches the identifier as well as the prose, with camelCase and
+dots split so a two-word keyword can reach it (`HostShutdownEvent` → `host
+shutdown`, `esx.problem.cpu.ready` → `cpu ready`).
+
+For a classic vCenter event this changes almost nothing — `VmMigratedEvent` and
+its message say the same words. It matters for `EventEx`, which is how modern
+vSphere emits most events: the message is generic boilerplate ("Issue detected on
+esx01") and the whole identity is in `eventTypeId`. Drop that field and a storage
+incident arrives as an unreadable event; keep it and it classifies as storage.
+
+`vmware-monitor`'s `get_events` returns it as `event_type`; passing the row
+through unchanged is enough.
 
 The normaliser is tolerant of common field-name variants (e.g. `timestamp`,
 `createTime`, `startTimeUTC` for `ts`; `criticality`, `level` for `severity`;

vmware_debug-1.11.3/tests/__init__.py

@@ -0,0 +1,9 @@
+"""Test package.
+
+``tests/eval/`` and ``tests/eval/regression/`` were already packages while this
+file was missing, so ``from tests.eval.regression._vsphere_event_vocabulary
+import ...`` resolved only where the namespace-package fallback happened to
+work. It did not on Windows, and the whole suite -- 398 tests -- failed at
+collection. The other repos that use cross-module test imports all carry this
+file; this one is the half-built package.
+"""

{vmware_debug-1.11.1 → vmware_debug-1.11.3}/tests/eval/capability/_family.py

@@ -11,31 +11,34 @@ from __future__ import annotations
 
 FAMILY_TOOLS: dict[str, frozenset[str]] = {
     'vmware-aiops': frozenset({
-        'acknowledge_vcenter_alarm', 'attach_iso_to_vm', 'batch_clone_vms',
+        'acknowledge_vcenter_alarm', 'add_host_vmk', 'attach_iso_to_vm', 'batch_clone_vms',
         'batch_deploy_from_spec', 'batch_linked_clone_vms', 'browse_datastore',
         'cluster_add_host', 'cluster_configure', 'cluster_create', 'cluster_delete',
         'cluster_health_summary', 'cluster_info', 'cluster_remove_host',
-        'convert_vm_to_template', 'cross_vcenter_attention',
-        'datastore_investigation_bundle', 'deploy_linked_clone', 'deploy_vm_from_ova',
-        'deploy_vm_from_template', 'host_investigation_bundle', 'list_vcenter_alarms',
-        'reset_vcenter_alarm', 'scan_datastore_images', 'vm_apply_plan', 'vm_cancel_ttl',
-        'vm_clean_slate', 'vm_clone', 'vm_create', 'vm_create_plan', 'vm_create_snapshot',
-        'vm_delete', 'vm_delete_snapshot', 'vm_guest_download', 'vm_guest_exec',
-        'vm_guest_exec_output', 'vm_guest_provision', 'vm_guest_upload',
+        'convert_vm_to_template', 'create_drs_rule', 'create_dvs_portgroup',
+        'cross_vcenter_attention', 'datastore_investigation_bundle', 'delete_drs_rule',
+        'deploy_linked_clone', 'deploy_vm_from_ova', 'deploy_vm_from_template',
+        'host_investigation_bundle', 'list_drs_rules', 'list_dvs_portgroups',
+        'list_host_vmks', 'list_vcenter_alarms', 'remove_host_vmk', 'reset_vcenter_alarm',
+        'scan_datastore_images', 'set_drs_rule_enabled', 'set_vmk_service', 'vm_apply_plan',
+        'vm_cancel_ttl', 'vm_clean_slate', 'vm_clone', 'vm_create', 'vm_create_plan',
+        'vm_create_snapshot', 'vm_delete', 'vm_delete_snapshot', 'vm_guest_download',
+        'vm_guest_exec', 'vm_guest_exec_output', 'vm_guest_provision', 'vm_guest_upload',
         'vm_investigation_bundle', 'vm_list_plans', 'vm_list_snapshots', 'vm_list_ttl',
         'vm_migrate', 'vm_power_off', 'vm_power_on', 'vm_reconfigure', 'vm_revert_snapshot',
-        'vm_rollback_plan', 'vm_set_ttl', 'vm_task_status',
+        'vm_rollback_plan', 'vm_set_ttl', 'vm_task_status', 'vmk_ping',
     }),
     'vmware-aria': frozenset({
         'acknowledge_alert', 'cancel_alert', 'create_alert_definition',
-        'delete_alert_definition', 'delete_report', 'generate_report', 'get_alert',
-        'get_aria_health', 'get_capacity_overview', 'get_remaining_capacity', 'get_report',
-        'get_resource', 'get_resource_health', 'get_resource_metrics',
-        'get_resource_riskbadge', 'get_time_remaining', 'get_top_consumers',
-        'investigate_alert', 'list_alert_definitions', 'list_alerts', 'list_anomalies',
-        'list_collector_groups', 'list_report_definitions', 'list_reports',
-        'list_resources', 'list_rightsizing_recommendations', 'list_symptom_definitions',
-        'set_alert_definition_state',
+        'delete_alert_definition', 'delete_report', 'findings_list',
+        'fleet_certificate_list', 'fleet_domain_list', 'fleet_password_account_list',
+        'generate_report', 'get_alert', 'get_aria_health', 'get_capacity_overview',
+        'get_remaining_capacity', 'get_report', 'get_resource', 'get_resource_health',
+        'get_resource_metrics', 'get_resource_riskbadge', 'get_time_remaining',
+        'get_top_consumers', 'investigate_alert', 'list_alert_definitions', 'list_alerts',
+        'list_anomalies', 'list_collector_groups', 'list_report_definitions',
+        'list_reports', 'list_resources', 'list_rightsizing_recommendations',
+        'list_symptom_definitions', 'promql_query', 'set_alert_definition_state',
     }),
     'vmware-avi': frozenset({
         'ako_amko_status', 'ako_clusters', 'ako_config_diff', 'ako_config_show',
@@ -47,11 +50,15 @@ FAMILY_TOOLS: dict[str, frozenset[str]] = {
         'vs_status', 'vs_toggle',
     }),
     'vmware-debug': frozenset({
-        'incident_timeline', 'list_symptom_categories',
+        'case_close', 'case_get', 'case_grade', 'case_hypotheses', 'case_knowledge',
+        'case_list', 'case_open', 'case_plan', 'case_readiness', 'case_record_gap',
+        'case_submit_evidence', 'case_timeline', 'incident_timeline',
+        'list_symptom_categories',
     }),
     'vmware-harden': frozenset({
-        'get_baseline_rules', 'get_remediation', 'list_baselines', 'list_drift_events',
-        'list_violations', 'scan_target',
+        'describe_stig_content_sync', 'get_baseline_rules', 'get_remediation',
+        'list_baselines', 'list_drift_events', 'list_stig_controls', 'list_violations',
+        'scan_target',
     }),
     'vmware-log-insight': frozenset({
         'alert_get', 'alert_history', 'alert_list', 'log_aggregate', 'log_fields',
@@ -59,12 +66,14 @@ FAMILY_TOOLS: dict[str, frozenset[str]] = {
     }),
     'vmware-monitor': frozenset({
         'active_sessions', 'active_tasks', 'certificate_status', 'cluster_health_summary',
-        'cross_vcenter_attention', 'datastore_capacity', 'datastore_investigation_bundle',
-        'get_alarms', 'get_events', 'get_host_sensors', 'get_host_services',
-        'host_investigation_bundle', 'host_log_scan', 'host_performance', 'license_status',
+        'cluster_last_apply_result', 'cluster_patch_compliance', 'cross_vcenter_attention',
+        'datastore_capacity', 'datastore_investigation_bundle', 'get_alarms', 'get_events',
+        'get_host_sensors', 'get_host_services', 'host_investigation_bundle',
+        'host_log_scan', 'host_memory_tiering', 'host_performance', 'license_status',
         'list_all_clusters', 'list_all_datastores', 'list_all_networks', 'list_esxi_hosts',
         'list_virtual_machines', 'ntp_status', 'resource_pool_usage', 'snapshot_aging',
-        'vm_info', 'vm_investigation_bundle', 'vm_list_snapshots', 'vm_performance',
+        'vcenter_deployment_size', 'vm_info', 'vm_investigation_bundle',
+        'vm_list_snapshots', 'vm_performance',
     }),
     'vmware-nsx': frozenset({
         'configure_tier0_bgp', 'create_ip_pool', 'create_nat_rule', 'create_segment',
@@ -82,9 +91,9 @@ FAMILY_TOOLS: dict[str, frozenset[str]] = {
         'apply_vm_tag', 'create_dfw_policy', 'create_dfw_rule', 'create_group',
         'delete_dfw_policy', 'delete_dfw_rule', 'delete_group', 'get_dfw_policy',
         'get_dfw_rule_stats', 'get_group', 'get_idps_status', 'get_traceflow_result',
-        'list_dfw_policies', 'list_dfw_rules', 'list_groups', 'list_idps_profiles',
-        'list_vm_tags', 'remove_vm_tag', 'run_traceflow', 'update_dfw_policy',
-        'update_dfw_rule',
+        'list_dfw_exclusions', 'list_dfw_policies', 'list_dfw_rules', 'list_groups',
+        'list_idps_profiles', 'list_vm_tags', 'remove_vm_tag', 'run_traceflow',
+        'update_dfw_policy', 'update_dfw_rule',
     }),
     'vmware-pilot': frozenset({
         'approve', 'cancel_workflow', 'confirm_draft', 'create_workflow', 'design_workflow',
@@ -95,7 +104,7 @@ FAMILY_TOOLS: dict[str, frozenset[str]] = {
         'browse_datastore', 'list_all_datastores', 'list_cached_images',
         'scan_datastore_images', 'storage_iscsi_add_target', 'storage_iscsi_enable',
         'storage_iscsi_remove_target', 'storage_iscsi_status', 'storage_rescan',
-        'vsan_capacity', 'vsan_health',
+        'vsan_capacity', 'vsan_efficiency', 'vsan_health',
     }),
     'vmware-vks': frozenset({
         'check_vks_compatibility', 'create_namespace', 'create_tkc_cluster',
@@ -103,22 +112,24 @@ FAMILY_TOOLS: dict[str, frozenset[str]] = {
         'get_supervisor_kubeconfig', 'get_supervisor_status', 'get_tkc_available_versions',
         'get_tkc_cluster', 'get_tkc_kubeconfig', 'list_namespace_storage_usage',
         'list_namespaces', 'list_supervisor_storage_policies', 'list_tkc_clusters',
-        'list_vm_classes', 'scale_tkc_cluster', 'update_namespace', 'upgrade_tkc_cluster',
+        'list_vm_classes', 'list_vm_groups', 'list_vm_network_interfaces',
+        'list_vm_snapshots', 'scale_tkc_cluster', 'update_namespace', 'upgrade_tkc_cluster',
     }),
 }
 
 FAMILY_COMMANDS: dict[str, frozenset[str]] = {
     'vmware-aiops': frozenset({
         'alarm acknowledge', 'alarm list', 'alarm reset', 'attention', 'cluster add-host',
-        'cluster configure', 'cluster create', 'cluster delete', 'cluster info',
-        'cluster remove-host', 'daemon start', 'daemon status', 'daemon stop',
-        'datastore browse', 'datastore scan-images', 'deploy batch', 'deploy batch-clone',
-        'deploy iso', 'deploy linked-clone', 'deploy mark-template', 'deploy ova',
-        'deploy template', 'doctor', 'hub status', 'init', 'investigate datastore',
-        'investigate host', 'investigate vm', 'mcp', 'mcp-config generate',
-        'mcp-config install', 'mcp-config list', 'plan list', 'scan now', 'summary',
-        'vm cancel-ttl', 'vm clean-slate', 'vm clone', 'vm create', 'vm delete',
-        'vm guest-download', 'vm guest-exec', 'vm guest-upload', 'vm list-ttl',
+        'cluster configure', 'cluster create', 'cluster delete', 'cluster drs-rule-create',
+        'cluster drs-rule-delete', 'cluster drs-rule-set', 'cluster drs-rules',
+        'cluster info', 'cluster remove-host', 'daemon start', 'daemon status',
+        'daemon stop', 'datastore browse', 'datastore scan-images', 'deploy batch',
+        'deploy batch-clone', 'deploy iso', 'deploy linked-clone', 'deploy mark-template',
+        'deploy ova', 'deploy template', 'doctor', 'hub status', 'init',
+        'investigate datastore', 'investigate host', 'investigate vm', 'mcp',
+        'mcp-config generate', 'mcp-config install', 'mcp-config list', 'plan list',
+        'scan now', 'summary', 'vm cancel-ttl', 'vm clean-slate', 'vm clone', 'vm create',
+        'vm delete', 'vm guest-download', 'vm guest-exec', 'vm guest-upload', 'vm list-ttl',
         'vm migrate', 'vm power-off', 'vm power-on', 'vm reconfigure', 'vm set-ttl',
         'vm snapshot-create', 'vm snapshot-delete', 'vm snapshot-list',
         'vm snapshot-revert', 'vm task-status',
@@ -126,10 +137,11 @@ FAMILY_COMMANDS: dict[str, frozenset[str]] = {
     'vmware-aria': frozenset({
         'alert acknowledge', 'alert cancel', 'alert definitions', 'alert get', 'alert list',
         'anomaly list', 'anomaly risk', 'capacity overview', 'capacity remaining',
-        'capacity rightsizing', 'capacity time-remaining', 'doctor', 'health collectors',
-        'health status', 'init', 'mcp', 'report definitions', 'report delete',
-        'report generate', 'report get', 'report list', 'resource get', 'resource health',
-        'resource list', 'resource metrics', 'resource top',
+        'capacity rightsizing', 'capacity time-remaining', 'doctor', 'fleet certificates',
+        'fleet domains', 'fleet findings', 'fleet passwords', 'fleet promql',
+        'health collectors', 'health status', 'init', 'mcp', 'report definitions',
+        'report delete', 'report generate', 'report get', 'report list', 'resource get',
+        'resource health', 'resource list', 'resource metrics', 'resource top',
     }),
     'vmware-avi': frozenset({
         'ako amko-status', 'ako clusters', 'ako config-diff', 'ako config-show',
@@ -145,7 +157,8 @@ FAMILY_COMMANDS: dict[str, frozenset[str]] = {
     }),
     'vmware-harden': frozenset({
         'advise', 'apply', 'baseline import', 'baseline list', 'baseline validate',
-        'doctor', 'drift', 'mcp', 'report', 'scan', 'web',
+        'doctor', 'drift', 'mcp', 'report', 'scan', 'stig controls', 'stig sync-info',
+        'web',
     }),
     'vmware-log-insight': frozenset({
         'aggregate', 'alert get', 'alert history', 'alert list', 'doctor', 'fields', 'mcp',
@@ -153,13 +166,14 @@ FAMILY_COMMANDS: dict[str, frozenset[str]] = {
     }),
     'vmware-monitor': frozenset({
         'activity sessions', 'activity tasks', 'attention', 'capacity datastores',
-        'capacity pools', 'daemon start', 'daemon status', 'daemon stop', 'doctor',
-        'health alarms', 'health events', 'health sensors', 'health services',
+        'capacity pools', 'daemon start', 'daemon status', 'daemon stop', 'deployment-size',
+        'doctor', 'health alarms', 'health events', 'health sensors', 'health services',
         'infra certs', 'infra licenses', 'infra ntp', 'init', 'inventory clusters',
         'inventory datastores', 'inventory hosts', 'inventory networks', 'inventory vms',
         'investigate datastore', 'investigate host', 'investigate vm', 'mcp',
-        'mcp-config generate', 'mcp-config list', 'perf hosts', 'perf vms', 'scan now',
-        'snapshots aging', 'summary', 'vm info', 'vm snapshot-list',
+        'mcp-config generate', 'mcp-config list', 'memory tiering', 'patch compliance',
+        'patch last-apply', 'perf hosts', 'perf vms', 'scan now', 'snapshots aging',
+        'summary', 'vm info', 'vm snapshot-list',
     }),
     'vmware-nsx': frozenset({
         'doctor', 'gateway configure-tier0-bgp', 'gateway create-tier1',
@@ -188,14 +202,15 @@ FAMILY_COMMANDS: dict[str, frozenset[str]] = {
     'vmware-storage': frozenset({
         'datastore browse', 'datastore list', 'datastore scan-images', 'doctor', 'init',
         'iscsi add-target', 'iscsi enable', 'iscsi remove-target', 'iscsi rescan',
-        'iscsi status', 'mcp', 'vsan capacity', 'vsan health',
+        'iscsi status', 'mcp', 'vsan capacity', 'vsan efficiency', 'vsan health',
     }),
     'vmware-vks': frozenset({
         'check', 'harbor', 'init', 'kubeconfig get', 'kubeconfig supervisor', 'mcp',
         'namespace create', 'namespace delete', 'namespace get', 'namespace list',
         'namespace update', 'namespace vm-classes', 'preflight-auth', 'storage',
         'supervisor status', 'supervisor storage-policies', 'tkc create', 'tkc delete',
-        'tkc get', 'tkc list', 'tkc scale', 'tkc upgrade', 'tkc versions',
+        'tkc get', 'tkc list', 'tkc scale', 'tkc upgrade', 'tkc versions', 'vm groups',
+        'vm nics', 'vm snapshots',
     }),
 }