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 @@
+${config:hostname}
@@ -0,0 +1,7 @@
+# The machine's own names (module hostname, novox/hq ADR 0199, ADR 0223). Every line outside this
+# block is the operator's: kept across every push, changed through the node-hostname verbs add and
+# remove, and given back when this module goes. The mesh's names are not here: the mesh's resolver
+# answers them.
+127.0.0.1	localhost
+::1	localhost
+127.0.1.1	${machine:name}