The toolchain carries the SDK the mesh last published, and esbuild (hq issue 212, ADR 0193)

mesh-tools stands on mesh-sdk's published package: the build receives its exact version and
installs it after the package.json install, so a release is a new argument and the cached layer
cannot keep an older SDK; the planner orders the toolchain after the SDK, and every bundle after the
toolchain (issue 211). esbuild, a development dependency, is what the builder bundles each
TypeScript entrypoint and launcher into one file with.

module.json

@@ -21,6 +21,11 @@
       {
         "arg": "NODE_BASE",
         "image": "node@sha256:48e4b67d85f87bd551df43704e24d252f56cc5f8e9718841aace50f19948f0f9"
+      },
+      {
+        "arg": "MESH_SDK",
+        "module": "mesh-sdk",
+        "artifact": "lib"
       }
     ]
   },