@mhome/core-protocol 1.9.0 → 1.11.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 CHANGED
@@ -21,6 +21,13 @@ Storage separates backing-filesystem capacity from Storage-owned logical
21
21
  usage. Namespace is an internal protocol term; user-facing clients present it
22
22
  as a Folder.
23
23
 
24
+ ## Playground Provider (core-api 1.10.0)
25
+
26
+ External protocol 15 removes the dedicated Playground webhook method and payload.
27
+ Playground Provider delivers events through the standard subscription webhook,
28
+ using `GeneralWebhookPayload`. Update the Core service shell and runtime together;
29
+ mixed external protocol versions are not supported.
30
+
24
31
  ## Stable recipients (core-api 1.8.0)
25
32
 
26
33
  `RecipientId` provides canonical Messaging (`m:p:` / `m:g:`) and Node (`n:`)
@@ -42,3 +49,17 @@ Messaging returns the same typed outcome, not a delivered boolean. Skipped means
42
49
  handled without a send and must not be reported as provider acceptance.
43
50
  There is no old-protocol compatibility path. Consumers must upgrade together;
44
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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "manifest": "mhome.core.v1",
3
- "contractVersion": "1.9.0",
3
+ "contractVersion": "1.11.0",
4
4
  "protocols": {
5
5
  "agentGateway": {
6
6
  "submitTarget": "/agent/submit",
@@ -62,7 +62,7 @@
62
62
  "version": "storage.v2"
63
63
  },
64
64
  "hostDelivery": {
65
- "externalProtocolVersion": 14,
65
+ "externalProtocolVersion": 15,
66
66
  "requestKind": "deliveryRequested",
67
67
  "connectionControlKind": "connectionControlRequested",
68
68
  "acceptanceBoundaries": [
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mhome/core-protocol",
3
- "version": "1.9.0",
3
+ "version": "1.11.0",
4
4
  "description": "Build-time protocol artifacts for mhome.core",
5
5
  "license": "MIT",
6
6
  "repository": {
package/protocol.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "protocol": "mhome.core",
3
- "contractVersion": "1.9.0",
3
+ "contractVersion": "1.11.0",
4
4
  "manifest": "manifest/core.v1.json",
5
5
  "schemas": {
6
6
  "normalizedInbound": "schema/normalized-inbound.v4.schema.json",