Archived
The controller is to be declared as a Go bundle run by a process instead of an image (novox/hq issue 213, ADR 0188 §1, §3). The composer could not express that honestly yet: - a module declaring tools had every bundle served by the node's runtime, so the controller's own binary would have been launched a second time as an MCP child; a bundle one of the module's resources runs is now served only when it says `loads` - a module's accounts went after the mesh-computed files, so secrets owned by the account a process runs as were refused on the first apply; a module's `user` resources now go first - `prepares` derived its step only from a container; a process is now prepared by the same program with `prepare` as a run-once process - a process may say what it `replaces` (a resource of its module it no longer declares), prefixed as the host records it, so the host keeps the old one running until the process is (needs mesh-host's `replaces`) This lands before the controller's manifest uses any of it: the running controller composes its own declaration, so the code that fills the new shape must be live first.