Files

T

jschoubben c35c27f664 Area 1 (part): the tool runner's manifest states approval-mark/1

The runner states the approval mark's word beside its call families, so its
artifact's states are exactly what it says (the join of A3's and A5's lines);
TestTheWordsTheRunnerStatesAreItsManifestsStates failed without it.

Builds: design 47 G §545, design 46 7-approval-mark §6; join 11 area 1

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

2026-11-12 10:44:02 +01:00

cmd/node-tools

Join 11: the merged heads compile where no area's fix is owed

2026-11-12 10:41:44 +01:00

internal

Join 11: the merged heads compile where no area's fix is owed

2026-11-12 10:41:44 +01:00

test/fixtures

A3h item 1: the tool runner serves a held seat's approvals from its gate's record

2026-11-12 10:21:21 +01:00

go.mod

Merge branch 'feat/47-G-fix11-a3' into feat/47-G-join11

2026-11-12 10:27:01 +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

Area 1 (part): the tool runner's manifest states approval-mark/1

2026-11-12 10:44:02 +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.