Take the catalogue's composition rules into the node-engine

ADR 0593 §7: the composer with its refusals leaves mesh-sdk, so mesh-sdk carries no composition rule. The catalogue functions only the node-engine's composition reaches (Resolve, Resolution's Compose, Declaration, DataItems, LeftOut, Rules and the rest, the settings, placeholder and template refusals, the rendering helpers) are copied with their tests into internal/compose/resolution; a method of a mesh-sdk shape becomes a function taking it first. The composition calls its own copies, and the captured catalogue its tests read lives here now, shared by mesh-compose's tests. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
2026-11-02 19:15:55 +01:00
parent be0226b624
commit d68e241724
686 changed files with 35703 additions and 80 deletions
@@ -0,0 +1,4 @@
+# The operator account's environment for its service manager and graphical session, generated by
+# the mesh (module node-env, novox/hq ADR 0203). Do not edit: this file is replaced at every push.
+# The same facts as ~/.config/mesh/environment.sh, in environment.d(5) syntax.
+${collected:environment:systemd}
@@ -0,0 +1,5 @@
+# The operator account's environment, generated by the mesh (module node-env, novox/hq ADR 0203).
+# Do not edit: this file is replaced at every push. Every line names the module that contributed it.
+# Sourced by the login shell from its always-read startup file (for zsh, ~/.zshenv), so a script, a
+# login and the shell's execute verb all see it. Your own variables belong in your shell's own lines.
+${collected:environment:posix}