This session's work, proven 22/22: mesh-tools resolves @novox/mesh-sdk by version via a throwaway deps stage (Phase 2), plus the mesh-control→mesh-controller / substrate→foundation rename.
This session's work, proven 22/22: mesh-tools resolves @novox/mesh-sdk by version via a throwaway deps stage (Phase 2), plus the mesh-control→mesh-controller / substrate→foundation rename.
https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
package.json names @novox/mesh-sdk by version and the install is a
buildkit-secret-mounted resolve from the mesh's package registry, closing the
git-URL half of issue 053. The lock is regenerated against the registry (a
follow-up switches install to ci with a committed lock).
Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
A machine's docker may carry no buildx, so --mount=type=secret cannot be relied
on. Instead a deps stage copies in the builder-written .npmrc, resolves
node_modules from the mesh's registry, and the toolchain stage copies those
node_modules out without the credential — so it is in no published layer.
Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
One name per thing, per the HQ glossary: the module/container/image/binary/repo
becomes mesh-controller, the seat the-controller, and the store+broker pair the
foundation (embedded base bundles, default template and example lock renamed with
their go:embed directives). No behaviour change — a pure vocabulary rename.
Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This session's work, proven 22/22: mesh-tools resolves @novox/mesh-sdk by version via a throwaway deps stage (Phase 2), plus the mesh-control→mesh-controller / substrate→foundation rename.
https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx