3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	b7b5c6ef27	The copied composer grants the grants part reading every membership, and its memberships are held to the controller's too (ADR 0547 §5, review of mesh-grants) ... The grants part reads each module's last membership before it publishes, so it needs the direct get on every membership subject, as the controller's composer now grants (fix/1945-mesh-grants-publishes-memberships). The equality test compares every membership the fixtures issue with the controller's MembershipFor, written by its own code.	2026-10-25 22:50:21 +01:00
jschoubben	881da7f599	The copied bus composer grants the grants part publishing memberships, as the controller's does (ADR 0547 §5) ... The same line as mesh-controller f67d1553; the fixtures name a mesh-grants module and the lists were written again by the controller's own composer on that branch, so the copy is held byte-equal to it.	2026-10-25 22:33:20 +01:00
jschoubben	b5f8604d03	Copy the controller's bus composer into mesh-sdk as buscompose, held byte for byte to the controller's lists (issue 1377, ADR 0547 §5) ... The grants part composes the bus's user list with the composer the controller uses (ADR 0547 §5), copied rather than moved: the controller is not changed and keeps its own until it loses the lease. Left out: the bus client, the broker's address from the environment and the client's two methods; the lease's two subjects are copied in. One table test holds the copy to four meshes' lists and the server golden, written by the controller's own internal/broker from the same fixtures (testdata/controller-user-lists.json).	2026-10-25 21:54:58 +01:00