multi-openim-channel 0.1.0

package/dist/friend-guard.js

@@ -0,0 +1,66 @@
+/**
+ * Optional shield for the OpenIM SDK's friend-relationship methods. When the
+ * channel-level `disableFriendSdk` flag is true (the default), every friend
+ * SDK method on a connected client is replaced by a throwing stub that
+ * surfaces a grep-able error code (`MULTI_OPENIM_FRIEND_API_DISABLED`).
+ *
+ * Use case: when an external system (your own backend, a CRM, a directory
+ * service, etc.) is the authoritative store for friend relationships,
+ * letting the SDK's friend methods run directly would split the source of
+ * truth and — under multi-account load — has been observed to raise
+ * uncaught rejections during token rotation. Operators who want raw SDK
+ * friend behavior can opt out per channel or per account via
+ * `disableFriendSdk: false`.
+ */
+import { logTag } from "./utils.js";
+export const FRIEND_API_DISABLED_CODE = "MULTI_OPENIM_FRIEND_API_DISABLED";
+const FRIEND_METHOD_NAMES = [
+    "addFriend",
+    "addFriendV2",
+    "applyFriend",
+    "acceptFriendApplication",
+    "refuseFriendApplication",
+    "deleteFriend",
+    "checkFriend",
+    "setFriendRemark",
+    "addBlack",
+    "removeBlack",
+    "getFriendApplicationListAsApplicant",
+    "getFriendApplicationListAsRecipient",
+    "getFriendApplicationList",
+    "getRecvFriendApplicationList",
+    "getSendFriendApplicationList",
+    "getFriendList",
+];
+export function applyFriendGuard(sdk, account, logger) {
+    if (!sdk)
+        return 0;
+    if (!account.disableFriendSdk) {
+        logger?.info?.(`${logTag("friend-guard")} account=${account.accountId} disableFriendSdk=false — leaving raw SDK friend APIs intact`);
+        return 0;
+    }
+    const sdkObj = sdk;
+    if (sdkObj.__multiOpenimFriendGuardApplied)
+        return 0;
+    let shimmed = 0;
+    for (const name of FRIEND_METHOD_NAMES) {
+        const current = sdkObj[name];
+        if (typeof current !== "function")
+            continue;
+        sdkObj[name] = async (..._args) => {
+            const message = `${FRIEND_API_DISABLED_CODE}: SDK ${name}() is disabled by multi-openim-channel` +
+                ` (account=${account.accountId}). Route friend operations through your own backend.`;
+            logger?.warn?.(`${logTag("friend-guard")} blocked SDK ${name}() on account=${account.accountId}`);
+            throw new Error(message);
+        };
+        shimmed++;
+    }
+    sdkObj.__multiOpenimFriendGuardApplied = true;
+    if (shimmed > 0) {
+        logger?.info?.(`${logTag("friend-guard")} account=${account.accountId}: shimmed ${shimmed} friend SDK method(s) (set disableFriendSdk=false to opt out)`);
+    }
+    return shimmed;
+}
+export function listGuardedMethods() {
+    return FRIEND_METHOD_NAMES;
+}

package/dist/inbound.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Inbound message dispatcher.
+ *
+ * Pipeline per message:
+ *   1. Filter (self-sent ignore, dedup, whitelist gating, group @-mention).
+ *   2. Extract a structured body (text + media items + quote unwrapping).
+ *   3. Optionally materialize image bytes for downstream multimodal agents.
+ *   4. Build a session key that always includes accountId for direct chats
+ *      so two accounts in the same conversation never collide.
+ *   5. Hand off to the host runtime's reply pipeline with a deliver()
+ *      callback that routes the agent reply back via the SDK.
+ */
+import type { MessageItem } from "@openim/client-sdk";
+import type { PluginContext } from "./context.js";
+import type { ClientState } from "./types.js";
+export declare function processInboundMessage(ctx: PluginContext, state: ClientState, msg: MessageItem): Promise<void>;
+export declare function _internal_clearInboundDedup(): void;