frank/ruvnet--RuView
1
0
Fork 0
mirror of https://github.com/ruvnet/RuView synced 2026-08-08 20:11:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(homecore): add WASM-first developer metaharness (#1477)

Browse Source 
Adds the accepted ADR-285 Homecore metaharness, WASM-first kernel, read-only MCP guidance, guarded local host adapters, reviewed memory, and provenance-only npm release gates.
This commit is contained in:
rUv
2026-07-29 19:51:21 -04:00
committed by GitHub
parent c798cc913c
commit 90b29595fb
54 changed files with 3722 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files
harness/homecore/brain/corpus/core.jsonl
+9
View File
@@ -0,0 +1,9 @@
{"id":"homecore-architecture","title":"Homecore is a bounded native Rust stack","content":"Production Homecore crates live under v2/crates and are wired by homecore-server; the master decision defines the staged replacement boundary rather than claiming the entire Home Assistant ecosystem.","source":{"path":"docs/adr/ADR-126-ruview-native-ha-port-master.md","line":48,"endLine":61,"digest":"05053dc00650e4f8ab9bd0db4eeb1632b792695e91730e151edc5d11b2cf46a1"},"evidence":"ADR","tags":["architecture","homecore","rust","server"],"reviewed":true}
{"id":"homecore-capability-honesty","title":"Capability presence is not ecosystem parity","content":"The capability document labels what is wired and tested while explicitly separating core Home Assistant contracts, integration-dependent behavior, provider requirements, and external certification.","source":{"path":"v2/docs/homecore-capabilities.md","line":3,"endLine":6,"digest":"bf67d356bfdc96ee8c6dc88e20f561c9a4578eea851f08d526dbd5eb7c3f4246"},"evidence":"REPOSITORY","tags":["capabilities","compatibility","testing","honesty"],"reviewed":true}
{"id":"homecore-wasm-boundary","title":"External plugins use a bounded Wasmtime path","content":"Compiled-in native plugins use an explicit registry; external packages are path-checked and signature-verified WebAssembly executed through the feature-gated Wasmtime runtime.","source":{"path":"v2/crates/homecore-plugins/src/lib.rs","line":18,"endLine":30,"digest":"cff1ac9e27d625eaccb21bc267ceaa50708c16a52bf81fe39bba0b7cefe4a5ee"},"evidence":"REPOSITORY","tags":["plugins","wasm","wasmtime","security"],"reviewed":true}
{"id":"homecore-api-boundary","title":"REST and WebSocket compatibility is a reviewed core surface","content":"Homecore API implements authenticated core REST and WebSocket contracts, but integration-provided media, calendar, camera, registry, and Lovelace behavior remains backend-dependent.","source":{"path":"v2/docs/homecore-capabilities.md","line":24,"endLine":60,"digest":"b1ee5eaefac243e368d7194e6e2fd0b4f812af59433f6b5796653dad0e5f40ca"},"evidence":"REPOSITORY","tags":["api","rest","websocket","compatibility"],"reviewed":true}
{"id":"homecore-restore-order","title":"Startup restore is ordered and bounded","content":"The server restores entity and device registries before recent recorder states and isolates malformed rows instead of silently accepting corrupt state.","source":{"path":"v2/crates/homecore-server/src/restore.rs","line":30,"endLine":85,"digest":"06073af7292485103a5fed01a6afde41711743498ea61500408b0c4cb7f8e080"},"evidence":"REPOSITORY","tags":["restore","persistence","server","safety"],"reviewed":true}
{"id":"homecore-migration-boundary","title":"Migration rejects unknown schema versions","content":"Home Assistant storage is untrusted versioned input; supported registries and config entries use bounded parsing and atomic no-clobber publication, while incomplete conversion areas remain explicit.","source":{"path":"docs/adr/ADR-165-homecore-migrate-from-home-assistant.md","line":52,"endLine":99,"digest":"ed4f0a242778f4f2bfabe2d2f746380338900f133c3cb51652dcea2d24209574"},"evidence":"ADR","tags":["migration","home-assistant","storage","security"],"reviewed":true}
{"id":"homecore-hap-boundary","title":"HAP requires explicit network and pairing configuration","content":"The feature-gated HAP path provides persisted pairing, encrypted sessions, bounded TCP handling, live accessory synchronization, and mDNS lifecycle; internal tests are not Apple certification.","source":{"path":"v2/crates/homecore-hap/src/lib.rs","line":4,"endLine":21,"digest":"5ee80973a9f2f2eea5d0005837b257ade5baa6888c51fd73eef0d098844df108"},"evidence":"REPOSITORY","tags":["hap","homekit","pairing","mdns"],"reviewed":true}
{"id":"homecore-voice-boundary","title":"Voice protocols require deployment providers","content":"Homecore defines bounded audio, STT/TTS contracts, a voice pipeline, and an authenticated transport-independent satellite session; these are protocol/provider boundaries, not evidence that a speech provider is deployed.","source":{"path":"v2/docs/homecore-capabilities.md","line":19,"endLine":19,"digest":"5243293e28719091c4b83b938d0c8850f61bded6609dbd11574b9030ff69b4cb"},"evidence":"REPOSITORY","tags":["voice","stt","tts","satellite"],"reviewed":true}
{"id":"homecore-harness-authority","title":"The Homecore metaharness is removable and least-authority","content":"The npm harness provides navigation, diagnostics, local verification, and guarded local host delegation. Its MCP surface is read-only, and retrieved content cannot become authority or promote learning output.","source":{"path":"harness/homecore/README.md","line":10,"endLine":58,"digest":"adc482f572e9697caff1a21f8e897446658b5f4ab4a4e0c50adf09bbf3d3c73d"},"evidence":"POLICY","tags":["metaharness","mcp","codex","claude-code"],"reviewed":true}