* CI: dev profile keeps line tables for workspace crates and no debug info for dependencies * Control server tests: persistent_requests_and_slow_replies_outlive_the_idle_read_timeout no longer races the idle timeout Each request (and the closing half-shutdown) reaches the socket before the worker reads, so on a slow machine only the reply waits outlast the 100 ms idle timeout, as the test intends. The idle test sends its input the same way, and the no-frames test allows 5 s instead of 2 s to give up. * CI: one integration-test binary per crate Each crate's tests/*.rs become modules of tests/it/main.rs (51 test files into 13 binaries, plus 6 that stay their own). Inner #![cfg] attributes move to the mod lines. Files that change state for the whole process keep a binary of their own: codecs jxl_tail_heap and raw sr2_heap (dhat global allocator), gpu shutdown, shutdown_first and memory, ui-egui shutdown. Docs, comments and the GPU probe name the new paths and targets (--test it <module>::); the CI report names an it binary's skips after the crate. * CI: tests under nextest, doctests apart, one wasm check xtask ci runs the tests with cargo nextest run --lib --bins --tests when cargo-nextest is installed, else cargo test with the same targets and a one-line notice; doctests run after them with cargo test --workspace --doc. The heif and hardware GPU steps use the same runner. Examples stay out of the test build (clippy --all-targets still checks them). Concurrent tests under nextest follow the RUST_TEST_THREADS cap (NEXTEST_TEST_THREADS). The wasm check is one cargo check --keep-going over the same crates, and clippy runs with --keep-going. * CI: tests run under cargo test by default, nextest with LIGHTCRAFT_NEXTEST=1 (per-process scene cache)
lightcraft-denoise
L1 pure-Rust AI RAW denoise primitives and CPU inference. No weights are bundled. See user workflow and limitations.
lightcraft-denoise-core provides metadata, Bayer helpers and cache formats,
re-exported here. manifest and known validate opt-in models; onnx reads a bounded operator subset
into net; cpu executes it and reference supplies scalar checks. bayer, tiles
and run pack sensor data and blend overlapping tiles while preserving clipped
highlights. product reads/writes the disposable .lcdn cache. runtime supplies
the installation self-test. Synthetic networks are generated in Rust for tests.
Run cargo test -p lightcraft-denoise --features runtime. The CPU backend is optional;
featureless and web builds keep the model metadata and cache format without faer/GEMM.
The rawnind-model feature enables the otherwise empty download catalog and requires
an explicit release-policy decision. Real-model tests are ignored by default and
require an explicitly supplied local model. The GPU twin is lightcraft-gpu::nn;
model management, background jobs and export integration live in lightcraft-engine.