2 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	a74f9db508	Test route-proxy without composing: its manifest's own facts and a plan entry's port, since the composition left mesh-sdk ... The composer's proof that the manifest composes, and that a port is the placement's, is the node-engine's now (ADR 0593 §7). Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:06:37 +01:00
jschoubben	6f038810fd	Move route-proxy out of the controller's repository, which is archived with the controller ... route-proxy provides `route` to five modules and lived in novox/mesh-controller, archived once the controller is removed (issue 1126). Its history comes along (git filter-repo of modules/route-proxy and its earlier home examples/route-proxy). Its contract's Go module path names this repository, and route-proxy builds the contract from its own tree through a replace, so no tag is needed before the first build. The two manifest tests that held its public ACME account and mounted program lived in the controller's internal/ownmanifest; they move beside the module. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 11:45:17 +01:00