5 Commits

Include renames

Author	SHA1	Message	Date
jochen	424a7eec82	Keep what discovery heard when a round hears nothing, and fetch only changed announcements (issue 554) ... A round in which no PING reached the laptop's console within the 750 ms window was taken as the mesh's answer that nothing is there, and replaced the index: every seat and module call was refused for five seconds at a time. Discovery now waits up to its patience for a first PING, a round that heard nothing is not kept, a runtime not heard this round is resolved from what it announced last (said with its age), and a round that misses runtimes is logged once. A PING carries a digest of what the instance serves, so an unchanged announcement is not pulled again every round (some 880 kB to the laptop).	2026-10-12 13:56:50 +02:00
jochen	fce3dcb98d	Say a timeout is not a failure, and where the controller keeps the answer (hq issue 265)	2026-10-06 01:14:59 +02:00
jochen	8405e32efc	The console says an account was refused only when the bus refused it ... "authorization" alone matched a tool's own answer mentioning the word — the runtime refusing a state value with an Authorization header read as "this account may not call".	2026-10-04 11:31:42 +02:00
jochen	7722668220	Every runtime announces what it serves in the NATS services protocol; the console discovers by asking the bus (hq ADR 0197) ... The Go runtime answers $SRV.PING, $SRV.INFO and $SRV.STATS (and per name and id) in the io.nats.micro.v1 format with what it serves at the moment it is asked: one service per runtime process, since the bus admits one reply per request from each responder, and one endpoint per tool per subject, its metadata saying module, seat, scope, machine, description, schema and whether the module is interchangeable. Serving is unchanged. The console gathers one $SRV.INFO request's answers instead of asking the catalogue's roster and each module's tools, and reads the controller's records as JSON for what should have answered: an assignment with tools that did not announce is named, a module without tools never is. The text parsers of node list and module list are gone. Packages share the test bus: go test -p 1.	2026-10-03 22:14:16 +02:00
jochen	e45389f75a	node-tools in Go: the node's runtime, launch-only, wire-compatible with the TypeScript (hq ADR 0193) ... The runtime knows no language, so nothing ties it to Node.js. This ports its serve mode — the pinned bus connection and patient connect, following memberships, launching every served bundle over MCP on stdio with its own environment, a child's emit published as its module, each tool, the tools verb and seat verbs served where the mesh issued them, and the console on loopback — to one static binary. Same subjects, request and reply bodies, event headers and MCP answers. The TypeScript stays: it is still the runtime inside the per-module containers until WP4c. Tests run against a real bus and share the TypeScript fixtures.	2026-10-03 21:21:52 +02:00