@mhome/app-facade-protocol 1.130.0 → 1.132.0

package/contract/automation-v1.md

@@ -26,3 +26,15 @@ Generated Twin and Group programs remain internal resources.
   rename. The script's authored root name remains available in the script itself.
 
 Inputs are closed objects. The schema is `schema/automation.v1.schema.json`.
+
+For `/app/automation/save` and `/app/automation/snapshot/rollback`, the definition
+is committed before the optional attempt to restore the enabled state. If that
+attempt is rejected or unconfirmed, the Facade returns `partial` with the
+Automation ID and `restoreIssue` (`failed` or `unconfirmed`). Rollback also
+includes the snapshot ID. Its `enabled` field is omitted when the post-write
+observation is unavailable. Read current state before deciding whether to enable.
+
+`/app/automation/delete` returns `success` when all targets complete and `partial`
+when `deletedIds` and `failedIds` both contain IDs. A batch with no completed
+targets returns `error` with its per-target details. These outcomes apply to direct
+calls and prepared commits, in Full and Essential presentation.

package/contract/dashboard-composition-v1.md

@@ -50,6 +50,18 @@ source and target Canvas documents together. Delete and resource cleanup prune
 leaf references: one surviving member becomes an independent Card at its current
 absolute position; zero members removes the container.
 
+`/app/dashboard/canvas/list` and `/app/dashboard/canvas/content/get` include
+`pendingDeletion: {canvas, itemIds}` when a Canvas has a staged deletion.
+`canvas: true` identifies a staged whole-Canvas deletion. For card deletions,
+`itemIds` contains the root or member IDs that were selected for deletion.
+The read field is omitted after cleanup finishes.
+
+Users can explicitly finish a staged deletion with `retryPending: true` on
+`/app/dashboard/canvas/delete` for that `canvasId`, or on
+`/app/dashboard/card/delete` with the selected pending `itemIds` as
+`cardIds`. The backend processes the requested pending targets. An already
+completed retry returns success with zero deletions.
+
 Existing data is converted explicitly with old writers stopped, a verified
 backup and conflict checks. Runtime startup never converts legacy placement or
 silently deletes a database. Cloud Canvas records stay in the existing `canvas`

package/contract/nfc-v1.md

@@ -33,8 +33,9 @@ Only activation changes pending to active and sets createdAt. Repeating activati
 preserves createdAt and lastUsedAt. Cancelled/failed physical writes explicitly
 delete pending; read/list/sync do not clean it up. No TTL or background cleanup.
 Update patches configuration without activating or resetting metadata.
-Delete missing IDs is idempotent, has no deleted-count guarantee, does not erase
-physical tags, and does not promise cross-record atomicity on cloud storage.
+Delete treats missing IDs as complete and returns an acknowledgement. SQLite and
+DynamoDB delete a request atomically. Tablestore batch deletion can partially
+apply before returning an error. Physical tags retain their written content.
 Prepared preview includes requested IDs, found state, name and creation state;
 last-use observations do not invalidate a preview.
 

package/manifest/app-facade.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.app-facade.v1",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "callSchema": "schema/facade-call.v1.schema.json",
   "routing": "manifest/routing.v1.json",
   "routingSchema": "schema/routing.v1.schema.json",

package/manifest/authorization.v1.json

@@ -1,5 +1,5 @@
 {
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "operations": {
     "/app/agent/context/get": "spaceRead",
     "/app/agent/credit/usage": "spaceRead",

package/manifest/host-provision-targets.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.host-provision.targets.v1",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "contract": "contract/host-provisioning-v1.md",
   "localTargets": [
     "/local/host/provision/start",

package/manifest/hub-targets.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.hub.targets.v1",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "appTargets": [
     "/app/hub/get",
     "/app/hub/remove"

package/manifest/pod-targets.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.pod.targets.v1",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "contract": "contract/pod-commissioning-v1.md",
   "localTargets": [
     "/local/pod/discovery/start",

package/manifest/routing.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.app-facade.routing.v1",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "targetPrefix": "/app/",
   "default": {
     "execution": "spaceMode"

package/manifest/targets.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.messaging.targets.v1",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "requestTargets": [
     "/app/messaging/provider/list",
     "/app/messaging/provider-account/list",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mhome/app-facade-protocol",
-  "version": "1.130.0",
+  "version": "1.132.0",
   "description": "Build-time protocol artifacts for mhome.app-facade",
   "license": "Apache-2.0",
   "repository": {

package/protocol.json

@@ -1,6 +1,6 @@
 {
   "protocol": "mhome.app-facade",
-  "contractVersion": "1.130.0",
+  "contractVersion": "1.132.0",
   "manifest": "manifest/app-facade.v1.json",
   "schemas": {
     "storage": "schema/storage.v1.schema.json",