5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	136fa8b2a8	Say how a declared bucket and module stream are created, so the grants part makes the same stream the controller does ... BucketStreamConfig and ModuleStreamConfig are the stream configurations the controller's CreateOrUpdateKeyValue (BucketConfig) and StreamConfigFor assert at its start, pure, for the grants part's create of a bucket or stream a manifest declares and the bus lacks. A log already has Log.Config. Never used for an update. Issue: 1790	2026-10-26 09:04:43 +01:00
jschoubben	8f6ee2fd18	Let the grants part create the streams manifests declare, so a new module state no longer waits for a controller start ... The copied bus composer grants mesh-grants' principal $JS.API.STREAM.CREATE.<stream> and $JS.API.STREAM.INFO.<stream> for each bucket (KV_<module>_<state>), log (LOG_<module>_<log>) and module stream a placed module's manifest declares, each by its own name: NATS wildcards are whole tokens, so nothing narrower than an exact name exists and nothing wider is granted. The writers table lets the grants part create, never update or delete. The operator allowed this one grant on 2026-10-26 08:54, beside the memberships grant of 22:31 (ADR 0547 clause 1 and 5). The expected lists were written again by the controller's own internal/broker with the same change (mesh-control fix/1790-grants-create-buckets); a fixture now places mesh-grants beside the builder's state, log and stream. Issue: 1790	2026-10-26 09:01:32 +01:00
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