ProxmoxMCP-Plus v0.6.5

Changes

• Integrate #181: add download_template for HTTPS LXC archives through the native Proxmox download-url API with content=vztmpl and TLS verification enabled. Validate identifiers, archive names and optional digests; require observed enabled/active template storage and reject an existing destination volume.
• Apply target-specific high-risk approval, read-only and client-grant policy to the new tool. Accept approval metadata without forwarding it to Proxmox.
• Report submission separately from completion, preserve UPIDs if local tracking fails, and classify uncertain responses as unsuccessful/non-retryable. Do not attach a blind retry recipe. Use the native task DELETE endpoint for cancellation.
• Integrate #178: permit Ruff 0.17 while explicitly preserving the existing E4/E7/E9/F lint baseline and Python 3.11 target. Review adoption of new rule families independently from a dependency update.
• Add a pull-request AMD64 container build/health job so Dockerfile updates are exercised before merging, without publishing a PR image.
• Integrate #179: update the pinned official Python 3.11 slim base-image digest; retain Linux AMD64/ARM64 publication and native ARM runtime checks.

Upgrade and operating limits

Install proxmox-mcp-plus==0.6.5 or ghcr.io/rekklesna/proxmoxmcp-plus:0.6.5, restart workers and reconnect MCP clients. No state/database migration is introduced. Add download_template to any custom command_policy.high_risk_operations list. Default high-risk mode is audit-only; configure enforcement and approval tokens when required.

Use trusted publishers and preferably SHA-256/SHA-512 digests. Proxmox performs the download from its own network, so HTTPS validation does not prevent access to internal endpoints or redirects. Proxmox enforces storage/network permissions, TLS, checksum verification and task failures.

Inventory checks do not reserve disk space or the filename, and cannot prevent an external concurrent upload. Downloads can fail asynchronously. Poll the task and verify list_templates before using the resulting volume with create_container. After SUBMISSION_UNCERTAIN, inspect tasks and storage before another call. retry_job deliberately does not resubmit template downloads.

Validation uses automated tests, simulated API/protocol calls, package installation and container smoke checks. No production Proxmox download or guest operation is performed.