update

docs/client-api.md

@@ -98,6 +98,7 @@ V2 clients register a locally generated installation identity:
 {
   "schema_version": 1,
   "installation_id": "123e4567-e89b-42d3-a456-426614174000",
+  "hostname": "pve01",
   "credential": "64-lowercase-hexadecimal-characters",
   "proxmenu_version": "2026.7.26-7",
   "git_commit": "40-lowercase-hexadecimal-characters",
@@ -134,8 +135,10 @@ Accepted events are `run_started`, `run_completed`, `run_failed`, and
 `upgraded`. Events are best-effort and are sent only while TA-ProxMenu is
 running; there is no resident monitoring service.
 
-The fleet API deliberately does not accept or store hostnames, machine IDs,
-MAC addresses, usernames, customer names, VM/container inventory, deployment
-tokens, or command output. The portal shows random installation IDs, first and
-last activity, verification status, software/platform versions, cluster mode,
-and the latest structured result.
+The fleet API stores the reported hostname as a limited operational identifier.
+It deliberately does not accept or store machine IDs, MAC addresses, usernames,
+VM/container inventory, deployment tokens, credentials, or command output. The
+portal shows hostname, random installation ID, first and last activity,
+verification status, software/platform versions, cluster mode, and the latest
+structured result. A record becomes verified only after the same installation
+ID is included in a successful deployment-code exchange.