novox/mesh-networking
10
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
92 Commits 3 Branches 0 Tags
4d1f9acae18ea7ab00f6491822ea0dbec9727489
Commit Graph
9 Commits
Author SHA1 Message Date
jschoubben 2f0b7c9741 Route-proxy and the overlay name the assigner's new places: the contracts' go/ path and the state assignments (issue 1966) 
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
 2026-11-05 22:00:49 +01:00
jschoubben db50239373 No client names the holder of the seat mesh-provisioner: each reader keeps its own constant, held to its manifest (ADR 0625 section 4, issue 1966) 
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
 2026-11-05 19:36:21 +01:00
jschoubben acaebc5ddf route-proxy: provisions and the provider come from the provisioner's client, not mesh-sdk (N-1, ADR 0634 §4; issue 1966) 
The requires of the two mesh-contracts modules carry a placeholder version the group's re-pin replaces.
 2026-11-05 14:09:12 +01:00
jschoubben 759a7bff12 Keep route-proxy's contract a package of its own module, not a second module behind a replace
mesh/delivery-group group feat/1126-removal rejected: composed together: the checker's verdict at the members' heads (6593d973ff2e): the composition
Details
mesh/delivery closed: the pull request closed unmerged
Details
mesh/check failed: the composition: route-proxy is defined twice, in novox/mesh-controller and novox/mesh-networking | 759a7bff129b on fe0392e05f62 | … 
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 fa56e38429 Serve route-proxy's routes through its own contract: decode each plan entry's opaque contribution with it, say each name served, withdrawn or refused on the bus, and take who is inside from the seat mesh-placement, since the membership went with the assignments stream (issue 774, research 072 rows 33 and 34) 2026-10-31 09:44:07 +01:00
jschoubben 373565c2f7 Serve route-proxy's routes from the seat mesh-provisioner's plans alone and drop its received routes file, since a route is a provision and the file is the deprecated path (issue 774, research 072 row 34; needs the mesh-sdk pin carrying plan entries' given and Conn.Read) 2026-10-31 09:24:53 +01:00
jschoubben d82f24b51a Bring build-agent and route-proxy in whole (issue 1019) 2026-10-17 18:15:33 +02:00