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/nh3-pve/README.md

@@ -0,0 +1,33 @@
+# nh3-pve
+
+Proxmox VE hypervisor for the NH3 site (`nh3-vmhost.phasefinal.com`).
+
+## Network
+
+- **LAN IP:** 10.100.250.60
+- **FQDN:** `nh3-vmhost.phasefinal.com`
+- **Web UI:** `https://10.100.250.60:8006`
+- **SSH:** `root@nh3-pve` (key auth)
+
+## Hardware
+
+- **CPU:** 13th Gen Intel Core i9-13900H
+- **RAM:** 62.5 GB
+- **Kernel:** `6.8.12-11-pve` (Proxmox 8.x)
+- **Storage:** mostly networked — `/mnt/pve/pfi-nh3-nas` (42 TB) mounted from the Synology at `10.100.50.50:/volume1/VMStorage`; ~27 TB used
+
+## What it runs
+
+`nh3-docker` (`10.100.50.40`) is a VM on this hypervisor. Other VMs (if any) aren't catalogued yet — run `qm list` on the host when you need the current inventory.
+
+## Refresh state
+
+```bash
+scripts/refresh-server-info.sh nh3-pve
+```
+
+Same Proxmox-inspect caveat as `pfi-pve`: snapshots capture host-level detail only. VM/LXC/storage enumeration needs the Proxmox tooling manually.
+
+## Placement rule
+
+Hypervisor. New NH-site workloads land here as VMs.