Begin MACOS_VM_NATIVE_AGENT_Markdown

Nucleic-Session: 8BBA8B40-FA38-4556-8B3A-7A2DFD4C87B2
Co-authored-by: Nucleic <[email protected]>

docs/MACOS_VM.md

@@ -592,10 +592,11 @@ responsible process), which is the supported shape — but keep this in mind if
 5. **SSH `sendSignal` targets the local `ssh` client.** A killed one-shot signals the host-side
    `ssh` process; the remote command may **orphan** and keep running in the guest until VM teardown.
    Acceptable because the clone is disposable, but worth noting. 🟡
-6. **vsock as a future transport.** SSH-over-NAT is used because the framework has no Mac-guest exec
-   API today; a future revision could move guest interaction onto **vsock** (as the container control
-   plane did — see [VSOCK_CONTROL_PLANE](VSOCK_CONTROL_PLANE.md)) to drop the NAT/DHCP dependency and
-   the local-`ssh`-client indirection entirely. 🟡
+6. **vsock as a future transport (partly done).** Computer-use now rides **vsock** when the native
+   agent is baked in ([MACOS_VM_NATIVE_AGENT](MACOS_VM_NATIVE_AGENT.md)); `mac_vm_exec` command
+   execution still uses SSH-over-NAT (the framework has no Mac-guest exec API). A future revision
+   could add an `exec` op to the agent to drop the NAT/DHCP dependency and the local-`ssh`-client
+   indirection entirely. 🟡
 7. **Residual shared-*source* collision under nvrsion.** Each session gets its own VM, so the
    per-VM isolation removes the shared-host-toolchain thrash and the shared-DerivedData corruption
    (`xcodebuild` writes DerivedData to a VM-local `~/Library/Developer/Xcode/DerivedData`, so two