feat(aura-cli): composite definition renders as a typed signature

Refines #41's blueprint-definition render. The [param:<name>] marker nodes
#41 added bloated the ASCII MACD graph (three extra nodes + fan-in edges);
this moves the interface into the title line and folds names into the leaf
labels that already exist:

- title is the composite's typed signature, e.g.
  macd(fast:i64, slow:i64, signal:i64) -> (macd, signal, histogram)
  (param kinds from the aliased leaf's factory params via a new
  ScalarKind->lowercase kind_str; output NAMES only — output kinds need a
  pre-build factory interface, deferred to #43)
- leaf labels fold aliased param names: [EMA] -> [EMA(fast)]
- unnamed interior input slots render as ordered stubs: [Sub] -> [Sub(#A,#B)]
  (count/order derived render-side from c.edges() + c.input_roles(), no
  engine schema needed; arity-1 nodes get no stub)
- outputs de-prefixed: [out:macd] -> [macd]; the [param:*] marker nodes are
  gone
- two stale doc comments corrected: render_definition's [param:] prose and
  node.rs LeafFactory::label (the renderer went flat in 0017, so the cited
  ascii-dag cluster-garble rationale no longer applies — wide labels are
  safe; the factory label stays bare because alias names are composite-level)

Render-only: no engine/ParamAlias/param_space change. compiled_view_golden
byte-identical (C23 guard — verified untouched in the diff); aura run --macd
deterministic and unchanged (total_pips 0.1637945563898923, 3 sign flips).

The title format change repinned five .matches("name:")->.matches("name(")
definition-count asserts (sma_cross/outer/inner/dup/macd); the stub
separator is "," (no space) to match the [Sub(#A,#B)] surface.

Verification (orchestrator-run): cargo build/test/clippy --workspace
-D warnings all green; the redesigned MACD render confirmed by eye.

refs #41 #43

crates/aura-core/src/node.rs

@@ -91,14 +91,15 @@ impl LeafFactory {
         (self.build)(params)
     }
     /// The param-generic render label for the blueprint view (C22 "structure
-    /// before"): just the node type, e.g. `SMA`. A value-empty recipe has no
-    /// values to show; the tunable knobs are surfaced by `Blueprint::param_space`,
-    /// not in the graph. The label stays the bare type because the `ascii-dag`
-    /// renderer writes a label verbatim on one line (no wrapping) and overlaps two
-    /// wide sibling boxes inside a cluster subgraph — appending the knob names
-    /// (`SMA(length)`) would garble the blueprint view, and domain labels grow
-    /// unboundedly wide. The compiled view labels the built node valued (`SMA(2)`)
-    /// via `Node::label`, unaffected.
+    /// before"): just the node type, e.g. `SMA`. A value-empty recipe has no values
+    /// to show; the tunable knobs are surfaced by `Blueprint::param_space`. The
+    /// factory label stays the bare type because alias / handle names are a
+    /// *composite-level* concept — the renderer folds them into the leaf label at
+    /// the composite boundary (`render_definition`'s `leaf_label`), where the
+    /// `(node, slot)` → name mapping lives, not on the standalone factory. (Wide
+    /// labels are safe: both `aura graph` views are flat since cycle 0017 — no
+    /// cluster subgraph, so no sibling-overlap garble.) The compiled view labels the
+    /// built node valued (`SMA(2)`) via `Node::label`, unaffected.
     pub fn label(&self) -> String {
         self.name.to_string()
     }