ProxmoxMCP-Plus v0.6.7

Changes

• Add optional purge=false to delete_vm and delete_container. Explicitly
  setting purge=true also removes HA resources and backup/replication references
  through the native Proxmox delete endpoint. Preserve the selected option across
  in-process and persisted retries, including after a job-store restart. Older
  retry recipes without the field retain their previous behavior.
• Fix forced deletion of HA-managed guests: after the stop task succeeds, poll
  the guest's current status for up to 60 seconds and submit deletion only after
  it reports stopped. A timeout or failed status read prevents the delete
  request; the earlier stop request can still complete later.
• Preserve existing positional approval arguments for Python callers. The new
  purge argument is keyword-only, preventing an approval token from accidentally
  enabling additional cleanup. Existing target, read-only, and approval policies
  continue to apply.
• Update Monty, its client, and runtime to 1.2.0 with a synchronized universal
  hashed lock. Keep the existing Code Mode restrictions and execution limits.
  Add a dependency-lock regression check and installed-dependency checks to CI
  and Docker builds.
• Update certifi to 2026.10.19 to address
  GHSA-6q48-6c7w-9gw2.
  Upgrade SHA-pinned setup-python to 7.1.0 and the PyPI publishing action to
  1.14.3; allow Paramiko 5 typing stubs.
• Add contribution guidelines, Contributor Covenant 2.1, bug/feature/accessibility
  issue forms, a PR template, and an accessibility statement. Align documented
  validation commands with the current CI requirements.

These changes integrate #185
through #186,
#187, and dependency PRs
#188,
#189,
#190, and
#191 through
#192.

Upgrade

Install proxmox-mcp-plus==0.6.7 or update the container image to
ghcr.io/rekklesna/proxmoxmcp-plus:0.6.7, then restart workers and reconnect MCP
clients to refresh tool schemas. Recreate Docker containers after pulling the new
image. Keep the existing configuration and persistent jobs volume.

No database schema migration or new configuration setting is required. Existing
deletion calls keep purge=false. For direct Python calls, opt in explicitly with
purge=True; named MCP arguments use purge=true. Proxmox removes guest ACLs
during normal deletion regardless of this flag. See the
API reference for deletion parameters.

Deleting a guest and purging its references cannot be undone by downgrading the
software. Restore guest data from backups and restore cluster references
separately if recovery is needed. A software rollback to 0.6.6 loses the new purge
option and HA stop-state wait, and returns to the older dependency set.

Validation

The integrated changes passed 1,433 tests with 2 optional skips on both Python
3.11 and 3.12 in CI, including complete runtime statement coverage and complete
branch coverage of the nine critical modules. The release PR runs these gates
again, alongside container health/authentication, Windows contracts, dependency
audits, package checks, secret scanning, and CodeQL. No live Proxmox guest is
stopped or deleted as part of release validation.