Release: https://github.com/ruvnet/RuView/releases/tag/v2051
Merged PR: ruvnet/RuView#1451
Merge commit: 42d56fc1a5cea50c48f8c191ae5aeee1fee29807
- Server-side plugin runtime:
- bounded directory discovery and manifest validation
- Ed25519 publisher-signature trust policy
- compiled-in native plugin registration
- Wasmtime 36.0.12 component loading
- setup, state-change, and teardown lifecycle integration
- Network HomeKit Accessory Protocol:
- persistent accessory identity and pairing state
- SRP-6a Pair-Setup and X25519/Ed25519 Pair-Verify
- ChaCha20-Poly1305 encrypted HAP/IP records
- controller pairing administration and live revocation
- TCP serving, state synchronization, and mDNS advertisement
- Home Assistant compatibility:
- core REST states, services, events, templates, configuration, history, logbook, calendars, and camera fallback
- authenticated WebSocket commands, subscriptions, registries, panels, and supported-feature reporting
- machine-readable
/api/homecore/compatibilitycontract
- Deterministic registry and recorder restore during startup.
- Forward-compatible device/config-entry migrations with unknown-field preservation.
- Bounded STT/TTS provider interfaces and authenticated satellite voice sessions.
cd v2
cargo build -p homecore-server --release --features wasmtime,hap-serverThe HAP server is opt-in. On first provisioning, supply a stable device ID and setup code using the documented server flags or secret environment inputs. The persisted store retains the verifier rather than the plaintext setup code.
- Plugin/Wasmtime: 35 tests passed
- HAP: 45 tests passed, including encrypted TCP access and replay rejection
- All-feature server: 22 tests passed
- HOMECORE core, migration, recorder, assist, REST, authentication, and WebSocket suites passed
- Strict clippy passed for all changed crates/features on Rust 1.89
- Optimized all-feature release build passed
- HOMECORE covers its documented core Home Assistant REST/WebSocket compatibility manifest, not every third-party integration or frontend-specific extension.
- HAP has not received Apple certification or current external-controller interoperability testing.
- Timed HAP writes,
/resource, persisted stable AID/IID allocation, and hardware-backed key storage remain future work. - Arbitrary native dynamic libraries are intentionally not loaded; native plugins must be compiled into the server registry.
- Remaining monorepo audit findings are outside the enabled HOMECORE server dependency graph.