ruvnet 99549cec2c test(mmwave-bridge): production-ready CLI coverage + CI wiring (iter 118) ... Iter 116 shipped the bridge → cluster integration with a manual live test, but nothing committed. Production-ready means the integration tests run on every commit. This iter closes the gap. New tests/mmwave_bridge_cli.rs (7 tests, ~180 LOC): bridge_simulator_emits_cycle_of_jsonl_events spawns bridge --simulator --rate 10 for 700ms; asserts all four frame kinds (breathing, heart_rate, distance, presence) appear in stdout JSONL — guards against state-machine regressions that would silently drop a frame type. bridge_simulator_with_workers_posts_to_cluster spawns fakeworker + bridge with --workers, asserts ≥3 successful "posted text=" lines on stderr in 900ms and zero "cluster post failed" lines. Verifies the iter-116 cluster sink path actually composes with a live tonic server, not just unit-level mocks. bridge_workers_without_fingerprint_refused_by_default --workers + empty --fingerprint must fail before any RPC fires (ADR-172 §2a parity with embed/bench). Guards against the gate being bypassed in the bridge's discovery path. bridge_workers_without_fingerprint_succeeds_with_opt_in --allow-empty-fingerprint is the documented escape hatch for legacy fleets; verify it actually works. bridge_no_mode_flag_errors_cleanly Running with no mode flag must produce a useful error referencing the three valid mode flags. Operator-experience guard. bridge_help_prints_synopsis --help mentions --simulator, --workers, --fingerprint. bridge_version_prints_pkg_name_and_version --version output parses as `<name> <version>`. CI changes (.github/workflows/hailo-backend-audit.yml): - Path watcher now triggers on `crates/ruvector-mmwave/**` so a regression in the shared parser fails CI before consumers (firmware + bridge) can ship broken decoders. - test job adds `cargo test --all-features` + clippy for the standalone ruvector-mmwave crate. Tested independently so the parser bisect cleanly when CI fails. Validation: - 17 test groups in the cluster crate now (was 16); 7 new bridge tests join the matrix on default + tls feature configs. - clippy --all-targets -D warnings clean for both ruvector-mmwave (--all-features) and ruvector-hailo-cluster (default + tls). Co-Authored-By: claude-flow <ruv@ruv.net>		2026-05-02 14:48:40 -04:00
..
benchmarks	feat: Add Neo4j-compatible hypergraph database package (ruvector-graph)	2025-11-25 23:11:54 +00:00
workflows	test(mmwave-bridge): production-ready CLI coverage + CI wiring (iter 118)	2026-05-02 14:48:40 -04:00