@mhome/core-protocol 1.7.1 → 1.8.0

package/README.md

@@ -21,6 +21,14 @@ Storage separates backing-filesystem capacity from Storage-owned logical
 usage. Namespace is an internal protocol term; user-facing clients present it
 as a Folder.
 
+## Stable recipients (core-api 1.8.0)
+
+`RecipientId` provides canonical Messaging (`m:p:` / `m:g:`) and Node (`n:`)
+addresses. See [the contract](contract/recipient-id-v1.md) and the packaged
+cross-language [conformance vectors](fixtures/recipient-id.conformance.json).
+This is additive; the external Host transport protocol remains version 14.
+Consumers must explicitly migrate their identities after this release is available.
+
 ## Host delivery (core-api 1.7.1)
 
 Core resolves logical recipients; the Host executes a concrete App connection,

package/contract/recipient-id-v1.md

@@ -0,0 +1,36 @@
+# Stable recipient identity
+
+These identities address recipients, not WebSocket sessions or Agent conversations.
+Tenant and Space are required routing context outside the identity. Cloud/local
+placement is a route property, never a prefix or an identity component.
+
+| Recipient | Canonical representation |
+| --- | --- |
+| Personal Messaging conversation | `m:p:<provider>:<account>:<conversation>[:<lane>]` |
+| Shared Messaging conversation | `m:g:<provider>:<account>:<conversation>[:<lane>]` |
+| Node | `n:<nodeType>:<nodeId>` |
+
+Account, conversation, lane and Node ID are strict UTF-8 encoded as canonical
+unpadded base64url. Empty values and surrounding whitespace are invalid. Provider
+and Node type match `[a-z][a-z0-9_]*`; wire parsing must reject noncanonical input.
+
+Messaging uses exactly the same address components as ConversationSurface. The
+conversion between `m:p:` / `m:g:` and `cs1:mp:` / `cs1:mg:` preserves every
+component, including lane. Generate both from one structured address; do not store
+two independently editable addresses. A base authorization lookup may omit lane,
+but the actual recipient must retain it. Personal and shared identities never
+collapse into one another.
+
+Node identity resolves against the existing scoped Node registry. It does not
+create an App Client, a second registry, or a WebSocket. Node capability/endpoint
+selection remains a separate field. Connection close still addresses a specific
+connection, not a stable Node identity.
+
+App installation selectors (`a:`), user selectors, connection IDs (`L:` / `C:`),
+and Phone Provider credentials (`p:`) are outside this codec. In particular, `p:`
+is not a personal Messaging recipient; only `m:p:` is. The codec does not accept
+legacy `M:` IDs or ConversationSurface IDs as recipient IDs.
+
+Cross-language implementations must pass `fixtures/recipient-id.conformance.json`.
+This additive Foundation release prepares consumers for a coordinated identity
+cutover; it does not itself migrate Core/Lion storage or delivery adapters.

package/fixtures/recipient-id.conformance.json

@@ -0,0 +1,9 @@
+{
+  "valid": [
+    {"id":"m:p:telegram:Ym90:Y2hhdA","surface":"cs1:mp:telegram:Ym90:Y2hhdA"},
+    {"id":"m:g:telegram:Ym90:Y2hhdA:dG9waWM","surface":"cs1:mg:telegram:Ym90:Y2hhdA:dG9waWM"},
+    {"id":"m:g:feishu:YWNjb3VudA:Y29udmVyc2F0aW9u","surface":"cs1:mg:feishu:YWNjb3VudA:Y29udmVyc2F0aW9u"},
+    {"id":"n:camera:bm9kZTox","nodeType":"camera","nodeId":"node:1"}
+  ],
+  "invalid": ["", "a:device", "p:provider", "L:socket", "C:peer:socket", "M:telegram:Ym90:Y2hhdA", "cs1:mp:telegram:Ym90:Y2hhdA", "m:x:telegram:Ym90:Y2hhdA", "m:p:telegram:Ym90=:Y2hhdA", "m:p:telegram::Y2hhdA", "m:p:telegram:Ym90:Y2hhdA:", "n:Camera:bm9kZQ", "n:camera:", "n:camera:bm9kZQ==", "n:camera:_w", "n:camera:IG5vZGU", "n:camera:bm9kZQ:extra"]
+}

package/manifest/core.v1.json

@@ -1,6 +1,6 @@
 {
   "manifest": "mhome.core.v1",
-  "contractVersion": "1.7.1",
+  "contractVersion": "1.8.0",
   "protocols": {
     "agentGateway": {
       "submitTarget": "/agent/submit",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mhome/core-protocol",
-  "version": "1.7.1",
+  "version": "1.8.0",
   "description": "Build-time protocol artifacts for mhome.core",
   "license": "MIT",
   "repository": {

package/protocol.json

@@ -1,6 +1,6 @@
 {
   "protocol": "mhome.core",
-  "contractVersion": "1.7.1",
+  "contractVersion": "1.8.0",
   "manifest": "manifest/core.v1.json",
   "schemas": {
     "normalizedInbound": "schema/normalized-inbound.v4.schema.json",
@@ -12,6 +12,7 @@
     "normalizedInbound": "fixtures/normalized-inbound.conformance.json",
     "messagingCommands": "fixtures/messaging-commands.conformance.json",
     "interactionFlowNode": "fixtures/interaction-flow-node.conformance.json",
-    "cameraPluginManagement": "fixtures/camera-plugin-management.conformance.json"
+    "cameraPluginManagement": "fixtures/camera-plugin-management.conformance.json",
+    "recipientId": "fixtures/recipient-id.conformance.json"
   }
 }