Drop route-proxy's stale notes of a contract module of its own, which the move made a package

The go.mod comment and the contract package's comment still described a separate Go module with its own tags. Issue 1126.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

modules/route-proxy/contract/contract.go

@@ -3,10 +3,9 @@
 // row 34; the operator, 2026-10-31: "the route-proxy should define its own contract for the seat (with the message
 // contracts of course) which other modules can use").
 //
-// **Published by the repository that holds route-proxy, as its own Go module**, versioned by tags of the form
-// `modules/route-proxy/contract/vX.Y.Z`, the subdirectory form Go's module system expects, the same way mesh-sdk is
-// published (`go/vX.Y.Z`). A module that asks a route, reads what the proxy serves or hears its events imports this
-// package; nothing imports the repository. Standard library only, so a consumer takes nothing else with it.
+// **A package of the route-proxy module**, imported as `route-proxy/contract`: standard library only, built from the
+// same tree as the proxy, so the two never drift. No other module imports it today; when one must, it moves into the
+// networking domain's package (research 081).
 //
 // **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 seat

modules/route-proxy/go.mod

@@ -16,5 +16,3 @@ require (
 	golang.org/x/sys v0.48.0 // indirect
 	golang.org/x/text v0.42.0 // indirect
 )
-
-// The contract is this repository's own Go module, beside this one (contract/): built from the tree, not fetched.