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

testdata/beside/mesh-catalog/modules/sudo/files/10-mesh-operator

@@ -0,0 +1,9 @@
+# The mesh's (module sudo, novox/hq to-be 42, research 027): the operator account escalates
+# without a prompt. The mesh's tools that act as root run `sudo -n` as this account and rely on it;
+# until this file, every machine said so only in a line set by hand in /etc/sudoers.
+# Written whole at every push: an edit here is overwritten. A file of this directory whose name
+# holds a dot or ends in ~ is not read by sudo; this name holds neither.
+# Every command run through sudo gets a terminal of its own (novox/hq ADR 0266): an agent the operator
+# starts as the agent account through sudo cannot push keystrokes into the operator's shell (TIOCSTI).
+Defaults use_pty
+${machine:account} ALL=(ALL:ALL) NOPASSWD: ALL