Design 38 WP4d: every served bundle launched and node-tools in Go, proven live on all four machines

03-DESIGN/01-to-be/38-building-the-operators-machine.md

@@ -277,6 +277,16 @@ over HTTP — and replaces the TypeScript one, proven the same way.
 **Proof.** The tests ADR 0193 names; live, every moved module's tools and both node seats answer from
 launched bundles on every machine, and then do again from the Go runtime.
 
+*Built and proven live 2026-10-03.* mesh-sdk #13/#14 (0.1.4, 0.1.5: served as the named module; an
+emit travels through the runtime), mesh-controller #239/#240 (a launcher beside every TypeScript
+entrypoint; a runtime compiled to a binary runs itself), mesh-host #81 (`./name` is the process's own
+binary), mesh-tools #35/#36/#37/#38 (the module named; launch-only; the toolchain requiring 0.1.5; the
+runtime in Go). On all four machines node-tools is now the Go binary, launching every served bundle:
+both node seats answered from it on every machine and the four moved modules on theirs. Found on the
+way: issue [212](../../04-ISSUES/212-a-toolchain-rebuild-keeps-the-sdk-it-cached/00-report.md) (the
+toolchain image kept a cached SDK, and the seats' verbs went unanswered on three machines for an hour),
+and the controller's plan losing track of its own rebuild when it restarts mid-plan.
+
 ## WP4c — The module's own long-running code moves
 
 *Not yet broken down.* Twenty-three containers carry code that is not a tool: event handlers,