Remove the toolchain image module; node-tools is the repository's only module (issue 979, S1; ADR 0524 §5)

Only build-agent built inside that image, and it goes in R4g.

README.md

@@ -1,13 +1,11 @@
 # mesh-tools
 
-Two modules in one repository (novox/hq ADR 0069), one piece of software:
+One module, `node-tools`; the toolchain image module that stood beside it is retired (novox/hq ADR 0524 §5):
 
 - **`node-tools`** (`node-tools/`) — the node's **tool runtime** as a module (ADR 0175, to-be 38
   WP3): one process per machine the host runs from this bundle, serving every assigned module's tools
   and every held seat's verbs on the bus, and answering MCP on the machine's loopback — the console
   (design 34). The code, its tests and the `mesh` client all live there.
-- **`mesh-tools`** (this directory) — the two images TypeScript bundles are compiled in and a module's
-  own *service* may still run in. Built from the same code; no longer how tools reach a node.
 
 The runtime:
 
@@ -49,8 +47,7 @@ MESH_BROKER_URL         a plain URL instead of the credential, for the bootstrap
 
 `node dist/main.js`. On a node the controller composes the variables and the host supervises the
 process like any other host-side workload (novox/hq to-be 38). As `node-tools` the same process is
-the console: MCP on `127.0.0.1:4270` (or `MESH_CONSOLE_LISTEN`). The container (`Dockerfile`) is how
-a module's own *service* may still be built; it is no longer how tools reach a node.
+the console: MCP on `127.0.0.1:4270` (or `MESH_CONSOLE_LISTEN`).
 
 ## `mesh` — the tools for whoever is on a machine