@ruvnet/ruview 0.9.2
Maintenance fixes from PR #2248, which records the exact source heads for 38 integrated contributor PRs.
- Accept official C6 firmware bundle filenames while preserving checksum and board-variant validation.
- Correct CSI loss accounting, observed capture duration, dominant stream selection, and synthetic-data provenance; reject malformed auxiliary packets.
- Correct ESPHome units and entity roles, report incomplete serial captures, and fix LiDAR/mmWave summaries and stream completion.
- Validate CLI numeric arguments, preserve gaps in watch history, report corrupt manifests through doctor, and honor SDK strict errors.
- Replace inherited and explicit Windows hosts-file ACL grants with verified current-user-only access. Paths are passed as data to the bounded helper, including Unicode and shell-special characters.
- Preserve source recordings during transcoding, avoid capture-session filename collisions, and retain complete relayed UDP datagrams.
- Exercise the contributor harness on Linux and Windows and correct CI snapshot release metadata.
Install the exact package with npm install @ruvnet/ruview@0.9.2, or run its CLI using npx @ruvnet/ruview@0.9.2 --help.
Repository-only changes also improve Home Assistant client topic compatibility and the MTK bridge test lifecycle. These changes do not imply that a new Python wheel or hardware-qualified firmware was published with this npm package.
The release commit also contains the separately reviewed calibration and sensing fixes: failed recording or baseline-save sessions finish as aborted, and diagnostic fields follow the actual occupancy decision without changing the accepted decision rules.
Compatible board images are available separately in the ESP32 firmware 0.8.14 prerelease. Its S3 8 MB, S3 4 MB, and C6 4 MB bundles have verified archive and image checksums. They have CI build and host-test coverage, with no new physical-board qualification.
Published by the npm release workflow from commit 0f95193190261a8966ad5f52e188aa6a480c2968. Registry signatures and the provenance attestation verified successfully and bind the downloaded tarball to this exact commit and workflow. The attached tarball is identical to the tested, published npm package; verify it with the attached SHA256SUMS.txt.
A fresh installation passed package-manifest, CLI, SDK, and read-only firmware-bundle checks for all three published board variants. No hardware operations were performed. No learning proposal or experimental Dream Machine candidate is promoted by this release.