5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	6e78203959	Compose no placed user from the node-engine's manifest, so the tool runner never becomes a second writer of the engine's state (issue 774) ... Second meeting of the engine-state-in-runner kind (mesh-host_acts this morning, mesh-host_health now); thorough: the runner never carries the engine module. One predicate, Composed, keeps the engine out of the placed loop (no user, no process, nothing carried); CarriedByRunner is the one test of what the runner carries. The engine's grants stay the node account's, its state created through Records.Engine.	2026-10-30 16:30:27 +01:00
jschoubben	2323ba19db	The node-engine's declared state acts: created by the grants part as a placed module's, its manifest placed on every node, and written by each node's engine under its own keys alone (issue 774, ADR 0563 §2, §3)	2026-10-28 21:54:04 +01:00
jschoubben	d515c71e1c	process: a bucket missing at a part's start is bound when the bus says it was created, keeping what was written meanwhile; buscompose grants each principal the creation of the buckets it may bind (issue 1790) ... Since the grants part creates a manifest's buckets after a delivery (ADR 0547), a module restarted by that delivery can open a new state before it exists; OptionalBucket answered nil and the part never looked again (mesh-delivery's checker and builder, state hearing, 2026-10-26). AwaitBucket binds on the server's STREAM.CREATED advisory, or at the next use, and writes the latest value kept per key. The copied composer's agreement test leaves that one row out: the controller's list is no longer loaded since the take-over.	2026-10-26 15:11:00 +01:00
jschoubben	175a5567b8	The bus node follows the grants part's sealed user list, and only the grants part reads the vault's hashes (ADR 0547 clauses 7, 9; issue 1945) ... The grants part writes its list as an object of its own bucket, sealed to the bus node's key, and names it in user-list.sealed; the node-engine of the node holding mesh-broker is granted that one key and an object by name, the grants part its bucket (the controller's copy carries the same grants, byte for byte, golden regenerated there). A state may name its readers (announce, NamedReaders): mesh-vault.bus-accounts is read by mesh-grants alone.	2026-10-26 11:53:11 +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