jschoubben
9239177efd
A node-wide hold while any module's composition was unpublished meant one placed module whose newest build never completes blocked every retirement on its node for good, said only as a line of the pass. The incomplete first read is already covered by the load gate, and an unpublished module's own plan and keys are already kept as held. So the node-wide hold goes; a removed consumer retires beside an unpublished module, and a module held unpublished for more than two passes in a row is said on provisioner_health with its build. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL