@opencxh/domain 1.221.0 → 1.224.0

package/dist/platform/communication.d.ts

@@ -510,6 +510,24 @@ export type ServerOp = {
     channelId: string;
     interactionId: string;
     body: NoteBody;
+}
+/**
+ * Put an emoji on a message at the provider, or take it off.
+ *
+ * Only dispatched to a provider that declares the `message_reactions` feature — everywhere
+ * else the reaction stays ours alone, which is the honest outcome for a channel whose
+ * protocol has no such thing (mail).
+ *
+ * `emoji` is the literal character. Providers that speak their own vocabulary translate at
+ * their own edge; a reaction means the same thing on every channel and should read the same.
+ */
+ | {
+    kind: "message.react";
+    channelId: string;
+    activityId: string;
+    emoji: string;
+    /** `true` sets it, `false` removes it. */
+    on: boolean;
 } | {
     kind: "message.forward";
     channelId: string;
@@ -640,6 +658,13 @@ export declare const FEATURE_FOLDER_MANAGEMENT = "folder_management";
  * channels in `GET /search/sources`; the client fans out via `POST /search/mailbox`.
  */
 export declare const FEATURE_REMOTE_SEARCH = "remote_search";
+/**
+ * Well-known `ProviderFeature.name` for per-message emoji reactions. A provider that can both
+ * report the reactions on a message and set one on the user's behalf declares it true; the
+ * comm-server then dispatches `message.react` there. Everywhere else the reaction is ours
+ * alone, which is the honest outcome for a protocol that has no such thing (mail).
+ */
+export declare const FEATURE_MESSAGE_REACTIONS = "message_reactions";
 /**
  * Result shape for `IProvider.dispatch` and the comm-server
  * `dispatchToProvider` helper, discriminated on `ok`. Deliberately not

package/dist/platform/documents.d.ts

@@ -84,6 +84,15 @@ export interface DocumentCapability {
     title: string;
     /** Someone else holds the lock, or a write-back would drop content, or it is read-only. */
     readOnly: boolean;
+    /**
+     * Is the document parsed and answerable, or still loading?
+     *
+     * A separate field because the page knows what the file *is* (name, kind, which operations
+     * apply) the moment it opens, while the engine needs a second or two to parse it. Without the
+     * distinction a consumer cannot tell "no content" from "not yet", and a model told the first
+     * reports an empty document.
+     */
+    ready: boolean;
     /** What a write-back would lose, from the editor's own `unsupportedFeatures`. */
     blocked: string[];
     /** The subset of {@link DOCUMENT_OPERATIONS} this mounted editor actually implements. */

package/dist/platform/permission.d.ts

@@ -18,7 +18,7 @@ export declare const APP_PERMISSIONS: {
     readonly "app-store": readonly ["app.publish", "app.read", "app.write", "setting.read", "setting.write"];
     readonly assist: readonly ["board.read"];
     readonly automations: readonly ["sync.read", "sync.write", "webhook.read", "webhook.write"];
-    readonly communication: readonly ["account.read", "account.write", "activity-type.read", "activity.read", "activity.write", "attachment.read", "attribute.read", "attribute.write", "calendar.read", "calendar.write", "channel.read", "channel.write", "custom-field.read", "custom-field.write", "folder.read", "folder.write", "inbox.read", "inbox.write", "interaction.read", "interaction.write", "reminder.read", "template.read", "template.write", "topic.read", "topic.write"];
+    readonly communication: readonly ["account.read", "account.write", "activity-type.read", "activity.read", "activity.write", "attachment.read", "attribute.read", "attribute.write", "calendar.read", "calendar.write", "channel.read", "channel.write", "custom-field.read", "custom-field.write", "folder.read", "folder.write", "inbox.read", "inbox.write", "interaction.read", "interaction.write", "reaction.read", "reaction.write", "reminder.read", "template.read", "template.write", "topic.read", "topic.write"];
     readonly context: readonly ["kind.read", "kind.write", "memory.read", "memory.write"];
     readonly crm: readonly ["company.read", "company.write", "contact.read", "contact.write"];
     readonly "eylo-voip": readonly ["account.read", "account.write", "callflow.read", "callflow.write", "channel.read", "channel.write", "contact.read", "contact.write", "device.read", "device.write", "group.read", "group.write", "interaction.read", "interaction.write", "media.read", "media.write", "menu.read", "menu.write", "phone-number.read", "phone-number.write", "recording.read", "recording.write", "sip.read", "temporal-rule.read", "temporal-rule.write", "user.read", "user.write", "vmbox.read", "vmbox.write", "webhook.read", "webhook.write"];

package/dist/platform/resource-source.d.ts

@@ -161,6 +161,30 @@ export interface Relation {
     createdBy: string;
     createdAt?: number;
 }
+/**
+ * One resource a single person keeps in reach, stored by apps/context.
+ *
+ * **Private by construction.** `userId` comes from the session, never from the body, so a pin is
+ * not an org-wide fact about the resource — which is exactly why it is not a {@link Relation}:
+ * relations are merged into `/resource/related` and would surface everyone's pins in a customer
+ * file. Nothing reads another user's pins.
+ *
+ * `label` and `icon` are **snapshots**, used cold: a pinned conversation from three months ago is
+ * not in any list the screen loaded, so without them the row has no name. Whoever renders it
+ * lets the live value win when the resource is at hand.
+ */
+export interface Pin {
+    id: string;
+    organizationId: string;
+    userId: string;
+    /** `<kind>:<ref>` — the same key vocabulary as {@link ResourceSummary} and {@link Relation}. */
+    scopeKey: string;
+    /** Title snapshot. See the note above. */
+    label: string;
+    /** Icon hint the owning app understands (comms stores the channel scheme). */
+    icon?: string;
+    createdAt?: number;
+}
 /**
  * What the hub asks one app. `scopeKey` is already authorized — the answering app must not
  * re-gate it, but it must filter its own rows for the stamped acting identity.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@opencxh/domain",
-  "version": "1.221.0",
+  "version": "1.224.0",
   "type": "module",
   "main": "./dist/index.js",
   "module": "./dist/index.js",