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
@@ -5,7 +5,7 @@ package main
 // name from the entry in this module's bucket, the one its machine's client fills its files from.
 //
 // **It composes nothing.** A route's public name is the label its consumer chose joined to the node's public domain,
-// which only the controller knows (the domain is placement), so the controller composes it and carries it in the
+// which only placement holds, so the seat mesh-provisioner composes it and carries it in the
 // consumer's plan entry (`names`); the helper copies it into the entry's values unchanged. There is no credential for
 // a route and nothing to make. The proxy itself serves the same plans' entries (cmd/route-proxy plans.go), the one
 // source of routes (issue 774, research 072 row 34).