3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9132b6a296	mesh-grants: take each user's hash from the vault's bus-accounts and say per user whether one is held, so take-over waits until every user has a credential ... ADR 0547 clause 9: the vault writes the hash of each bus account it holds into bus-accounts.<user>. The grants part watches that state (no timer), carries the hash with each shadow user in memory only, and its user-list tool says per user whether a hash is held and how its line would differ from the loaded one (same, adds, left out for want of a credential, loses its login); never the hash, since bcrypt salts make two hashes incomparable. Take-over names the users with no hash. Issue: 1945	2026-10-26 02:29:54 +01:00
jschoubben	1ff5049d03	mesh-grants publishes memberships on change; the user list, assertions and grants stay in shadow (issue 1945) ... Since release 6 nobody publishes memberships, so a module placed since cannot serve its seat or reach a new state (the operator, 2026-10-25 22:31). The part publishes each membership on the assignments stream only when it differs from the one last published, composes from the manifest the wanted build names, and says a refused publish and tries again at the next event. Pins mesh-sdk 881da7f, whose composer grants mesh-grants that publish.	2026-10-25 22:37:06 +01:00
jschoubben	998fe3a515	Add mesh-grants in shadow: compose the bus's user list, memberships and assertions from the bus and compare, writing only its own state (ADR 0547 clauses 5-8, issue 1945) ... The grants part must compose with the controller's own composer before it can take over the list; in shadow it proves the two agree, names every input the bus does not carry yet, and takes no effect. It claims no seat (mesh-sdk's seat list does not name mesh-grants for the running composer), serves module tools, and keeps running when a read or write is refused.	2026-10-25 22:27:47 +01:00