Archived
Once the runtime module is registered, a module serving tools from a container built on the runtime's image is refused at registration — as written, including every rebuild of the thirty-odd modules already in that shape, from the day the runtime arrives until WP4 onward moves each one. That would stop the catalogue's whole pipeline to make a point the record already makes. Now a module already registered in that shape — judged from the manifest the catalogue holds and what its newest build stood on, the same two things a new registration is judged by — is rebuilt as before; a module new to the catalogue in that shape, or one that had moved to a bundle and comes back, is refused naming the record.