Files

T

jschoubben ea8d9c5f56 Test budget: the approval mark's two tables replace two tests folded into their neighbours

The tool runner ends milestone G with no more tests than it started with: the no-responders
test takes the 503 case, and the stated-capabilities test takes the sent-object row.

Builds: design 46 7-approval-mark §22; design 47 G §626

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

2026-11-12 05:26:24 +01:00

cmd/node-tools

A-7 tools: mesh_approvals reads and steers what was asked; mesh_describe says a mark and its source

2026-11-12 05:24:41 +01:00

internal

Test budget: the approval mark's two tables replace two tests folded into their neighbours

2026-11-12 05:26:24 +01:00

test/fixtures

Remove the TypeScript runtime code that called the old catalog module's tools; a test finds no file naming one (ADR 0604 section 4, issue 774)

2026-11-03 17:15:17 +01:00

go.mod

A-4 record: a run on the operator's approval answers its approval and is recorded in the hand-act log

2026-11-12 05:18:42 +01:00

go.sum

Require every mesh package of the group at the floor version (ADR 0573 sections 2 and 4, issue 1966)

2026-11-05 16:56:39 +00:00

module.json

W16.6: the tool runner reads which modules exist and their manifests from the catalog half through meshcatalogclient's branch follower on its own consumer (milestone 47/G)

2026-11-11 23:40:23 +01:00

package-lock.json

Remove the TypeScript runtime code that called the old catalog module's tools; a test finds no file naming one (ADR 0604 section 4, issue 774)

2026-11-03 17:15:17 +01:00

package.json

Remove the TypeScript runtime code that called the old catalog module's tools; a test finds no file naming one (ADR 0604 section 4, issue 774)

2026-11-03 17:15:17 +01: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

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.