@mhome/core-protocol 1.10.0 → 1.12.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -0
- package/manifest/core.v1.json +1 -1
- package/package.json +1 -1
- package/protocol.json +1 -1
package/README.md
CHANGED
|
@@ -49,3 +49,17 @@ Messaging returns the same typed outcome, not a delivered boolean. Skipped means
|
|
|
49
49
|
handled without a send and must not be reported as provider acceptance.
|
|
50
50
|
There is no old-protocol compatibility path. Consumers must upgrade together;
|
|
51
51
|
version 1.7.1 must be published before updating registry-backed consumer locks.
|
|
52
|
+
|
|
53
|
+
## Host contracts (core-api 1.11.0)
|
|
54
|
+
|
|
55
|
+
`core_api::host` is the single owner of Host hardware information, installed
|
|
56
|
+
service inventory, system/service metrics, and OS permission declarations and
|
|
57
|
+
observations. It replaces the independent `mhome-host-api` crate. App Facade
|
|
58
|
+
reuses these types and owns its public routing and observation envelopes. Importing
|
|
59
|
+
this module does not require a running Core or a Space.
|
|
60
|
+
|
|
61
|
+
Host/Client producers and readers must use these DTOs rather than redeclare
|
|
62
|
+
matching JSON structures. Platform collectors may keep private sampling structs;
|
|
63
|
+
only the canonical DTOs cross HTTP/IPC boundaries. The permissions contract is in
|
|
64
|
+
`contract/host-permissions.md`; runtime permission handlers remain a separate
|
|
65
|
+
implementation step. The existing Core external runtime protocol stays at 15.
|
package/manifest/core.v1.json
CHANGED
package/package.json
CHANGED