The B0 audit (commit 62ab8ed85) under-counted insert_batch test
callers as 2 (1 production + 1 in-file unit test). Surfaced during
B1.0 implementation when cargo check --workspace --tests failed
with 5 arity-mismatch errors after B0's signature change.
Root cause: B0 audit's grep filter was `grep -v test` and didn't
enumerate crates/ml/src/trainers/dqn/smoke_tests/ (compiled as
part of the lib's test binary, not behind #[cfg(test)]) nor
crates/ml/tests/.
Sites fixed (zero-init i32 alloc, threaded through):
- crates/ml/src/trainers/dqn/smoke_tests/training_stability.rs:152, 196
- crates/ml/src/trainers/dqn/smoke_tests/performance.rs:142
- crates/ml/src/trainers/dqn/smoke_tests/gpu_residency.rs:75
- crates/ml/tests/gpu_per_integration_test.rs:125
No behavior change — the column carries zero data and no consumer
reads it pre-B1.1. B1.1 lands the producer kernel that fills with
-1/0/1 from the 30-bar price trajectory.
Process correction documented in docs/dqn-wire-up-audit.md
"B0.1 cascade-gap fix-up" subsection: future B-series audits must
run cargo check --workspace --tests before claiming cardinality
completeness.
Build: cargo check --workspace --tests clean.
Tests: cargo test -p ml --lib compiles + passes (GPU tests
#[ignore]-gated).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6a869ad366