Files

T

jschoubben 3f538027e9 Read a per-node state through mesh-sdk's pernode package, so the runtime and a process share one copy of its rules

Replaces the runtime's own bucket listing, advisory hearing and per-bucket bookkeeping; the bound on progress and the runtime's shapes stay here. ADR 0593 §6.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL

2026-11-02 18:31:18 +01:00

cmd/node-tools

node-tools: start no bundle again once the runtime itself is stopping (issue 1126)

2026-10-28 15:30:12 +01:00

internal

Read a per-node state through mesh-sdk's pernode package, so the runtime and a process share one copy of its rules

2026-11-02 18:31:18 +01:00

src

Name no controller verb in hints and drop its handover and paging reads, since the controller ended (issue 1126 B19)

2026-11-02 11:23:14 +01:00

test

Name no controller verb in hints and drop its handover and paging reads, since the controller ended (issue 1126 B19)

2026-11-02 11:23:14 +01:00

go.mod

Pin mesh-sdk to the group head of issue 1126

2026-11-02 12:27:34 +01:00

go.sum

Pin mesh-sdk to the group head of issue 1126

2026-11-02 12:27:34 +01:00

module.json

node-tools waits on the self-check's checked, not the controller's (ADR 0571 clause 13, issue 1955)

2026-11-01 09:54:39 +01:00

package-lock.json

Bring node-tools' lock back in step with package.json, and fail the check when it falls behind (hq issue 624)

2026-10-13 15:12:10 +02:00

package.json

Give the TypeScript toolchain pg, mongodb and mssql, so a catalogue check can type-check the modules that use them (issue 385)

2026-10-12 12:27:46 +02:00

README.md

Name no controller verb in hints and drop its handover and paging reads, since the controller ended (issue 1126 B19)

2026-11-02 11:23:14 +01:00

tsconfig.json

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)

2026-10-02 21:43:37 +02:00

README.md

node-tools

The node's tool runtime as a module (novox/hq ADR 0175, to-be 38 WP3). Assigned to a machine, it is one process the host runs from this bundle, as the operator's account: it serves every assigned module's tools and every held seat's verbs on the bus, and answers MCP on the machine's loopback — the console (design 34). The mesh composes the process (which bundles to load, where the credential is, whose machine it is); this manifest says only what the machine must have for it: the interpreter, a place for the credential, the loopback port, and leave to call every tool.

The code is the mesh-tools package in this directory; the module at the repository root, mesh-tools, builds the images TypeScript bundles are compiled in. See the repository README.