Add clear host deletion controls with workload safeguards

docs/native-hosts.md

@@ -70,6 +70,9 @@ explicit installer `--reenroll` when local credentials already exist.
 
 API outline:
 
+- `GET /api/hosts/:id`: host details, operation history and deletion blockers.
+- `DELETE /api/hosts/:id`: administrator removes an unused host and revokes access;
+  returns `409` if servers, reservations or unresolved delivered operations remain.
 - `POST /api/agent/enroll`: consume enrollment token and return host credentials.
 - `POST /api/agent/heartbeat`: authenticated inventory, current operation and caches.
 - `GET /api/agent/operations`: deliver/reconcile durable operation IDs.
@@ -123,6 +126,18 @@ may still join until an eligible empty moment; draining does not kick them.
 **Disable** holds agent dispatch. Neither mode, controller downtime nor agent
 communication loss stops unrelated running containers.
 
+Administrators can choose **Delete host** on a host card or at the top of its
+detail page. The confirmation lists anything that must be resolved first:
+registered servers, reserved ports, or operations already sent to the agent.
+Drain the host or remove its servers, then let outstanding operations reconcile.
+An unused host can be deleted before enrollment or while offline.
+
+Deleting a host removes it from the controller's host list and deployment
+choices, revokes its credentials, and invalidates unused installer links.
+Queued commands that have never been sent to the agent are cancelled. Operation
+history and published libraries are retained; the agent and game files remain on
+the machine. Adding the machine again requires a new host enrollment.
+
 ## Libraries and ports
 
 Choose the actual game folder, not its parent, a ZIP archive or the Plutonium