Proxion v0.11.0

Added

• Convert to template: a stopped VM or container can be turned into a template from the object
  header's "More" menu or the inventory tree's context menu, behind a typed-VMID confirmation
  (the change is permanent). POST /api/actions/guest/:node/:type/:vmid/template needs a signed-in
  session and VM.Allocate on the guest, and refuses a running/paused guest (guest-running) or one
  that is already a template (already-template).
• Create container wizard: General, Template, Disks, CPU, Memory, Network, DNS and Confirm steps
  (opened from the node context menu or the top bar's Create menu), validated per step, ending in
  one new allow-listed POST /api/actions/guest/:node/lxc/create that follows the task and opens
  the new container. Needs a signed-in session, VM.Allocate on the new CT ID and
  Datastore.AllocateSpace on the root disk's storage (409 vmid-taken for an id in use). The root
  password is never logged, echoed or stored; SSH public keys travel newline-separated, as PVE's
  ssh-public-keys expects.
• Create VM wizard: eight steps (General, OS, System, Disks, CPU, Memory, Network, Confirm) that
  mirror PVE's, opened from the top bar's Create menu or a node's context menu. One request to a
  new allow-listed route, POST /api/actions/guest/:node/qemu/create, composes the whole VM (ISO
  or no media, q35/OVMF with an EFI disk, optional TPM 2.0, one disk, CPU, memory, one NIC, boot
  order) from a strict typed body, then Proxion follows the task and opens the new VM. Needs a
  signed-in session, VM.Allocate on the new VMID and Datastore.AllocateSpace on every storage a
  new volume goes on (Datastore.Audit or Datastore.AllocateSpace on the ISO's storage); a VMID
  already in use is refused with 409 before PVE is called. The shared service token stays
  read-only.

Changed

• An invalid PROXION_NOTIFY_* / PROXION_PUBLIC_URL value no longer crash-loops the server at
  boot: notifications are disabled with one startup warning (Notifications disabled: <key and allowed values>, never echoing webhook/SMTP URLs or tokens), GET /api/notify/status reports
  the error, and the Preferences page shows it and disables "Send test notification". Core
  settings (PVE URL, token, session secret, ports, TLS pin, agents) still fail hard.