918 B
211 — Diagnosis
2026-10-03. The planner orders a merge's modules by inventory.Dependencies, whose edges come from a
manifest's build.on, from what a build recorded it stood on, from the repositories it read, and from
the build machine. A bundle names its toolchain by language; the builder takes the toolchain image
(ToolchainFor(language)) from what the mesh holds and records nothing of it as stood on. So no edge
ran from a bundle to the module publishing its toolchain, and a merge moving both (mesh-tools: the
images and node-tools) tiered them together. Fix (mesh-controller, branch
fix/issue-211-a-bundle-stands-on-its-toolchain, commit c72f6ca): dependenciesOf adds a stands-on
edge from every bundle artifact to its toolchain's module, read from the manifest. Tested: TypeScript
bundle → mesh-tools, Go bundle → mesh-tools-go, image → none; a merge moving both plans two tiers.