vm-provisioning.md: name provision-vm after the nexus rename #67

Merged
vnprc merged 1 commit from agent/rename-host-scripts-note into master 2026-09-26 22:19:22 +01:00
Member

Memory text only. The host-key rotation gotcha in vm-provisioning.md names provision-vm, the command that exists after the nexus rename, instead of the retired provision-vm-from-host. Nothing on a running machine changes. If it is wrong, revert the one commit.

Follow-up to the nexus rename, which has already landed and reached the host through the deploy pin. Refs allod/nexus#66

Risk

R0. One command name in a topic file.

Validation

  • .hooks/memory-budget --worktree: passed.
  • grep -rn from-host over the repo: no matches.
Memory text only. The host-key rotation gotcha in `vm-provisioning.md` names `provision-vm`, the command that exists after the nexus rename, instead of the retired `provision-vm-from-host`. Nothing on a running machine changes. If it is wrong, revert the one commit. Follow-up to the nexus rename, which has already landed and reached the host through the deploy pin. Refs allod/nexus#66 ## Risk R0. One command name in a topic file. ## Validation - `.hooks/memory-budget --worktree`: passed. - `grep -rn from-host` over the repo: no matches.
The nexus host command provision-vm-from-host is now provision-vm and the
old name is gone, so the host-key rotation gotcha names the command that
exists.

Refs allod/nexus#66
vnprc approved these changes 2026-09-26 22:19:16 +01:00
vnprc merged commit e1ea6bf25a into master 2026-09-26 22:19:22 +01:00
vnprc deleted branch agent/rename-host-scripts-note 2026-09-26 22:19:22 +01:00
Sign in to join this conversation.
No description provided.