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
parent 30cb63e29f
commit d2c5057fdf
7 changed files with 18 additions and 18 deletions
@@ -9,8 +9,8 @@
 // package; nothing imports the repository. Standard library only, so a consumer takes nothing else with it.
 //
 // **How a route travels.** A module that must be reachable requires `route` and says, in its manifest's
-// `contributes.route`, one Request, or several by local name; Schema is that object's JSON schema. The controller
-// composes each (its label joined to the node's domains into `name` and `internal-name`, its endpoint's port into
+// `contributes.route`, one Request, or several by local name; Schema is that object's JSON schema. The seat
+// mesh-provisioner composes each (its label joined to the node's domains into `name` and `internal-name`, its endpoint's port into
 // `port`) and the seat mesh-provisioner carries the result in the consumer's plan entry as an opaque payload
 // (mesh-sdk catalogue.PlanProvision.Contributed, in the generic catalogue.ContributedForm). Neither the seat nor its
 // client knows a field of a route: route-proxy decodes each contribution with DecodeRequest, and refuses, saying why