novox/mesh-tools

Files

T

History

jschoubben 860043fd7f

mesh/delivery failed: its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine

Details

mesh/delivery-group group feat/r4g failed: a member failed

Details

mesh/check checking 860043fd7fa0 on e0fadc43d9dd | novox/mesh-tools#40 in group feat/r4g

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied

2026-10-23 17:06:12 +02:00

..

Feature 57 (config and provisioning): release mesh-tools (the provider's StateBus, the SDK pin, templates), reviewed

2026-10-16 09:41:17 +00:00

Merge branch 'feat/r4g-asks' into feat/r4g

2026-10-23 16:20:32 +02:00

Say what becomes of an event a handler gives up on (hq issue 330)

2026-10-08 17:36:04 +02:00

node-tools: a tool call names its caller, and the module is told it from the subject (hq issue 365)

2026-10-11 05:19:08 +02:00

go.mod

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied

2026-10-23 17:06:12 +02:00

go.sum

Pin mesh-sdk at feat/r4g's head a2c813a6, its test fixture fix, with go.sum tidied

2026-10-23 17:06:12 +02:00

module.json

Wait on the gate's transition alone: today's module is forgotten (issue 1406)

2026-10-20 12:59:33 +00: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

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

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 controller 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.