6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4f636b7080	Name no controller verb in hints and drop its handover and paging reads, since the controller ended (issue 1126 B19) ... Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 11:23:14 +01:00
jochen	c401bbff2d	Say what becomes of an event a handler gives up on (hq issue 330) ... The comments said a failing event dead-letters, which nothing did; the controller now keeps it, and delivers it again under a subject this runtime reads the same key from (ADR 0264).	2026-10-08 17:36:04 +02:00
jochen	6604d44372	A refused tool subscription is said, never fatal (novox/hq issue 218) ... After the controller stopped granting a mesh seat to claimants that do not hold it, an image built before the runtime followed its membership still subscribed the seat's subject, and the refusal ended the process: ace's postgres runtime crash-looped. A subject the grants leave out now costs that subject only, as an announcement's already did (issue 217).	2026-10-04 00:13:15 +02:00
jochen	6ba0f4dc1e	A refused announcement is said, never fatal (hq issue 217) ... The raw subscription that answers discovery ran its loop unguarded, so a refusal escaped as an unhandled rejection and ended the process: every per-module container crash-looped on 2026-10-03 over a subscription that only serves the mesh seeing the runtime. It is now caught, logged, and the runtime serves on. Tested against a bus whose permissions refuse the subject; fails without it.	2026-10-03 23:24:38 +02:00
jochen	66e8be0e31	The TypeScript runtime announces what it serves too, in the same services format (hq ADR 0197) ... The per-module containers still run this runtime; their tools and the seats they hold (the store's, the catalogue's) must be found by the console the same way as the node runtime's. It answers $SRV.PING, $SRV.INFO and $SRV.STATS with one service per process, one endpoint per tool per subject and per seat verb served, the metadata as the Go runtime writes it.	2026-10-03 22:15:48 +02:00
jochen	c46f9502ee	node-tools is a module beside mesh-tools: the runtime as a bundle, and serve is the console (hq ADR 0175, to-be 38 WP3) ... One repository, two modules (ADR 0069). `node-tools/` holds the runtime — its code, tests, package and the manifest of the module the controller composes a process for on every machine it is assigned to: a bundle of `src/main.js`, the interpreter as a package, a place for the node's credential, the loopback port the console declared, and leave to call every tool. Nothing about how it runs: which bundles to load, where the credential is and whose machine it is are the controller's to compose (WP2). The root module `mesh-tools` keeps the two images TypeScript bundles are compiled in and a module's own service may run in; it is no longer how tools reach a node. As node-tools, `serve` is also the console (ADR 0175 §6): the same process answers MCP on loopback for whoever is on the machine, through which the tools it serves can be called. A module's own runtime in a container keeps serving without a listener. The toolchain image now carries /app/runtime — a package.json saying the compiled files are ES modules and the production node_modules — for the builder to copy into every TypeScript bundle, so a bundle unpacked on a machine starts (ADR 0188 §5; the builder's side is the controller's). Proven here by compiling node-tools with the toolchain's exact flags and starting the result. The AMQP probe script is gone with the bus it probed.	2026-10-02 21:43:37 +02:00