Snapshots and forks

POST /v1/machines/{id}/snapshot saves memory and disk while leaving the source running. The computer briefly pauses while memory is written. POST /v1/snapshots/{id}/machines starts a new computer from a snapshot.

POST /v1/machines/{id}/fork with {"count":3} snapshots the source and starts copies. Count is 1 to 32 per request, within prepaid runway and capacity. Partial failures return the snapshot and the copies that did start. Keep those IDs; do not blindly repeat a fork.

GET /v1/snapshots lists snapshots. DELETE /v1/snapshots/{id} erases one. Snapshots and forks have their own state and keys.

Protected computers (prevent_cloning: true) refuse forks and starting copies from their snapshots. Keep and resume the original instead.