@agentchatme/openclaw 0.6.10 → 0.6.11

package/dist/setup-entry-Dtj6vwDY.d.cts

@@ -1,104 +0,0 @@
-import * as openclaw_plugin_sdk_channel_core from 'openclaw/plugin-sdk/channel-core';
-import { defineChannelPluginEntry, ChannelPlugin } from 'openclaw/plugin-sdk/channel-core';
-import { z } from 'zod';
-
-/**
- * Zod schema for AgentChat channel config.
- *
- * Source of truth: this file. The JSON Schema inlined in `openclaw.plugin.json`
- * MUST stay in sync (P1 adds a build step that emits it via zod-to-json-schema).
- *
- * `.strict()` rejects unknown keys — a common source of "the config silently
- * ignored my setting" bugs.
- */
-
-declare const agentchatChannelConfigSchema: z.ZodObject<{
-    apiBase: z.ZodDefault<z.ZodString>;
-    apiKey: z.ZodString;
-    agentHandle: z.ZodOptional<z.ZodString>;
-    reconnect: z.ZodPrefault<z.ZodObject<{
-        initialBackoffMs: z.ZodDefault<z.ZodNumber>;
-        maxBackoffMs: z.ZodDefault<z.ZodNumber>;
-        jitterRatio: z.ZodDefault<z.ZodNumber>;
-    }, z.core.$strict>>;
-    ping: z.ZodPrefault<z.ZodObject<{
-        intervalMs: z.ZodDefault<z.ZodNumber>;
-        timeoutMs: z.ZodDefault<z.ZodNumber>;
-    }, z.core.$strict>>;
-    outbound: z.ZodPrefault<z.ZodObject<{
-        maxInFlight: z.ZodDefault<z.ZodNumber>;
-        sendTimeoutMs: z.ZodDefault<z.ZodNumber>;
-    }, z.core.$strict>>;
-    observability: z.ZodPrefault<z.ZodObject<{
-        logLevel: z.ZodDefault<z.ZodEnum<{
-            warn: "warn";
-            error: "error";
-            trace: "trace";
-            debug: "debug";
-            info: "info";
-        }>>;
-        redactKeys: z.ZodDefault<z.ZodArray<z.ZodString>>;
-    }, z.core.$strict>>;
-}, z.core.$strict>;
-type AgentchatChannelConfig = z.infer<typeof agentchatChannelConfigSchema>;
-/**
- * Parse + validate config at plugin startup.
- *
- * Strict on `apiKey` and the four nested groups — `parseChannelConfig` is
- * called only AFTER `resolveAgentchatAccount` has confirmed that the
- * persisted config block is non-empty (see `channel.ts`), so an empty
- * install-time config never reaches Zod. The runtime-time strictness here
- * surfaces typos and out-of-range values fast. The OpenClaw install-time
- * JSON Schema (emitted by `scripts/emit-manifest-schema.mjs`) is more
- * permissive — see that script's post-process step for the rationale —
- * so a freshly-installed plugin can pass install validation against an
- * empty config block before the setup wizard fills in credentials.
- *
- * `AgentChatChannelError` wraps validation failures so the gateway can
- * classify them (`terminal-user` — operator fix required).
- */
-declare function parseChannelConfig(input: unknown): AgentchatChannelConfig;
-
-/**
- * ChannelStatusAdapter — account health + configured-state probe.
- *
- * `probeAccount` hits `/v1/agents/me` with a short timeout and reports
- * whether the configured key still authenticates and whether the account
- * is active / restricted / suspended. The gateway uses this to surface a
- * red/yellow/green status in `openclaw channels status` and to decide when
- * to page an operator for stuck accounts.
- */
-
-type AgentchatProbeResult = {
-    readonly ok: boolean;
-    readonly handle?: string;
-    readonly status?: 'active' | 'restricted' | 'suspended' | 'deleted';
-    readonly pausedByOwner?: 'none' | 'send' | 'full';
-    readonly error?: string;
-};
-
-interface AgentchatResolvedAccount {
-    accountId: string;
-    enabled: boolean;
-    configured: boolean;
-    config: AgentchatChannelConfig | null;
-    parseError: string | null;
-}
-declare const agentchatPlugin: ChannelPlugin<AgentchatResolvedAccount, AgentchatProbeResult>;
-/**
- * Canonical channel-entry descriptor consumed by OpenClaw's extension loader.
- * Exported as `default` because `openclaw.extensions` in package.json points to
- * this module and the loader reads the default export.
- *
- * The explicit `ReturnType<...>` annotation pins the emitted `.d.ts` to the
- * function signature instead of the structural shape — otherwise the inferred
- * type references `ChannelConfigSchema` through a non-exported path and TS
- * fails with TS2742 ("cannot be named without a reference to ...").
- */
-declare const agentchatChannelEntry: ReturnType<typeof defineChannelPluginEntry<typeof agentchatPlugin>>;
-
-declare const agentchatSetupEntry: {
-    plugin: openclaw_plugin_sdk_channel_core.ChannelPlugin<AgentchatResolvedAccount, AgentchatProbeResult>;
-};
-
-export { type AgentchatChannelConfig as A, type AgentchatResolvedAccount as a, agentchatChannelEntry as b, agentchatPlugin as c, agentchatSetupEntry as d, parseChannelConfig as p };

package/dist/setup-entry-Dtj6vwDY.d.ts

@@ -1,104 +0,0 @@
-import * as openclaw_plugin_sdk_channel_core from 'openclaw/plugin-sdk/channel-core';
-import { defineChannelPluginEntry, ChannelPlugin } from 'openclaw/plugin-sdk/channel-core';
-import { z } from 'zod';
-
-/**
- * Zod schema for AgentChat channel config.
- *
- * Source of truth: this file. The JSON Schema inlined in `openclaw.plugin.json`
- * MUST stay in sync (P1 adds a build step that emits it via zod-to-json-schema).
- *
- * `.strict()` rejects unknown keys — a common source of "the config silently
- * ignored my setting" bugs.
- */
-
-declare const agentchatChannelConfigSchema: z.ZodObject<{
-    apiBase: z.ZodDefault<z.ZodString>;
-    apiKey: z.ZodString;
-    agentHandle: z.ZodOptional<z.ZodString>;
-    reconnect: z.ZodPrefault<z.ZodObject<{
-        initialBackoffMs: z.ZodDefault<z.ZodNumber>;
-        maxBackoffMs: z.ZodDefault<z.ZodNumber>;
-        jitterRatio: z.ZodDefault<z.ZodNumber>;
-    }, z.core.$strict>>;
-    ping: z.ZodPrefault<z.ZodObject<{
-        intervalMs: z.ZodDefault<z.ZodNumber>;
-        timeoutMs: z.ZodDefault<z.ZodNumber>;
-    }, z.core.$strict>>;
-    outbound: z.ZodPrefault<z.ZodObject<{
-        maxInFlight: z.ZodDefault<z.ZodNumber>;
-        sendTimeoutMs: z.ZodDefault<z.ZodNumber>;
-    }, z.core.$strict>>;
-    observability: z.ZodPrefault<z.ZodObject<{
-        logLevel: z.ZodDefault<z.ZodEnum<{
-            warn: "warn";
-            error: "error";
-            trace: "trace";
-            debug: "debug";
-            info: "info";
-        }>>;
-        redactKeys: z.ZodDefault<z.ZodArray<z.ZodString>>;
-    }, z.core.$strict>>;
-}, z.core.$strict>;
-type AgentchatChannelConfig = z.infer<typeof agentchatChannelConfigSchema>;
-/**
- * Parse + validate config at plugin startup.
- *
- * Strict on `apiKey` and the four nested groups — `parseChannelConfig` is
- * called only AFTER `resolveAgentchatAccount` has confirmed that the
- * persisted config block is non-empty (see `channel.ts`), so an empty
- * install-time config never reaches Zod. The runtime-time strictness here
- * surfaces typos and out-of-range values fast. The OpenClaw install-time
- * JSON Schema (emitted by `scripts/emit-manifest-schema.mjs`) is more
- * permissive — see that script's post-process step for the rationale —
- * so a freshly-installed plugin can pass install validation against an
- * empty config block before the setup wizard fills in credentials.
- *
- * `AgentChatChannelError` wraps validation failures so the gateway can
- * classify them (`terminal-user` — operator fix required).
- */
-declare function parseChannelConfig(input: unknown): AgentchatChannelConfig;
-
-/**
- * ChannelStatusAdapter — account health + configured-state probe.
- *
- * `probeAccount` hits `/v1/agents/me` with a short timeout and reports
- * whether the configured key still authenticates and whether the account
- * is active / restricted / suspended. The gateway uses this to surface a
- * red/yellow/green status in `openclaw channels status` and to decide when
- * to page an operator for stuck accounts.
- */
-
-type AgentchatProbeResult = {
-    readonly ok: boolean;
-    readonly handle?: string;
-    readonly status?: 'active' | 'restricted' | 'suspended' | 'deleted';
-    readonly pausedByOwner?: 'none' | 'send' | 'full';
-    readonly error?: string;
-};
-
-interface AgentchatResolvedAccount {
-    accountId: string;
-    enabled: boolean;
-    configured: boolean;
-    config: AgentchatChannelConfig | null;
-    parseError: string | null;
-}
-declare const agentchatPlugin: ChannelPlugin<AgentchatResolvedAccount, AgentchatProbeResult>;
-/**
- * Canonical channel-entry descriptor consumed by OpenClaw's extension loader.
- * Exported as `default` because `openclaw.extensions` in package.json points to
- * this module and the loader reads the default export.
- *
- * The explicit `ReturnType<...>` annotation pins the emitted `.d.ts` to the
- * function signature instead of the structural shape — otherwise the inferred
- * type references `ChannelConfigSchema` through a non-exported path and TS
- * fails with TS2742 ("cannot be named without a reference to ...").
- */
-declare const agentchatChannelEntry: ReturnType<typeof defineChannelPluginEntry<typeof agentchatPlugin>>;
-
-declare const agentchatSetupEntry: {
-    plugin: openclaw_plugin_sdk_channel_core.ChannelPlugin<AgentchatResolvedAccount, AgentchatProbeResult>;
-};
-
-export { type AgentchatChannelConfig as A, type AgentchatResolvedAccount as a, agentchatChannelEntry as b, agentchatPlugin as c, agentchatSetupEntry as d, parseChannelConfig as p };

package/dist/setup-entry.d.cts

@@ -1,3 +0,0 @@
-export { d as agentchatSetupEntry, c as agentchatSetupPlugin, d as default } from './setup-entry-Dtj6vwDY.cjs';
-import 'openclaw/plugin-sdk/channel-core';
-import 'zod';

package/dist/setup-entry.d.ts

@@ -1,3 +0,0 @@
-export { d as agentchatSetupEntry, c as agentchatSetupPlugin, d as default } from './setup-entry-Dtj6vwDY.js';
-import 'openclaw/plugin-sdk/channel-core';
-import 'zod';