Campaign Quartermaster v1.2.2

Campaign Quartermaster v1.2.2

Campaign Quartermaster v1.2.2 corrects the primary Proxmox VE bootstrap so an
eligible interactive host receives the guided blue whiptail wizard advertised
in v1.2.1.

Corrected Proxmox one-command install

Run this from the Proxmox VE host shell as root:

bash -c 'set -Eeuo pipefail; umask 077; tmp="$(mktemp -d)"; cleanup() { rm -rf -- "$tmp"; }; trap cleanup EXIT; base="https://github.com/Mptower/campaign-quartermaster/releases/download/v1.2.2"; for file in proxmox-install.sh proxmox-install.sh.sha256 proxmox-common.sh proxmox-common.sh.sha256; do curl --fail --show-error --silent --location --proto "=https" --proto-redir "=https" --tlsv1.2 --output "$tmp/$file" "$base/$file"; done; (cd "$tmp"; sha256sum --check --strict proxmox-install.sh.sha256 proxmox-common.sh.sha256); CQ_LIB_PATH="$tmp/proxmox-common.sh" bash "$tmp/proxmox-install.sh"'

The command downloads immutable v1.2.2 installer and helper assets plus both
SHA-256 sidecars into a private temporary directory. It verifies both scripts
with strict checksum checking before executing the installer, pins the verified
helper through CQ_LIB_PATH, and removes the temporary directory on success or
failure. curl writes payloads only to files and reports failures on stderr, so
download output cannot interfere with the wizard.

Unlike the legacy curl | bash path, the verified installer runs from a file and
inherits the invoking terminal's stdin/stdout. When whiptail, TERM, and the
TTY checks are suitable, the blue wizard remains eligible. Piped, explicit
environment, and CQ_NONINTERACTIVE=1 paths remain supported through their
existing validated plain-text or automation flows.

Validation scope

The exact command is syntax-checked and exercised with modeled release downloads,
real SHA-256 verification, TTY-preservation checks, checksum-failure blocking,
temporary-directory cleanup, and secret-leak assertions. Physical Proxmox
hardware validation was waived for this corrective release.

Upgrade

Back up state before upgrading. Docker users rerun the v1.2.2 installer.
Proxmox users run the v1.2.2 updater from the PVE host with CQ_CTID set to
their managed container.