Add the four Proxmox hypervisors to the inventory

pfi-pve (Anaheim), nh3-pve (NH), esh-pve + esh-pve-nas (ESH home lab) now
have servers/<host>/ entries with ssh-target files, README stubs, and
first snapshots. Register all four via add-host.sh + ssh-copy-id; SSH
auth is root@<name> with key-based access.

Fix a resolver bug in the three workspace scripts: previously, when a
hostname resolved via /etc/hosts, resolve_target returned the bare name
and ssh dropped the user prefix stored in ssh-target (connecting as the
wrong user). Now ssh-target wins whenever it's present, since it can
carry user@ or port info that /etc/hosts + ssh_config cannot. Falls back
to the dir name only when no ssh-target file exists.

CLAUDE.md and README.md split the fleet table into Docker hosts vs
hypervisors with an explicit placement rule: don't deploy Docker stacks
on PVE hosts; capture host-level detail with server_inspect.sh, use
Proxmox-native tooling (qm list, pvesh, zpool) for VM/storage audits.

servers/pfi-pve/README.md

@@ -0,0 +1,35 @@
+# pfi-pve
+
+Proxmox VE hypervisor for the Anaheim colo (`pve.phasefinal.com`). Hosts every VM in the PFI-ANA cluster.
+
+## Network
+
+- **LAN IP:** 10.250.250.31
+- **FQDN:** `pve.phasefinal.com`
+- **Web UI:** `https://10.250.250.31:8006`
+- **SSH:** `root@pfi-pve` (key auth; `ssh-target` file uses the hostname)
+
+## Hardware
+
+- **CPU:** Intel Xeon Silver 4310 @ 2.10 GHz
+- **RAM:** 188 GB
+- **Kernel:** `6.8.12-8-pve` (Proxmox 8.x)
+- **Storage:** local `pve-root` at 65G (49% used) + `pve` LVM pool for VM disks
+
+## What it runs
+
+The VMs in [`docs/pfi/proxmox-vms.md`](../../docs/pfi/proxmox-vms.md) live here — VM 100 (PFI-ANA-TRUENAS, now Debian NFS/SMB), VM 101 (DC), VM 102 (PFI-ANA-Docker = `ana-docker`), 103–111 (Mongo, Postgres, Tailscale, Pteradactyl, Webhost, tacticalrmm, etc.).
+
+`ana-ml2` (`10.250.50.54`) is a separate bare-metal box, not on this hypervisor.
+
+## Refresh state
+
+```bash
+scripts/refresh-server-info.sh pfi-pve
+```
+
+The snapshot captures host/hardware/filesystem/network/ports but **not** VM-level detail (`server_inspect.sh` targets Docker hosts). Running `qm list`, `pvesh get /cluster/resources`, and `zpool list -v` manually is the current way to audit VMs and storage. A Proxmox-flavored inspect script is a future improvement.
+
+## Placement rule
+
+This is a hypervisor, not a target for Docker stacks. Add new workloads by standing up VMs here (or on ana-docker / ana-ml2, whichever fits) rather than deploying containers directly on the PVE host.