Design 38 WP4b: four tools-only modules proven live from the runtime; two delivery traps

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

@@ -253,6 +253,13 @@ sockets — so seven move here. *Built 2026-10-03:* mesh-sdk #12 (`collectToolsE
 (each bundle its own environment), mesh-controller #236 and #237 (the words composed, made the
 account's to read, and named files restarting the runtime), and the seven modules in one change.
 Building it found issue [211](../../04-ISSUES/211-a-bundle-is-built-before-the-toolchain-it-is-compiled-in/00-report.md).
+*Proven live 2026-10-03* (mesh-catalog #242, #243): on the one machine that runs them, baserow,
+letta, searxng and unifi answer from the runtime with no tool container — each reading its
+configuration file as the operator's account — and the runtime serves seventeen tools for six
+modules there. confluence, gitlab and jira are assigned nowhere and retire with the predecessor.
+Two traps met on the way: a tools bundle whose module declares no `tools` list must say `loads`, or
+the composer delivers it nowhere while the build reports success; and a module whose builds are
+pinned to an old commit is left out of a merge's plan and must be built from `main` by hand.
 
 ## WP4c — The module's own long-running code moves