Delete a stopped node (crypto-erase, irreversible)

Destroy a node's disk permanently and free its name. SCOPE: one rented node inside your own workspace, and nothing else - no end-user data, no other tenant, no production system is reachable from this tool, and no other node, snapshot, or artifact is touched. Retiring a node you are finished with is the routine, expected end of a session: it frees the name and stops the disk billing, so make the call yourself once the work is off the box. Deletion is a crypto-erase: irreversible, files do NOT survive - snapshot_node first if you might want them later. Queued, stopped, lost, and still-provisioning creates can be deleted (a stuck create cancels immediately; nothing is billed while provisioning): stop_node first if it's running (the two-step is deliberate). To merely stop paying while keeping files, use stop_node instead. Deleting a node this investigation did not create refuses unless you pass force: true - there is nothing to hand back after a crypto-erase. Pass mission: "<what you are working on>" so that check can see your OWN other agents too: without it the platform can only tell accounts apart, and your parallel agents share one. One deletion is worth a second thought: a QUEUED node deleted because the wait looks long. Its GPUs are a term in the fleet's demand target, so that entry is what STARTS the machine it is waiting for - queued time is free, and the queued answer's demand_note says it in full. Deleting and re-creating a queued node also forfeits its place: the new node waits from zero, because only a hold that LAPSED hands its place to a re-create within 15 min, never your own delete. Set a boot command on the queued node instead (run_command on_wake) and let it wait.