6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9b01c94a9e	buildrun: the asker hears DEAD_LETTERS again on its next reconnect or ask, in the background, and says whether it hears; buscompose grants only what a pulled ordered consumer needs (issue 734, review round 1) ... An asker started before its grant was composed was refused once and stayed deaf until it started again, silently. DeadLetterHearing tries in the background and again on an event (Again: a reconnect, an ask waited for while deaf), and tells each change of Hearing so the module's health tool can say it. DeadLetterReads drops the flow control a pull consumer does not use and deletes one consumer by name.	2026-10-26 14:16:58 +01:00
jschoubben	e7f0dc612e	buscompose: a user of a seat pulled by kind reads its seat's dead letters, so an asker hears an ask given up (issue 734) ... A check ask given up during a bus reload left its try running for ever: the asker had no grant to learn that DEAD_LETTERS holds it. DeadLetterReads grants an ordered consumer on DEAD_LETTERS filtered to the seat stream's copies, and nothing else of the stream.	2026-10-26 13:51:35 +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