refactor(cloud-iac): rename control-plane VM eliza-cp-<env>-<n> → eliza-<n>

The shorter prefix matches the data-plane convention (eliza-core-<hex>)
and supports the in-place rename of the legacy prod VM (milady → eliza-1)
via Hetzner's PUT /servers/{id}. Environment moves to a label
(`environment = production|staging`) so the Hetzner Console can filter
without bloating every SSH command.

Also drops the inline import walkthrough from the README — it's a
one-shot adoption op that lives in operator scratch space, not in repo
docs that drift over time.

Author: standujar

packages/cloud-infra/cloud/terraform/hetzner/ARCHITECTURE.md

@@ -9,7 +9,7 @@ split so we stop treating manually-created VMs as "infrastructure-by-prayer".
 ┌──────────────────────────────────────────────────────────────┐
 │  Tier 1 — Control plane (static, 1-2 VMs, Terraform)        │
 │                                                              │
-│   eliza-cp-production-1   (Hetzner cpx21, fsn1)             │
+│   eliza-1   (Hetzner cpx21, fsn1)             │
 │     ├── eliza-provisioning-worker  (systemd, queue consumer)│
 │     ├── eliza-agent-router         (systemd, HTTP routing)  │
 │     ├── headscale                  (VPN mesh)               │
@@ -64,7 +64,7 @@ to coordinate it.
 
 | Layer | Prefix | Example | Where it's set |
 |---|---|---|---|
-| Control plane VM | `eliza-cp-<env>-<n>` | `eliza-cp-production-1` | Terraform `var.environment` |
+| Control plane VM | `eliza-<n>` | `eliza-1` | Terraform `hcloud_server.control_plane` |
 | Data plane node (NEW) | `eliza-core-<hex>` | `eliza-core-38ea87b1` | [`generateNodeId()`](../../../../cloud-shared/src/lib/services/containers/node-autoscaler.ts) |
 | Data plane node (LEGACY) | `milady-core-<n>` | `milady-core-1` | DEPRECATED — see [Legacy migration](#legacy-milady-core-migration) |
 

packages/cloud-infra/cloud/terraform/hetzner/control-plane/README.md

@@ -53,24 +53,15 @@ scp packages/cloud-shared/.env.local root@<vm-ip>:/opt/eliza/cloud/.env.local
 
 ## Adopt the existing production VM into Terraform
 
-The current prod manager VM (`89.167.63.246`, hostname `milady`) was
-created by-hand via `packages/scripts/cloud/admin/bootstrap-provisioning-worker-host.mjs`
-on May 7th. To bring it under Terraform without recreating it:
-
-```bash
-# 1. Look up the Hetzner Cloud server ID:
-hcloud server list  # find the one with IP 89.167.63.246
-
-# 2. Import the existing resource into state:
-terraform init -backend-config=backend-production.hcl
-terraform import \
-  -var-file=tfvars/production.tfvars \
-  'hcloud_server.control_plane["1"]' \
-  <SERVER_ID>
-
-# 3. Run `terraform plan` and adjust variables until the diff is empty.
-#    Common drift: labels, ssh_keys (manually added during initial setup).
-```
+The current prod manager VM (`89.167.63.246`, historical hostname
+`milady`) was created by hand in May 2026. To bring it under Terraform
+without recreating it, look up the Hetzner Cloud server ID
+(`hcloud server list`), then `terraform import 'hcloud_server.control_plane["1"]' <id>`
+plus a `terraform import` for each existing `hcloud_ssh_key`. The first
+plan after import shows the in-place rename `milady → eliza-1`, the new
+labels, and the Cloudflare DNS record creation; `user_data` and `image`
+diffs are suppressed by `lifecycle { ignore_changes }`. One-shot — never
+re-run.
 
 ## What this module does NOT manage (yet)
 

packages/cloud-infra/cloud/terraform/hetzner/control-plane/main.tf

@@ -15,15 +15,20 @@ resource "hcloud_ssh_key" "operators" {
   # inserted/reordered in `var.ssh_public_keys`.
   for_each = { for key in var.ssh_public_keys : substr(sha256(key), 0, 12) => key }
 
-  name       = "eliza-cp-${var.environment}-op-${each.key}"
+  name       = "eliza-op-${var.environment}-${each.key}"
   public_key = each.value
   labels     = local.common_labels
 }
 
 resource "hcloud_server" "control_plane" {
   for_each = toset([for i in range(var.control_plane_count) : tostring(i + 1)])
 
-  name        = "eliza-cp-${var.environment}-${each.value}"
+  # Naming: `eliza-${index}` — short, matches the data-plane convention
+  # `eliza-core-<hex>` and supports the in-place rename from the legacy
+  # `milady` VM. The environment lives in labels, not the hostname, so the
+  # prod/staging distinction shows up in the Hetzner Console filter
+  # without bloating the hostname every operator types into SSH.
+  name        = "eliza-${each.value}"
   location    = var.hcloud_location
   server_type = var.hcloud_server_type
   image       = var.hcloud_image
@@ -33,7 +38,7 @@ resource "hcloud_server" "control_plane" {
   })
 
   user_data = templatefile("${path.module}/cloud-init/bootstrap.yaml.tftpl", {
-    hostname          = "eliza-cp-${var.environment}-${each.value}"
+    hostname          = "eliza-${each.value}"
     deploy_branch     = var.deploy_branch
     operator_ssh_keys = var.ssh_public_keys
   })

packages/cloud-infra/cloud/terraform/hetzner/control-plane/variables.tf

@@ -47,9 +47,9 @@ variable "cloudflare_zone_id" {
 }
 
 variable "control_plane_hostname_prefix" {
-  description = "DNS subdomain prefix. Final record: <prefix>-<environment>-<n>.elizacloud.ai"
+  description = "DNS subdomain prefix. Final record: <prefix>-<environment>-<n>.elizacloud.ai (e.g. eliza-production-1.elizacloud.ai)"
   type        = string
-  default     = "cp"
+  default     = "eliza"
 }
 
 variable "deploy_branch" {