novox/mesh-tools

Fork 0

Files

T

History

jschoubben 634c77f90f

mesh/delivery merged: source.main moved to novox/mesh-tools@27710ccabd53

Details

mesh/check checking 634c77f90f98 on 27710ccabd53

The runtime says no lost compare-and-set as a failed operation, and its test waits on a channel, never a sleep (review round 1)

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

2026-11-09 02:21:55 +01:00

cmd/node-tools

Tool runner: waits for the first read of the seat list on the reader's Ready, to a bound, and serves with the bootstrapped seats past it (B9c, ADR 0636 §1; issue 1966)

2026-11-05 14:49:52 +01:00

internal

The runtime says no lost compare-and-set as a failed operation, and its test waits on a channel, never a sleep (review round 1)

2026-11-09 02:21:55 +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

Take tidy's go.mod whole: mesh requirements at the zero version only, unused ones dropped

2026-11-06 00:52:18 +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

The console reads the assigner's state assignments and imports the contracts' new paths (issue 1966)

2026-11-05 22:02:06 +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.