Both were facts about this driver that netOrk kept in hardcoded driver-name sets, each duplicated across a file pair (netork#113). The driver is the right place for them: everything runs over the PVE REST API, and a node reboots through a full init sequence plus storage checks before it is worth polling.