@gaodefa/daocore 2026.5.75 → 2026.5.76

package/dist/{pairing-challenge-EwSQYSud.d.ts → pairing-store-Cfy_zHzi.d.ts}

@@ -1,6 +1,39 @@
 import { t as ChannelPairingAdapter } from "./pairing.types-B8gJXl1a.js";
 import { t as PairingChannel } from "./pairing-store.types-BcORBxth.js";
 
+//#region src/pairing/pairing-challenge.d.ts
+type PairingMeta = Record<string, string | undefined>;
+type PairingChallengeParams = {
+  channel: string;
+  senderId: string;
+  senderIdLine: string;
+  meta?: PairingMeta;
+  upsertPairingRequest: (params: {
+    id: string;
+    meta?: PairingMeta;
+  }) => Promise<{
+    code: string;
+    created: boolean;
+  }>;
+  sendPairingReply: (text: string) => Promise<void>;
+  buildReplyText?: (params: {
+    code: string;
+    senderIdLine: string;
+  }) => string;
+  onCreated?: (params: {
+    code: string;
+  }) => void;
+  onReplyError?: (err: unknown) => void;
+};
+/**
+ * Shared pairing challenge issuance for DM pairing policy pathways.
+ * Ensures every channel follows the same create-if-missing + reply flow.
+ */
+declare function issuePairingChallenge(params: PairingChallengeParams): Promise<{
+  created: boolean;
+  code?: string;
+}>;
+//#endregion
 //#region src/pairing/pairing-store.d.ts
 type PairingRequest = {
   id: string;
@@ -51,37 +84,4 @@ declare function approveChannelPairingCode(params: {
   entry?: PairingRequest;
 } | null>;
 //#endregion
-//#region src/pairing/pairing-challenge.d.ts
-type PairingMeta = Record<string, string | undefined>;
-type PairingChallengeParams = {
-  channel: string;
-  senderId: string;
-  senderIdLine: string;
-  meta?: PairingMeta;
-  upsertPairingRequest: (params: {
-    id: string;
-    meta?: PairingMeta;
-  }) => Promise<{
-    code: string;
-    created: boolean;
-  }>;
-  sendPairingReply: (text: string) => Promise<void>;
-  buildReplyText?: (params: {
-    code: string;
-    senderIdLine: string;
-  }) => string;
-  onCreated?: (params: {
-    code: string;
-  }) => void;
-  onReplyError?: (err: unknown) => void;
-};
-/**
- * Shared pairing challenge issuance for DM pairing policy pathways.
- * Ensures every channel follows the same create-if-missing + reply flow.
- */
-declare function issuePairingChallenge(params: PairingChallengeParams): Promise<{
-  created: boolean;
-  code?: string;
-}>;
-//#endregion
-export { approveChannelPairingCode as a, readChannelAllowFromStore as c, readLegacyChannelAllowFromStoreSync as d, removeChannelAllowFromStoreEntry as f, addChannelAllowFromStoreEntry as i, readChannelAllowFromStoreSync as l, upsertChannelPairingRequest as m, issuePairingChallenge as n, clearPairingAllowFromReadCacheForTest as o, resolveChannelAllowFromPath as p, PairingRequest as r, listChannelPairingRequests as s, PairingChallengeParams as t, readLegacyChannelAllowFromStore as u };
+export { listChannelPairingRequests as a, readLegacyChannelAllowFromStore as c, resolveChannelAllowFromPath as d, upsertChannelPairingRequest as f, clearPairingAllowFromReadCacheForTest as i, readLegacyChannelAllowFromStoreSync as l, issuePairingChallenge as m, addChannelAllowFromStoreEntry as n, readChannelAllowFromStore as o, PairingChallengeParams as p, approveChannelPairingCode as r, readChannelAllowFromStoreSync as s, PairingRequest as t, removeChannelAllowFromStoreEntry as u };

package/dist/plugin-sdk/.boundary-entry-shims.stamp

@@ -1 +1 @@
-2026-05-27T05:00:34.539Z
+2026-05-27T09:22:29.516Z