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>
- Format all Rust code with cargo fmt
- Generate Cargo.lock for security audit
- Add build:wasm script to graph-wasm package.json
- Update npm/package-lock.json
The CI was failing due to:
1. Rust code formatting check failures
2. Missing Cargo.lock file for cargo audit
3. Missing build:wasm script expected by graph-ci.yml workflow
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- ruvector-cluster: Distributed coordination with DAG-based consensus,
consistent hashing sharding, node discovery (static/gossip/multicast),
and load balancing across shards
- ruvector-raft: Full Raft consensus implementation following the paper
spec, including leader election, log replication, snapshots, and RPC
messages with bincode 2.0 serialization
- ruvector-replication: Data replication with sync/async/semi-sync modes,
vector clock conflict resolution, CRDT-inspired merge strategies,
change streaming with checkpointing, and automatic failover with
quorum-based decisions
All 56 tests pass across the 3 new crates. Fixed several issues during
review: bincode error types, Send bounds for async spawns, unnecessary
async methods converted to sync.
