2 Commits

Author	SHA1	Message	Date
Claude	7393cc2b73	feat(rvcsi): rvcsi-runtime composition + rvcsi-node (napi-rs) + rvcsi-cli + @ruv/rvcsi TS SDK ... - rvcsi-runtime — the composition layer (no FFI): CaptureRuntime (CsiSource + validate_frame + SignalPipeline + EventPipeline, with next_validated_frame / next_clean_frame / drain_events / health) plus one-shot helpers (summarize_capture → CaptureSummary, decode_nexmon_records, events_from_capture, export_capture_to_rf_memory, rf_memory_self_check). 10 tests. - rvcsi-node — the napi-rs seam (cdylib+rlib, build.rs runs napi_build::setup): thin #[napi] wrappers over rvcsi-runtime — rvcsiVersion / nexmonShimAbiVersion / nexmonDecodeRecords / inspectCaptureFile / eventsFromCaptureFile / exportCaptureToRfMemory + an RvcsiRuntime streaming class. Everything that crosses the boundary is a validated/normalized rvCSI struct serialized to JSON (D6). deny(clippy::all). - @ruv/rvcsi npm package (package.json + index.js + index.d.ts + README + __test__/api.test.cjs) — curated JS surface that JSON-parses the addon's output into plain CsiFrame/CsiWindow/CsiEvent/SourceHealth/CaptureSummary objects; lazy native-addon load with a helpful "not built" error. - rvcsi-cli — the `rvcsi` binary: record (Nexmon dump → .rvcsi, validating), inspect, replay, stream, events, health, calibrate (v0 baseline), export ruvector. 7 tests exercising every subcommand against in-memory captures. - rvcsi-cli no longer depends on rvcsi-node (a binary can't link the napi addon); the shared logic moved to rvcsi-runtime. .gitignore: ignore the generated *.node / binding.js / binding.d.ts / npm/ under rvcsi-node. All rvcsi crates: build together OK, clippy-clean, 140 unit/integration tests + 2 doctests, 0 failures (core 29, dsp 28, events 18, adapter-file 20+1, adapter-nexmon 9, ruvector 20+1, runtime 10, cli 7). https://claude.ai/code/session_01CdYAPvRTjcch6YrYf42n1z	2026-05-13 00:17:45 +00:00
Claude	1e684cb208	feat(rvcsi): rvcsi-core + napi-c Nexmon shim + crate skeletons (ADR-095/096) ... First implementation milestone for the rvCSI edge RF sensing runtime: - rvcsi-core — the foundation: CsiFrame/CsiWindow/CsiEvent normalized schema, ValidationStatus, AdapterProfile, CsiSource plugin trait, id newtypes + IdGenerator, RvcsiError, and the validate_frame pipeline (length/finiteness/ subcarrier/RSSI/monotonicity hard checks + multiplicative quality scoring → Accepted/Degraded/Recovered/Rejected). 29 unit tests, forbid(unsafe_code). - rvcsi-adapter-nexmon — the napi-c boundary: native/rvcsi_nexmon_shim.{c,h} (the only C in the runtime, allocation-free, bounds-checked, parses/writes a byte-defined "rvCSI Nexmon record" — a normalized superset of the nexmon_csi UDP payload), compiled via build.rs + cc, wrapped by a documented ffi module and a NexmonAdapter implementing CsiSource. 9 tests round-tripping through C. - Workspace registration in v2/Cargo.toml (8 new members + napi/cc workspace deps) and compiling skeletons for rvcsi-dsp, rvcsi-events, rvcsi-adapter-file, rvcsi-ruvector, rvcsi-node (napi-rs cdylib + build.rs napi_build::setup) and rvcsi-cli (`rvcsi` binary) — to be filled in by the implementation swarm. cargo build -p rvcsi-core -p rvcsi-adapter-nexmon -p rvcsi-node -p rvcsi-cli: OK cargo test -p rvcsi-core -p rvcsi-adapter-nexmon: 38 passed, 0 failed https://claude.ai/code/session_01CdYAPvRTjcch6YrYf42n1z	2026-05-12 23:49:58 +00:00