mesh-provisioner keys provisions from a consumer's wanted and newest builds but writes the wanted build's plan alone, so a requirement the newest build adds was never bound. Each key now carries its plan entry, and a key ahead of its want says in its why that no plan names it yet and its provider binds it from the entry (issue 1126 review 1). Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL