The controller announces as the tool runtimes do, and answers $SRV.STATS (hq ADR 0197) #242

2026-10-03T20:18:41Z

mesh-admin commented

2026-10-03 20:18:41 +00:00

Aligns #241 with the runtimes' announcement (mesh-tools feat/0197-tools-announce-themselves): endpoints named <seat>__<verb> with the metadata the console identifies them by (kind: seat, module, tool, seat, scope: mesh, interchangeable); $SRV.STATS answered (identity and endpoints, nothing counted). Grants: STATS beside PING and INFO; the node's tool runtime may answer under its own name node-tools, because it announces everything it carries as one service — the bus's allow_responses: max 1 lets a process answer each request once. Golden regenerated; installer template in mesh-host companion PR. Full suite passes from the worktrees.

Aligns #241 with the runtimes' announcement (mesh-tools feat/0197-tools-announce-themselves): endpoints named `<seat>__<verb>` with the metadata the console identifies them by (`kind: seat`, `module`, `tool`, `seat`, `scope: mesh`, `interchangeable`); `$SRV.STATS` answered (identity and endpoints, nothing counted). Grants: STATS beside PING and INFO; the node's tool runtime may answer under its own name `node-tools`, because it announces everything it carries as one service — the bus's `allow_responses: max 1` lets a process answer each request once. Golden regenerated; installer template in mesh-host companion PR. Full suite passes from the worktrees.

mesh-admin added 2 commits 2026-10-03 20:18:42 +00:00

A bundle stands on the toolchain it is compiled in (hq issue 211) 58b4fcb8c8

A manifest names its toolchain by language, not in build.on, so the planner did not know a bundle
depends on the module that publishes its toolchain and built the two in one tier: the bundle
against the old toolchain, recorded as built from the new commit. The edge is read from the
manifest, so it holds before any build recorded it, and a toolchain that moves rebuilds every
bundle compiled in it.

The controller announces as the tool runtimes do, and answers $SRV.STATS (hq ADR 0197) b127f005c3

Endpoints named <seat>__<verb> with the metadata the console identifies them by (kind, module,
tool, seat, scope); $SRV.STATS answered with its identity and endpoints, nothing counted. Grants:
STATS beside PING and INFO, and the tool runtime may answer under its own name, since it announces
everything it carries as one service — the bus lets it answer each request once.

mesh-admin merged commit 82481099b7 into main

2026-10-03 20:18:49 +00:00

mesh-admin deleted branch fix/0197-the-controller-announces-as-the-runtimes-do

2026-10-03 20:18:49 +00:00

mesh-admin referenced this pull request

2026-10-03 21:16:08 +00:00

Tools pipeline: issues 214, 215, 216, Go tools bundles served, and the runtime consumes for its modules (ADR 0193, 0198) #246

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#242