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

internal/compose/resolution/doc.go

@@ -0,0 +1,7 @@
+// Package resolution is the node-engine's resolution and rendering of a machine's modules from their manifests: which
+// modules a node runs and why (Resolve), what each composes to (Compose, Declaration, DataItems), what is left out and
+// why, and every refusal of a composition, settings and templates included. It moved here from mesh-sdk's catalogue
+// package (novox/hq ADR 0593 §1, §7): only the node-engine composes, so mesh-sdk carries no composition rule. The
+// manifest's shapes and the indexer's judgement stay in mesh-sdk; a method of a mesh-sdk shape that composes is a
+// function here taking that shape first (Compose(r, with) for Resolution.Compose).
+package resolution