mesh-vault takes what runs of a node's own secret through move-in, on the node's ask (issue 1126 C4, group fix/1126-seed-same) #535

Merged

mesh-tools merged 6 commits from fix/1126-seed-same into main 2026-10-28 09:46:29 +00:00

Conversation 1 Commits 6 Files Changed 12

+698 -14

6 Commits

Author	SHA1	Message	Date
jschoubben	0974d1a57d	mesh-vault's own_drift row carries the id as a node runs it, its module's name first, and the vault pins mesh-sdk 3028c7e (issue 1126, cause C4; review round 2)	2026-10-28 10:02:46 +01:00
jschoubben	a17356a162	Fill go.sum for mesh-sdk 1062b33, the group's head (issue 1126)	2026-10-28 09:53:34 +01:00
jschoubben	35ad58e6e2	mesh-vault pins the group's mesh-sdk head 1062b33 (issue 1126; go.sum is filled once that head is pushed)	2026-10-28 09:51:48 +01:00
jschoubben	da5da4f6f7	The vault takes what runs through move-in's replace_running, not a verb of its own, so no seat promises anything new (issue 1126, cause C4)	2026-10-28 09:48:14 +01:00
jschoubben	671a6a1f47	own-take-running has a person's switch, own_take_switch, kept in the vault's store (issue 1126, cause C4)	2026-10-28 09:39:16 +01:00
jschoubben	47ed384d97	The vault takes the value that runs on a machine over the one it was first handed, from that machine alone (issue 1126, cause C4) ... move-in never replaces a value the vault holds, so where the controller made an own secret anew after the move, the new value runs while the vault keeps the first. The verb own-take-running takes it from the node-engine of the machine it is for, keeps the replaced value as the previous generation, raises the generation and says own-replaced without a value; own_drift lists every own secret a node's shadow answer says another value of, mesh-wide. The module needs the mesh-sdk head of fix/1126-seed-same-own-resync (delivery.OwnValuesDiffer, the seat's verb).	2026-10-28 09:37:54 +01:00