5 Commits

Include renames

Author	SHA1	Message	Date
jochen	e6d5ead50d	nats: a WebSocket listener for a page in a browser, from the overlay only (hq research 036) ... The bus has no way for a browser to reach it (research 036, gap G1). The server now also listens over WebSocket on 4223: published from the mesh like 4222, so the machine's filter admits it from the overlay and nothing else; no TLS, acceptable only because the overlay is WireGuard and a browser cannot be made to trust the mesh's own certificate; compression on. The user a page connects as is the read-only view the controller composes (mesh-controller, `bus view-credential`). A test parses the declared configuration with the server itself, holds the opening, the published port and the listener to one port, and connects a client over WebSocket. The bus module's policy is `record`: this reaches the bus's machine only through the planned step a person starts (`bus upgrade`), as every bus change does.	2026-10-10 16:00:52 +02:00
jochen	ea69e795ab	Read the tested nats release from the server itself ... The build seat's test binary listed no dependencies, so the check that the image and the tests run one release failed on a release that matched.	2026-10-08 18:07:29 +02:00
jochen	0063cc2ad1	Say who opens and closes connections to the bus, and why each closed (hq issue 327) ... The connection total rose by hundreds an hour while the open count stayed flat, and nothing could say which clients those were.	2026-10-08 17:54:01 +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