route-proxy from the provisioner's plans with its own contract; the controller forwards accounts to the vault (issue 774) #487

Merged

mesh-tools merged 6 commits from feat/072-moves into main 2026-10-31 10:31:07 +00:00

Conversation 1 Commits 6 Files Changed 36

+1397 -541

6 Commits

Author	SHA1	Message	Date
jschoubben	7a169eae76	Keep the controller on main's mesh-sdk pin and mint until the grants part takes over, so its impact stays small and no account is minted that the bus it loads refuses (issue 774) ... The controller is being removed, so its root module goes back to origin/main's mesh-sdk pin (2da0de7) and testdata/beside's capture; route-proxy keeps its own pins. Its one functional change stays the account issue: - Before the grants part's take-over (its key user-list.sealed not saying FollowGrants) the bus loads the controller's list, whose hashes come only from its store, so the controller mints as before and hands every account it mints, covered or not, to an installed vault at once: no account waits on a node reporting its hash. - From the take-over it forwards the issue to the vault's issue-account (d791052f) and mints nothing. And the controller no longer declares or asserts the ASSIGNMENTS stream, which the bus module's tools delete at the lease write and nothing may make again (research 072 row 33); the verified-sender re-issue stops once it is gone. Research 072 piece: the gap "vault mints after the lease", the minting piece moves to the vault from the take-over.	2026-10-31 10:37:13 +01:00
jschoubben	a07621d761	Pin route-proxy at the group's mesh-sdk head acbf80a and its contract at the published tag v0.1.0, so it builds and reads the contributed payload; refresh its manifest digest for the events its contract names (issue 774)	2026-10-31 10:27:05 +01:00
jschoubben	d791052f77	Forward module issue and an assignment's issue to the vault once one is installed, so the controller mints no bus account and none waits on a node reporting here (issue 774; research 072, the controller NATS-native: gap "vault mints after the lease", the minting piece moves to the vault)	2026-10-31 10:02:39 +01:00
jschoubben	22935b9202	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	efe745f2be	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
jschoubben	ff912d0972	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