d25c0ce64d
The DGX Sparks run DGX OS with a proprietary NVIDIA driver and firmware stack. No image in our pipeline restores it, so an install destroys the machine's software permanently -- and `labctl provision install` would happily do it. Machines carry an `onboard` classification and the `vendor_os` they must keep running. Both install entry points (the HTTP route and the labd command handler) refuse, naming the machine, what it runs, and pointing at `provision debug` instead. Rescue is deliberately never guarded: being unable to reinstall is exactly when you need a rescue shell. Classification is a fact about the machine, not a blocklist. When a DGX OS image joins the pipeline, teaching the installer about that vendor_os is what unblocks these boxes. It is keyed on DMI identity, with the two known Sparks also matched by MAC -- neither has DMI in bastion state today, so a DMI-only rule would fail open on exactly the machines this protects. Also refuses an OS/architecture combination with no netboot artifacts, which is Ubuntu on aarch64. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015nRFZXpKwUVE4SRSHw6GjF