Pre-existing rustfmt drift across the workspace was blocking CI's
`Rustfmt` check on PR #373 + PR #377. Running plain `cargo fmt`
reformats 427 files; no semantic changes, no logic changes, no
behavior changes — just what rustfmt already wanted.
None of the touched files are in ruvector-rabitq, ruvector-rulake,
or the new mirror-rulake workflow — those were already fmt-clean
per the per-crate checks on commits 5a4b0d782, 5f32fd450, f5003bc7b.
Drift is in cognitum-gate-kernel, mcp-brain, nervous-system,
prime-radiant, ruqu-core, ruvector-attention, ruvector-mincut,
ruvix/* and sub-crates, plus several examples.
Verified post-fmt:
cargo check -p ruvector-rabitq -p ruvector-rulake → clean
cargo clippy -p ... -p ... --all-targets -- -D warnings → clean
cargo test -p ... -p ... --release → 82/82 pass
Intentionally does NOT touch clippy drift — many more warnings
(missing docs, precision-loss casts, too-many-args, unsafe-safety-
docs) spread across unrelated crates, each category a cross-cutting
design decision that deserves its own review.
With this commit Rustfmt CI goes green on PR #373 and PR #377.
Clippy will still fail — that's honest pre-existing state for a
separate dedicated PR.
Co-Authored-By: claude-flow <ruv@ruv.net>
- Run cargo fmt --all to fix formatting in 362 files across the entire workspace
- Add PGDG repository for PostgreSQL 17 in CI test-all-features and benchmark jobs
- Add missing rvf dependency crates to standalone Dockerfile for domain-expansion
- Add sona-learning and domain-expansion features to standalone Dockerfile build
- Create npu.rs stub for ruvector-sparse-inference (fixes rustfmt resolution error)
Co-Authored-By: claude-flow <ruv@ruv.net>
- Remove duplicate workspace members (solver/solver-wasm/solver-node)
- Add ruvector-attn-mincut to workspace members
- Switch ruvector-solver and ruvector-solver-wasm to workspace version/metadata
- Add version pin on ruvector-solver dep for solver-wasm and solver-node
- Remove stale version pins in examples/dna and examples/prime-radiant
- Fix unused assignment and unused mut warnings in neumann.rs
- Remove publish = false from ruvector-profiler, add keywords/categories
- Bump @ruvector/rvf-solver to 0.1.4
- Add Publishing section to CLAUDE.md
Published to crates.io: ruvector-solver, ruvector-solver-wasm,
ruvector-solver-node, ruvector-coherence, ruvector-attn-mincut,
ruvector-profiler (all v2.0.3)
Published to npm: @ruvector/rvf-solver v0.1.4
Co-Authored-By: claude-flow <ruv@ruv.net>
- Remove KahanAccumulator from forward_push hot paths, use plain Vec<f64>
(halves working set from 16 to 8 bytes/element for cache efficiency)
- Standardize near-zero thresholds in bmssp.rs: replace hardcoded 1e-30
with NEAR_ZERO_F64 = 1e-15 constant matching other solver modules
- Add f64→f32 overflow checks in neumann.rs and true_solver.rs
SolverEngine::solve() before downcasting matrix/rhs values
- Add cfg-gated rayon parallelism for random walks in random_walk.rs
with per-chunk RNG seeding and fold/reduce aggregation
All 171 tests pass. Downstream crates (wasm, node) compile clean.
https://claude.ai/code/session_01TiqLbr2DaNAntQHaVeLfiR
Add ruvector-solver with 8 iterative solver algorithms:
- Jacobi-preconditioned Neumann series for diagonally dominant systems
- Conjugate Gradient (CG) for symmetric positive definite systems
- Forward/Backward Push for Personalized PageRank
- Hybrid Random Walk with Monte Carlo sampling
- TRUE solver with JL projection and spectral sparsification
- BMSSP multigrid preconditioner for ill-conditioned systems
- Jacobi and Gauss-Seidel iterative solvers
Includes intelligent algorithm router (SolverRouter/SolverOrchestrator),
WASM bindings (ruvector-solver-wasm), Node.js NAPI bindings
(ruvector-solver-node), Criterion benchmark suite, comprehensive
validation, audit logging, and 143 passing tests.
https://claude.ai/code/session_01TiqLbr2DaNAntQHaVeLfiR
