14 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	0184e2a5b8	Watch the have bucket only where the node's grant allows, so a node composing itself is not refused by the bus (issue 1126) ... The fold's watch of every have key ('>') was refused (permissions violation on CONSUMER.CREATE KV_node-engine_have), and every self-composing agent stopped after the seed. The composer now watches '*.node' (records) and '<node>.>' (its own haves), as buscompose grants a node; the shadow watches '<node>.>' too. The selfcompose tests check every watch and get against PermissionsFor(KindNode), and the agent's integration tests run the agent as the node under that grant.	2026-10-27 09:27:54 +01:00
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
jschoubben	1803d25c3a	Watch afresh and read from nothing at each shadow run, so a candidate deleted while it was down is not answered and no earlier watch stays open (issue 1126, review of L2b round 2)	2026-10-27 02:48:54 +01:00
jschoubben	d56c576e9a	Begin the shadow composer again with a backoff when an input cannot be watched yet, and pin mesh-sdk's fixed head, so a node answers candidates for the whole link (issue 1126, review of L2b round 1)	2026-10-27 02:44:39 +01:00
jschoubben	fb0cdabe25	Answer every placement candidate in shadow in the node's own key, applying nothing, so a placement change is checked by the nodes it places before it merges (issue 1126, ADR 0559 §4)	2026-10-27 02:26:07 +01:00
jschoubben	0474a2a3cb	Keep the node's own composition's sealed values in its key and read a policy within the agent's context, so a restart applies nothing again (issue 1126)	2026-10-27 02:21:36 +01:00
jschoubben	4476e58080	Review of L2, round 2: a refusal at the first compose after a start keeps what the module's have said runs (1); each have of a self-composing node carries the values its composition holds sealed, and the composer reuses them after a restart, so a rotated secret moves no composition at a restart (2); pin mesh-sdk dd9d9d5 (issue 1126, ADR 0547 §3)	2026-10-26 20:23:16 +01:00
jschoubben	58de6aa10a	Review of L2: a node that cannot compose says so in each wanted module's have, failed, while it keeps what it runs (H2); the composer keeps the box the node runs when it opens to the vault's value, so neither the switch nor a restart moves a composition (H1); pin mesh-sdk 3968849, whose node asks the vault only for a module declaring a secret (H8's failure) (issue 1126)	2026-10-26 20:09:40 +01:00
jschoubben	bb46a6ad0f	The node composes again when the vault says a secret changed, so a rotated secret or credential reaches it at once (issue 1126, ADR 0547 §2)	2026-10-26 19:26:25 +01:00
jschoubben	1e38c42646	The node's composer asks the vault for the pair credentials its composition reads, as consumer and provider, sealed to its key (issue 1126, ADR 0550 §5)	2026-10-26 19:21:22 +01:00
jschoubben	1241ee7041	Pin mesh-sdk 4d5f430: the node's wants say it composes them (Self) (issue 1126)	2026-10-26 19:14:38 +01:00
jschoubben	2dc384d641	The node's composer asks the vault's own for its modules' secrets sealed to its key, and keeps a value first had while its generation stands; two agent tests folded to hold the count (issue 1126, ADR 0550 §5)	2026-10-26 19:05:12 +01:00
jschoubben	02d9d7b053	The node composes its own modules once the catalogue places it: one composer per node drains a mark set by any input's change, the agent applies what it composed when it differs, and a record move waits for a yes (issue 1126, ADR 0547 §2, §3)	2026-10-26 18:44:58 +01:00