@mhome/app-facade-protocol 1.61.0 → 1.64.0

package/README.md

@@ -73,7 +73,10 @@ App UI requests full and unwraps the envelope at its transport boundary. Agent
 and MCP public results use essential; internal workflow reads use full. The CLI
 uses `--response-detail full|essential`, and the bundled external Skill requests
 essential. Dashboard essential projection keeps card identity, title, type,
-layouts and view choices, excluding renderer configuration and resource payloads.
+view choices, excluding renderer configuration and resource payloads. Card list
+returns only ID/type/title; card detail essential omits layouts. Canvas layout get
+requires one sm/md/lg size and retains every card ID/title/layout in full and essential;
+uninitialized layouts or coordinates are null.
 Device brief-list essential retains identity, room, capability IDs, Integration and
 availability, omitting `connectId`, `manufacturerId` and `manufacturerName`.
 Selected Device detail, history, recent activity and mutation outcomes keep their
@@ -96,6 +99,10 @@ asset manifests and renderer configuration schemas. Selected release detail keep
 Revisions, installation IDs, existing override config and supported patterns remain.
 Empty mutation acknowledgements remain empty; they do not invent a new revision.
 
+Room uses one `/app/room/list` read. Every Room has `roomId`, `roomName`,
+`index`, `deviceCount`, and `deviceIds`; full and essential keep all five fields.
+Membership IDs include Device groups without expanding their members or state.
+
 Targets without a dedicated projection retain their business fields in YAML;
 essential does not promise a smaller field set for every domain. Targets own that selection.
 

package/contract/entity-presentation-v1.md

@@ -0,0 +1,22 @@
+# Entity UI presentation
+
+`/app/entity/presentation/get` is a read-only App Facade for the UI. Its direct
+input is `{entityType, entityId}`; tenant, Space and caller come from authenticated
+context. It requires Space read access. It is not an Agent or MCP catalog entry.
+
+The successful data object contains `entityEntry`, nullable `entityCard`, and
+`twinAutomations`. The entry and card reuse the existing UI renderer models;
+the schema owns this boundary without duplicating their nested widget/runtime
+contracts. A missing, deleted or differently typed Twin is not found. Device
+presentation reads reuse the device manager; other Twin entities reuse the general
+manager. Ordinary Entity business detail and Group detail retain their own APIs.
+
+Device card assembly is best effort. An absent card is `null`, with an empty
+association list. Association-read failures retain the existing execution policy:
+local Core returns an empty list; cloud propagates the error. No writes or repairs
+are performed. Current Twin states still have their separate read/subscription.
+
+UI uses `control: {mode: "direct", responseDetail: "full"}` and receives the shared
+`{status: "success", data: ...}` envelope. The generic essential projection returns
+`{status: "success", text: ...}` with the same business fields rendered as YAML;
+there is no domain field reduction. This is not the compact business detail API.

package/contract/pod-directory-v1.md

@@ -13,11 +13,11 @@ bridge. A cloud Space composes it in cloud. LLM placement does not change this
 owner. Cloud entrypoints forward local-Space business to Core; only an unavailable
 Hub transport permits the explicit read-only registration fallback below.
 
-The result contains `pods`, `scopeId`, `observedAtMs`, and `sourceErrors`.
+The result contains `pods`, `spaceId`, `observedAtMs`, and `sourceErrors`.
 Every row contains `registrationId`, `clientMode` (`user` or `space`), `registered`
-(true), and `connection` with `scopeId`, `state` (`connected`, `disconnected`, or
+(true), and `connection` with `spaceId`, `state` (`connected`, `disconnected`, or
 `unknown`), and `source` (`hub`, `cloud`, or `unavailable`). Space rows also contain
-`scopeId` and `appClientId`. Personal rows contain the saved `name`, `deviceId`,
+`spaceId` and `appClientId`. Personal rows contain the saved `name`, `deviceId`,
 `model`, `platform`, `firmwareVersion`, `issuedAt`, and `activatedAt`.
 No tokens, enrollment grants, credential IDs or private keys are returned.
 

package/fixtures/binding-list.response.json

@@ -9,7 +9,7 @@
         "placement": "local",
         "accountId": "bot",
         "conversationId": "group",
-        "scopeId": "home",
+        "spaceId": "home",
         "displayName": "Family",
         "createdAtMs": 1
       }

package/fixtures/entity-presentation.conformance.json

@@ -0,0 +1,54 @@
+{
+  "input": {
+    "valid": [
+      {
+        "entityType": "basic.device.Device",
+        "entityId": "device-1"
+      }
+    ],
+    "invalid": [
+      {},
+      {
+        "entityType": " ",
+        "entityId": "device-1"
+      },
+      {
+        "entityType": "basic.device.Device",
+        "entityId": ""
+      },
+      {
+        "entityType": "basic.device.Device",
+        "entityId": "device-1",
+        "scopeId": "other"
+      }
+    ]
+  },
+  "output": {
+    "valid": [
+      {
+        "entityEntry": {
+          "uid": "device-1",
+          "type": "basic.device.Device",
+          "integration": "example.device",
+          "name": "Desk lamp",
+          "active": false,
+          "data": {},
+          "capabilities": [],
+          "twinTags": [],
+          "cardCount": 0,
+          "issue": false
+        },
+        "entityCard": null,
+        "twinAutomations": []
+      }
+    ],
+    "invalid": [
+      {},
+      {
+        "entityEntry": null,
+        "entityCard": null,
+        "twinAutomations": []
+      }
+    ]
+  }
+}

package/fixtures/hub-state.configured.json

@@ -1,5 +1,5 @@
 {
-  "scopeId": "scope-1",
+  "spaceId": "scope-1",
   "configured": true,
   "hub": {
     "id": "hub-1",

package/fixtures/hub-state.revoked.json

@@ -1,5 +1,5 @@
 {
-  "scopeId": "scope-1",
+  "spaceId": "scope-1",
   "configured": false,
   "operation": {
     "kind": "REMOVE",