4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	087e9266d1	Test the capability gate, the sweep's mark re-read and the lock use of a send and of the sweep, each failing under its mutation (issues 1696, 1697; review round 2)	2026-10-21 16:28:24 +02:00
jochen	909062e729	Deliver a dead letter again only where it is received, and never stop serving for the notices ... A dead letter was let go as delivered even when its consumer did not filter its again subject; seat asks needed a grant over every seat's queue and left the original stuck; a notices bind failure stopped the controller (review).	2026-10-08 18:32:58 +02:00
jschoubben	aecac5bda2	One bus: the AMQP transport is gone from the controller ... The mesh runs on the seat's bus alone (novox/hq ADR 0131, design 28 task 5.5). The old transport's consume loop, build request, tool ask, management API and account scoping are deleted, and the bus switch with them; the controller connects to the broker seat and to nothing else. The store-window tests keep their assertions on a bus-less fake, and the tests that only made sense for the old transport's in-memory holding go with it.	2026-09-28 03:36:16 +02:00
jschoubben	3907ea0db0	The control plane serves and pushes on the bus it is told to ... The seams were there and nothing chose a side: serve, push, ask and build all opened the old bus's connection and declared over its channel, whatever MESH_BUS_NATS said. So the switch moved every host and left the control plane unable to follow — "this control plane has no MESH_BROKER_AMQP" with the new bus named and standing (2026-09-28). That was task 4.3 of design 28, still open. One place now decides: connectLink reads the switch, refuses both buses named at once, raises the new bus's streams and this controller's consumers when it is handed the inventory, and opens the link over whichever bus it is on. Every caller that sent a declaration or asked a tool through the old channel goes through the server's bus instead, which the new transport has and the channel is not. OverNats is that outbound: a declaration is a JetStream publish into the node's own subject, an event is announced on the subject its name derives to, a tool is request and reply on the module's tool subject.	2026-09-28 01:29:44 +02:00