Enhance documentation and validation for VM lifecycle and network management; add tests for legacy cleanup and address validation.

DEVELOPER.md

@@ -272,6 +272,9 @@ mode. There is no persisted boolean asserting that a policy is enforced.
 - Missing `disk` and process start time remain absent. Legacy `disk_ready` is
   inferred only for running/stopped records with a recorded private disk;
   start still validates the path, file, and provisioning state.
+- Legacy records own their canonical runtime directory independently of whether
+  they had a private disk. Deletion never removes the shared rootfs template;
+  explicit `runtime_owned=False` on a new interrupted creation stays authoritative.
 - Records created before credential provisioning default to username `root`
   and password `null`; UVM does not apply a password retroactively.
 - `next_mac_index` is reconstructed from older locally administered MACs when
@@ -384,7 +387,8 @@ merely because its PID was never persisted or its socket has not appeared.
 
 ### Policy and Bulk Operations
 
-`set_ports()` persists the new allowlist with `operation=policy` before
+`set_ports()` takes a frozen registry ID, not a reusable name/IP; the CLI resolves
+the user's identifier before confirmation. It persists the new allowlist with `operation=policy` before
 applying it. Live updates apply atomically and retain conntrack; cleanly
 stopped edits are metadata-only. On apply/readback failure, preserve the new
 intent, attempt link-down/quarantine, and leave a failed pending record. Never