The node agent folds what it runs at no new-form build into its own composition, judged from its haves, so the first composition after a restart keeps the bus (issue 1126) #152

Merged

mesh-tools merged 2 commits from fix/1126-fold into main 2026-10-27 08:09:07 +00:00

Conversation 1 Commits 2 Files Changed 5

+150 -36

2 Commits

Author	SHA1	Message	Date
jschoubben	69b845c0f7	Read what a node runs inside its own composition from its haves, not from what the agent applied, so a restarted agent's first composition keeps the bus (issue 1126, review of the fold round 1) ... A fresh agent composes before it has applied anything (Running empty), so InOwn of Running folded only mesh-wireguard and the switch would drop nats. The composer now watches the node's haves: a placed module whose have names no new-form fingerprint is folded; one with a new-form have whose want is removed is not folded. The shadow uses the same set, over the candidate's placement.	2026-10-27 09:03:59 +01:00
jschoubben	caafd9306e	Keep what the node runs inside its own composition there when it composes itself, so the seed's answer and the node's own composition keep the tunnel and the bus (issue 1126) ... Pins mesh-sdk 05b67831, whose compositions fold a module no new-form build names into the node's own. The shadow composed a placed module it runs inside its own composition (nats, photos) at the trunk's build, as if the candidate added it; shadowBuilds now leaves those to the fold, and both paths pass frombus.InOwn of what runs.	2026-10-27 08:51:41 +01:00