@ever-works/discord-connector-plugin 1.0.0

package/dist/index.d.cts

@@ -0,0 +1,36 @@
+import { IConnectorPlugin, PluginCategory, ConnectorMetadata, JsonSchema, ChannelTargetConfig, ConnectorCallOptions, ChannelVerification, ChannelSendInput, ChannelSendResult } from '@ever-works/plugin';
+
+/**
+ * Discord connector — a first-party BIDIRECTIONAL connector. This
+ * increment implements the OUTBOUND leg: it posts messages to a Discord
+ * channel with a bot token via `POST /channels/:id/messages` on the
+ * official `discord.js` `REST` client (distinct from `discord-channel`'s
+ * incoming-webhook `fetch` path — a connector is a superset of a channel).
+ *
+ * Inbound (Discord Interactions API: `verifyInbound` Ed25519 signature
+ * verification over `X-Signature-Ed25519` + `X-Signature-Timestamp`,
+ * `handleChallenge` for the `PING` handshake, `parseInbound` → route to an
+ * Agent, `reply` into the channel) is a follow-up (P2) — the `publicKey`
+ * setting is captured now so the connection is inbound-ready. Metadata
+ * therefore declares `direction: 'outbound'` with `inbound`/`reply`/
+ * `pairing` flags off until that runtime lands.
+ *
+ * See `docs/specs/features/connectors/spec.md` §7.5.1.
+ */
+declare class DiscordConnectorPlugin implements IConnectorPlugin {
+    readonly id = "discord-connector";
+    readonly name = "Discord Connector";
+    readonly version = "1.0.0";
+    readonly category: PluginCategory;
+    readonly capabilities: readonly ["connector", "connector-discord"];
+    readonly connector: ConnectorMetadata;
+    readonly settingsSchema: JsonSchema;
+    private readonly idempotencyCache;
+    onLoad(): Promise<void>;
+    onUnload(): Promise<void>;
+    verifyConnection(config: ChannelTargetConfig, _options: ConnectorCallOptions): Promise<ChannelVerification>;
+    send(payload: ChannelSendInput, options: ConnectorCallOptions): Promise<ChannelSendResult>;
+}
+declare const discordConnectorPlugin: DiscordConnectorPlugin;
+
+export { DiscordConnectorPlugin, discordConnectorPlugin };

package/dist/index.d.ts

@@ -0,0 +1,36 @@
+import { IConnectorPlugin, PluginCategory, ConnectorMetadata, JsonSchema, ChannelTargetConfig, ConnectorCallOptions, ChannelVerification, ChannelSendInput, ChannelSendResult } from '@ever-works/plugin';
+
+/**
+ * Discord connector — a first-party BIDIRECTIONAL connector. This
+ * increment implements the OUTBOUND leg: it posts messages to a Discord
+ * channel with a bot token via `POST /channels/:id/messages` on the
+ * official `discord.js` `REST` client (distinct from `discord-channel`'s
+ * incoming-webhook `fetch` path — a connector is a superset of a channel).
+ *
+ * Inbound (Discord Interactions API: `verifyInbound` Ed25519 signature
+ * verification over `X-Signature-Ed25519` + `X-Signature-Timestamp`,
+ * `handleChallenge` for the `PING` handshake, `parseInbound` → route to an
+ * Agent, `reply` into the channel) is a follow-up (P2) — the `publicKey`
+ * setting is captured now so the connection is inbound-ready. Metadata
+ * therefore declares `direction: 'outbound'` with `inbound`/`reply`/
+ * `pairing` flags off until that runtime lands.
+ *
+ * See `docs/specs/features/connectors/spec.md` §7.5.1.
+ */
+declare class DiscordConnectorPlugin implements IConnectorPlugin {
+    readonly id = "discord-connector";
+    readonly name = "Discord Connector";
+    readonly version = "1.0.0";
+    readonly category: PluginCategory;
+    readonly capabilities: readonly ["connector", "connector-discord"];
+    readonly connector: ConnectorMetadata;
+    readonly settingsSchema: JsonSchema;
+    private readonly idempotencyCache;
+    onLoad(): Promise<void>;
+    onUnload(): Promise<void>;
+    verifyConnection(config: ChannelTargetConfig, _options: ConnectorCallOptions): Promise<ChannelVerification>;
+    send(payload: ChannelSendInput, options: ConnectorCallOptions): Promise<ChannelSendResult>;
+}
+declare const discordConnectorPlugin: DiscordConnectorPlugin;
+
+export { DiscordConnectorPlugin, discordConnectorPlugin };