Per iter-10 security audit (docs/security/HOMECORE-security-audit-iter10.md):
sqlx 0.7.4 ships an advisory for binary protocol misinterpretation.
Bump to 0.8.1+ — cargo resolved to 0.8.6.
Feature set unchanged (default-features = false +
runtime-tokio-native-tls, sqlite, chrono, uuid). Tests still pass:
cargo test -p homecore-recorder --features ruvector
→ 20 passed; 0 failed
No code changes required. The 0.7 → 0.8 API surface we touch in
`db.rs` is stable across the bump.
Deferred to a later iter:
- shlex 0.1.1 → ≥1.3.0 (transitive via wasm3-sys, only on
--features wasm3 which is default-off; will be addressed when
the wasm3 path is removed per ADR-128 Q2 Wasmtime resolution)
- wasmtime 25 → 36+/42+ (HC-03/04 CVSS 9.0 sandbox-escape) — being
handled by a background coder agent this iter, separate commit.
Refs: docs/security/HOMECORE-security-audit-iter10.md (HC-09 sqlx)
Refs: #798
Co-Authored-By: claude-flow <ruv@ruv.net>
- SQLite-backed state history with HA-compat schema (states, state_attributes,
events, recorder_runs) mirroring recorder schema v48
- FNV-1a 64-bit attribute deduplication matching HA's db_schema.py fnv64a
- RecorderListener subscribes to StateMachine broadcast and persists every
state change; subscription created at construction to avoid missed events
- SemanticIndex trait + NullSemanticIndex for P1; ruvector-backed impl stub
feature-gated behind --features ruvector for P2 hand-off
Co-Authored-By: claude-flow <ruv@ruv.net>
ruv