ruvnet 551b3107de ci: extend aarch64 cross-build guard to all three sensor bridges (iter 128) ... Iter 122 added the cross-build job for ruvector-mmwave-bridge but iters 123-124 added two more bridges (ruview-csi-bridge, ruvllm-bridge). The CI guard was lagging — a transitive dep that didn't cross-compile in those bins could slip past CI even though the mmwave-bridge alone is fine. Now every PR explicitly cross-builds all three: cargo build --release --target aarch64-unknown-linux-gnu \ --bin ruvector-mmwave-bridge cargo build --release --target aarch64-unknown-linux-gnu \ --bin ruview-csi-bridge cargo build --release --target aarch64-unknown-linux-gnu \ --bin ruvllm-bridge Each ELF is verified via `file` to actually be `ARM aarch64`; mismatch fails the job loudly with the bin's name in the error. Local verification before adding the CI step: - All three bins cross-built clean from x86 in 0.43s (warm cache). - scp'd ruview-csi-bridge + ruvllm-bridge to cognitum-v0 (Pi 5), ran each `--version` natively. Both reported "ruvector-hailo-cluster 0.1.0" — bins work end-to-end on the target arch + target distro (Pi 5 OS Bookworm, glibc 3.7+). Co-Authored-By: claude-flow <ruv@ruv.net>		2026-05-02 15:19:31 -04:00
..
benchmarks	feat: Add Neo4j-compatible hypergraph database package (ruvector-graph)	2025-11-25 23:11:54 +00:00
workflows	ci: extend aarch64 cross-build guard to all three sensor bridges (iter 128)	2026-05-02 15:19:31 -04:00