4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	759a7bff12	Keep route-proxy's contract a package of its own module, not a second module behind a replace ... The group's check failed at go mod verify: the build module's workspace carries one module, so the replace of ./contract named a go.mod it never placed; and ADR 0573 clause 1 refuses a path into another tree. Nothing outside route-proxy imports the contract today; when one must, it moves into the networking domain's package (research 081). Issue 1126. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 13:55:07 +01:00
jschoubben	d2c5057fdf	Say that the seat mesh-provisioner composes route-proxy's plans, since the controller ended ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 12:23:47 +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
jschoubben	bf395f88ee	Publish route-proxy's contract as a Go module of its own: the route a consumer asks, its schema, the events the proxy says, what it keeps on the bus and its tools' arguments, so other modules use the contract by its version and the provisioner carries a route unread (issue 774, research 072 row 34)	2026-10-31 09:44:00 +01:00