Which containers survive a reboot is a flag, not a runbook

The box holds sixty containers. Twelve are production. The other forty-eight are branches, experiments, and last quarter's demos, and nobody wants all of them booting after a kernel update at 4am.

Each container has autostart, set with PATCH /api/v1/containers/{id} and {"autostart": true}. When the server reboots, finishes maintenance, or comes back from a power loss, the twelve start themselves. The forty-eight stay stopped, costing nothing on the flat-rate box until someone wants one and starts it.

The old runbook was a wiki page listing what to bring up, executed by whoever was awake. This one is a boolean on the thing itself, and the operator doesn't need to be awake, or exist.