4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	35ff67bda0	Design 47's last milestones: the keeper, self-check, healers, hand-acts, provisioner, vault, artifact sweep, disk readings, credential forms (issues 774, 1952, 1953, 1954, 1955) ... One commit with exactly the tree of the reviewed head 35b4509c0a, on main 12c2574c9d, so two compiled programs added and removed on the branch leave no trace in history (issue 1577).	2026-10-30 02:21:51 +01:00
jschoubben	b4e90e5fce	Run the bus from its pinned upstream image with the snapshot program and the entrypoint mounted, and write and rehearse the way there and back (issues 1640, 1641, 1642, ADR 0480 clauses 1-3, 5, 6, 11)	2026-10-22 09:55:03 +02:00
jochen	0275c2eeac	nats: run 2.11.17, which hands a consumer with several filters every message (hq issue 266) ... On 2.10.29 such a consumer was moved past a message now and then without handing it over; the controller's events consumer has seven filters, and a merge on the stream never reached it. The test reproduces the skip on 2.10.29 and keeps the image's release equal to the server it tests.	2026-10-06 01:29:20 +02:00
jochen	f53fc0929b	The bus's own tools: server, connections, subscriptions, streams, backlog, buckets, users, user_can ... A Go bundle the runtime launches beside the nats module's server. It reads the server's monitoring API and the composed user list — never a password hash — and changes nothing. Reached directly when the endpoint is published, through the container otherwise: its configuration binds monitoring to the container's own loopback, so the published port answers nothing today.	2026-10-04 16:51:33 +02:00