5 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	8d58afea6c	Broker tests read a consumer's pending count through pendingOf, which waits up to 10 s, wherever they expect a count after a publish (issue 1126) ... The server counts a consumer's pending after it acknowledges the publish, so a read at once failed the try of main on a loaded ace (TestAResetOfTheEventsConsumerLeavesTheMergesAndTheirConsumerAlone, 2026-10-26 22:24 UTC). Fixed for the kind, not the one test: all six reads of a positive count go through the package's own pendingOf, whose deadline was 1 s. Research 'The controller, NATS-native': none; this changes tests only, not a part of the controller.	2026-10-26 23:28:03 +01:00
jschoubben	a0c971cea9	Make a module's consumer from now and refuse a start word in consumes, so no part replays a week at its first start (issue 1279, ADR 0443)	2026-10-19 21:53:08 +02:00
jschoubben	14fe2ad736	Split the unit level from the integration level outside cmd, builder, link, catalogue, inventory; merge-check.sh times and bounds the unit level (issue 895)	2026-10-17 20:41:57 +02:00
jochen	743e6478a7	Remove a restricted stream's consumer when the bus refuses to narrow it, so its wider filters deliver nothing more (ADR 0363 §6, review of PR 338)	2026-10-14 22:05:47 +02:00
jochen	ee13e75bf3	Let a module declare a stream of its own and restrict who hears it by a trusted config value (hq issue 718, ADR 0363) ... mesh-mail's events must live on a stream of their own and reach only the modules the operator granted an account (ADR 0359 §2, §4). The controller now creates a module's declared stream, publishes its events on mesh.stream.<module>.event.<event>, and composes a consumer's durable consumer, filters and bus grants on a restricted stream only where its consumes asks and the provider's trusted value names it; a consumer that loses its grant has its consumer removed on the next assertion. Nothing changes while no manifest declares a stream.	2026-10-14 21:52:45 +02:00