Brummel
d97fadaafa
Architect drift review over 9fbc16a..0a855c3 (aura graph ASCII-DAG render, #13): no contract violation. Regression gate is a no-op (commands.regression empty); architect is the sole gate. Contracts verified against the diff (by fact, not claim): - C8/C1: `Node::label()` is genuinely non-load-bearing — called only in the renderer (aura-cli/src/graph.rs) and test assertions, never in the run loop (harness.rs) nor the compile path (blueprint.rs). Wiring stays index-based; determinism untouched. The C8 Refinement note (INDEX.md) matches what shipped. - C16: no engine-crate manifest changed (aura-core/std/engine/ingest Cargo.toml all clean); ascii-dag v0.9.1 appears only in aura-cli/Cargo.toml + the matching Cargo.lock delta. The zero-external-dependency engine firewall is intact. - C9/C23: `Composite.name` dissolves at inline — `inline_composite` destructures `name: _` (blueprint.rs), the name never reaches the flat compilat. The compiled view emits no cluster (golden asserts `!contains("sma_cross")`); the blueprint view draws composites as clusters. Boundary dissolution holds. Drift status: drift_found = technical debt only (no fix iteration; contracts hold). Filed to the forward queue rather than fixed in-cycle: - #26 (feature) — the blueprint (clustered) view panics `unimplemented!` on nested composites while the compiled view handles nesting; the two views diverge in capability. Built-in sample is single-level so it is unreachable today. Bundles the low-severity source-label gap (sources render `source:{kind}` because SourceSpec has no name — latent C20 gap). - #27 (idea) — the SMA-cross sample wiring is now triplicated (aura run flat harness, aura graph composite blueprint, engine bit-identical fixture); distinct from #14's Recorder-fixture dedup. No baseline update (no regression script). Next-iteration direction (architect): resolve #26 before the next render-touching cycle so the two views stop diverging.