5 Commits

Include renames

Author	SHA1	Message	Date
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	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