audit: cycle 0010 tidy (clean)
Architect drift review over 7a8d209..559903a (aura run CLI, #8): drift-clean, carry-on. Regression gate is a no-op (commands.regression empty); architect is the sole gate and found nothing actionable. What holds against the ledger: - C22 closing seam genuinely delivered: `aura run` bootstraps a CLOSED harness WITH two sinks and emits a populated, non-trivial trace (one exposure sign flip, a real drawdown) — a newcomer sees a real trace, as C22 promises. - C16 respected: Recorder ships in aura-std as a domain-free universal block (parameterised over ScalarKind/Firing/Sender, no instrument/strategy concepts); sample_harness lives in aura-cli, not aura-engine, so the engine stays domain-free while wiring stays plain Rust (C17/C20 — raw Harness::bootstrap, no DSL). - C7 purity: mpsc::Sender out-of-graph handle, no Rc/RefCell. C8 sink contract: output: vec![], eval returns None. C14 structured face: real binary → canonical JSON on stdout, exit-code contract integration-tested. C1 determinism pinned. Acknowledged, spec-deferred debt (tracked, not silent drift) — filed to the forward queue: - Three near-identical Recorder definitions now coexist: the shipped aura-std block (the strict superset — four kinds) plus the two #[cfg(test)] engine fixtures (f64-only) in report.rs / harness.rs. The spec explicitly defers de-dup; flagged for a later tidy. - manifest.commit is option_env!("AURA_COMMIT") → "unknown" — the C18 identity field is a placeholder until build.rs git capture (named non-goal). The one implementer deviation (a scoped #[allow(clippy::type_complexity)] on sample_harness) is consistent with the identical allow on aura-engine's build_two_sink_harness fixture — not drift.
This commit is contained in:
