[followup] vcpus/mem_mb=0 burns full create budget (permanence gap)

open   by a73x

Labels: backlog

[claude 2026-07-04] DEF-2 review (fdbd4d98): permanence marker covers the disk guards, but vcpus:0 / mem_mb:0 fail inside cloud-hypervisor at Boot with an unmarked error and still burn all 3 attempts across ticks — same shape, one field over. Mark buildArgs/Boot validation errors permanentf() to close it. Low priority; the values are also floored at the API so this needs a direct-agent path.