@agentchatme/openclaw 0.6.3 → 0.6.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -44,9 +44,18 @@ type AgentchatChannelConfig = z.infer<typeof agentchatChannelConfigSchema>;
44
44
  /**
45
45
  * Parse + validate config at plugin startup.
46
46
  *
47
- * Fails fast on invalid config rather than waiting until the first request.
48
- * The `AgentChatChannelError` wrapper makes validation failures classifiable
49
- * by the gateway's error handler (`terminal-user` operator fix required).
47
+ * Strict on `apiKey` and the four nested groups `parseChannelConfig` is
48
+ * called only AFTER `resolveAgentchatAccount` has confirmed that the
49
+ * persisted config block is non-empty (see `channel.ts`), so an empty
50
+ * install-time config never reaches Zod. The runtime-time strictness here
51
+ * surfaces typos and out-of-range values fast. The OpenClaw install-time
52
+ * JSON Schema (emitted by `scripts/emit-manifest-schema.mjs`) is more
53
+ * permissive — see that script's post-process step for the rationale —
54
+ * so a freshly-installed plugin can pass install validation against an
55
+ * empty config block before the setup wizard fills in credentials.
56
+ *
57
+ * `AgentChatChannelError` wraps validation failures so the gateway can
58
+ * classify them (`terminal-user` — operator fix required).
50
59
  */
51
60
  declare function parseChannelConfig(input: unknown): AgentchatChannelConfig;
52
61
 
@@ -44,9 +44,18 @@ type AgentchatChannelConfig = z.infer<typeof agentchatChannelConfigSchema>;
44
44
  /**
45
45
  * Parse + validate config at plugin startup.
46
46
  *
47
- * Fails fast on invalid config rather than waiting until the first request.
48
- * The `AgentChatChannelError` wrapper makes validation failures classifiable
49
- * by the gateway's error handler (`terminal-user` operator fix required).
47
+ * Strict on `apiKey` and the four nested groups `parseChannelConfig` is
48
+ * called only AFTER `resolveAgentchatAccount` has confirmed that the
49
+ * persisted config block is non-empty (see `channel.ts`), so an empty
50
+ * install-time config never reaches Zod. The runtime-time strictness here
51
+ * surfaces typos and out-of-range values fast. The OpenClaw install-time
52
+ * JSON Schema (emitted by `scripts/emit-manifest-schema.mjs`) is more
53
+ * permissive — see that script's post-process step for the rationale —
54
+ * so a freshly-installed plugin can pass install validation against an
55
+ * empty config block before the setup wizard fills in credentials.
56
+ *
57
+ * `AgentChatChannelError` wraps validation failures so the gateway can
58
+ * classify them (`terminal-user` — operator fix required).
50
59
  */
51
60
  declare function parseChannelConfig(input: unknown): AgentchatChannelConfig;
52
61
 
@@ -1796,7 +1796,7 @@ var CircuitBreaker = class {
1796
1796
  };
1797
1797
 
1798
1798
  // src/version.ts
1799
- var PACKAGE_VERSION = "0.6.3";
1799
+ var PACKAGE_VERSION = "0.6.5";
1800
1800
 
1801
1801
  // src/outbound.ts
1802
1802
  var DEFAULT_RETRY_POLICY = {